My Oracle Support Banner

Aborted Instance Leaves Inactive Resequencing Groups (Doc ID 2763421.1)

Last updated on MARCH 24, 2021

Applies to:

Oracle SOA Suite - Version 12.2.1.3.0 and later
Information in this document applies to any platform.

Goal

It is observed that in case a business error occurs when interfacing with BRM using Mediator, then composite is aborted automatically the instance in the BPEL flow and as a result:

1. Business Flow instances are aborted and cannot be retried/aborted by console
2. Aborted Instances leave Inactive re-sequencing groups. When querying SOAINFRA schema, we notice that those groups are in error status 3

The impact of the above is the following:

1. Inactive re sequencing groups cannot be cleared because we cannot abort/retry the instance since it was aborted from EBF code. The workaround for this is to either delete the aborted instance and skip re sequencing group or update status from database.
2. Because of the inactive re sequencing group, subsequent orders on the same account remain running because manual intervention is required on the re sequencer.

For batches, customer is looking for SQL statements to work on resequencer tables. As you can see, customer has found out a workaround to update the status on mediator_group_status table and any other tables
 

Solution

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
Goal
Solution
References


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