Setting ASAP CSDL Rollbacks With PONR (Point of No Return) (Doc ID 2045319.1)

Last updated on AUGUST 28, 2015

Applies to:

Oracle Communications ASAP - Version 7.2.0 and later
Information in this document applies to any platform.

Goal

On : 7.2.0 version, SARM

ASAP CSDL Rollback is operating in the following manner.

Here is a situation when attempting  to avoid CSDL rollbacks:

CSDL1
ASDL1
ASDL2 -->execute ASDL2_rollback if ASDL3 fails
ASDL3

CSDL2
ASDL1  --> execute ASDL1_rollback if ASDL2 fails.
ASDL2  

With the above setting, during the execution in CSDL2, when it fails in ASDL1, the rollback operation will extend to CSDL1 to invoke ASDL2_rollback.

Is there any way to avoid the CSDL1 rollback in this case? We are expecting that only the current CSDL is rolled back. No completed CSDL should be rolled back.

 

Solution

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