Enable AI file encryption after enabling encryption
- Last Updated: February 11, 2026
- 1 minute read
- OpenEdge
- Version 13.0
- Documentation
If you specifically indicate that your AI files should not be encrypted when you first enable encryption on your database, you can enable them for encryption later, as follows:
- You can re-issue PROUTIL ENABLEENCRYPTION and add
-aiencryption enableto the command line, as shown:proutil dbname -C enableencryption -aiencryption enable -aiCipherName cipher-name
- You can indicate that AI files are to be encrypted when you begin AI operations, as
shown:
rfutil dbname -C aimage begin -aiencryption enable -aiCipherName cipher-nameBy default, if your database is enabled for encryption, enabling after-imaging attempts to enable encryption for your AI files.
- You can indicate that AI files are to be encrypted when you enable after-imaging with an
online backup, as shown:
probkup online dbname backupname -enableai -aiencryption enable -aiCipherName cipher-nameBy default, if your database is enabled for encryption, enabling after-imaging enables encryption for your AI files.
Note: You can use the same commands, with
-aiencryption
disable to turn off the encryption of your AI files.