7 Deadly Sins Of Oracle Database Management (Sin 1)

After my last post, I thought about it and I have decided to create a series of 7 Posts for Oracle Databases and 7 posts for Microsoft SQL Server Databases. Where I will identify the 7 things that we see far to often and represent very bad practices in database administration. This is the Oracle version of that.

The first and most deadly sin concerns the Database Backups. Just like in Microsoft SQL Server Database Administration this is a major Problem in Oracle Database Administration. Given the number one job of the database administrator is the protection of the Data, I am surprised how often we find problems with database backups. When we look under the covers of Oracle databases just like with Microsoft SQL Server databases, we fine far too many of the databases that are not being backed up properly.

See my previous post titled “Have your fire drilled your Oracle or Microsoft SQL server backup posted on December 18th, 2007 about the important of fire drills. If you don’t test your backup, then experience has taught me it won’t work when you really need it.

With an Oracle database you have lots of options on how to backup the database. Exports, many flavors of cold and hot backups. I am a firm believer as long as you have the disk space, you should implement hot backups. Given how cheap disk space is today, that should not be a problem. If my memory serves me right its officially called archive log mode backup. Simply means you can back up the database as its being used. That is why it is more commonly called a hot backup. In the event of a failure you can recover the database to just before the problem happened. It’s really nice to be able to recover your database to 12:01 when you accidentally deleted a table you needed at 12:02 and not loose a days work.

Oracle Database Management Deadly Sin 1: Poor or Untested Database Backups

Take full advantage of the many options you have when backing up an Oracle database, I strongly encourage hot backups (Archive log mode backup). Make sure that your database backup is tested. What I mean by tested, is that you run a fire drill and actually physically recover something.

Posted by Michael Corey, Ntirety

www.ntirety.com

View blog top tags

Add to Technorati Favorites

Leave a Reply