This list of procedures should be performed on a daily basis to check the status of your Oracle databases:
For Unix: at the command line, type:
ps –ef | grep dbsnmp
There should be two dbsnmp processes running. If not, restart DBSNMP.
For each instance, make sure that enough free space exists in each tablespace to handle the day's expected growth. When incoming data is stable and the average daily growth can be calculated, your minimum free space should at least equal the amount of data growth you expect during the time it will take to order, receive, and install additional disks.
Verify rollback segment.
Identify bad growth projections.
Look for segments in the database that are running out of resources (e.g., extents) or growing at an excessive rate. You may need to adjust the storage parameters of these segments. For example, if any object has reached 200 as the number of current extents, upgrade the MAX_EXTENTS parameter in the INIT.ORA file to a value of UNLIMITED.
Space-bound objects' next_extents are bigger than the largest extent that the tablespace can offer. Space-bound objects can harm database performance. If we get such objects, we first need to investigate the situation. Then we can use ALTER TABLESPACE <tablespace> COALESCE. Or add another datafile.
Run spacebound.sql. If all is well, zero rows will be returned.
Be sure to review contention for CPU, memory, network, and disk resources.