Database Reference
In-Depth Information
Purging metadata version history
As the metadata repository is usually backed by a database, it would be neces-
sary to purge unnecessary and archaic customizations made to composites that
are no longer applicable. Purging is only required for database-based MDS re-
positories as file-based repositories do not maintain composite version histories.
Purging metadata version history from a partition deletes all unlabeled documents
from it, leaving only the tip version (the latest version), even if it is unlabeled.
Purging metadata version history on a regular basis is a necessary maintenance
activity to prevent the database from running out of space or when its perform-
ance starts to degrade. Purging an MDS repository is performance intensive and
hence should either be attempted in a maintenance window or when the sys-
tem is not busy. To use Oracle Enterprise Manager Fusion Middleware Control to
purge the metadata version history, perform the following:
1.
Log in to Oracle Enterprise Manager Fusion Middleware Control.
2.
You can purge the version history of unlabeled documents from the partition
that are older than a selected time period. Navigate to
Farm_[Domain_Name] | soa-infra | Administration | MDS Configuration .
3.
The MDS Configuration dashboard page is displayed.
4.
In the Purge all unlabeled past versions that are older than field , enter a
number and select the unit of time.
5.
Click on OK .
6.
A progress box is displayed. When the operation completes, a completion box
is displayed.
7.
Click on Close .
It is also possible to purge metadata version history using the
purgeMetadata() command in WLST. You specify the documents to be purged
by using the olderThan parameter and specifying the time in number of
seconds. The following example purges all documents older than 100 seconds:
purgeMetadata(application='soa-infra', server=' soa_server1', olderThan=100 )
Search WWH ::




Custom Search