IBM(R) DB2(R) Performance Expert for Multiplatforms, V2.2.3 IBM DB2 Performance Expert for Workgroups, V2.2.3 IBM DB2 Performance Expert for Content Manager, V2.2.3 Fix Pack 3 README CONTENTS 1.0 ABOUT THIS README FILE 1.1 Evaluation code 1.2 Corrected problems 1.3 Limitations, known problems, and workarounds 1.4 Enhancements 2.0 PREREQUISITES 2.1 Hardware requirements 2.2 Software requirements 3.0 INSTALLATION INSTRUCTIONS 3.1 General notes 3.2 UNIX(R)-specific and Linux(R)-specific installation information 3.3 Windows(R)-specific installation information 4.0 CONFIGURATION AND USAGE INSTRUCTIONS 4.1 Enabling access to a CIM Server 4.2 CIM Server 4.3 Using Performance Expert with DB2 V8 Fix Pack 9 or later 4.4 Using the IBM Content Manager threshold set 4.5 Reducing data volume for SQL activity tracing 4.6 Workload generator 'pedemo' 4.7 Impact of Daylight Saving Time changes 4.8 Impact of time zone code changes 4.9 Viewing the trend for a counter with a certain range validity 5.0 CORRECTIONS TO DOCUMENTATION 6.0 HOW TO GET HELP 7.0 NOTICES 7.1 Use of evaluation program 7.2 Trademarks and service marks 1.0 ABOUT THIS README FILE Welcome to IBM DB2 Performance Expert, Version 2, Release 2, Fix Pack 3 README file of 6 February 2007. Always check the following Web site for later versions of this README file: http://www.ibm.com/software/data/db2imstools/support/fixpaks.html This README file contains information about installing and configuring IBM DB2 Performance Expert for Multiplatforms, IBM DB2 Performance Expert for Content Manager, and IBM DB2 Performance Expert for Workgroups. It also contains information about known problems. In this README file, the following naming conventions apply: IBM DB2 Performance Expert for Multiplatforms, IBM DB2 Performance Expert for Workgroups, and IBM DB2 Performance Expert for Content Manager are abbreviated to Performance Expert where applicable. You can use Performance Expert Client or Performance Expert Agent also with the following products: - IBM Tivoli(R) OMEGAMON(R) XE for DB2 Performance Expert on z/OS(R), V3.1 or later - IBM Tivoli OMEGAMON XE for DB2 Performance Monitor on z/OS, V3.1 or later - IBM DB2 Buffer Pool Analyzer for z/OS, V3.1 or later - IBM DB2 Performance Expert for z/OS, V2.1 - IBM DB2 Performance Monitor for z/OS, V8.1 - Performance Toolkit for z/OS - SAP Edition V2.1 or later Known problems that exist for these products in Performance Expert Client or Performance Expert Agent are also listed in this README file. 1.1 Evaluation code If you use evaluation code, the evaluation code enables you to try this product for a period of 60 days. After 60 days, you must purchase a license to continue to use the product. When you purchase the product, the license is enforced based upon the platform on which you are running Performance Expert. 1.2 Corrected problems Performance Expert V2.2.3 contains the following corrections: APAR PK32616: WHILE STARTING SERVICE FOR PERFORMANCE EXPERT ON WINDOWS, IT STOPS WITH NO ERROR IF DATA EXECUTION PREVENTION IS TURNED ON. APAR PK33144: DB2 PE VERSION 2.2.1 CD INSTALLATION GETS 'COM.IBM.DB2PM.INSTALLER.DB2.DB2INSTANCEEXCEPTION' APAR PK33168: PE CLIENT GUI DOES NOT DISPLAY COLLECTED SNAPSHOT HISTORY ROW ACTIVITY DATA FOR A SPECIFIC POINT IN TIME. 1.3 Limitations, known problems, and workarounds 1.3.1 Limitations 1.3.1.1 If you monitor a DB2 instance that is located on an AIX(R), a Solaris, or a Linux machine, you cannot enable CIM if the host name of the monitored machine starts with an underscore or a number. If you enable CIM, the error "invalid locator" occurs when Performance Expert Server accesses CIM. 1.3.1.2 When a monitored database is in WRITE SUSPEND mode, Performance Expert Server does not collect data and display it on Performance Expert Client. This behavior is a DB2 limitation. 1.3.1.3 When you install Performance Expert on UNIX or Linux systems, the installation path may not contain blanks. If you specify a path name that contains blanks, the previously displayed default path name is used for installation. 1.3.1.4 If you use DB2 9 fix pack 2 on your monitored Linux or UNIX system and you have set the DB2 registry variable DB2_LIMIT_FENCED_GROUP to YES and if you have configured Performance Expert to use database objects to exchange event monitor files then the configured remote directory at the monitored system that contains Performance Expert's shared library fpeevm must have read, write and execute permissions for the DB2 instance owner, fenced user and the group (775). 1.3.2 Known problems and workarounds 1.3.2.1 Problem: When you install Performance Expert Server on Windows on a DB2 V8 and on a DB2 9 instance, the Windows registry contains only the entry for the last installation of Performance Expert Server. Therefore, you cannot start the Performance Expert Server of the first installation as a Windows service. Also, you cannot uninstall the first Performance Expert Server installation from the Control Panel -> Add/Remove Programs. - Workaround: To uninstall the first Performance Expert Server installation, use the uninstaller.exe that is located in the uninstall directory of Performance Expert Server. To start Performance Expert Server of the first installation, click Start -> All Programs -> IBM DB2 Performance Expert Server V2 -> Start. 1.3.2.2 Problem: The Multiplatform Installer might hang on UNIX and Linux systems, because it does not find a valid Java(TM) version for the installation. - Workaround: Start the Multiplatform Installer by using the following command: -is:javahome "" -console For example, for Solaris using Java 1.4, enter: db2pe.server.v2.2.3.install-on-solaris -is:javahome "/usr/java1.4" -console 1.3.2.3 Problem: Performance Expert Server might display wrong assignments of objects (e.g.tables) to databases and might record the DB2 error SQL0803N in the db2pesrv.log file several times and writes a lot of data into the TEMP directory of the Performance Expert Server machine if the following conditions occur: - You monitor one or more multipartition databases in one DB2 instance. - More than one multipartition database in the DB2 instance is active. - One or both of the following: - History processing for the setting 'System' is enabled in the Properties window of the monitored DB2 instance on Performance Expert Client. - In Performance Expert Client you refresh Statistics Details in GLOBAL mode. Under these conditions, DB2 sometimes assigns table spaces, buffer pools, dynamic SQL statements or tables to the wrong database. This results in an incorrect display of assignments of objects and statements to databases in Performance Expert Client. If history processing for 'System' is enabled (default) then you may also get the error SQL0803N on the Performance Expert server console and in the db2pesrv.log file and the affected history data is not stored. In this case there are also a lot of binary files accumulating in the TEMP directory. In DB2 V8 this incorrect assignment of objects or statements to databases is fixed in Fix Pack 10 (APAR IY71463). In DB2 V9 this is still an open problem (APAR JR25879). - Workaround: If you get the SQL0803 error message or get an incorrect display of assignments of objects and statements to databases take these steps: -- In Performance Expert Client, open the Properties window for the monitored DB2 instance and turn off the history settings for 'System'. -- In Performance Expert Client don't refresh the Statistic Details window in GLOBAL mode. -- On the Performance Expert Server machine in the TEMP directory delete the files with the following name: snapshot__ 1.3.2.4 Problem: The pecentralize command fails with error 'db2 not found' on UNIX and Linux systems because db2profile was not executed in bash shell. - Workaround: Use a different shell, for example, the Korn shell, as login shell for the DB2 instance user. 1.3.2.5 Problem: If you monitor a DB2 instance that is located on an AIX machine with CIM enabled, N/P values might be present on the Operating System Information window if the /tmp directory on the monitored machine or the Performance Expert Server machine is nearly full. - Workaround: Free space in the appropriate /tmp directory. 1.3.2.6 Problem: Installation and configuration of Performance Expert Server or Performance Expert Client on UNIX or Linux in console mode might cause errors if you correct input data with the backspace key and if the backspace key is not correctly configured. - Workaround: Before installation and configuration, activate the backspace key with the command "stty erase ^?". Depending on the shell, you might have to enter "stty erase ^H". 1.3.2.7 Problem: If CIM is enabled, retrieving data from the CIMOM Server might fail because the host name of the monitored system on which the CIMOM Server runs cannot be resolved on the system on which Performance Expert Server runs. - Workaround: Add the fully qualified host name of the monitored system to the /etc/hosts file on the system on which Performance Expert Server runs. 1.3.2.8 Problem: If you monitor a DB2 instance that is located on an AIX machine and if CIM is enabled, a value for 'Disk Utilization-I/O time' might not be displayed. - Workaround: The I/O time value is displayed if the SYSP_V_IOSTRUN flag is set. To set the flag, enter the following command as root: chdev -l sys0 -a iostat=true To remove the flag, enter the following command as root: chdev -l sys0 -a iostat=false To see the current status of the flag, enter the following command as root: lsattr -E -l sys0 -a iostat For more details, see the "Disk Input/Output History" section of the iostat command documentation on this Web site: http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?topic= /com.ibm.aix.doc/cmds/aixcmds3/iostat.htm 1.3.2.9 Problem: The password that you enter when you install Performance Expert Server on Windows is rejected, even if it is valid. During the installation of Performance Expert Server and Performance Expert Agent, you are prompted for the service password. Even if the password that you enter is valid, you might get the message "Invalid password entered". The reason might be that the forceguest registry value on Windows XP is set to 1 by default in the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa This setting forces the Microsoft(R) Security Support Provider Interface (SSPI) to log on as the guest user. If the guest user is not enabled, SSPI cannot validate the password. - Workaround: 1) Open the registry editor. 2) Set the variable forceguest to the value 0 in the following registration key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa 3) Restart the installation. 1.3.2.10 Problem: If you monitor a DB2 instance that is located on an AIX machine and if CIM is enabled, the following limitation exists: The CIM Server might have crashed if these conditions occur on Performance Expert Client: a. You see N/P values on operating system windows or graphical data views that you have defined for operating system values. b. A red icon in the right corner on the window with a tooltip indicates that the CIM Server cannot be reached. - Workaround: Restart the CIM Server. 1.3.2.11 Problem: If you monitor a DB2 instance that runs on DB2 V8 Fix Pack 11, you might get the message 'An internal error occurred' in Performance Expert Client because of an allocation failure of a high amount of memory when you open 'Applications in Lock Conflicts'. The allocation failure message is also displayed on Performance Expert Server. - Workaround: Install DB2 V8 Fix Pack 12 or later on your monitored system. This problem is fixed with DB2 APAR LI70768. 1.3.2.12 Problem: If you see corrupted windows on Performance Expert Client, for example, corrupted graphical data views or missing information, check the screen color bit width of your machine. - Workaround: Change the screen color bit width of your machine from 16 bit to 32 bit. 1.3.2.13 Problem: You can connect to a Performance Warehouse from the Performance Warehouse client from the toolbar on the System Overview window in Performance Expert Client. If you do this, the following error message might be issued: "SYSIBM.SQLTABLES" (specific name "TABLES") has returned an error SQLSTATE with diagnostic text "SYSIBM:CLI:-805". SQLSTATE=38553 - Workaround: Log on as the DB2 instance owner to the system on which Performance Expert Server runs and switch to the bnd directory of the DB2 instance on which Performance Expert Server runs. Connect to the performance database that contains the Performance Warehouse and enter the following commands: db2 bind db2clipk.bnd db2 bind db2clist.bnd db2 bind db2schema.bnd Connect again to the Performance Warehouse from the Performance Warehouse client. 1.3.2.14 Problem: If you have installed Performance Expert Agent on a Windows machine with DB2 V8 and DB2 9 instances, the Agent Configuration Utility can only display DB2 V8 or DB2 9 instances for configuration depending on the setting of the DB2INSTANCE environment variable. - Workaround: For example, if the environment variable DB2INSTANCE is set to a DB2 V8 instance, the Agent Configuration Utility shows all DB2 V8 instances. To configure DB2 9 instances, set the environment variable DB2INSTANCE to a DB2 9 instance and call the Agent Configuration Utility again. 1.3.2.15 Problem: If you use Performance Expert Server on Windows and if you want to enable or use CIM for a monitored DB2 instance, you get the DB2 error message SQL0444 that the library fpecim328*.dll cannot be accessed if the bin directory of Performance Expert Server installation is not available in the PATH system environment variable. - Workaround: Complete these steps: a. Add the Performance Expert Server installation bin directory to the PATH system environment variable. b. Restart the DB2 instance on which Performance Expert Server runs. c. Retry to enable or use CIM for a monitored DB2 instance. 1.3.2.16 Problem: If you have enabled deadlock event exception processing for a multipartitioned database and if you have set the event monitor settings to 'Deadlock event monitor ON with details and history' or to 'Deadlock event monitor ON with details and history values' then the following problem might occur if applications are active that are executing large transactions: The number of DB2 FCM buffers might not be sufficient for internal communication among partitions depending on the size of the transaction. Performance Expert Server then deactivates the deadlock event monitor temporarily for this database and tries to reactivate it again later. In the worst case the lack of FCM buffers might cause a database hang. This is a known DB2 problem and can occur on DB2 V8 and DB2 9. - Workaround: Do one of the following: 1) In peconfig set the deadlock event monitor settings for this database to 'Deadlock event monitor ON with details' only. 2) Increase the number of FCM buffers (FCM_NUM_BUFFERS) in the database manager configuration of the monitored instance accordingly depending on the size of the transactions performed in the monitored database. 1.3.2.17 Problem: If you get blank screens in Performance Expert Client on Windows then this might occur due to a known GUI optimization problem in Java. - Workaround: If this happens too often then GUI painting acceleration can be turned off by adding the following string to the call string in db2pe.bat: -D sun.java2d.nodraw=true The file db2pe.bat is located in the bin directory of the Performance Expert client installation. The string must be inserted after the following string separated by a blank: -D java.util.prefs.syncInterval=2000000 1.3.2.18 Problem: Unexpected errors during installation of Performance Expert on Windows might occur due to too many existing temporary files and directories written by the installer. Workaround: Delete the temporary files and then try the installation again. The temporary files are located in the directory C:\Documents and Settings\\Local Settings\Temp. The temporary directories that should be deleted have the name 'ismp*' where * can be any number. The temporary files that should be deleted have the name 'isp*.tmp' where * can be any number. 1.4 Enhancements Performance Expert V2.2.3 contains the following enhancements: The System Overview window, which is the main window in Performance Expert Client, has been redesigned to provide a quick but comprehensive overview of the performance of your DB2 systems. In addition to data views and exceptions, it now also shows the main performance counters as key performance indicators (KPIs). You can find and index attributes in the item-type tables of a Content Manager Library Server database that should be indexed. For counters and system parameters for which data is stored in the Performance Warehouse database, you can now perform an ad-hoc, long-term analysis that gives you long term statistical information and visualization of the selected counter or parameter. This includes trend information and trend forecast. The text of an SQL statement, which is shown in various windows, is now always displayed in full length and can be viewed in a separate window. 2.0 PREREQUISITES Performance Expert has hardware and software requirements. They are described in detail in 'Installation and Configuration', SC18-9191-06. Refer to this web site to download DB2 tools publications: http://www.ibm.com/software/data/db2imstools/db2tools-library.html 2.1 Hardware requirements For information about hardware requirements, refer to the following chapters in 'Installation and Configuration', SC18-9191-06: - Installing Performance Expert Client on Windows - Installing Performance Expert Server on Windows - Installing Performance Expert Agent on Windows - Installing Performance Expert Client on UNIX and Linux systems - Installing Performance Expert Server on UNIX and Linux systems - Installing Performance Expert Agent on UNIX and Linux systems - Space requirements for Performance Expert Server 2.2 Software requirements 2.2.1 Windows, UNIX, and Linux systems For information about software requirements, refer to the following chapters in 'Installation and Configuration', SC18-9191-06: - Installing Performance Expert Client on Windows - Installing Performance Expert Server on Windows - Installing Performance Expert Agent on Windows - Installing Performance Expert Client on UNIX and Linux systems - Installing Performance Expert Server on UNIX and Linux systems - Installing Performance Expert Agent on UNIX and Linux systems The minimum DB2 requirements for Performance Expert and for the monitored DB2 instance are DB2 V8.1 Fix Pack 9 or later, or DB2 9 or later. The required DB2 editions, however, are different for Performance Expert Server, Client, and Agent. This is described in detail in the chapters listed above. 2.2.2 AIX Pegasus CIM Server If you want to integrate operating system data in Performance Expert and if your monitored DB2 instance resides on AIX, an open-source implementation of the Common Information Model Object Manager (CIMOM), called Pegasus Version 2.5 or later, of AIX Expansion Pack 5.2.7, or AIX Expansion Pack 5.3.3 must be installed and running. The expansion packs are contained on the CD with the label LCD4-1163-14 for AIX 5.2, and on the CD with label LCD4-7477-04 for AIX 5.3. For more information, see this Web site: http://www.ibm.com/servers/aix/expansionpack/ 3.0 INSTALLATION INSTRUCTIONS 3.1. General notes These installation instructions describe briefly how to install and configure Performance Expert. For a more detailed description and for migration procedures, read the installation chapters in 'Installation and Configuration', SC18-9191-06. For information about DB2 tools publications, refer to this Web site: http://www.ibm.com/software/data/db2imstools/db2tools-library.html Performance Expert Client V2.2.3 can run with an earlier Performance Expert Server, but Performance Expert Server V2.2.3 cannot run with an earlier Performance Expert Client. If you plan to migrate your Performance Expert installation to Performance Expert V2.2.3 and if you plan to install Performance Expert Client V2.2.3 and Performance Expert Server V2.2.3 on different dates, install Performance Expert Client V2.2.3 first. Before you install Performance Expert Server V2.2.3, a base version V2.2.0 or V2.2.1 is prerequisite. If you do not have the base version installed and configured, see the installation and configuration chapters in 'Installation and Configuration', SC18-9191-06, for instructions. The installation of Performance Expert Agent is optional. Install Performance Expert Agent on a system on which DB2 Connect runs to monitor Database Connection Services (DCS) connections within the Distributed Relational Database Architecture (DRDA(R)) of DB2. Otherwise skip the installation of Performance Expert Agent. 3.2 UNIX-specific and Linux-specific installation information This section lists brief instructions about how to install and configure Performance Expert on UNIX and Linux systems. For a detailed description, see the following chapters in 'Installation and Configuration', SC18-9191-06: - Configurations for Performance Expert - Installing Performance Expert Client on UNIX and Linux systems - Installing Performance Expert Server on UNIX and Linux systems - Configuring Performance Expert Server on UNIX and Linux systems 3.2.1 Performance Expert Server Step 1: The installer requires Java 1.4. Check if Java 1.4 is installed on the machine. If it is not installed, install the jar file that is delivered with the installation files of Performance Expert Server. Then, enter the following command as root: jar -xvf For example: jar -xvf aix32.jar cd < installed Java path> chmod -R 755 If Java is not installed, copy the jar file to a zip file and use an unzip utility to extract it. Ensure that the jar files for your platform are located in the same path as the installation files. Step 2: Install Performance Expert Server by issuing one of the following commands as root and follow the instructions: db2pe.server.v2.2.3.install-on-aix db2pe.server.v2.2.3.install-on-solaris db2pe.server.v2.2.3.install-on-xlinux db2pe.server.v2.2.3.install-on-zlinux db2pe.server.v2.2.3.install-on-plinux db2pe.server.v2.2.3.install-on-hpux To use the console mode instead of the graphical mode, add the following option to the program call: -console During installation the installer suggests the installation directory of an existing Performance Expert Server installation. Either accept this or, if you have multiple Performance Expert Server installations, specify a directory of a different existing installation of Performance Expert Server V2.2.0 or later. Step 3: Update the DB2 instance for Performance Expert Server by entering the following command as root from the bin directory of your installation, for example, /opt/IBM/db2pesrv/bin: ./pecentralize db2inpe Change instance name 'db2inpe' as required. This step is necessary to generate new timezone codes. See also step 5. Step 4: You can now start the configured Performance Expert Server. As the DB2 instance owner, enter the following command from the bin directory of your installation, for example, /opt/IBM/db2pesrv/bin: ./pestart Step 5: During the start of Performance Expert Server, existing Performance Expert Server configurations are migrated. Because some time zone codes are no longer supported, they are migrated to new regional names. See section 4.8 in this README for information about how to check if your time zone codes are migrated correctly. Step 6 (Optional): During the first start of the Performance Expert Server some new indexes are created in the existing performance databases. Performance Expert takes the best advantage from the new indexes after runstats was executed. The performance database are configured for automatic runstats by default but if you want to execute runstats immediately you can use the script perunstats.ddl which is available in the bin directory of your Performance Expert Server installation. 3.2.1.1 Performance Expert Server first time configuration 3.2.2 Performance Expert Client Step 1: The installer requires Java 1.4. Check if Java 1.4 is installed on the machine. If it is not installed, install the jar file that is delivered with the installation files of Performance Expert Client. Then, enter the following command as root: jar -xvf For example: jar -xvf aix32.jar cd < installed Java path> chmod -R 755 If Java is not installed, copy the jar file to a zip file and use an unzip utility to extract it. Ensure that the jar files for your platform are located in the same path as the installation files. Step 2: Install Performance Expert Client by entering one of the following commands as root and follow the installation instructions: db2pe.client.v2.2.3.install-on-aix db2pe.client.v2.2.3.install-on-solaris db2pe.client.v2.2.3.install-on-xlinux db2pe.client.v2.2.3.install-on-plinux To use the console mode instead of the graphical mode, add the following option to the program call: -console Step 3: You can now start Performance Expert Client by entering the following command from the bin directory of your installation, for example, /opt/IBM/db2pecli/V2.2.3/bin: ./db2pe To use the function 'New DB2 System' in Performance Expert Client, ensure that the user who starts Performance Expert Client has SYSADM or SYSCTRL authority on the DB2 instance on which Performance Expert Client runs. This authority is required to catalog and uncatalog databases. 3.2.3 Performance Expert Agent Step 1: The installer requires Java 1.4. Check if Java 1.4 is installed on the machine. If it is not installed, install the jar file that is delivered with the installation files of Performance Expert Agent. Then, enter the following command as root: jar -xvf For example: jar -xvf aix32.jar cd < installed Java path> chmod -R 755 If Java is not installed, copy the jar file to a zip file and use an unzip utility to extract it. Ensure that the jar files for your platform are located in the same path as the installation files. Step 2: Install Performance Expert Agent by issuing one of the following commands as root and follow the instructions: db2pe.agent.v2.2.3.install-on-aix db2pe.agent.v2.2.3.install-on-hpux db2pe.agent.v2.2.3.install-on-solaris db2pe.agent.v2.2.3.install-on-xlinux db2pe.agent.v2.2.3.install-on-zlinux db2pe.agent.v2.2.3.install-on-plinux To use the console mode instead of the graphical mode, add the following option to the program call: -console Step 3: This step is only necessary if you install Performance Expert Agent for the first time. Register a performance database of a Performance Expert Server into which Performance Expert Agent inserts the collected data by entering the following command as root from the bin directory of your installation, for example, /opt/IBM/db2peage/V2.2.3/bin: ./db2peage-config Step 4: You can now start Performance Expert Agent. As the DB2 instance owner of the DB2 instance on which Performance Expert Agent should run, enter the following command from the bin directory of your installation, for example,/opt/IBM/db2peage/V2.2.3/bin: ./e2e --start 3.3 Windows-specific installation information This section lists brief instructions about how to install and configure Performance Expert on Windows. For a more detailed description, see following chapters in 'Installation and Configuration', SC18-9191-06: - Configurations for Performance Expert - Installing Performance Expert Client on Windows - Installing Performance Expert Server on Windows - Configuring Performance Expert Server on Windows 3.3.1 Performance Expert Server Step 1: The installer requires Java 1.4. Check if Java 1.4 is installed on the machine. If it is not installed, install the jar file that is delivered with the installation files of Performance Expert Server. Then, enter the following command: jar -xvf For example: jar -xvf win32.jar If Java is not installed, copy the jar file to a zip file and use an unzip utility to extract it. Ensure that the jar files for your platform are located in the same directory as the installation files. Step 2: Install Performance Expert by issuing one of the following commands as administrator user and follow the installation instructions: db2pe.server.v2.2.3.install-on-win.exe During the installation, the installer suggests the installation directory of an existing Performance Expert Server installation. Either accept this or, if you have multiple Performance Expert Server installations, specify a directory of a different existing installation of Performance Expert Server V2.2.0 or later. Perform step 3 only if you have installed, but not yet configured and used a base version of Performance Expert. Otherwise, continue with step 4 after the installation. Step 3: Configure Performance Expert Server in one of the following ways: - Select the configuration from the Performance Expert Server program menu. - Open a Command Prompt window and enter the following command from the bin directory of your Performance Expert Server installation: peconfig Step 4: Start Performance Expert Server. Step 5: During the start of Performance Expert Server, existing Performance Expert Server configurations are migrated. Because some time zone codes are no longer supported, they are migrated to new regional names. See section 4.8 in this README for information about how to check if your time zone codes are migrated correctly. Step 6 (Optional): During the first start of the Performance Expert Server some new indexes are created in the existing performance databases. Performance Expert takes the best advantage from the new indexes after runstats was executed. The performance database are configured for automatic runstats by default but if you want to execute runstats immediately you can use the script perunstats.ddl which is available in the bin directory of your Performance Expert Server installation. 3.3.2 Performance Expert Client Step 1: The installer requires Java 1.4. Check if Java 1.4 is installed on the machine. If it is not installed, install the jar file that is delivered with the installation files of Performance Expert Client. Then, enter the following command: jar -xvf For example: jar -xvf win32.jar If Java is not installed, copy the jar file to a zip file and use an unzip utility to extract it. Ensure that the jar files for your platform are located in the same directory as the installation files. Step 2: Install Performance Expert Client by entering the following command and follow the installation instructions: db2pe.client.v2.2.3.install-on-win.exe Step 3: Start Performance Expert Client. To run 'New DB2 System' in Performance Expert Client, ensure that the user who starts Performance Expert Client has SYSADM or SYSCTRL authority on the DB2 instance. This authority is required to catalog and uncatalog databases. 3.3.3 Performance Expert Agent Step 1: The installer requires Java 1.4. Check if Java 1.4 is installed on the machine. If it is not installed, install the jar file that is delivered with the installation files of Performance Expert Agent. Then, enter the following command: jar -xvf For example: jar -xvf win32.jar If Java is not installed, copy the jar file to a zip file and use an unzip utility to extract it. Ensure that the jar files for your platform are located in the same directory as the installation files. Step 2: Install Performance Expert Agent by issuing the following command as an administrator user and follow the installation instructions: db2pe.agent.v2.2.3.install-on-win.exe During the installation, you can configure Performance Expert Agent. Configuring Performance Expert Agent is only necessary if you install Performance Expert Agent for the first time. To configure Performance Expert Agent after the installation, perform Step 3. Step 3: If not already done during Step 2, configure Performance Expert Agent by selecting the configuration from the Performance Expert Agent program menu. Step 4: You can now start the Performance Expert Agent service from the Windows Control Panel -> Administrative Tools -> Services. Right-click DB2 Performance Expert Agent service and click Start. 4.0 CONFIGURATION AND USAGE INSTRUCTIONS 4.1 Enabling access to a CIM Server To collect operating system data by using a CIM Server, you must install, configure, and run a CIMOM version on the monitored DB2 instance. How to do this is described in 'Installation and Configuration', SC18-9191-06, in Chapter 4 for Windows, and in Chapter 10 for UNIX and Linux systems. If you migrate from Performance Expert V2.1 to V2.2.3 and if you want to collect operating system data for a monitored DB2 instance, you must also change the configuration of the monitored DB2 instance. The reason is that the default setting to access the CIM Server is set to 'No' when you migrate the configuration data. To change the configuration, configure Performance Expert Server in one of the following ways: - By using the configuration GUI: Select 'Use CIM to retrieve operating system data.' This is described in Chapter 16 of 'Installation and Configuration', SC18-9191-06. - By using the command line utility: Answer the following question with 'Y': 'Do you want to configure access to CIMOM (Y/N)' This is described in Chapter 15 of 'Installation and Configuration', SC18-9191-06. 4.2 CIM Server 4.2.1 Retrieving process information about Performance Expert Client If you monitor a DB2 instance that is located on an AIX or a Linux machine, and if CIM is enabled, note the following: If you check 'Receive process information' on the window Operating System Status -> Processes, all running processes are displayed. The field 'CPU Usage %' shows only N/P values in online mode. It shows real usage values if you switch to history mode. 4.3 Using Performance Expert with DB2 V8 Fix Pack 9 or later DB2 Version 8 Fix Pack 9 or later no longer supports SERVER authentication of a DB2 client if the database manager parameter AUTHENTICATION of the DB2 server is set to SERVER_ENCRYPT. Performance Expert supports this DB2 change, but under certain conditions, you might get an authentication error if DB2 V8 Fix Pack 9 or later is used for the monitored DB2 instances or for the DB2 instance on which Performance Expert Server runs. The authentication error message can be: SQL30082N Attempt to establish connection failed with security reason "17" ("UNSUPPORTED FUNCTION"). SQLSTATE=08001 The conditions and solutions are: Conditions for Performance Expert Client: 1) The database manager configuration parameter AUTHENTICATION is set to SERVER_ENCRYPT for the DB2 V8 Fix Pack 9 instance or later on which Performance Expert Server runs, and you have migrated from Performance Expert V2.1 or still use it. The authentication error appears on your Performance Expert Clients. Solution for 1): On your Performance Expert Clients, you must recatalog the performance databases of Performance Expert Server to change the authentication to one that is compatible with SERVER_ENCRYPT. After installing Performance Expert Client Version 2.2.3, perform this step before starting Performance Expert Client: As a user with DB2 administration rights (SYSADM) on Performance Expert Client, change to the bin directory of your Performance Expert Client Version 2.2.3 installation and enter the following command to recatalog the Performance Expert databases: java -jar recatdb.jar Ensure that Java 1.4.2 is called by adding it to your PATH variable or by fully qualifying the java call. For example, on Windows enter the following command: "c:\Program Files\IBM\IBM DB2 Performance Expert V2\java142\jre\ bin\java" -jar recatdb.jar Conditions for Performance Expert Server: 2) The database manager configuration parameter AUTHENTICATION is set to SERVER_ENCRYPT for the monitored DB2 instances of DB2 V8 Fix Pack 9 or later, and you have migrated from Performance Expert V2.1 or still use it. The authentication error appears on your Performance Expert Server. Solution for 2): On your Performance Expert Server, you must recatalog the monitored databases to change the authentication to one that is compatible with SERVER_ENCRYPT. As a user with DB2 administration rights (SYSADM) on the DB2 instance where the Performance Expert Server runs, change to the bin directory of your Performance Expert Server Version 2.2.3 installation and invoke the following command to recatalog the databases that Performance Expert monitors: java -jar recatdb.jar Ensure that Java 1.4.2 is called by adding it to your PATH variable or by fully qualifying the java call. Ensure that you access a 32-bit or 64-bit Java version, depending on whether the DB2 instance on which Performance Expert Server runs is a 32-bit or a 64-bit version. For example, on UNIX in ksh shell, export the PATH variable by entering the following command: export PATH=/opt/IBM/db2pesrv/java142/jre/bin:$PATH On UNIX, additionally ensure that the library search path environment variable contains the bin directory of the Performance Expert Server installation and the lib directory of the DB2 Version 8 Fix Pack 9 or later installation. Set the environment variable before calling the recatalog tool, for example, by entering the following command in ksh shell on AIX: export LIBPATH=/opt/IBM/db2pesrv/bin:/usr/opt/db2_08_01/ lib:$LIBPATH Note that the name of the environment variable is different for these UNIX systems: - On AIX: LIBPATH - On Linux, Solaris, and HP/UX (64 bit): LD_LIBRARY_PATH - On HP/UX (32 bit): SHLIB_PATH. 4.4 Using the IBM DB2 Content Manager threshold set Performance Expert provides a predefined threshold set, called 'IBM Content Manager'. You can use this threshold set if you monitor Content Manager (CM) DB2 databases, such as the Library Server (LS) or a Resource Manager (RM) database. Note that the thresholds are based on settings for a mid-sized to large-sized system and might need adjustments for your environment. If you monitor operating system parameters by using Performance Expert, you might want to add the following additional threshold: Exception Category: Operating System Subcategory: Storage Exception Field: Free Space Qualifier: Volume Name for the following items: LS and RM database (if SMS table spaces are used), RM Staging Area (if LAN cache is used) and RM LBOSDATA. For the RM Staging Area, the threshold values should be lower than the value that is defined in the purger setting of the CM System Administration Client. 4.5 Reducing data volume for SQL activity tracing If you use the SQL activity tracing feature, a large amount of data is collected by a statement event monitor that is started on your monitored DB2 instance. You can limit the amount of the collected data if your monitored DB2 instance runs on DB2 9. Set the following registry variable on your monitored DB2 instance: db2set DB2_EVMON_STMT_FILTER= ALL This variable causes the SQL activity tracing to skip the single fetch operations. Depending on the ratio of fetch operations, this can reduce the data volume of SQL activity traces significantly, which speeds up loading of the data into Performance Warehouse and the generation of SQL activity trace reports. 4.6 Workload generator pedemo The Performance Expert Server installation bin directory includes a workload generator called 'pedemo' for sample and demo purposes. Note that this workload generator is meant for sample and demo purposes only and therefore support for it is not provided. Call 'pedemo -help' to get usage information. If you call pedemo without any options, a subset of all available scenarios is started in the local PEDEMO database. 4.7 Impact of Daylight Saving Time changes A provision of the US Energy Policy Act of 2005 extends Daylight Saving Times (DST) by four weeks, beginning in 2007. Systems and applications that process dates and times will be affected by this change. For more general information, see the following Web site: http://www.ibm.com/support/alerts/daylightsavingstimealert.html Performance Expert V2.2.3 already includes the new DST. If you use Performance Expert V2.2.3, you do not have to update the time zone information in Performance Expert. If you want to continue to use a previous level of Performance Expert, see the following Technote for updating the time zone information used in Performance Expert: http://www-1.ibm.com/support/docview.wss?rs=434&context=SSZJXP&dc=D600&uid=swg21249638&loc=en_US&cs=utf-8&lang=en 4.8 Impact of time zone code changes Because 2-digit or 3-digit values for time zone codes are no longer supported, they are migrated to the new correct values during the first start of Performance Expert Server V2.2.3, that is the regional names for the time zones. Each time zone code might have several regional names. For example, CET for Central European Time has several regional names, such as Europe/Paris or Europe/Rome. You must now ensure that the regional name for each monitored DB2 instance is correct. To check the correctness, complete these steps: a. On Linux or UNIX make sure that you have called pecentralize before starting Performance Expert Server. b. Start the peconfig program in GUI mode or in console mode. c. Check for each monitored DB2 instance that the regional name of the time zone is correct. The timezone_codes.txt file contains the time zone values and their regional names. It is located in the bin subdirectory of the installation directory in which Performance Expert Server is installed. For detailed information about how to start the peconfig program, refer to the latest Installation and Configuration information for Performance Expert for Multiplatforms on this Web site: http://www-306.ibm.com/software/data/db2imstools/db2tools-library.html 4.9. Viewing the trend for a counter with a certain range validity If you want to view the trend or trend forecast by right-clicking a counter in Statistics Details and choosing 'Analyze Performance Warehouse History' then it may occur that displayed trend or trend forecast values are out of scope of the range validity of this counter. For example, this may happen for percentage values like Buffer Pool Hit Ratio that have a valid range between 0% and 100%. This happens due to a technical limitation that range validity constraints are not reflected in the statistical algorithms that perform the trend and trend forecast calculation in Performance Expert. 5.0 CORRECTIONS TO DOCUMENTATION For a complete list of documentation enhancements see the section 'Summary of changes' in 'Installation and Configuration', SC18-9191-06, and to the section 'Summary of changes' in 'Monitoring Performance from the Workstation', SC18-9584-03. To obtain the latest refresh of DB2 Performance Expert publications see this Web site: http://www.ibm.com/software/data/db2imstools/library.html 6.0 HOW TO GET HELP For complete and up-to-date source of Performance Expert information, including information about issues discovered after this README was published, go to the following Web site: Performance Expert Online Support: http://www.ibm.com/software/data/db2imstools/support.html If you cannot find an answer to your question searching this Web site, call 1-800-IBM-SERV to speak to an IBM representative for assistance. For Fix Packs to be installed before using the program, see the following Web site: http://www.ibm.com/software/data/db2imstools/support/fixpaks.html For a redbook about Performance Expert, see the following web site: http://www.redbooks.ibm.com/abstracts/sg246470.html 7.0 NOTICES This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10594-1785 U.S.A. For license inquiries regarding double-byte character set (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106, Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this publication to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. Licensees of this program who want to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation J74/G4 555 Bailey Avenue San Jose, CA 95141-1003 U.S.A. Such information may be available, subject to appropriate terms and conditions, including, in some cases, payment of a fee. The licensed program described in this information and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurement may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements, or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility, or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM's application programming interfaces. 7.1 Use of evaluation program If you are using an evaluation copy of the program, the following terms apply: This program contains a disabling device that will prevent it from being used upon expiration of this license. You will not tamper with this disabling device or program. You should take precautions to avoid any loss of data that might result when the program can no longer be used. See the License Agreement for a complete explanation of the terms that apply. 7.2 Trademarks and service marks The following terms are trademarks or service marks of the IBM Corporation in the United States, other countries, or both: AIX DB2 IBM OMEGAMON Tivoli z/OS Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a trademark of Linus Torvalds in the United States, other countries, or both. Other company, product and service names may be trademarks or service marks of others. (C) Copyright IBM Corporation 2003, 2007. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.