Thursday, September 25, 2008

DB_SECUREFILE

Property

Description

Parameter type

String

Syntax

DB_SECUREFILE = { NEVER | PERMITTED | ALWAYS | IGNORE }

Default value

PERMITTED

Modifiable

ALTER SESSION, ALTER SYSTEM

Basic

No

DB_SECUREFILE specifies whether or not to treat LOB files as SecureFiles.

Values:

· NEVER

Any LOBs that are specified as SecureFiles are created as BasicFile LOBs. All SecureFile-specific storage options and features (for example, compress, encrypt, deduplicate) will cause an exception. The BasicFile LOB defaults will be used for storage options not specified.

· PERMITTED

LOBs are allowed to be created as SecureFiles.

· ALWAYS

All LOBs created in the system are created as SecureFile LOBs. If the LOB is not created in an Automatic Segment Space Managed tablespace, then an error will occur. Any BasicFile LOB storage options are ignored. The SecureFile defaults will be used for all storage options not specified.

· IGNORE

The SECUREFILE keyword and all SecureFile options are ignored.

If the COMPATIBLE initialization parameter is not set to 11.1 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 BasicFile LOBs.

Note:

1. This parameter was introduced in 11g.

2. Query for the current value of the parameter

select name, value, isdefault, isses_modifiable, issys_modifiable,

isinstance_modifiable, isdeprecated, description

from v$parameter

where upper(name) = ‘DB_SECUREFILE’;

Oracle initializatoin parameters

No comments:

Post a Comment