ODI Agent Session Status Query Impacts Database Performance Due To Missing Indexes In ODI 11g
(Doc ID 1681972.1)
Last updated on MAY 06, 2021
Applies to:Oracle Data Integrator - Version 18.104.22.168.0 to 22.214.171.124.99 [Release 11gR1]
Information in this document applies to any platform.
After observing poor performance when executing Oracle Data Integrator (ODI) 11g Scenarios on an Agent, an auditing of the SQL instructions executed at runtime has been performed, and the following SQL instruction has been identified:
- To be executed very frequently... and
- Indicate the performing of full table scans...
.. therefore resulting in inefficient processing and poor performance.
The SQL command ODI 11g executes is:
select count(*) RUNNING_SESSIONS
from WORK_REP.SNP_SESSION where SESS_STATUS = :1 and AGENT_NAME = :2
The SQL explain plan states the following:
TABLE ACCESS FULL - (operation) | SNP_SESSION - (name) | 32217 - (rows) | 597K - (bytes) | 4403 (1) - (%CPU) | 00:00:53 (time)
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