Troubleshooting Batch Validation
Batch Validation completes with a status of FAILURE when it encounters any error or warning. However, a failed job may abort or it may complete with warnings. It does not abort if there were only warning messages because a custom procedure or a TMS derivation procedure failed. Any other error is a fatal error and causes the job to abort.
Check if a failed Batch Validation aborted or completed with warnings
If the log file displays the message Batch Validation aborted due to an error, the job aborted. If the log file displays the message NOTE: Batch Validation Completed with warnings due to TMS or Procedure execution or generation, this can mean that the job returned warnings only and completed, or that the job aborted due to an error and also returned warnings; in this case, the job aborted if there is any SQL error in the log file that does not relate to TMS execution (TMS SQL errors would return only warnings).
Effects of an aborted job
If Batch Validation aborts, updates related to univariate discrepancies and procedures that executed successfully before encountering the fatal error are not rolled back. The Current view will show any updates made prior to the fatal error. However, the values for Last_Batch_TS and Mark_rdcm are not updated. For this reason, stable views will not reflect the updates that occurred before the job aborted.
Effects of a job that completed with warnings
When Batch Validation continues to run despite warnings caused by procedures, edit checks are performed as expected for all validation procedures that did not fail and data is populated for derivation procedures that did not fail. The Current view shows updated data and the Stable view data is refreshed.
Note:
The default error log is overwritten at each stage of the batch data load. To retain the error log you must enter a new name in the Output File field of the Submission Details window of PSUB.For more information, see: