CA Log Analyzer for DB2 for z/os

Transcription

1 CA Log Analyzer for DB2 for z/os User Guide Version , Third Edition

2 This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the Documentation ) is for your informational purposes only and is subject to change or withdrawal by CA at any time. This Documentation is proprietary information of CA and may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. If you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy. The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION AS IS WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE. The use of any software product referenced in the Documentation is governed by the applicable license agreement and such license agreement is not modified in any way by the terms of this notice. The manufacturer of this Documentation is CA. Provided with Restricted Rights. Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections , , and (c)(1) - (2) and DFARS Section (b)(3), as applicable, or their successors. Copyright 2013 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

3 CA Technologies Product References This document references the following CA Technologies products: CA InfoTransport (CA InfoTransport) CA Fast Load for DB2 for z/os (CA Fast Load) CA Fast Recover for DB2 for z/os (CA Fast Recover) CA Log Analyzer for DB2 for z/os (CA Log Analyzer) CA SYSVIEW Performance Management (CA SYSVIEW PM) Contact CA Technologies Contact CA Support For your convenience, CA Technologies provides one site where you can access the information that you need for your Home Office, Small Business, and Enterprise CA Technologies products. At you can access the following resources: Online and telephone contact information for technical assistance and customer services Information about user communities and forums Product and documentation downloads CA Support policies and guidelines Other helpful resources appropriate for your product Providing Feedback About Product Documentation If you have comments or questions about CA Technologies product documentation, you can send a message to techpubs@ca.com. To provide feedback about CA Technologies product documentation, complete our short customer survey which is available on the CA Support website at

4 Documentation Changes The following documentation updates have been made with the third edition of this documentation: Audit Table Requirements (see page 73) Added the following colums that hold extended values: PLA_EXTENDED_URID, PLA_EXTENDED_LOGRBA, and PLA_EXTENDED_LOGLRSN. The following documentation updates have been made with the second edition of this documentation: Support a Subsystem After Converting to Extended Logging (see page 17) Added this topic. Customize the DML and DDL Report Forms (see page 20) Added instructions for specifying the Extended Values field. Noted that the inclusion of LOB column data is optional in the following topics: Generate the Load Output Files (see page 78) Generate the Load Output Files (see page 83) Generate the Load Output Files (see page 111) Generate UNDO or REDO SQL Statements (see page 117) The following documentation updates have been made since the last release of this documentation: XML Support Limitations (see page 24) Added this topic. Select Key Columns (see page 60) Added the new U (Unique) option on the Index List panel. Specify Related Updates Options (see page 65) Added DB2 history table updates. Column Data Formats (see page 71) Updated the TIMESTAMP data type to indicate additional precision support. Added TIMESTAMP WITH TIME ZONE. INTO TABLE Statement (see page 92) Added TIMESTAMP WITH TIME ZONE. REDO SQL and History Table Updates (see page 116) Added this topic. DDL Activity Object Report (see page 152) Added a description of this new report option. How to Audit Which Objects Have Changed (see page 152) Added this scenario. Control Statement Listing Added the OBJECT option to the DDLREPT statement. DDLREPT Control Statement Added the OBJECT option to the LEVEL parameter.

5 Contents Chapter 1: Introduction 13 General Overview Chapter 2: Operational Considerations 15 Product Authorization EXECUTE Plan Security BSDS Security Access to DB2 Data Sets Access to DB2 Table Data Support a Subsystem After Converting to Extended Logging Valid Processing Dates Set Profile Variables Customize the DML and DDL Report Forms Sort Processing Syncsort Users Specify a DDname for Syncsort SORTPARM in the JCL Stream Modify the JES3 Initialization Parameters Support a Subsystem After an RBA Reset Data Sharing Groups with Quiesced Members DB2 10 Support Limitations LOB Support Limitations XML Support Concurrent Copy Support Chapter 3: Process Log Facility 27 Process Log Overview Processing Flow Access the Process Log Facility Access the Report Source Specifications Panel Specify an Alternate Image Copy Source Select Members of a Data Sharing Group Specify Alternate Log Data Specify Alternate Table Definitions Output Specifications Panel Specify File Allocation Parameters Contents 5

6 Report Submission Panel Submit the Report Online Submit the Report in Batch Mode Chapter 4: DML Activity Options 45 DML Activity Output Types Specify the DML Activity Options Format Options How to Select the Level of Detail Log Data Filter Options Select Objects From a List Enter Table Names Manually Filter Data by Log Statement Link Filters Using the Join Operator Refine a Filter by Using a Query Miscellaneous Options Report Discards Request a Subsequent Update Report Select Key Columns Set the Load Options Specify Related Updates Options Chapter 5: Load Files and Log Apply 67 Load File Overview Load File Output Files Load File Fields Column Data Formats Audit Table Requirements How to Update a Table in a Data Warehouse Set the Load Utility Control Statement Options Generate the Load Output Files Apply the Load Output Files to the Data Warehouse Table How to Propagate Table Data to a Non-z/OS Database Set the Load Utility Control Statement Options Generate the Load Output Files Create the CA InfoTransport Strategy Create a JCL Job for the Strategy Execute the JCL Job Log Apply Overview Log Apply Control Statements Log Apply Performance Considerations User Guide

