StorageTek Lifecycle Director DB2 Manager 312564001 User Manual
DB2 Manager User Guide
109
StorageTek
Proprietary
Figure 5: Detailed table analysis report
Condition codes
The table analysis utility will set a condition code on completion. This code
may take the following values:
may take the following values:
0 - the utility has been executed successfully.
4 - a warning condition has been encountered during processing of the
utility. A warning message will have been written to the SYSPRINT
dataset. The utility has been executed successfully.
dataset. The utility has been executed successfully.
8 - an error condition has been encountered during processing of the
utility. An error message will have been written to the SYSPRINT
dataset. Execution of the utility has continued.
dataset. Execution of the utility has continued.
12 - a serious error has been encountered during processing of the
utility. An error message will have been written to the SYSPRINT
dataset. Execution of the utility has been terminated.
dataset. Execution of the utility has been terminated.
Utility failure and restart considerations
If the table analysis utility fails to complete successfully (return code greater
than 8), consult the error report in the SYSPRINT dataset to identify the
cause of the problem. Refer to chapter 7 for a description of the message(s)
appearing in the error report.
than 8), consult the error report in the SYSPRINT dataset to identify the
cause of the problem. Refer to chapter 7 for a description of the message(s)
appearing in the error report.
After correcting the error, the utility may be rerun normally. The utility will
start analysis processing from the beginning of the table once again. No
special actions need to be taken prior to re-starting the failed table analysis
job.
start analysis processing from the beginning of the table once again. No
special actions need to be taken prior to re-starting the failed table analysis
job.
OTDBP170 - the database housekeeping utility
OTDBP170 is the DB2 Manager database housekeeping utility program.
The program is executed as a batch job in order to scan a DB2 table and
identify Archive Manager objects which no longer contain any active migrated
rows. These objects will be deleted from the Archive Manager database
used for storage of objects migrated from the DB2 table being processed by
the utility. Migrated rows are deleted from an Archive Manager object in
response to SQL UPDATE or DELETE commands issued by an application
program, or by selection for processing by the DB2 Manager row restore
utility.
The program is executed as a batch job in order to scan a DB2 table and
identify Archive Manager objects which no longer contain any active migrated
rows. These objects will be deleted from the Archive Manager database
used for storage of objects migrated from the DB2 table being processed by
the utility. Migrated rows are deleted from an Archive Manager object in
response to SQL UPDATE or DELETE commands issued by an application
program, or by selection for processing by the DB2 Manager row restore
utility.
The program will also “normalize” the storage of migrated rows in the DB2
table, if required, by ensuring that the stubs for migrated rows are only stored
in the archive partition of the tablespace used for storage of the table, and
that non-migrated rows are stored in one of the non-archive partitions of the
tablespace. Any inconsistencies with the storage of migrated and non-
table, if required, by ensuring that the stubs for migrated rows are only stored
in the archive partition of the tablespace used for storage of the table, and
that non-migrated rows are stored in one of the non-archive partitions of the
tablespace. Any inconsistencies with the storage of migrated and non-