Error 12537 Received Logging On To The Standby
Contents |
SQL TuningSecurityOracle UNIXOracle LinuxMonitoringRemote supportRemote plansRemote servicesApplication Server ApplicationsOracle FormsOracle PortalApp UpgradesSQL ServerOracle ConceptsSoftware SupportRemote Support Development Implementation Consulting error 12154 received logging on to the standby StaffConsulting PricesHelp Wanted! Oracle PostersOracle Books Oracle Scripts Ion error 12154 received logging on to the standby 11g Excel-DB Don Burleson Blog
Error 12154 Received Logging On To The Standby Rac
Diagnosing the ORA-12537: TNS: connection closed error Oracle Database Tips by Burleson Consulting Question: I'm trying to connect to Oracle and
Error 1031 Received Logging On To The Standby
I get the ORA-12537: TNS: connection closed error. How do I fix an ORA-12537?Answer: The ORA-12537 is an informational error, and the "real" error is the secondary error message. ORA-12537 TNS:connection closed Cause: Normal "end of file" condition has been reached; partner has disconnected. Action: None needed; this is error 1031 received logging on to the standby ora-01031 insufficient privileges an information message. The ORA-12537 error sometimes relates configuration issues in the sqlnet.ora, protocol.ora and listener.ora files. Verify that you service names match between your listener and remote client connect strings.This ORA-12537 can also happen if your firewall has disconnected idle connections.Also, the ORA-12537 sometimes happens in these cases: 1. You have a path name that is too long for the Oracle TNS client. See MOSC note:263489.1. Since the iORA-12537 ssue is caused by a large connection string there are several workarounds for the issue. 1. Install the exe in a shorter named directory. 2. Modify the TNS Names entry so that it is shorter. 3. Replace domain names with IP Addresses if that shortens and vice versa. 4. Remove any parameters from the entry that are not needed. 5. Patch the Database Listener to the most recent version. References 2. Bug:1566794: CONNECTIONS FAIL WITH ORA
Materialized View (1) Monitoring (2) segment (3) shrink space (3) session (3) Table (1) tablespace (2) Backup & Recovery (14) Datapump expdp/impdp
Error 1033 Received Logging On To The Standby
(4) exp/imp (2) Log Miner (1) Rman Backup & Recovery (7) Block error 12514 received logging on to the standby corruption recovery (1) duplicate for standby (1) Data Guard (13) Active Data Guard (2) Enterprise Manager (2) error 12514 received logging on to the standby oracle File System (11) ACFS (2) ASM (7) HA (8) Clusterware (2) Grid Infrastructure (6) RAC (1) Installation, upgrading and Patching (8) Clone (1) Logical Standby (1) Networking (1) SqlNet http://www.dba-oracle.com/t_ora_12537_tns_error.htm (1) OS-related (18) AIX (12) RHEL (2) Performance (19) binds (1) cursor (1) explain plan (2) Parsing (2) PGA (1) pl/sql profiler (1) SGA (1) Sql tracing (2) Sql Tuning Advisor (2) Storage (4) Async IO (2) PL/SQL (7) Security (3) user (3) Uncategorized (10) Utility (7) oradebug (2) rlwrap (1) Sqlplus (4) « Encountering ORA-01153: an https://chenguangblog.wordpress.com/2011/02/20/data-guard-scripts/ incompatible media recovery is active When Starting Up PhycialStandby| Guarantee data currency using Real-TimeApply » Data Guard Scripts Index Starting up physical standby Shutting down physical standby Opening Real-Time Apply on physical standby Check database status Check Fast-Start Failover status Check Redo Apply and Redo Transport status on physical standby Show received archived logs on physical standby Show applied archived logs on physical standby Show archived log destination status +++ Check transport Lag +++ Show message Is physical standby currently performing managed recovery? Check level of synchronization Starting up physical standby (no Active Data Guard) 1) Start physical standby database to mount state sys@phystdby> startup mount; 2) Start Media Recovery Process on physical standby: sys@phystdby> alter database recover managed standby database using current logfile disconnect; 3) Ensure the LOG_ARCHIVE_DEST_n assigned to physical standby on primary database is enabled sys@primary>select value from v$parameter where name = 'log_archive_dest_state_2'; VALUE ---------------------------------------------------------------------------------------------------- ENABLE shutting down physical standby 1) Defer the physical standby destination on primary database (e.g. LOG_ARCHIVE_DEST_2 is assigned to physical standby) sys@primary> alter
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 Database, http://www.orafaq.com/forum/t/152662/ not sure why primary database not able to connect to standby database PING[ARCi]: Heartbeat failed to connect to standby 'orclstand1'. Error is 12154. Sat Nov 28 22:15:06 2009 Error 12154 received logging on 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 able received logging 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 can not received logging on 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 >28-NOV-2009 22:29:24 * (CONNECT_DATA=(SID=orc