7 How Restart Processing Works With Log Apply How to Replicate Table Changes Using Log Apply Set the Load Utility Control Statement Options Generate the Load Output Files Apply the Load Output Files to the Production Table Chapter 6: Generating SQL 115 SQL Generation Use of DATA CAPTURE CHANGES UNDO SQL for Unqualified Deletes REDO SQL and Referential Integrity REDO SQL and History Table Updates DELETE and UPDATE Statements in SQL LOB Columns and SQL Generation Generate UNDO or REDO SQL Statements Chapter 7: Generating DML Activity Reports 119 Generate a DML Activity Report Common DML Activity Report Sections DML Activity Summary Report Description DML Activity Totals Report Description DML Activity Detail Report Description DML Activity Image Copy Detail Report Description DML Activity Key Detail Report Description DML Activity Update Report Description DML Activity Subsequent Update Report Description Chapter 8: Generating Commit Frequency Reports 127 Generate a Commit Frequency Report Commit Frequency Report Description Chapter 9: Generating Image Copy Frequency Reports 131 Generate an Image Copy Frequency Report Image Copy Frequency Report Description How Extrapolated Changes are Calculated Chapter 10: Generating Rollback Activity Reports 139 Generate a Rollback Activity Report Rollback Activity Report Description Contents 7

8 Chapter 11: Generating Recovery Point Analysis Reports 143 Generate a Recovery Point Analysis Report Recovery Point Analysis Report Description Chapter 12: Generating DDL Activity Reports 147 Generate a DDL Activity Report Common DDL Activity Report Sections DDL Activity Summary Report Description DDL Activity Totals Report Description DDL Activity Detail Report Description DDL Activity Object Report Description How to Audit Which Objects Have Changed Create a Strategy for a DDL Activity Object Report Test the Strategy Add the Strategy to a Job Scheduler Chapter 13: DDL Activity Options 157 DDL Activity Output Types Specify the DDL Activity Options Format Options Log Data Filter Options Select Objects From a List Enter Object Names Manually Link Filters Using the Join Operator Refine a Filter by Using a Query Miscellaneous Options Chapter 14: Generating DDL 163 Generate UNDO or REDO DDL Statements Chapter 15: Generating Change Data Capture Analysis Reports 165 Generate a CDC Analysis Report How to Interpret and Use CDC Analysis Reports How the Full Log Length is Calculated Common CDC Activity Report Sections CDC Analysis Summary Report Description CDC Analysis Detail Report Description User Guide

9 Chapter 16: Strategy Services 173 Strategy Overview Create or Update a Strategy Update the Resume Point Execute a Strategy View the Strategy Output Files Copy a Strategy to Another Subsystem Chapter 17: DDL File Mapping 179 DDL File Mapping Overview File Maps and Versioned Tables File Maps and Clone Tables File Maps and Materialized Query Tables File Maps and Tables With LOB Columns DDL File Requirements How to Propagate Changes When the Tables Have Different Names Map the Target Table to the Source Table Generate REDO SQL Update the Target Table How to Propagate Changes to Selected Columns Map the Source Table DDL Edit the Source DDL to Point to the Target Table Generate REDO SQL for the Selected Columns Update the Target Table Chapter 18: Using an Alternate Image Copy Source 195 Alternate Image Copy Overview Create or Update an Image Copy Map Create or Update an Image Copy Group Use an Image Copy Map How to Report Table Activity When SYSCOPY Rows are Missing Locate the Image Copy Information Create Image Copy Maps Use the Maps to Generate an Activity Report Chapter 19: List Log Inventory 205 Chapter 20: Generating Image Copy Status Reports 207 Generate an Image Copy Status Report Contents 9

10 How the Number of Available Image Copies is Determined Image Copy Status Report Description Chapter 21: SMF Audit Trace Reporting 211 SMF Audit Trace Overview How to Produce an SMF Audit Trace Report Access the SMF Audit Trace Reporting Facility Abend Codes SMF Audit Tracing (Quick Steps) Generate an SMF Audit Trace Status Report Start an SMF Audit Trace Stop an SMF Audit Trace Display an SMF Audit Trace SMF Audit Tracing (Sample Scenarios) Generate an SMF Audit Trace Report Generate Multiple SMF Audit Trace Reports Filter Data Sample SMF Audit Trace Report Manual SQL File Creation Stop an SMF Audit Trace Display an SMF Audit Trace Chapter 22: DSN1LOGP Wizard 247 Generate a DSN1LOGP Report Chapter 23: DSN1COPY Wizard 249 DSN1COPY Wizard Overview How to Prepare Before Invoking the DSN1COPY Wizard Generate DSN1COPY Statements (Quick Steps) Chapter 24: How to Recover a Dropped Object 253 Gather Your Information Recreate the DDL for the Dropped Object Recreate and Populate the Dropped Object Create a Map of the Dropped Object DDL Create a Map of the Image Copy Use the Maps to Update the Recreated Object Recovery Worksheet User Guide

