CA Plan Analyzer for DB2 for z/os

Transcription

1 CA Plan Analyzer for DB2 for z/os User Guide Version , Fourth 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 Database Analyzer for DB2 for z/os (CA Database Analyzer) CA Detector for DB2 for z/os (CA Detector) CA Index Expert for DB2 for z/os (CA Index Expert) CA Plan Analyzer for DB2 for z/os (CA Plan Analyzer) CA RC/Query for DB2 for z/os (CA RC/Query) CA SQL-Ease for DB2 for z/os (CA SQL-Ease) 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 updates have been made in the fourth edition of this documentation: How to Convert Plan DBRMs to Packages (see page 305) New topic. The following updates have been made in the third edition of this documentation: Using Quick Explains and Explain Strategy Services chapter Consolidated the quick explain and explain strategy documentation into two new user scenarios: How to Explain SQL Using Quick Explain (see page 51) How to Explain SQL Using Explain Strategy Services (see page 61) Moved the reference material to the CA Plan Analyzer Reference Guide. Statistics Manager Functions (see page 194) Updated to indicated that the detailed information about the Statistics Manager batch cards is now provided in the CA Plan Analyzer Reference Guide. The following updates have been made in the second edition of this documentation: How to Implement a Statement-Level Optimization Hint (see page 261) New user scenario that describes how to implement statement-level optimization hints for static SQL. This user scenario also describes how to (optionally) disable implemented hints that have become obsolete or invalid. The following documentation updates have been made since the last release of this documentation: QUERY Reporting (see page 24) New topic that describes the new QUERY Reporting feature. This feature provides information about data that is contained in the access path repository. Create Explain/Input Table(s) (see page 25) Updated to include the following tables: DSN_COLDIST_TABLE, DSN_KEYTGTDIST_TABLE and DSN_USERQUERY_TABLE. Administrative Functions (see page 27) Updated to include the Optimization Hints and DB2 Profile Services facilities.

5 Product Authorization (see page 31) Updated to indicate that Thread Termination\Dynamic DSNZPARM read access is required to create a modeling profile using the automated process or to verify that optimization hints are enabled. UPDATE Catalog Statistics Security (see page 33) Lists the authorities that the PSM main plan and package owner requires to update DB2 catalog statistics. Authority to Execute an EXPLAIN PLAN (see page 33) Updated to indicate that UPDATE authority is now possible against all explain tables that the user defines in CA Plan Analyzer. BIND and FREE QUERY Security (see page 34) Lists the authorities that are required to execute a BIND QUERY or FREE QUERY against SQL. DB2 Profile Services Facility Security (see page 36) Lists the authorities that are required to start, stop, and display profiles in the DB2 Profile Services facility. Set or Customize a CA Plan Analyzer Profile (see page 43) Updated to indicate that remote package support applies only to remote z/os DB2 subsystems. About Enhanced Explain Added the Index Probe Statistics report. Identify and Compare SQL Source Versions (see page 97) Updated to indicate that the cost difference filters can be set to filter data by a percentage or an actual value, or by a percentage and an actual value. Physical Rule Number (see page 119) Added Rule Reporting Services (see page 123) Added QUERY Reporting. Generate a Plan, DBRM, Package, Object, or QUERY Report (see page 125) Added QUERY Reporting. Create Explain or Input Tables (see page 189) Updated to include the following tables: DSN_USERQUERY_TABLE, DSN_COLDIST_TABLE, and DSN_KEYTGTDIST_TABLE. Optimization Hints (see page 251) New chapter that describes the following tasks: How to Create and Maintain Statement-Level Optimization Hints How to Implement a PLAN_Table Optimization Hint Managing DB2 Profiles (see page 279) New chapter that describes how to use DB2 profiles. Comparing SQL Access Paths (see page 283) New appendix that describes how to configure CA Plan Analyzer to perform compare processing, and how to explain SQL sources and identify changes to the access paths and SQL costs.

6

7 Contents Chapter 1: Introduction 17 Product Overview Explain Services Explain Strategy Services and Quick Explain Query Explain Database Compare Explain Versions Update Expert System Rules Reporting Services Plan Reporting DBRM Reporting Package Reporting Object Reporting QUERY Reporting Statement Reporting Plan/Package Management Identifying Problem Plans and Packages Identify Problem SQL Create Explain/Input Table(s) Batch Processor Batch Reporting Facility Administrative Functions Extended Query Facility Alternate Catalog Mapping Multiple DB2 Subsystems Distributed Data Facility Double-Byte Character Set Support Unicode Support Chapter 2: Operational Considerations 31 Product Authorization Operation Level Performance Recommendations Avoid the DB2 System Catalog Limit Analysis Requests Accordingly Use Filters to Target SQL for Analysis Create Additional Indexes on DB2 Catalog Tables Contents 7

