Cube Instance Composite Label Is Not Getting Updated With LATEST Label While BPM Instance Patching
(Doc ID 2550003.1)
Last updated on SEPTEMBER 24, 2023
Applies to:
Oracle Business Process Management Suite - Version 12.2.1.0.0 and laterInformation in this document applies to any platform.
Applies to 12c.
Symptoms
On : 12.2.1.3.0 version, Orchestration Engine
ACTUAL BEHAVIOR
---------------
In BPM 12.2.1.3 the Cube Instance Composite Label is not getting updated with LATEST label while BPM Instance Patching or Migration
After deployment of the composite with Keep Instances Running option the JAVA API InstanceManagementService.migrateMultipleInstances is used for patching PENDING_MIGRATION instances and while running this script some of the instances are not getting migrated to latest label on the second deployment.
After third or fourth deployment , only instance in previous label (current label -1 deployment) get patched , the instance in label (current label -2 deployment) cannot be patched.
EXPECTED BEHAVIOR
-----------------------
All existing instance needs to be migrated to latest label.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Deploy the composite with Keep instances Running option.
2. Invoke script for instance migration.
3. Check CUBE_INSTANCE table COMPOSITE_LABEL column
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |