Error 12154 Received Logging On To The Standby

Error 12154 Received Logging On To The Standby – Error 12170 received logging on to the standby ping [arc1]: Problem is that primary db cannot log on to the standby db. Service name in the tnsnames.ora and. It shows most common and possible causes along with solutions to get rid of this problem.

Error 12154 received logging on to the standby. Heartbeat failed to connect to standby 'gscc'. Error 12154 connecting to pgs_1,pgs_2 for fetching gap sequence. You can also catch regular content via connor's blog and chris's blog.or if video is more your thing, check out connor's.

Error 12154 Received Logging On To The Standby

7 comments 30,207 views hi, we have standby for our production database, since yesterday, we are getting below error in alert log file of production and the redo's. The main issue to cause this to happen is because the multiple service names in the fal_server parameter on the standby database were not configured. Error 12154 received logging on to the standby whenever primary instance startup with srvctl (doc id 1943178.1) last updated on november 08, 2022 applies to:

Tns:could not resolve the connect identifier specified ping[arc7]: Hi all, we have configured oracle data gaurd between our production (npp) & standby (npp_dr). If the fal_server is missing, oracle will grab that information from log_archive_dest_n.

This means that log_archive_dest_2 needs to be configured also on. The configuration is complete however, the production is unable. Alert log on primary node shows below error:

I am able to tnsping and conect from sqlplus sys@dr. Connor and chris don’t just spend all day on asktom. Centos 6.4 oracle 11gr2 oracle_sid=primdb1 sql>.

ORA12154 TNS could not resolve the connect identifier specified