As the amount of data in the Oracle SOA Suite database tables grows over time it is recommended to maintain the database growth proactively. Maintaining the SOA Suite databases includes purging for the SOA database tables. This can be done by using one of the various available purging strategies depending mainly on database growth.
If purging is not done using the best fitting strategy it will cause a growth in the SOA database tables which will then lead to performance problems. It is also known that this can cause a situation where it will be hard to clean up the tables by purging based on the pure amount of data that needs to be purged.
Keep in mind that for any implemented solution, not to run purging in parallel with online activities on the system as it dramatically reduces the performance of the online operations. Keep in mind that any purging solution needs to run in maintenance mode where no online activity is allowed.
The SOA Suite environment for Oracle Fusion Applications (FA) is configured across multiple Weblogic Domains for FA. Diverse purging strategies may be used for different FA Domains such as Human Capital Management (HCM), Finance, Supply Chain Management (SCM) among others but in all cases, it is important to run purging for any SOA installation in FA to avoid the problems discussed above.
The standard purging scripts are located under$SOA_HOME/rcu/integration/soainfra/sql/soa_purge where $SOA_HOME refers to the SOA ORACLE_HOME of the installation. For FA this would be located under the following path: /u01/app/fa/fusionapps/soa.
For additional information about the methods for managing and troubleshooting database growth issues, see the Managing Database Growth in the Oracle Fusion Middleware Documentation that corresponds to the FMW release for which the FA environment is currently working with.