Shulou(Shulou.com)05/31 Report--

This article introduces the relevant knowledge of "how to solve DG error Error 1031 received logging on to the standby". In the operation of actual cases, many people will encounter such a dilemma, so let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

After the establishment of the DG, the alarm log of the main database has been reported with errors.

Error 1031 received logging on to the standby

PING [ARC2]: Heartbeat failed to connect to standby 'dgdb'. Error is 1031.

Sat Jul 29 17:19:48 2017

Reference: https://community.oracle.com/thread/4005017

Check the password file according to the above answer

View gv$pwfile_users

Main library

SQL > select * from gv$pwfile_users

INST_ID USERNAME SYSDB SYSOP SYSAS

1 SYS TRUE TRUE FALSE

Prepare the library

SQL > select * from gv$pwfile_users

No rows selected

Sure enough, there is a problem with the password file, and the standby library does not use the password file of the main library.

From the scp password file in / home/oracle/dbs of the main library to / home/oracle/dbs in the standby library

You may need to change the sid of the password file name

I restarted the standby library directly and checked it again.

SQL > select * from gv$pwfile_users

INST_ID USERNAME SYSDB SYSOP SYSAS

1 SYS TRUE TRUE FALSE

The password file of the slave library is normal, and there are no such errors in the main library.

This is the end of the content of "how to solve DG error Error 1031 received logging on to the standby". Thank you for your reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.