Tuning the Purging Strategy; Oracle SOA Suite Metadata Repository Performance Management by Martijn van der Kamp
By Juergenkress-Oracle on Apr 11, 2016
colleague, Paul Wever, wrote an excellent blog about turning the MDS to
increase performance. Purging is something we do at almost all our
customers. Paul provides excellent tips, tricks and insights to increase
In my job as system administrator/DBA, projects related to Oracle’s SOA Suite I put a lot of emphasis on configuration of the environment, like the OS, the Oracle database, WebLogic, OSB, and other products. Part of the Oracle SOA Suite is the Oracle Metadata Repository, where all metadata and run-time data of applications is stored. This repository is often forgotten in performance management, but deserves special attention when dealing with performance improvements.
This blog is part of a series of blogs around Oracle SOA Suite Metadata Repository Performance Management. In this blog we will show how a performance gain of factor more than 100 was achieved while purging the Metadata Repository.
Oracle Metadata Repository
Oracle Metadata Repository is an Oracle database that contains additional schemas to support Oracle Fusion Middleware and its components, for design and run-time management of the applications. Oracle SOA Suite mainly uses two components:
- The Metadata Store (MDS) to store all SCA artifacts
- The Dehydration Store (SOAINFRA) to persist composite instances and to audit composite instance
Investigating performance issues around purging the Oracle Metadata Repository, I stumbled over the following delete statement that was executed during purging the Oracle Metadata Repository: Read the complete article here.
For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.