Database Reference
In-Depth Information
There are some
ALTER DATABASE
and
ALTER SYSTEM
statements that fail in a PDB if
NONCDB_COMPATIBLE=FALSE
, but they will succeed if
NONCDB_COMPATIBLE
is set to
TRUE
.
PDB_FILE_NAME_CONVERT
When you're creating a pluggable database as a copy or clone of another PDB or non-CDB, the
PDB_FILE_NAME_CONVERT
parameter is used to map directory names of source files to the direc-
tory name of new target files when using the
CREATE PLUGGABLE DATABASE
command. Also
this parameter is used when the
CREATE DATABASE ENABLE PLUGGABLE DATABASE
command is
issued, when Oracle Managed Files is not enabled, and if the
FILE_NAME_CONVERT_CLAUSE
is
not used. Do not use filenames or directories that use Oracle Managed Files. The parameter
values need to be a string that includes valid directory names. There is no default value.
Here's an example
PDB_FILE_NAME_CONVERT = 'C:\oradata\dbs\s1\','C:\oradata\dbs\t1\', 'C:\oradata\
dbs\s2\','C:\oradata\dbs\t2\'
where source and target alternate.
RESOURCE_MANAGER_PLAN
In a non-CDB,
RESOURCE_MANAGER_PLAN
specifies the top-level resource plan to use for
the instance.
In the
CDB$ROOT
of a CDB,
RESOURCE_MANAGER_PLAN
specifies the resource plan for
the CDB, which allocates resources among PDBs. You create a CDB resource plan with the
DBMS_RESOURCE_MANAGER.CREATE_CDB_PLAN
and
CREATE_CDB_PLAN_DIRECTIVE
procedures.
A common user must be logged into
CDB$ROOT
and use the
ALTER SYSTEM
command to
change the
RESOURCE_MANAGER_PLAN
for a CDB, for example:
SQL> ALTER SYSTEM SET RESOURCE_MANAGER_PLAN = mycdb_resource_plan;
SQL> ALTER SYSTEM SET RESOURCE_MANAGER_PLAN = '';
In a PDB,
RESOURCE_MANAGER_PLAN
indicates the PDB resource plan to use for this PDB.
A session must have its current container set to the PDB to enable or disable a PDB resource
plan for this PDB. The following limitations apply to PDB resource plans:
They cannot have subplans.
■
They can have a maximum of eight consumer groups.
■
They can't have a multiple-level scheduling policy.
The CDB resource plan should contain policies regarding resource allocation among PDBs.
■
SESSIONS
The
SESSIONS
initialization parameter specifies the maximum number of sessions that can be
created in the CDB. This parameter determines the maximum number of concurrent users in
Search WWH ::
Custom Search