Trying to implement MAA on 4node race(urgent)
Subject: Trying to implement MAA on 4node race
RDBMS Version: 10.2.0.3
Operating System and Version: Solaris 5.9
Error Number (if applicable): ORA-12154
Product (i.e. SQL*Loader, Import, etc.): DATAGUARD
Product Version: 10.2.0.3
Trying to implement MAA on 4node race
Can anyone clarify my questions related to RAC & DATAGUARD.
We are trying to implement 4node physical standby, our primary is a 4node RAC.
How does oracle ship the archive logs and apply at the secondary(physical standby). Does we need to mount all the instances on the physical standby or only one instance?
what we have done is mounted one instance recovered the primary database at physical standby.
We are currently shipping the logs manually and recovering at the physical. we are hoping that the automatic shipping of archive logs and recovery at the physical, will catch up when its current. Is my assumption correct???
On the primary we see the following eroors:
Redo shipping client performing standby login
OCIServerAttach failed -1
.. Detailed OCI error val is 12154 and errmsg is 'ORA-12154: TNS:could not resolve the connect identifier specified
'
*** 2007-11-05 14:56:12.338 61287 kcrr.c
Error 12154 received logging on to the standby
Error 12154 connecting to destination LOG_ARCHIVE_DEST_3 standby host 'CP00TSG002'
Error 12154 attaching to destination LOG_ARCHIVE_DEST_3 standby host 'CP00TSG002'
ORA-12154: TNS:could not resolve the connect identifier specified
*** 2007-11-05 14:56:12.338 61287 kcrr.c
PING[ARC1]: Heartbeat failed to connect to standby 'CP00TSG002'. Error is 12154.
*** 2007-11-05 14:56:12.338 59530 kcrr.c
kcrrfail: dest:3 err:12154 force:0 blast:1
*** 2007-11-05 15:01:16.450
Redo shipping client performing standby login
OCIServerAttach failed -1
.. Detailed OCI error val is 12154 and errmsg is 'ORA-12154: TNS:could not resolve the connect identifier specified
'
*** 2007-11-05 15:01:18.208 61287 kcrr.c
Error 12154 received logging on to the standby
Error 12154 connecting to destination LOG_ARCHIVE_DEST_3 standby host 'CP00TSG002'
Error 12154 attaching to destination LOG_ARCHIVE_DEST_3 standby host 'CP00TSG002'
ORA-12154: TNS:could not resolve the connect identifier specified
*** 2007-11-05 15:01:18.209 61287 kcrr.c
PING[ARC1]: Heartbeat failed to connect to standby 'CP00TSG002'. Error is 12154.
*** 2007-11-05 15:01:18.209 59530 kcrr.c
kcrrfail: dest:3 err:12154 force:0 blast:1
*** 2007-11-05 15:06:22.682
Redo shipping client performing standby login
OCIServerAttach failed -1
.. Detailed OCI error val is 12154 and errmsg is 'ORA-12154: TNS:could not resolve the connect identifier specified
'
*** 2007-11-05 15:06:23.460 61287 kcrr.c
Error 12154 received logging on to the standby
Error 12154 connecting to destination LOG_ARCHIVE_DEST_3 standby host 'CP00TSG002'
Error 12154 attaching to destination LOG_ARCHIVE_DEST_3 standby host 'CP00TSG002'
ORA-12154: TNS:could not resolve the connect identifier specified
*** 2007-11-05 15:06:23.460 61287 kcrr.c
PING[ARC1]: Heartbeat failed to connect to standby 'CP00TSG002'. Error is 12154.
*** 2007-11-05 15:06:23.460 59530 kcrr.c
kcrrfail: dest:3 err:12154 force:0 blast:1
**************************************************************************************************** ****
we are unable to find why we are getting these errors.
Can anyone let me know how MAA functions. I mean..4 node RAC shipping logs and applying at 4 node physical standby.........
can you clear this out why automatic shipping of archivelogs is not happening?....and the errors on the primary rac?
Thanks in advance..
