Encryption at Rest
Options
ttAdmin has these options for encryption at rest of checkpoint and
transaction log files:
| Option | Description |
|---|---|
|
|
An ODBC connection string that specifies a database location, driver, and optionally other connection attribute settings. |
|
|
An ODBC data source name of the database to be administered. |
|
|
On an encrypted database, rotates the master and data encryption keys used to encrypt the checkpoint and transaction log files. Re-encrypts the database files using the new randomly-generated keys. On an unencrypted database, creates a master and data encryption keys to encrypt the checkpoint and transaction log files. Encrypts the database files using the new randomly-generated keys. The
Valid values for the
See Re-Keying an Encrypted Database in Oracle TimesTen In-Memory Database Security Guide. |
Examples
The database1 encrypted database needs its master and data
encryption keys rotated. Use the following ttAdmin command to
rotate the encryption keys for database1 and re-encrypt the
checkpoint and transaction log files.
% ttAdmin -rekey database1You can also use the -encrAlg option to change the encryption
algorithm used for the database.
% ttAdmin -rekey -encrAlg AES256 database1Notes
To rotate the encryption keys, the database must to be loaded into memory.
To encrypt an existing database for the first time, it is not necessary
to define the DbEncrypted and DbKeyWallet data
store attributes for the database in the odbc.ini file, just run
the ttAdmin utility with the -rekey and
-encrAlg options to encrypt the database.
Encryption attempts for an unencrypted database fail if the replication agent is running. See Replicating an Encrypted Database in Oracle TimesTen In-Memory Database Security Guide.