Eliminate Fatal Ni Connection Error 12514 With Simple Oracle Connection

If you are facing Ni Connect Fatal Error 12514 when connecting to Oracle, this user guide can help you.

Don’t suffer from crashes and errors. Fix them with ASR Pro.

  • Step 1: Download and install ASR Pro
  • Step 2: Launch the application and click on the "Restore" button
  • Step 3: Select the files or folders you want to restore and click on the "Restore" button
  • Click here to Download this software and fix your computer.

    If you see this specific error below in the warning report for the new primary server during failover, that’s fine. It’s huge ephemeral.

      ***************************************** * * *********************** NI 12514 Fatal Attachment Error, connecting to:  (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP) (Host = OL6DB01) (Port = 1521))) (CONNECT_DATA = (SERVICE_NAME = PROD1) (CID = (PROGRAM = oracle) (HOST = ol7db02) (USER = Oracle)))) VERSION INFORMATION:         For Linux tns: Version 12.1.0.2.0 - production        NT TCP / IP Protocol Adapter with Linux: Version 12.1.0.2.0 - Production   Time: 15:08:40 October 30, 2020 Trace not activated.   TNS error structure:     major error code ns: 12564 TNS-12564: TNS: Connection refused     secondary error code ns: 0     major error code: 0     secondary error code nt: 0     Operating system error code nt: 0  

    fatal ni connect error 12514 connecting to oracle

    What is happening is that during the migration, the old primary database is likely to be shut down and started as a new standby instance. Services previously listed in the listener are removed when Oracle is started in modern standby and restarted It is registered daily. During this time, you will likely see errors and they will disappear once the auditor’s services are recorded altogether.

    If you see a glitch in the new primary server’s alert across the switch, that’s okay. It’s very fleeting.

      ***************************************** * * *********************** Fatal hit error NI 12514 connecting to:  (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP) (Host = OL6DB01) (Port = 1521))) (CONNECT_DATA = (SERVICE_NAME = PROD1) (CID = (PROGRAM = oracle) (HOST = ol7db02) (USER = Oracle)))) VERSION INFORMATION:         TNS for Linux support: version 12.1.0.2.0 - Production        NT TCP / IP Protocol Adapter for Linux: Version 12.1.0.2.0 - Production   Time: 15:08:40 October 30, 2020 Trace not activated.   TNS error structure:     main code ns: wrong 12564 TNS-12564: TNS: Connection refused     secondary code ns: admit error 0     intermediate code nt: error 0     nt secondary code: make errors 0     Operating system code nt: Error 0  

    What happened during the switch, the old primary side must be disconnected and the new backupMy copy. Services previously approved on the listener are randomly dropped and re-registered daily when the pending Oracle update is run. During this time, you will likely see errors, and they may disappear once the registered services are normally in the listener.

    Problem – NI

    fatal connection error 12514, connecting to:
    (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP) (HOST = abc.xyz.com) (PORT = 9501)) (CONNECT_DATA = (SERVICE_NAME = stby) (CID = (PROGRAM = oracle) (HOST = abc234.xyz. VERSION com) (user = oracle))))

    INFORMATION:
    TNS for Linux: Version 12.1.0.2.0 – Production
    NT TCP / IP Adapter Method for Linux: Version 12.1.0.2.0 – Production
    Time: 18.07.2018 11:59:41
    The trail was not tracked.
    Tns error structure:
    Dominant code: err 12564

    TNS-12564: TNS: Connection refused
    Other code: err 0
    Small code: error 0
    secondary signal nt: error 0
    NT OS Code: Errors 0

    Acceptance –

    The problem began to look for a test fail-safe.
    During the switch, DGMGRL did not make a career, so on the switch had to do a check in SQL
    Crash recovery was successful – its backupthe database has become primary (the old one is mostly disabled – intentionally)
    Errors are confirmed in the information log of the new primary database.

    Sending Archive Log Stopped
    Checked listener and tns filenames – no problems found.

    The restored standby server, during some process in the standby database, found that this special ARCHIVE_LOG_DEST_2 is in the deffer / null state.

    Once this LOG_ARCHIVE_DEST_2 has been defined with The primary_role, the fatal NI 12514 connection error disappears.
    Example –
    ALTER SYSTEM SET LOG_ARCHIVE_DEST_2 = ‘SERVICE = stby NOAFFIRM ASYNC VALID_FOR = (ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME = STBY’;

    Link –

    LOG_ARCHIVE_DEST_2 was previously ignored because this target is only ideal for the main role. When failover occurs and these incidents become the master database.

    https://docs.oracle.com/database/121/SBYDB/create_ps.htm#SBYDB4725
    Archive log from submission of major error to fallback error with ORA-12514 (document id 563801.1)

    fatal ni connect error 12514 connecting to oracle

    Click here to Download this software and fix your computer.

    Elimina L’errore Fatale Di Connessione Ni 12514 Con Una Semplice Connessione Oracle
    Wyeliminuj Krytyczny Błąd Połączenia Ni 12514 Za Pomocą Prostego Połączenia Z Oracle
    Élimine L’erreur Fatale De Connexion Ni 12514 Avec Une Simple Connexion Oracle
    간단한 Oracle 연결로 치명적인 Ni 연결 오류 12514 제거
    Elimine El Error Fatal De Conexión De Ni 12514 Con Una Conexión Simple De Oracle
    Elimineer Fatale Ni-verbindingsfout 12514 Met Een Eenvoudige Oracle-verbinding
    Beseitigen Sie Den Schwerwiegenden Ni-Verbindungsfehler 12514 Mit Einer Einfachen Oracle-Verbindung
    Устранение фатальной ошибки подключения Ni 12514 с помощью простого подключения к Oracle
    Eliminera Dödligt Ni-anslutningsfel 12514 Med Enkel Oracle-anslutning
    Elimine O Erro Fatal De Conexão Ni 12514 Com Uma Conexão Oracle Simples