11 Index 267 Contents 11

12

13 Chapter 1: Introduction General Overview CA Log Analyzer is the complete analysis and management tool for DB2 active and archive log data sets, image copies, and bootstrap data sets (BSDS). Note: This guide assumes that the correct product components have already been installed at your site. For more information, see the CA Database Management Solutions for DB2 for z/os Installation Guide. Chapter 1: Introduction 13

14

15 Chapter 2: Operational Considerations This section contains the following topics: Product Authorization (see page 15) Support a Subsystem After Converting to Extended Logging (see page 17) Valid Processing Dates (see page 18) Set Profile Variables (see page 19) Customize the DML and DDL Report Forms (see page 20) Sort Processing (see page 21) Modify the JES3 Initialization Parameters (see page 23) Support a Subsystem After an RBA Reset (see page 23) Data Sharing Groups with Quiesced Members (see page 24) DB2 10 Support Limitations (see page 24) LOB Support Limitations (see page 24) XML Support (see page 24) Concurrent Copy Support (see page 25) Product Authorization The Product Authorizations Facility is used to grant authority to access CA Log Analyzer plans. You must have the proper authorization and security to perform different operations. Many security restrictions are implemented by the DB2 security system. CA Log Analyzer never lets you bypass DB2 security. The IFI reason code 00E60824 indicates an authorization error. When CA Log Analyzer uses the Log Reader, MONITOR2 access is required. Note: For more information about the Product Authorizations Facility, see the CA Database Management Solutions for DB2 for z/os General Facilities Reference Guide. For more information about DB2 security considerations, see the IBM DB2 Administrative Guide. EXECUTE Plan Security CA Log Analyzer has two plans: LAPO0100 and LAPB0100. These plan names can be modified during installation. Plan LAPO0100 lets you use the online portion of CA Log Analyzer. This plan is executed when you create strategies, specify process log options, or run Image Copy Reporting. Chapter 2: Operational Considerations 15

16 Product Authorization Plan LAPB0100 is executed when the log reporting component is invoked. Log reporting generates all log reports and REDO and UNDO SQL statements. You can execute these plans if you have either of the following authorities: SYSADM authority EXECUTE authority BSDS Security You can use the List Log Inventory component if you have READ access on the Bootstrap Data Set (BSDS) from which the log inventory list is generated. Access to DB2 Data Sets Log Reporting reads the following data sets, based on the report options that are selected: Bootstrap Data Set (BSDS) To read the BSDS, you must define it with VSAM SHAREOPTIONS (2, 3). These options allow any number of users to access the data set for read processing, and one user to access the data set for write processing. Active and archive log data sets Image copy data sets VSAM data sets containing user table data Image Copy Reporting reads the following data sets: Bootstrap Data Set (BSDS) SYSLGRNG directory table The Log Reporting and Image Copy Reporting components run APF authorized. 16 User Guide

17 Support a Subsystem After Converting to Extended Logging Access to DB2 Table Data DB2 authorization can be used to determine whether a user has the authority to review or use the log data for specific tables. To enable this capability, specify Y for Security support on the Edit Parmlib Member PLA panel. When DB2 authorization is enabled, DB2 table authorizations are used to determine a user's authority on data in the log. Both primary and secondary authid information is used. The DB2 tables SYSUSERAUTH, SYSDBAUTH, and SYSTABAUTH are read to determine whether the user has SELECT authority on a table that has information in the log. Note: For more information about using the DSN3@SGN authorization exit routine to check secondary authid information, see the IBM DB2 Diagnosis Guide and Reference. If the user does not have SELECT authority on a table, any log information relating to that table is discarded. The information is not written to a discard file but is ignored, and the following message appears for each table: LAE0207E USER:authid, IS NOT AUTHORIZED TO SELECT DATA FROM TABLE owner.tablename Support a Subsystem After Converting to Extended Logging IBM provides a means to convert a DB2 subsystem from 6-byte RBA and LRSN values to 10-byte values. This conversion significantly increases the log addressing capacity and reduces the possibility of exhausting these values due to heavy logging activity. When a subsystem is converted to 10-byte RBA and LRSN values, perform the following tasks to support the longer values. Follow these steps: 1. Enable extended logging support in CA Log Analyzer. This function is enabled through an ENABLE parmlib option. Note: For more information, see informational solution RI64114 on the CA Support web site. 2. (Optional) Update your customized report forms to accommodate the longer RBA and LRSN values. This step is necessary only when you use customized report forms. a. Select P (Profile) from the CA Log Analyzer main menu. b. Select 4 (Report Forms Administration) from the profile menu. The Report Form Services panel appears. Chapter 2: Operational Considerations 17

