IBM(R) DB2(R) Performance Expert for Multiplatforms, V2.2.0.1 IBM DB2 Performance Expert for Workgroups, V2.2.0.1 Fix Pack 1, README CONTENTS 1.0 ABOUT THIS README FILE 1.1 Evaluation code 1.2 Corrected problems 1.3 Known limitations, 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- and Linux-specific installation information 3.3 Windows-specific installation information 4.0 CUSTOMIZATION AND USAGE INSTRUCTIONS 4.1 Enabling access to a CIM Server 4.2 CIM Server 4.3 Using Performance Expert with DB2 Version 8 Fix Pack 9 or later 4.4 Importing CM- and BI-specific data views 4.5 Using the IBM Content Manager threshold set 5.0 CORRECTIONS TO DOCUMENTATION 6.0 HOW TO GET HELP 7.0 NOTICES 7.1 Use of evaluation program 7.2 Other notices 7.3 Trademarks and service marks 1.0 ABOUT THIS README FILE Welcome to IBM DB2 Performance Expert, Version 2 Release 2, Fix Pack 1 README file of 21 February 2006. 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 for Multiplatforms and IBM DB2 Performance Expert for Workgroups, and information about known problems. In this README file the following naming conventions apply: IBM DB2 Performance Expert for Multiplatforms and IBM DB2 Performance Expert for Workgroups are abbreviated to Performance Expert where applicable. The Performance Expert Client can also be used with the following products: - IBM Tivoli(R) OMEGAMON(R) XE for DB2 Performance Expert on z/OS(R), V3.1 - IBM DB2 Buffer Pool Analyzer for z/OS, V3.1 - IBM DB2 Performance Expert for z/OS, V2.1 - IBM DB2 Performance Monitor for z/OS, V8.1 Known problems for these products 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. Read NOTICES Section 7.1, Use of 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: - APAR PK13393: New BPA report generation and display functionality. - APAR PK14431: SQL error SQL0413N occurs for PWHLOAD during the start of the Performance Expert Server. - APAR PK15264: Error SQL0407N occurs during "DB2 get snapshot for application information". - APAR PK17657: Error 'java.io.IOException: No event monitor files found in xxx.evt (A file or directory in the path name does not exist.) : Return code ....... :201' occurs during SQL Activity Trace execution. Reason: A long remote monitoring folder pathname may be truncated and therefore not found. - The Java(R) virtual machine of the Performance Expert Server crashes and writes dumps because of "OutOfMemoryExceptions". This might happen in complex environments with many tables and table spaces while processing periodic exceptions. 1.3 Known limitations, problems and workarounds 1.3.1 Limitations 1.3.1.1 If you monitor a DB2 instance located on an AIX machine and have CIM enabled, the following limitation exists: On the Performance Expert Client: If you see N/P values on Operating Systems panels or graphical data views that you have defined for operating system values, and a red icon in the right corner on the panel with a tooltip indicating that the CIM server is not reachable, the CIM server might have crashed. A fix is expected to be available with Pegasus CIM server 2.5.0.1 in the first half of 2006. As a workaround, start the CIM server again. 1.3.1.2 If you have CIM enabled, and if you disable history processing for operating system parameters on the Performance Expert Client in the properties of a monitored instance, then periodic exception processing for operating system parameters is not possible after the last history entries have been deleted by the Performance Expert Server. Additionally, the operating system parameters on panel Statistic Details->Tablespace ->Container contain no values. 1.3.1.3 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 executed. 1.3.1.4 Running the Performance Expert Client on HP/UX is not supported. 1.3.1.5 If you monitor a DB2 instance located on an AIX, Solaris or Linux(R) machine, you cannot enable CIM if the host name of the monitored machine starts with an underscore or a number. If you enable CIM, an "invalid locator" error occurs if Performance Expert Server accesses CIM. 1.3.1.6 When a monitored database is in write suspend mode, no data is collected by the Performance Expert Server and displayed on the Performance Expert Client. This behavior is a DB2 limitation. 1.3.2 Known problems and workarounds 1.3.2.1 Problem: If you request a GLOBAL view in the 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. - Workaround: Install DB2 Version 8 Fix Pack 8 (APAR IY56379) 1.3.2.2 Problem: The GLOBAL views of the Performance Expert Client and Performance Warehouse display incorrect assignments of table spaces to databases because the corresponding DB2 snapshot returns incorrect values. - Workaround: Install DB2 Version 8 Fix Pack 8 (APAR LI70453) 1.3.2.3 Problem: A monitored DB2 instance might hang 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 the Performance Expert Server. Alternatively, install DB2 Version 8 Fix Pack 8. 1.3.2.4 Problem: On UNIX(R) and Linux systems, the Multiplatform Installer might hang because it does not find a valid Java 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.4: db2pe.server.v2.2.fp1.install-on-solaris -is:javahome "/usr/java1.4" -console 1.3.2.5 Problem: Under the following conditions, the Performance Expert Server might restart repeatedly, thereby recording the DB2 error SQL0803N in the db2pesrv.log file: - If you monitor more than one multipartition database in one DB2 instance. - If more than one of these databases are currently active. - If history processing for the setting 'System' is enabled in the properties panel of the monitored DB2 instance on the Performance Expert Client. Under these conditions, DB2 sometimes assigns table spaces and tables to the wrong database, which results in error SQL0803N. The wrong assignment of tablespaces to databases is fixed with DB2 Version 8 Fix Pack 8 (APAR LI70453). - Workaround: In the Performance Expert Client, open the Properties window for your monitored DB2 instance and turn off the history settings for 'System'. The wrong assignment of tables to databases is fixed in DB2 Version 8 Fix Pack 10 (APAR IY71463). - Workaround: Within a monitored instance, if you are monitoring two or more databases that contain at least one table with the same name, either: -- Switch off the table monitor switch of the monitored instance. -- In the Performance Expert Client, open the Properties window for the monitored DB2 instance and turn off the history settings for 'System'. 1.3.2.6 Problem: In the Japanese version, the contents of dynamic SQL statements are corrupted if double-byte characters are included. - Workaround : Install DB2 Version 8 Fix Pack 8. 1.3.2.7 Problem: The pecentralize command fails with error 'db2 not found' on UNIX and Linux systems because db2profile was not executed in bash shell. - Workaround: Use a different shell, for example, the Korn shell, as login shell for the instance user. 1.3.2.8 Problem: If you use the Performance Expert Server on Windows, and monitor a remote partitioned DB2 instance based on DB2 Version 8, and have configured the Performance Expert Server to use no shared file system for exchanging event monitor data, then enabling event monitoring during configuration causes a hang of the monitored DB2 instance after starting the Performance Expert Server. - Workaround: The problem is solved in DB2 Version 8 Fix Pack 9. Without this fix, do not enable databases for event monitoring, or configure the Performance Expert Server to use a shared file system to exchange event monitoring data. 1.3.2.9 Problem: If you see only N/P values for performance counters on the Performance Expert Client after you have installed and configured the Performance Expert Client and the Performance Expert Server, you might have used the adddb command from the command line or 'Add database' from the GUI and have specified a name of a database that does not exist on your monitored DB2 instance. - Workaround/Solution: On the Performance Expert Server, call peconfig again and check whether the specified database name actually exists on the monitored DB2 instance. If it does not exist, remove the database from monitoring and add it again using the correct name. 1.3.2.10 Problem: If you monitor a DB2 instance located on an AIX machine and have CIM enabled, the following problems and workarounds exist: 1. Problem on the Performance Expert Client: If you use Pegasus CIM Server 2.3 and check 'Receive process information' on the panel Operating System Status->Processes, it might take long until the information for all running processes is displayed, or even cause a timeout message. - Workaround: A response time improvement is available with Pegasus CIM Server 2.5. 2. Problem on the Performance Expert Client: If you use Pegasus CIM Server 2.3, the processor status field on the Operating System Information panel always shows 'Enabled',even if the processor is only defined, but not available. - Workaround: A fix is available with Pegasus CIM Server 2.5. 3. Problem: You might see N/P values on the Operating System Information panel, if the /tmp directory of either the monitored machine or the Performance Expert Server machine is nearly full. - Workaround: Free space in the appropriate /tmp directory. 1.3.2.11 Problem: Installation and configuration of the Performance Expert Server or the Performance Expert Client on UNIX or Linux in console mode might cause errors if you correct input data with the backspace key and the backspace key is not correctly configured. - Workaround/Solution: Before installation and configuration, activate the backspace key with the command "stty erase ^?". Depending on the shell, you might need to enter "stty erase ^H". 1.3.2.12 Problem: If you use DB2 Version 8 Fix Pack 9 or later for a monitored DB2 instance, but an earlier DB2 level for Performance Expert Server, then a N/C value is shown for Default Page Size in the System Parameters-Databases->Capacity Management pane of the Performance Expert client. The same is true for other System Parameters that are introduced with DB2 levels later than the DB2 level of the Performance Expert Server. - Workaround: Use DB2 Version 8 Fix Pack 9 or later with Performance Expert Server 1.3.2.13 Problem: If you have CIM enabled then getting data from the CIMON server may fail may fail because the hostname of the monitored system where the CIMON server is running cannot be resolved on the system where the Performance Expert Server is running. - Workaround: Add fully qualified hostname of monitored system to /etc/hosts file on system where the Performance Expert Server is running. 1.3.2.14 Problem: If you monitor a DB2 instance located on an AIX machine and have CIM enabled then no value for 'Disk Utilization-I/O time' might be displayed. - Workaround: The I/O time value is displayed if the SYSP_V_IOSTRUN flag is set. The flag can be set by using the following command as root: chdev -l sys0 -a iostat=true The flag can be unset by using the following command as root: chdev -l sys0 -a iostat=false The current status of the flag can be got thru the following command as root: lsattr -E -l sys0 -a iostat For more details refer to the "Disk Input/Output History" section of the iostat command documentation: http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?topic=/com.ibm.aix.doc/cmds/aixcmds3/iostat.htm 1.4 Enhancements This fix pack contains the following enhancements: The collection of operating system data is now also supported for Linux platforms if a CIM Server is running on Linux. Enabling and changing monitored instances while the Performance Expert Server is running is now supported. The enable command automatically activates monitoring of the instance. Changes to the configuration can be activated while the Performance Expert Server is running. The Performance Expert Server now supports the execution of a user exit after the occurrence of an exception. This lets you execute customized actions or route the exception to other applications. New calculated counters and snapshot counters, introduced by DB2 Version 8 Fix Pack 9, are displayed on the Performance Expert Client panels. Graphical data views on the System Overview panel now have the same refresh rate as the data views on the System Health panel. New external commands are available for peconfig. If the Performance Expert Server is running on DB2 Version 8.2.2 (DB2 Version 8.1 Fix Pack 9) or later and you configure a new instance for monitoring, the performance database is configured for automatic RUNSTATS and REORG. New predefined queries and a new scheduler are available for Performance Warehouse. Extended filter capabilities are available for the definition of periodic exceptions. On Windows, a graphical user interface is available to configure the Performance Expert Agent. DB2 Personal Edition and DB2 Connect Personal Edition can now be used for the Performance Expert Client. Predefined data views for Business Intelligence (BI) or Content Manager (CM) environments are available for import. A predefined threshold set 'IBM Content Manager' is provided that can be used in CM environments. 2.0 PREREQUISITES Performance Expert has hardware and software requirements. 2.1 Hardware requirements For information about hardware requirements, refer to the following chapters in 'Installation and Configuration', SC18-9191: - Installing Performance Expert Client on Windows - Installing Performance Expert Server on Windows - Installing Performance Expert Client on UNIX and Linux systems - Installing Performance Expert Server on UNIX and Linux systems - Appendix D 'Space requirements' 2.2 Software requirements 2.2.1 Windows, UNIX and Linux systems To install and run the Performance Expert Client or the Performance Expert server on a xLinux 64 bit system (EM64T, X86_64), DB2 Version 8.2.2 or later is required. To install and run Performance Expert on xLinux with kernel 2.4 and to integrate operating system data in Performance Expert (possible if your monitored instance runs on AIX or Solaris), the Performance Expert Server requires DB2 Version 8.2.2 or later. For more information on software requirements, refer to the following chapters in 'Installation and Configuration', SC18-9191: - Installing Performance Expert Client on Windows - Installing Performance Expert Server on Windows - Installing Performance Expert Client on UNIX and Linux systems - Installing Performance Expert Server on UNIX and Linux systems 2.2.1 AIX Pegasus CIM Server To integrate operating system data in Performance Expert, if your monitored instance resides on AIX, an open-source implementation of the Common Information Model Object Manager (CIMOM), called Pegasus Version 2.3.2 or later, of AIX Expansion Pack 5.2.6 or AIX Expansion Pack 5.3.2 must be installed and running. If you have the Expansion Pack CDs, the Pegasus packages are located on CD 1 of the Expansion Pack. On the CD label the number LCD 4-7515-02 is shown. The part number for the Expansion Pack itself is LCD 4-1142-08. Since October 2005 new Expansion Pack Editions are available (5.2.7 and 5.3.3), containing an updated Pegasus CIM Server. They can be found on the CD with label LCD4-1163-14 for AIX 5.2, and on the CD with label LCD4-7477-04 for AIX 5.3. For more information refer to http://www-03.ibm.com/servers/aix/expansionpack/ 3.0 INSTALLATION INSTRUCTIONS 3.1. General notes Before migrating from Performance Expert Version 1 to Version 2, read the following sections in 'Installation and Configuration', SC18-9191: - Before you install Performance Expert on Windows - Before you install Performance Expert on UNIX and Linux systems For referencing DB2 tools publications please go to: http://www-306.ibm.com/software/data/db2imstools/db2tools-library.html The Performance Expert Client V2.2.0.1 (fix pack 1) can run with the Performance Expert Server V2.2.0, but Peformance Expert Server V2.2.0.1 (fix pack 1) can not run with the Performance Expert Client V2.2.0. If you plan to install fix pack 1 of the Performance Expert Client and the Performance Expert Server on different dates, then install fix pack 1 of the Performance Expert Client first. 3.2 UNIX- and Linux-specific installation information This section lists brief instructions about how to install and configure Performance Expert on UNIX and Linux systems. For a detailed description, refer to the following chapters in 'Installation and Configuration', SC18-9191: - Configurations for Performance Expert - Installing Performance Expert Client on UNIX and Linux systems - Installing Performance Expert Server on UNIX and Linux systems - Configuring Performance Expert Server on UNIX and Linux systems 3.2.1 Performance Expert Server (base product) Step 1: The installer needs Java 1.4. Check whether Java 1.4 is installed on the machine. If not, install the jar file that is delivered together with the Performance Expert Server installation files. Execute as root: jar -xvf , e.g. jar -xvf aix32.jar cd < installed Java path> chmod -R 755 Ensure that the platform jar files are located in the same path as the installation files. Step 2: Install the Performance Expert Server by executing one of the following commands as root and follow the instructions: db2pe.server.v2.2.install-on-aix db2pe.server.v2.2.install-on-solaris db2pe.server.v2.2.install-on-xlinux db2pe.server.v2.2.install-on-zlinux db2pe.server.v2.2.install-on-plinux db2pe.server.v2.2.install-on-hpux If you want to use the console mode instead of the graphical mode, add the following option to the program call: -is:javaconsole -console Step 3: If not already existing, create the DB2 instance on which the 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 4: 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 5: Set up the DB2 instance for the Performance Expert Server by executing the following command as root from the bin directory of your installation, for example /opt/IBM/db2pesrv/V2.2/bin: ./pecentralize db2inpe Change instance name 'db2inpe' as required. Step 6: Configure the DB2 instance for the 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.2/bin: ./peconfig -console Step 7: 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.2/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 to Step 4 in section 3.2.1 Performance Expert Server (base product). Step 1: Stop the Performance Expert Server if it is running. Step 2: Install the fix pack by executing one of the following commands as root and follow the instructions: db2pe.server.v2.2.fp1.install-on-aix db2pe.server.v2.2.fp1.install-on-solaris db2pe.server.v2.2.fp1.install-on-xlinux db2pe.server.v2.2.fp1.install-on-zlinux db2pe.server.v2.2.fp1.install-on-plinux db2pe.server.v2.2.fp1.install-on-hpux If you want to use the console mode instead of the graphical mode, add the following option to the program call: -is:javaconsole -console If you have installed, but not yet configured and used the base product, proceed with Step 5 and the following steps in section '3.2.1 Performance Expert Server (base product)'. Step 3: 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.2/bin: ./pestart 3.2.3 Performance Expert Client Step 1: The installer needs Java 1.4. Check whether Java 1.4 is installed on the machine. If not, install the jar file that is delivered together with the Performance Expert Client installation files. Execute as root: jar -xvf , e.g. jar -xvf aix32.jar cd < installed Java path> chmod -R 755 Ensure that the platform jar files are located in the same path as the installation files. Step 2: Install the Performance Expert Client by executing one of the following commands as root and follow the installation instructions: db2pe.client.v2.2.fp1.install-on-aix db2pe.client.v2.2.fp1.install-on-solaris db2pe.client.v2.2.fp1.install-on-xlinux db2pe.client.v2.2.fp1.install-on-plinux If you want to use the console mode instead of the graphical mode, add the following option to the program call: -is:javaconsole -console Step 3: 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/V2.2/bin: ./db2pe If you want to execute the function 'New DB2 System' in the Performance Expert Client, ensure that the user who starts the Performance Expert Client has SYSADM or SYSCTRL authority on the DB2 instance on which the Performance Expert Client runs. This authority is needed to catalog and uncatalog databases. 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: - 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 (base product) Step 1: The installer needs Java 1.4. Check whether Java 1.4 is installed on the machine. If not, install the jar file that is delivered together with the Performance Expert Server installation files: jar -xvf , e.g. jar -xvf win32.jar Ensure that the platform jar files are located in the same directory as the installation files. Step 2: Define a user group and put all users of Performance Expert Client and Performance Expert Server in this group. Alternatively, do this during the installation of Performance Expert Server. Step 3: Install Performance Expert by executing one of the following commands as administrator user and follow the installation instructions: db2pe.server.v2.2.install-on-win.exe db2pe.server.v2.2.install-on-win.workgroup-edition.exe During the installation, you can configure the DB2 instance on which the Performance Expert Server should run. If you want to do this after the installation, perform Step 4. Step 4: If not already done during Step 3, configure the DB2 instance for the 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 5: Start the 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 to Step 3 in section '3.3.1 Performance Expert Server (base product). Step 1: Stop the Performance Expert Server if it is running. Step 2: Install the Performance Expert Servefr by executing one of the following commands as administrator user and follow the instructions: db2pe.server.v2.2.fp1.install-on-win.exe db2pe.server.v2.2.fp1.install-on-win.workgroup-edition.exe If you have installed but not yet configured and used the base product, proceed with Step 4 and the following steps of section '3.3.1 Performance Expert Server (base product)'. Step 3: Start the Performance Expert Server. 3.3.3 Performance Expert Client Step 1: The installer needs Java 1.4. Check whether Java 1.4 is installed on the machine. If not, install the jar file that is delivered together with the Performance Expert Server installation files: jar -xvf , e.g. jar -xvf win32.jar Ensure that the platform jar files are located in the same directory as the installation files. Step 2: Install the Performance Expert Client by executing the following command and follow the installation instructions: db2pe.client.v2.2.fp1.install-on-win.exe Step 3: Start the Performance Expert Client. If you want to execute the function 'New DB2 System' in the Performance Expert Client, ensure that the user who starts the Performance Expert Client has SYSADM or SYSCTRL authority on the DB2 instance on which the Performance Expert Client runs. The authority is needed to catalog and uncatalog databases. 4.0 CUSTOMIZATION AND USAGE INSTRUCTIONS 4.1 Enabling access to a CIM Server If you want to collect operating system data by using a CIM Server, you must install, configure, and run a CIMOM version on the monitored DB2 instance. This is described in 'Installation and Configuration', SC18-9191, in Chapter 4 for Windows, and in Chapter 10 for UNIX and Linux systems. If you migrate from Performance Expert V2.1 to V2.2, and if you want to collect operating system data for a monitored DB2 instance, you must also change the configuration of the monitored DB2 instance. The reason is that the default setting to access the CIM Server is set to 'No' when you migrate the configuration data. To change the configuration, configure Performance Expert Server in one of the following ways: - By using the configuration GUI: Select 'Use CIM to retrieve operating system data.' This is described in Appendix D of 'Installation and Configuration', SC18-9191. - By using the command line utility: Answer the following question with 'Y': 'Do you want to configure access to CIMOM (Y/N)' This is described in Appendix A of 'Installation and Configuration', SC18-9191. 4.2 CIM Server 4.2.1 Retrieving process information on the Performance Expert Client If you monitor a DB2 instance located on an AIX or Linux machine and have CIM enabled, note the following: If you check 'Receive process information' on the panel Operating System Status->Processes, all running processes are displayed. The field 'CPU Usage %' shows only N/P values in online mode, but shows real usage values if you switch to history mode. 4.2.2 Changing history collection for processes (CPU usage %) In history mode only those processes are collected and displayed by default that exceed a CPU usage of 2%. Dependent on the type and number of processes running, it might happen that no processes are collected and displayed in history mode because none has a CPU usage of at least 2%. If you want to change this threshold, do the following: 1. On the Performance Expert Server machine, connect to the performance database of your monitored instance. 2. For changing the value issue the following SQL statement: db2 update db2pm.parameter set PA_INTVALUE= where PA_KEY=MIN_PROCESS_PCT_CPU_TIME Note that is to be specified as hundredfold of the percentage value, for example, 100 for 1%. 3. Restart the Performance Expert Server. 4.3 Using Performance Expert with DB2 Version 8 Fix Pack 9 or later DB2 Version 8 Fix Pack 9 or later no longer supports SERVER authentication of a DB2 client, if the database manager parameter AUTHENTICATION of the DB2 server is set to SERVER_ENCRYPT. Performance Expert supports this DB2 change, but under certain conditions you might get an authentication error if DB2 Version 8 Fix Pack 9 is used for the monitored DB2 instances or for the DB2 instance where the Performance Expert Server runs. The authentication error message can be: SQL30082N Attempt to establish connection failed with security reason "17" ("UNSUPPORTED FUNCTION"). SQLSTATE=08001 The conditions are listed below, together with a solution: Conditions (Performance Expert Client): 1) The database manager configuration parameter AUTHENTICATION is set to SERVER_ENCRYPT for the DB2 Version 8 Fix Pack 9 or later instance where the Performance Expert Server runs, and you have migrated from an earlier version of Performance Expert or are still using an earlier version. The authentication error appears on your Performance Expert clients. Solution for 1): On your Performance Expert Clients, the performance databases of the Performance Expert Server must be recataloged to change the authentication to one compatible with SERVER_ENCRYPT. After installing the Performance Expert Client Version 2.2, perform the following before starting the client: As a user with DB2 administration rights (SYSADM) on the Performance Expert Client, change to the bin directory of your Performance Expert client Version 2.2 installation and invoke the following command to recatalog the Performance Expert databases: java -jar recatdb.jar Ensure that Java 1.4.2 is called by adding it to your PATH variable or by fully qualifying the java call. For example, on Windows: "c:\Program Files\IBM\IBM DB2 Performance Expert V2\java142\jre\bin\java" -jar recatdb.jar Conditions (Performance Expert Server): 2) The database manager configuration parameter AUTHENTICATION is set to SERVER_ENCRYPT for the DB2 Version 8 Fix Pack 9 or higher monitored instances, and you have migrated from an earlier version of Performance Expert or are still using an earlier version. The authentication error appears on your Performance Expert server. Solution for 2): On your Performance Expert Server, the monitored databases must be recataloged to change the authentication to one compatible with SERVER_ENCRYPT. As a user with DB2 administration rights (SYSADM) on the DB2 instance where the Performance Expert Server runs, change to the bin directory of your Performance Exert Server Version 2.2 installation and invoke the following command to recatalog the databases that Performance Expert monitors: java -jar recatdb.jar Ensure that Java 1.4.2 is called by adding it to your PATH variable or by fully qualifying the java call. Ensure that you access a 32-bit or 64-bit Java version, depending on whether the DB2 instance where the Performance Expert Server runs is a 32-bit or 64-bit version. For example, on UNIX in ksh shell, export the PATH variable by using the following command: export PATH=/opt/IBM/db2pesrv/V2.2/java142/jre/bin:$PATH On UNIX, additionally ensure that the bin directory of the Performance Expert Server installation and the lib directory of the DB2 Version 8 Fix Pack 9 installation is contained in the library search path environment variable. Set the environment variable, before calling the recatalog tool, for example by using the following command in ksh shell on AIX: export LIBPATH=/opt/IBM/db2pesrv/V2.2/bin:/usr/opt/db2_08_01/lib:$LIBPATH Note that the name of the environment variable is different on the different UNIX platforms: On AIX the name is LIBPATH, on Linux, Solaris and HP/UX (64bit) LD_LIBRARY_PATH. On HP/UX (32 bit) the name is SHLIB_PATH. 4.4 Importing CM- and BI-specific data views In the samples/SystemHealth directory of your Performance Expert Client installation a set of XML files is provided that contain either IBM Content Manager (CM) or Business Intelligence (BI) specific data view definitions. These XML files can be imported into the System Health component of the Performance Expert client and help you to set up your System Health view quickly if you monitor either a BI or a CM system. On the Performance Expert Client open the System Health component, right-click Data Groups, and select Import. Navigate to the samples/SystemHealth directory containing the XML files, select an XML file and press Open. Some of the data view definitions in these XML files require parameters to be adapted to your environment, for example buffer pool names. You can change these during importing the data views. After importing, the data group is displayed in your navigation tree in System Health. Repeat these steps for each XML file you want to import. The CM data view definitions are provided in these XML files: CM_DataViews_CPU_Memory_Disk_Storage.xml, CM_DataViews_LibraryServer_PageIO.xml, CM_DataViews_Locks.xml, CM_DataViews_ResourceManager_PageIO.xml CM_DataViews_Workload.xml Most of these CM XML files can be important for your Library server system and your Resource Manager system. Each file, after being imported, results in a new data group with the respective data view definitions. Some of the data views are preselected for being displayed in System Overview. The BI data views are provided in another set of XML files. The following list describes, for each XML file, the parameters that should be specified during the import: BI_DataViews_CPU_Memory_Disk.xml: Specify the disks for which you want to monitor I/O activity. BI_DataViews_FCM.xml: Specify the partitions for which you want to monitor FCM buffer activity. BI_DataViews_Sorts.xml, BI_DataViews_IncrementalLoad.xml, BI_DataViews_PageIO.xml and BI_DataViews_Workload.xml: Specifiy the database of which you want to monitor sorting, data loading, page I/O and general workload. If you have only one database, nothing must be specified. BI_DataViews_Sorts.xml: Specify the disks where your temporary tablespaces are located. BI_DataViews_Storage.xml: Specify the file systems for which you want to monitor usage activity. CM_DataViews_CPU_Memory_Disk.xml: Specify the disks of which you want to monitor I/O activity and the file systems for which you want to monitor usage activity. CM_DataViews_Workload, CM_DataViews_Locks: Specifiy the database of which you want to monitor sorting, locks and general workload. If you have only one database, nothing must be specified. CM_DataViews_LibraryServer_PageIO: For the data view 'Compare Hit Ratios (%) for buffer pools' select the following buffer pools of your Library Server database: CMBMAIN, ICMLSFREQBP4, ICMLSMAINBP32, ICMLSVOLATILEBP4 For the data view 'Compare Asynchronous Write Ratio (%) for buffer pools' select the following buffer pools of your Library Server database: ICMLSMAINBP32, ICMLSVOLATILEBP4 CM_DataViews_ResourceManager_PageIO: For the data view 'Compare Hit Ratios (%) for buffer pools' select the following buffer pools of your Resource Manager database: BLOBPOOL, OBJECTPOOL, PARTSPOOL, SMSPOOL, TRACKINGPOOL 4.5 Using the IBM Content Manager threshold set Performance Expert provides a predefined threshold set, named IBM Content Manager. This threshold set can be used if you monitor Content Manager (CM) DB2 databases, such as the Library Server (LS) or a Resource Manager (RM) database. Note that the thresholds are based on settings for a mid- to large-sized system and might need adjustments for your environment. If you are monitoring Operating System parameters with Performance Expert, you might want to add the following additional threshold: Exception Category: Operating System Subcategory: Storage Exception Field: Free Space Qualifier: Volume Name for the following items: LS and RM database (if SMS table spaces are used), LS Staging Area (if LANCache is used) and RM LBOSDATA. For the LS Staging Area the threshold values should be lower than the value that is defined in the purger setting of the CM admin server. 5.0 CORRECTIONS TO DOCUMENTATION For a complete list of documentation enhancements refer to the section 'Summary of changes' in 'Installation and Configuration', SC18-9191, and to the section 'What's new?' in 'Monitoring Performance from the Workstation', SC18-7976. 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 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 Other notices 7.2.1 OpenPegasus OpenPegasus is an excluded component. License: Copyright (c) 2000, 2001, 2002 BMC Software; Hewlett-Packard Development Company, L. P.; IBM Corp.; The Open Group; Tivoli Systems. Copyright (c) 2003 BMC Software; Hewlett-Packard Development Company, L. P.; IBM Corp.; EMC Corporation; The Open Group. Copyright (c) 2004 BMC Software; Hewlett-Packard Development Company, L. P.; IBM Corp.; EMC Corporation; VERITAS Software Corporation; The Open Group. Copyright (c) 2005 Hewlett-Packard Development Company, L. P.; IBM Corp.; EMC Corporation; VERITAS Software Corporation; The Open Group. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: THE ABOVE COPYRIGHT NOTICE AND THIS PERMISSION NOTICE SHALL BE INCLUDED IN ALL COPIES OR SUBSTANTIAL PORTIONS OF THE SOFTWARE. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. 7.2.2 Info-Zip unzipSFX stub file and hsqldb Info-Zip unzipSFX stub file and hsqldb are excluded components and third party code. THIRD PARTY LICENSE TERMS AND CONDITIONS, NOTICES AND INFORMATION The license agreement for this product refers you to this file for details concerning terms and conditions applicable to third party software code included in this product, and for certain notices and other information IBM must provide to you under its license to certain software code. The relevant terms and conditions, notices and other information are provided or referenced below. Please note that any non-English version of the licenses below is unofficial and is provided to you for your convenience only. The English version of the licenses below, provided as part of the English version of this file, is the official version. Notwithstanding the terms and conditions of any other agreement you may have with IBM or any of its related or affiliated entities (collectively "IBM"), the third party software code identified below are "Excluded Components" and are subject to the following terms and conditions: - the Excluded Components are provided on an "AS IS" basis; - IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT NOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE AND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE; - IBM will not be liable to you or indemnify you for any claims related to the Excluded Components; and - IBM will not be liable for any direct, indirect, incidental, special, exemplary, punitive or consequential damages with respect to the Excluded Components. UnZipSFX Stub file: The Program includes "UnZipSFX stub" software from the Info-Zip group which is Copyright (c) 1999-2002, Info-ZIP. All rights reserved. IBM did not modify the UnZipSFX software. There are no extra charges or costs due to the use of this code, and the original compression sources are freely available from http http://www.info-zip.org/ on the Internet. 7.3 Trademarks and service marks The following terms are trademarks or service marks of the IBM Corporation in the United States, other countries, or both: AIX DB2 IBM 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. 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, 2005. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.