Most Base KSH Scripts Report "false" Failures
(Doc ID 2764673.1)
Last updated on APRIL 19, 2023
Applies to:Oracle Retail Merchandising System - Version 16.0.3 and later
Information in this document applies to any platform.
Most of the base KSH batch scripts will report failures even though the current run of the script was successful. This is due to a 'grep' command that searches the batch log for 'Abort' based on the current run PID. However, the same PID can be used many times during the day.
If a completely different batch uses the PID and fails earlier in the day, then the current run of the KSH will fail. Here is an example for a PROD batch log:
Tue Oct 20 10:13:14 Program: saimptlogi: PID=XXXXXXXXX: Started by default user
Tue Oct 20 10:13:14 Program: saimptlogi: PID=XXXXXXXXX: Aborted in init
Tue Oct 20 12:13:18 Program: salesuploadarch: PID=XXXXXXXXX: salesuploadarch.ksh - Started by default user
Tue Oct 20 12:16:01 Program: salesuploadarch: PID=XXXXXXXXX: CORESVC_SALES_UPLOAD_SQL.ARCHIVE_RECORDS - Successfully Completed SVC_ARCHIVE
Tue Oct 20 12:16:01 Program: salesuploadarch: PID=XXXXXXXXX: Errors encountered. See error file
The run of salesuploadarch ran fine, but the 'grep' hit on the 'Abort' of saimptlogi earlier and thus causes batch to fail.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document