I have encountered a problem which is specific to ODI 11G (18.104.22.168.3) where ODI session gets stuck.
I have a procedure and in a particular step there are multiple Update statements. When i run the job through standalone agent the job gets stuck in this step.
When i took the SQL's and run in a DB tool it fails with a valid reason. I fixed the data issue and ran the job again and it didn't stuck this time.
So i did a negative test and found that the ODI job gets stuck only if there is some data issue and the SQL actually fails.
Any help on fixing this is highly appreciated. Thanks!!
yes most of our code has been written the way you have suggested.
The problem here is we have this code in production in 10g and we recently upgraded it to 11g. We can make the change but want to know what the reason is.
Coming to the Error message, it doesnt fail in the operator it just hangs. The error can be anything in the DB tool (ex: attempt to multiple rows)