IBM DB2 Universal Database* Version 7 FixPak 6 for Windows 95/98/NT/2000/Me/XP 1) Overview of FixPak for IBM DB2 Universal Database* Version 7 FixPak 6 for Windows 95/98/NT/2000/Me/XP IBM DB2 Universal Database* Version 7 FixPak 6 for Windows 95/98/NT/2000/Me/XP PTF No: WR21299 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 Data Links Manager, 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 Relational Connect, Version 7.2 * DB2 Run-Time Client, Version 7.2 * DB2 Spatial Extenders, Version 7.2 * DB2 UDB Enterprise Edition, Version 7.2 * DB2 UDB Enterprise-Extended Edition, Version 7.2 * DB2 UDB Personal Edition, Version 7.2 * DB2 UDB Workgroup Edition, Version 7.2 * DB2 Warehouse Manager, Version 7.2 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:\Program Files\sqllib . For additional information on changes to the product, review the product Release Notes: X:\RELEASE.TXT 2) Windows 95/98/NT/2000/Me/XP Installation Notes 2a) Prerequisites This FixPak requires one of the following DB2 products: * DB2 UDB Version 7.2 for Windows, or * DB2 UDB Version 7.1 for Windows with DB2 V7 FixPak 3 or higher To determine the version and level of the currently installed DB2 product, type regedit from an MS-DOS prompt and check the following values under the registry key HKEY_LOCAL_MACHINE\SOFTWARE\IBM\DB2\\CurrentVersion The values should be the following: * Version "7" * Release "1" * Modification "3" 2b) Installing Non-English Versions of DB2 on Windows 95 You will need to manually upgrade WinSock to version 2 if you are installing DB2 on a Windows 95 machine that uses a non-English language. The English-language version of DB2 will upgrade WinSock 1.1 to Version 2 automatically during the install process. Non-English versions of DB2 will fail to install if WinSock is not upgraded prior to installation. If you are installing DB2 on a non-English Windows 95 machine, please download the WinSock 2 upgrade facility from the following Microsoft web site: http://www.microsoft.com/windows95/downloads/contents/WUAdminTools/ S_WUNetworkingTools/W95Sockets2/Default.asp Follow the Microsoft installation instructions to upgrade WinSock to Version 2, and then proceed with the DB2 installation. 2c) Installation Instructions Note: Once you have installed a FixPak, you cannot uninstall it. Stop all database activity before applying this FixPak. To stop all database activity, issue the commands: db2stop db2admin stop To install the FixPak, run: X:\SETUP.EXE or run: X:\SETUP.EXE /i where is the language that you want to install. The locale option specified is valid only if that locale exists on the media being used. If the 1.cab file exists in the db2\common\ or db2\windows\common\ directories on the media, then the specified is valid. The valid locale codes are: ENGLISH_UNITEDSTATES "EN" BULGARIAN "BG" CHINESE_TAIWAN "TW" CHINESE_PRC "CN" CZECH "CZ" DANISH "DK" DUTCH "NL" FINNISH "FI" FRENCH_STANDARD "FR" GERMAN "DE" GREEK "GR" HEBREW "IL" HUNGARIAN "HU" ITALIAN "IT" JAPANESE "JP" KOREAN "KR" NORWEGIAN "NO" POLISH "PL" PORTUGUESE_BRAZILIAN "BR" PORTUGUESE_STANDARD "PT" SLOVENIAN "SI" SPANISH "ES" SWEDISH "SE" RUSSIAN "RU" TURKISH "TR" 2c.i) Applying FixPak on Windows XP After installing a DB2 version 7.2 FixPak on Windows XP, restart the machine. 2c.ii) Applying FixPak for Data Links Manager 1. As the DB2 Data Links Manager Administrator (dlmadmin), bring down the DB2 Data Links Manager by stopping the DB2 Data Links Manager service: Start->Settings->Control Panel->Services Stop DB2 Data Links Manager Ensure that there are no other DB2 processes remaining, by issuing a db2stop for each instance. 2. Install the FixPak 3. As the DB2 Data Links Manager Administrator, run the following commands to bring up the DB2 Data Links Manager: dlfm bind dlfm start Check the db2diag.log to ensure that the Data Links Manager is started properly. 2d) Unattended Install Instructions The version of SETUP.EXE shipped with this FixPak is capable of running via an "unattended install" option. The syntax for this feature is documented in the Quick Beginnings book. A sample response file (DB2FIXPK.RSP) is included in this FixPak. 2e) After Installation 2e.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. 2e.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. 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.iii) DataJoiner Replication Administration Tool The DataJoiner Replication Administration (DJRA) tool (djra.exe) is now installed in the directory $DB2DIR\DJRA. 2f) Uninstallation Notes When upgrading or uninstalling the DB2 product(s) on a Windows NT system, it is recommended that you manually shut down all DB2 services and processes on your machine. Note: Once you have installed the FixPak, you cannot uninstall it. 2g) Special Notes 2g.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. 2g.ii) Using DB2 XML Extender The readme.nt file incorrectly lists Software Requirements of DB2 Universal Database Version 6.1 or higher with FixPak 3 installed. This is incorrect. The DB2 XML Extender requires DB2 Version 7.1 or 7.2. 2g.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. 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. ** *******************************************************************************