Re: Person leaving company

Funny. On the Backup and Recovery course, there's a slide about 'disaster recovery', and it mentions fire, flood, earthquake, meteorite strikes (OK, I made that last one up) ..... and loss of key personnel (and no, I *didn't* make that one up).

There's not much you can do about earthquakes, but the answer to the last one comes in three parts: documentation, documentation and documentation.

So your question to your departing DBA is really easy: where's the documentation? And if he hasn't got any, then he hasn't done his job. Which doesn't make yours any easier, I agree.

I guess if he can't supply you with good documentation, I'd be tempted to ask what his policies on backup and recovery have been, what tablespace management strategies he's employed (is everything on autoextend for example), what roles has he employed for security issues, and what scripts has he used for automating any tasks. There's heaps more, but if you only have a few days....

Regards
HJR

--
--------------------------------------------------------------------------
Opinions expressed are my own, and not those of Oracle Corporation
Oracle DBA Resources:               http://www.geocities.com/howardjr2000
--------------------------------------------------------------------------



"DBA in Training" <user_at_home.net> wrote in message
news:39bd66e9.7393285_at_news.mindspring.com...


> Primary DBA is leaving the company.  We have a few days left to pick

> his brain.  Those of us reamaining to support the databases are all

> newly trained DBA's fresh out of "Oracle University".  What questions

> should we ask of the departing DBA???