After Running ESB Instance Purge Scripts, The Values Of The ID Field In The ESB_ACTIVITY Table From the ORAESB Schema Are Not Unique, Causing Several Problems
(Doc ID 780995.1)
Last updated on AUGUST 01, 2018
Applies to:Oracle ESB - Version 10.1.3.3 to 10.1.3.4 [Release AS10gR3]
Information in this document applies to any platform.
***Checked for relevance on 31-Mar-2011***
You have been using ESB instance purge scripts located on the ESB server at $OH/integration/esb/sql/other/purge_ESB_* on a version lower than 10.1.3.3.1 MLR#18 or lower than 10.1.3.4 MLR#4.
You have noticed problems with the ORAESB.ESB_ACTIVITY table.
The values of the field ID in the ESB_ACTIVITY table from the ORAESB schema are not unique, a situation which causes some trouble in some components of ESB, because this field is used as a "soft foreign key" to other tables, including ESB_TRACKING_FIELD_VALUE, ESB_FAULTED_INSTANCE, etc. Some of the problems are:
1. Frequent occurrence of wrong fields in the "Tracking Data" section ("Detail" section) of the "Instances" view in the "ESB Control" web application.
2. "Purge_by_Date" procedure not working as expected.
3. Potential errors in queries to the ESB_FAULTED_INSTANCE table due to the relation between that table and the ESB_ACTIVITY table ID field.
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