Tags

11g (5) 12c (6) 18c (3) 19c (4) ASM (1) Critical Patch (11) Data Pump (1) Dataguard (9) Diverse (3) GRID (7) GitLab (2) Linux (8) OEM (2) ORA Errors (13) Oracle (12) RMAN (4)

Wednesday, April 7, 2021

Error 12514 received logging

 

Error 12514 received logging on to the standby

Fatal NI connect error 12514, connecting to

PURPOSE: All documents are provided on this Blog just for educational purposes only.  Please make sure that you run it in your test environment before to move on to production environment. 


Fatal NI connect error 12514, connecting to:

 (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=kardb-sbt.th)(PORT=1521))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=KARDB01)(CID=(PROGRAM=oracle)(HOST=kardb-prd.th)(USER=oracle))))


  VERSION INFORMATION:

        TNS for Linux: Version 12.2.0.1.0 - Production
        Oracle Bequeath NT Protocol Adapter for Linux: Version 12.2.0.1.0 - Production
        TCP/IP NT Protocol Adapter for Linux: Version 12.2.0.1.0 - Production
  Time: 04-MAR-2021 08:48:42
  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
2021-03-04T08:48:42.998683+01:00

Error 12514 received logging on to the standby


Solution:

check the connections as follow:

==> Primary: sqlplus sys@kardb01 as sysdba

tnsping kardb01

NOTE: in my case everything works fine but somehow got the above error - Strange behavior. 

Add the entry in the sqlnet.ora as follow.  

NAMES.DIRECTORY_PATH = (TNSNAMES, EZCONNECT, HOSTNAME)

Everything works fine at this point.

No comments:

Post a Comment

physical standby without duplicate command

physical standby without duplicate command create a physical standby database using RMAN without using duplicate command PURPOSE:   All docu...