ODI Jobs That Load to BAM Comsumes More and More Memory from the Server
(Doc ID 1143703.1)
Last updated on JUNE 16, 2022
Applies to:Oracle Data Integrator - Version 10.1.3.5.6 and later
Information in this document applies to any platform.
Using ODI 10.1.3.5.6, and running one ODI scheduler Agent, with following Java settings in the ODI "odiparams.sh" file:
The jobs are scheduled to run every n minutes. After a couple of days, the OS memory is used up and the OS user gets a Closed Connection error and can not log into the machine any more.
The symptoms vary depending on your environment set up but mostly other symptoms you will see are:
- ODI Agent dies with no error.
- the scheduled Scenario errors with java.lang.OutOfMemoryError: GC overhead limit exceeded
- Or Scenarios hang at RUNNING status forever.
It happens regardless which version of the java is being used.
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