8 Chapter 3: Maintaining Profiles 43 Set or Customize a CA Plan Analyzer Profile About Floating Point Format Notation Chapter 4: Understanding Current and Future Explains 45 Current and Future Explains Current Explains Future Explains Prepare Plans and Packages Prepare Plans with DBRMs or Packages for a Current Explain Prepare Plans with Package Lists for a Current Explain Chapter 5: Using Quick Explain and Explain Strategy Services 49 About Explain Strategy Services and Quick Explain How to Explain SQL Using Quick Explain Address the Prerequisites (Optional) Configure the Historical Database (Optional) Configure the Explain Options Define and Execute a Quick Explain How to Explain SQL Using Explain Strategy Services Address the Prerequisites (Optional) Configure the Historical Database (Optional) Configure the Explain Options Identify the SQL Sources to Explain Explain the SQL Sources Procedures for Quick Explain and Explain Strategy Services Managing Selection Lists Specifying Historical Database Options Specify SQL Qualifiers Specifying Report Options Changing Catalog Statistics Specifying Search Conditions Specifying Access Path Filters Chapter 6: Querying the Explain Database 81 Accessing the Query Explain Database Feature Generate Reports Controlling Report Hierarchy Display Determining the Initial Hierarchical Level User Guide

9 Understanding the Hierarchical Display Exploding the Report Display Resetting the Report Display Examples Switching Among Reports Regenerate a Report from the Historical Database About the Batch Job Filtering Reports View the Database Information Display View the Performance Database Display Using Line Commands Chapter 7: Comparing Explain Versions 97 Identify and Compare SQL Source Versions Explode the Compare Cost Report Hierarchy Request a Comparison During Explain Strategy Processing Using Line Commands Chapter 8: Updating Expert System Rules 103 Rules Database Customizing Rules Update Thresholds and Severity Codes DB2 Versions Supported How Rule Sets Are Used Panel Flow Default Rule Sets Create a Rule Set Template a Rule Set View and Update Existing Rule Sets Delete a Rule Set Filter the Rules List Change the Activation Status of Rules Set the Notify Option Print the Rule and Recommendation Text Viewing Rule Violation Notifications Using the Expert System Rules Exit Activating the Exit Object Module PPAEXIT Linking the Object Module Expert System Rules Exit Communications Block Sample Exit - PPAEXIT Contents 9

10 Chapter 9: Using Reporting Services 123 Reporting Services Generate a Plan, DBRM, Package, Object, or QUERY Report Generate a Statement Report Controlling Report Hierarchy Display Determining the Initial Hierarchical Level Understanding the Hierarchical Display Object Dependency Report Examples Statement Report Examples Chapter 10: Using Batch Reporting 133 Batch Reporting Job Submission Batch Reporting Model JCL Default Model JCL Parameters Batch Reporting Return Codes for the Reporting Service Implementing CA Plan Analyzer in the Development Cycle Development Cycle Support Creating Enhanced Explain Input Creating Strategies and Versions in Batch Enhanced Explain Return Codes Sample 1 - After Precompilation Sample 2 - Moving a Plan from Test to Production Batch Input Mode Field Batch Processor Card Display Panel Online Mode (O) Batch Mode (B) Immediate Batch Mode (I) Changing Modes Sample Scenario Chapter 11: Identifying Problem Plans and Packages 171 Understanding Problem Conditions Repeatable Read (Plans or Packages) Uncommitted Read No Isolation Level (Packages Only) VALIDATE(RUN) (Plans or Packages) Invalid (Plans or Packages) Inoperative (Plans or Packages) EXPLAIN(NO) (Plans or Packages) User Guide

11 Degree Degree Any Accessing This Feature Generating Reports Using Line Commands List of Available Line Commands Chapter 12: Identifying Problem SQL 181 How to Identify and Assess Problem SQL by Querying the Historical Database Chapter 13: Using Plan and Package Utilities 185 How to Manage Plan and Package Performance (Optional) Correct Errors in Your Batch Input Chapter 14: Creating Explain or Input Tables 189 Create Explain or Input Tables Chapter 15: Using Statistics Manager 193 Overview of Statistics Manager Statistics Manager Functions Accessing Statistics Manager Accessing Stats Manager Through the Main Menu Access Stats Manager For a PPA Explain How to Develop a Strategy and Migrate Statistics Managing Statistics Strategies Create a Statistics Strategy Managing DB2 Objects Managing Strategy Masks Filtering the List of Statistics Strategies Executing Statistics Strategies and Versions Specify Statistics Options Unload the Statistics Data Load the Statistics Data Editing Strategy Statistics Accessing the PSM Catalog Statistics Editor Panel Updating Calculation Options Viewing Column Statistics Controlling the Display Calculating and Resetting Object Statistics Contents 11

