-
Which clause of the CREATE TABLE statement should you include for a LOB if you want to store the data as a SecureFile?
The STORE AS SECUREFILE clause
-
What is the recommended way to migrate traditional LOBs to SecureFiles?
Using online redefinition
-
When using online redefinition to migrate traditional LOBs to SecureFiles, are you required to take the table or partition offline?
No
-
For which type LOBs does the DBMS_SPACE.SPACE_USAGE procedure return space usage for LOB chunks?
Only for SecureFile LOBs
-
At which two levels can you use online redefinition to migrate traditional LOBs to SecureFiles?
At the table level or partition level
-
How large are the chunks of disk storage used with SecureFiles?
They vary from the data block size to 64 MB.
-
Which three settings can you configure for a specified LOB using the DBMS_LOB.SETOPTIONS procedure?
Encryption, compression, and deduplication settings
-
Which initialization parameter do you use to enable using SecureFiles?
The DB_SECUREFILE initialization parameter
-
What does the DBMS_SPACE.SPACE_USAGE procedure return for LOBs?
Information about LOB space usage for both SecureFiles and BasicFiles
-
When creating a SecureFile LOB using a CREATE TABLE statement, is encryption for the LOB enabled or disabled if you do not specify the ENCRYPT parameter?
Disabled
-
Are SecureFile LOBs cached in the buffer cache by default?
No, you must specify the CACHE parameter.
-
To create a SecureFile in a tablespace, what requirement must be met by the tablespace?
The tablespace must use automatic segment space management.
-
In which two ways can you migrate traditional LOBs to SecureFiles?
Using partition exchange or online redefinition
-
Which new Oracle 11g feature provides access to unstructured data, such as an LOB, but offers better performance than using the file system?
Oracle SecureFiles
-
What is the result of setting the DB_SECUREFILE initialization parameter to IGNORE?
BasicFiles are created even if the STORE AS SECUREFILE clause is specified.
-
What is the result of setting the DB_SECUREFILE initialization parameter to ALWAYS?
All LOBs created in ASSM tablespaces are created as SecureFiles, and those created in non-ASSM tablespaces are created as BasicFiles.
-
With default settings, what is the result if you create a table containing an LOB and do not specify the STORE AS SECUREFILE clause?
A BasicFile is created.
-
Which value for the DB_SECUREFILE initialization parameter indicates that all LOBs will be created as SecureFiles?
FORCE
-
Which LOB parameter should you include in your CREATE TABLE statement if you want to enable LOB compression?
The COMPRESS parameter
|
|
