|Oracle® Database Reference
12c Release 1 (12.1)
|PDF · Mobi · ePub|
DB_SECUREFILE specifies whether to treat LOB files as SecureFiles.
Any LOBs that are specified as SecureFiles are created as BasicFiles LOBs. All SecureFiles-specific storage options and features (for example, compress, encrypt, deduplicate) will cause an exception. The BasicFiles LOB defaults will be used for storage options not specified.
LOBs are allowed to be created as SecureFiles.
All LOBs are created as SecureFiles unless
BASICFILE is explicitly specified in the LOB storage clause or the tablespace is a Manual Segment Space Management tablespace. When
PREFERRED is set, cases where
BASICFILE would otherwise be inherited from the partition or column level LOB storage are ignored; the LOBs will be created as SecureFiles instead.
Attempts to create all LOBs as SecureFiles LOBs but creates any LOBs not in an Automatic Segment Space Managed (ASSM) tablespace as BasicFiles LOBs, unless
SECUREFILE is explicitly specified. Any BasicFiles LOB storage options that are specified will be ignored and the SecureFiles LOB defaults will be used for all storage options not specified.
SECUREFILE keyword and all SecureFiles options are ignored.
COMPATIBLE initialization parameter is not set to
11.1.0 or higher, then LOBs are not treated as SecureFiles.
If there is a LOB column with two partitions (one that has a tablespace for which ASSM is enabled and one that has a tablespace for which ASSM is not enabled), then LOBs in the partition with the ASSM-enabled tablespace will be treated as SecureFiles and LOBs in the other partition will be treated as BasicFiles.
If an application is not certified with SecureFiles, the value of the
DB_SECUREFILE initialization parameter can be set to
PERMITTED to get the default behavior of Oracle Database 11g.
See Also:Oracle Database SecureFiles and Large Objects Developer's Guide for an example of setting this parameter using the