Encryption at rest in Oracle secures data files, tablespaces, or specific columns with Transparent Data Encryption (TDE) so stolen disks expose only ciphertext.
Protect customer PII, comply with PCI-DSS/GDPR, and remove the need for application-level encryption. Even if a drive is stolen, data stays unreadable without the wallet key.
Enterprise Edition with the Advanced Security option is required. The database must be in ARCHIVELOG mode, and you need OS access to store the keystore (wallet).
Run ADMINISTER KEY MANAGEMENT commands as SYSDBA to create, open, and back up the software keystore that stores the master key.
1) Create directory /u01/app/oracle/keystores.
2) CREATE KEYSTORE.
3) OPEN KEYSTORE.
4) SET ENCRYPTION KEY.
Use ALTER TABLESPACE … ENCRYPTION ONLINE. Oracle rewrites each block in the background, so the tablespace remains available.
Yes—ALTER TABLE … MODIFY (column ENCRYPT) encrypts just the chosen columns, minimizing CPU overhead.
Query V$ENCRYPTED_TABLESPACES, DBA_TABLESPACES, and DBA_ENCRYPTED_COLUMNS for a quick audit trail.
Rotate the master key regularly, automate wallet backups, enable FORCE KEYSTORE CLOSE on shutdown, and monitor for any auto-login wallet exposure.
Run ALTER TABLESPACE … DECRYPT or ALTER TABLE … MODIFY (column DECRYPT) during low-traffic windows to avoid I/O spikes.
Expect ≤5% CPU increase for AES256. Use hardware acceleration (AES-NI) and keep tablespaces small to minimize rekey time.
No. Oracle encrypts/decrypts at the storage layer, so applications continue to issue normal SQL.
Column/Tablespace encryption rewrites existing blocks; you cannot encrypt just future rows. Use different tablespaces and move fresh data if partial coverage is needed.
Yes—Hybrid Columnar Compression works with TDE tablespaces, but data is compressed before encryption, so expect minor size changes.