At different process steps, Oracle BPEL engine dehydrates (stores) information about process instances in a database, and retrieves them when the process instance is ready to resume. The dehydration store is critical to Oracle BPEL integrity and performance. Over time, the dehydration store can grow and affect overall performance of the solution. How do you manage the data growth in the dehydration store?
My colleague Deepak Arora (see his blog here) has written an excellent white paper on purging old instance data from SOA Suite/BPEL 10g and also a great blog post on automating the deletion of old partitions. If you are interested in this topic, I encourage you to check them out!