-

Born encrypted: Oracle AI Database 26ai

TDE has come a long way; from the humble beginnings of TDE column encryption in Oracle Database 10gR2 in July 2005 to automated and mandatory encryption for all Oracle databases that are controlled by OCI.

Starting with Oracle database 21c, DBCA (Database Configuration Assistant) can create encrypted (primary and standby) databases; this is documented here for 21c and here for 26ai (did you notice that TDE in 26ai has its own documentation book, separated from Data Redaction?)

Here is the 26ai dbca code part that encrypts your new database: 

  -configureTDE TRUE  \
    -tdeWalletRoot /local/directory/for/TDE/  \
    -tdeWalletLoginType LOCAL_AUTO_LOGIN  \
    -TdeWalletPassword <TDE wallet password>  \
    -encryptTablespaces SYSTEM:true,SYSAUX:true,USERS:true  \
    -createTDESepsWallet

Some remarks:
Default for "-encryptTablespaces": USERS tablespace will be encrypted in CDB$ROOT
Default for "-encryptPDBTablespaces": SYSTEM, SYSAUX and USERS will be encrypted in the PDB.
"-createTDESepsWallet" currently has no option for a local auto-open wallet
"-tdeAlgorithm" in 26ai is AES256 with XTS cipher mode.
"-tdeWalletRoot" can be any existing local directory (for RAC: ACFS or ASM)

The result will be:

    PDB_NAME        TBS_NAME        ENC_ALG MODE  ENC_STATUS
   --------------- --------------- ------- ----- ----------
   CDB$ROOT        SYSAUX          AES256  XTS   NORMAL
   CDB$ROOT        SYSTEM          AES256  XTS   NORMAL
   CDB$ROOT        USERS           AES256  XTS   NORMAL
   CDB$ROOT        TEMP            ----    ----  ----
   CDB$ROOT        UNDOTBS1        ----    ----  ----
   FINPDB26        SYSAUX          AES256  XTS   NORMAL
   FINPDB26        SYSTEM          AES256  XTS   NORMAL
   FINPDB26        USERS           AES256  XTS   NORMAL
   FINPDB26        TEMP            ----    ----  ----
   FINPDB26        UNDOTBS1        ----    ----  ----

Over the next few weeks, I will talk about the other TDE-related tricks that DBCA can do in 26ai.

Try it out for yourself: Grab Tim Hall's Vagrant scripts that build RAC and Data Guard databases and add TDE to your databases by default.

Location: San Diego, Kalifornien, USA

Comments

Post a Comment

Popular posts from this blog

-
TDE HEALTHCHECK  The TDE health-check was planned to give Oracle Support personnel a quick overview about your TDE setup, but eventually it was decided to include it in recent Oracle Database RUs in 19c and 26ai. In Oracle database 19c before 19.30, you need to apply patch 38486044 . It is very easy to use: First, compile it with: SQL> @$ORACLE_HOME/rdbms/admin/tde_healthcheck.sql To get the complete results, simply execute: SQL> execute tde_healthcheck.get_tde_healthcheck_report; Individual checks allow for a more targeted validation: SQL> exec tde_healthcheck.get_wallet_root; Display WALLET_ROOT from gv$parameter.  SQL> exec tde_healthcheck.get_wallet_ location; Where are my TDE wallets? Usually in WALLET_ROOT/tde   SQL> exec tde_healthcheck.get_tde_config; Shows the value of the parameter TDE_CONFIGURATION. SQL> exec tde_healthcheck.get_props_ details; Read the TDE configuration from internal tables.  SQL> exec tde_healthcheck.valida...
Read more

Upgrade encrypted databases to 26ai

-
  Oracle AI Database 26ai has been made available to all customers (on-prem or any cloud). With this, the "upgrade" question will come sooner rather than later. Upgrading to Oracle AI Database 26ai  is only possible from 19c and 21c , older releases cannot be directly upgraded to 26ai. If your 19c or 21c databases are encrypted, and TDE is set up with the old (desupported) sqlnet.ora parameters (ENCRYPTION_WALLET_LOCATION), upgrades will be blocked and pre-upgrade checks will fail with 'TDE_WALLET_ROOT_NOT_IN_USE'. You need to have WALLET_ROOT and TDE_CONFIGURATION set before the upgrade. Also, the GOST and ARIA encryption algorithms are desupported in 26ai; before upgrading, online-rekey those tablespaces to AES with XTS cipher mode; for upgrades via database links to 26ai CDBs, we have introduced the "rekey using" parameter: SQL> create pluggable database "FINANCE" from FINANCE@dblink rekey using 'AES256' MODE 'XTS'; ...
Read more
-
Encryption and Compression in Exadata: How It Really Works After a great vacation, I'm finally back with a new blog post. This one is about two weeks later than my usual Thursday schedule, but I hope you'll find it worth the wait. Today's topic is a question that comes up surprisingly often: how do compression and Transparent Data Encryption (TDE) actually work in Oracle Exadata? The answer is actually quite simple - with one important exception. Everything described here applies equally to Oracle Exadata and all of its deployment models, including ExaDB-C@C, ADB-C@C, ADB-D, and ExaDB-D, whether deployed on-premises, in OCI, or in supported third-party clouds. The Normal Data Path The fundamental rule is simple: Compression always happens before encryption. This has to be the case because encrypted data is essentially random and therefore cannot be compressed efficiently. Oracle's implementation of TDE tablespace encryption is fully compatible with Oracle compression t...
Read more