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

    exec_backup_main log: "TNS:could not resolve the connect identifier specified"


    • Product: Aleph
    • Product Version: 20, 21, 22, 23
    • Relevant for Installation Type: Dedicated-Direct, Direct, Local, Total Care


    Problem Symptoms: 
    After an Oracle refresh of the Test server from Production, Test server backup logs have: 

    ORA-12154: TNS:could not resolve the connect identifier specified 
    >>>rman_set_config ... bstatus=1 
    >>> 14-05-2015 01:30:08 

    >>>Error in rman_set_config ... bstatus=1 
    exec_backup_main 14-05-2015 01:30:02 

    The environment setup in the backup log shows: 
    BKP_USER = aleph 
    BKP_DB = server X.aleph0 

    The BKP_DB should be Y.aleph0 (Test) rather than X.aleph0 (Production). 

    Rather than bringing just the Oracle data over to Test, the Aleph u-tree, including the alephe, had been brought over. (This includes server specific values, such as the ORA_HOST value in $alephe_root/aleph_start.) 

    Either just the Oracle data needs to be brought over, or the server-specifice alephe values need to be preserved.

    Additional Info



    • Article last edited: 02-Mar-2016