You opened the encryption wallet and then issued the following command:
SQL>CREATE TABLESPACE securespace
DATAFILE ‘/home/user/oradata/secure01.dbf’
SIZE 150M
ENCRYPTION USING ‘3DES168’
DEFAULT STORAGE(ENCRYPT);
Then you closed the wallet. Later, you issued the following command to create the
EMPLOYEES table in the SECURESPACE tablespace and you use the NO SALT option for
the EMPID column.
What is the outcome?
A.
It creates the table and encrypts the data in it.
B.
It generates an error because the wallet is closed.
C.
It creates the table but does not encrypt the data in it.
D.
It generates an error because the NO SALT option cannot be used with the ENCRYPT
option.
I suggest reading
http://oracle.su/docs/11g/network.112/e10746/asotrans.htm#BABEBFBA
From Eamon’s link:
http://oracle.su/docs/11g/network.112/e10746/asotrans.htm#BABEBFBA
Closing the wallet disables all encryption and decryption operations. Any attempt to encrypt/decrypt data or access encrypted data results in the following error:
ORA-28365: wallet is not open