Dataguard for Single Pluggable database skipping the other PDBs

-

Setup and Backup script

When using Oracle multi-tenant architecture there can be situations where it is required to setup Dataguard only for single PDB, skipping the log replication of other PDBs. Below steps can be used to achieve the above configuration on Oracle 12C  setup. The steps mainly stays same to a normal dataguard setup but main difference comes during the recovery where it is required to skip the pdb which is not in the dataguard configuration.

Primeary Side PDB configuration is as below. Rman backup script is used to backup the CDB root, PDB$SEED and the PDB1. 
 SQL> show pdbs;  
   CON_ID CON_NAME            OPEN MODE RESTRICTED  
 ---------- ------------------------------ ---------- ----------  
      2 PDB$SEED             READ ONLY  NO  
      3 PDB1                 READ WRITE NO  
      4 PDB2                 READ WRITE NO  
 SQL> 

RMAN backup script --> 
 run  
 {  
 ALLOCATE CHANNEL CH1 DEVICE TYPE DISK FORMAT '/tmp_01/onlback/bk_mis_u%u_s%s_p%p_t%t';  
 ALLOCATE CHANNEL CH2 DEVICE TYPE DISK FORMAT '/tmp_01/onlback/bk_mis_u%u_s%s_p%p_t%t';  
 ALLOCATE CHANNEL CH3 DEVICE TYPE DISK FORMAT '/tmp_01/onlback/bk_mis_u%u_s%s_p%p_t%t';
 BACKUP DATABASE ROOT;
 BACKUP PLUGGABLE DATABASE "PDB$SEED" plus archivelog;  
 BACKUP PLUGGABLE DATABASE PDB1 plus archivelog;  
 }

Standby side restore and configuration

Create the standby control file, set the parameter file as per the requirements of dataguard (LOG_ARCHIVE_CONFIG, FAL, DG_CONFIG etc..) and copy the required backup pieces to Standby. These steps are equal to normal dataguard configuration 
 run  
 {  
 allocate channel c1 type disk;  
 backup current controlfile for standby;  
 }
Mount the standby database with standby controlfile and restore the backups of root database, PDB$SEED and the PDB1 as below. 
 run {  
 ALLOCATE CHANNEL c1 DEVICE TYPE DISK ;  
 ALLOCATE CHANNEL c2 DEVICE TYPE DISK ;  
 ALLOCATE CHANNEL c3 DEVICE TYPE DISK ;  
 restore database root;  
 restore database "PDB$SEED";  
 restore database PDB1;  
 }

Recovery

Once the restore is done, main difference comes with the recovery. During the recovery we need to skip the PDB2 and all it is tablespaces similar to below example script. Other wise recover will fail with "RMAN-06067: RECOVER DATABASE required with a backup or created control file" 
 run  
 {  
 recover database skip forever tablespace PDB2:SYSTEM,PDB2:USER,PDB2:SYSAUX,PDB2:USERS;  
 }
Once the recovery is completed skipping the PDB2, data guard configuration and the recover can be enabled similar to normal data guard setup.
Related Articles --

Comments

Post a Comment

Popular posts from this blog

ORA-16433: The database or pluggable database must be opened in read/write

-
Image
ORA-16433 is an error returned when a database cannot be opened. This can be a result of multiple conditions including, The inconsistency of the database Physical corruption Loss of dependent files or access issues etc.. More often than not the solution is to recover from available backups, but there can be situations where backups are not available, specially on UAT or Test setups. Although not the ideal scenario, in this type of situation you might want to open the databases even with inconsistency.  In Comes --> _ALLOW_RESETLOGS_CORRUPTION First, if you are in a position to use _ALLOW_RESETLOGS_CORRUPTION=TRUE, that means it has to be a critical moment, and when you come across more ora- errors while you are trying to reopen the databsae, that can be annoying. Note - _ALLOW_RESETLOGS_CORRUPTION=TRUE must only be used after Oracle support confirmation as a last resort. Also make sure to take cold backup before proceeding. Basic steps to be followed to resolve ORA 16433 after
Read more

Wait for unread message on broadcast channel - Blocking Sessions

-
Image
What is Wait for unread message on broadcast channel wait event? Wait for unread message on broadcast channel is a wait event where source destination communication is involved and the database is waiting for a reply from remote party. Mostly this wait is seen related to data pump export (expdp) or import (impdp) operations. Although categorized in idle wait class "Wait for unread message on broadcast channel" can become the blocking session for some other sessions. Common causes for stuck sessions waiting on this wait event includes, Broken databases links, where remote database is not responding. Abnormally killed remote processes causing the sessions to wait. When a session is waiting on "Wait for unread message on broadcast channel" it can become a blocking session for dependent sessions. Most probably these sessions will be waiting on "library cache pin" or related concurrency wait events. The blocking_session column of (g)v$session view
Read more

ORA-14126 - While splitting max value partition

-
Oracle version -- Oracle 9i to 11g While splitting partitions, SQL> alter TABLE ARBOR.CDR_BILLED split PARTITION CDR_BILLED_MAXVALUE at (TO_DATE('2014-09-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN')) into (partition CDR_BILLED_01SEP14,partition CDR_BILLED_MAXVALUE) TABLESPACE "C01_CDR_BILL" update global indexes; 2 into (partition CDR_BILLED_01SEP14,partition CDR_BILLED_MAXVALUE) TABLESPACE "C01_CDR_BILL" update global indexes * ERROR at line 2: ORA-14126: only a <parallel clause> may follow description(s) of resulting partitions 4:58:56 PM The reason for above error is while splitting max value partition, it is not allowed to explicitly provide a tablespace. The splitted partition will be reside on the same tablespace as the max value partitions. Below can be used without the tablespace clause to split the max value partition, alter TABLE ARBOR.CDR_BILLED split PARTITION CDR_BILLED_
Read more