You are here

Tablespace Capacity Planning Report

Tablespace Capacity Planning Report
Author JP Vijaykumar
Written Sep 14 2017
Modified Mar 08 2019
***************************************************************************************************************
This script is provided for enducational purpose only.
The readers are advised to make necessary changes to the script as may be required for their use in their repective environments.
Pls test this script thoroughly in a lower environment, before using in any production db.

This script was generated/tested in Oracle 11G environment.
This script may not work in other versions of Oracle, pls modify the script as may be needed using your own discretion/ingenuity.
***************************************************************************************************************

I need to run capacity planning report in my project.

Requirements:

Predict db growth for 3 months, 6 months and one year.
Display message, if the available free space in each tablespace is less than it's projected growth for the next 3 months period.

Issues:

You need to increase the snapshot retention in the db to 3 months(conservative period).
If the snapshot retention is too low, the predictions may have huge variation on the expected actual growth of db.
If the available data in the dba_hist_tbsp_space_usage is scanty, the projections may not be near accurate.
If for some reason, the snapshots generation stopped, this report may not work as expected.

Usage:

Pl run this report in a lower environment and make necessary changes as applicable in your case.
This script work for Oracle rdbms, and was tested in version 11G.
If this script is to be used in a different version of Oracle rdbms, pls make necessary modifications to run.
As per your convenience/requirement, the flagged message "ADD SPACE" can be changed to display a meaningful message.

Owing to many limitations, there will be a fair chance of variation in the projected growth of the db and the actual growth of the db.
And yet, I will have a starting point as to how much diskspace, upfront I need to be procured for my db's future growth.
Few deviations this way that way are ok, as I may not be caught off the guard with sudden huge diskspace requirements.