My Oracle Support Banner

Subset Of Threads On A Batch Job Stay 'In Progress' Without Processing Records (Doc ID 2475572.1)

Last updated on JUNE 03, 2024

Applies to:

Oracle Utilities Meter Data Management - Version and later
Information in this document applies to any platform.


**Any examples provided in this article do not represent real life personal/confidential information**
**Disclaimer:** This KM article may include the following abbreviations:

MDM - Oracle Utilities Meter Data Management
DBA - Database Administrator

On : version, Usage

Subset of threads on a batch job stay 'In Progress' without processing records

Batch processing seems to happen without issues in Production, but an occasional batch job fails to complete some of its threads and leaves the job in a ‘Pending’ state while those threads remain ‘In Progress’ processing 0 records.

Upon monitoring the database using Oracle Enterprise Manager there seems to be a single query which consumes over 40% of CPU but never seems to complete. This is an insert statement into the F1_TSPACE_ENTRY table most of the times or occasionally the F1_SYNC_REQ_IN table.




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

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