12 Forcing Statistics Values Setting Statistics to Zero Propagating Cardinality and Statistics Updating Statistics Strategies Browsing Statistics Strategies or Strategy Version Definitions Browsing Execution Options Deleting Statistics Strategies or Strategy Versions Viewing the Information Report Viewing Statistics Reports Toggling the Display of Strategy Versions Chapter 16: Maintaining the Source Database 223 Accessing the Source Database Maintenance Facility Viewing a Source List Controlling Report Hierarchy Saving SQL Sources Deleting SQL Sources Using Line Commands List of Available Line Commands Accessing Online Help Chapter 17: Maintaining Stored Procedures 231 Accessing the Stored Procedures Maintenance Facility Stored Procedures Under DB2 V7 and Later Creating Stored Procedures Using Saved Variables Using Options Browsing Stored Procedures Starting Stored Procedures Operations Supported by Primary Commands Operations Supported by Line Commands Chapter 18: Maintaining Auto HVersions 243 Access the Auto HVersion Maintenance Feature Create Auto HVersion Definitions Filter the Selection List_Hversion Update Auto HVersion Definitions Browse Auto HVersion Definitions Delete Auto Hversion Definitions User Guide

13 Chapter 19: Maintaining Explain Profiles 247 Accessing the Explain Profile Maintenance Feature Creating New Explain Profiles Filtering the Selection List Updating Existing Explain Profiles Browsing Existing Explain Profiles Deleting Explain Profiles Chapter 20: Optimization Hints 251 About Optimization Hints How to Create and Maintain Statement-Level Optimization Hints Review the Prerequisites Create a DSN_USERQUERY_TABLE Create a Statement-Level Optimization Hint (Optional) Free Queries from the Access Path Repository How to Implement a Statement-Level Optimization Hint Address the Prerequisites Review the Hints in the Access Path Repository Enable the Hint Prepare the SQL Sources for Hint Verification Verify the Hint Was Used (Optional) Disable Obsolete or Invalid Hints How to Implement a PLAN_TABLE Optimization Hint Review the Prerequisites Create a PLAN_TABLE Optimization Hint Apply a PLAN_TABLE Optimization Hint Chapter 21: Managing DB2 Profiles 279 How to Use DB2 Profiles Appendix A: Comparing SQL Access Paths 283 How to Identify Access Path Changes and SQL Cost Changes Address the Prerequisites Configure the Historical Database Configure the Explain Options Prepare Plans and Packages Identify the SQL Sources to Explain Explain the SQL Sources Compare the Access Paths Contents 13

14 (Optional) Obtain More Detailed Comparison Information Appendix B: Using Performance Data 299 Starting a CA Detector Collection Unloading Collection Data into a Sequential File Copying PDTDLOAD Modifying the PDTULD Step Sequential File Record Layout Loading Performance Data Cards in the Sample Load JCL Appendix C: Migrating Plan DBRMs to Packages 305 How to Convert Plan DBRMs to Packages Appendix D: CA Plan Analyzer Health Checks 309 DB2_PPA_EXPLAIN_RC1@xmanxxxx DB2_PPA_EXPLAIN_RC2@xmanxxxx DB2_PPA_EXPLAIN_RC3@xmanxxxx Appendix E: Quick Steps 313 Setup Procedures Steps for the Installer Steps for the Tutorial User Profile Variables Accessing the Profile Variables Changing the Default Values Explain Strategy Services Accessing the Explain Strategy Services Creating a Strategy Explaining the Strategy Identifying SQL and Object Problems Problem Summary Identifying Problem SQL Accessing the Identify Problem SQL Option Generating the Identify Problem SQL Report Interpreting the Identify Problem SQL Report Generating Object Reports Accessing the Object Reports Menu Generating the Table Dependency Report User Guide

15 Interpreting the Table Dependency Report Viewing and Hiding Object Qualifiers Altering the Object Submitting the Data Set Online Correcting Plan Problems Identifying Problem Plans and Packages Accessing the Identify Problem Plan/Package(s) Facility Selecting Plans or Packages for Display Viewing the Problem Plan List Executing a REBIND from the Problem Plan List Panel Generating Subreports Reexplaining a Strategy Setting Up the Explain Interpreting the Results Index 347 Contents 15

16

17 Chapter 1: Introduction This section contains the following topics: Product Overview (see page 17) Explain Services (see page 17) Reporting Services (see page 22) Plan/Package Management (see page 24) Administrative Functions (see page 27) Extended Query Facility (see page 28) Alternate Catalog Mapping (see page 28) Multiple DB2 Subsystems (see page 29) Distributed Data Facility (see page 29) Double-Byte Character Set Support (see page 29) Unicode Support (see page 30) Product Overview CA Plan Analyzer optimizes and manages DB2 plans and packages. The product is comprised of four main components: Explain Services, Reporting Services, Plan/Package Management, and Administrative Functions. Note: This guide assumes that all product components have already been installed at your site. For more information, see the Installation Guide and the Implementation Guide. Explain Services Explain Services uses information returned from the DB2 Optimizer with catalog statistics and CA Plan Analyzer Expert System Rules to analyze SQL statements. Explain services expand on DB2 EXPLAIN processing and provide enhanced explain output in various reports. Enhanced explain output provides detailed information about access path choices and the factors that led to the path choice. Explain Strategy Services and Quick Explain Two facilities let you group SQL sources: Explain Strategy Services and Quick Explain. Explain Strategy Services lets you save the grouped SQL sources. After a strategy is created, it can be explained over and over. Each time an explain is executed against a strategy, the results of the explain are saved as a version of that strategy. Chapter 1: Introduction 17

