Aleph: procedure p_arc_01 fails with error ORA-12154 when started from job_list
- Article Type: General
- Product: Aleph
Problem Symptoms:
(1)
When started from the job_list on a customer's server the procedure p_arc_01 fails with the following error messages:
-----------------------------------------------------------------
Now testing Oracle connection with ARC DB
Testing TWO_TASK connection to il-arc01.arc3 :
ORA-12154: TNS:could not resolve the connect identifier specified
ORA-12154: TNS:could not resolve the connect identifier specified
Could not connect to ARC_ADMIN (ARC_ADMIN)
**** Aborting ****
------------------------------------------------------------------
The output above comes from the dependent script p_arc_01_test. This script tries to connect to the Oracle database with the Connect Identifier il-arc01.arc3 and fails.
(2)
However, the procedure p_arc_01 completes successfully when started with the same parameters from the command line.
Cause:
The root cause why the procedure p_arc_01 fails when started from the job_list has not been determined yet.
Resolution:
Workaround:
Add the following line to the file prof_library of the Aleph Library where the procedure p_arc_01 is supposed to run:
unsetenv ARC_TWO_TASK
Add this line at the top of the section "Reporting Center Definitions" in the file prof_library.
The command above ensures that the variable $ARC_TWO_TASK has no value when the script p_arc_01 starts, regardless of any value that the variable may have had before.
- Article last edited: 7/16/2014