My Oracle Support Banner

Issue With Amendment Fallout Redo Mode - Error Retrieving Order From AbstractOrderCacheManager (Doc ID 2465249.1)

Last updated on FEBRUARY 23, 2024

Applies to:

Oracle Communications Order and Service Management - Version and later
Information in this document applies to any platform.


RAC Configuration Type : Active-Active
Weblogic Deployment Type: Clustered
WebLogic Server Version and PSU  :
Java version and Patch level : jdk1.8.0_144
OSM Version and Patch Level : OSM

During amendment for one of the production orders, when the automation task transitions from redo to fallout redo mode, we are observing the following error :

SQL Exception ORA-20006: Workflow thread does not exist followed by Error retrieving order from AbstractOrderCacheManager. 


Steps leading to the issue :

1) Sender Plugin for redo will execute and add correlation id and also send a request along with failTask.
2) Task will go in failed_redo and received state.
3) OSM will update the hist id of existing correlation.
4) External receiver is executed and accept the task (which is now failed_redo) - that is a problem.
5) Plugin of failed_redo will also start executing but failed as task is already moved to accepted.





To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.