18 Valid Processing Dates c. Verify that the Form and Creator fields contain an asterisk (*), and then press Enter. The panel displays a list of all existing report forms. The Ext. Val. column indicates whether a form has been updated to accommodate extended log values. d. Type U (Update) next to a form that has not been updated. Press Enter. The Report Form Definition panel appears. e. Type Y (Yes) in the Extended Values field and update the following text blocks as needed: DML Unit of Recovery Description DML Updated Row Description DDL Unit of Recovery Description DDL Update Description Press PF3 (End). The updated report form is saved. The Report Form Services panel reappears, displaying a Y in the Ext. Val. column for that form. More information: Audit Table Requirements (see page 73) Valid Processing Dates CA Log Analyzer is restricted by the IBM S/390 machine clock when evaluating and reporting on DB2 logs. The S/390 TOD clock supports dates from 12:00 a.m. January 1, 1900 to 11:59 p.m. December 31, CA Log Analyzer supports log processing dates from 12:00 a.m. January 1, 1980 to 11:59 p.m. December 31, Any processing of activity occurring outside of this range, or specified as occurring outside of this range, will have unpredictable results. 18 User Guide

19 Set Profile Variables Set Profile Variables The profile facility lets you define variables specific to CA Log Analyzer. These variables act as the default execution values, and can be overwritten by users as needed. The log reporting variables let you configure various settings for the CA Log Analyzer log reporting component. (This component generates all log reports and REDO and UNDO SQL statements.) For example, you can specify the number of sort work data sets to allocate. You can also specify how to process units of work that are in flight at the start or end of the log processing range. The control statement variables let you specify how CA Log Analyzer builds control statements for the DB2 LOAD utility. For example, you can specify whether logging occurs during the load process, and how work data sets are allocated during this process. For a complete list of control statements, see the CA Log Analyzer Reference Guide. Notes: For detailed information about each variable, see the online help panels. The profile facility also lets you set global variables that apply to all installed CA Database Management Solutions products. These options include execution libraries, JOB statement specifications, print parameters, screen colors, and usage language options. For information about defining global variables, see the CA Database Management Solutions for DB2 for z/os General Facilities Reference Guide. The profile facility also lets you customize the appearance of your DML and DDL reports. Customization instructions are provided separately. Follow these steps: 1. Select the Profile (option P) from the CA Log Analyzer main menu or type the PROFILE primary command. The Profile panel appears. 2. Select option 2, set your log reporting profile variables, and press PF3 (End). The Profile panel reappears. 3. Select option 3, set your load utility control statement variables, and press PF3 (End). The Profile panel reappears. More information: Customize the DML and DDL Report Forms (see page 20) Chapter 2: Operational Considerations 19

20 Customize the DML and DDL Report Forms Customize the DML and DDL Report Forms When you generate a DML or DDL activity report, CA Log Analyzer uses a generic report layout. You can create your own forms to provide customized report layouts. The forms can be recalled for use during any session and can be edited or changed before each use. Forms let you save and reuse a customized layout for a frequently needed report. Report forms are created and edited using the Report Form Definition panel. This panel breaks down the DML or DDL activity report into discrete text blocks. For example, the report lines that describe the unit of recovery are considered a text block. You can customize each text block by selecting the fields to include and specifying where the fields appear within the block of text. Note: We recommended that you test a form on a small report before using it on a large report. Follow these steps: 1. Display the Report Form Services panel by doing one of the following actions: Select option 4 (Report Forms Administration) from the CA Log Analyzer Profile panel. Specify Y in the Customize Rept field on the DML Activity Report Options panel. Specify Y in the Customize Rept field on the DDL Activity Report Options panel. 2. Verify that the Form and Creator fields contain an asterisk (*), and then press Enter. The panel displays a list of all existing report forms. 3. Specify whether to create or update a form: To create a form, type C in the Option field and complete the Form and Description fields. To create a form that is based on an existing form, type T next to the existing form. To update an existing form, type U next to the form. Press Enter. The Report Form Definition panel appears. 4. (Optional) Enter a new form name and description at the top of the panel. Note: This step is required only when you are using the T (template) option to copy an existing form. When you enter a new name and description, the changes are saved to a new form. The original form remains unchanged. Press Enter. Your changes are saved. 20 User Guide

21 Sort Processing 5. Customize the report form: a. Type Y in the Extended Values field if your subsystem has been converted from 6-byte RBA and LRSN values to 10-byte values. b. Select a text block, such as Report Headings, and press Enter. The panel for the selected text block appears. c. Make your selections. If you specified Y in the Extended Values field, be sure to adjust the layout to accommodate 10-byte RBAs and LRSNs. On most panels, the lower half shows an example of the report with your current formatting selections applied. As you make your selections, you can press Enter to refresh the lower half and see how your selection affects the report format. Note: For detailed information about each field, press PF1 to view the online help panel. Press PF3 (End). The Report Form Definition panel reappears. d. Repeat Steps b and c to format more report options. You have customized a report form for your DML or DDL report. You can now specify this form when selecting your report options. Sort Processing The System Sort program is used to perform sorts. System Sort supports all 31-bit sort programs. DFSORT, CA Sort, and Syncsort are dynamically allocated using the standard 31-bit parameter list that these programs support. This list includes the following values: The sort size (MAINSIZE or CORE) specified with the SORTSIZE keyword, the sort work ddname, and the addresses of sort exits E15 and E35. Sort exits E15 (input to the sort program) and E35 (output from the sort program) sort the log data and internal log analyzer data. Notes: Sort size is per sort; it is not divided by the number of sorts. For more information about your sort program, see your sort guide. Chapter 2: Operational Considerations 21

