[sloppypoet]

Our database LOBs continue to grow seemingly uncontrollably. So far this has not impacted production but we are running out of space and fear what will happen when we do. What can we do to control this growth? Any help is appreciated.

[chrisplough]

Hello,

You're looking for the OTM Purge process in order to reduce the database LOBs. In order to get started, I recommend looking up the Purge process in the OTM Administration Guide and also searching these forums for "Purge". You'll find some existing issues that users have given workarounds for.

I noted that you've already posted on this topic a bit, so it's possible that you may need to compact your tablespaces in order to reclaim space after the purge process.

--Chris

[sloppypoet]

Chris, thanks for the response. We are on the same page and I spent some time yesterday looking through the admin guide regarding the purge process. My concern is how do I control which records are purged.....or is this done automatically?

We purge transmissions/transactions regularly but never shipments. Is it the shipment purge that needs to be done?

Thanks!

[chrisplough]

Most companies have had to modify the purge scripts in order to get them to work correctly, and/or to get them to purge additional data elements.

I would guess that either your scripts need to be modified, because the related shipments are keeping the transmissions/transactions from purging out correctly (an alternative is simply to null out the transmissions/transactions). Or - you need to defrag (i.e. recreate) your tablespaces in order to reclaim the used space.

Can you verify that the purge script is truly purging out your transmissions/transactions?

--Chris