Error 12547 Received Logging On To The Standby
Contents |
connect to standby [message #348121] Mon, 15 September 2008 13:06 Alps Messages: 28Registered: November 2006 Location: Toronto Junior Member Hi guys, My alert for primary is showing me error 12154 received logging on to the standby these errors. Errors in file /var/ORADUMP/diag/rdbms/test_devzon/TEST ORA-16191: Primary log shipping client not
Error 12154 Received Logging On To The Standby 11g
logged on standby PING[ARC1]: Heartbeat failed to connect to standby 'STANDBY_TEST' Mon Sep 15 14:07:59 2008 Error 1017 received error 12154 received logging on to the standby rac logging on to the standby ------------------------------------------------------------ Check that the primary and standby are using a password file and remote_login_passwordfile is set to SHARED or EXCLUSIVE, and that the SYS password error 1031 received logging on to the standby is same in the password files. returning error ORA-16191 ------------------------------------------------------------ Errors in file /var/ORADUMP/diag/rdbms/testsxu_devzon/TEST/trace/TEST_arc1_10396.trc: ORA-16191: Primary log shipping client not logged on standby PING[ARC1]: Heartbeat failed to connect to standby 'STANDBY_TEST'. Error is 16191. But I can connect from standby and primary as follows. Connected to: Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - 64bit Production With the Partitioning, Oracle Label Security,
Error 1031 Received Logging On To The Standby Ora-01031 Insufficient Privileges
OLAP, Data Mining, Oracle Database Vault and Real Application Testing options SQL> connect sys/XXXXX@PRIMARY_TEST AS SYSDBA Connected. SQL> connect sys/XXXXX@STANDBY_TEST AS SYSDBA Connected. SQL> Report message to a moderator Re: Heartbeat failed to connect to standby [message #348129 is a reply to message #348121] Mon, 15 September 2008 13:57 BlackSwan Messages: 24930Registered: January 2009 Location: SoCal Senior Member http://www.orafaq.com/forum/t/88153/0/ Please read & follow posting guidelines as stated in URL above When did this last work? What changed? >SQL> connect sys/XXXXX@PRIMARY_TEST AS SYSDBA >Connected. >SQL> connect sys/XXXXX@STANDBY_TEST AS SYSDBA >Connected. >SQL> do the same from BOTH systems. Does listener.log file on standby show failed login attempt from Primary? Provide CUT & PASTE proof. Report message to a moderator Re: Heartbeat failed to connect to standby [message #348150 is a reply to message #348129] Mon, 15 September 2008 15:46 Alps Messages: 28Registered: November 2006 Location: Toronto Junior Member When did this last work? I am implementing on 11g What changed? Nothing changed yet still in process of getting archivelogs from primary Standby listener log: 15-SEP-2008 16:41:33 * (CONNECT_DATA=
by the reviewers are theirs alone and may not reflect my opinion whether implied or not. None of the advice is warranted to be free of errors and ommision. Please use at your own risk and error 1033 received logging on to the standby after thorough testing in your environment. Pages Home Collection of Some of My Very Popular error 12514 received logging on to the standby Published Web Articles Friday, December 18, 2009 Resolving Gaps in Data Guard Apply Using Incremental RMAN BAckup Recently, we had a glitch
Error 12514 Received Logging On To The Standby Oracle
on a Data Guard (physical standby database) on infrastructure. This is not a critical database; so the monitoring was relatively lax. And that being done by an outsourcer does not help it either. In any case, the laxness http://www.orafaq.com/forum/t/124922/ resulted in a failure remaining undetected for quite some time and it was eventually discovered only when the customer complained. This standby database is usually opened for read only access from time to time.This time, however, the customer saw that the data was significantly out of sync with primary and raised a red flag. Unfortunately, at this time it had become a rather political issue.Since the DBA in charge couldn't resolve the problem, I was called http://arup.blogspot.com/2009/12/resolving-gaps-in-data-guard-apply.html in. In this post, I will describe the issue and how it was resolved. In summary, there are two parts of the problem:(1) What happened(2) How to fix itWhat HappenedLet's look at the first question - what caused the standby to lag behind. First, I looked for the current SCN numbers of the primary and standby databases. On the primary:SQL> select current_scn from v$database;CURRENT_SCN----------- 1447102On the standby:SQL> select current_scn from v$database;CURRENT_SCN----------- 1301571Clearly there is a difference. But this by itself does not indicate a problem; since the standby is expected to lag behind the primary (this is an asynchronous non-real time apply setup). The real question is how much it is lagging in the terms of wall clock. To know that I used the scn_to_timestamp function to translate the SCN to a timestamp:SQL> select scn_to_timestamp(1447102) from dual;SCN_TO_TIMESTAMP(1447102)-------------------------------18-DEC-09 08.54.28.000000000 AMI ran the same query to know the timestamp associated with the SCN of the standby database as well (note, I ran it on the primary database, though; since it will fail in the standby in a mounted mode):SQL> select scn_to_timestamp(1301571) from dual;SCN_TO_TIMESTAMP(1301571)-------------------------------15-DEC-09 07.19.27.000000000 PMThis shows that the standby is two and half days lagging! The data at this point is not just stale; it must be rotten.The next question is why it would be lagging so far back in the past. This is a 10.2 databa
entry for my Data Guard series. First things first, below are the specs of my test environment: - HP G60-445DX (w/ http://im-a-dba.blogspot.com/2009/09/settting-up-oracle-dataguard.html 4GB RAM) - Ubuntu 9.04 64-bit (instead of Vista Home premium to maximize https://davidalejomarcos.wordpress.com/2011/01/18/removing-fatal-ni-connect-error-xxxx-from-your-alert-log/ the RAM) - VMWare 2.0 For the Oracle Data Guard Configuration I created 2 Virtual Machines, each with the ff. specs: RAM: 1GB (have tried this with 512 MB before, but very slow) OS : Oracle Enterprise Linux 4 (can be downloaded from e-delivery.oracle.com) DB: Oracle 10g R2 (10.2.0.4) received logging HD: 30 GB (not pre-allocated) I assumed that you guys already have background in database administration, so I will be skipping the fundamentals (e.g DB installation, patching etc.) I named my Primary database as "prim10g" and its host as "oel41", while my Physical Standby database as "stby10g" and its host as "oel42". Setting Up Oracle Data Guard (Physical Standby Database) received logging on 1. Turn on archiving on the Primary database [root@oel41 ~]# su - oracle [oracle@oel41 ~]$ export ORACLE_SID=prim10g [oracle@oel41 ~]$ sqlplus / as sysdba SQL*Plus: Release 10.2.0.4.0 - Production on Tue Sep 1 14:20:03 2009 Copyright (c) 1982, 2007, Oracle. All Rights Reserved. Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production With the Partitioning, OLAP, Data Mining and Real Application Testing options SQL> alter system set log_archive_dest='/u02/oradata/archive/' scope=both; System altered. SQL> shutdown immediate Database closed. Database dismounted. ORACLE instance shut down. SQL> SQL> startup mount ORACLE instance started. Total System Global Area 285212672 bytes Fixed Size 1267044 bytes Variable Size 104860316 bytes Database Buffers 171966464 bytes Redo Buffers 7118848 bytes Database mounted. SQL> alter database archivelog; Database altered. SQL> alter database open 2 / Database altered. 2. Gather necessary files to create a physical standby database and perform an RMAN backup 2.1 Create a staging directory on Primary and Standby host [oracle@oel41 ~]$ mkdir -p /u02/stage [oracle@oel41 ~]$ 2.2 Create a copy of the init.ora (pfile) SQL> create pfile='/u02/stage/initprim10g.ora' from spfile; 2.3 Backup the database including archivelogs and create a
have a script to monitor the alert.log file for any ORA-xxxx errors. With 11g we found out many entries in regards of: Fatal NI connect error The problem: alert.log file has many entries for Fatal NI connect error. Examples: *********************************************************************** Fatal NI connect error 12514, connecting to: (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=xxxx)(PORT=nnn))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=sss)(CID=(PROGRAM=oracle)(HOST=xxx)(USER=oracle)))) VERSION INFORMATION: TNS for Linux: Version 11.2.0.2.0 - Production TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.2.0 - Production Time: 17-JAN-2011 10:20:45 Tracing not turned on. Tns error struct: ns main err code: 12564 TNS-12564: TNS:connection refused ns secondary err code: 0 nt main err code: 0 nt secondary err code: 0 nt OS err code: 0 Error 12514 received logging on to the standby Mon Jan 17 10:21:45 2011 *********************************************************************** or *********************************************************************** Fatal NI connect error 12170. VERSION INFORMATION: TNS for Linux: Version 11.2.0.2.0 - Production Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.2.0 - Production TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.2.0 - Production Time: 18-JAN-2011 15:13:08 Tracing not turned on. Tns error struct: ns main err code: 12535 TNS-12535: TNS:operation timed out ns secondary err code: 12560 nt main err code: 505 TNS-00505: Operation timed out nt secondary err code: 110 nt OS err code: 0 Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=xx.xx.x.xx)(PORT=nnnn)) Tue Jan 18 15:40:20 2011 The solution: We will have an entry on the alert.log file every time a client connection of any kind fails to complete or is aborted. One way to minimize the impact is by using the parameter SQLNET.INBOUND_CONNECT_TIMEOUT (default to 60 seconds on 10gR2 and 11g) but, sometimes, this value is not adequate. Oracle also mentions the occurrence of this error if you use DB Console or Enterprise Manager to monitor your databases and the emagent will try to connect to the target database repeatedly and, statistically, some will fail (frequency will depend on h