We are currently on OTM 5.5 (CU4 RU2). We perform a fair amount of integration into OTM via SOA (20K transmissions = ~ 50K transactions). This results is a fair amount of database space being consumed by the I_TRANSMISSION table, due to the staged XML stored in CLOB columns. Due to this, we do run the OTM-provided I_TRANSMISSION purge process on a nightly basis (we keep 14 days). Immediately after this purge we run a reorg job to reclaim the space from the purged CLOB data. This reorg runs an extemely long time (3 hours or more). Much of this has to do with how the I_TRANSMISSION table is partitioned out-of-the-box. Various folks at Oracle said that there are many OTM customers that have more integration volume, keep more days of I_TRANSMISSION data, but have no problems to speak of.
So.......I am curious to find out what 'best practices' other OTM customers have instituted to make this process less painful. Any feedback would be greatly appreciated!
So.......I am curious to find out what 'best practices' other OTM customers have instituted to make this process less painful. Any feedback would be greatly appreciated!
Comment