Scenario for using the analysis and resolution topics

If you receive exceptions from Autonomics Director, you should analyze the state of the database and, if necessary, change the database configuration or tune the database.

The following figure shows an overview of the major steps to analyze and resolve exceptions. The organization of the topics in Analyzing and tuning IMS full-function databases correspond to the steps of this scenario.

This figure illustrates overview of the major steps to analyze and resolve exceptions for full-function databases. Detail of the figure is described in this topic. — Figure 1. Overview of the major steps to analyze and resolve exceptions (full-function databases)

The following steps correspond to the flow that is presented in the previous figure:

If you received space use exceptions, see Analyzing space use exceptions for all full-function database types and analyze the space use exceptions.
If you do not resolve space use exceptions that alert you about insufficient free space, database data sets can cause out-of-space conditions where new segments cannot be added. This situation might give negative impact to the IMS applications that use the database.
If you determine that immediate actions are required to improve the space utilization status, see the following topics and determine the actions to resolve the condition:
If you determine that space utilization does not require immediate action, analyze fragmentation exceptions next, followed by optimization exceptions to understand the overall status of the database. A good understanding of the status helps you determine the best approach to resolve the exceptions. Then you should determine how you will resolve the exceptions based on your maintenance schedule.
1. If you received fragmentation exceptions, analyze the fragmentation exceptions.
  The fragmentation exceptions can cause redundant space and performance degradation that might be caused by excessive database I/Os.
  See the following topics to analyze the fragmentation exceptions:
  After you have analyzed the fragmentation exceptions, see the following topics to determine the actions to resolve the condition:
2. If you received optimization exceptions, analyze the optimization exceptions.
  Optimization exceptions also can cause performance degradation. Performance degradation might be caused by excessive database I/Os when database record and root segment randomizing are not optimized.
  See the following topics to analyze the optimization exceptions:
  Optimization exceptions typically cannot be resolved by a simple reorganization. Resolving optimization exceptions involves database tuning by changing the database definitions and other factors.
  
  You can find guidelines for optimization tuning in the following topics:
If you receive both fragmentation and optimization exceptions, consider working on the fragmentation exceptions first. Working on fragmentation exceptions before optimization exceptions will help you simplify your optimization tuning steps.
When you complete working on the exceptions, run DB Sensor to generate a Sensor Data Statistics report to confirm that the exceptions are resolved or that the status of the database has improved.

The scenario in this topic is an example of the flow for working on exceptions. Use this scenario as a starting point to develop your own approach that is best suited for your particular environment.