Taking over from another DBA: What should I want to know?

[p***@hotmail.com]

Hi all,
I am due to take over DBA functions for a DB2 UDB LUW. I am
meeting with the outgoing DBA soon and I thought I should ask
this vast base of kowledgeable practitioners what are the
questions they would want to ask the outgoing DBA if they were
in my shoes. There is not much documentation on shop practices
and procedures, type of or critical applications running (every
thing is in everyones head), what to watch out for, etc.

Please share with me your thoughts and examples how you might go
about getting as much information from and covering major areas
of managing a UDB environment...

Thanks

[c***@hotmail.com]

For me...

I will ask for:
1. Data Dictionary.
2. DFD.
3. Any existing issues. (Outstanding issue).
4. Common issues...

Hope this help....

[p***@hotmail.com]

Hello again,

Thanks for the good suggestion...

[Blair Kenneth Adamache]

Post by p***@hotmail.com
Hi all,
I am due to take over DBA functions for a DB2 UDB LUW. I am
meeting with the outgoing DBA soon and I thought I should ask
this vast base of kowledgeable practitioners what are the
questions they would want to ask the outgoing DBA if they were
in my shoes. There is not much documentation on shop practices
and procedures, type of or critical applications running (every
thing is in everyones head), what to watch out for, etc.
Please share with me your thoughts and examples how you might go
about getting as much information from and covering major areas
of managing a UDB environment...
Thanks

Ensure you get all the scripts that created the database(s) and all
objects in it. While you can extract much of this from the database with
db2look -e, in a well run shop, all of these commands should be saved in
scripts (in a production database, it is bad form to create objects
interactively).