How to Resolve OutOfMemoryError in CreateWorkUnit Upon Running a cm Java Batch Job with a Huge Number of Records to be Processed
Last updated on OCTOBER 18, 2016
Applies to:Oracle Utilities Customer Care and Billing - Version 2.3.1 to 2.3.1 [Release 2.3]
Oracle Utilities Framework - Version 2.2.0 to 2.2.0 [Release 2.2]
Information in this document applies to any platform.
Upon running a cm java batch job with more than 240000 records to be processed, an OutOfMemoryError is raised in createWorkUnit.
The recommendations in Patch 7447321 regarding the usage of createJobWorkForQueryIterator have already been used.
TPW is given 4GB heap space.
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