As the metadata repository is usually maintained in a database, it would be necessary to purge unnecessary and archaic customizations made to composites that are no longer applicable. Purging is only required for database-based MDS repositories, as file-based repositories do not maintain composite version histories. Purging the 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 the metadata version history on a regular basis is a necessary maintenance activity to control database size or when its performance starts to degrade. Purging an MDS repository is performance intensive and hence should either be attempted in a maintenance window or when the system is not busy. To use Fusion Middleware Control in order to purge the metadata version history, take the following steps:
It is also possible to purge the metadata version history using the purgeMetadata()
command in WLST. You can specify the documents to be purged using the olderThan
parameter, specifying the number of seconds. The following example purges all documents that are older than 100
seconds:
purgeMetadata(application='soa-infra', server='soa_server1', olderThan=100)
3.138.69.163