IBM DB2 Universal Database* Version 7 Fixpak 5sc for Windows 95/98/NT/2000/Me ------------------------------------------------------------------------ Contents Overview of FixPak for IBM DB2 Universal Database* Version 7 Fixpak 5sc for Windows 95/98/NT/2000/Me Windows 95/98/NT/2000/Me Installation Notes * 2.1 Prerequisites * 2.2 Prior to Installation * 2.3 Installation Instructions o 2.3.1 Applying FixPak on Windows XP o 2.3.2 Applying FixPak for Data Links Manager * 2.4 Unattended Install Instructions * 2.5 After Installation o 2.5.1 Enabling the New SQL Built-in Scalar Functions o 2.5.2 Rebinding Bind Files + 2.5.2.1 Rebinding to Non-DRDA DB2 Databases + 2.5.2.2 Rebinding to DRDA Databases + 2.5.2.3 Rebinding Specific Packages o 2.5.3 DataJoiner Replication Administration Tool * 2.6 Uninstallation Notes * 2.7 Special Notes o 2.7.1 Loss of Control Center Functionality o 2.7.2 Using DB2 XML Extender o 2.7.3 Restoring backup images created under FixPak 4 or greater Service * 3.1 Product and Service Technical Library * 3.2 Customer Support * 3.3 Corrective Service Notices ------------------------------------------------------------------------ Overview of FixPak for IBM DB2 Universal Database* Version 7 Fixpak 5sc for Windows 95/98/NT/2000/Me IBM DB2 Universal Database* Version 7 Fixpak 5sc for Windows 95/98/NT/2000/Me PTF No: WR21294_5450 VRMF: 7.1.0.55 Note: To read this file more easily, set your font to monospace. If you have received special fixes from IBM support since 12/11/2001, 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 Fixpak 5sc * DB2 Application Development Client, Version 7 Fixpak 5sc * DB2 Connect Personal Edition, Version 7 Fixpak 5sc * DB2 Connect Enterprise Edition, Version 7 Fixpak 5sc * DB2 Data Links Manager, Version 7 Fixpak 5sc * DB2 Life Sciences Data Connect, Version 7 Fixpak 5sc * DB2 OLAP Starter Kit , Version 7 Fixpak 5sc * DB2 Query Patroller, Version 7 Fixpak 5sc * DB2 Relational Connect, Version 7 Fixpak 5sc * DB2 Run-Time Client, Version 7 Fixpak 5sc * DB2 Spatial Extenders, Version 7 Fixpak 5sc * DB2 UDB Enterprise Edition, Version 7 Fixpak 5sc * DB2 UDB Enterprise-Extended Edition, Version 7 Fixpak 5sc * DB2 UDB Personal Edition, Version 7 Fixpak 5sc * DB2 UDB Workgroup Edition, Version 7 Fixpak 5sc * DB2 Warehouse Manager, Version 7 Fixpak 5sc Throughout this document X: is used to refer to the CD-ROM drive into which the FixPak CD is placed and C:\SQLLIB is where the DB2 products are installed. For additional information on changes to the product, review the product Release Notes: X:\SQLLIB\RELEASE.TXT ------------------------------------------------------------------------ Windows 95/98/NT/2000/Me Installation Notes ------------------------------------------------------------------------ 2.1 Prerequisites This FixPak requires that at least one Version 7.1 FixPak 3 or Version 7.2 DB2 UDB for Windows product is already installed on your system. 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" * Service Level "WR21254" ------------------------------------------------------------------------ 2.2 Prior to Installation It is recommended you stop all database activity before applying this FixPak. To stop all database activity, issue the commands: db2stop db2admin stop ------------------------------------------------------------------------ 2.3 Installation Instructions Note: Once you have installed a FixPak, you cannot uninstall it. To start 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" 2.3.1 Applying FixPak on Windows XP After installing a DB2 version 7.2 FixPak on Windows XP, restart the machine. 2.3.2 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. ------------------------------------------------------------------------ 2.4 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. ------------------------------------------------------------------------ 2.5 After Installation 2.5.1 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. 2.5.2 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. 2.5.2.1 Rebinding to Non-DRDA DB2 Databases After applying fixes, you must do the following: db2 terminate db2 CONNECT TO db2 BIND C:\SQLLIB\BND\@db2ubind.lst GRANT PUBLIC db2 BIND C:\SQLLIB\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. 2.5.2.2 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 C:\SQLLIB\BND\@ddcsmvs.lst BLOCKING ALL SQLERROR CONTINUE GRANT PUBLIC VM BIND C:\SQLLIB\BND\@ddcsvm.lst BLOCKING ALL SQLERROR CONTINUE GRANT PUBLIC VSE BIND C:\SQLLIB\BND\@ddcsvse.lst BLOCKING ALL SQLERROR CONTINUE GRANT PUBLIC OS400 BIND C:\SQLLIB\BND\@ddcs400.lst BLOCKING ALL SQLERROR CONTINUE GRANT PUBLIC 2.5.2.3 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 C:\SQLLIB\BND\ BLOCKING ALL GRANT PUBLIC db2 terminate where is the name of the bind file, and is the name of your database. 2.5.3 DataJoiner Replication Administration Tool The location of the DataJoiner Replication Administration (DJRA) tool (djra.exe) is now installed in the directory SQLLIB\DJRA. ------------------------------------------------------------------------ 2.6 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. ------------------------------------------------------------------------ 2.7 Special Notes 2.7.1 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. 2.7.2 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. 2.7.3 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. ------------------------------------------------------------------------ Service ------------------------------------------------------------------------ 3.1 Product and Service Technical Library For a complete and up-to-date source of DB2 information, including information on issues discovered after this readme was published, go to the following web sites: DB2 Product and Service Technical Library: http://www.ibm.com/software/data/db2/library DB2 Universal Database and DB2 Connect Online Support: http://www.ibm.com/software/data/db2/udb/winos2unix/support DB2 Universal Database and DB2 Connect Online Support - Technical Library Search: http://www-4.ibm.com/cgi-bin/db2www/data/db2/udb/winos2unix/support/techlib.d2w/report ------------------------------------------------------------------------ 3.2 Customer Support To speak to an IBM representative regarding assistance with this product, call 1-800-237-5511. Customer support is also provided through Electronic Question and Answer (Q&A) forums. These forums are accessible through CompuServe, IBMLink, and Usenet Newsgroup. 1. CompuServe o To access the forums on CompuServe, execute GO IBMDB2. o If you don't have access to CompuServe, call 1-800-848-8199 for membership information in Canada or the US. 2. Usenet Newsgroup: comp.databases.ibm-db2 o This Internet Newsgroup is a general forum for discussing questions and/or problems encountered using the DB2 family of products. 3. (IBMLink) Talklink OS/2 BBS o To access the forums on IBMLink, go to the OS2BBS section. o If you don't have access IBMLink, call 1-800-547-1283 for membership information in Canada or the United States. ------------------------------------------------------------------------ 3.3 Corrective Service You can access corrective service using the following methods: 1. FTP to anonymous server 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). 2. Use a Web browser to connect to the DB2 UDB and DB2 Connect Online Support Page at: http://www.ibm.com/software/data/db2/udb/winos2unix/support 3. On CompuServe, execute GO IBMDB2. Then go to the appropriate library to find the FixPak. 4. On IBM PCC BBS (in US), call (919) 517-0001 (in Raleigh, North Carolina) and then type "db2" on the main menu to find the FixPaks. If you do not have access to any of the above locations, call 1-800-992-4777 to request these FixPaks be sent to you in the mail. For countries other than US and Canada, contact your local DB2 Customer Service number for assistance in obtaining them. ------------------------------------------------------------------------ Notices ------------------------------------------------------------------------------- * are trademarks or registered trademarks of IBM Corporation. ** are trademarks or registered trademarks of their respective owners. ------------------------------------------------------------------------------- ******************************************************************************* ** ** (c) COPYRIGHT INTERNATIONAL BUSINESS MACHINES CORPORATION 2001. ** ALL RIGHTS RESERVED. ** *******************************************************************************