IBM(R) DB2(R) Performance Expert for Multiplatforms, V1 R1, Fix Pack 7 DB2 Performance Monitor for z/OS - Workstation Online Monitor V7 and V6 DB2 Buffer Pool Analyzer for z/OS CONTENTS 1.0 ABOUT THIS README FILE 1.1 Evaluation code 1.2 Corrected problems 1.3 Enhancements 1.4 Known problems and workarounds 2.0 PREREQUISITES 2.1 Minimum hardware requirements 2.2 Minimum software requirements 3.0 INSTALLATION INSTRUCTIONS 3.1 General notes 3.2 Installation on UNIX(TM)-based operating systems 3.3 Configuration on UNIX-based operating systems 3.4 Instructions for Windows operating systems 4.0 CUSTOMIZATION INSTRUCTIONS 4.1 Performance Expert Server on Red Hat Linux 5.0 FIXPAK INSTALLATION 5.1 Fix Pack Install for Performance Server on Windows(TM) 5.2 Fix Pack Install for Performance Server on UNIX-based operating systems 5.3 Fix Pack Install for Performance Server Agent on Windows 6.0 RESTRICTIONS 6.1 Performance Expert 6.2 Workstation Online Monitor 6.3 Japanese version of Performance Expert 8.0 HOW TO GET HELP 8.0 NOTICES 8.1 Use of the evaluation program 8.2 Trademarks and service marks 1.0 ABOUT THIS README FILE Welcome to IBM DB2 Performance Expert, Version 1 Release 1, README file. This README file contains information about installing IBM DB2 Performance Expert. It is the most current README file as of 04/09/2003. In this README file, the following naming conventions apply: IBM DB2 Performance Expert for Multiplatforms is abbreviated to Performance Expert. When the name Performance Expert is used, DB2 Performance Monitor (DB2 PM) is included 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 run Performance Expert. Read NOTICES Section 8.1, Use of the evaluation program, and the License Agreement provided with your evaluation copy of the program. 1.2 Corrected problems This Fix Pack contains the following corrections: - Fixed: The performance decreased. The following conditions increased the response time: The server ran for a long time and the client was permanently refreshed. More than ten databases were to be monitored. - Fixed: The "DB2PM database already exists" problem. If the DB2PM database existed and if you installed from scratch, you had to drop the database manually. Now, you can choose whether the installation program should drop the DB2PM database or whether it remains. If it remains, set the following parameter in the file db2pesrv.prop, which is located in the bin subdirectory of your installation directory: tracerouterlevel=5 The DB2PM database is then automatically migrated to the latest version when you start the server for the first time. - Fixed: Sometimes, all windows of Performance Expert became gray and unusable. - Fixed: The memory of Windows was exhausted. If Buffer Pool Analyzer for z/OS tried to analyze 100.000 objects (data spaces) by using object placement, the available memory of Windows was exhausted. Now, you can analyze more than 200.000 objects. The following memory usage is valid for Fix Pack 7: 40 MB for 1000 objects, 220 MB for 100.000 objects, and 500 MB for 200.000 objects. - Fixed: A Java error occurred during the installation on UNIX-based operating systems. (APAR PQ69326) - Fixed: Only up to 59 mounts were possible. (APAR PQ69734) - Fixed: NIS support for UNIX-based operating systems was not available. (APAR PQ69755) - Fixed: An SQL statement containing a Japanese table name did not work. (APAR PQ66838) - Fixed: An error regarding 'pestart' occurred on the Solaris Operating Environment. (APAR PQ68199) - Fixed: On Windows, spaces in the directory path were not allowed. (APAR PQ69804) - Fixed: For DB2PM, z/OS systems could not be defined. (APAR PQ70604) - Fixed: Sometimes, data that was collected and stored by Performance Expert Agent was not shown. (APAR PQ70828) To obtain a list of fixes that were included in previous Fix Packs, refer to APARs PQ65948, PQ65963, PQ66447, PQ66899, PQ66900, PQ66901, PQ66902, PQ66903, PQ67875, PQ68199, PQ68201, PQ68206, PQ68207, PQ68208, PQ68209, PQ68339, PQ68382, PQ68713, PQ68713, PQ68713, PQ68892, PQ68893, PQ68895, PQ68896, PQ68949, PQ68950, PQ68951, PQ68952, PQ68953, PQ69734, PQ69755, PQ69317, PQ69323, PQ69321, PQ69322, PQ69324, PQ69807. 1.3 Enhancements This Fix Pack contains the following enhancements: - Statistics Details data now contains also the SQL table data. 1.4 Known problems and workarounds - If you have Windows NT and DB2 V8 installed, Performance Expert Server does not run. - Problem: If Performance Expert Server runs on UNIX-based operating systems on which DB2 V7 Enterprise-Extended Edition (EEE) is installed, the 'Exception processing' function of Performance Expert might damage DB2 processes when you activate it. You must then stop DB2 by using the command db2_kill and restart it. Workaround: Do not activate the 'Exception processing' function in this environment. - In a DB2 EEE environment, functions based on event monitoring, such as SQL activity, exception processing, buffer pool analysis, and Performance Warehouse work only in a single partition environment for Fix Pack 7. - Problem: If a DB2 V7 client connects to a DB2 V8 server, the following error message might occur: FRAMEWORK : SQLError : [IBM][CLI Driver][DB2/6000] SQL0551N "" does not have the privilege to perform operation "EXECUTE" on object "NULLID.SQLLF000". SQLSTATE=42501 Workaround: Enter the following commands on the DB2 V8 server db2 connect to db2pm user using db2 bind @db2cli.lst blocking all grant public db2 grant execute on package nullid.sqllf000 to public db2 grant execute on package nullid.sqllf200 to public db2 grant execute on package nullid.sqllf400 to public For more information on this problem, refer to the DCF document (Technote) containing the following subject: "CLI Packages in DB2 V8.1". This document explains the changes in V8.1 regarding the CLI bind files and packages. - Problem: When running an SQL Activity Tracing report from the Application Details window on Windows 2000, the report might fail with the message 'SQL086N A default table space could not be found with a page size of at least 4096 that authorization ID DB2PESERVER is authorized to use.' Workaround: In DB2, manually grant the use of this table space to the user DB2PESERVER. 2.0 PREREQUISITES Performance Expert has hardware and software requirements. 2.1 Minimum hardware requirements Performance Expert for Multiplatforms has the following hardware requirements: - Memory and disk space sufficient to fulfill DB2 requirements. If you use Buffer Pool Analyzer for z/OS, you might need the maximum memory. See also 1.2 Corrected problems. - A minimum of 150 MB of free disk space. - Additional space for user data. This varies depending on the size of your databases and the amount of activity your system encounters. 2.2 Minimum software requirements To use Performance Expert for Multiplatforms, you must have IBM DB2 V7 Fix Pack 6 or later. Performance Expert Agent needs at least IBM DB2 V7 Fix Pack 7. For Performance Expert Server, however, do not use IBM DB2 V7 Fix Pack 7. 3.0 INSTALLATION INSTRUCTIONS 3.1 General notes 1. If you plan to install Performance Expert Server for a DB2 UDB EEE configuration, you have to install it only once. Select a partition of your choice and install it there. Note, however, that for Fix Pack 7 the functions based on event monitoring work only in a single partition environment. See also section 1.4 Known problems and workarounds. 2. Because you can install Performance Expert without installing DB2, consider the following: If DB2 is not installed, functions of Performance Expert regarding a multiplatform server or a Performance Warehouse cause an error. To enable these functions after installing the correct version of DB2, you must run the setup of Performance Expert Client again by using the Repair option. 3. Before you start installing the program, read "IBM DB2 Performance Expert for z/OS and Multiplatforms, Version 1 Release 1, Installation and Customization", SC27-1646. You can find this documentation also on the following Web site: http://www.ibm.com/software/data/db2imstools/library.html 4. Close all Performance Expert Agents and Performance Expert Agent connections before installing Performance Expert Server. 5. Before you install Performance Expert Server, ensure that all DB2 instances to be monitored are started. 6. What to consider when you have DB2 Version 8 installed: - If Performance Expert Server is installed on a workstation that runs under DB2 Version 8, Performance Expert Client must be installed on a workstation that runs at least under DB2 Version 7 Fix Pack 8. - Clients running under DB2 Version 8 can connect only to servers running under DB2 Version 8. 7. To use Performance Expert Client with a Performance Expert Server for z/OS Version 1.1, APAR PQ68678 must be applied on the server to ensure correct results. 3.2 Installation on UNIX-based operating systems Performance Expert for Multiplatforms uses the InstallShield Multiplatform wizard on UNIX-based operating systems. You can run it in a GUI or in console mode. The following instructions apply to both methods unless otherwise indicated. 1. Log on to the UNIX-based operating system on which Performance Expert is to be installed as a user with root authority. 2. Ensure that the umask is set to 022. The command 'umask' displays the current umask setting. The command 'umask 022' sets umask for current session. 3. This step depends on your installation mode. If you use the GUI, perform step 3.a. If you use the console, perform step 3.b. 3.a If you want to use the GUI for the installation, you must run the InstallShield in an X Window System environment. In an X Window System environment, do the following: 1. Ensure that applications of the X Window System can access the display of your choice by using the following commands: echo $DISPLAY This command shows the current DISPLAY variable setting. export DISPLAY=hostname:0 This command sets the DISPLAY if it is incorrect or not set. 'hostname' denotes the name of the host of which the screen is to be used. xclock & This command verifies that applications of the X Window System can be displayed correctly. You can close the clock display after it appears. 2. If you get a message that contains the line 'Xlib: Client is not authorized to connect to Server', grant this authorization on the host of which the screen is to be used by entering the following command: xhost hostname where hostname denotes the host on which Performance Expert Server is to be installed. Then try it again. 3. You can now install Performance Expert Server by using the InstallShield Multiplatform wizard in a GUI. To start the installation, enter the following commands, depending on your operating system: For AIX: /db2pesrv-install-on-aix For HP-UX: /db2pesrv-install-on-hpux For Linux: /db2pesrv-install-on-linux For Linux390: /db2pesrv-install-on-linux390 For Solaris Operating Environment: /db2pesrv-install-on-solaris After the installation completes successfully, you must configure Performance Expert Server as described in 3.3. 3.b If you use the console, enter one of the following commands depending on your operating system: For AIX: /db2pesrv-install-on-aix \ -is:javaconsole -console For HP-UX: /db2pesrv-install-on-hpux \ -is:javaconsole -console For Linux: /db2pesrv-install-on-linux \ -is:javaconsole -console For Linux390: /db2pesrv-install-on-linux390 \ -is:javaconsole -console For Solaris Operating Environment: /db2pesrv-install-on-solaris \ -is:javaconsole -console After starting the command, several dots are displayed. The dots indicate that the installation program is initializing and running, and you get the first prompt. After the installation completes successfully, you must configure Performance Expert Server as described in 3.3. 3.3 Configuration on UNIX-based operating systems To configure Performance Expert Server, perform these steps for each instance that you want to monitor: 1. Run the configuration script db2pesrv-config db2inst1 where 'db2inst1' is the DB2 instance user under which Performance Expert Server runs. You are asked to enter several parameters. These parameters determine: - Where the DB2PM database is stored. - The group that has access to this database. - Where trace and log files are stored. - Your Java Runtime environment for DB2. This Java Runtime environment is set in the DB2 environment variable JDK11_PATH on DB2 V7 or JDK_PATH on DB2 V8. 2. If DB2 environment variables are changed while you run this script, you are asked to invoke the following commands. These commands activate the DB2 environment variables and register the file fpesp.jar with your new Java Runtime environment setting: db2stop db2start /var/db2pe/db2inst1/peregjar.sh where '/var/db2pe' is your DB2PE working directory as defined during the configuration. The script /var/db2pe/db2inst1/peregjar.sh tries to register the file fpesp.jar with your new Java Runtime environment setting. 3.4 Instructions for Windows While installing the base or a Fix Pack of Performance Expert on Windows, the message 'Cannot find file layout.bin. Please insert disk ...' might appear. If this message occurs, do one of the following: - Restart Windows in the following way: Before you log on to the system, press the Shift key and keep it pressed while you log on. The system then starts without the autostart options. Then retry installing the base or the Fix Pack. - Delete all files in the InstallShield directory. On Windows, for example, this directory is located in: C:\Program Files\Common Files\InstallShield 4.0 CUSTOMIZATION INSTRUCTIONS For complete instructions on how to customize and use Performance Expert, refer to "IBM DB2 Performance Expert for z/OS and Multiplatforms, Version 1 Release 1, Installation and Customization". You can find this document on the following Web site: http://www.ibm.com/software/data/db2imstools/library.html If you install this image from CD-ROM, the documentation is located in the /doc directory. The User's Guide on the Web can contain updates to the publication on CD-ROM. 4.1 Performance Expert Server on Red Hat Linux Setting kernel parameters: To run DB2, you must set kernel parameters in the following way: 1. Display the kernel parameters by entering the following command: ipcs -l 2. Add the following lines to the file /etc/sysctl.conf: kernel.msgmni = 512 kernel.sem=250 128000 32 512 3. Activate the kernel parameters by entering the following command: sysctl -p Setting links: To avoid the problem that some Java libraries cannot be found, add the following links if your JDK11_PATH on DB2 V7 or your JDK_PATH on DB2 V8 is /opt/IBMJava-131: ln -s /opt/IBMJava2-131/jre/bin/libhpi.so /usr/lib ln -s /opt/IBMJava2-131/jre/bin/libjava.so /usr/lib ln -s /opt/IBMJava2-131/jre/bin/classic/libjvm.so /usr/lib 5.0 FIXPAK INSTALLATION 5.1 Fix Pack Install for Performance Server on Windows Before you can install a Fix Pack, the base package of Performance Expert Server must be installed. If it is not installed, you get the error message 'Could not start the DB2 Performance Expert Server (DB2) service on local computer.' Usually, the installation program performs the update automatically. If not, use the Repair option. This option repairs only program files of the Performance Expert Server installation. To repair the DB2PM database, reinstall Performance Expert Server. 5.2 Fix Pack Install for Performance Server on UNIX-based operating systems Before you can install a Fix Pack, the base package of Performance Expert Server must be installed. Do not remove the installed version of Performance Expert. Instead, install the Fix Pack in a new directory. To install the Fix Pack: 1. Ensure that the Fix Pack installation file db2pesrv.fpx.install-on-system is executable, where x denotes the version of the Fix Pack, and system denotes your operating system, for example, db2persrv.fp7.install-on-aix. 2. Invoke the Fix Pack installation file. 3. When you are asked for the installation path, select, for example, /opt/IBM/db2pesrv.fpx/V1.1, where x denotes the version of the Fix Pack. 4. After the installation of the Fix Pack completes successfully, you must copy the file nodelock from the directory /opt/IBM/db2persrv/V1.1/bin/nodelock to /opt/IBM/db2persrv.fpx/V1.1/bin/nodelock, where x denotes the version of the Fix Pack. 5. If InstallShield does not remove Performance Expert completely, you must drop the DB2PM database for each monitored instance by using the following command: db2 drop db db2pm In addition, you might have to remove old temporary files of Performance Expert Server by using the following command: rm -fr /var/db2pe/ where db2inst denotes the name of the DB2 instance. 6. Run the following configuration script for each DB2 instance that you want to monitor: /opt/IBM/db2persrv.fpx/V1.1/adm/db2pesrv-config db2inst1 where x denotes the version of your Fix Pack and db2inst1 denotes the name of the instance, where you want to run the Performance Expert Server. The output is logged in the file /tmp/db2pesrv-config.db2inst1.log . 5.3 Fix Pack Install for Performance Server Agent on Windows Usually, the installation program performs the update automatically. If not, use the Repair option. 6.0 RESTRICTIONS 6.1 Performance Expert - If you use Performance Expert for DB2 Version 8, and if there are connectivity problems between the DB2 client and server of this version, refer to "IBM DB2 Connectivity Supplement Version 8". - If you install Performance Expert Server on a machine on which DB2 Version 7.2 Fix Pack 7 for UNIX is installed, you must run Performance Expert Client on the same machine. Remote access causes a DB2 problem. - You might need to increase limits to handle too many database connections on Performance Expert. Event exception processing is, by default, activated by Performance Expert Server for all databases of the monitored DB2 instance. Thus, an additional connection is established for each database. It might be necessary to increase either or both of the following: - The maximum number of concurrent applications (maxappls) that can be connected to a database. - The maximum number of database manager agents (maxagents) available at any time to accept application requests. Alternatively, you can deactivate event exception processing at Performance Expert Server and thus reduce the number of connections by switching it off within the Properties of the DB2 instance of the Performance Expert Client. 6.2 Workstation Online Monitor - Launching Netscape as your HTML browser from the client can fail. In this case, start the browser separately. - Threshold sets cannot be imported or exported in periodic exception processing, threshold sets cannot be imported or exported. Therefore, you cannot use exception profiling on the host. - When the Data Collector or Performance Expert Server is restarted, the client might not reconnect. In this case, log off manually from the monitored DB2 subsystems or DB2 instances, then log on again. In some cases, you must restart the client. - When SQL activity traces are generated, several database connections are used. Note that these connections are not released after the SQL activity trace is generated so that they can be reused for further tracing. They are only released when you log off from the DB2 instance. 6.3 Japanese version of Performance Expert - You cannot use double-byte character set (DBCS) entries for Performance Warehouse functions and for the System Health window of the Workstation Online Monitor. - Performance Warehouse does not work with databases defined with CCSID 1390. It works, however, with databases defined with CCSID 500. 7.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 are not able to find your answer searching the listed 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 8.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. 8.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. 8.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: DB2 DB2 Universal Database IBM OS/390 z/OS Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. 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. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.