Mistake #9: Not keeping an eye on database space allocation
What happens when you run out of space?
If you run out of space between you car and the car in front of you, the two cars will crash into each other. If you come home with a bag of groceries and find that you have run out of space in your pantry, you’ll have to dig out those old cans of soup from three years ago, consolidate those seven partially full boxes of Ziploc bags, and decide if you’ll ever actually use that box of seaweed soup mix. Running out of space is no fun. If you proactively manage the various space allotments in your life, you will have fewer unhappy surprises.
The same is true with your database. When key areas of your database or their associated external storage allocations fill, you can suffer from failed transactions, database outages or hangs, and lost logging information. Many space problems accumulate gradually and could have been prevented by early intervention.
Are you watching your database for tablespace full conditions, nonextendable segments, and nonextendable datafiles? Are you properly managing your alert log, trace files, and archived redo logs? Are you watching your file systems/drives for near-full conditions? Have you configured your datafiles not to try extend to a size larger than your file system/drives can accommodate?
Do you know how to do these things? Contact us if we can help.