If you had re-deployed a BPEL Process in 10g, the instances that were available before the re-deployment, would have become stale (grayed out) and you would not be able to see the Flow/Audit Trail. There will be an error stating "revision for the instance # was not loaded by the domain...XXProcess revision 1.0 may have been deleted from the domain manually; in this case the domain would not have been able to mark all instances belonging to the process as stale". You can however, view the instance by clicking on "View Raw XML" from the audit table, in the XML form.
In 11g, this problem seems to have been overcome. The instances of the composite can be viewed from the Audit Trail/Flow tab even though the instance has been marked "Stale", like seeing any active instance of a composite.
Peace!
Cheers,
-AR
What makes BizTalk360 the best BizTalk Server Monitoring tool?
-
Key takeaways from this blog Introduction BizTalk Server Monitoring tools
Azure Serverless Monitoring Pricing Structure of BizTalk360 If everything
is a ...
1 year ago
3 comments:
If I redeployed some composite, can I recover the instances that now are in the "stale" status? Thanks.
Stale instances cannot be recovered if the composite is redeployed.
However, if you can update the state in the table cube_instance from 9 to 5, that particular component instance can be made active.
Cheers,
-AR
Hello,
Would updating the cube_instance
cube_instance from 9 to 5, leave the cube instances in an inconsistent state (assuming that the version of BPEL redeployed was almost the same and coded in a backward compatible manner) ?
Thanks,
Rama
Post a Comment