Skip to main content
ExLibris
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    ORA-12514: TNS:listener does not currently know of service requested in connect

    • Article Type: General
    • Product: Aleph
    • Product Version: 18.01

    Problem Symptoms

    • running hot and cold backups on our Aleph live system (Aleph backup utility v 2.6) failed

     

    Error log:


    [root@xxxxxx-vm logs]# more ora_hot_a2_Detail_091008_1210.log

    /exlibris/backup/logs/ora_hot_a2_Detail_091008_1210.log

     

    exec_backup_main 08-10-2009 12:10:15

     

    BKP_TYPE = ora_hot

    SLOT = a2

     

    BKP_USER = aleph
     

    BKP_DB = xxxxxx-vm.aleph18
     

    BKP_UDIR = /exlibris/aleph/a18_1
     

    BKP_DIR = /var/ssu/backup/

    RM_USER = aleph_dba

     

    ORACLE_HOME = /exlibris/app/oracle/product/102

    ORACLE_SID = aleph18

    HOST = louisville-vm

    OS = Linux

    su = /bin/su -f

     

    0

    >>>rman_findinc0 ... RMAN_BSN=0 RMAN_IN0=0

    >>> 08-10-2009 12:10:15

     

    Recovery Manager: Release 10.2.0.3.0 - Production on Thu Oct 8 12:10:15 2009

     

    Copyright (c) 1982, 2005, Oracle. All rights reserved.

     

    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================

    RMAN-00554: initialization of internal recovery manager package failed

    RMAN-04005: error from target database:

    ORA-12514: TNS:listener does not currently know of service requested in connect

    descriptor

    >>>rman_set_config ... bstatus=1

    >>> 08-10-2009 12:10:16

     

    >>>Error in rman_set_config ... bstatus=1

    Cause

    The hot and cold backups of the Oracle database aleph 18 on yourserver-vm failed because the Recovery Manager (RMAN) could not connect to the database.
     

    RMAN failed to connect because the parameter service_name

    Definition of the Oracle Net Service Name yourserver-vm.aleph18

    in the file $ORACLE_HOME/network/admin/tnsnames.ora did not match the initialization parameter service_names of the database.

    Resolution

    Change initialization parameter service_names of the database aleph18:

     

    1. Log on to the server yourserver-vm as UNIX user aleph.

    2. Connect to the database aleph18 with privilege sysdba:

     

    $ sqlplus aleph_dba/aleph_dba as sysdba

     

    OR

    su - root

    su - oracle

    oracle@libcat(alepht)~$sqlplus '/as sysdba'

     

    3. Update with SQL:

    alter system
    set service_names = 'aleph18.yourserver-vm.ac.uk'
    scope=both;

    Additional Information

     

    File $ORACLE_HOME/network/admin/tnsnames.ora

    yourserver-vm.aleph18=(description=

    [...]

    (connect_data=(service_name=aleph18.yourserver-vm.ac.uk)(server=DEDICATED)))

     

    Init parameter:

    show parameter service_names

     

    NAME TYPE VALUE

    ------------------------------------ ----------- ------------------------------

    service_names string aleph18.yourserver.ac.uk


    • Article last edited: 08-Oct-2013