IBM(R) DB2(R) Performance Expert for Multiplatforms, V2 R1 IBM DB2 Performance Expert for Workgroups, V2 R1 IBM DB2 Performance Expert for z/OS(R), V2 R1 IBM DB2 Performance Monitor for z/OS, V8 R1 IBM DB2 Buffer Pool Analyzer for z/OS, V2 R1 Fix Pack 1, README CONTENTS 1.0 ABOUT THIS README FILE 1.1 Evaluation code 1.2 Corrected known problems 1.3 Known problems and workarounds 1.4 Enhancements 2.0 PREREQUISITES 2.1 Hardware requirements 2.2 Software requirements 3.0 INSTALLATION INSTRUCTIONS 3.1 General Notes 3.2 UNIX-specific installation information 3.3 Windows-specific installation information 3.4 Configuration of Performance Expert Server 4.0 CUSTOMIZATION INSTRUCTIONS 4.1 Setting monitor switches for the monitored instance 4.2 Using the Control Center plug-in on UNIX with DB2 Version 7 4.3 Performance Expert Server performance recommendations 5.0 CORRECTIONS TO DOCUMENTATION 6.0 HOW TO GET HELP 7.0 NOTICES 7.1 Use of Evaluation Program 7.1 Trademarks and service marks 1.0 ABOUT THIS README FILE Welcome to IBM DB2 Performance Expert, Version 2 Release 1, Fix Pack 1, README file of August 09, 2004. Always check the following Web site for later versions of this README file: http://www-306.ibm.com/software/data/db2imstools/support/fixpaks.html This README file contains information about installing and configuring IBM DB2 Performance Expert and information about known problems that still exist. In this README file the following naming conventions apply: IBM DB2 Performance Expert for Multiplatforms, IBM DB2 Performance Expert for Workgroups, and IBM DB2 Performance Expert for z/OS are abbreviated to Performance Expert where applicable. 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. Read NOTICES Section 7.1, Use of Evaluation Program, and the License Agreement provided with your evaluation copy of the program. 1.2 Corrected known problems This fix pack contains the following corrections: - APAR PQ88215 for Windows: In the Japanese version, the Statistics Details window now opens correctly. - APAR PQ88217 for UNIX-based operating systems: In the Japanese version, the Statistics Details window now opens correctly. 1.3 Known problems and workarounds - Problem: If a user of Performance Expert Client switches the active instance between different Performance Expert Client sessions, important client setting information (DB aliases) is not found in the DB2 catalog. In Windows(R), this problem might occur if you have multiple DB2 instances and if you change the content of the DB2INSTANCE environment variable between different Performance Expert Client sessions. - Workaround: Do not switch the active DB2 instance for all Performance Expert Client sessions of a user. - Problem: The monitored DB2 instance hangs. This might occur if multiple event monitors are created or dropped concurrently. - Workaround: Do not monitor the same DB2 instance from multiple Performance Expert Servers. Also, do not start event monitors in the monitored DB2 instance if you use event exception processing or SQL activity tracing in Performance Expert Server. - Problem: On UNIX-based platforms, the Multiplatform Installer might hang because it does not find a valid Java(R) version that is to be used for the installation. - Workaround: Call the Multiplatform Installer by using the following command: -is:javahome "" -console For example, for Solaris using Java 1.3: db2pesrv.install-on-solaris -is:javahome "/usr/java1.3" -console - Problem: If you use Performance Expert for z/OS, and if you cannot perform SQL activity tracing or Collect Report Data (CRD) steps within Performance Warehouse, you might have insufficient system privileges. - Workaround: You must have MONITOR1 and MONITOR2 system privileges. Ask your DB2 administrator. - Problem: The Control Center plug-in does not work after you migrate your Performance Expert Client workstation from DB2 Version 7 to DB2 Version 8. - Workaround: Restart the installation of Performance Expert Client and select the Repair option. - Problem: A connection cannot be established from a Performance Expert Client running under DB2 Version 7 to a UNIX-based Performance Expert Server running under DB2 Version 8 64-bit. - Workaround: Use a Performance Expert Client on DB2 Version 8. - Problem: On UNIX-based operating systems, you cannot change the contents of the db2pesrv.prop file because the file is read-only. The file is located in the working directory. The default working directory is: /var/db2pe/v21// - Workaround: Log on as instance owner and change the access access rights by using the following command: chmod 664 db2pesrv.prop - Problem: If you want to run Performance Expert Server on a 64-bit DB2 instance and if you get the error message Error loading native library 'fpesv648' during the start of Performance Expert Server, you might have used a 32-bit Java version. - Workaround: Install a 64-bit Java version on your Performance Expert Server machine. For 64-bit DB2 instances, you must use Java 1.4. - Problem: If you want to run Performance Expert Server on a 64-bit DB2 instance on UNIX-based systems, you might get an error message during the execution of the command 'pecentralize' that Java 1.4 must be used. - Workaround: Install a 64-bit Java 1.4 version on your Performance Expert Server machine. - Problem: Performance Expert Server might restart repeatedly showing DB2 error message SQL0803N in the log file db2pesrv.log if the following conditions apply: - You monitor more than one multipartition database for one DB2 instance. - More than one of these databases are currently active. - History processing for the setting 'System' is enabled. Sometimes, DB2 assigns table spaces to the wrong database. This might result in the DB2 error message SQL0803N. PMR 20087,070,724 against DB2 is open. The problem is under investigation. - Workaround: In Performance Expert Client, open the Properties window for your monitored DB2 instance. Then turn of the history settings for 'System'. - Problem: If you open the predefined data view 'Ratio of SELECT or UPDATE/INSERT/SELECT stmts' in the System Health component, you might see positive ratios although no SQL DML statements are currently executed. - Problem: If monitoring a data-sharing group under z/OS, the Statistic Details window of Performance Expert Client might not show complete information about locking situations. - Problem: If you request a GLOBAL view in Performance Expert Client for a remote multipartition database environment, the first database connect timestamp might be wrong. This results in wrong aggregation in Performance Warehouse. No workaround is currently available. The problem is under examination (DB2 PMR 39475,999, APAR IY56379). - Problem: If the System Health Monitor of Performance Expert runs under DB2 V7 Fix Pack 12, deadlocks are not shown. A PMR (82339 B070) is open. Interim fixes (special builds) are available. If you need a fix, contact your IBM representative to get a special build for your system. Permanent fixes are expected to be made available through APAR JR19748. - Problem: In the Japanese version, the contents of dynamic SQL statements is corrupted if double-byte characters are included. A PMR (04520) against DB2 is open. Interim fixes for Version 8 are available. If you need a fix, contact your IBM representative to get a special build for your system. Permanent fixes are expected to be made available through APAR JR19972. - Problem: The GLOBAL views of Performance Expert Client and Performance Warehouse display incorrect assignments of tablespaces to databases because the corresponding DB2 snapshot returns incorrect values. A PMR 20087 against DB2 is open. Fixes are expected to be made available through APAR number LI70387. - Problem: If you install the Japanese version of Performance Expert Server or Performance Expert Client on AIX systems, the installation program might create a core dump after the installation is complete. You can ignore this because the core dump does not affect your application. 1.4 Enhancements The usage of a 64-bit DB2 instance for Performance Expert Server on HP-UX is now supported. Migration support from DB2 V7 to DB2 V8 was added for the DB2 instance on which Performance Expert Server runs. For more information, refer to section 'Migrating Performance Expert Server from DB2 V7 to DB2 V8' in Chapter 3 of 'Installation and Configuration', SC18-9191-01. Enhancements were added to customize table columns. Some windows or panes show the key performance counters as columns of a table. One or more columns might be hidden. You can use the Customize columns function to view hidden counters, to hide counters, or to change the order of counters. If you use silent configuration to configure Performance Expert Server, the configuration does not stop any more if a monitored system cannot be configured. The configuration continues and writes all warnings or errors in a log file. For monitoring partitioned databases, the group view in the System Parameters - Databases window is now supported. If you open a function, for example, Application in Lock Conflicts, and if the appropriate snapshot monitor switches are not turned on for the monitored DB2 instance, Performance Expert Client displays a warning message. You can deactivate this function so that the warning message is not displayed. To reactivate the function, select Configuration from the Monitor menu in the System Overview window and click the reactivation button. You can use DB2 Stinger (DB2 V8.2) for Performance Expert Server and as monitored DB2 instance. However, Performance Expert does not yet support new functions of DB2 Stinger, for example, new snapshot counters. A new property is introduced in the properties file db2pesrv.prop of Performance Expert Server. The new property is called 'eventmonitor.checkfolder'. It determines if the shared event monitor folder that is defined during configuration of a monitored DB2 instance through peconfig is checked for accessibility before a remote DB2 instance is enabled for monitoring. The default value is 'Yes'. If you set it to 'No' before starting peconfig, you can configure a remote DB2 instance without having a shared file system defined between the machine of Performance Expert Server and the machine of the monitored DB2 instance. Requirements: - You must specify existing local paths for the local and the remote access path to the shared file system, for example, /tmp. You must not share this path between the machines. - Do not use the event exception processing function and the SQL activity tracing function if you have set this property to 'No'. Otherwise, an error occurs in Performance Expert Client. Note: When you run pecentralize on UNIX-based operating systems, the db2pesrv.prop file is copied to your working directory, for example, /var/db2pe/v21/. Copying the file might fail because the original db2pesrv.prop file is read-only. To copy the file, do the following: 1. Log on as instance owner and change the access rigths by using the following command: chmod 664 db2pesrv.prop 2. Copy the db2pesrv.prop file manually from the bin directory of Performance Expert Server to your working directory. Important: If the db2pesrv.prop file in the working directory is not read-only, previous changes are overwritten. Therefore, you must edit the file and redo your changes. 2.0 PREREQUISITES Performance Expert has hardware and software requirements. 2.1 Hardware requirements Performance Expert for Multiplatforms has the following space requirements: - A shared file system is needed between the Performance Expert Server machine and the monitored DB2 instance machine to exchange deadlock and statement event monitor files and reports between both. For deadlock event monitor files, 8 MB disk space is needed for each monitored database that is enabled for deadlock event monitoring. For statement event monitor files and reports, the size depends on the workload on the monitored instance and the event monitor runtime. Statement event monitor files and reports are created if you start SQL activity tracing either from Performance Warehouse or from the Application Summary window. As a starting value, reserve 300 MB for the shared file system. For more information, refer to 'Installation and Configuration', SC18-9191-01, Appendix D 'Space requirements for Performance Expert Server'. - A master database 'DB2PM' is created on Performance Expert Server to store metadata. The master database requires approximately 25 MB of disk space and does not grow much in size over time. For more information, refer to 'Installation and Configuration', SC18-9191-01, Appendix D 'Space requirements for Performance Expert Server'. - For each monitored DB2 instance, a separate database is created on Performance Expert Server to store collected history data and Performance Warehouse data. The size of this database grows over time, depending on several parameters. As a starting value, reserve 300 MB for each database. For more information, refer to 'Installation and Configuration', SC18-9191-01, Appendix D 'Space requirements for Performance Expert Server'. For complete information, refer to the following chapters in 'Installation and Configuration', SC18-9191-01: - Installing Performance Expert Client on Windows - Installing Performance Expert Server on Windows - Installing Performance Expert Client on UNIX-based operating systems - Installing Performance Expert Server on UNIX-based operating systems 2.2 Software requirements 2.2.1 UNIX-based systems and Windows To use Performance Expert Server, you must have installed DB2 Version 7 Fix Pack 12 or later, or DB2 Version 8 Fix Pack 5 or later, for the Performance Expert Server instance and for the monitored DB2 instances. Otherwise, the installation process issues a warning message. For the Performance Expert Agent,Fix Pack 12 is a must! For Performance Expert Server and Performance Expert Client, the following is valid: If you cannot install Fix Pack 12 for DB2 Version 7, a DB2 interim fix must be installed based on Fix Pack 11 (see below). Do not use earlier fix pack levels for the Performance Expert Server instance and for the monitored DB2 instances. If you use DB2 Version 7 with Fix Pack 11, a DB2 interim fix for APAR IY51710 must be applied to the Performance Expert Server instance and the monitored DB2 instances. Otherwise, a monitored instance might hang after a while if event exception processing, history processing, or Performance Warehouse are activated. Special builds for this interim fix based on DB2 Version 7 Fix Pack 11 build s031208 are available and can be requested from your DB2 service team. Provide the APAR number and the build identifier according to your operating system: Windows: 9740 AIX 5L(TM): 9739 Solaris: 9738 Linux(R) and Intel(R): 9737 If you use DB2 Version 8 Fix Pack 5 for Performance Expert Server and the monitored DB2 instances, a DB2 interim fix must be applied for APAR JR19735. Otherwise, a monitored DB2 instance might hang after a while if history processing or Performance Warehouse are activated. Therefore, do not use earlier DB2 Version 8 fix pack levels for the Performance Expert Server instance and monitored DB2 instances. The fix for the APAR JR19735 is available in DB2 Version 8 Fix Pack 6. Special builds for this interim fix based on DB2 Version 8 Fix Pack 5 build s040212 are available and can be requested from your DB2 service team. Provide the APAR number and the build identifier according to your operating system: Windows: 10025 AIX 5L: 10026 Solaris: 10038 Linux/Intel: 10029 zLinux: 10030 HP-UX: 10031 For more information on software requirements, refer to the following chapters in 'Installation and Configuration', SC18-9191-01: - Installing Performance Expert Client on Windows - Installing Performance Expert Server on Windows - Installing Performance Expert Client on UNIX-based operating systems - Installing Performance Expert Server on UNIX-based operating systems 2.2.2 Java on UNIX-based systems Performance Expert on UNIX and Java Performance Expert and its installation program are Java applications and therefore require that Java is installed on your system. Usually, a Java Runtime Environment (JRE) or a Java Development Kit (JDK), which is a superset of a JRE, is installed on your system. If Java is not yet installed on your system, or if your Java does not work with Performance Expert, you can install the Java that is shipped with Performance Expert. For instructions about how to do this, refer to the section 'Installing the Java that is shipped with Performance Expert'. For Performance Expert Agent, you must ensure that the PATH variable of the DB2 instance contains a valid Java 1.3. For Performance Expert Client, JavaHelp and JavaMail are required. If JavaHelp and JavaMail are not yet installed on your system, copy the files from the lib/ext subdirectory of your Performance Expert Client installation into the jre/lib/ext subdirectory of your Java 1.3. To ensure that the DB2 instance on which you start Performance Expert Client uses Java 1.3, set the PATH variable of this DB2 instance accordingly. Installing the Java that is shipped with Performance Expert The Java that is shipped with Performance Expert, is shipped as a single package. It is located on the CD in the subdirectory Java/, where denotes the operating system. Java is an element of the electronic package of your operating system. Installing Java on AIX(R): The Java that is shipped with the AIX package is: For the 32-bit AIX: jre131-20031021.tar.gz For the 64-bit AIX: jre13_64-20031021.tar.gz To install it: 1. Create the directory in which you want to install Java by using one of the following commands: For the 32-bit AIX: mkdir /usr/Java131-20031021-32bit For the 64-bit AIX: mkdir /usr/Java131-20031021-64bit 2. Copy the package to this directory. 3. Uncompress the package by using the command gunzip, then untar it. For example, use the following commands for the 32-bit AIX: cd /usr/Java131-20031021-32bit gunzip jre131-20031021.tar.gz tar -xf jre131-20031021.tar 4. Remove the remaining tar file that is no longer needed by using the following command: rm jre131-20031021.tar Installing Java on HP-UX: The Java that is shipped with the HP-UX package is: sdk13_13106_1100.depot To install it: 1. Copy the package to a directory with enough space, for example, /tmp, and install it from there. For example, use the following command: /usr/sbin/swinstall -s /tmp/sdk12_131_06_1100.depot The program SD Install opens. In the SD Install program, take these steps: 1. Select the shown product, which is the Java package that you want to install. 2. Mark the selected product: Actions/Mark for Install 3. Install the product: Actions/Install... 4. Leave the program SD Install: File/Exit The package is installed automatically in the directory /opt/Java1.3. 5. Create a subdirectory for JavaMail if it does not yet exist by using the following command: mkdir -m 755 /opt/Java1.3/jre/lib/ext Installing Java on Linux The Java that is shipped with the Linux package is: IBMJava2-JRE-1.3.1-6.0.i386.rpm To install it: 1. Log on as root. 2. Enter the following command: rpm -i IBMJava2-JRE-1.3.1-6.0.i386.rpm Java is installed in the directory /opt/IBMJava2-131. Installing Java on Linux on zSeries(R): The Java that is shipped with the Linux package is: IBMJava2-JRE-1.3.1-5.0.s390.rpm. To install it: 1. Log on as root. 2. Enter the following command: rpm -i IBMJava2-JRE-1.3.1-5.0.s390.rpm Java is installed in the directory /opt/IBMJava2-s390-131. Installing Java on Solaris: The Java that is shipped with the Solaris package is: Solaris_j2sdk1_3_1_07_sparc_ibm.tarversion.tar.Z To install it: 1. Copy the package to the directory /usr. 2. Uncompress and untar the package by using the following commands: cd /usr uncompress Solaris_j2sdk1_3_1_07_sparc_ibm.tarversion.tar.Z tar -xf Solaris_j2sdk1_3_1_07_sparc_ibm.tarversion.tar Java is be installed in /usr/j2sdk1_3_1_07. 3. Remove the remaining tar file that is not needed anymore by using the following command: rm Solaris_j2sdk1_3_1_07_sparc_ibm.tarversion.tar 2.2.3 z/OS To start and use Performance Warehouse on a z/OS Performance Expert Server running under DB2 Version 8, APAR PQ86276 must be applied to the DB2 system. 3.0 INSTALLATION INSTRUCTIONS 3.1. General Notes If you want to migrate from Performance Expert Version 1 to Performance Expert Version 2, first read the following sections in 'Installation and Configuration', SC18-9191-01: - Before you install Performance Expert on Windows - Before you install Performance Expert on UNIX-based operating systems 3.2 UNIX-specific installation information This section lists brief instructions about how to install and configure Performance Expert on UNIX-based operating systems. For a detailed description, refer to the following chapters in 'Installation and Configuration', SC18-9191-01: - Configurations for Performance Expert - Installing Performance Expert Client on UNIX-based operating systems - Installing Performance Expert Server on UNIX-based operating systems - Configuring Performance Expert Server on UNIX-based operating systems 3.2.1 Performance Expert Server (Base product) Step 1: Install Performance Expert Server by executing one of the following commands as root and follow the installation instructions: db2pesrv.install-on-aix db2pesrv.install-on-solaris db2pesrv.install-on-linux db2pesrv.install-on-zlinux db2pesrv.install-on-hpux If you want to use the console mode instead of a graphical mode, add the following option to the program call: -is:javaconsole -console Step 2: Create the instance on which Performance Expert Server should run by executing the DB2 command db2icrt as root, for example: DB2DIR/instance/db2icrt -a SERVER -p db2cdb2inpe -s ese -u db2fepe -w 32 db2inpe Change port name 'db2cdb2inpe' and user names 'db2fepe' and 'db2inpe' as required. Step 3: Update the /etc/services file to include the port name of the created DB2 instance. For example, add the following line as root: db2cdb2inpe 60010/tcp #DB2 connection service port for db2inpe Step 4: Set up the DB2 instance for Performance Expert Server by executing the following command as root from the adm directory of your installation, for example /opt/IBM/db2pesrv/V2.1/adm: ./pecentralize db2inpe Change instance name 'db2inpe' as required. Step 5: Configure the DB2 instance for Performance Expert Server by adding the monitored instances. As instance owner execute the following command from the bin directory of your installation, for example /opt/IBM/db2pesrv/V2.1/bin: ./peconfig Step 6: You can now start the configured Performance Expert Server. As instance owner execute the following command from the bin directory of your installation, for example /opt/IBM/db2pesrv/V2.1/bin: ./pestart 3.2.2 Performance Expert Server (Fix Pack) Before you can install the fix pack, the base product must be installed. If you have not yet installed the base product, refer to Step 1 in section 3.2.1 Performance Expert Server (Base product). Step 1: Install the fix pack by executing one of the following commands as root and follow the installation instructions: db2pesrv.v2.1.fp1.install-on-aix db2pesrv.v2.1.fp1.install-on-solaris db2pesrv.v2.1.fp1.install-on-linux db2pesrv.v2.1.fp1.install-on-zlinux db2pesrv.v2.1.fp1.install-on-hpux If you want to use the console mode instead of a graphical mode, add the following option to the program call: -is:javaconsole -console The default install path that is offered is the same as the base product install path. It is recommended to choose a different install path, for example /opt/IBM/db2persrv.fp1/V2.1. Step 2: After the installation of the fix pack completes successfully, you must copy the file nodelock from the bin directory of your base product installation to the bin directory of your fix pack installation, for example /opt/IBM/db2persrv.fp1/V2.1/bin. If you have installed but not yet configured and used the base product, proceed with Step 2 and follow-on steps in section '3.2.1 Performance Expert Server (Base product). Step 3: Set up the DB2 instance on which Performance Expert Server should run by executing the following command as root from the adm directory of your installation, for example, /opt/IBM/db2pesrv.fp1/V2.1/adm: ./pecentralize db2inpe Change the instance name 'db2inpe' as required to the same instance name that was used for the base product installation. Note that you must start the DB2 instance 'db2inpe' before you call pecentralize because the master database DB2PM is migrated while pecentralize is executed. The migration of the master database DB2PM might fail. If Performance Expert Server does not start after you install the fix pack, refer to the log file db2pesrv.log. This log file is located in "/" where "" denotes the DB2 instance on which Performance Expert Server runs. The is defined when you configure a DB2 instance on which Performance Expert Server should run. The default working directory is "/var/db2pe/v21". If the log file shows that the master database DB2PM is not migrated, you might restart the migration by issuing as DB2 instance owner the command "peconfig -migrate" from the installation directory. Step 4: You can now start the configured Performance Expert Server. As instance owner, execute the following command from the bin directory of your installation, for example /opt/IBM/db2pesrv.fp1/V2.1/bin: ./pestart 3.2.3 Performance Expert Client Step 1: Install Performance Expert Client by executing one of the following commands as root and follow the installation instructions: db2pecli.install-on-aix db2pecli.install-on-solaris db2pecli.install-on-linux db2pecli.install-on-zlinux db2pecli.install-on-hpux If you want to use the console mode instead of a graphical mode, add the following option to the program call: -is:javaconsole -console Step 2: You can now start the installed Performance Expert Client by executing the following command from the bin directory of your installation, for example /opt/IBM/db2pecli.fp1/V2.1/bin: ./db2pe Ensure that the user who starts the Performance Expert Client is allowed to execute DB2 commands and is a member of the group that was created while running the pecentralize script. 3.2.4 Installing in a language other than English If you want to install the Performance Expert Client in a language environment other than English, font problems might occur in graphical mode under one of the following conditions: - If you are logged on to the system remotely. - If you are logged on to the system locally, but have changed the language environment after logon to the language that you want to use during the installation. Under these conditions, perform the installation in console mode. 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, refer to following chapters in 'Installation and Configuration', SC18-9191-01: - Configurations for Performance Expert - Installing Performance Expert Client on Windows - Installing Performance Expert Server on Windows - Configuring Performance Expert Server on Windows Requirement: Your Windows system must allow the creation of "8dot3" names during the installation of Performance Expert. To ensure this, check the appropriate registry entry as follows: From REGEDIT Open hkey_local_machine->system->currentcontrolset->control->filesystem. Check the entry name NtfsDisable8dot3Creation. It must be set to "0" to enable the installation of Performance Expert. After the installation, you can reset it to "1" if required. 3.3.1 Performance Expert Server (Base product) Step 1: Define a user group and put all users of Performance Expert Client and Performance Expert Server in this group. Step 2: Install Performance Expert by executing one of the following commands as administrator user and follow the installation instructions: db2pesrv.install-on-win db2pesrv.install-on-win.workgroup-edition During the installation, you can configure the DB2 instance on which Performance Expert Server should run. If you want to do this after the installation, perform Step 3. Step 3: If not already done during Step 2, configure the DB2 instance for Performance Expert Server in one of the following ways: - Select the configuration from the Performance Expert Server program menu. - Enter the following command from a command window from the bin directory of your Performance Expert Server installation: peconfig Step 4: Start Performance Expert Server. 3.3.2 Performance Expert Server (Fix pack) Before you can install the fix pack, the base product must be installed. If you have not yet installed the base product, refer to Step 1 and Step 2 in section '3.3.1 Performance Expert Server (Base product). Step 1: Install Performance Expert Server by executing the following command as administrator user and follow the installation instructions: db2pesrv.v2.1.fp1.install-on-win.exe Usually, the installation program performs the update of the base product installation automatically. If not, use the Repair option. Note that you must start the DB2 instance on which Performance Expert Server runs before you install the fix pack because the master database DB2PM is migrated during installation. The migration of the master database DB2PM might fail. If Performance Expert Server does not start after you install the fix pack, refer to the log file db2pesrv.log. This log file is located in "\instances\" where "" denotes the DB2 instance on which Performance Expert Server runs. The is defined during the installation of Performance Expert Server. The default directory is "c:\Program Files\IBM\DB2 Performance Expert Server v2". If the log file shows that the master database DB2PM is not migrated, you might restart the migration by issuing the command "peconfig -migrate" from "\bin". If you have installed but not yet configured and used the base product, proceed with Step 3 and follow-on steps of section '3.3.1 Performance Expert Server (Base product)'. Step 2: Start Performance Expert Server. 3.3.3 Performance Expert Client Step 1: Install Performance Expert Client by executing the following command and follow the installation instructions: db2pecli.install-on-win.exe Step 2: Start Performance Expert Client. 3.4 Configuration of Performance Expert Server 3.4.1 Configuring Performance Expert Server in silent mode You can configure Performance Expert Server in interactive or in silent mode. In silent mode, a response file with the necessary parameters must be created. The response file might be kept for further configuration runs. The bin directory contains a response file template. Copy it and modify it as required. Call it as user with DB2 SYSADM authority by using the following command from the command line: peconfig -silent 3.4.2 Setting DB2 registry variables During the configuration of Performance Expert Server, the following DB2 registry variables are set: DB2_CORRELATED_PREDICATES=TRUE DB2_HASH_JOIN=YES If you use the DB2 instance not exclusively as Performance Expert Server instance, and if you require different values for these registry variables, create a separate DB2 instance on which Performance Expert Server should run. 3.4.3 Monitoring instances containing non-ASCII encoded databases During the configuration of Performance Expert Server the Performance Expert Server creates the performance databases as UTF-8 encoded databases to enable multilingual support. If monitored instances contain non-ASCII encoded databases, you must set the environment variable DB2CODEPAGE=1208 (IBM's CCSID for UTF-8) before you start the configuration of Performance Expert Server for the monitored DB2 instance This ensures conversion to UTF-8 for collected performance data that is saved in the performance databases. Variable DB2CODEPAGE can also be set as DB2 registry variable by using the db2set utility. Recommendation: To avoid effects on other applications, you should create a separate DB2 instance on which Performance Expert Server is to run. 3.4.4 Determining the NUMDB database manager configuration variable For each monitored DB2 instance, a local database is created on the DB2 instance on which Performance Expert Server runs. This happens during the configuration of Performance Expert Server. Performance Expert Server also creates a master database 'DB2PM' for its own use. If the number of active databases on the DB2 instance on which Performance Expert Server runs exceeds the value of the DB2 configuration parameter NUMDB, you get the error SQL1041N during configuration or startup of Performance Expert Server. You can check the current value by using the following command: db2 get dbm cfg The default value for NUMDB is 8. For more information about NUMDB, refer to the DB2 documentation. You can use the following calculation to determine the minimum value of NUMDB for your installation: 1 + (number of pre-existing databases that you expect to be active) + (1 * number of monitored instances) Example: If you create a new DB2 instance exclusively for Performance Expert Server, and if you plan to monitor five DB2 instances, the NUMDB value should be at least 6. If you install Performance Expert Server on an existing DB2 instance that has already databases in it, you might need to increase the NUMDB value beyond the default value. 4.0 CUSTOMIZATION AND USAGE INSTRUCTIONS 4.1 Setting monitor switches for the monitored DB2 instance The monitor switches that are set for the monitored DB2 instance determine the amount of data that is shown by Performance Expert Client. By default, all monitor switches are turned off after the installation of DB2 and the creation of a DB2 instance. Before you use Performance Expert, check the monitor switches for the monitored DB2 instances and set them as required. To check the monitor switches, issue the following command from the DB2 command line and inspect the 'Default database monitor switches': db2 get dbm cfg For complete instructions about how to configure and use Performance Expert, refer to 'Installation and Configuration', SC18-9191-01. 4.2 Using the Control Center plug-in on UNIX with DB2 Version 7 The DB2 Performance Expert Control Center plug-in requires at least JRE 1.2, although the DB2 Version 7 Control Center on UNIX requires JRE 1.1.8. To start the Control Center on a UNIX- based system by using a JRE version later than 1.1.8, set the JAVA_HOME environment variable to point to your Java distribution by using the following command: set JAVA_HOME=/usr/java12 In IBM JDK 1.2, the jre command is no longer supported. However, the db2cc script, which starts the Control Center, calls the jre command. Create a link, called jre, to the Java executable in the java/bin directory by issuing the link command as root, for example: ln -sf /usr/java12/bin/java /usr/java12/bin/jre The db2cc script calls the jre command with argument -nojit argument that is not supported in IBM JDK 1.2 or later. Remove the option by changing line 44 in the db2cc script to the following: JRE_OPTIONS="-ss256k -mx128m -Ddb2path=$DB2PATH" 4.3 Performance Expert Server performance recommendations 4.3.1 Autorefresh function increases CPU consumption on Performance Expert Server The CPU consumption on Performance Expert Server can increase considerably if you specify a short autorefresh interval, for example, 10 seconds, on the Statistics Details window and if you additionally receive table information and statement cache information. The reason is that different DB2 snapshots are taken for different categories, such as tables, statement cache, databases, table spaces, and buffer pools. Especially snapshots for the table and statement cache category are consuming CPU resources. If an autorefresh interval is specified, these snapshots are repeatedly taken according to the specified interval. Note also that the information displayed on the Statistics Details window is lost when a new snapshot is taken and new data is displayed. To avoid unnecessary CPU resource consumption: - Use the autorefresh interval only if an intensive analysis is required. If you do not need table and statement cache information, turn them off. - If sufficient, use the history slider to monitor data over a certain time frame, or use the Refresh button to perform a one-time refresh when you require current information. 4.3.2 Executing runstats and reorg on your performance databases To maintain a good performance on your performance databases, run the DB2 runstats and reorg commands regularly on your performance databases. First, use the reorgchk command to check if executing the reorg command is necessary. For more information, refer to your DB2 documentation. Connect to the performance databases and execute the following commands: db2 -tvf perunstats (for runstats command) db2 -tvf pereorgv7 (for reorg on DB2 V7 databases) db2 -tvf pereorgv8 (for reorg on DB2 V8 databases) The scripts are located in the bin directory of your Performance Expert Server installation. After executing these commands, disconnect from the performance databases. 5.0 CORRECTIONS TO DOCUMENTATION Enhancements were added to the documentation. For example, Appendix D in 'Installation and Configuration', SC18-9191-01, describes space requirements for Performance Expert Server. Appendix B of 'Installation and Configuration', SC18-9191-01, contains scenarios for the installation and configuration of Performance Expert. For a complete list of documentation enhancements refer to the section 'Summary of changes' in 'Installation and Configuration', SC18-9191-01, and to the section 'What's new ?' in 'Monitoring Performance from the Workstation', SC18-7976-02. To obtain the latest refresh of DB2 Performance Expert publications refer to: 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 on 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 URL, call 1-800-IBM-SERV to speak to an IBM representative for assistance. For fix packs to be installed before using the program, refer to the following Web site: http://www.ibm.com/software/data/db2imstools/support/fixpaks.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 the evaluation program If you are using an evaluation copy of the program, the following terms apply: This program contains a disabling device that will prevent it from being used upon expiration of this license. You will not tamper with this disabling device or program. You should take precautions to avoid any loss of data that might result when the program can no longer be used. See the License Agreement for a complete explanation of the terms that apply. 7.2 Trademarks and service marks The following terms are trademarks or service marks of the IBM Corporation in the United States, other countries, or both: AIX AIX 5L DB2 IBM OS/390 z/OS zSeries Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Intel, Intel Inside (logos), MMX, and Pentium are trademarks of Intel Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a trademark of Linus Torvalds in the United States, other countries, or both. Other company, product and service names may be trademarks or service marks of others. (C) Copyright IBM Corporation 2003, 2004. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.