Last updated on OCTOBER 17, 2016
Applies to:Oracle Value Chain Planning Integration Base Pack - Version 11.1 and later
Information in this document applies to any platform.
There are a few ODI errors which are NOT reported back to ASCP
They appear to be Connection/Network/Communication type failures that are not reported back
Client seeded JDE-PIP ODI scenario,
it errored in ODI
yet ASCP continued as if successful
As an Example:
1. Setup the JDE-VCP PIP
2. Assume a setup/configuration issue (in this case JDBC connection might have been incorrect)
3. Launch JDE Collection
4. in ASCP it all runs and appears successful.
-- the ASCP calls ODI
-- ODI runs the scenario
-- Monitor the ODI scenario
-- ODI scenario fails - jdbc connection bad
-- ASCP request log shows - SUCCESS, SUCCESSS, SUCCESS on each scenario pkg
-- What trigger or signal did ASCP receive back that said it was OK to continue?
-- Even if the JDBC connection is failed, how did ODI report it was OK to continue?
-- Why didn't ASCP Stop, Wait, and receive a Timeout?
That is all without any Customization running.
Expected Behavior: if the communication is lost between ODI and ASCP then ASCP ought to sit, wait for a response from ODI and if not received in some amount of time, ASCP ought to error on Timeout, instead of continue as if successful.
In another SR/bug 19057003 in June-2014, the same fix was approved to be applied for AIA release 3.1
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms