Long running DDL Report (Summary)
Article ID: 236699
Updated On:
Products
Issue/Introduction
Running a Log Analyzer DDL Report Summary.
The job only looks at 1 minute of DB2 Log;
Typically the minute that covers the "Create Required DB2 Objects" job .
The job ended up having to be cancelled after nearly half an hour, what reason would there
be for the job running for so long?
Environment
Release : 20.0
Component : Log Analyzer for DB2 for z/OS
Resolution
1) Specify PURSRC = (AUTO) in the control cards. This allows the program to choose the more effective way to reconstruct partial updates.
2) Alter the catalog tables to DATA CAPTURE CHANGES to prevent the need for the reconstruction process completely.
Especially if all the DDL activity is concentrated into one minute of log data this can be very effective.
Alternatively take more frequent full image copies of catalog tablespaces.
3) Switch the SHRLEVEL parmlib parameter to (U). Assuming SHRLEVEL CHANGE copies are taken this can reduce a need for reading older logs.
4) There is a PTF LU01385 which improved performance of DDL reporting in general.
Feedback