22 Sort Processing Syncsort Users CA Log Analyzer dynamically allocates the $ORTPARM DDNAME to pass parameters to Syncsort. You can override these passed values by coding a $ORTPARM DDNAME in the JCL. This override can be necessary to overcome storage-related problems when using Syncsort. Important! Override the dynamic $ORTPARM DDNAME only under the direction of CA Support. Specify a DDname for Syncsort If you use Syncsort as your sort package, specify a value for the DDNAME for SyncSort parameters in the PLA parmlib member. The default is $ORTPARM. SORTPARM in the JCL Stream If you use Syncsort and experience storage issues, you can specify $ORTPARM in the CA Log Analyzer JCL stream. Note: Each sort in CA Log Analyzer uses successive definitions of the $ORTPARM. These successive definitions allow the Syncsort parameter to be overridden for each sort. The $ORTPARM DDNAMEs can be specified as follows: //$ORTPARM DD DISP=SHR,DSN=PLA.DB2.CNTL(ORTP1),FREE=CLOSE //$ORTPARM DD DISP=SHR,DSN=PLA.DB2.CNTL(ORTP2),FREE=CLOSE //$ORTPARM DD DISP=SHR,DSN=PLA.DB2.CNTL(ORTP3),FREE=CLOSE //$ORTPARM DD DISP=SHR,DSN=PLA.DB2.CNTL(ORTP4),FREE=CLOSE //$ORTPARM DD DISP=SHR,DSN=PLA.DB2.CNTL(ORTP5),FREE=CLOSE LAL@BLDX SORT 1 LAL@REPT SORT 2 LAL@MERG SORT 3 LAL@ICSR SORT 4 LAL@CRSH SORT 5 Create extract file Create reports, SQL (DDL), Load format files Image Copy level of detail - Optional Inline image copy processor - Optional Subsequent update - Optional 22 User Guide

23 Modify the JES3 Initialization Parameters Modify the JES3 Initialization Parameters In JES3 environments, you must modify the JES3 initialization parameters to read log records from DB2 active log data sets. To modify the JES3 initialization parameters, add the following line: DYNALDSN,BYPASS=(Logcopy1,Logcopy2) Logcopy1 and Logcopy2 are data set masks for the active logs of your DB2 environments. If you are using the IBM recommended naming convention, specify the following: DYNALDSN,BYPASS=(?.LOGCOPY1.DS*,?.LOGCOPY2.DS*) Note: An IPL is required to reflect this change. Support a Subsystem After an RBA Reset IBM provides a means to reset the log RBA on a DB2 subsystem when the RBA reaches its maximum. This procedure resets the RBA to zero and removes the prior logs and image copies. However, the versioning information in the subsystem still refers to log ranges from before the reset. On a data sharing system, an RBA reset does not affect CA Log Analyzer because it uses the LRSN values in the log. However, on a nondata sharing system, CA Log Analyzer uses the RBA log values; therefore, a reset affects its ability to process log data for that subsystem. When the log RBA is reset on a nondata sharing subsystem, identify the time of the reset. Also note the time when the subsystem underwent a cold start during the RBA reset process. You can specify the reset time by using the ENABLE parmlib member in highlevel.cdbaparm. Contact CA Support for assistance in creating this member. After the reset time is specified, CA Log Analyzer can support that subsystem. After you specify a reset time, CA Log Analyzer requires full row images for all DML, DDL, and Change Data Capture processing. If you specify any processing type other than Image Copy, the settings are changed automatically to the Image Copy option. If image copy processing significantly increases your overhead, consider enabling DATA CAPTURE CHANGES on your tables. This setting eliminates the need for image copy processing by logging a full image copy of all updated rows. Chapter 2: Operational Considerations 23

24 Data Sharing Groups with Quiesced Members Data Sharing Groups with Quiesced Members If a data sharing member is quiesced and the BSDS or current active log is unavailable, the member is not processed. This situation can occur when you delete the BSDS or logs for the member because you do not plan to use the member again. A message alerts you to this situation. If the BSDS and current active log are available, the member is monitored in case it is activated during the job execution. DB2 10 Support Limitations CA Log Analyzer has the following DB2 10 support limitations: DDL strategies and generated jobs created in pre-r15 CA Log Analyzer versions do not support LOB data. Before using an older strategy or job to generate DDL, use the current CA Log Analyzer online panels to update the strategy or regenerate the control statements. CA Log Analyzer does not support the DB2 10 CREATE MASK and CREATE PERMISSIONS DDL statements. The product also does not support the XMLSCHEMA clause in CREATE TABLE DDL statements. CA Log Analyzer supports hash objects when generating DDL activity reports, and UNDO or REDO DDL statements. Hash support is not provided when generating DML reports, SQL statements, and load files. LOB Support Limitations CA Log Analyzer has the following LOB support limitations: LOB data is not supported when generating load files for CA Fast Load or CA InfoTransport. DDL file mapping supports only LOBs that are fully inline. If a DDL file map points to a table with LOB columns, only the columns that are fully inline are processed. LOB columns that are partially inline are skipped. XML Support When CA Log Analyzer encounters a table with XML columns, it formats the XML indicator data in the base table row. However, it does not report on the XML data or process it in any way. All other table columns are formatted and processed as expected. 24 User Guide

