Critical Batch Job Is Exceeding Error Count By One, But Is Being Marked As Complete Instead (Doc ID 2875183.1)

Last updated on JUNE 12, 2022

Applies to:

Symptoms

ACTUAL BEHAVIOR
---------------
Critical Batch Job is exceeding error count by one, but is being marked as complete instead

  User noticed that Critical Batch Job (TXNDDT_BJ_100_01) is exceeding error count by one, but is being marked as complete instead of failed. Errors allowed count is set it to 2, errors occurred 3 still Job is marked as completed instead of failed.

EXPECTED BEHAVIOR
-----------------------
 In above scenario Job should be marked as failed instead of making as completed.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Setup the error allowed value for TXNDDT_BJ_100_01 as 2.
2. Execute the TXNDDT_BJ_100_01 job with few test accounts.
3. Check whether TXNDDT_BJ_100_01 completed if the errors are equal or less than the errors allowed value defined or it should update the status as failed.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot have due date batch job(TXNDDT_BJ_100_01) completed successfully.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.