Redo transport failing for 1 node of 2 node RAC database - error is 12154
644720Nov 17 2010 — edited Nov 23 2010Hello,
I have a 2 node RAC primary database (db name is S2EMREP) Data Guarded to a 2 node RAC physical standby database (db name is S1EMREP). My problem is that the redo log for primary database S2EMREP node *2* is not being transported to the the standby database, as a result I cannot get the standby database into Managed Recovery. The redo log from the primary database S2EMREP node *1* however, is being successfully transported to the standby database. The sample output from the alert logs on both nodes of the primary database S2EMREP show below illustrates my problem.
Output from the alert log on primary database S2EMREP node 2 is as follows:-
Wed Nov 17 10:54:18 2010
Archived Log entry 28526 added for thread 2 sequence 7174 ID 0xebc06b9f dest 1:
Wed Nov 17 11:00:11 2010
Error 12154 received logging on to the standby
Errors in file /u01/app/oracle/diag/rdbms/s2emrep/emrep2/trace/emrep2_arc1_16453.trc:
ORA-12154: TNS:could not resolve the connect identifier specified
PING[ARC1]: Heartbeat failed to connect to standby 's1emrep'. Error is 12154.
Output from the alert log on primary database S2emreo node 1 (successful redo log transport) is as follows:-
Thread 1 advanced to log sequence 12218 (LGWR switch)
Current log# 2 seq# 12218 mem# 0: +DATA/s2emrep/onlinelog/group_2.279.732124779
Current log# 2 seq# 12218 mem# 1: +FRA/s2emrep/onlinelog/group_2.556.732124779
Wed Nov 17 11:05:54 2010
Archived Log entry 28530 added for thread 1 sequence 12217 ID 0xebc06b9f dest 1:
Wed Nov 17 11:05:54 2010
LNS: Standby redo logfile selected for thread 1 sequence 12218 for destination LOG_ARCHIVE_DEST_2
I have checked my TNSNAMES.ORA and SQLNET.ORA files on both primary and standby nodes many times and I just cannot see any potential errors. Additionally I can successfully TNSPING and connect with SQLPLUS to the standby database using the standby database service name S1EMREP from node 2 of the primary database, that is the node experiencing the redo transport problems. Sufficient standby redo logifiles for both redo log threads also exist on the standby database.
Any help in resolving this would be greatly appreciated.
Thanks in advance,
Shaun