An IFS database has grown to a large size after less than two years of use, and clearing out old data from the tables that seem like obvious candidates (like shop order clocking/lines) doesn't meaningfully reduce the size — how do you actually identify what's consuming the space?

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

Don't assume which tables are the culprit — query Oracle directly to find the actual largest segments, for example: SELECT owner, segment_name, bytes/1024/1024 meg FROM dba_segments WHERE segment_type = 'TABLE' ORDER BY bytes/1024/1024 DESC, limited to the top handful of rows. This often surfaces something unexpected — a common cause of database size growing faster than expected is a large volume of images or documents stored as BLOBs rather than transactional row data. It's also worth checking whether your database's own storage configuration (datafile initial size and extent sizing) is causing Oracle to keep allocating new disk space rather than reusing freed space, which can make the apparent database size larger than the actual data it holds.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Developer Studio, deployment, and upgrades questions