Purging metadata version history
As the metadata repository is usually backed by 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 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 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 Oracle Enterprise Manager Fusion Middleware Control to purge the metadata version history, perform the following:
1. Log in to Oracle Enterprise Manager Fusion...
