| PING[ARCX]: Heartbeat failed to connect to standby 'XXX'. Error is 1034 [message #655513] |
Thu, 01 September 2016 02:40  |
 |
RenataS
Messages: 7
Registered: September 2016
|
Junior Member |
|
|
Hello,
I'm new to oracle and for now i'm trying to configure data guard physical standby.
Seems my primary and standby databases cannot communicate properly (there are two servers in the same network)
I found the following error in alert logs on Primary database:
Thu Sep 01 03:14:25 2016
Error 1034 received logging on to the standby
PING[ARC3]: Heartbeat failed to connect to standby 'Standby'. Error is 1034.
tpsping is OK to both sides
I can connect from standby db to primary as sysdba, but cannot connect to standby from primary
ERROR:
ORA-01017: invalid username/password; logon denied
Do I understand correctly that if i can connect from standby to primary with the same account/password that i use when connection from primary to standby, the error is not related to password file?
Or please correct me
And if password file is not he reason, what can be checked/modified in my configuration?
Could please anyone advise me what to check or the direction where i can find the answer?
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Re: PING[ARCX]: Heartbeat failed to connect to standby 'XXX'. Error is 1034 [message #655526 is a reply to message #655524] |
Thu, 01 September 2016 04:02  |
John Watson
Messages: 8962
Registered: January 2010
Location: Global Village
|
Senior Member |
|
|
I realize that you are probably getting irritated by repeated requests for information. However, you need to show what you actually did, and what happened. For example:$
$ orapwd file=$ORACLE_HOME/dbs/orapwPrimary password=oracle_4U force=y
$ ls -l $ORACLE_HOME/dbs/orapwPrimary
-rw-r----- 1 oracle oinstall 7680 Sep 1 04:59 /u01/app/oracle/product/12.1.0/dbhome_2/dbs/orapwPrimary
$
|
|
|
|
|
|
| Re: PING[ARCX]: Heartbeat failed to connect to standby 'XXX'. Error is 1034 [message #655542 is a reply to message #655532] |
Thu, 01 September 2016 11:31 |
John Watson
Messages: 8962
Registered: January 2010
Location: Global Village
|
Senior Member |
|
|
Can you show your db_name, db_unique_name, and instance_name parameters at both sites? Having a mixed-case instance name, Primary, is a bit odd.
Then run lsnrctl status at each site, to see what service names and instance names are being registered.
Then delete the password files, and confirm by querying v$pwfile_users that the databases can no longer see their password files. That should prove that you are using the pw files that you think you are using.
Lastly, create a new one like this:orapwd file=$ORACLE_HOME/dbs/orapwNAME_OF_THE_INSTANCE password=oracle entries=10 ignorecase=y
|
|
|
|
| Re: PING[ARCX]: Heartbeat failed to connect to standby 'XXX'. Error is 1034 [message #655558 is a reply to message #655542] |
Fri, 02 September 2016 01:14 |
|
RenataS
Messages: 7
Registered: September 2016
|
Junior Member |
|
|
Hello John,
Parameters on my Primary:
SQL> sho parameter db_name
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
db_name string Primary
SQL> sho parameter db_unique_name
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
db_unique_name string Primary
SQL> sho parameter instance_name
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
instance_name string Primary
SQL> sho parameter db_name
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
db_name string Primary
SQL> sho parameter db_unique_name
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
db_unique_name string Standby
SQL> sho parameter instance_name
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
instance_name string Primary
Listener on Primary
[oracle@primary ~]$ lsnrctl status
LSNRCTL for Linux: Version 11.2.0.4.0 - Production on 02-SEP-2016 01:47:48
Copyright (c) 1991, 2013, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=10.10.111.132)(PORT=1521 )))
STATUS of the LISTENER
------------------------
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.4.0 - Production
Start Date 31-AUG-2016 05:05:12
Uptime 1 days 20 hr. 42 min. 44 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/app/oracle/product/11.2.0.4/dbhome_1/network/admi n/listener.ora
Listener Log File /u01/app/oracle/diag/tnslsnr/primary/listener/alert/lo g.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.10.111.132)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
Services Summary...
Service "PRIMARY.WORLD" has 1 instance(s).
Instance "Primary", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
[oracle@standby ~]$ lsnrctl status
LSNRCTL for Linux: Version 11.2.0.4.0 - Production on 02-SEP-2016 01:48:58
Copyright (c) 1991, 2013, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=10.10.111.125)(PORT=1521 )))
STATUS of the LISTENER
------------------------
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.4.0 - Production
Start Date 30-AUG-2016 07:51:29
Uptime 2 days 17 hr. 57 min. 40 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/app/oracle/product/11.2.0.4/dbhome_1/network/admi n/listener.ora
Listener Log File /u01/app/oracle/diag/tnslsnr/standby/listener/alert/lo g.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.10.111.125)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
Services Summary...
Service "PRIMARY.WORLD" has 1 instance(s).
Instance "PRIMARY", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
SQL> select * from v$pwfile_users;
USERNAME SYSDB SYSOP SYSAS
------------------------------ ----- ----- -----
SYS TRUE TRUE FALSE
SQL> select * from v$pwfile_users;
USERNAME SYSDB SYSOP SYSAS
------------------------------ ----- ----- -----
SYS TRUE TRUE FALSE
I've deleted the password file on both sites and got the following output on Primary and Standby:
SQL> select * from v$pwfile_users;
no rows selected
Then created the password file again and copied it to standby:
[oracle@primary dbs]$ orapwd file=$ORACLE_HOME/dbs/orapwPrimary password=oracle entries=10 ignorecase=y
[oracle@primary dbs]$ ll
total 9544
-rw-rw----. 1 oracle oinstall 1544 Aug 31 09:09 hc_Primary.dat
-rw-r--r--. 1 oracle oinstall 2851 May 15 2009 init.ora
-rw-r-----. 1 oracle oinstall 24 Aug 30 05:30 lkPRIMARY
-rw-r-----. 1 oracle oinstall 2560 Sep 2 01:57 orapwPrimary
-rw-r-----. 1 oracle oinstall 9748480 Aug 30 06:56 snapcf_Primary.f
-rw-r-----. 1 oracle oinstall 4608 Aug 31 10:36 spfilePrimary.ora
[oracle@primary dbs]$ scp orapwPrimary oracle@10.10.111.125:/u01/app/oracle/product/11.2.0.4/dbhome_1/dbs
oracle@10.10.111.125's password:
orapwPrimary 100% 2560 2.5KB/s 00:00
[oracle@primary dbs]$
SQL> select * from v$pwfile_users;
USERNAME SYSDB SYSOP SYSAS
------------------------------ ----- ----- -----
SYS TRUE TRUE FALSE
The same issue
On Primary:
SQL> connect sys/oracle@Standby as sysdba
ERROR:
ORA-01017: invalid username/password; logon denied
on Standby:
SQL> connect sys/oracle@Primary as sysdba
Connected.
|
|
|
|
| Re: PING[ARCX]: Heartbeat failed to connect to standby 'XXX'. Error is 1034 [message #655565 is a reply to message #655558] |
Fri, 02 September 2016 03:22 |
John Watson
Messages: 8962
Registered: January 2010
Location: Global Village
|
Senior Member |
|
|
I see some anomalies.
First, it appears that you have not configured your local_listener parameters correctly: the instances are not dynamically registering with their listeners. That needs to be corrected. On the primary, this:alter system set local_listener='10.10.111.132:1521'
Second, your static registrations in the listeners' SID_LISTs are for services with a .world suffix. That was an old release 9 default. Get rid of it, and then adjust your tnsnames entries to connect to the service_name, not the SID. Eventually you'll need to add entries for the DGMGRL services too, so that you can use the Data Guard Broker.
Third, you need to check whether that .world domain is anywhere else, such as the db_domain parameter or the database global name or any database links, and if so get rid of it.
Possibly this will fix it. Possibly....
|
|
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
) and (since you mentioned it) the tnspings. 
