Working with SecureFiles
Before discussing the implementation of advanced features in SecureFiles, we will see the creation of a SecureFile. The LOB clause makes the difference in the CREATE TABLE statement and decides whether the LOB has to behave as a BasicFile or SecureFile.
The interpreting behavior of the Oracle server depends upon a newly introduced parameter called db_securefile. It can accept the values as follows:
PERMITTED: This value allows DBA to create SecureFiles in the system of appropriate compatibility that is 11.1 and higher. It is the default value setting for thedb_securefileparameter.ALWAYS: Apart from normal SecureFiles, all BasicFiles on ASSM tablespaces are also treated as SecureFiles. But BasicFiles, which are created on a non-ASSM tablespace, are still BasicFiles.FORCE: All LOB columns (both with SecureFile and BasicFile specifications) are forced to be created as SecureFiles only. It does not allow any LOB column to be created on a non-ASSM tablespace.NEVER...
