This content has been marked as final. Show 4 replies
We don't have DBA's looking at individual databases on a daily basis.DBA should not do this stupid task.
The answer is - MONITORING
A good proactive tablespace management policy should be based on forecasting. Follow the links below to my presentation about tablespace forecasting with Oracle EM.
Autoextend is a great feature, but it requires some planning - http://wp.me/p1DHW2-37
Thanks, Iordan. We actually do use EM repository information to "predict" tablespace growth and forecast it out. However, DBA's still need to take time out of their day to add the space.
My ultimate goal is to not have DBA's add space entirely (or close to it) freeing them up to focus on performance tuning and other more exciting DBA tasks. As I stated, we have thousands of databases and our business is growing rapidly which means our databases are also growing rapidly.
I'm looking for a way to have a more "intelligent autoextend". With autoextend, the database engine won't take action until there is space pressure (ie. 99%). I'm looking for something when it crosses a defined thershold (ie. 85%).What will be a benefit of such "intelligent autoextend"? What is a difference if a data file extended being 85% full versus 99% full?
From Application perspective there is no difference, it got the space for data in any case.
My ultimate goal is to not have DBA's add space entirely (or close to it)why the "out of box" autoextend does not work for you?
Just specify MAXSIZE according to your storage and DBA do not need to add space entirely. Until disk is full.
But. If you really do need some "intelligent autoextend" you (or your DBA) can write a PL/SQL script that can use any level of intelligence you put in its logic. It can forecast, extend datafiles, add datafiles, shrink them, even check disk space and send email about it.
Writing this script will be that "more exciting DBA task" ;)