18 Explain Services Regular and Expert Mode Quick Explain provides an easy method of grouping SQL sources for on demand Enhanced Explain. The main difference between Quick Explain and Explain Strategy Services is that you cannot save enhanced explain reports with Quick Explain. Quick Explain does, however, let you save the information used to create the explain as an historical version of that SQL source. The focal point of Explain Services is how CA Plan Analyzer lets you combine SQL sources for Enhanced Explain processing. SQL sources can be: SQL statements Packages File input DBRMs PRF and QMF queries DBRM library input Plans Exported PRF and QMF queries Explain Strategy Services and Quick Explain offer two modes to address the needs of various users and situations. Regular mode condenses the enhanced explain process into its fundamentals so that you use only a few screens and a few options. You can specify SQL sources singly or in groups with minimal effort. With the Expert mode, you can explain single SQL statements or entire applications by grouping multiple SQL sources. Any of the following can be SQL sources: Plans DBRMs Packages SQL statements DBRM library input File input PRF and QMF queries Exported PRF and QMF queries You can use a data editor screen to narrow your explain to a specific SQL statement number. You can also select which rule sets to use from Update Expert System Rules to analyze the SQL source. In addition, you can use data editor screens to update catalog statistics, enter search conditions, and specify filters. Each of these options let you customize how the explain is executed. 18 User Guide

19 Explain Services Explain Profiles Explain on Multiple Subsystems Explain without SYSADM Authority Administrators can use explain profiles to easily set up and save a common set of explain options in a profile shared by multiple users. Explain profiles can help simplify the explain process for quick explains and explain strategies. Enhanced explain processing lets you explain a plan or package on any DB2 subsystem without moving the plan or package. Specify the target subsystem ID (SSID), and CA Plan Analyzer does the rest. You can tune applications on your testing subsystem before they are bound on your production subsystem. Enhanced explain processing provides the ability to access a stored procedure through the PPA profile option Use Stored Proc. for EXPLAIN. Users without SYSADM authority can perform EXPLAIN processing on SQL. Note: This feature can also be activated through EXPLAIN batch cards. Explain Test Plans on Production Subsystems Explain with Projected Data Statistics Historical Versioning of Explains You can execute enhanced explain processing on your production DB2 subsystem for a plan or package that resides on your test subsystem. You can tune applications on your test subsystem to help determine how they will perform when bound on your production subsystem. During an enhanced explain, statistics stored in the DB2 catalog are used to determine the optimal access path. Forcing the DB2 Optimizer to use other statistics (such as your production statistics) requires significant revamping. The Catalog Update facility utilizes Statistics Manager by letting you temporarily change catalog statistics for an enhanced explain. You can commit the catalog updates or roll them back. Enhanced explain processing lets you save the explains to the CA Plan Analyzer historical database. Use this explain data to help identify performance improvement or degradation when upgrading to new DB2 releases or changing the application. This historical database drives the following reporting options: Query Explain Database Compare Explain Versions Chapter 1: Introduction 19

20 Explain Services Enhanced Explain Reports Identify Problem SQL Source Database Maintenance Facility Enhanced explain reports include information about the chosen access path and the factors that led to that choice. These factors include DB2 catalog statistics and physical object configurations. CA Plan Analyzer goes beyond DB2 EXPLAIN analysis with Expert System Rules. These rules govern SQL syntax, physical object design, plan and package bound design, and use of predicates. You can use these rules to generate reports with accompanying recommendations whenever a conflict occurs during Explain processing. You can update these Expert System rules to reflect threshold values for your installations. Use the default rules or create custom rule sets. CA Plan Analyzer details this information in several different reports: Summary report SQL Cost report Access Path Analysis report Predicate Analysis report Dependency Analysis report Referential Integrity report Tree report Statistics reports SQL design rule report Physical design rule report Predicate design rule report Plan design rule report Performance report Compare Versions Cost Compare report Compare Explain Versions report Index Probe Statistics Report 20 User Guide

