Home » Server Options » Data Guard » Heartbeat failed to connect to standby (11.1.0.6.0)
Heartbeat failed to connect to standby [message #348121] Mon, 15 September 2008 13:06 Go to next message
Alps
Messages: 28
Registered: November 2006
Location: Toronto
Junior Member
Hi guys,
My alert for primary is showing me these errors.

Errors in file /var/ORADUMP/diag/rdbms/test_devzon/TEST
ORA-16191: Primary log shipping client not logged on standby
PING[ARC1]: Heartbeat failed to connect to standby 'STANDBY_TEST'
Mon Sep 15 14:07:59 2008
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
------------------------------------------------------------
Errors in file /var/ORADUMP/diag/rdbms/testsxu_devzon/TEST/trace/TEST_arc1_10396.trc:
ORA-16191: Primary log shipping client not logged on standby
PING[ARC1]: Heartbeat failed to connect to standby 'STANDBY_TEST'. Error is 16191.

But I can connect from standby and primary as follows.


Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - 64bit Production
With the Partitioning, Oracle Label Security, OLAP, Data Mining,
Oracle Database Vault and Real Application Testing options

SQL> connect sys/XXXXX@PRIMARY_TEST AS SYSDBA
Connected.
SQL> connect sys/XXXXX@STANDBY_TEST AS SYSDBA
Connected.
SQL>

Re: Heartbeat failed to connect to standby [message #348129 is a reply to message #348121] Mon, 15 September 2008 13:57 Go to previous messageGo to next message
BlackSwan
Messages: 26766
Registered: January 2009
Location: SoCal
Senior Member
http://www.orafaq.com/forum/t/88153/0/
Please read & follow posting guidelines as stated in URL above

When did this last work?
What changed?


>SQL> connect sys/XXXXX@PRIMARY_TEST AS SYSDBA
>Connected.
>SQL> connect sys/XXXXX@STANDBY_TEST AS SYSDBA
>Connected.
>SQL>

do the same from BOTH systems.

Does listener.log file on standby show failed login attempt from Primary?
Provide CUT & PASTE proof.
Re: Heartbeat failed to connect to standby [message #348150 is a reply to message #348129] Mon, 15 September 2008 15:46 Go to previous messageGo to next message
Alps
Messages: 28
Registered: November 2006
Location: Toronto
Junior Member
When did this last work?
I am implementing on 11g

What changed?
Nothing changed yet still in process of getting archivelogs from primary

Standby listener log:
15-SEP-2008 16:41:33 * (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=TEST.sbuat.com)(CID=(PROGRAM=oracle)(HOST=sbdev)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=172.xx.xxxx.xxx)(PORT=xxxxx)) * establish *

My password file is the same on the both the database.

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
sec_case_sensitive_logon boolean FALSE

Let me know if you need any more information.

Thanks in advance
Re: Heartbeat failed to connect to standby [message #349105 is a reply to message #348150] Thu, 18 September 2008 22:20 Go to previous messageGo to next message
babuknb
Messages: 1736
Registered: December 2005
Location: NJ
Senior Member


what about your database GLOBAL_NAME and DB_NAME in primary & standby database?

Babu
Re: Heartbeat failed to connect to standby [message #385970 is a reply to message #348121] Thu, 12 February 2009 01:51 Go to previous message
prkaur
Messages: 1
Registered: February 2009
Junior Member
checking if this issue was resolved.

I am facing the same issue ....10204 on AIX

tnspings listener everything responds via sql prompt/server ... however when dataguard is started receive the same error.

Checked db_name and db_domain .. everyting is good and same for both instances (they are on different servers).

any pointer are apprecaiated.


Previous Topic: Failed to query v$archived_log to find archive gap exists on standby db (ORA-00235)
Next Topic: Log Apply Service
Goto Forum:
  


Current Time: Thu Mar 28 16:32:47 CDT 2024