Oracle Capacity Planning

by JP Vijaykumar

Prelude

02:00 AM
Boss:

Reclaim every byte of free space from other tablespaces in the database/ server that are not 100% full and allocate to EMP_TBSP01 tablespace, which is 100% full.

OncallDBA (Oracle):

I need to resize, at least a few dozen datafiles to get 1 GB of free space on the server, to allocate to EMP_TBSP01 tablespace. I have to work at least couple of hours, just to search and reclaim free space from other tablespaces, which are not 100% full and allocate space to EMP_TBSP01 tablespace.

There is no perfect world. There is no perfect application. If I am permitted to say, there is no perfect CAPACITY PLANNING. In this world, we strive hard to achieve near PERFECTION.

Better capacity planning should provide sufficient free space for the database to grow for at least three months down the road. It should give sufficient breathing time for the support team to meet the database’s disk space requirements. If you have to fight for free space everyday, then you are in fire fighting mode.

DISK SPACE ESTIMATED FOR THE DATABASE(RDBMS) ONLY
ESTIMATES ARE BASED ON ASSUMPTIONS, SAMPLING, STATISTICS
ESTIMATES CAN NOT QUANTIFY DISK SPACE REQUIREMENTS IN REAL TIME
ACTUALS ALWAYS VARY FROM ESTIMATES

Latest Articles