Troubleshoot ORA-16191: ORA-17629 with case studies in Active Dataguard ( Oracle 11g)

~ Troubleshoot ORA-16191: ORA-17629 with case studies in Active Dataguard ( Oracle 11g)
~ Troubleshoot : when standby server is out of synch
~ Troubleshoot : when archivelogs are not applying in standby side

Case:1:  ORA-16191

Error 1017 received logging on to the standby ( message fro alert log)
< ------------------------------------------------------------
< Check that the primary and standby are using a password file
< and remote_login_passwordfile is set to SHARED or EXCLUSIVE,
< and that the SYS password is same in the password files.
<       returning error ORA-16191
< ------------------------------------------------------------
< PING[ARC2]: Heartbeat failed to connect to standby 'STANDBY'. Error is 16191.
< Sat Jul 06 15:23:28 2013
< Error 1017 received logging on to the standby

If above error found from alert log in DR side, i.e., some body changed Primary sys password.

Solution: Recreate password file both Primary and DR side with same password and re-synch again.

Now do the following: e.g.,

SQL> alter database recover managed standby database cancel;
SQL> shut immediate;
SQL> startup nomount;
SQL> alter database mount standby database;
SQL> alter database recover managed standby database using  current logfile disconnect;

Case:2: : ORA-17627: ORA-01017

channel ORA_DISK_1: SID=33 device type=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 06/27/2012 15:05:53
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 06/27/2012 15:05:53
ORA-17629: Cannot connect to the remote database server
ORA-17627: ORA-01017: invalid username/password; logon denied
ORA-17629: Cannot connect to the remote database server

Solution:

RMAN> duplicate target database for standby from active database nofilenamecheck;

This may not work. do the following

RMAN> run {
allocate channel ch1 type disk;
allocate auxiliary channel stby1 type disk;
duplicate target database for standby from active database nofilenamecheck;
}

Case-3 : ORA-16191

Thu Nov 14 10:52:35 2013
Error 1017 received logging on to the standby
------------------------------------------------------------
Check that the primary and standby are using a password file
and remote_login_passwordfile is set to SHARED or EXCLUSIVE, and that the SYS password is same in the password files.
returning error ORA-16191

Solution:

1) In primary side:

Ship missed archive logs:
pass the password file again to standby side and rename it with standy database name in standby side.

2) In standby side:
e.g.,
SQL> alter database recover managed standby database cancel;
SQL> alter database recover managed standby database disconnect from session;
RMAN> catalog start with '/oracle/PRIMARY/flash_recovery_area/archivelogs';

Now check, sure archive logs will apply

Now you will find following type alerts in alert log file.

Thu Nov 14 12:17:07 2013
Media Recovery Log /oracle/PRIMARY/flash_recovery_area/archivelogs/1_7945_804801209.dbf
Thu Nov 14 12:17:34 2013
Media Recovery Waiting for thread 1 sequence 7946

Now do the following:

SQL> alter database recover managed standby database cancel;
SQL> shut immediate;
SQL> startup nomount;
SQL> alter database mount standby database;
SQL> alter database recover managed standby database using  current logfile disconnect;


Now sure it will start shipping

SQL> select max(sequence#) from v$archived_log where applied='YES';

MAX(SEQUENCE#)
--------------
          7951


Hope this document will help you.
Post your comments.