fIBM(R) DB2(R) Performance Expert for Multiplatforms, V3.1.1 IBM DB2 Performance Expert for Content Manager, V3.1.1 IBM DB2 Performance Expert for Workgroups, V3.1.1 Fix Pack 1 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 prerequisites 2.2 Software prerequisites 3.0 INSTALLATION INSTRUCTIONS 3.1 General notes 3.2 Linux(R)-specific and UNIX(R)-specific installation information 3.3 Windows(R)-specific installation information 4.0 CONFIGURATION AND USAGE INSTRUCTIONS 4.1 CIM Server 4.2 Using the IBM Content Manager threshold set 4.3 Reducing data volume for SQL activity tracing 4.4 Workload generator 'pedemo' 4.5 Viewing the trend for a counter with a certain range validity 4.6 Calculating the disk space for the performance database 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 the IBM DB2 Performance Expert, Version 3, Release 1, Fix Pack 1 README file of 5 June 2008. 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 Content Manager, and IBM DB2 Performance Expert for Workgroups 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 APAR PK56540: DELTA/INTERVAL COUNTER VALUES IN DYNAMIC SQL STATEMENTS PANEL OF PE CLIENT CALCULATED INCORRECTLY. APAR PK57355: DB2PE RECEIVES A SQL0450N MESSAGE IN THE PMGET STORED PROCEDURE APAR PK58988: DB2 PE RECEIVES "SQL0104N AN UNEXPECTED TOKEN "LOCALEVMONNAME001FOR STATEMENTS WRITE T O" WAS FOUND FOLLOWING "LESIZE 150... APAR PK60189: INCORRECT MESSAGE DATA IN DB2 PERFORMANCE EXPERT V2 TO V3 DATA MIGRATION APAR PK58138: PATH TO EXPORT TABLES TO CANNOT BE CHANGED PROPERLY APAR PK61239: NO VALID DB2 INSTALLATION IS FOUND DURING INSTALL OF DB2 PERFORMANCE EXPERT V3.1 APAR PK61115: DB2 PERFORMANCE EXPERT VER 3.1 THE 'CONTAINER NAME' FIELD IN THE PE CLIENT STATISTIC DETAIL PANEL IS TRUNCATED APAR PK56315: DB2 PERFORMANCE EXPERT SERVER RECEIVES ERROR SQL0407N WHEN PMGET TRIES TO INSERT DATA INTO 'DB2PM.PROGRESS' TABLE APAR PK56317: DB2 PERFORMANCE EXPERT SERVER RECEIVES ERROR SQL0407N WHEN PMGET TRIES TO INSERT DATA INTO 'DB2PM.PROGRESS' TABLE APAR PK56515: DB2 PERFORMANCE EXPERT DOES NOT CHECK CONDITION DEFINITIONS WHEN DEFINING A THRESHOLD TO BE MONITORED. APAR PK46628: UTILITY NODE DETAILS MISSING IN DB2 PERFORMANCE EXPERT CLIENT APAR PK62059: DB2 PERFORMANCE EXPERT RECEIVES ERROR SQL0407N WHEN PMGET TRIES TO INSERT DATA INTO 'DB2PM.DYNSQL' TABLE APAR PK62628: NO GRAPHS IN SYSTEM OVERVIEW OF PE CLIENT, BUT THE SAME GRAPHS ARE DISPLAYED IN SYSTEM HEALTH APAR PK61385: "PWHLOAD ERROR: SQL0413N OVERFLOW OCCURRED" ERROR MESSAGE SEEN IN DB2PESRV.LOG APAR PK65123: PE CLIENT DATA VIEWS HAVE EMPTY GRAPHS FOR SOME COLLECTED COUNTERS APAR PK65887: DB2 PE MONITORED INSTANCES FORCED OFFLINE DURING RECOVERY RESTART APAR PK66136: DB2 PERFORMANCE EXPERT SHOWS WRONG PERCENTAGE IN DISTRIBUTION OF USED SPACE BY ACTIVE PARTITION GRAPH APAR PK69809: THE PE CLIENT DISPLAYS THE DGOK1472 MESSAGE AND THE DETAILS SHOW THAT THE JCC DRIVER RAISED AN EXCEPTION FOR A CHARACTER CONVERSION. (Reference section 1.3.2.30 for additional information). 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 a Linux system, an AIX(R) system, or a Solaris system, you cannot enable CIM if the host name of the monitored system 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 The configured remote directory on the monitored system that contains the shared library fpeevm of Performance Expert must have read permission, write permission, and execute permission for the DB2 instance owner, the fenced user, and the group (777) if all of these conditions apply: a) You use DB2 V9 Fix Pack 2 on your monitored Linux or UNIX system. b) You have set the DB2 registry variable DB2_LIMIT_FENCED_GROUP to YES. c) You have configured Performance Expert to use database objects to exchange event monitor files. 1.3.1.4 The installation of Performance Expert Client is supported only on Linux on xSeries(R) and on Windows. For more information about software prerequisites, see 'Installation and Configuration', SC19-1174-01. 1.3.1.5 The installation of Performance Expert on a 32-bit DB2 instance is supported only on Linux on xSeries and on Windows. If you, however, monitor a DB2 V8 instance, this monitored instance can be a 32-bit DB2 instance on any supported platform. For more information about software prerequisites, see 'Installation and Configuration', SC19-1174-01. 1.3.1.6 It is not supported to install Performance Expert Server, Performance Expert Client, or Performance Expert Agent simultaneously on a workstation. Install the components one after the other. The order in which you install the components is arbitrary. 1.3.1.7 If you run Performance Expert Server on DB2 V8, and if you monitor a multipartition DB2 V9.5 instance, the creation of SQL activity reports, SQL PL reports, and WLM activity reports is not supported. 1.3.1.8 For periodic exception processing the filter value 'GLOBAL' for the qualifier 'Partition' is not supported. Only single partition numbers are supported as filter value. 1.3.2 Known problems and workarounds 1.3.2.1 Problem: You get a 'Server Timeout' error message on Performance Expert Client when you request data from a monitored DB2 system. This might happen, for example, if you monitor a multipartition DB2 instance with many partitions, or if you have CIM enabled. Workaround: You can increase the timeout value or try again later. To increase the timeout value, add or modify the parameter hostconnection.timeout in the db2pm.prop file and assign a new timeout value in milliseconds. On Linux on xSeries, the db2pm.prop file is located in the directory $HOME/.db2pev3. On Windows, the db2pm.prop file is located in the directory c:\Documents and Settings\\.db2pev3. If you get the timeout message because you monitor a DB2 instance with many table spaces or many table space containers or because you monitor a multipartition DB2 instance, you can additionally take the steps that are described in the following topics in 'Troubleshooting' of 'Installation and Configuration': 'Collecting table space snapshots takes too long' 'Collecting global snapshots takes too long' 1.3.2.2 Problem: Performance Expert Server might display wrong assignments of objects, such as tables, to databases, record the DB2 error SQL0803N in the db2pesrv.log file several times, and write a lot of data into the temporary directory of Performance Expert Server if the following conditions apply: - You monitor one or more multipartition databases in one DB2 instance. - More than one multipartition database in the DB2 instance is active. - One or all of the following conditions apply: - 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, which is the default, you might also get the error SQL0803N on the Performance Expert Server console and in the db2pesrv.log file. Also, the affected history data is not stored. In this case, there are also a lot of binary files accumulating in the temporary directory. Workaround: Take these steps: a) On Performance Expert Server, connect to the performance database. b) Update the PARAMETER table by using the following SQL statement: UPDATE DB2PM_.PARAMETER SET PA_FLAGVALUE='Y' WHERE PA_KEY='DISABLE_GLOBAL_SNAPSHOT' c) Replace by the instance ID of the monitored DB2 instance for which the problem occurs. To get the instance ID of the monitored DB2 instance, call 'peconfig -list' from the bin directory of the Performance Expert Server installation. After you update the PARAMETER table, no GLOBAL snapshot is taken from the monitored DB2 instance any more. d) In the TEMP (Windows) or /tmp (Linux and UNIX) directory of the Performance Expert Server workstation, delete the files with the following name: snapshot__ 1.3.2.3 Problem: The pecentralize command fails with error 'db2 not found' on Linux and UNIX 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.4 Problem: If you monitor a DB2 instance that is located on an AIX system with CIM enabled, N/P values might be shown in the Operating System Information window if the temporary directory on the monitored system or on the Performance Expert Server workstation is nearly full. Workaround: Free space in the appropriate temporary directory. 1.3.2.5 Problem: Installation and configuration of Performance Expert Server or Performance Expert Client on Linux or UNIX in console mode might cause errors if you correct input data with the backspace key because 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.6 Problem: If CIM is enabled, retrieving data from the CIMOM Server might fail because the host name of the monitored DB2 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. The format must be: Example: 129.10.20.30 myhost.ibm.host.com myhost 1.3.2.7 Problem: If you monitor a DB2 instance that is located on an AIX system 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.8 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 configuration of 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: Take these steps: a) Open the registry editor. b) Set the variable forceguest to the value 0 in the following registration key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa c) Restart the installation. 1.3.2.9 Problem: If you monitor a DB2 instance that is located on an AIX system, and if CIM is enabled, the following limitation exists: The CIM Server might have crashed if these conditions apply 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.10 Problem: If you monitor a DB2 instance that runs on DB2 V8 Fix Pack 11, you might get the message 'An internal error occurred' on 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 DB2 system. This problem is fixed with DB2 APAR LI70768. 1.3.2.11 Problem: If you see corrupted windows on Performance Expert Client, for example, corrupted graphical data views or missing information, the screen color bit width of your workstation might not be correct. Workaround: Change the screen color bit width of your workstation from 16 bit to 32 bit. 1.3.2.12 Problem: When you connect to a Performance Warehouse from the Performance Warehouse client or from the toolbar on the System Overview window of Performance Expert Client, the following error message might occur: "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 of Performance Expert Server and enter these commands: db2 bind db2clipk.bnd db2 bind db2clist.bnd db2 bind db2schema.bnd Then connect again to Performance Warehouse from the Performance Warehouse client. 1.3.2.13 Problem: If you have installed Performance Expert Agent on a Windows system with DB2 V8 instances and DB2 V9 instances, the Agent Configuration Utility can display only DB2 V8 instances or DB2 V9 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 V9 instances, set the environment variable DB2INSTANCE to a DB2 V9 instance and call the Agent Configuration Utility again. 1.3.2.14 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.15 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', the following problem might occur if applications that execute large transactions are active: 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. At the worst, the lack of FCM buffers might cause a database hang. This is a known DB2 problem and can occur on DB2 V8 and on DB2 V9. Workaround: Take one of these steps: - In peconfig, set the deadlock event monitor settings for this database to 'Deadlock event monitor ON with details' only. - Increase the number of FCM buffers (FCM_NUM_BUFFERS) in the database manager configuration of the monitored DB2 instance accordingly, depending on the size of transactions that are performed in the monitored database. 1.3.2.16 Problem: Unexpected errors during installation of Performance Expert on Windows might occur due to too many existing temporary files and directories that are written by the installer. Workaround: Delete the temporary files and restart the installation. The temporary files are located in the directory C:\Documents and Settings\\Local Settings\Temp. The name of the temporary directories that you should delete is 'ismp*' where * can be any number. The name of the temporary files that you should delete is 'isp*.tmp' where * can be any number. 1.3.2.17 Problem: On Performance Expert Client, you get the message 'DGOK1456 DB2 or DB2 Performance Expert Server is not started, the monitored DB2 instance is not enabled or DB2 is not started locally.' In addition to the reasons that you get when you click 'Details' in the Message window, the following reason might be possible: a) You have configured a monitored DB2 instance in Performance Expert Server and Performance Expert Client. b) You have dropped the monitored DB2 instance on Performance Expert Server by using peconfig. c) You have configured it again later. The monitored DB2 instance then gets a new instance ID and when you log on from Performance Expert Client, the error message occurs. Workaround: In the System Overview window of Performance Expert Client, drop the monitored DB instance from the tree. Then add it again by clicking 'Monitor -> New DB2 System'. 1.3.2.18 Problem: During installation of Performance Expert in console mode or silent mode on Linux or UNIX, you might get the following message due to a known problem of the installer: X connection to broken (explicit kill or server shutdown) Workaround: To complete the installation successfully, take these steps: - Export the DISPLAY environment variable so that it points to null or blank, as shown in the following example: export DISPLAY=null - Start the installation again 1.3.2.19 Problem: If you start Performance Expert Client on xLinux, one of the following two error messages occurs: - ./db2pe: line 169: cd: //sqllib/cfg: No such file or directory ls: db2*.lvl: No such file or directory The DB2 Edition you are using is not supported by Performance Expert. - To find the correct DB2 bit width, the file ${HOME}/sqllib/ctrl/.instuse is required. Ensure that your HOME environment variable (${HOME}) points to the correct home location. Workaround: The reason for the error message might be that you have started Performance Expert Client as a user who is not the DB2 instance owner. To start Performance Expert Client as a user who is not the DB2 instance owner, create the following link in the home directory of the user: ln -s /sqllib/ $HOME/sqllib Replace by the name of the home directory of the DB2 instance owner. 1.3.2.20 Problem: On Windows Vista systems, you might not be able to configure Performance Expert Agent because you do not have the required authorizations, or because the creation of folders or files fails. Workaround: Take one of these steps: - Switch off the User Access Control (UAC) before you start to configure Performance Expert Agent. - Run Performance Expert Agent as administrator by taking these steps: a) Click Start -> All Programs -> IBM DB2 Performance Expert Agent. b) Right-click Configure Using the GUI, then click Properties. c) Select the Shortcut tab, then click Advanced. d) Select Run as administrator. e) Click OK. 1.3.2.21 Problem: During the installation of Performance Expert on Linux or UNIX you get the message that no valid DB2 installation is found even if you have a valid DB2 version installed that meets the prerequisites of Performance Expert. Workaround: The reason for the error message might be that the DB2 license file is not correctly linked on your system. To create the link of the DB2 license file, logon as root and execute the following command: ln -s /install/db2ls /usr/local/bin/db2ls Replace .LOADLOG table, where is the instance ID of your monitored DB2 instance as listed in peconfig. 5) Delete the record from the DB2PM_.LOADLOG table by using an SQL DELETE statement. The entire collected data is deleted because the tables are created with the DELETE CASCADE option. If you still get the error message that the transaction log is full, you might have to increase it further. 1.3.2.23 Problem: If you install Performance Expert on Linux on RHEL5 you get the error message that no valid JRE is found. The installation is then stopped. Workaround: The reason for the error message might be that SELinux is enabled on your Linux system. For the installation of Performance Expert, temporarily disable SELinux before you start the installation and enable it again after the installation is complete. Before you run Performance Expert, execute the following command as root to allow the execution of the Java that is installed by Performance Expert: chcon -R -t texrel_shlib_t /java150 is the path where Performance Expert is installed. 1.3.2.24 Problem: The monitored DB2 instance crashes when Performance Expert takes dynamic SQL snapshots. For DB2 V8, the problem is described in detail in APAR JR22901 on this Web site: http://www-1.ibm.com/support/docview.wss?uid=swg1JR22901 For DB2 V9, the problem is described in detail in APAR IZ06254 on this Web site: http://www-1.ibm.com/support/docview.wss?uid=swg1IZ06254 Workaround: Take one of these steps: - Install the DB2 fix pack that solves the problem according to the APAR description - Disable dynamic SQL snapshots in Performance Expert a) Connect to the performance database of Performance Expert b) Issue the following statement: db2 update DB2PM_.HISTORYDATA set HD_FLAG='N' where HD_DATA='DYNAMICSTATEMENTCACHE' c) Replace by the instance ID of the monitored DB2 instance for which the problem occurs. To get the instance ID of the monitored DB2 instance, call 'peconfig -list' from the bin directory of the Performance Expert Server installation. 1.3.2.25 Problem: Creating a WLM Activity Summary Report takes a very long time even if you specify a short time period as elapsed time. The problem might occur if you start the WLM Acitivity Summary Report from the WLM window of Performance Expert Client or from Performance Warehouse. Workaround: To create the WLM Activity Summary Report, Performance Expert activates the ACTIVITY event monitor on the monitored system. The report is not created before the event monitor is completely deactivated. The deactivation step can take a long time (one hour or more) depending on the amount of activity that the event monitor has collected. The problem is a DB2 problem and is described in APAR IZ19170. The APAR should be fixed in DB2 V9.5 Fix Pack 2. 1.3.2.26 Problem: The historical data of Performance Expert Server has gaps. No data was collected in a specific time frame although Performance Expert Server was running and databases of the monitored DB2 instance were active. Workaround: Possible reasons for the gaps: 1) In Performance Expert Client you have enabled history data collection for 'Locking Conflicts'. This collection includes that the LOCKS snapshot is executed against your monitored databases. If a high number of locks exist on the tables of your monitored databases, then a hugh amount of snapshot data is returned to Performance Expert Server that must be evaluated for locking conflicts. This processing takes time and consumes a lot of memory which might lead to memory allocation problems on the Performance Expert Server machine and to gaps in the history. As workaround either increase the interval for 'Locking Conflicts' history data collection or disable it completely. 2) The performance database of Performance Expert Server is set up for automatic maintenance. This means that runstats commands and reorg commands are executed at certain time stamps depending on the setup of the maintenance window. During the execution of runstats commands and reorg commands, the access to the performance database might be limited. This might lead to gaps in the historical data, especially if the runstats commands and reorg commands take a long time. To solve the problem, you can choose different times for the maintenance window. Check the db2diag.log file of the DB2 instance on which Performance Expert Server runs to verify whether runstats operations or reorg operations were responsible for the gaps. 1.3.2.27 Problem: When you use Performance Expert Client on Windows, the dialogs that you get might have a very small font size. Workaround: Disable the usage of system font sizes by changing the following line in the /bin/db2pe.bat file: -DDB2PEJVMOPTIONS="-Djava.util.prefs.syncInterval=2000000 -Dsun.java2d.noddraw=true" to the following line: -DDB2PEJVMOPTIONS="-Djava.util.prefs.syncInterval=2000000 -Dsun.java2d.noddraw=true -Dswing.useSystemFontSettings=false" 1.3.2.28 Problem: After installing DB2 Performance Expert Client V3.1 Fix Pack 1, you can no longer access buffer pool analysis reports for DB2 for Linux, UNIX, and Windows that are created with previous versions of Performance Expert Client. Workaround: Performance Expert Client creates a new folder for your buffer pool analysis reports. The folder name is different to the folder name in previous versions. To access reports that are created with Performance Expert Client V3.1 or previous versions, copy the reports from the previous directory with the name /.db2pev3/-- to the new directory with the name /.db2pev3/-- -- Not that the new directory might not exist. To let Performance Expert Client create it, log on to the corresponding monitored DB2 system by using Performance Expert Client and open Buffer Pool Analysis for MP. 1.3.2.29 Problem: When you monitor a multipartition DB2 instance and have periodic exception processing enabled, you don't get exceptions if you have specified the filter 'Partition=GLOBAL'. Workaround: The value 'GLOBAL' is not supported as filter for the qualifier 'Partition'. Either remove the filter for this qualifier or specify a single partition number as filter. 1.3.2.30 Problem: On Performance Expert Client you get one of the following error messages if you open a window such as Application Summary or Statistic Details, do a refresh on one of these windows or browse in historical data: - Caught java.io.CharConversionException. See attached Throwable for details. ERRORCODE=-4220, SQLSTATE=null, SQLState=, ErrorCode=<-4220>. - Null pointer exception. Error happened : null, SQLState=, ErrorCode=<-99999>. Workaround: The problem is caused by invalid characters available in the snapshot data. As a workaround you can set a property on Performance Expert Client to ignore the invalid characters. If the property is set then the error message is ignored and the string 'INVALID' is displayed for a snapshot value instead. Additionally contact the IBM support to check whether a fix instead of the workaround is already available. To set the property complete the following steps: 1. Close Performance Expert Client 2. On Performance Expert Client open the file db2pm.prop. On Linux on xSeries, the db2pm.prop file is located in the directory $HOME/.db2pev3. On Windows, the db2pm.prop file is located in the directory c:\Documents and Settings\\.db2pev3. 3. Add the property db2pm.jdbc.ignoreConversionErrors=true and save the file 4. Restart Performance Expert Client 1.4 Enhancements Performance Expert V3.1.1 contains the following enhancements: You can log on to one or more selected DB2® instances in history-only mode. This means that Performance Expert Client can access only history data. You can use this mode if the monitored DB2 instance is down or disabled for monitoring or if you monitor a large system with a lot of workload to get a better response time. You can also set the history-only mode as the default logon mode on Performance Expert Client. You can force an application or cancel a single activity from Application in Locking Conflicts or Locking Conflicts on Performance Expert Client. All windows that display snapshots, including the System Overview window and the System Health window, have a new toolbar. This toolbar shows you which performance data you currently view and collect, how the values of performance data are calculated, and how and when data is refreshed. You cannot hide the toolbar. If a DB2 instance is partitioned, you can collect performance data for specific partitions. Performance Expert supplies predefined partition sets for monitoring. However, you can also create your own partition sets that you can use to monitor the partitions of your choice. Partition sets improve performance because Performance Expert Server collects performance data only for a specific number of partitions. In addition, they improve usability because you can, for example, create a partition set that contains only those partitions that have performance problems and later compare the performance data that was collected for these partitions. You can create summary reports on the individual activities of one or more service subclasses or of one or more workloads in a database. Such WLM activity summary reports contain information about the individual activities, including SQL statement text with parameter marker values. In addition, the reports provide information about the workload management objects that were involved in an activity. This can be useful for debugging individual activities or your workload management setup. When you created a service subclass or a work action set, you might not have enabled the collection of aggregate activity data and aggregate request data, or you might have enabled the collection of specific aggregate data only. You can change the settings with regard to the collection of aggregate data for one or more service subclasses and work classes while you view the workload on your databases. If you have many partitions in your database environment, and if you selected the GLOBAL view to see the aggregated data for all database partitions, the collection of global snapshots might take too long. You can disable the collection of global snapshots. If you have many table spaces or many table space containers in your database environment, the collection of table space snapshots or table space container snapshots might take too long. You can disable the collection of snapshots for table spaces or for table space containers. If you monitor DB2 V9.5, the following new snapshot counters are available on the Statistics Details Dynamic SQL Statements view: Package Cache ID and Package Cache Entry Time. You can now enable tracing for a single monitored DB2 instance from the Performance Expert Server property file db2pesrv.prop. The instance ID of a monitored DB2 instance is now also displayed in the configuration GUI of the peconfig tool. Additionally, the schema names of he tables that the performance database contains for the monitored DB2 instance are listed in the configuration GUI and in the command line configuration. You can configure in which situations a user exit should be executed. If a new exception occurs, or if a new exception occures and an existing exception is updated or closed. By default, Performance Expert Server V3.1.1 is started with a higher maximum Java heap size than Performance Expert Server V3.1.0, which was 512 MB. For more details see the 'Hardware prerequisites' topic for Performance Expert Server in 'Installation and Configuration', SC19-1174-01. 2.0 PREREQUISITES Performance Expert has hardware and software prerequisites. They are described in detail in 'Installation and Configuration', SC19-1174-01. Refer to this web site to download DB2 tools publications: http://www.ibm.com/software/data/db2imstools/db2tools-library.html. If you install from CD, 'Installation and Configuration' is available on each CD in all supported languages. 2.1 Hardware prerequisites For information about hardware prerequisites, see the following topics in 'Installation and Configuration', SC19-1174-01: - Installing Performance Expert Client on Linux and UNIX systems - Installing Performance Expert Server on Linux and UNIX systems - Installing Performance Expert Agent on Linux and UNIX systems - Installing Performance Expert Client on Windows - Installing Performance Expert Server on Windows - Installing Performance Expert Agent on Windows - Space requirements for Performance Expert Server By default, Performance Expert Server V3.1.1 is started with a higher maximum Java heap size than Performance Expert Server V3.1.0, which was 512 MB. For a Performance Expert Server running on Windows, the maximum Java heap size is set to 768 MB. For a Performance Expert Server running on Linux or UnIX, the maximum Java heap size is set to 1024 MB. Additionally, Performance Expert Server is started with a minimum Java heap size of 128 MB. See the above listed topics for Performance Expert Server to get more information about how to change the maximum Java heap size and the and minimum Java heap size in the pestart scripts (-Xmx and -Xms parameters). 2.2 Software prerequisites 2.2.1 Linux systems, UNIX systems, and Windows systems For information about software prerequisites, see the following topics in 'Installation and Configuration', SC19-1174-01: - Installing Performance Expert Client on Linux and UNIX systems - Installing Performance Expert Server on Linux and UNIX systems - Installing Performance Expert Agent on Linux and UNIX systems - Installing Performance Expert Client on Windows - Installing Performance Expert Server on Windows - Installing Performance Expert Agent on Windows The minimum DB2 requirements for Performance Expert and for the monitored DB2 instance are DB2 V8.1 Fix Pack 9 or later, or DB2 V9 or later. The required DB2 editions, however, are different for Performance Expert Server, Performance Expert Client, and Performance Expert Agent. This is described in detail in the above listed topics. 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, AIX Expansion Pack 5.2.7 or AIX Expansion Pack 5.3.3 with an open-source implementation of the Common Information Model Object Manager (CIMOM), called Pegasus Version 2.5 or later must be installed and running. For AIX 5.2, the expansion packs are contained on the CD with the label LCD4-1163-14. For AIX 5.3, the expansion packs are contained on the CD with the 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 ´topics in 'Installation and Configuration', SC19-1174-01. For information about DB2 tools publications, refer to this Web site: http://www.ibm.com/software/data/db2imstools/db2tools-library.html If you have Performance Expert V2 installed, and if you plan to migrate the Performance Expert V2 performance databases to Performance Expert V3, see the following topics in 'Installation and Configuration', SC19-1174-01, before you start the installation: - Migrating databases of Performance Expert Server Version 2 on Linux and UNIX - Migrating databases of Performance Expert Server Version 2 on Windows Performance Expert Client V3.1.1 can run with an earlier version of Performance Expert Server, for example V3.1 or V2.2.3, but Performance Expert Server V3.1.1 cannot run with an earlier version of Performance Expert Client. Install Performance Expert Client V3.1.1 first if these conditions apply: a) You have Performance Expert V2 installed, and you plan to migrate your Performance Expert V2 installation to Performance Expert V3.1.1 b) You plan to install Performance Expert Client V3.1.1 and Performance Expert Server V3.1.1 on different dates. The installation of Performance Expert Agent is optional. Install Performance Expert Agent on a system on which DB2 Connect(TM) runs to monitor Database Connection Services (DCS) connections within the Distributed Relational Database Architecture(TM) (DRDA(R)) of DB2. Otherwise, skip the installation of Performance Expert Agent. 3.2 UNIX-specific and Linux-specific installation information This section briefly lists the instructions about how to install and configure Performance Expert on Linux and UNIX systems. For a detailed description, see the following topics in 'Installation and Configuration', SC19-1174-01: - Configurations for Performance Expert - Installing Performance Expert Client on Linux and UNIX systems - Installing Performance Expert Server on Linux and UNIX systems - Configuring Performance Expert Server on Linux and UNIX systems 3.2.1 Performance Expert Server Prerequisite: The base package of Performance Expert Server V3.1.0 must be installed. Step 1: Install Performance Expert Server by issuing one of the following commands as root and follow the instructions: db2pe.server.v3.1.1.install-on-aix db2pe.server.v3.1.1.install-on-solaris db2pe.server.v3.1.1.install-on-xlinux db2pe.server.v3.1.1.install-on-zlinux db2pe.server.v3.1.1.install-on-plinux db2pe.server.v3.1.1.install-on-hpux To use the console mode instead of the graphical mode, append the following option to the program call: -console During the installation, the installer suggests the installation directory of an existing Performance Expert Server V3.1.0 installation. Accept this path. Step 2: Take this step only if you have not yet already done so after the installation of Performance Expert Server V3.1.0. Specify 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/v3/bin: ./pecentralize where is the name of the DB2 instance on which Performance Expert Server should run. Step 3: Configure the DB2 instance for Performance Expert Server by adding the monitored DB2 instances. As the DB2 instance owner, enter the following command from the bin directory of your installation, for example, /opt/IBM/db2pesrv/v3/bin: ./peconfig To use the console mode instead of the graphical mode, append the following option to the program call: -console Important: Even if you have configured the DB instance for Performance Expert Server before installing this fix pack, call peconfig so that the changes come into effect in the performance database. The reason is that peconfig also increases several database configuration parameters of the performance database. After you call peconfig, you can exit it without taking any further actions. 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/v3/bin: ./pestart 3.2.2 Performance Expert Client Step 1: Install Performance Expert Client by entering the following command as root and follow the installation instructions: db2pe.client.v3.1.1.install-on-xlinux To use the console mode instead of the graphical mode, append 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/v3/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: Install Performance Expert Agent by issuing one of the following commands as root and follow the instructions: db2pe.agent.v3.1.1.install-on-aix db2pe.agent.v3.1.1.install-on-hpux db2pe.agent.v3.1.1.install-on-solaris db2pe.agent.v3.1.1.install-on-xlinux db2pe.agent.v3.1.1.install-on-zlinux db2pe.agent.v3.1.1.install-on-plinux To use the console mode instead of the graphical mode, append the following option to the program call: -console Step 2: This step is only required if you install Performance Expert Agent for the first time. Register a performance database of a Performance Expert Server into which Performance Expert Agent stores the collected data. To register the performance database, enter the following command as root from the bin directory of your installation, for example, /opt/IBM/db2peage/v3/bin: ./db2peage-config Step 3: 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/v3/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 topics in 'Installation and Configuration', SC19-1174-01: - 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 Prerequisite: The base package of Performance Expert Server V3.1.0 must be installed. Step 1: Install Performance Expert by issuing the following command as the administrator user and follow the installation instructions: db2pe.server.v3.1.1.install-on-win.bat During the installation, the installer suggests the installation directory of an existing Performance Expert Server V3.1.0 installation. Accept this path. Step 2: 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 To use the console mode instead of the graphical mode, append the following option to the program call: -console Important: Even if you have configured the DB instance for Performance Expert Server before installing this fix pack, call peconfig so that the changes come into effect in the performance database. The reason is that peconfig also increases several database configuration parameters of the performance database. After you call peconfig, you can exit it without taking any further actions. Step 3: Start Performance Expert Server. 3.3.2 Performance Expert Client Step 1: Install Performance Expert Client by entering the following command and follow the installation instructions: db2pe.client.v3.1.1.install-on-win.bat Step 2: 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: Install Performance Expert Agent by issuing the following command as the administrator user and follow the installation instructions: db2pe.agent.v3.1.1.install-on-win.bat During the installation, you can configure Performance Expert Agent. To configure Performance Expert Agent after the installation, perform Step 2. Step 2: If not already done during Step 1, configure Performance Expert Agent by selecting the configuration from the Performance Expert Agent program menu. Configuring Performance Expert Agent is only required if you install Performance Expert Agent for the first time. Step 3: 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 CIM Server 4.1.1 Retrieving process information about Performance Expert Client If you monitor a DB2 instance that is located on a Linux system or an AIX system, 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.2 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.3 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 V9. 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.4 Workload generator pedemo The bin directory of the Performance Expert Server installation includes a workload generator called 'pedemo'. It is meant exclusively for sample purposes and demo purposes. 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.5. 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', displayed trend or trend forecast values might be out of scope of the range validity of this counter. For example, this might happen for percentage values, such as Buffer Pool Hit Ratio that have a valid range between 0% and 100%. The reason is a technical limitation that range validity constraints are not reflected in the statistical algorithms that perform the trend calculation and trend forecast calculation in Performance Expert. 4.6 Calculating the disk space for the performance database For a detailed calculation of the disk space that is required for the performance database, read the following topic in 'Installation and Configuration', SC19-1174-01: - Space prerequisites for Performance Expert Server However, if want to install and configure Performance Expert Server before calculating the required disk space in detail, take these steps: 1) During configuration of a monitored DB2 instance, specify a table space that has around 10 GB free space. 2) Start Performance Expert Server. 3) The default time frame for history collection is 50 hours, which is around two days. History data that is older than 50 hours is deleted automatically. If you keep this default, check one day later how much space is consumed in the specified table space path. Thus, you can estimate whether the free space for the second day of history data collection is sufficient. Depending on your estimate, increase the available disk space. For history data collection, the table space SHORTTERM_ is used. 4) Note that history data is aggregated into the Performance Warehouse tables. These tables are located in the LONGTERM_ table space. The data is not deleted automatically, so you can assume that the same amount of data that was collected after one day in the LONGTERM_ table space is collected also on other days. 5.0 CORRECTIONS TO DOCUMENTATION To obtain the latest edition 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-1.ibm.com/support/docview.wss?rs=434&uid=swg27008647 For IBM Redbooks(R) 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 IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. A current list of other IBM trademarks is available on the Web at http://www.ibm.com/legal/copytrade.shtml. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Linux is a trademark of Linus Torvalds in the United States, other countries, or both. Microsoft and Windows 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. Other company, product and service names may be trademarks or service marks of others. © Copyright IBM Corporation 2004, 2008. All Rights Reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.