Troubleshooting Guide

Chapter 2. Troubleshooting the DB2 Universal Database Server

This chapter presents troubleshooting tips for the database administrator of DB2 Universal Database products:

• IBM DB2 Universal Database Workgroup Edition

• IBM DB2 Universal Database Enterprise Edition

• IBM DB2 Universal Database Extended Enterprise Edition (see also Chapter 6. "Troubleshooting DB2 Universal Database Extended Enterprise Edition")

For more information on administering databases, see:

• The Quick Beginnings guides for information on setting up and migrating databases

• The DB2 Extended Enterprise Edition Quick Beginnings guide for information on setting up Extended Enterprise Edition

• The Administration Guide for detailed information on database administration

• The Administration Getting Started for a high-level overview of database administration

• The System Monitor Guide and Reference for information on monitoring databases

• The Command Reference for information on DB2 commands

• The API Reference for the API syntax to call utilities from a program

It is beyond the scope of this book to cover all aspects of problem determination on a DB2 server. See the information in the DB2 library (especially the Administration Guide) to find out more about operations required of DB2 administrators. Typical operations include:

• Migrating a database from a previous version
• Designing the physical and logical characteristics of a database
• Day-to-day operations, such as backing up data
• Authorizing users to use the database
• Importing, exporting, and loading data
• Tuning the database manager for optimal application and operational performance

The following list provides some basic troubleshooting rules that you should follow:

[  ]

Spend time designing a logical database that meets your requirements, and a physical database that will be adequate for future demands. Use SMS or DMS table spaces as appropriate.

[  ]

Always ensure that you have a backup/recovery plan. If you encounter serious problems, you may need a backup to restore your database and perhaps roll it forward.

[  ]

User-defined functions and stored procedures should be fenced, unless performance is critical and they have been thoroughly tested and debugged.

[  ]

To ensure optimal performance of your database, regularly run utilities such as reorgchk, reorg, and runstats. (See "Improving Database Performance".)

[  ]

Consult the db2diag.log file if you suspect problems, and remember to prune this file occasionally when it gets too big. (See "Interpreting the db2diag.log File".)

[ DB2 List of Books | Search the DB2 Books ]