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"
Last updated on NOVEMBER 18, 2016
Applies to:Oracle SOA Suite - Version 22.214.171.124.0 to 126.96.36.199.0 [Release 11gR1]
Oracle(R) BPEL Process Manager - Version 188.8.131.52.0 to 184.108.40.206.0 [Release 11gR1]
Information in this document applies to any platform.
You have multiple process instances in-flight during an upgrade from 220.127.116.11.0 (or earlier versions).
- The in-flight instances are for a BPEL process which contains a While Activity.
- Also, your resuming activity occurs within the While Activity.
After the upgrade, these type of in-flight instances cannot be resumed.
When you try to resume those instances, the audit trail shows:
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.
The log files show:
Starting in version 18.104.22.168.0, a new internal variable CubeEngineDefs.SCOPE_VAR_loop_condition was introduced (declared in the BPELWhileBlock).
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