25 Concurrent Copy Support Concurrent Copy Support CA Log Analyzer does not support concurrent copies of objects that have a physical control interval (CI) size greater than 4 KB. The objects must have a CI size of 4 KB. Note: For more information about CI size and the DSVCI parameter that controls this size, see the IBM DB2 Installation and Migration Guide. Chapter 2: Operational Considerations 25

26

27 Chapter 3: Process Log Facility This section contains the following topics: Process Log Overview (see page 27) Processing Flow (see page 28) Access the Process Log Facility (see page 30) Access the Report Source Specifications Panel (see page 30) Output Specifications Panel (see page 38) Report Submission Panel (see page 39) Process Log Overview The Process Log option on the CA Log Analyzer main menu provides the following report options: DML Activity Reports changes to your databases. You can also create executable SQL statements to undo or redo database activity or create a load file. Commit Frequency Report Analyzes DB2 log data sets to determine the number of updates that occur within the scope of each commit. Use this report to determine if local standards for performing commits are being met. Image Copy Frequency Report Reports how often tablespace image copies are made in relation to the amount of activity on the tablespace. This is helpful in determining if image copies are being taken at appropriate intervals for data recovery. Rollback Activity Report Reports on the frequency of DB2 rollbacks requested by DB2 and application programs. This feature helps you analyze system efficiency. Recovery Point Analysis Determines where safe recovery points are in the DB2 log. This can help you choose a good point at which to recover data. DDL Activity Analyzes the DB2 log for creates and drops of DB2 objects. You can also generate an executable DDL to recreate created objects onto another system and recover dropped objects that were not supposed to be dropped. Chapter 3: Process Log Facility 27

28 Processing Flow Change Data Capture Analysis Analyzes the DB2 log to determine the impact of using Data Capture Changes in your DB2 subsystem. The report shows the percentage of increase or decrease in logged data that will occur if Data Capture Changes is turned on or off. Processing Flow All of the reports available in the Process Log facility use a consistent processing flow. The same basic steps are performed regardless of the type of report you are generating. The following illustration shows the processing flow for selecting Process Log reports: 28 User Guide

29 Processing Flow The Report Specification panel lets you select reports. This is the first panel you encounter when generating a report. The following panels are used in generating a report, in the order in which they are listed: 1. The Report Specification panel lets you select which reports to generate. Select the report and press Enter. The Report Options panel appears. 2. The Report Options panel lets you specify the format of the report and define filters. Filters let you control the types of data that are included or excluded from the report. The options that appear on this panel vary depending on the report you have selected. Enter the options you want and press PF3 (End). The Report Specification panel reappears. 3. Select additional reports. When you have finished selecting the options for the reports, press PF3 (End) to register your choices. The Report Source Specifications panel appears. 4. The Report Source Specifications panel lets you specify the range of log data to analyze and an alternate source of log data and table information. When you have entered the options, press PF3 (End). The Output Specifications panel appears. 5. The Output Specifications panel lets you specify the type and destination of the output files, such as the extract file, SQL file, and load file. After you specify the destinations, press PF3 (End). The Report Submission panel appears. 6. The Report Submission panel lets you specify the execution mode for the report. You can generatd the report online or execute as a batch job. Select the execution mode and press Enter to process your job. If you selected the online mode, a message appears while the report is generated. The report appears on your terminal when processing has completed. If you selected the batch mode, the Batch JCL Specification panel of the Batch Processor appears. The job can be submitted directly to JES or saved for later execution. Chapter 3: Process Log Facility 29

30 Access the Process Log Facility Access the Process Log Facility This section explains how to access the Process Log facility. Follow these steps: 1. Select 1 (Process Log) from the CA Log Analyzer Main Menu and press Enter. The Report Specification panel appears. This panel lets you begin the report generation process, or indicates where you can obtain information about the reports through the online help system. 2. Type S in the Sel field next to each report you want to generate. Press Enter to access the option panel for each report, or press PF3 (End) to process your selections. Note: You can also type? next to a report to view a description of that report. Access the Report Source Specifications Panel You can access the Report Source Specifications panel from the Report Options panel. The Report Source Specifications panel lets you do the following: Specify the range of log data to analyze. Specify where CA Log Analyzer looks for log files and which table definitions are used to format the data. Select the DB2 catalog or an alternate image copy as the source of copy information. Select data sharing groups or specific members of a group as the source of DB2 data sharing. Select the BSDS or an alternate log to identify log data sets. Select the DB2 catalog or an alternate table as the source for table definitions. Follow these steps: 1. Press PF3 (End). The Report Specification panel appears. 2. Press PF3 (End) again. The Report Source Specifications panel appears. 30 User Guide

