Step 4: At File system level calculation: To make all tablespaces at 75%–> 25GB is required. Check tablespace utilization and bring down the utilization below 80% for all tablespaces if possible.If not check how much space needed at tablespace level to make it 80% and add that space also in total calculation.įor EDSDATA tablespace –> 24G needed to make it to 75%(99172/1024=96G*25/100= 25% 0f origninal value(this space to be added to make it to 75%) Step 3: At Tablespace Level:Ĭlick here for tablespace scripts. Growth rate: 1GB/month–> For one year 12GB. Sdb.report_date in (select next_day(trunc(report_date, 'MONTH')-1, 'Monday') from system.db_trends where report_date= sdb.report_date) Where sdb.report_date > sysdate - 180 and sdb.database='TESTDB' and Step 1: Login into the database: step 2: Calculate database growth by using below script: select sdb.database, sdb.report_date, sum(sdb.used_space/1024/1024) "used_space-GB", sum(sdb.total_space/1024/1024) "total_space-GB" The UNIX team will receive file system utilization alert and since its ORACLE database disk, they will ask us to clear some space to bring it under threshold.īefore asking for space, we need to check last one year database growth, tablespace utilization in database and how much space needed at disk level to bring it below threshold.īelow is the real time example steps for oracle database capacity planning(the database name TESTDB and server name is UNIXSERVER). Capacity planning for ORACLE database comes into play when ORACLE file system reaches above threshold level.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |