Whenever ORMB Batch Jobs' Threads Encounters Severe Errors, Batch Run Status Still Getting Completed
Last updated on FEBRUARY 05, 2018
Applies to:Oracle Financial Services Revenue Management and Billing - Version 188.8.131.52.0 to 184.108.40.206.0 [Release 2]
Information in this document applies to any platform.
Whenever the ORMB batch jobs encounters severe errors, like SQL errors or anything related to infrastructure, only the Batch Run Thread (CI_BATCH_THD) goes to 'Error' status, but eventually this error does not reach the Batch Run (CI_BATCH_RUN) level because it is still going to 'Complete' status.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms