IBM DB2 Universal Database* for AIX* (64-bit) Version V7.1 ------------------------------------------------------------------------ Contents Overview of FixPak for IBM DB2 Universal Database* for AIX* (64-bit) Version V7.1 AIX (64-bit) Installation Notes * 2.1 Prerequisites * 2.2 Prior to Installation * 2.3 Installation Instructions * 2.4 Migration to 64-bit AIX * 2.5 After Installation o 2.5.1 Update Instances to use the New Fix Level o 2.5.2 Updating Instances to use 64-bit o 2.5.3 Enabling the New SQL Built-in Scalar Functions o 2.5.4 Rebinding Bind Files + 2.5.4.1 Rebinding to Non-DRDA DB2 Databases + 2.5.4.2 Rebinding to DRDA Databases + 2.5.4.3 Rebinding Specific Packages + 2.5.4.4 Binding Database Utilities Using the Run-Time Client * 2.6 Special Notes o 2.6.1 Loss of Control Center Functionality o 2.6.2 Using DB2 XML Extender 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* for AIX* (64-bit) Version V7.1 IBM DB2 Universal Database* for AIX* (64-bit) Version V7.1 PTF No: U475376 VRMF: 7.1.1.41 Note: To read this file more easily, set your font to monospace. If you have received interim fixes from IBM support after 05/04/2001, then 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 FixPak will upgrade your system to Version 7.2 on all platforms. This README file contains information for the following products and components: * DB2 Application Development Client, V7.1 * DB2 Connect Enterprise Edition, V7.1 * DB2 Run-Time Client, V7.1 * DB2 UDB Enterprise Edition, V7.1 * DB2 UDB Enterprise-Extended Edition, V7.1 For additional information on changes to the product, review the product Release Notes: /usr/lpp/db2_07_01/Readme/%L/Release.Notes where %L is the locale name. ------------------------------------------------------------------------ AIX (64-bit) Installation Notes ------------------------------------------------------------------------ 2.1 Prerequisites You should have DB2 UDB V7.1 and a previous V7.1 FixPak already installed before installing this FixPak. See section 2.4 "Migration to 64-bit AIX" below for details. To determine if the required prerequisites 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.1.x In order to run DB2 in 64 bit mode on AIX, the following two filesets must both be at level 4.3.3.50 or higher: bos.rte.libc bos.adt.prof If you do not have the required levels, you need to install the following PTFs: * For bos.rte.libc, the PTF is U473728.bff * For bos.adt.prof, the PTF is U473581.bff The PTFs can be downloaded from the IBM Web site: http://www-1.ibm.com/servers/aix/download/index.html ------------------------------------------------------------------------ 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. There are two steps to installing this FixPak. The first step is to install the .bff files. The second step is to install the filesets in the extras subdirectory. The extras subdirectory is located in the same directory as the .bff files. 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 the .bff files, with all the prerequisites in apply state, select the following menu options in SMIT: smit update_all If you would like to be able to reject (uninstall) the FixPak afterwards, make sure to select the following options in SMIT: COMMIT software updates = NO SAVE replaced files = YES You can later commit or reject the FixPak using SMIT again. This FixPak has an additional subdirectory in the installation image. The name of this subdirectory is "extras". This "extras" subdirectory contains the filesets for the double-byte and unicode conversion tables, specifically, the following filesets: db2_07_01.cnvucs db2_07_01.conv.jp db2_07_01.conv.kr db2_07_01.conv.sch db2_07_01.conv.tch To install the filesets in the extras subdirectory, select the following menu options in SMIT: smit install_all Note: Installing the "extras" subdirectory will automatically commit the above filesets. You will not be able to reject the FixPak if you install the "extras" subdirectory. Since future FixPaks will require this FixPak to be already installed, they will no longer include the "extras" subdirectory. This means that you must have these filesets installed before going on to future FixPaks. For more information about the installp command or SMIT, refer to the online documentation by issuing `man installp` or `man smit`. ------------------------------------------------------------------------ 2.4 Migration to 64-bit AIX To start using 64-bit DB2 on AIX, you must download and install the DB2 V7.1 64-bit for AIX FixPak 1. This FixPak includes all 32-bit fixes as well as adding 64-bit DB2 functionality to your system. The VRMF for FixPak 1 is 7.1.1.0. Once you have installed this FixPak, you cannot install 32-bit FixPaks, and must get any new fixes through the 64-bit FixPaks. You can download the DB2 V7.1 64-bit for AIX FixPak 1 from the same location as this FixPak. The PTF is U472895. As an example, if you want to move from a 32-bit image to a 64-bit FixPak x image, where x > 1 then you must first apply the 64-bit FixPak 1 (this will bring your DB2 system to 64-bit) then apply the 64-bit FixPak x. ie. All subsequent 64-bit FixPaks can be applied directly once 64-bit FixPak 1 has been applied. To install DB2 UDB 64-bit FixPak for AIX with all the prerequisites in apply state, select the following menu options in SMIT: smit update_all If you would like to be able to reject the FixPak afterwards, make sure to select the following options in SMIT: COMMIT software updates = NO SAVE replaced files = YES You can later commit or reject the FixPak using SMIT again. For more information about the installp command or SMIT, refer to the online documentation by issuing `man installp` or `man smit`. Note: If you have already applied 32-bit FixPaks and you decide to move to 64-bit, it is highly recommended that you move to 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 Update Instances to use the New Fix Level Note: You need to be logged on 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. Note: If you are running both Enterprise - Extended Edition (EEE) and Enterprise Edition (EE) on the same machine, then you need to run db2iupdt with the "-k" option. Otherwise, it will check to see if EEE filesets exist; if they do, it will perform the update as if it was an EEE instance. For more information on the db2iupdt command, run db2iupdt with the "-h" option. 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: /usr/lpp/db2_07_01/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 Enabling the New SQL Built-in Scalar Functions FixPak 2 and later of Version 7.1 delivers new SQL built-in scalar functions. Refer to the SQL Reference 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.4 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.4.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. DB2UBIND.LST and DB2CLI.LST contain lists of commonly required bind files used for DB2. 2.5.4.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 /@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 DB2 Connect 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.5.4.3 Rebinding Specific Packages If you want to bind only the specific .bnd files to the database, issue the following commands for each 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 where is the name of the bind file, and is the name of your database. 2.5.4.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.6 Special Notes 2.6.1 Loss of Control Center Functionality There should be no problems introduced against downlevel Control Center clients by applying FixPak 2 to a DB2 server. However, with this FixPak and 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.6.2 Using DB2 XML Extender The README.TXT file for DB2 XML Extender Version 7.1 incorrectly states the following under "Considerations": * The default version of DB2 UDB is DB2 UDB Version 7.1. If you wish to use DB2 UDB Version 6.1 on AIX and Solaris, you should ensure that you are running with DB2 UDB V6.1 instances and with the DB2 UDB V6.1 libraries. This is incorrect. The DB2 XML Extender is supported only with DB2 Version 7.1 and 7.2. The readme.aix file incorrectly lists Software Requirements of DB2 UDB 6.1 with FP1_U465423 or higher. This is incorrect. The DB2 XML Extender requires DB2 Version 7.1 or 7.2. ------------------------------------------------------------------------ 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 (e.g. english-us, spanish, german etc.), and %P is the product name/version (eg. db2ntv71, 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, 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. ** *******************************************************************************