[rj5316]

How does one do a table sizing in OTM

what are impending factors ...

Rgds---

[nick.polites]

It varies by shipments, orders, invoices etc. and how long you want to keep your transmissions. There isn't a set way to measure this as each client uses the application differently. The larger and longer they are, the larger DB size you will need. For midsize to large corporations estimate between 150-300GB for the database, not including the amount for backups.

[chrisplough]

Also, the best way to reduce OTM DB growth is to setup and utilize the purge packages/procedures mentioned in the OTM Administration guide. This often requires customization of the processes to get them to fully work (we've done this for a lot of clients), but should improve significantly in OTM v6.0.

This process will purge out the integration XML that is saved for incoming and outbound transmissions, which can account for 70-80% of your database growth.

--Chris

[Stefano]

Chris
After purging procedure on I_TRANSMISSION & I_TRANSACTION, seems however necessary to run a REORG on these table (due to CLOB/BLOB) objects to really reclaim space, do you know a different way?
This happens in your experience only working with partitioned table ?
Thanks in advance

[nick.polites]

That's probably the easiest way to show the reclaimed space. There are other ways of doing this such as creating a new tablespace and copying the data over to it, but this is a bug in the Oracle database code.

[stoganv]

Why reorg when you'll be reusing the space for the next round of inserts of xml clobs?

[nick.polites]

You don't need to but is speeds up the exports if you do.