ODI Session Runs To A Successful Completion But No SQL Code Is Recorded In Operator For Any Of The Session Steps And Tasks
(Doc ID 1318632.1)
Last updated on JUNE 16, 2022
Applies to:
Oracle Data Integrator - Version 10.1.3.2.0 and laterInformation in this document applies to any platform.
Symptoms
All of a sudden, and no matter what type of Oracle Data Integrator (ODI) object is executed (Variable refresh, Procedure, Integration Interface, Package...), the corresponding Session goes to completion in the ODI Operator but close inspection of the Operator shows that no code has been recorded in the Journal for any of the associated Steps and Tasks.
Running the same with an ODI Agent started in verbose/trace mode shows that the code generation phase is correct and complete, but no SQL code is created in the execution related tables.
Note that Oracle database is used to host the ODI Work Repository.
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 |