31 Access the Report Source Specifications Panel Specify an Alternate Image Copy Source CA Log Analyzer uses image copies of tablespaces to generate complete row images of log data. Image copies are also the source of decompression dictionaries that are used for compressed log records. By default, the information in the DB2 catalog determines which image copies to use. If the Modify Recovery utility is run against a tablespace, the rows in SYSIBM.SYSCOPY containing the image copy information are deleted. The actual image copy data sets still exist, but they cannot be found through the DB2 catalog. If CA Log Analyzer cannot find the image copies, it cannot construct complete updates from the log and it cannot expand records from compressed tablespaces. In this case, you can specify an alternate image copy source. The alternate image copy mapping facility lets you specify the relevant information for those image copy data sets that still exist. These image copy maps let you correctly process log ranges that those copies cover. Follow these steps: 1. Type Y in the Specify Other Source field on the Report Source Specifications panel and press Enter. The Copy Source Specification panel appears: LAAICS1 COMMAND ===> Process Log - Copy Source Specification SCROLL ===> PAGE Specify the source of DB2 Image Copy definitions. The Image Copies used to complete row images and provide compression dictionaries can be retrieved from the DB2 Catalog or from Image Copy maps. Enter the desired source. Source ==> C ( C - DB2 Catalog, M - Image Copy Maps, O - IC Maps Only) USER1 Enter the Image Copy Group name(s) below. Enter search criteria at the Creator and Group Name prompts to display a selection list of Image Copy Groups. Group/ S O Creator Map Name Description O Y <== CREATE GROUP ******************************** BOTTOM OF DATA ******************************* Valid O Cmds For Image Copy Group: C,U,D,L PF7/8 - Scroll Up/Down Valid O Cmds For Image Copy Maps : C,U,D PF3 - End Chapter 3: Process Log Facility 31

32 Access the Report Source Specifications Panel 2. Complete the following steps: a. Enter one of the following values in the Source field: C (DB2 Catalog) Uses DB2 catalog information. M (Image Copy Maps) Uses both image copy maps and information from the DB2 catalog. O (IC Maps Only) Uses only the image copy maps specified. Press Enter. b. Enter one of the following commands in the O (option) field to create, update, or delete an image copy map from the list: C (Create) Creates an image copy group or map. This command is valid only on the create lines. If C is typed on the Create Group line, the IC Group Editor panel appears. The process of creating an image copy group involves selecting preexisting maps, or creating maps to include in the group. Groups allow easy reference to a set of related image copy maps. If C is typed on the Create Map line, the IC Map Editor panel appears. The process of creating an image copy map involves specifying the data set information for the image copy, and indicating the log point at which the copy was taken. D (Delete Group) Removes an image copy group or map from your selection list. The group or map is deleted only from your selection list. U (Update Group) Edits a map or group. L (List Maps) Accesses a list of maps in a group. This option is valid only on a group line. Press Enter. c. If you are creating a map, specify a share option (Y, N, U) in the SO field. Note: This information is applicable only when the Source is M (Image Copy Maps) or O (IC Maps Only). 32 User Guide

33 Access the Report Source Specifications Panel Access the Alternate Image Copy Selection List The alternate image copy selection list lets you select which image copy maps and groups to use while completing and expanding log records during analysis. Follow these steps: 1. Enter a creator, map, or group selection mask in the Creator or Group/Map Name fields on the Copy Source Specification panel and press Enter. The Alternate IC Selection panel appears. 2. Enter specific names or selection criteria in the Creator and Name fields to limit the image copy map or group list and press Enter. The maps or groups that meet your selection criteria appear on the panel. 3. Type S in the O field next to the map or groups to use and press Enter. The maps and groups are placed in your selection queue. 4. Type S on the command line to shrink the queue to only the selected items. Press Enter. The Selected Image Copies panel appears. 5. Either press PF3 (End), or type S and press Enter. If you pressed PF3 (End), the Copy Source Specification panel reappears. If you typed S, the selection list reappears. Select Members of a Data Sharing Group The Member Selection panel lets you select data sharing groups or specific members of a group. Follow these steps: 1. Type Y in the Specify Other Source field on the Report Source Specifications panel and press Enter. The Member Selection panel appears. Chapter 3: Process Log Facility 33

34 Access the Report Source Specifications Panel 2. Complete the following fields: Type X next to a member to exclude that member. Type S next to a member to select that member or, if already selected, the alternate BSDS of that member. Press Enter. Note: You can alternatively type BSDS on the command line to expand the group member list to show all of the BSDSs of each member. You can then type S next to the specific member that you want to use. The following illustration shows the BSDSs for each member: LAMEML COMMAND ===> Log Analyzer - Member Selection SCROLL ===> PAGE Enter S to select the Data Sharing Members, X to unselect the members. Data Sharing Group: DSNDA0G O Host Member: DXXX Member ID 01 Selected 1 BSDS1: DSNDA0G.DXXX.BSDS01 Selected BSDS2: DSNDA0G.DXXX.BSDS02 Member: DXXX Member ID 02 Selected 2 _ BSDS1: DSNDA0G.DXXX.BSDS01 _ BSDS2: DSNDA0G.DXXX.BSDS02 Selected Member: DXXX Member ID 03 Selected 1 _ BSDS1: DSNDA0G.DXXX.BSDS01 Selected _ BSDS2: DSNDA0G.DXXX.BSDS02 Specify Alternate Log Data CA Log Analyzer can read and analyze log data sets other than the ones cataloged in the BSDS. This option is useful when you want to reread a previously created extract file. An extract file contains log data that has already been extracted for analysis. You can use data set names to specify which active or archive log files to analyze. Follow these steps: 1. Type Y in the Specify Other Source field on the Report Source Specifications panel and press Enter. The Log Source Specification panel appears. 34 User Guide

