Database Sessions Remain Active For Oracle Revenue Management and Billing (ORMB) Jobs Even Though The Threadpool (TPW) Workers and Application (App) Servers Have Been Shut Down
(Doc ID 2358684.1)
Last updated on MARCH 06, 2019
Applies to:Oracle Financial Services Revenue Management and Billing - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
1) What is the proper way to abnormally terminate an ORMB batch job, if shutting down TPW and App server is not the way to do it?
2) What should be the database setting or application properties setting in order for ORMB jobs' database sessions to get killed automatically if the ORMB job itself is no longer running?
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