:

Error 604 received logging on to the standby

When setting up the environment for Change Data Capture (CDC), which uses streams and, in our case, archive redo log shipping, I noticed that it wouldn’t work straight away and there were some errors in the alert log of the primary database:

Wed Apr 07 09:37:59
Error 604 received logging on to the standby

I also noticed that there were more errors in an archiver trace log

Error 604 received logging on to the standby
Error 604 connecting to destination LOG_ARCHIVE_DEST_2 standby host ‘DB2’
Error 604 attaching to destination LOG_ARCHIVE_DEST_2 standby host ‘DB2’
*** 09:41:59.629 62692 kcrr.c
PING[ARC1]: Heartbeat failed to connect to standby ‘DB2’. Error is 604.
*** 09:41:59.629 60970 kcrr.c
kcrrfail: dest:2 err:604 force:0 blast:1

I also noticed that there were other errors at the same time:

.. Detailed OCI error val is 604 and errmsg is ‘ORA-00604: error occurred at recursive SQL level 1
ORA-04045: errors during recompilation/revalidation of HRADD_PKG
ORA-04052: error occurred when looking up remote object HRADD_PKG@DB2DB1.UK.COM
ORA-00604: error occurred at recursive SQL level 3
ORA-12154: TNS:could not resolve the connect identifier specified
ORA-06508: PL/SQL: could not find program unit being called: “HRADD_PKG”
ORA-06512: at line 3

This turned out to be an incorrectly named database link and once this was changed it all started working again. A very strange error and it could have been a coincidence that this happened at the same time but as soon as it was changed the CDC parts started working again as well. Unlikely to be a coincidence I think…

Database link names are definitely of concern when you have the parameter GLOBAL_NAMES set to true.

Like it, share it...

Category: Change Data Capture


Related Posts

Leave a Reply

Your email address will not be published. Required fields are marked *