Database Reference
In-Depth Information
In a CDB, the scope of the settings for
AUDIT_TRAIL
is the CDB. The audit trail is provided
per PDB in a CDB, but
AUDIT_TRAIL
is not configurable for individual PDBs.
ENABLE_PLUGGABLE_DATABASE
ENABLE_PLUGGABLE_DATABASE
must be set in
init.ora
before creating a CDB.
ENABLE_
PLUGGABLE_DATABASE
is a Boolean bootstrap initialization parameter that, when set to
TRUE
,
indicates that the DB is to be created as a CDB. When set to the default
FALSE
, the database
is created as a non-CDB.
LDAP_DIRECTORY_ACCESS
The
LDAP_DIRECTORY_ACCESS
initialization parameter is a string value and has no default;
valid options are
SSL
,
PASSWORD
, or
NONE
. All the PDBs in a CDB use the Oracle Internet
Directory (OID) authentication specified by the parameter. You use the DBCA to register
Oracle databases (including PDBs) with OID.
MAX_STRING_SIZE
The
MAX_STRING_SIZE
initialization parameter defaults to
STANDARD
, and a valid alternative
is
EXTENDED
. When set to
STANDARD
, the length limits of 4000 bytes for VARCHAR2 and
NVARCHAR2 and 2000 bytes for RAW apply. When set to
EXTENDED
and the
COMPATIBLE
initialization parameter is set to
12.0.0.0
or higher, the 32,767-byte limit introduced in
Oracle Database 12
c
applies.
You can change the value of
MAX_STRING_SIZE
from
STANDARD
to
EXTENDED
, but you can't
change it from
EXTENDED
to
STANDARD
. To take advantage of the increased column sizes in a
PDB, do the following:
1.
Shut down the PDB, and then restart it with the
STARTUP UPGRADE
command.
2.
Change
MAX_STRING_SIZE
in the PDB to
EXTENDED
by issuing the
ALTER SYSTEM SET
MAX_STRING_SIZE=EXTENDED
command.
3.
Connect
AS SYSDBA
and run the
$ORACLE_HOME\rdbms\admin\utl32k.sql
script in
the PDB.
4.
Restart the PDB.
NONCDB_COMPATIBLE
The
NONCDB_COMPATIBLE
Boolean parameter, default value
FALSE
, indicates that SQL executed
in a PDB will default to normal CDB behavior. If you have a specific case where SQL com-
mands executed in a PDB need to function as they do in a non-CDB, then set this value to
TRUE
. Specifically, if you have code that causes
ORA-65040
in the PDB, then setting
NONCDB_
COMPATIBLE
to
TRUE
may be required.
Search WWH ::
Custom Search