MDM F1-SYNRQ Batch Out Of Memory Error
Last updated on AUGUST 10, 2015
Applies to:Oracle Utilities Meter Data Management - Version 22.214.171.124 and later
Information in this document applies to any platform.
Performing initial load of data from MDM to the OUA requires F1-SYNRQ batch for large number of records (about 2.5 mln sync requests), resulting in OutOfMemory errors (either "java.lang.OutOfMemoryError: GC overhead limit exceeded" or "java.lang.OutOfMemoryError: Java heap space") even with large heap size (2 GB).
This error is reported in threadpoolworker log - batch log is not yet created and threads are still reported in status "Pending". This leads to conclusion that OutOfMemory error is caused by initial batch query that selects the records for processing. This query seems to load all the records to memory (instead of using e.g. scrollable cursor).
As a workaround limit the number of records processed by the single batch run using batch parameters or by starting single threads in separate submissions.
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