21 Explain Services Query Explain Database You can query the historical database with the Query Explain Database facility to retrieve information about an explained strategy. Query Explain Database presents the information within five reports. For example, you can review: Access methods that your SQL uses SQL (Explain Summary report) Most costly SQL statements (Cost Summary report) Most frequently used statement types (Statement Summary report) Objects that are referenced within the explained SQL (Object Summary report) Summary of object information (Information Summary report) Compare Explain Versions You can specify the comparison of two historical database SQL sources to generate a Compare Explain Versions or Compare Versions Cost Compare report. These reports detail the changes found for SQL, access path, or SQL cost. You can compare versions for the following SQL sources: Plan Package SQL DBRM library input File Report Facility (PRF) queries and Exported Report Facility query QMF queries and Exported QMF query The Compare Explain Versions report shows the compared SQL text, short access path report, and the SQL cost increase or decrease highlighted. The report also contains a summary detailing the match statistics. The Compare Versions Cost Compare report lets you compare the historical versions cost (Milliseconds, Service Units, and Total Cost) of various SQL sources. You can also compare sources contained in CA Plan Analyzer explain strategies. The report helps you quickly detect and analyze packages where performance degradation or improvement exists. Chapter 1: Introduction 21

22 Reporting Services The Compare Versions Cost Compare report displays in a five-level hierarchical format arranged and shown indented by hversion, level, group (collection), object (package), and statement. The object and statement levels display access path change indicators, SQL text change indicators, and SQL cost. The SQL cost is displayed in New, Old, and SQL cost difference format for the possible cost categories (Milliseconds, Service Units, and Total Cost). Update Expert System Rules Rules can be triggered during explain processing to highlight problematic SQL or physical descriptions, or both. The Update Expert System Rules options allow you to create rulesets specific to your needs by activating or deactivating rules and setting thresholds. For example, physical rule 1077 is triggered when FREEPAGE for a universal tablespace partition is not between the acceptable range of This threshold can be changed to adapt to your site standards. Reporting Services With Reporting Services, you do not have to write complex queries. You have six options to monitor your plans, DBRMs, objects, and SQL statements: Plan Reporting Package Reporting Statement Reporting DBRM Reporting Object Reporting Query Reporting By changing the report header, you can generate the same report for different plans, packages, or objects without exiting the current report. Subreport options also let you issue commands to generate subreports for the items that are listed on a report. All reports support distributed data facility (DDF) locations. By letting you change the location and DB2 SSID on any report panel, you can navigate your way through many DB2 subsystems. You can produce reports in online or batch mode. You can also extend the WHERE clause on any SQL statement using the Extended Query Facility (EQF). 22 User Guide

23 Reporting Services Plan Reporting You can use the Plan Reporting facility to obtain information regarding DB2 application plans. Application plans are the bound application programs (DBRMs) that access DB2 data and define the relationship between the program and the DB2 data. The Plan List report, for example, can list multiple plans. To rebind all these plans, simply enter REBIND in the command line. CA Plan Analyzer invokes the Batch Processor to generate the input to execute your request. DBRM Reporting DBRM Reporting provides facilities similar to Plan Reporting, but from a DBRM point of view. For example, when you change a common DBRM, you can quickly find out which plans must be rebound. Once the plans are listed, you can issue the REBIND command to rebind all plans affected by the DBRM change. Package Reporting A package contains a single optimized DBRM. Package Reporting displays detailed information about packages and their collections. For example, the Package Plan Inclusion report displays all the plans that include packages. The plans containing the package are indented under the package name for quick reference. This display lets you see which plans are affected by a BIND PACKAGE command. Object Reporting Object Reporting provides a powerful view into SQL dependency. You can view all plans, collections, DBRMs, packages, and SQL that are dependent on a database, tablespace, table, index, MQT, view, synonym, alias, column, column mask, or row permission. With this capability you can answer questions like, Show me all the SQL in my system that updates the SALARY column. Chapter 1: Introduction 23

24 Plan/Package Management QUERY Reporting Use the QUERY Reporting option for requesting catalog based reports about data that is contained in the access path repository. The access path repository is a group of DB2 catalog tables that contain data about queries that are tied to statement-level optimization hints. Statement-level optimization hints help influence the access path that the DB2 optimizer selects for processing SQL statements. Statement-level optimization hints are created in the DSN_USERQUERY_TABLE. The contents of this table are bound using the BINDQRYOPT command and then added to the access path repository. Identify the status, validity, and parameters of your statement-level optimization hints using QUERY Reporting. Optionally free queries from within the QUERY reports. Free the queries from the access path repository to remove invalid hints, address performance degradation, or capitalize on DB2 optimizer improvements. You can also free queries when the contents of the DSN_USERQUERY_TABLE are bound inadvertently. Important! DB2 allows a FREE QUERY against only a local location. Changing the location value from the local default causes the FREE QUERY to fail. More information: About Optimization Hints (see page 251) Statement Reporting You can use the Statement Reporting facility to report on all SQL within your subsystem or on plans that meet certain syntax configurations. This flexibility provides a powerful method for monitoring and enforcing SQL standards at your site. This method is the only way to do things like finding all SQL with only Stage I predicates or finding all SQL containing correlated subqueries. Plan/Package Management Plan/Package Management Services help identify problem plans and packages, along with problematic SQL when stored in the historical database. Correct the plan and package problems by executing utilities from online report panels. Another solution is to create explain tables for multiple users with an online interface. Working directly from any report, you can enter primary or line commands to: BIND, FREE, or REBIND some or all of the listed plans or packages Execute utilities through the Plan/Package Utilities menu. 24 User Guide

