IBM DB2 Universal Database* for Solaris** (64-bits) Version 7.1 PTF: U472546 VRMF: 07.01.0001.0000 +-- Note: --------------------------------------------------------------------+ | | To read this file more easily, set your font to monospace. | | If you have received interim fixes from IBM support after 07/27/2000, | you must contact IBM support to request an updated version of the interim | fixes instead of installing this FixPak. By doing this, you are assured that | your system is in an consistent state and no interim fixes are lost. | +-----------------------------------------------------------------------------+ This README file contains information for the following products and components: Solaris Specific ---------------- DB2 Connect Enterprise Edition, V7.1 DB2 UDB Workgroup Edition, V7.1 DB2 UDB Enterprise Edition, V7.1 DB2 UDB Enterprise - Extended Edition, V7.1 DB2 Application Development Client, V7.1 DB2 Run-Time Client, V7.1 =============================================================================== 1. Contents of FixPak 2. Installation Notes 2.1 Pre-requisites 2.2 Prior to Installation 2.3 Installation Instructions 2.4 Migration to 64-bit Solaris 2.5 After Installation 2.5.1 Updating instances to use the new fix level 2.5.2 Updating instances to use 64-bit 2.5.3 Rebinding bind files 2.5.3.1 Rebinding to non-DRDA DB2 databases 2.5.3.2 Rebinding to DRDA databases 2.5.3.3 Rebinding Specific Packages 3. Service 3.1 Product and Service Technical Library 3.2 Customer Support 3.3 Corrective Service For additional information please see the following files: /opt/IBMdb2/V7.1/Readme/%L/Release.Notes where %L is the locale name. ------------------------------------------------------------------------------- 2. Installation Notes 2.1 Prerequisites This FixPak requires one of the following to already be installed on the machine: DB2 Connect Enterprise Edition, V7.1 DB2 UDB Workgroup Edition, V7.1 DB2 UDB Enterprise Edition, V7.1 DB2 UDB Enterprise - Extended Edition, V7.1 DB2 Application Development Client, V7.1 DB2 Run-Time Client, V7.1 at the level: 07.01.0000.0000 and will upgrade to the level: 07.01.0001.0000 Use 'pkginfo | grep db2' to determine all DB2 UDB packages installed. The output of the command should include the following application db2cliv71 DB2 client Application Enabler 2.2 Prior to Installation Logon as root and do the following for each instance: su - iname . $HOME/sqllib/db2profile db2 force applications all db2 terminate db2stop db2licd end exit where iname is the instance name. Then, while still logged on as root, do the following: su - dasname . $HOME/sqllib/db2profile db2admin stop exit where dasname is the das instance name. 2.3 Installation Instructions run (as root) cd /cdrom/db2_for_solaris_v710_fixpak1 ./installallpatch 2.4 Migration to 64-bit Solaris To start using 64-bit DB2 on Solaris, you must download and install the 64-bit Solaris FixPak. This FixPak includes all 32-bit fixes as well as adds 64-bit DB2 functionality to your system. Once you have installed this FixPak, you cannot install 32-bit FixPaks, and must gain any new fixes through the 64-bit FixPaks. To install DB2 UDB 64-bit FixPak for Solaris with all the prerequisites in apply state, run the `installallpatch` script that came with the FixPak. Note: If you have already applied 32-bit FixPaks and you decide to move to 64-bit, it is highly recommended that you use a 64-bit FixPak of at least the same level so you do not lose any fixes that you had before moving to 64-bit. 2.5 After Installation 2.5.1 Updating instances to use the new fix level To use the new fix level, you will still need to issue the standard update as if this were the normal 32-bit FixPak. For all instances, whether migrating to 64-bit or not, issue the command: /opt/IBMdb2/V7.1/instance/db2iupdt iname where iname is the instance name. Note that you need to be logged in as user root to update the instances. 2.5.2 Updating instances to use 64-bit Once the instance has been updated to the current fix level with the above command, you may update individual instances to use 64-bit DB2. For each instance that you want to migrate to 64-bit, issue the command: /opt/IBMdb2/V7.1/instance/db2iupdt -w 64 iname where iname is the instance name. Once the instance has been migrated to 64-bit, it can not be migrated back to 32-bit. Only migrations from 32- to 64-bit require the "-w 64" flag. Applying further fixes to an existing 64-bit instance will not need the "-w 64" flag. 2.5.3 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.3.1 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. Examine the DB2PATH environment variable to determine the correct path. DB2UBIND.LST and DB2CLI.LST contain lists of commonly required bind files used for DB2. 2.5.3.2 Rebinding to DRDA databases If you are using DDCS 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 Chapter 4 "Binding Applications and Utilities" in the DDCS User's Guide for a list of the 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. 2.5.3.3 Rebinding Specific Packages If you wish to bind only the specific .bnd files to the database, issue the following command for each database (where is the name of the bind file, and is the name of your 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 3. 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, use the Product and Service Technical Library on the World Wide Web at: http://www.ibm.com/software/data/db2/udb/winos2unix/support 3.2 Customer Support To speak to an IBM representative regarding assistance with this product, please call 1-800-237-5511. Customer support is also provided via Electronic Question and Answer (Q&A) forums. These forums are accessible through CompuServe, IBMLink, and Usenet Newsgroup. (1) CompuServe - To access the forums on CompuServe, execute GO IBMDB2. - 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 - 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 - To access the forums on IBMLink, go to the OS2BBS section. - If you don't have access IBMLink, call 1-800-547-1283 for membership information in Canada or the US. 3.3 Corrective Service Corrective service can be downloaded electronically from by either: (1) FTP to anonymous server ftp.software.ibm.com. Go to ps/products/db2/fixes/%L/%P/ where %L is the appropriate locale (e.g. english-us, spanish, german, etc.), and %P is the product name/version (eg. db2sunv71, etc.). (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, please call 1-800-992-4777 to request these FixPaks be sent to you in the mail. For countries other than US and Canada, please contact your local DB2 Customer Service number for assistance in obtaining them. ------------------------------------------------------------------------------- * are trademarks or registered trademarks of IBM Corporation. ** are trademarks or registered trademarks of their respective owners. ------------------------------------------------------------------------------- ******************************************************************************* ** ** (c) COPYRIGHT INTERNATIONAL BUSINESS MACHINES CORPORATION 2000. ** ALL RIGHTS RESERVED. ** *******************************************************************************