ODI 11g Agent Always Uses PreparedStatements Causing Excessive Parsing and High CPU Usage
(Doc ID 2040261.1)
Last updated on JUNE 16, 2022
Applies to:
Oracle Data Integrator - Version 11.1.1.7.0 to 11.1.1.9.99 [Release 11gR1]Information in this document applies to any platform.
Symptoms
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.
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |