Fatal Ni Connect Error 12514 Standby
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 t
connecting to: (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=hostname)(PORT=port))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=DBSID_DGB)(CID=(PROGRAM=oracle)(HOST=hostname)(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: 01-JUN-2015 11:12:47 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 Solution: When checking the service in DR using lsnrctl status, you are not able to see the https://davidalejomarcos.wordpress.com/2011/01/18/removing-fatal-ni-connect-error-xxxx-from-your-alert-log/ service "DBSID_DGB". sologgedin to the Standby db and modify the parameter, SQL> alter system set "__dg_broker_service_names" = 'DBSID_DGB' scope=both; System altered. ++Check the values. SELECT a.ksppinm "Parameter",b.ksppstvl "Session Value",c.ksppstvl "Instance Value" FROM x$ksppi a, x$ksppcv b, x$ksppsv c WHERE a.indx = b.indx AND a.indx = c.indx AND a.ksppinm LIKE '/__dg%' escape '/' / ------------------ __dg_broker_service_names DBSID_DGB DBSID_DGB ++Then check the lsnrctl status,You can see the services("DBSID_DGB"). $lsnrctl status LSNRCTL http://oracletechdba.blogspot.com/2015/06/primary-database-alertlog-giving-below.html for Linux: Version 11.2.0.2.0 - Production on 01-JUN-2015 11:11:26 Copyright (c) 1991, 2010, Oracle. All rights reserved. Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC))) STATUS of the LISTENER ------------------------ Alias LISTENER Version TNSLSNR for Linux: Version 11.2.0.2.0 - Production Start Date 01-JUN-2015 10:29:23 Uptime 0 days 0 hr. 42 min. 2 sec Trace Level off Security ON: Local OS Authentication SNMP OFF Listener Parameter File /u01/app/11.2.0/grid/network/admin/listener.ora Listener Log File /u01/app/diag/tnslsnr/za-fdbs-dr-03/listener/alert/log.xml Listening Endpoints Summary... (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521))) (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=hostname)(PORT=prot))) Services Summary... Service "DBSID" has 1 instance(s). Instance "DBSID", status READY, has 1 handler(s) for this service... Service "DBSID_DGB" has 1 instance(s). Instance "DBSID", status READY, has 1 handler(s) for this service... ++Now in Primary alert log we are not getting any more warnings. Posted by Karl Marx at 02:24 Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels:DATABASE,PERFORMANCE Database No comments: Post a Commen
Oracle 11gR1 RAC to 11gR2 Applying PSU 11.2.0.3.5 to Grid Infrastructure http://askdba.org/weblog/oracle11g/dataguard/dataguard-and-dg-broker-setup-issues/ and DB Home ASM Dataguard Install Transportable Tablespace Example http://phxcharger.blogspot.com/2014/03/rac-standby-database-tns-12564.html Oracle12c Performance Grid MySQL Reset MySQL Root Password Unix Linux AIX HP-UX Solaris Netapp Reference Resource Center ADRCI Starting with Oracle Goldengate Scripts Useful SQL for DBA's Useful Metalink Articles About Us Contact Dataguard fatal ni and DG Broker Setup Issues This article comprises of various issues encountered by us while setting up Dataguard and DG Broker on 11gR2 RAC setup. 1)Connection to RMAN Auxiliary database gives ORA-1031 rman target [emailprotected]_dgmgrl auxiliary [emailprotected]_dgmgrl Recovery Manager: Release 11.2.0.3.0 - Production fatal ni connect on Wed Feb 15 10:52:20 2012 Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved. connected to target database: TINTIN (DBID=2175947715) RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-00554: initialization of internal recovery manager package failed RMAN-04006: error from auxiliary database: ORA-01031: insufficient privileges To resolve this ensure that you are able to connect to database using sqlplus sqlplus [emailprotected]_dgmgrl as sysdba If this gives error then a)Ensure password file exists for auxiliary database and remote_login_passwordfile=exclusive b)In case of RAC ensure that tnsnames.ora entry is correct. It should look like below snowy_dgmgrl = (DESCRIPTION_LIST = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = oradbdev02.eglbp.corp.yahoo.com)(PORT = 1521)) (ADDRESS = (PROTOCOL = TCP)(HOST = oradbdev01.eglbp.corp.yahoo.com)(PORT = 1521)) (CONNECT_DATA =(SERVER = DEDICATED) (SERVICE_NAME = snowy_DG
ora-prod2-scan Standby - Single instance (11..2.0.4) Node - dbhost1d Using GI and ASM Error in Standby Alert log - Fatal NI connect error 12521, connecting to: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=dbhost1-vip)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=psprod_DGB)(INSTANCE_NAME=psprod2)(SERVER=DEDICATED)(CID=(PROGRAM=oracle)(HOST=dbhost1d.com)(USER=oracle)))) VERSION INFORMATION: TNS for Linux: Version 11.2.0.4.0 - Production TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production Time: 24-MAR-2014 12:17:27 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 in Standby drcpsprod.log - Failed to connect to remote database psprod. Error is ORA-12521 Error on Node 2 drcpsprod.log - Data Guard Broker Status Summary: Type Name Severity Status Configuration psprod_linux Warning ORA-16607 Primary Database psprod Success ORA-00000 Physical Standby Database psproddg Error ORA-16664 The error in Standby alert log show that the standby database is trying to connect to second instance (psprod2) of the 2 node RAC database using the vip of node 1. Since psprod2 instance is running on the node 2 which is dbhost2-vip there is an error in the alert log saying it connection refused. Solution - We have to change the DGConnectIdentifier using Data Guard broker to point to SCAN name instead of VIP name of the nodes. DGMGRL> SHOW DATABASE VERBOSE psprod Database - psprod Enterprise Manager Name: psprod_linux Role: PRIMARY Intended State: TRANSPORT-ON Instance(s): psprod1 psprod2 Properties: DGConnectIdentifier = '(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=dbhost1-vip)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=psprod)(SERVER=DEDICATED)))' ObserverConnectIdentifier = '' LogXptMode = 'ASYNC' DelayMins = '0' Binding = 'optional' MaxFailure = '0' MaxConnections = '1' ReopenSecs = '300' NetTimeout = '30' RedoCompression = 'DISABLE' LogShipping = 'ON' PreferredApplyInstance = '' ApplyInstanceTimeout = '0' App