MDM F1-SYNRQ Batch Out Of Memory Error (Doc ID 1937737.1)

Last updated on DECEMBER 07, 2023

Applies to:

Symptoms

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.

Cause

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