============================================================= Readme file for: IBM(R) DB2(R) Performance Expert for Linux, UNIX, and Windows Version 3 Release 2 Fix Pack 1 24 March 2009 ============================================================= CONTENTS Copyright statement 1.0 ABOUT THIS README FILE 1.1 Evaluation code 1.2 Corrected problems 1.4 Limitations, known problems, and workarounds 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 Reducing data volume for SQL activity tracing 4.3 Workload generator 'pedemo' 4.4 Viewing the trend for a counter with a specific range validity 4.5 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 © Copyright IBM Corporation 2004, 2009. All Rights Reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. 1.0 ABOUT THIS README FILE This readme file contains information about installing and configuring IBM DB2 Performance Expert for Linux, UNIX, and Windows. It also contains information about known problems. In this readme file, the following naming conventions apply: IBM DB2 Performance Expert for Linux, UNIX, and Windows is abbreviated to Performance Expert where applicable. You can use Performance Expert Client 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 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 The following Performance Expert problems are corrected in fix pack 1: APAR PK73031: THE V31 PE INSTALLATION CODE IS NOT ABLE TO INSTALL BECAUSE PE INSTALLER CAN NOT FIND A VALID DB2 APAR PK69705: SQL0803N PWHLOAD ERROR PWH_X.TABLE IN PESERVER.LOG APAR PK72932: DB2PE RECEIVES A SQL0450N MESSAGE IN THE PMCIMGET STORED PROCEDURE APAR PK66215: DB2 PERFORMANCE EXPERT DOES NOT SHOW DATA VIEWS DATA WHEN DEFAULT REGIONAL SETTINGS IS TURKISH APAR PK66934: UNABLE TO CHANGE THE 'USER LOGON ID' FOR A MONITORED INSTANCE USING PECONFIG CHANGE COMMAND APAR PK64486: DB2 PE HISTORY DATA COLLECTION HAS LONG GAPS IN THE HISTORY DATA AS DISPLAYED IN THE PE CLIENT APAR PK68659: DB2 PE CLIENT TRYING TO SAVE A PEXP DEFINITION FAILS WITH DGOK1468 APAR PK70463: PECONFIG 'CHANGE' SCRIPT DOES NOT SHOW CURRENTLY CONFIGURED PORTNUMBER FOR CIMOM MONITORING APAR PK70635: DB2 PERFORMANCE EXPERT GENERATES I/O FOR PWH_#.TABLE APAR PK68119: "SELECT" RIGHTS ARE MISSING ON DB2PM.PE_SETUP TABLE FOR PE GROUP IN PECENTRALIZE SCRIPT (UNIX) OR DURING INSTALLATION (WINDOWS) APAR PK68363: DB2 PERFORMANCE EXPERT CLIENT GUI DOES NOT HAVE THE SCROLL BAR TO SELECT A DATABASE PARTITION WHEN IT HAS MORE THAN 30 PARTS APAR PK67000: PE PESTOP V3.1 RUNS INTO "KILL SERVER" SCENARIO AND KILLS EVERYTHING, INCLUDING PE V2.2 APAR PK64481: DB2 PERFORMANCE EXPERT RECEIVES DARI ERROR WHEN THE PE STORED PROCEDURE DOES NOT HAVE MEMORY AVAILABLE FROM OPERATING SYSTEM. APAR PK71202: SQL0803N PWHLOAD ERROR PWH_X.TABLE IN PESERVER.LOG APAR PK69809: THE PE CLIENT RECEIVES A DGOK1472 MEASSGE APAR PK68215: DB2 PE CLIENT FAILS TO BE ABLE TO LOGON TO ANY INSTANCE AFTER ADDING A NEW INSTANCE WITH PECONFIG APAR PK73881: 'PECONFIG RESTART' command fails APAR PK72730: DB2 PERFORMANCE EXPERT PESERVER: TERMINATING :ERROR WHILE TAKING HISTORY SNAPSHOT. SQLCODE: -1131 APAR PK76316: DB2 PERFORMANCE EXPERT DELHISTORY SCRIPT SHOWS ERROR SQL3201N APAR PK79742: DB2 PERFORMANCE EXPERT HANGS WHEN USING BUFFERPOOL REPORT GENERATION 1.4 Limitations, known problems, and workarounds 1.4.1 Limitations 1.4.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 Common Information Model (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.4.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.4.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.4.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', GC19-2503-00. 1.4.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', GC19-2503-00. 1.4.1.6 It is not supported to install Performance Expert Server or Performance Expert Client simultaneously on a workstation. Install the components one after the other. The order in which you install the components is arbitrary. 1.4.1.7 If you run Performance Expert Server or Client on DB2 V8, and if you monitor a DB2 V9.5 instance, the creation of SQL activity reports, SQL PL reports, and WLM activity reports is not supported. 1.4.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.4.1.9 If you use Performance Expert Server on HP-UX, the password for the monitored DB2 instance that you specify in peconfig may not be longer than 8 characters. 1.4.1.10 If you migrate an earlier Performance Expert installation to Performance Expert V3.2 and if you want to change the default port number used for CIM access, only port numbers lower than 32767 are allowed. 1.4.1.11 If you use Performance Expert Extended Insight and if the connections of your monitored applications to your monitored databases are very short then no SQL statements might be displayed for these applications in the end-to-end database monitoring panels. 1.4.1.12 In Performance Expert Client the Explain button is disabled if Performance Expert Client is running on a lower DB2 version or release than the monitored DB2 instance. To get the Explain button enabled run Performance Expert Client on the same or higher DB2 version or release than the monitored DB2 instance. 1.4.1.13 Problem: If you use Performance Expert Extended Insight Feature, you may observe deadlock situations on the Performance Expert Server performance database. In these situations it works as designed and does not affect the Performance Expert Server. Background: The DB2-internal Asynchronous index cleanup(AIC) automatically cleans up the index entries and reclaims index space for table partitions that have been detached. It may run into deadlock situations with other operations detaching table partitions. In these rare situations the internal AIC (process 'db2ddpartid ') is forced and the Performance Expert Server will not be affected. 1.4.1.14 Because of a correction in the display of time values you might get higher time values on Performance Expert Client than with a previous version of Performance Expert Client. If you use functions that report on historical such as Performance Warehouse then you might see higher time values for performance data that was collected with this version of Performance Expert than with a previous one, e.g. DB2 Performance Expert V3.2.0. 1.4.2 Known problems and workarounds 1.4.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.4.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.4.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.4.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.4.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.4.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.4.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.4.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.4.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.4.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.4.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.4.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.4.2.13 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.4.2.14 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.4.2.15 Problem: Unexpected errors during the installation of Performance Expert on Windows might occur because of too many existing temporary files and directories that are written by the installation program. 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.4.2.16 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 reasons might be possible: - You have configured a monitored DB2 instance in Performance Expert Server and Performance Expert Client. - You have dropped the monitored DB2 instance on Performance Expert Server by using peconfig. - 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.4.2.17 Problem: During installation of Performance Expert in console mode or silent mode on Linux or UNIX, you might get the following message because of a known problem of the installion program: 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.4.2.18 Problem: If you start Performance Expert Client on Linux for xSeries, 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.4.2.19 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, log on 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.4.2.21 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.4.2.22 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 is fixed in DB2 V9.5 Fix Pack 2. 1.4.2.23 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.4.2.24 Problem: After installing DB2 Performance Expert Client V3.1 Fix Pack 1 or later, 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.4.2.25 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, 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 4. Save your changes in the db2pm.prop file. 4. Restart Performance Expert Client. 1.4.2.26 If you use Performance Expert Extended Insight Feature, the automatic discovery of Performance Expert Server through multicast might not work in the following environments or situations: - in VPN (AT&T) networks - in VPN (Lotus Mobility Conect) networks - if Symantec Client Firewall is used - if the multicast between subnetworks is not allowed or configured on network routers - if VMWARE is used Workaround: Configure the host name and port name of Performance Expert Server in the pdq.properties file of Performance Expert Server and Performance Expert Extended Insight Feature. Use the property pdq.cmx.controllerURL. 1.4.2.27 Problem: On Windows Vista systems, you might not be able to start the Try and Buy edition of Performance Expert Server because you do not have the required authorizations. Workaround: Take one of these steps: - Switch off the User Access Control (UAC) before you start the Performance Expert Server - Run Performance Expert Server as administrator by taking these steps: a) Click Start -> All Programs -> IBM DB2 Performance Expert Server. b) Right-click Start, then click Properties. c) Select the Shortcut tab, then click Advanced. d) Select Run as administrator. e) Click OK. 1.4.2.28 Problem: If you run Performance Expert Server on DB2 V9.5 fix pack 2 then you might encounter slow response times of Performance Expert Server because the statistics of the performance database are not updated automatically. Workaround: Install DB2 APAR IZ31409 which is contained in DB2 V9.5 fix pack 2a on the DB2 instance that is used for Performance Expert Server. 2.0 PREREQUISITES Performance Expert has hardware and software prerequisites. They are described in detail in 'Installation and Configuration', GC19-2503-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', GC19-2503-01: - Installing Performance Expert Client on Linux and UNIX systems - Installing Performance Expert Server on Linux and UNIX systems - Installing Performance Expert Client on Windows - Installing Performance Expert Server on Windows - Space requirements for Performance Expert Server By default, Performance Expert Server V3.2 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 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', GC19-2503-01: - Installing Performance Expert Client on Linux and UNIX systems - Installing Performance Expert Server on Linux and UNIX systems - Installing Performance Expert Client on Windows - Installing Performance Expert Server 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 and Performance Expert Client. The end-to-end database monitoring function is available only if Performance Expert Server runs on a DB2 Enterprise Server Edition of Version 9.1 or later and if the monitored DB2 instance runs on DB2 V9 or later. A complete list of displayed end-to-end database monitoring data is available only if the monitored DB2 instance runs on DB2 Version 9.1 Fix Pack 6 or later. This is described in detail in the above listed topics. 3.0 INSTALLATION INSTRUCTIONS 3.1. General notes These installation instructions describe briefly how to install and configure Performance Expert Server and Performance Expert Client. For a more detailed description and for migration procedures, read the installation ´topics in 'Installation and Configuration', GC19-2503-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', GC19-2503-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.2.1 can run with an earlier version of Performance Expert Server, for example V3.1 or V2.2.3, but Performance Expert Server V3.2.1 cannot run with an earlier version of Performance Expert Client. Install Performance Expert Client V3.2.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.2.1. b) You have an earlier version of Performance Expert installed and you plan to install Performance Expert Client V3.2.1 and Performance Expert Server V3.2.1 on different dates. 3.2 Linux-specific and UNIX-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', GC19-2503-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 Important: If you do not perform a new installation but migrate from a previous version of Performance Expert Server, you must run pecentralize. Otherwise, the pdq.properties file that is required to change communication settings for end-to-end monitoring is not contained in your working directory. 3.2.1 Performance Expert Server Prerequisite: The base package of Performance Expert Server V3.2.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.2.1.install-on-aix db2pe.server.v3.2.1.install-on-solaris db2pe.server.v3.2.1.install-on-xlinux db2pe.server.v3.2.1.install-on-zlinux db2pe.server.v3.2.1.install-on-plinux db2pe.server.v3.2.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.2.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.2.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 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.2.1.install-on-xlinux To use the console mode instead of the graphical mode, append the following option to the program call: -console Step 2: 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 Step 3: Add a configured monitored DB2 instance to Performance Expert Client by using the function 'New DB2 System'. 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. Step 4: If you want to use Performance Expert Extended Insight Feature for end-to-end database monitoring, enable the collection of end-to-end data in the Properties window of the monitored DB2 instance. 3.2.3 Performance Expert Extended Insight Feature If you want to use Performance Expert Extended Insight Feature for end-to-end database monitoring then install, activate and configure it as described in the following topic in 'Installation and Configuration', GC19-2503-01: - Part 4. Installing, activation and configuring Performance Expert Extended Insight Feature 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', GC19-2503-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.2.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.2.1.install-on-win.bat During the installation, the installer suggests the installation directory of an existing Performance Expert Server V3.2.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 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.2.1.install-on-win.bat Step 2: Start Performance Expert Client. Step 3: Add a configured monitored DB2 instance to Performance Expert Client by using the function 'New DB2 System'. 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. Step 4: If you want to use Performance Expert Extended Insight Feature for end-to-end database monitoring, enable the collection of end-to-end data in the Properties window of the monitored DB2 instance. 3.3.3 Performance Expert Extended Insight Feature If you want to use Performance Expert Extended Insight Feature for end-to-end database monitoring then install, activate and configure it as described in the following topic in 'Installation and Configuration', GC19-2503-01: - Part 4. Installing, activation and configuring Performance Expert Extended Insight Feature 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 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.3 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.4 Viewing the trend for a counter with a specific 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.5 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', GC19-2503-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 15 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) If you use Performance Expert Extended Feature, the table space SHORTTERM_ is also used for end-to-end data collection. End-to-end data is stored in four different aggregation levels. Each aggregation level has a different storage period before the data is deleted automatically. The data of the most detailed aggregation level 1 is stored for 12 hours by default. The data of the next detailed aggregation level 2 is stored for one week by default. This means that if you check the space consumption of the table space after one day as suggested in 3) then you can estimate roughly whether the free space is sufficient for the aggregation level 2 with a default storage period of one week, aggregation level 3 with a default storage period of one month, and aggregation level 4 with a default storage period of one year. If you keep the default values for history collection and end-to-end data collection, no more than a third of the available space should be consumed after one day. Check the space consumption again after each week to estimate whether the available disk space is sufficient for all aggregation levels of end-to-end data. If it is not sufficient, increase the available disk space or change storage period of the aggregation levels in Performance Expert Client. 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 file 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.