Re: Quick Tale: Lost production database because of keyboard and Veritas Cluster Server

milkfilk wrote:

> "Viper" <viper_at_2ghz.net> wrote in message news:<u7rcbilsmt3pbf_at_corp.supernews.com>...
>

>>Well I guess the first question is what Type of database are you useing? If
>>

you're much more likely to hit a bug on a x.x.x.0.0 release than on something current, like 8.1.7.2.7. If you have the slightest problem, the oracle analyst will like utter the mantra: "upgrade to the current patch set".
I'm not saying to "upgrade for the sake of upgrading", but if you read the release notes for the patch sets made available, there's a fair number of bugs out there.

I suggest a couple of documents to get you squared away with what needs to be in place prior to putting a database into production.

Tom Cox's DBA checklist
http://www.geocities.com/tbcox23/dba_checklist15.doc

it was incorporated into an O'Reilly mini-book with the help of several other authors:
http://www.oreilly.com/catalog/ordbacheck/

A good way to check your backup/recovery ability is to clone your prod db over to a test db, apply redo and open it. run some queries, see that it doesn't complain about invalid objects, data not available, etc.

There's papers up on metalink that are version/platform specific as to howto clone a db from one ORACLE_SID to another.

you can do the same thing by using the hot backup set as a source for a standby database on another machine. just open it read only for verifying that everything is okay - no need to activate it.

hth,

Paul Received on Thu Feb 28 2002 - 22:40:11 CST