Select
the Server tab, and then click the Transparent Data Encryption link under the Security Heading.
You will see the page in Figure 9-10. In this example, there is no wallet created yet. The file
sqlnet.ora stores the location of the wallet using the ENCRYPTION_WALLET_LOCATION
variable. If this variable does not exist in sqlnet.ora, the wallet is created in $ORACLE_HOME/
admin/database_name/wallet, which in this example is /u01/app/oracle/admin/dw/wallet.
To create the encryption key and place it in the wallet, create a wallet password that is at least
ten characters long, a mix of upper- and lowercase letters, numbers, and punctuation. Clicking
OK creates the wallet, and you see the page in Figure 9-11.
?–
?–
FIGURE 9-10 Transparent Data Encryption: creating a wallet
344 Oracle Database 11g DBA Handbook
If your master key becomes compromised, you can use the page in Figure 9-10 to recreate the
master key. You can also close the wallet??”disabling Transparent Data Encryption??”and prevent
access to any encrypted table columns or tablespaces.
The equivalent SQL commands to create, open, and close a wallet are very straightforward
and probably take less time to type than using Oracle Enterprise Manager! To create a new key,
and create the wallet if it does not already exist, use the alter system command as follows:
SQL> alter system set encryption key identified by "Uni123#Lng";
System altered.
SQL>
Note the importance of putting the wallet key within double quotes; otherwise, the password
will map all lowercase characters and the wallet will not open.
Pages:
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562