Resolving fragmentation exceptions for HISAM and SHISAM databases
Resolve the fragmentation exceptions that you received for your HISAM and SHISAM databases.
Before you begin
Ensure that you have completed the analysis steps for HISAM and SHISAM exceptions and that you have identified the possible causes of the database exceptions. If you have not yet analyzed the fragmentation exceptions, see Analyzing fragmentation exceptions for HISAM and SHISAM databases.
Procedure
If the only the exception that you received for fragmentation is
EXCESSIVE_CI_OR_CA_SPLITS, and if you observe no performance degradation in IMS applications that use the database, you can ignore this exception.
If you observe performance degradation, you can resolve this exception by removing the CI splits and CA splits by reorganizing the database.
If you received other exceptions, which can be EXCESSIVE_HISAM_DELETE_SEGM and FRAGMENTED_FREE_SPACE, reorganize the database.