25 Plan/Package Management CA Plan Analyzer provides online and batch processing options for the BIND, FREE, and REBIND utilities. Identifying Problem Plans and Packages The Identify Problem Plan/Package(s) facility lets you identify all of the plans invalidated by altering an object. This facility is more efficient than using Object Reporting to predict which plans were invalidated. Object Reporting displays only those objects dependent on the selected object, making it time-consuming to predict which plans were invalidated. Identify Problem SQL You can query the historical database to help identify potential problematic SQL captured during the explain. The Identify Problem SQL facility consists of two reports, Identify Explain Problems and Identify Rule Problems. The Identify Explain Problems report can be used to identify SQL tied to a specific access path problem. For example, the report can show all SQL statements that encountered tablespace scans. The Identify Rule Problems report can be used to identify SQL that triggered specific CA Plan Analyzer Expert System Rules. Create Explain/Input Table(s) The Create Explain/Input Table(s) facility lets you generate the DDL for the input table DSN_USERQUERY_TABLE and for the following explain tables: PLAN_TABLE DSN_STATEMNT_TABLE DSN_FUNCTION_TABLE DSN_STATEMENT_CACHE_TABLE DSN_COLDIST_TABLE DSN_KEYTGTDIST_TABLE This facility also lets you generate the DDL for the DB2 recommended indexes for each table. Chapter 1: Introduction 25

26 Plan/Package Management Batch Processor CA Plan Analyzer invokes the Batch Processor when you use the following features: Create Explain/Input Tables Plan/Package Utilities Explain Services features online or in batch mode. For example, you can request a REBIND of all plans listed from a plan report. CA Plan Analyzer invokes the Batch Processor to write the input that is required to execute the REBIND utility command. CA Plan Analyzer can also list the batch input that is used to execute your request on the Batch Processor Card Display panel. Use this panel to specify the execution mode and review the cards for the job. CA Plan Analyzer lets you execute the job in online, batch, or immediate batch mode. In the example, a REBIND is requested for listed plans. Submit the generated cards through the Batch Processor, and all your plans are rebound. Note: For more information, see the Batch Processor Reference Guide. Batch Reporting Facility The Batch Reporting facility lets you generate CA Plan Analyzer reports in batch mode. Batch Reporting creates a job stream that contains the JCL commands and control information necessary to generate and print the reports. Access the Batch Reporting facility by entering the BATCH primary command from the following menus and reports: Plan Reporting DBRM Reporting Package Reporting Object Reporting Statement Reporting Query Reporting Identify Problem SQL Query Explain Database Compare Explain Versions 26 User Guide

27 Administrative Functions Identify Problem Plan/Package(s) Note: Do not confuse the Batch Reporting facility with the Batch Processor. The Batch Processor is a product for processing data sets that contain SQL and special Batch Processor commands. Batch Reporting is a facility for generating reports in batch. Administrative Functions CA Plan Analyzer also provides the following Administrative Functions: Source Database Maintenance Helps maintain the integrity of your historical database by letting you save, rename, or delete SQL sources. Stored Procedures Maintenance Allows you to create, update, browse, delete, and start stored procedures and maintain your DB2 SYSIBM.SYSPROCEDURES table. Auto Hversion Maintenance Helps manage the automatic historical versioning that Explain Services uses to save the explain to the historical database. This facility can create, update, browse, and delete automatic historical version definitions. Explain Profile Maintenance Helps manage and store a common set of explain options in an explain profile that multiple users can share. This facility can create, update, browse, and delete explain profiles. Optimization Hints Helps manage PLAN_TABLE and statement-level optimization hints, which influence the access path that the DB2 optimizer selects. For PLAN_TABLE optimization hints, you can update specific plan table columns that can influence access paths, as determined by DB2. Browse all columns in the plan table or delete plan table rows. You can generate a short access path report for the query. You can also generate a compare access path report to show before-and-after changes when an optimization hint is updated. The Optimization Hints facility also supports the creation and implementation of statement-level optimization hints. Statement-level optimization hints use statement text matching to apply hints to all instances of a statement systemwide or against a package. DB2 Profile Services Facilitates the process of managing profiles and profile attributes in the DSN_PROFILE_TABLE and DSN_PROFILE_ATTRIBUTES tables. For example, this facility helps verify that only valid profiles and attributes are added to catalog tables. Chapter 1: Introduction 27

