OracleFree calculatorPDF, Excel, Word exportOracle E-Business Suite

Oracle EBS Tablespace Growth Forecast Calculator

EBS databases grow in steps: transaction history, attachments, workflow and request logs. This calculator turns a measured monthly growth rate into a clear answer: when you cross your alert threshold and how much storage to add.

Your numbers

GB

Used size from DBA_SEGMENTS or DBA_DATA_FILES minus free space.

GB

Total data file size for the tablespace or database.

% per month

Measure from AWR or monthly size snapshots.

12 months
85 % of allocated
GB

For example Purge Concurrent Request and Manager Data, workflow purge, archived history.

Your results

Months until threshold is crossed
7.4 months
Zero means the threshold is already exceeded.
Additional storage to add
144.89
Current utilisation
70.8%
Projected used space at horizon
1,143.16
Compound growth with no purge.
Projected space after purge
1,143.16
Allocation needed at horizon
1,344.89
Space to allocate so utilisation stays at or below the threshold.

Growth is rarely perfectly compound. Use your own measured history, and add headroom for month end, upgrades and temporary data.

Save results:

Projected used space (GB) by planning horizon

Sweeps Planning horizon from 1 to 60, holding your other inputs fixed.

Ask your database questions in plain language

Optional demo of private natural-language queries over operational and capacity data.

Optional. The tool and every export work without this. No spam.

How to use the calculator

Enter current used and allocated space, then your measured monthly growth rate. Take growth from monthly snapshots of segment size over at least six months, not from a single busy month. Choose a planning horizon and an alert threshold, such as 85 percent. If you plan a purge, enter the space it frees. The outputs show months until the threshold, projected size and the extra storage required.

The formula

Projected size equals current used space times one plus the monthly growth rate, raised to the number of months. Months to threshold equals the natural log of threshold space divided by used space, divided by the natural log of one plus the growth rate. Allocation needed is projected size after purge divided by the threshold fraction. This assumes steady percentage growth, which is a planning approximation.

  • Use segment level history, not file size, to measure growth
  • Check large objects, such as AQ, attachments and workflow tables
  • Run the standard purge programs before buying storage
  • Recalculate after major go-lives and acquisitions

Reading the result and common mistakes

If the months to threshold is under your procurement lead time, act now. A common error is projecting from a month with a one time load, which overstates growth. Another is forgetting that backups, standby copies and clones multiply the real storage cost. Purges free space inside data files, so allocated space only drops after a reorganisation or shrink.

Frequently Asked Questions

How do I measure EBS database growth?

Record the total size of segments by tablespace or schema at the same point each month, for example from DBA_SEGMENTS, and compare. Six to twelve months of history gives a more reliable rate than any single month.

Which EBS tables usually grow fastest?

Common heavy hitters include workflow and notification tables, concurrent request history, general ledger and subledger accounting tables, and attachment storage. Your own top segments query will show the real list.

Will purging free space for the operating system?

Not immediately. A purge frees space within the tablespace for reuse. To return space to storage you typically need to move objects or resize data files, which should be planned with your DBA.

Is compound growth the right model?

It is a reasonable first approximation when growth scales with activity. If growth is steady in gigabytes rather than percent, or driven by one off projects, adjust the rate or run scenarios with different values.

If capacity questions keep landing on your DBA, tell us what data you collect. We can discuss natural-language access to those figures on your own infrastructure.