IBM DB2 Universal Database* for Solaris** (32-bit) Version 7 FixPak 6 1) Overview of FixPak for IBM DB2 Universal Database* for Solaris** (32-bit) Version 7 FixPak 6 IBM DB2 Universal Database* for Solaris** (32-bit) Version 7 FixPak 6 PTF: U481409 VRMF: 7.1.0.60 Note: To read this file more easily, set your font to monospace. If you have received special fixes from IBM support since 03/13/2002, then you must contact IBM support to request an updated version of the special fixes instead of installing this FixPak. By doing this, you are assured that your system is in a consistent state and no special fixes are lost. This README file contains information for the following products and components: * DB2 Administration Client, Version 7.2 * DB2 Application Development Client, Version 7.2 * DB2 Connect Enterprise Edition, Version 7.2 * DB2 Life Sciences Data Connect, Version 7.2 * DB2 OLAP Starter Kit, Version 7.2 * DB2 Query Patroller, Version 7.2 * DB2 Run-Time Client, Version 7.2 * DB2 UDB Enterprise Edition, Version 7.2 * DB2 UDB Enterprise-Extended Edition, Version 7.2 * DB2 UDB Workgroup Edition, Version 7.2 * DB2 Warehouse Manager, Version 7.2 For additional information on changes to the product, review the product Release Notes: /opt/IBMdb2/V7.1/Readme/%L/Release.Notes where %L is the locale name. If you are planning to install DB2 Query Patroller for the first time on AIX*, HP-UX, NUMA-Q/PTX, or the Solaris** Operating Environment, before you begin, refer to the technote "Installing DB2 Query Patroller version 7.1 and 7.2 on UNIX**," available from the DB2 Universal Database Online Support web page at http://www.ibm.com/software/data/db2/udb/winos2unix/support. 2) Solaris (32-bit) Installation Notes 2a) Prerequisites You must have DB2 UDB V7.2 or DB2 UDB V7.1 with FixPak 3 or greater already installed before installing this FixPak. Use the following command to determine the current level of DB2 installed on the system: pkginfo -l db2cliv71 | grep VERSION Look for the following output: VERSION: 7.1.x.y where x = 0 and y >= 40. If x = 1, then you have 64-bit DB2 installed, and cannot apply the 32-bit FixPak. If y < 40, you must install FixPak 3 first. If you receive an error, DB2 version 7 is not installed on your system. 2b) Prior to Installation Log on as root and enter the following commands for each instance: su - iname . $HOME/sqllib/db2profile db2 force applications all db2 terminate db2stop db2licd end # run at each physical node exit where iname is the instance owner name. Then, while still logged on as root, enter the following commands: su - aname . $HOME/sqllib/db2profile db2admin stop exit where aname is the administration server name. 2c) Installation Instructions In previous FixPaks, a script called installallpatch was used to start the FixPak installation process. Beginning with this FixPak, the installation script is called installFixPak. The installFixPak script is the recommended method for installing this FixPak. To install the FixPak: su - root cd ./installFixPak where is the top directory in which the FixPak image is located. 2d) After Installation 2d.i) Update Instances Note: You need to be logged on as root to update the instances. For each instance, issue the command: /opt/IBMdb2/V7.1/instance/db2iupdt iname where iname is the instance name. Note: If you are running both Enterprise - Extended Edition (EEE) and Enterprise Edition (EE) on the same machine, then you need to run db2iupdt with the "-k" option. Otherwise, it will check to see if EEE filesets exist; if they do, it will perform the update as if it was an EEE instance. For the DAS instance, issue the command: /opt/IBMdb2/V7.1/instance/dasiupdt dasname where dasname is the DAS instance name. For more information on the db2iupdt or dasiupdt commands, run db2iupdt or dasiupdt with the "-h" option. 2d.ii) Enabling the New SQL Built-in Scalar Functions FixPak 2 and later of Version 7 delivers new SQL built-in scalar functions. Refer to the SQL Reference and updates in the Release Notes for a description of these new functions. The new functions are not automatically enabled on each database when the database server code is upgraded to FixPak 2 or later of Version 7.1. To enable these new functions, you must login as the instance (or a SYSADM user) and issue the command db2updv7, specifying each database for each instance. This command makes an entry in the database that ensures that database objects created prior to executing this command use existing function signatures that may match the new function signatures. WARNING about use of db2updv7: If you intend to issue the db2updv7 command, you must be aware that it will change the database to run only with Version 7.1 FixPak 2 (or higher) of the database manager. You will not be able to run this database with any previous FixPak level. You must perform a full offline backup of the database prior to running db2updv7 in order to have the ability to restore to a previous FixPak level. 2d.iii) Rebinding Bind Files Due to the new bind (.bnd) files that have been shipped with this FixPak, you will need to rebind your DB2 utilities against all your databases after the FixPak installation. This step is necessary for the fixes in this FixPak to become effective. The procedure of rebinding, outlined below, only needs to be performed once per database. Rebinding to Non-DRDA DB2 Databases After applying fixes, you must do the following: - At a command prompt: db2 terminate db2 CONNECT TO db2 BIND /@db2ubind.lst BLOCKING ALL GRANT PUBLIC db2 BIND /@db2cli.lst BLOCKING ALL GRANT PUBLIC db2 terminate or, - At the DB2 command line: TERMINATE CONNECT TO BIND /@db2ubind.lst BLOCKING ALL GRANT PUBLIC BIND /@db2cli.lst BLOCKING ALL GRANT PUBLIC TERMINATE Where is the name of a database to which the utilities should be bound, and where is the full path name of the directory where the bind files are located, such as /sqllib/bnd. DB2UBIND.LST and DB2CLI.LST contain lists of commonly required bind files used for DB2. Rebinding to DRDA Databases If you are using DB2 Connect to connect to host databases, you will also need to bind the new bind files to the host. As above, use the DB2 Command Line Processor to connect to the host database, and then bind the utilities as follows: HOST COMMAND ======= =================================================== MVS BIND /@ddcsmvs.lst BLOCKING ALL GRANT PUBLIC SQLERROR CONTINUE VM BIND /@ddcsvm.lst BLOCKING ALL GRANT PUBLIC SQLERROR CONTINUE VSE BIND /@ddcsvse.lst BLOCKING ALL GRANT PUBLIC SQLERROR CONTINUE OS400 BIND /@ddcs400.lst BLOCKING ALL GRANT PUBLIC SQLERROR CONTINUE Please refer to "Binding Applications and Utilities" in the DB2 Connect User's Guide for a list of bind files that are used for your specific client operating system. If a bind file changes and your clients do not use that bind file, you do not need to re-bind it. Rebinding Specific Packages If you want to bind only the specific .bnd files to the database, issue the following commands for each database. - At a command prompt: db2 terminate db2 CONNECT TO db2 BIND / BLOCKING ALL GRANT PUBLIC db2 terminate or, - At the DB2 command line: TERMINATE CONNECT TO BIND / BLOCKING ALL GRANT PUBLIC TERMINATE where is the name of the bind file, and is the name of your database. 2e) Special Notes 2e.i) Loss of Control Center Functionality There should be no problems introduced against downlevel Control Center clients by applying FixPak 2 or FixPak 3 to a DB2 server. However, in DB2 Version 7.2, downlevel Control Center clients will lose nearly all functionality. Downlevel in this case refers to any Version 6 client prior to FixPak 6, and any Version 7 client prior to FixPak 2. Version 5 clients are not affected. The suggested fix is to upgrade any affected clients. Version 6 clients must be upgraded to FixPak 6 or later, and Version 7 clients must be upgraded to FixPak 2 or later. 2e.ii) Using DB2 XML Extender The README.TXT file for DB2 XML Extender Version 7.1 incorrectly states the following under "Considerations": * The default version of DB2 UDB is DB2 UDB Version 7.1. If you wish to use DB2 UDB Version 6.1 on AIX and Solaris, you should ensure that you are running with DB2 UDB V6.1 instances and with the DB2 UDB V6.1 libraries. This is incorrect. The DB2 XML Extender is supported only with DB2 Version 7.1 and 7.2. The readme.sun file incorrectly lists Software Requirements of DB2 UDB Version 6.1 with FixPak FP1_U465424 or higher. This is incorrect. The DB2 XML Extender requires DB2 Version 7.1 or 7.2. 2e.iii) Restoring backup images created under FixPak 4 or greater When the RELOCATE USING option is used with the db2inidb command, the user provided configuration file is copied into the database directory (for example, SQL00001) and is renamed to db2path.cfg. If the database was initialized as a snapshot then the db2path.cfg file will be removed after the necessary crash recovery completes. However, if the database was initialized as a standby then the file will only be removed after the database is taken out of the rollforward pending/in-progress state (by stopping or cancelling the rollforward). Databases can be backed up when in the rollforward pending/in-progress state. If the db2path.cfg file exists then it will be included in the backup image. Because this file is new to V7 beginning with FixPak 4, a restore of an image containing this file will fail on any V7 level earlier than FixPak 4. If restoring from such a backup image, the instance must be running with a DB2 level of FixPak 4 or greater. 2e.iv) Relational Connect and djxlink If you have DB2 Relational Connect installed, you must run the djxlink command after installing this FixPak and before running db2iupdt. Perform the following steps: 1. Log on as root. 2. Remove or rename the file djxlink.out, which is located in the $install_dir/lib/ directory, where $install_dir is the DB2 installation directory. 3. If you are using Relational Connect to connect to an Oracle data source, set the environment variable ORACLE_HOME to the oracle home directory. 4. Run the command: djxlink For more information on installing DB2 Relational Connect please see the DB2 Installation and Configuration Supplement. 3) DB2 Customer Support Web-based support for DB2 products, including documentation, FixPaks, and APAR information, is provided at http://www.ibm.com/software/data/db2/udb/winos2unix/support and http://www.ibm.com/software/data/db2/udb/support.html. DB2 FixPaks can also be downloaded from IBM's anonymous FTP server at ftp.software.ibm.com. Go to ps/products/db2/fixes/%L/%P/ where %L is the appropriate locale (for example, english-us, spanish, german), and %P is the product name/version (for example db2ntv71). The main Usenet newsgroup for DB2-related questions is comp.databases.ibm-db2. To contact DB2 Customer Service by phone: * In the United States, call 1-800-237-5511. * In Canada, call 1-800-IBM-SERV (426-7378). * Worldwide, call 1-404-238-1234 (charges may apply). For information on IBM offices in your country or region, consult IBM's Directory of Worldwide Contacts at http://www.ibm.com/planetwide. 4) Notices ------------------------------------------------------------------------------- * are trademarks or registered trademarks of IBM Corporation. ** are trademarks or registered trademarks of their respective owners. ------------------------------------------------------------------------------- ******************************************************************************* ** ** (c) COPYRIGHT INTERNATIONAL BUSINESS MACHINES CORPORATION 2002. ** ALL RIGHTS RESERVED. ** *******************************************************************************