After Upgrade to Oracle 11 -> Error 1034 received logging on to the standby

[Former Member]

Hi all,

After upgrading both databases to 11g verson:

The problem is on the standby database, automatic recovery is not working, evenb though is OK in manual mode.

Error Message on Oracle primary alert log (/oracle/dev/saptrace/diag/rdbms/dev/dev/trace)
Error 1034 received logging on to the standby

And in trace file :(/oracle/dev/saptrace/diag/rdbms/dev/dev/trace/dev_arc1.trc for example

OCISessionBegin failed -1
.. Detailed OCI error val is 1034 and errmsg is 'ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
IBM AIX RISC System/6000 Error: 2: No such file or directory
'
*** 2012-12-07 14:01:32.856 4320 krsh.c
Error 1034 received logging on to the standby
*** 2012-12-07 14:01:32.856 915 krsu.c
Error 1034 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'dev_STANDBY'
Error 1034 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'dev_STANDBY'
*** 2012-12-07 14:01:32.856 4320 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'dev_STANDBY'. Error is 1034.
*** 2012-12-07 14:01:32.856 2957 krsi.c
krsi_dst_fail: dest:2 err:1034 force:0 blast:1

Any hints ?

For now, I am applying the logs manually, but we need to fix the issue.

[stefan_koehler · Accepted solution]

Hi Jordan,

> Error 1034 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'dev_STANDBY'

This error is pretty clear. This error can have two root causes in your scenario. One reason is that the standby database is not mounted and the other one is that the (remote) database could not be identified.

Reason one is out of the game as you said you are applying the logs manually. You have performed an Oracle upgrade, so i am pretty sure, that there is a typo or mistake in the listener configuration on the standby side (like old/wrong ORACLE_HOME for example).

Regards

Stefan

[Former Member · Accepted solution]

Hi Stefan,

Nice, thanks. Solved

Jordy.