DB2 best practices for basic design, performance, and manageability
Recommended reading list: DB2 for Linux, UNIX, and Windows database administration
While databases are becoming more and more self-aware and self-healing, they still require some monitoring to keep them running as efficiently as possible. Just like your car, a database requires some checks to keep it running optimally. This document is broken down into tasks or checks that you can run at different time intervals to ensure that your DB2 databases are running optimally, and detect potential issues before they happen.
The first set of checks or tasks should be run every day to make sure there are no current or imminent problems. The second set should be run weekly to check for issues or problems that may have occurred during the week or are likely to occur in the coming week. The final set of checks or tasks need not be run every day or week, but should be run monthly to keep the system running without problems, and to prevent further issues in the event that a problem does occur.