Analyzing fragmentation exceptions for index databases
Analyze the fragmentation exceptions that were detected for index databases.
Before you begin
Ensure that you can access the Sensor Data Statistics report that contains the latest sensor data. If you cannot access this report, run the FF DB Sensor Printing utility to generate the report.
About this task
In the following procedure, you will analyze the fragmentation exception that you received for HIDAM primary indexes, secondary indexes, or HALDB partitioned secondary indexes.
The only fragmentation exception for index databases is EXCESSIVE_INDEX_CI_OR_CA_SPLITS. You will identify the relevant data elements to understand the condition of the index database.
By completing this task, you will identify the type of fragmentation symptoms that occurred and the index data set for which the exception was reported.
Procedure
- Exception class name: EXCESSIVE_INDEX_CI_OR_CA_SPLITS
- This exception applies to VSAM KSDSs such as HIDAM primary index databases, the primary data set of secondary index databases, and partitioned secondary index databases. This exception does not apply to VSAM ESDSs such as the overflow data set of secondary index databases.
What to do next
If EXCESSIVE_INDEX_CI_OR_CA_SPLITS is the only exceptions that you received, Resolving fragmentation exceptions for index databases.