Error 12154 Received Logging On To The Standby
Contents |
Web and Mobile SQL*Plus Data Warehousing Installation Networking Backup Recovery Security Tuning PLSQL Oracle Applications Scripts Administration ORA-HOWTO error 12154 received logging on to the standby oracle Web and Mobile SQL*Plus Data Warehousing Installation Networking Backup Recovery Security
Error 12154 Received Logging On To The Standby Rac
Tuning PLSQL Oracle Applications Papers Administration ORA-HOWTO Web and Mobile SQL*Plus Data Warehousing Installation Networking error 12154 creating remote archivelog file Backup Recovery Security Tuning PLSQL Oracle Applications Forum All threads Best last month Links Oracle official Oracle Technical Info Tools (free) Tools (commercial) Oracle FAQ Other
Error 12154 Received Logging On To The Standby 11g
DBA-sites Oracle development Not Oracle specific Oracle Blogs Imho Fqa Pirats | Start a new thread | All threads | Best last month | No question at this time DBA Top 10 1 M. Cadot 37400 2 F. Diaz 33800 3 J. Schnackenberg 18400 4 B. Vroman 16350 5 A. Kavsek 15950 6 ora 12154 tns could not resolve the connect identifier specified P. Wisse 14750 7 T. Boles 14400 8 M. Hidayathullah ... 11500 9 A. Hudspith 8600 10 A. Khan 4400 About Advertise here Download PLATOThe free tool for auditing and tuning your databaseVersion 55 now available Sep 02, 2016 The DBA-Village forum as RSS feed Site StatisticsEver registered users47779Total active users2112Act. users last 24h3Act. users last hour2Registered user hits last week561Registered user hits last month6457 Go up Heartbeat failed to connect to standby Next thread: Steps to fasten import Prev thread: "Oracle Clusterware Configuration Assistant" failed Message Score Author Date Dear Masters, i m getting following error very ...... javed akhtar May 30, 2012, 10:56 From doc.... If the Primary ARCn-Process is n...... Tarun Biswas May 30, 2012, 12:24 Check the network connection. On Dr site try to...... Raj thakur May 30, 2012, 14:25 Follow up by mail Click here Subject: Heartbeat failed to connect to standby Author: javed akhtar, India Date: May 30, 201
not able to connect to standby [message #433009] Sat, 28 November 2009 13:16 ankush_chawla Messages: 136Registered: November 2006 Senior Member hi we are receving following error in the Alert log of the primary
Ping Arc0 Heartbeat Failed To Connect To Standby
Database, not sure why primary database not able to connect to standby database PING[ARCi]:
Error 1031 Received Logging On To The Standby
Heartbeat failed to connect to standby 'orclstand1'. Error is 12154. Sat Nov 28 22:15:06 2009 Error 12154 received logging on error 1031 received logging on to the standby ora-01031 insufficient privileges to the standby Sat Nov 28 22:15:06 2009 Errors in file \oracle\product\10.2.0\admin\orcl\bdump\orcl_arci_424.trc: ORA-12154: TNS:could not resolve the connect identifier specified 1. TNSPING for the standby database server gives the positive result 2. We are http://dba-village.com/village/dvp_forum.OpenThread?ThreadIdA=51881 able to log on to the standby database from primary database server 3. Log files are shipped to the standby database server Please help Regards Report message to a moderator Re: primary database not able to connect to standby [message #433010 is a reply to message #433009] Sat, 28 November 2009 13:23 BlackSwan Messages: 24930Registered: January 2009 Location: SoCal Senior Member Ora-12154 = "I http://www.orafaq.com/forum/t/152662/ can not find the entry in the TNSNAMES.ORA file that I am using (regardless of the one YOU THINK I am using)!" >1. TNSPING for the standby database server gives the positive result Above only means you can get to listener, but in this case you are not even getting to the listener. listener records into listener.log every connection request along with the appropriate status code STATUS=0 means success. [Updated on: Sat, 28 November 2009 13:26]Report message to a moderator Re: primary database not able to connect to standby [message #433011 is a reply to message #433010] Sat, 28 November 2009 13:43 ankush_chawla Messages: 136Registered: November 2006 Senior Member thanks for the response Not understanding where the issue is exactly Listener is up and running on both the servers. Listener log 28-NOV-2009 22:29:24 * (CONNECT_DATA=(SID=orcl)(CID=(PROGRAM=\oracle\product\10.2.0\db_2\bin\emagent.exe)(HOST=EQ-W00300109765)(USER=OraUser))) * (ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=2920)) * establish * orcl * 12518 TNS-12518: TNS:listener could not hand off client connection TNS-12560: TNS:protocol adapter error TNS-00530: Protocol adapter error Report message to a moderator Re: primary database not able to connect to standby [message #433012 is a reply to message #433011] Sat, 28 November 2009 13:53 BlackSwan Messages: 24930Registered: January 2009 Location: SoCal Senior Member
any loss suffered as a result of following any of this blog posts.. Happy Learning... Tuesday, November 5, 2013 ORA-12154: TNS: could not resolve the connect identifier specified ########################## ## Error ########################## ORA-12154: TNS: could not resolve the connect identifier specified ### Full Error Mon Nov 04 21:01:00 2013 Error 12154 received logging on to the http://stepintooracledba.blogspot.com/2013/11/ora-12154-tns-could-not-resolve-connect.html standby ########################## # Error Occurred ########################## Error occured while Primary database is trying to connect to a standby database for https://dbatales.wordpress.com/2012/03/28/dataguard-setting-up-physical-standby-part1/ transfering archive logs in 11.2.0.3.0 version ########################## ## Command Executed ########################## Primary trying to transfer Archive logs to Standby ########################## ## Issue Description / Troubleshooting ########################## ### 11.2.0.3.0 ######################################### # 1) Check Whether archive destination is showing any errors ######################################### set lines 200 col dest_name for a20 col destination for a50 col error for a15 col db_unique_name for a15 col name for a100 select dest_id,dest_name,target,name_space,destination,status,error,db_unique_name from v$archive_dest where destination is not null; DEST_ID DEST_NAME received logging TARGET NAME_SP DESTINATION STATUS ERROR DB_UNIQUE_NAME ---------- -------------------- ------- ------- -------------------------------------------------- --------- --------------- --------------- 1 LOG_ARCHIVE_DEST_1 PRIMARY SYSTEM USE_DB_RECOVERY_FILE_DEST VALID NONE 2 LOG_ARCHIVE_DEST_2 STANDBY SYSTEM oralin_stdby received logging on ERROR ORA-12154: oralin_stdby TNS:could not resolve the connect identifier specified ######################################### # 2) TNS Names Used to Connect ###################################
Management Best Practices Useful LinksOracle Support (ex Metalink) OTN Documentation OTN Forum Ask Tom Dataguard - Setting up Physical Standbypart1 Posted: 20120328 in Oracle Database 0 Environment details: Oracle 10gR2 running on RHEL5 64bit. Dataguard final config: Physical standby, Maximum Performance, no broker. Primary DB A1AR running on server lnx-primary. Standby DB A2AR running on server lnx-standby. 1. Make sure that your primary DB is running in FORCE LOGGING mode. Otherwise, on the primary DB issue: ALTER DATABASE FORCE LOGGING; 2. Create a Password File on both systems (use the same sys password for both DBs), alternatively you can simply copy the primary password file to the standby server and rename it. 3. Clone the DB manually or using RMAN. 3a. Manual clone: Shutdown the primary DB. On the standby DB server, create the four dump dirs in the location you will speficy in the standby DB init file mkdir bdump
mkdir udump
mkdir cdump
mkdir adump Copy the redo logs and datafiles to the standby DB server using the locations you will speficy in the standby DB init file. No need to copy control file or init file at this stage, just follow the steps below. 3b. If you prefer to use RMAN then check my post "Dataguard - Setting up Physical Standby part2" 4. Make sure that your primary is running in ARCHIVELOG mode. Otherwise: SQL> SHUTDOWN IMMEDIATE;
SQL> STARTUP MOUNT;
SQL> ALTER DATABASE ARCHIVELOG;
SQL> ALTER DATABASE OPEN; 5. Create the control file for the standby database. If the DB is not mounted or opened. SQL> STARTUP MOUNT; Then, create the control file for the standby database, and open the primary database to user access, as shown in the following example:
SQL> ALTER DATABASE CREATE STANDBY CONTROLFILE AS '/tmp/A2AR.ctl';
SQL> ALTER DATABASE OPEN; 6. Set init parameters. First: SQL> CREATE PFILE FROM SPFILE; 6a. Then modify the pfile so that the primary initialization parameters are: [...]
*.db_domain='lnx-primary'
*.db_name='A1AR'
*.DB_UNIQUE_NAME='A1AR'
*.LOG_ARCHIVE_CONFIG='DG_CONFIG=(A1AR,A2AR)'
*.LOG_ARCHIVE_DEST_1=
'LOCATION=/u11/oracle/oradata/arch_A1AR/
VALID_FOR=(ALL_LOGFILES,ALL_ROLES)
DB_UNIQUE_NAME=A1AR'
*.LOG_ARCHIVE_DEST_2=
'SERVICE=A2AR LGWR ASYNC
VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
DB_UNIQUE_NAME=A2AR'
*.LOG_ARCHIVE_DEST_STATE_1=ENABLE
*.LOG_ARCHIVE_DEST_STATE_2=ENABLE