IBM DB2 Universal Database* for AIX* Version V7.1 PTF No: U472894 VRMF: 07.01.0000.0002 +-- Note: ----------------------------------------------------------------+ | | To read this file more easily, set your font to monospace. | | If you have received interim fixes from IBM support after 08/10/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 a consistent state and no interim fixes | are lost. | +-------------------------------------------------------------------------+ This README file (located in Readme) contains information for the following products and components: AIX 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 Administration Client, V7.1 DB2 Run-Time Client, V7.1 DB2 Datalinks Manager, V7.1 DB2 Warehouse Manager, V7.1 DB2 OLAP Starter Kit, V7.1 DB2 Query Patroller, V7.1 DB2 Relational Connect, V7.1 --------------------------------------------------------------------------- 1. Contents of FixPak 2. Installation Notes 2.1 Pre-requisites 2.2 Prior to Installation 2.3 Installation Instructions 2.3.1 Applying Fixpak for Data Links Manager on UNIX 2.4 After Installation 2.4.1 Update Instances 2.4.2 Rebinding bind files 2.4.2.1 Rebinding to non-DRDA DB2 databases 2.4.2.2 Rebinding to DRDA databases 2.4.2.3 Rebinding Specific Packages 2.4.2.4 Binding Database Utilities Using the Run-Time Client 2.4.3 DB2 OLAP Starter Kit for Universal Database 7.1 Fixpak 1 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: /usr/lpp/db2_07_01/Readme/%L/Release.Notes where %L is the locale name. =========================================================================== 2. Installation Notes 2.1 Pre-requisites You should have the DB2 UDB V7.1 already installed before installing this Fixpak. To determine if the required pre-requisites are installed, issue the following command: lslpp -al "db2_07_01*" The output of the command should include the following: db2_07_01.client 7.1.0.x where x must be less than the product fix level. You can find the product fix level from the VRMF, for example if VRMF is 07.01.0000.0012, then x must be less than 12 (x<12) in order to apply the Fixpak. 2.2 Prior to Installation Logon as root and do the following for each instance: su - ioname . $HOME/sqllib/db2profile db2 force applications all db2 terminate db2stop db2licd end (run at each physical node) exit where ioname is the instance owner name. Then, while still logged on as root, do the following: su - aname . $HOME/sqllib/db2profile db2admin stop exit /usr/sbin/slibclean where aname is the admin server name. 2.3 Installation Instructions Install the selected updates using either SMIT or installp. To list the installable options in this FixPak, use: installp -ld where is the name of the device where the updated image resides. To install DB2 UDB for AIX with all the prerequisites in apply state, select the following menu options in SMIT: smit update_all For more information about the installp command or SMIT, refer to the online documentation by issuing `man installp` or `man smit`. 2.3.1 Applying Fixpak for Data Links Manager on UNIX 1) As the DB2 Data Links Manager Administrator, bring down the DB2 Data Links Manager by running the following commands: dlfm stop dlfm stopdbm Ensure that there are no DB2 or DLFM processes remaining. 2) As root, unmount each of the dlfs filesystem(i.e. the filesystem which is controlled by the DB2 Data Links Manager) by running the following command: umount /filesystem_name where /filesystem_name is the name of the dlfs filesystem which you want to unmount. 3) As root, unload the DLFS device driver by running the following command: strload -uf /usr/lpp/db2_07_01/cfg/dlfs_cfg 4) Install the Fixpak. 5) After successful installation of the Fixpak, as root, update the Data Links Manager instance by running the following command: /usr/lpp/db2_07_01/instance/dlfmupdt dlm_instance_name where dlm_instance_name is the name of the DB2 Data Links Manager Administrator. 6) As root, load the DLFS device driver by running the following command: strload -f /usr/lpp/db2_07_01/cfg/dlfs_cfg 7) As root, mount each of the DLFS filesystems by running the following command: mount -v dlfs /filesystem_name 8) As the DB2 Data Links Manager Administrator, run the following commands to bring up the DB2 Data Links Manager: dlfm bind dlfm start 9) Check the db2diag.log to ensure that the Data Links Manager is started properly. 2.4 After Installation 2.4.1 Update Instances Note that you need to be logged in as user root to update the instances. For each instance, issue the command: /usr/lpp/db2_07_01/instance/db2iupdt iname where iname is the instance name. For DAS instance, issue the command: /usr/lpp/db2_07_01/instance/dasiupdt dasname where dasname is the das instance name. 2.4.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.4.2.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.4.2.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 "Binding Applications and Utilities" in the DDCS 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. 2.4.2.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 2.4.2.4 Binding Database Utilities Using the Run-Time Client The Run-Time client cannot be used to bind the database utilities (import, export, reorg, the Command Line Processor) and DB2 CLI bind files to each database before they can be used with that database. You must use the DB2 Administration Client or the DB2 Application Development Client instead. You must bind the database utilities (import, export, reorg, the Command Line Processor) and DB2 CLI bind files to each database before they can be used with that database. In a network environment, if you are using multiple clients that run on different operating systems or are at different versions or service levels of DB2, you must bind the utilities once for each operating system and DB2-version combination. 2.4.3 DB2 OLAP Starter Kit for Universal Database 7.1 Fixpak 1 The DB2 OLAP Starter Kit license does not update automatically when you install Fixpak 1 for Universal Database. In order to update the license for OLAP Starter Kit, follow these instructions: 1). Install Fixpak 1. 2). After the Fixpak is installed ensure that any OLAP services or processes are NOT started. 2a). For UNIX UNIX processes do not start automatically. Do not start the processes manually until after you execute the license program in Step (3). Refer to Chapter 4 of the OLAP Setup and User's Guide for information about starting and stopping OLAP Starter Kit on UNIX platforms. 2b). For Windows Windows services start automatically. You must stop any OLAP services that have started automatically using the directions in Chapter 3 of the OLAP Setup and User's Guide. 3). Issue the following command: \bin\db2licm.exe -o 4). Start OLAP services or processes. 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, please go to the following web site: 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: 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, 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. db2aixv71, 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. 3.4 DB2 OLAP Starter Kit for Universal Database 7.1 Fixpak 1 The DB2 OLAP Starter Kit license does not update automatically when you install Fixpak 1 for Universal Database. In order to update the license for OLAP Starter Kit, follow these instructions: 1). Install Fixpak 1. 2). After the Fixpak is installed ensure that any OLAP services or processes are NOT started. 2a). For UNIX UNIX processes do not start automatically. Do not start the processes manually until after you execute the license program in Step (3). Refer to Chapter 4 of the OLAP Setup and User's Guide for information about starting and stopping OLAP Starter Kit on UNIX platforms. 2b). For Windows Windows services start automatically. You must stop any OLAP services that have started automatically using the directions in Chapter 3 of the OLAP Setup and User's Guide. 3). Issue the following command: \bin\db2licm.exe -o 4). Start OLAP services or processes. --------------------------------------------------------------------------- * 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. ** ***************************************************************************