Here are some examples of where XM4DB2 detects and signals severe problems. A load utility puts a tablespace into a “RECP” state and abends leaving the table space in a very undesired restricted state. The consequence is a plan or a package (an application) will fail. XM4DB2 immediately alerts the responsible DBA and can take corrective actions. It links the required information and presents the “whole story”, the utility that failed, the affected objects and the afflicted application.
XM4DB2 not only detects problems but first and foremost it anticipates any upcoming problems. XM4DB2 reports timely an impending space shortage for table or index spaces. Another example is in the area of recoverability. XM checks image-copies (the underlying datasets) and calculates the recovery time to ensure that service levels are satisfied.
DBAs will receive a message if XM4DB2 calculates that the expected time to recover is longer than allowed under service levels agreements. A decrease in IO performance can become an ugly problem in peak load times. XM4DB2 continuously monitors the IO behavior and bufferpool performance. It detects problems and tuning opportunities and signals any critical developments.
XM4DB2 interfaces with the BPA4DB2 graphical workstation giving in-depth analysis and tuning guidance. XM4DB2 maintains and displays a table of current exceptions across the DB2 subsystems and enterprise wide. Each event is highlighted only once – the entry disappears when the problem is fi xed. On urgent matters, the system notifi es the database and system administrators. There is a function with the option to auto matically resolve “standard” issues.Some of the exceptions that are continuously checked include:
- Objects in an unexpected restricted state and all its affected plans/packages
- Foreseeable lack of space of objects whether attributable to z/OS, ICF or DB2
- Unrecoverable tablespaces due to missing image-copies
- Possible infringement of SLAs with regard to recovery time
- Missing Archived Logs; inconsistency with BSDS
- Stopped Procedures e.g. REJECT or QUEUE with queue length reached
- Stopped Utilities and affected objects
- In-doubt Threads and related system implications
- DDF status with regard to connections and threads
- Plans/packages that are invalid or inoperative or impacted by other failures
- Buffer pool related problems, e.g. avoidable re-reads, thresholds hit, etc.
DB2 systems continuously change. Activities invoke DB2 messages with information on events, warnings about restrictions and error messages on probable pitfalls. A dedicated effort is necessary to view and extract from the flood of messages those which are relevant. Simply scanning for particular messages or analyzing the output of display commands is not enough. Early recognition of costly disruptions requires that the DBA evaluate different sources of infor mation and reach timely conclu sions. An automated and proactive supervision prevents emer gen cies and ensures continuous database availability.
Multiple monitoring programs for DB2 and z/OS deliver great raw statistics. Unfortunately, they all lack the ability to intelligently review the observations to determine when a true exception or error situation is about to happen. The primary purpose of these monitoring tools is to make data available to the experts analyzing DB2 system failures. The UBS approach is to keep avoidable problems from impacting the company in the fi rst place by automatically tracking suspicious and potentially harmful events in real time.
XM4DB2 is for Operations and Production DBA staff. It delivers a timely pro-active status update of the DB2 systems to improve and guarantee availability of all objects to their dependent applications.
XM4DB2 offers predefi ned best practices solutions and also supports customized exception defi nitions. An exception that repeatedly leads to a particular error, and seems in the short term to be unavoidable, should receive a standard treatment. XM4DB2 offers prepared jobs for repair and other functions. These jobs can be checked, edited and released by the staff or submitted to a scheduler for execution.
XM4DB2 is designed to easily accept new defined actions. Defi ned actions or a described set of events are treated as an exception. They are continuously tracked and generate alerts.
There are hundreds of messages and warnings on over 30+ possible restricted states. With just two DB2 systems using potentially thousands of tablespaces it is near impos sible to manually observe and detect problems, with 10 or say 100 subsystems it’s defi nitely in the realm of the impossible.
It requires a dedicated program to unerringly fi nd the events within DB2 and z/OS that are causing problems. With the naked eye it’s impossible to see what is going on and to gauge possible consequences. XM4DB2 tackles the non-stop supervision of the DB2 environment with its unique func tionality and technology. Beyond saving time, effort and staff resources, it helps to keep mission critical applications running smoothly. How much does each minute of DB2 downtime cost your organization?
- Delivers smart analysis and recommendations for problem avoidance
- Reduces operational risks
- Increased productivity across the business
- Pro-active surveillance of each DB2 system
- Reduces manual efforts and keystroke errors through automation
- Fills the void in System Management tools market and IT Services
- Reduces denial of access on production databases
- Ensures non-stop operations