path search failed - Unable to locate dscapiop
Posted: Sat Oct 03, 2009 5:53 am
Hi all,
I am getting following error message(job aborts) for only one job whereas other jobs are running fine.
main_program: orchgeneral: loaded
orchsort: loaded
orchstats: loaded
main_program: PATH search failure:
main_program: Error loading "@dscapiop": Could not load "dscapiop": Could not load module .
System error: No such file or directory.
main_program: Could not locate operator definition, wrapper, or Unix command for "dscapiop"; please check that all needed libraries are preloaded, and check the PATH for the wrappers
main_program: Creation of a step finished with status = FAILED.
Job Job_name aborted.
(Sequence_name) <- Job_name: Job under control finished.
Note:
I have made change to .odbc.ini when the job aborts due to database down. since we are running on cluster environment I had given the virtual ip address of the database(earlier it was pointing to one database out of two)
After that I triggered the sequence, It was running for other parallel jobs when control comes to the particular job it aborts due to above error.
I have no clue to debug the error. since its in production i cannot avoid this job and run other.
Please share your views to debug and rectify the above error
thanks in advance
I am getting following error message(job aborts) for only one job whereas other jobs are running fine.
main_program: orchgeneral: loaded
orchsort: loaded
orchstats: loaded
main_program: PATH search failure:
main_program: Error loading "@dscapiop": Could not load "dscapiop": Could not load module .
System error: No such file or directory.
main_program: Could not locate operator definition, wrapper, or Unix command for "dscapiop"; please check that all needed libraries are preloaded, and check the PATH for the wrappers
main_program: Creation of a step finished with status = FAILED.
Job Job_name aborted.
(Sequence_name) <- Job_name: Job under control finished.
Note:
I have made change to .odbc.ini when the job aborts due to database down. since we are running on cluster environment I had given the virtual ip address of the database(earlier it was pointing to one database out of two)
After that I triggered the sequence, It was running for other parallel jobs when control comes to the particular job it aborts due to above error.
I have no clue to debug the error. since its in production i cannot avoid this job and run other.
Please share your views to debug and rectify the above error
thanks in advance