Database Reference
In-Depth Information
a small footprint of backend database a partitioning methodology can be com-
pletely avoided.
Filtering out completed, closed, and terminated composite instances from Oracle
Enterprise Manager Fusion Middleware Control is the easiest way to purge in-
stances from the Dehydration Store that are no longer running. It also provides
the ability to delete instances for a particular composite or from the entire infra-
structure and the steps involved to achieve this are already covered in
Chapter
Single-threaded or looped purging
Although deleting instances using the
Delete with Options
button from Oracle
Enterprise Manager Fusion Middleware Control may seem to be simple, it is not
recommended for deleting a large number of instances. This operation tends to
be time consuming and may result in a timeout on the console and it is also
harder to tell whether it is completed or not. Instead, it is best to use the stand-
ard looped purging scripts available in the
[PREFIX]_SOAINFRA
package to
delete instances that are no longer required. The instance purging scripts are ef-
fective and can be executed to delete process instances that are in the following
states:
•
Completed Successfully
•
Faulted
•
Terminated
•
Stale
•
Closed and Non Recoverable
Instances that are live, running, and pending recovery, either at the service
engine level or at the composite application level are left untouched by the
looped purging script. To purge these instances, it is first required to move them
to states that are supported by the purging scripts. Another important fact to
note is that purging deletes only closed composite instances that are beyond
their retention period. The
retention_period
is applied only on process in-
stances executing on the BPEL engine where users would want to retain the
composite instances based on the
modify_date
in the
cube_instance
