ODI Version: Oracle Data Integrator 11G
We have custom windows Batch scripts which are being called using ODI OSCommand2 Utility.
When the Batch scripts contains a WAIT statement - CHOICE /T 10 /D Y (the command instructs cmd to wait for 10 seconds and then Proceed to next step)
ODI Process hangs and never completes.
Removing the WAIT step from batch script, the process completes successfully.
Any suggestion on this behavior and how to rectify it would be very helpful.
This is the ODSI forum.
The ODI forum is Data Integrator
What happens when you run your script outside of ODI?
Keep in mind that CHOICE reads from standard-input, so that might be blocking it. To prevent that, use this :
REM | CHOICE /T 10 /D Y
Is there any point in waiting for 10 seconds in your script?
Edited by: mikereiche on Dec 1, 2011 9:38 AM
The issue is resolved now.
We had a mandatory condition where the script needs to wait before proceeding for the next step.
Instead of using, WAIT command in our windows batch scripts, i used the below command :
PING 184.108.40.206 -n 1 -w 20000 >NUL
This worked fine and did not give any errors in ODI. The above command will work in any cmd prompt.
Hence, this question is answered