Database Monitoring and Administration Using the DBA Cockpit
The DBA Cockpit provides a new access to monitoring and administration of DB2 UDB for UNIX and Windows.
You can start the DBA Cockpit by either calling transaction DB6COCKPIT or any of the transactions listed below.
There is a navigation frame that appears on each CCMS screen for DB2 UDB for UNIX and Windows. This frame contains a tree structure with the main task areas of database administration:
Performance ST04
Space DB02
Backup and Recovery DB12
Configuration DB03
Jobs DB13, DB24
Alerts DB16, DB17
Diagnostics DB6COCKPIT
Incompatibilities and Affected Functions
If you use the new CCMS transactions without having the appropriate
executables installed, the following problems may occur:
o Some actions that are completely new will not work properly as they
are based on new functions provided by the underlying monitoring
programs.
o Some actions that have replaced old functions will show no or
misleading results because of incompatible changes in the underlying
monitoring programs.
If you use a 4.6D kernel, the following actions are affected:
o Performance - Lockwaits
The results can only be displayed as a table. If you select the
layout graph, an error occurs.
o Performance - History - Database
Old history records that were collected before the new DBA Cockpit
was installed are no longer displayed.
o Space - History
Old history records that were collected before the new DBA Cockpit
was installed are no longer displayed.
o Backup and Recovery - Backup Overview (DB12)
For monitoring, no data is available.
o Backup and Recovery - Logging Parameters
The log archive directory is not readable and cannot be displayed.
o Configuration - Database Manager
The field Maximum Requester I/O Block Size is not displayed
correctly.
o Configuration - Database
The field Collate Sequence Type is not provided with any content.
o Configuration - Parameter Changes
Old change records that were collected before the new DBA Cockpit
was installed are no longer displayed.
o Configuration - CLP Commands
The function CLI configuration does not work.
o Jobs - DBA Planning Calendar (DB13)
You cannot switch the planning mode from local to global. The latter
is a 6.10-related function that needs the central 6.10 planning
calendar.
The new action Check Tables for Statistics Update is a prerequisite
for the action RUNSTATS and REORGCHK (DBSTATC). You need to schedule
it separately.
Actions that use old executables (dmdb6bkp, dmdb6srp) do not set
return codes correctly for the planning calendar. Therefore the
colors that indicate the status of an action are not reliable.
If you use a 4.6C kernel, there are further actions affected:
o Performance - Deadlocks
Function aborts with error message
o Backup and Recovery - Logging Parameters
The log directory is not readable and cannot be displayed
o Configuration - CLP Commands
None of the functions is available
o Configuration - File Systems
Function aborts with error message
o Diagnostics - System Check
Function aborts with error message
o Diagnostics - Database Alert Log
Function aborts with error message
o Diagnostics - Database Diag Log
Function aborts with error message
o Diagnostics - Dump Directory
Function aborts with error message
o Diagnostics - Kernel Executables
Function aborts with error message
Necessary Post-Processing Activities
For full availability of the DBA Cockpit you need to install patches for the following programs:
o dmdb6rdi patch level 7
o dmdb6srp patch level 4
o db6clp patch level 1
o dmdb6bkp patch level 3
o dmdb6rts patch level 3
o db6util patch level 7
o db6pmudf patch level 3
If there are higher patch levels available, use always the latest one.
Note: We strongly recommend that you do not to use a 4.6B kernel.
Install a 4.6D kernel instead.
Documentation
For detailed information, see the documentation on sapserv(x) in directory
.
For up-to-date information about the DBA Cockpit and the prerequistes
for monitoring systems with different SAP releases, see SAP Note 300828.