[ianlo]

Hi all,

I would like to find out if anyone has the following setup?

1) Whenever a transmission purge is executed, the shipment events in the Shipment Track and Trace screens are also purged.

2) This is expected and I have been told that I should use domain.no_status_purge = TRUE to just purge the XML CLOB and not the IE_SHIPMENT_STATUS tables.

3) However, I am receiving approximately 3000 messages per day and I need to manage the tablespace growth and I must keep my shipments for at the least 60 days. It is not sufficient for me to just purge the CLOBs alone. I need to manage the rate of growth of the transmissions without impacting shipment track and trace and purging the shipment events along with the transmissions.

I have also noticed that there is a SS_STATUS_HISTORY table where all the events are stored. Why isn't Shipment Track and Trace using this table?

Is there anyway to workaround this problem?

Thanks for any help!