Essential DB2 Health Check

You have more and more growing databases and Db2 systems to administer, but no additional help to get your work done? This is the normal case these days, but the good news is that there are ways to automate many of the necessary tasks to monitor and to control your Db2 systems and databases.

Enterprises want their application systems to be highly available and to perform well on an ongoing basis, but verifying the health of their systems seems a daunting task. On occasion, certain non-availability of applications can remain undetected. Sometimes problems develop over long periods of time, noticing trends and their timely detection would simplify resolution and avoid downtime. Performance degradation normally evolves slowly, adverse effects on users can be easily avoided, provided the first signs are recognized and countermeasures are taken early enough. New challenges continue, for example the growing flood of dynamic SQL. Automatic surveillance and assessment of the Dynamic Statement Cache can produce relief.

Normally your clients do not ask why the application failed, it just failed and it should not have. It doesn’t matter whether a tablespace became full or entered a restricted state, or whether a thread or procedure failed, or the system came to hold due to log offload difficulties, or a sharing group went down because the SCA was full. There are many error sources and as many suggested workarounds. Much better than a conglomeration of various scripts and procedures is a new unified and integrated approach. It is not enough to receive a list of the current restricted states, truly valuable information is provided only when the restricted states are immediately related with current utility executions or other system wide events.

A tool based implementation of continuous measurement and analysis helps to avoid the most frequently occurring problems in daily operations. Archived problem data also supports problem analysis, “Did this problem occur ever before and how was it solved?” A data warehouse of problem descriptions of all the problems that occurred in the past simply shows the common, most frequent issues for which general provisions can be made and automatically applied. An elegant solution offers its findings on what happened as a set of parameters for immediate deployment of counter measures: Copy Pending – copy it, problem with a thread, restart it, etc.

A big advantage of a unified solution is in the field of messages and warnings. Too many messages and warnings are annoying, elusive, or ignored. Only serious issues should be reported, and they should only be reported once. A solved problem should automatically vanish from the screen and enter the data warehouse of past problems.

What can be automatically monitored and analyzed by an appropriate tool? In principle everything, a tool I have in mind should detect conceivable lack of space, ensure timely recoverability according SLAs, monitor BSDS/log activities, check the quality of dynamic SQL statements, monitor and assess I/O performance and buffer pools, monitor threads, DDF, plans, packages, objects in restricted state and utility executions, SCA structures, group buffer pools, just to mention a few. Do you want to know what tool I am thinking of…. See XM4Db2™.