ODI 11g Agent Always Uses PreparedStatements Causing Excessive Parsing and High CPU Usage
Last updated on MAY 12, 2017
Applies to:Oracle Data Integrator - Version 126.96.36.199.0 to 188.8.131.52.99 [Release 11gR1]
Information in this document applies to any platform.
In KM and procedure steps, every SQL is executed as PreparedStatement.
It can result in a lot of additional parsing (CPU) costs (for some queries +70%) during the data load, without any added value.
According to the query log, every SQL submitted by the agent is first prepared, then executed. This step would make sense if the statement was executed repeatedly, but it is not the case.
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