28 Extended Query Facility Extended Query Facility The Extended Query Facility (EQF) lets you customize internal SELECT statements to control the data returned. Extended queries are used to control the data displayed on selection lists and reports. For example, when you are viewing a plan listing, you might want to view only valid plans that were bound within a specific time range. Using EQF, you enter the custom selection criteria, and they are executed as part of the internal SQL statements. You can save, share, and execute extended queries in online or batch mode. EQF also supports the use of symbolic variables that permit run-time customization of the search criteria. EQF is common to most MVS products for DB2. Alternate Catalog Mapping Alternate Catalog Mapping (ACM) is a facility used by several CA Database Management Solutions for DB2 for z/os. ACM lets you define shadow tables or views for the DB2 system catalog tables. You can use views to control access to the information in the catalog and use shadow catalog tables to reduce contention on the DB2 catalog. You can define any combination of shadow tables and views. CA Plan Analyzer supports ACM, which lets you control access to the DB2 system catalog for each user. Activate ACM through the CA Database Management Solutions for DB2 for z/os Main Menu (ACM set to ON). When you activate ACM for a user, dynamic SQL is used because the SQL statement is prepared dynamically based on the alternate table/view names. Therefore, you must have SELECT authority on the alternate views, tables, or both. Note: For more information about ACM, see the Value Pack Reference Guide. 28 User Guide

29 Multiple DB2 Subsystems Multiple DB2 Subsystems CA Plan Analyzer lets you switch between different DB2 subsystems, even different DB2 versions, without having to exit CA Plan Analyzer and reallocate load libraries. To switch subsystems, enter the new subsystem ID in the DB2 subsystem ID field (SSID), which appears on most CA Plan Analyzer panels. This feature lets you view a CA Plan Analyzer report on one subsystem, change the SSID, and view the same CA Plan Analyzer report on the newly specified subsystem. You can even select a subsystem from a subsystem listing. Note: For more information about multiple DB2 subsystems, see the General Facilities Reference Guide. In general, you can use products in a split panel mode. However, because the DB2 Call Attach Facility does not let you connect to two different subsystems simultaneously, you might encounter unpredictable results if you change subsystems in one of the sessions. For more information, see the IBM DB2 Application Programming and SQL Guide. Distributed Data Facility CA Plan Analyzersupports the Distributed Data Facility (DDF). CA Plan Analyzer implements DDF to let you view plan reports at remote installations. A Location prompt on all report panels lets you switch to a different location. You can view two different locations at the same time becauseca Plan Analyzer supports split panel mode. Enter a question mark (?) for Location to receive a listing of valid locations. When you use DDF, all remote SQL is dynamic because it must be bound on the remote system. CA Plan Analyzer automatically adds the FOR FETCH ONLY clause to provide the most efficient data retrieval across the network. Double-Byte Character Set Support CA Plan Analyzer supports double-byte character sets. The languages in countries such as China, Japan, and Korea use writing schemes that consist of large character sets which cannot be represented with one-byte codes. For example, Kanji (used in Japan) and Hanzi (used in China) each contain several thousand characters. A character set, DBCS (Double-Byte Character Set), has been created to represent these characters. DBCS uses two bytes per character. Note: For more information, see the IBM DBCS Applications Primer Guide and DBCS Design Guide. Chapter 1: Introduction 29

30 Unicode Support Unicode Support CA Plan Analyzer supports Unicode UTF-8. CA Plan Analyzer reports process Unicode UTF-8 data collected from the DB2 catalog, explain tables, or DBRMs, and convert the Unicode UTF-8 data to EBCDIC for display. A substitution character, x'3f', is substituted for any Unicode characters that cannot be translated to EBCDIC. 30 User Guide

31 Chapter 2: Operational Considerations This section contains the following topics: Product Authorization (see page 31) Performance Recommendations (see page 36) Product Authorization The Product Authorizations Facility lets you use DB2 security to control user access to the product functions. Note: For more information about using the Product Authorizations Facility, see the General Facilities Reference Guide. Review the following authorization requirements before running CA Plan Analyzer: To run CA Plan Analyzer, grant the user authority to execute the Batch Processor. To execute commands through the DB2 Command Processor, grant the user authority to execute this function (found in the General category). To create a modeling profile using parameters captured from another DB2 subsystem, or to verify whether optimization hints are enabled, grant the user read access to Thread Termination\Dynamic DSNZPARM. You can grant or revoke authorization to the following CA Plan Analyzer functions: PPA Main Plan Executes all product features, except for Update Expert System Rules. PPA Rule Admin Executes the Update Expert System Rules feature, which includes updating, creating, templating, and deleting rule sets. PPA Database Maint Performs any operations in the Source Database Maintenance facility. PPA Procedure Maint Performs any operations in the Stored Procedures Maintenance facility. PSM Main Plan Performs any operations in the Statistics Manager facility (including import, export, and rollback operations against the DB2 catalog tables). Chapter 2: Operational Considerations 31

