Last updated on NOVEMBER 21, 2014
Applies to:Oracle Communications Order and Service Management - Version 7.2.4 and later
Information in this document applies to any platform.
When a pivot node is created at runtime, the process will fork out based on the pivot node. When the revision is applied and the pivot node is recreated at runtime, the compensation is not properly happening for the process. The rolling back of process is not happening if the pivot node which is present in earlier version is missed in the current version.
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