While Loop of In-Flight Instances Cannot be Resumed Following an Upgrade with ERROR: "ORABPEL-02118 Variant not found. The variable "__loopCondition" is not declared in the current scope" (Doc ID 1451018.1)

Last updated on NOVEMBER 18, 2016

Applies to:

Oracle SOA Suite - Version 11.1.1.4.0 to 11.1.1.6.0 [Release 11gR1]
Oracle(R) BPEL Process Manager - Version 11.1.1.4.0 to 11.1.1.6.0 [Release 11gR1]
Information in this document applies to any platform.

Symptoms

You have multiple process instances in-flight during an upgrade from 11.1.1.3.0 (or earlier versions). 

After the upgrade, these type of in-flight instances cannot be resumed. 

When you try to resume those instances, the audit trail shows:

<message>
The transaction was rolled back. The work performed for bpel instance "xxx" was rolled back to the previous dehydration point, but the audit trail has been saved.You can recover the instance from the recovery console by resubmitting the callback message or activity for execution.
</message>

 

The log files show:

 

 

Changes

 Starting in version 11.1.1.4.0, a new internal variable CubeEngineDefs.SCOPE_VAR_loop_condition was introduced (declared in the BPELWhileBlock). 

Cause

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