How to reclaim disk space after purging the SOA infrastructure or BPEL Database (Doc ID 1387722.1)

Last updated on OCTOBER 13, 2017

Applies to:

Oracle SOA Suite - Version 11.1.1.1.0 and later
Information in this document applies to any platform.

Goal

In a typical production SOA installation, there is a very high throughput of data in the infrastructure database, also known as the dehydration store database. These data can accumulate and take up huge amounts of space in the database, if not managed at regular intervals. Various mechanisms of dealing with this data growth, such as purging and partitioning, are shipped with the SOA suite product. These mechanisms are described in detail in the following notes:

For 11g

Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite and Oracle Business Process Management Suite
11g Release 1 (11.1.1.4.0)
Part Number E10226-07
9 Managing Database Growth
http://docs.oracle.com/cd/E29542_01/admin.1111/e10226/soaadmin_partition.htm#CHDIHDIJ

For 10g

Oracle BPEL 10g Purging Strategies Doc ID 1286265.1
Oracle BPEL Process Manager 10g Database Schema Partitioning Doc ID 1286264.1

However, after deleting old and unused data in the dehydration store, administrators are sometimes surprised that the freed space is not visible on disk. This note explains why this is the case and provides some pointers on how to reclaim space freed by purging.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms