Job running forever....
Posted: Fri Apr 27, 2007 9:44 am
in one of the run, a job stayed in running mode for ever and eventually it had to be killed.
series of activities happened:
Job sequences triggered through control-m.
first job sequence completed successfully, second sequence started
the first job in the second sequence stayed in running mode forever
the job even didn't start reading the file. the job log produced only :
Starting Job <jobname>.
pxPRSLoadWrkrPvt02..BeforeJob (ExecSH): Executed command: touch <filename> *** No output from command ***
Environment variable settings:
Parallel job initiated
Parallel job default NLS map ISO-8859-1, default locale OFF
Advanced runtime options used: -default_date_format "%yyyy-%mm-%dd"
In this case, how to go about debugging without aborting the job?
PS: job ran successfully when it was killed and ran again.
series of activities happened:
Job sequences triggered through control-m.
first job sequence completed successfully, second sequence started
the first job in the second sequence stayed in running mode forever
the job even didn't start reading the file. the job log produced only :
Starting Job <jobname>.
pxPRSLoadWrkrPvt02..BeforeJob (ExecSH): Executed command: touch <filename> *** No output from command ***
Environment variable settings:
Parallel job initiated
Parallel job default NLS map ISO-8859-1, default locale OFF
Advanced runtime options used: -default_date_format "%yyyy-%mm-%dd"
In this case, how to go about debugging without aborting the job?
PS: job ran successfully when it was killed and ran again.