The two main database schemas in the Oracle SOA Suite database repository are: _SOAINFRA and _MDS. Composite instance and runtime information are stored in the SOAINFRA schema. Commonly used metadata like WSDLs, XSDs, rules, fault policies, etc. as well as composite deployments are stored within the MDS schema.

With every deployment / import of the metadata artifacts a new document version will be created in the MDS. This means that re-importing an updated WSDL-file into the MDS does not delete the previous version of the document. Furthermore we sometimes need to remove unnecessary and unwanted files from the repository. If this is not considered you might end in problems like below:

ORA-01654: unable to extend index DEV_MDS.MDS_PATHS_U2 by 128 in tablespace DEV_MDS ORA-06512: at "DEV_MDS.MDS_INTERNAL_COMMON", line 865 ORA-06512: at "DEV_MDS.MDS_INTERNAL_COMMON", line 1021 ORA-06512: at "DEV_MDS.MDS_INTERNAL_COMMON", line 1121 ORA-06512: at "DEV_MDS.MDS_INTERNAL_COMMON", line 1216 ORA-06512: at "DEV_MDS.MDS_INTERNAL_COMMON", line 1872 ORA-06512: at line 1

In order to avoid production problems because of a full MDS tablespace you should clean up the schema from time to time. My post „Remove data in Oracle MDS“ explains the following options to remove contents from MDS:

  • Remove directories and files from MDS using WLST
  • Remove directories and files from MDS using ANT
  • Remove files from MDS using WLST
  • Remove files from MDS using MBean Browser
  • Purge Metadata Version History using Fusion Middleware Control
Alle Beiträge von Danilo Schmiedel

Schreibe einen Kommentar