Database Reference
In-Depth Information
the location of the files at the standby. If data files are in ASM, use the ASMCMD utility to
copy the files to this location at the standby database
<db_create_file_dest>/<db_unique_name>/<GUID>/datafile
where the GUID is queried from the
V$CONTAINERS
view at the source PDB, for example:
SELECT guid
FROM V$CONTAINERS
WHERE con_id=3;
GUID
--------------------------------
A491586A99E14806AEFBD366A80D18AD
SQL>
The standby database and primary database path name of the data files must be the
same, unless you have configured the
DB_FILE_NAME_CONVERT
initialization parameter on
the standby.
Creating a Logical Standby of a CDB
Creating a logical standby of a CDB is the same as creating a logical standby of a non-
CDB. However, there are some differences you need to know about when you create and
manage a logical standby CDB:
■
The primary or standby role is defined at the CDB, not in PDBs.
■
If you switch over to a standby, the entire CDB is switched over.
■
Role change DDL is executed in the
CDB$ROOT
.
■
PDBs do not have their own roles.
■
It is not a requirement to have the same PDBs at the primary and standby, but only tables
that exist in the same PDB at both the primary and standby databases are replicated.
■
Remember that many DBA views have analogous CDB views whose names begin with
CDB_
instead of
DBA_
, but they have an extra column to indicate the
CON_ID
, which is
associated with the PDB.
■
In a logical standby of a CDB some SQL statements do not have the same scope, or
they have only a local scope, relative to the same SQL statement in a non-CDB.
A primary or standby role is associated with an entire CDB. So, for example, the following
DDL associated with logical standbys affects the entire CDB:
■
ALTER DATABASE RECOVER TO LOGICAL STANDBY
■
ALTER DATABASE [PREPARE|COMMIT] TO SWITCHOVER
■
ALTER DATABASE ACTIVATE LOGICAL STANDBY
Search WWH ::
Custom Search