Database Reference
In-Depth Information
There are three different types of databases used:
A Container Database as described in Chapter 7. The CDBs are numbered, starting with CDB1
to n. Container Databases use Oracle Managed Files and Automatic Storage Management by
default. The database CDBFS is the only example where a CDB uses a XFS file system without
OMF. Such an approach is often found in environments where block level replication is used
or in Solaris zones.
The ORACLE_SID reflects the data center where the databases are located. In the
examples to follow you will notice data centers A to C. The SIDs therefore are named
databaseNAmeDataCenterName . The standby database for database CDB1 in data center B is
called CDB1DCB as a consequence.
The db_unique_name is set to equal the ORACLE_SID
This naming scheme is only one out of a million possible combinations. Most often companies have naming
schemes in use referring to continents, countries, cities, and so on. Regardless of how the naming scheme is
implemented, it is important to make it consistent.
An observer process for lights-out management is started in data center c to observe the CDBFS databases.
Implementing Data Guard on a file system
The implementation of Data Guard using a traditional file system requires a little more thought, since the database
administrator cannot rely on the OMF parameters db_create_file_dest and db_create_online_log_dest_n to
perform the file name conversion if needed on the fly. As you read in Chapter 7, file name conversion with PDBs has
to be taken care of. The same applies to a Data Guard environment, but on the CDB level. If you decided to use a
different directory structure for your standby database (mount points for example), ensure that the relevant file name
conversion parameters are set. Although you can specify the log file definition and a file name conversion pattern
during the execution of the RMAN duplicate database command as well, it is often easier to have the conversion
parameters in the initialization file of the standby database.
You begin the duplication process by copying the password file and a parameter file to the standby host. The
steps will be shown in more detail in the next section. The files should be copied into the dbs directory of the RDBMS
home. You should also add the new ORACLE_SID to the oratab file to make it easier to switch environments.
[oracle@server2 ~]$ echo "CDBFSDCB:/u01/app/oracle/product/12.1.0.1/dbhome_1:N:" >> /etc/oratab
The initialization file needs to be amended next. The stream editor sed is a great way to create an almost
workable initialization file:
[oracle@server2 dbs]$ sed -e "s/${PRIMARY_SID}/${ORACLE_SID}/g" $PRIMARY_INIT_FILE_LOC \
> ${ORACLE_HOME}/dbs/init${ORACLE_SID}.ora
Edit the file with your favorite editor and ensure the following parameters are set correctly:
db_name
db_unique_name
db_file_name_convert and log_file_name_convert
 
Search WWH ::




Custom Search