32 Product Authorization Dynamic DB Access Lets the user have Dynamic SQL SELECT authority against the CA Plan Analyzer Database tables included in Explain Services, Identify Problem SQL, and Source Database Maintenance. You can grant or revoke authorization to the following CA Plan Analyzer common services functions: PPA Services Accesses the catalog for the common services that CA Plan Analyzer uses. Load Util. Commit Loads CA Detector data into the CA Plan Analyzer Historical Database Performance table using RELEASE(COMMIT). Load Util. Dealloc. Loads CA Detector data into the CA Plan Analyzer Historical Database Performance table using RELEASE(DEALLOCATE). Operation Level The DB2 security system implements many of the security restrictions that are discussed in this section. Users are never permitted to bypass DB2 security. More security is provided through the authorization exit and Product Authorization facilities. Note: For more information about the Product Authorization facilities, see the General Facilities Reference Guide. DB2 Security Create Explain Table Security This product follows the same security as DB2, as summarized in the following sections. Note: For more information, see the IBM DB2 Administrative Guide. Except where noted, when the SQL statement is embedded in a program, the privilege set consists of the privileges that the owner of the plan or package designates. When the statement is executed dynamically, the privilege set is the union of the privileges designated by each authorization ID of the process (primary and secondary IDs). You can create an Explain Table when you have at least one of the following: SYSADM authority DBADM, DBMAINT, or DBCTRL authority on the database that contains the Explain Table 32 User Guide

33 Product Authorization UPDATE Catalog Statistics Security CREATETAB privilege on the database that contains the Explain Table Note: For more information about Explain Tables, see the IBM DB2 SQL Reference Guide. The PSM main plan can update the DB2 catalog statistics using the CA Plan Analyzer Catalog Statistics facility. The PSM plan and package owner must have at least one of the follow authorities: SYSADM authority Authority to Execute an EXPLAIN PLAN UPDATE authority on the catalog table or column being updated You can execute an EXPLAIN PLAN on SQL when you have at least one of the following authorities: SYSADM SQLADM System DBADM Authority to execute the SQL (including SELECT authority for tables that the dynamic SQL references) and UPDATE authority on all installed explain tables that the user defines in CA Plan Analyzer Note: For more information about explain tables, see the IBM DB2 for z/os documentation. Access to the CA Plan Analyzer stored procedure to perform EXPLAIN processing To access this stored procedure, specify Y for the Use Stored Proc. for Explain variable in the PPA profile option. Doing so allows users without EXECUTE authority on the EXPLAIN PLAN statement to use the CA Plan Analyzer stored procedure to perform EXPLAIN processing. The authority of the stored procedure is used and you can still view the results of the EXPLAIN. Important! The CA Plan Analyzer stored procedure used to perform EXPLAIN processing is supported only in DB2 subsystems that use native DB2 security. EXPLAIN privileges that allow you to perform certain explain tasks without the ability to access or modify data Chapter 2: Operational Considerations 33

34 Product Authorization Authority to Execute an EXPLAIN PACKAGE You can execute an EXPLAIN PACKAGE on SQL when you have at least one of the following: SQLADM authority SYSADM authority SYSOPR authority SYSCTRL authority BIND, REBIND, FREE Plan Security EXECUTE Plan Security You can BIND, REBIND, or FREE a plan if you have at least one of the following: SYSCTRL or SYSADM authority BIND, BINDADD, or BINDAGENT authority You can EXECUTE a plan when you have at least one of the following: SYSADM authority EXECUTE authority BIND AND REBIND Package Security BIND and FREE QUERY Security You can BIND or REBIND a package when you have at least one of the following: SYSCTRL, SYSADM, or PACKADM authority ALL, BIND, BINDADD, or BINDAGENT authority SQLADM authority with limited authority to specify EXPLAIN (ONLY) or SQLERROR (CHECK) options Explain privileges with limited authority to specify EXPLAIN (ONLY) or SQLERROR (CHECK) options You can execute a BIND QUERY or FREE QUERY on SQL when you have at least one of the following authorizations: SQLADM authority SYSADM authority System DBADM authority SYSOPR authority 34 User Guide

35 Product Authorization FREE PACKAGE Security COPY Package Security EXECUTE Package Security CREATE IN Package Security SYSCTRL authority You can FREE a package when you have at least one of the following: SYSCTRL, SYSADM, or PACKADM authority BINDAGENT authority You can COPY a package when you have at least one of the following: SYSCTRL, SYSADM, or PACKADM authority ALL or COPY authority You can include a package in a plan when you have at least one of the following: SYSADM or PACKADM authority ALL or EXECUTE authority You can create a package inside a collection when you have at least one of the following: SYSCTRL, SYSADM, or PACKADM authority CREATE IN authority Stored Procedures Maintenance Facility Security You can perform any operations in the CA Plan Analyzer Stored Procedures Maintenance Facility when you have at least one of the following: SYSADM authority Source DB Maint authority Source Database Maintenance Facility Security You can perform any operations in the CA Plan Analyzer Source Database Maintenance Facility when you have at least one of the following: SYSADM authority Procedure Maint authority Chapter 2: Operational Considerations 35