IBM DB2 Universal Database* Version 7 FixPak 6 for OS/2* 1) Overview of FixPak for IBM DB2 Universal Database* Version 7 FixPak 6 for OS/2* IBM DB2 Universal Database* Version 7 FixPak 6 for OS/2* FixPak WR21298 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 Personal Edition, Version 7.2 * DB2 Connect Enterprise Edition, Version 7.2 * DB2 Run-Time Client, Version 7.2 * DB2 UDB Enterprise Edition, Version 7.2 * DB2 UDB Personal Edition, Version 7.2 * DB2 UDB Workgroup Edition, Version 7.2 * DB2 Warehouse Manager, Version 7.2 Before installing this DB2 for OS/2 FixPak, ensure that the line in your CONFIG.SYS file which initializes the HPFS file system is at the beginning of the file (if HPFS is being used). You can identify this line by looking for one similar to the following: IFS=C:\OS2\HPFS.IFS /CACHE:2048 /CRECL:4 /AUTOCHECK:CDE If it is not at the beginning of your CONFIG.SYS file, move it there before the DB2 FixPak installation. Throughout this document X: is used to refer to the CD-ROM drive into which the FixPak CD is placed and $DB2DIR is where the DB2 products are installed. By default, $DB2DIR is C:\SQLLIB. For additional information on changes to the product, review the product Release Notes: X:\SQLLIB\RELEASE.TXT 2) OS/2 Installation Notes 2a) Prerequisites Before installing this FixPak you must have DB2 UDB V7.2 or DB2 UDB V7.1 with FixPak 3 installed. To determine if the required prerequisites are installed, do the following: * Double-click on the Installation Utility icon in the IBM DB2 folder. * Select View, Installed Products. * Select the appropriate DB2 product. * Select Details, Product Status. The version should be 07.02.04 2b) Installation Instructions Stop all database activity before applying this FixPak. To stop all database activity, issue these commands: db2stop db2admin stop To install the FixPak, type X:\DB2\\INSTALL\INSTALL where is the appropriate language directory. You will be presented with a list of products currently installed. Select a product and then select UPDATE from the Action pull-down menu. You must install the FixPak for every product listed (it is not necessary to re-boot after each one, even if the completion message says so, it is sufficient to re-boot after all products have been updated). If you use ODBC applications, re-run the ODBC Installer after re-booting, by double-clicking on the icon. Note: Do not select the Save a backup version? check box. This will not properly backup the changes and restoring from the backup may damage the installed DB2 UDB product(s). 2c) Unattended Installation Instructions The FixPak install program (INSTALL.EXE) supports unattended installation using a response file. The syntax for this feature is documented in the Quick Beginnings book. A response file (DB2FIXPK.RSP) is provided for your convenience. It can be used without modification. * Each product must be updated separately. * Every DB2 UDB product that is installed on the system must be updated with this FixPak at the same time. You cannot mix service levels between the products. * A /P:"product name" command line parameter is required. The following sample command files are provided with the FixPak for your convenience: * DB2CONPE.CMD DB2 Connect Personal Edition * DB2CONEE.CMD DB2 Connect Enterprise Edition * DB2UDBEE.CMD DB2 Universal Database Enterprise Edition * DB2UDBWE.CMD DB2 Universal Database Workgroup Edition * DB2UDBPE.CMD DB2 Universal Database Personal Edition * DB2SDK.CMD DB2 Application Development Client * DB2ADMCL.CMD DB2 Administration Client * DB2RTCL.CMD DB2 Run-Time Client * DB2UDBWM.CMD DB2 Database Warehouse Manager 2d) After Installation 2d.i) 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.ii) 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: db2 terminate db2 CONNECT TO db2 BIND $DB2DIR\BND\@db2ubind.lst GRANT PUBLIC db2 BIND $DB2DIR\BND\@db2cli.lst GRANT PUBLIC db2 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 $DB2DIR\BND\@ddcsmvs.lst BLOCKING ALL SQLERROR CONTINUE GRANT PUBLIC VM BIND $DB2DIR\BND\@ddcsvm.lst BLOCKING ALL SQLERROR CONTINUE GRANT PUBLIC VSE BIND $DB2DIR\BND\@ddcsvse.lst BLOCKING ALL SQLERROR CONTINUE GRANT PUBLIC OS400 BIND $DB2DIR\BND\@ddcs400.lst BLOCKING ALL SQLERROR CONTINUE GRANT PUBLIC Rebinding Specific Packages If you want to bind only the specific .bnd files to the database, issue the following commands for each database. db2 terminate db2 CONNECT TO db2 BIND $DB2DIR\BND\ BLOCKING ALL GRANT PUBLIC db2 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) 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. 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. ** *******************************************************************************