35 Access the Report Source Specifications Panel 2. Enter one of the following values in the Source Type field: B X L Reads the DB2 BSDS to determine which active and archive logs are needed for the current analysis. The first copy of the active log data sets is used whenever possible. If the specified log range is not contained in the active log, the first copy of the archive log data sets is used. Reads a log extract file that was created in a previous analysis. The data set names for the extract and the extract control file must match the values in the Extract Dataset Name and Extract Control DSNAME fields. Verify that the extract and extract control files are paired correctly. Do not specify a control file that was created with a different extract file. Reads only the logs you specify. Enter the specific logs in the Active/Archive Log Datasets field near the bottom of the panel. Also type A (active) or R (archive) in the T field to specify the log type. To select from a list of log data sets, type % in the Log Dataset Name field and press Enter. The Log Inventory List panel appears. Make your selections and press Enter to return to the Log Source Specification panel. Press Enter. 3. (Optional) Use the following line commands in the O field next to the log data set names: I[n] D[n] R[n] Inserts a blank line in the selection list. Use the parameter n, where n is a number from 1 to 9, to insert multiple lines. Deletes a line from the selection list. Use the parameter n, where n is a number from 1 to 9, to delete multiple lines. Repeats the current line. Use the parameter n, where n is a number from 1 to 9, to repeat the line n times. Press Enter. 4. Press PF3 (End) again. The Report Source Specifications panel appears. Chapter 3: Process Log Facility 35

36 Access the Report Source Specifications Panel Specify Alternate Table Definitions DB2 does not use table names to log changes to a table. The data changes are recorded in the log using the internal DB2 identifiers DBID and OBID. These identifiers are assigned to a table by DB2 when the table is created. If a table has been dropped and recreated, the identifiers can change. If you analyze log data for a table with changed identifiers, CA Log Analyzer can fail to properly format the log data. The alternate table definition facility lets you specify alternate table definitions by associating a table definition with the DBID and OBID identifiers. You provide the definitions by associating CREATE TABLE SQL statements with the identifiers. The alternate table definition facility can also generate REDO SQL statements to apply changes from one table to a duplicate, or mirror, table. By changing the table name that is associated with the OBID and DBID contained in the logs, the generated SQL applies the changes to the other table. Follow these steps: 1. Type Y in the Specify Other Source field on the Report Source Specifications panel and press Enter. The Table Specifications panel appears. 2. Enter one of the following values in the Source Type field: C D Uses DB2 catalog definitions. Uses table definitions from one or more DDL files to format table data. To use these definitions, map the tables defined in the specified DDL files to specific DBIDs and OBIDs. Mapping can be done directly on the Table Specifications panel (using the C option). Mapping can also be done by selecting Source Mapping (option 3) on the Main Menu and then selecting DDL File Mapping (option 1) on the Source Mapping Maintenance panel. 36 User Guide

37 Access the Report Source Specifications Panel M Uses both the table definitions from the DDL file and the definitions from the DB2 catalog for the mapped DBID and OBID values. The DB2 catalog table SYSIBM.SYSTABLES contains row RBA1, which describes the log point at which this table was created. CA Log Analyzer uses this RBA1 value with the FROMRBA values in the DDLFILE map to split the log into sections that use the definition from either the DDLFILE map or the DB2 catalog. Note: If you specify D or M, you can create a map by typing C in the O field on the first line and specifying a creator and map name. You can also display a selection list of DDL files by entering selection criteria in the Creator and Map Name fields. Press PF3 (End). Access the DDL File Selection List Note: For more information about the fields on this panel, see the online help. The DDL file selection list lets you select which DDL file maps are used to format the tables during analysis. Follow these steps: 1. Enter a selection mask in the Creator and Map Name fields on the Table Specifications panel and press Enter. The Mapped DDL File Selection panel appears: 2. Enter specific names or selection criteria in the Creator and Name fields and press Enter. The map names that match your criteria appear. 3. Type S in the O (Option) field next to the file maps you want to use for the analysis, and press Enter. A message informing you that the selections have been queued appears. 4. (Optional) Type S (Shrink) on the command line and press Enter. The Selected Object Queue panel appears, showing the objects that are currently selected. To delete the object from the selected queue, remove the selection character. Note: You can alter or remove objects from the list shown in this panel. Type S in the SEL (Select) field to select an object. Delete the S to remove an object. 5. Press PF3 (End), or type S and press Enter. If you pressed PF3 (End), the Input Specification panel reappears. If you typed S, the selection list reappears. Chapter 3: Process Log Facility 37