Duplicate Standby : Issues & Issues all the way

Well doing,

All the DBA's using the duplicate database to build a standby database and its proved most of the times it works. But it happens sometimes that it creates a series of issues.

Thanks to our good old DBA Basavaraju (a very long time DBA) for pointing out this series of issues and permitted me to update in this blog for all benefit.

Here is the environment he was building

1. 11.2.0.3 with Grid Infrastructure
2. Primary 2 nodes and standby with single node rac
3. Using Duplicate database from active database to build standby

Issue 1:- "RMAN-06217: not connected to auxiliary database with a net service name"

Solution:- Ensure not to use Scan IP's of production box during DR Creation with the Duplicate command to avoid the issue change the Local_listener = Local VIP in both sides.

Issue 2:- "RMAN-04006: error from auxiliary database: ORA-12154: TNS:could not resolve the connect identifier specified"

Solution :- Ensure tnsnames. ora has "(UR=A)" to avoid the below error at both the locations(DR & Primary)

Issue 3:- "Undefined subroutine &main::read_file called at /u01/gi/oragrid/grid/11.2.0.2/crs/install/crspatch.pm line 86."

Solution:- We have mandatory patch to apply 12880299, to fix poison attack, Its a bug, change the $GI_HOME/OUI/bin/crsconfig_lib.pm
Make the following change in that file crsconfig_lib.pm From
my @exp_func = qw(check_CRSConfig validate_olrconfig validateOCR
To
my @exp_func = qw(check_CRSConfig validate_olrconfig validateOCR read_file
Above issue would be fixed with this above change and also it would start the has services.

Issue 4:- ORA-00245: control file backup failed; target is likely on a local file system

Solution:- RMAN> CONFIGURE SNAPSHOT CONTROLFILE NAME TO '+FRA/test/snapcf_opartl2.f';

Issue 5:- PLS-00201: identifier 'DBMS_RCVCAT.GETDBID' must be declared

Solution:- Use nocatalog in the rman connection script, like this this rman target sys@source auxiliary sys@targer nocatalog

Issue 6:- ERROR: failed to establish dependency between database target(standby) and diskgroup resource ora.DATA2.dg

Solution:- srvctl modify database -d targetdbname -a "DATA2,RECO2"
srvctl add database -d targetdbname -o /u01/app/oracle/product/11.2.0.4/dbhome_1

Issue 7:- Once you create the Stanadby arch no more applied, failed with error Error 1017 received logging on to the standby , ERror-16197

Solution:- Although you copy password files from production set param case_sensitivity_logon = false and also while creating password file use ignorecase=y option

Oop's very unfortunate day then, lots of issues in sequence for a standby from a well known feature duplicate standby. Hope the above helps if you fall down in this trap.

-Thanks
Geek DBAGeek DBA