IBM DB2 Universal Database* for AIX* Version V7.1 PTF No: U475365 VRMF: 07.01.0000.0035 +-- Note: ----------------------------------------------------------------+ | | To read this file more easily, set your font to monospace. | | If you have received interim fixes from IBM support after 03/26/2001, | 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. | | Note: This client fixpak includes all the fixes in Fixpak 2a plus | additional CLI fixes. | +-------------------------------------------------------------------------+ This README file (located in Readme) contains information for the following products and components: AIX Specific ------------ DB2 Administration Client, V7.1 DB2 Application Development Client, V7.1 DB2 Connect Enterprise Edition, V7.1 DB2 Data Links Manager, V7.1 DB2 Data Warehouse Agent, V7.1 DB2 OLAP Starter Kit, V7.1 DB2 Query Patroller Client, V7.1 DB2 Query Patroller Agent, V7.1 DB2 Query Patroller Server, V7.1 DB2 Relational Connect, V7.1 DB2 Run-Time Client, V7.1 DB2 Spatial Extenders Client, V7.1 DB2 Spatial Extenders Server, V7.1 DB2 UDB Workgroup Edition, V7.1 DB2 UDB Enterprise Edition, V7.1 DB2 UDB Enterprise - Extended Edition, V7.1 DB2 Warehouse Manager, 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 Enabling the New SQL Built-in Scalar Functions 2.4.3 Rebinding bind files 2.4.3.1 Rebinding to non-DRDA DB2 databases 2.4.3.2 Rebinding to DRDA databases 2.4.3.3 Rebinding Specific Packages 2.4.3.4 Binding Database Utilities Using the Run-Time Client 2.4.4 Loss of Control Center Functionality 2.4.5 New ODBC Driver for the Data Warehouse Center 3. Service 3.1 Product and Service Technical Library 3.2 Customer Support 3.3 Corrective Service For additional information on changes to the product, please review the product Release Notes: /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 number at the top of this readme, 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. 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 (ie. 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. 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. 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 a EEE instance. Here is the syntax for db2iupdt: FUNCTION: db2iupdt - update a DB2 instance after installation/removal: - of a new DB2 release (of the same version) - of additional DB2 products (eg. updating a client to a server) - of a patch/PTF USAGE: db2iupdt [-h|-?] [-d] [-k] [-s] [-a AuthType] [-u FencedID] InstName -h|-? display the usage information. -d turn debug mode on. -k keep the current instance type during update. -s ignore existing SPM log directory AuthType is the authentication type (SERVER, CLIENT or DCS) for the instance. The default is SERVER. FencedID is the name of user ID under which fenced User Defined Functions and fenced Stored Procedures will run. InstName is the name of the instance. For DAS instance, issue the command: /usr/lpp/db2_07_01/instance/dasiupdt dasname where dasname is the das instance name. 2.4.2 Enabling the New SQL Built-in Scalar Functions FixPak 2 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 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. A full offline backup of the database should be performed prior to running db2updv7 in order to have the ability to restore to a previous FixPak level. 2.4.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.4.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. DB2UBIND.LST and DB2CLI.LST contain lists of commonly required bind files used for DB2. 2.4.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 "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.4.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 2.4.3.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.4 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.4.5 New ODBC Driver for the Data Warehouse Center If you will be using the Data Warehouse Center AIX or SUN agent that has been linked to access Merant ODBC sources and will be accessing DB2 databases as well, please change the value of the "Driver=" attribute in the DB2 source section of the .odbc.ini file as follows: ON AIX: The Driver name is /usr/lpp/db2_07_01/lib/db2_36.o On SUN: The Driver name is /opt/IBMdb2/V7.1/lib/libdb2_36.so Here is a sample odbc source entry for AIX: [SAMPLE] Driver=/usr/lpp/db2_07_01/lib/db2_36.o Description=DB2 ODBC Database Database=SAMPLE Here is another sample odbc source entry for SUN: [SAMPLE] Driver=/opt/IBMdb2/V7.1/lib/libdb2_36.so Description=DB2 ODBC Database Database=SAMPLE 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. --------------------------------------------------------------------------- * 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. ** ***************************************************************************