500th questions, 053500 questions

500th questions, 053500 questions

500. You opened the encryption wallet and then issued the following command:
SQL> CREATE TABLESPACE securespace
DATAFILE '/home/user/oradata/secure01.dbf'
SIZE 150 M
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.
Answer:B

Use this clause to specify the encryption properties of the tablespace. This clause does not actually encrypt the tablespace. You must also specifyENCRYPTKeyword as part ofDEFAULT storage_clauseIn this statement in order for the tablespace to be encrypted. In addition, you must already have usedALTER SYSTEM SET ENCRYPTION WALLET OPEN IDENTIFIED BY... To load the TDE master key into database memory for the duration of the instance, or establish a connection to the HSM to send the encrypted table and tablespace keys to the HSM and receive them back decrypted.

SALT | no salt SpecifySALTTo instruct the database to append a random string, called "salt," to the clear text of the column before encrypting it. This is the default.

SpecifyNO SALTTo prevent the database from appending salt to the clear text of the column before encrypting it.

The following considerations apply when specifyingSALTOrNO SALTFor encrypted columns:

• If you want to use the column as an index key, then you must specifyNO SALT. Refer to Oracle Database Advanced Security Administrator's Guide for a description of "salt" in this context.

• If you specify table compression for the table, then the database does not compress the data in encrypted columnsSALT.

You cannot specifySALTOrNO SALTFor LOB encryption.

Lab

SQL> CREATE TABLESPACE securespace
2 datafile 'e: \ oradata \ test \ secures01.dbf'
3 SIZE 150 M
4 encryption using '3des168'
5 default storage (ENCRYPT );
Create tablespace securespace
*
Row 3 has an error:
ORA-28365: Wallet not open

Copyright Disclaimer: This article is an original article by the blogger and cannot be reproduced without the permission of the blogger.