My Oracle Support Banner

BALAPY Batch not Considering MAX-ERRORS=0 (Doc ID 2703517.1)

Last updated on SEPTEMBER 01, 2020

Applies to:

Oracle Financial Services Revenue Management and Billing - Version 2.6.0.1.0 and later
Information in this document applies to any platform.

Symptoms

On RMB v2.6.0.1.0, BALAPY batch run did not consider MAX-ERRORS=0

ACTUAL BEHAVIOR
----------------------------
BALAPY.properties file had the parameter of MAX-ERRORS set to '0'.
The thread in BALAPY had an error as well. But the job went to complete status.

EXPECTED BEHAVIOR
---------------------------------
We were expecting the job to fail for the failed records which is more than '0'.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Ensure to set MAX-ERRORS to 0.
2. Make sure to get at least one record to ERROR for the run.
3. Run the BALAPY job.
4. Notice if Job Status is 'Complete'.
May check if this is happening for other Batch job too.

BUSINESS IMPACT
---------------------------
The issue has the following business impact:
This seems not considering the MAX-ERRORS setup and needs to ensure it works.

Changes

 Put MAX-ERRORS = 0 for the batch.

Cause

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
Symptoms
Changes
Cause
Solution
References


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