Skip Headers
Oracle® Database Reference
12c Release 1 (12.1)

E17615-23
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

DB_SECUREFILE

Property Description
Parameter type String
Syntax DB_SECUREFILE = { NEVER | PERMITTED | PREFERRED | ALWAYS | IGNORE }
Default value PERMITTED if the COMPATIBLE initialization parameter is set to 11.2.0.1, 11.2.0.2, or 11.2.0.3, or PREFERRED if the COMPATIBLE initialization parameter is set to 12.0.0.0 or higher
Modifiable ALTER SESSION, ALTER SYSTEM
Basic No

DB_SECUREFILE specifies whether to treat LOB files as SecureFiles.

Values:

If the 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 ALTER SYSTEM statement