IBM DB2 Universal Database* for LINUX Version V7.1 PTF No: U474814 VRMF: 07.01.0000.0028 +-- Note: ----------------------------------------------------------------+ | | To read this file more easily, set your font to monospace. | | If you have received interim fixes from IBM support after 02/16/2001, | then you must contact IBM support instead of installing this FixPak, to | request an updated version of the interim fixes. By doing this, you are | assured that your system is in a consistent state and no interim fixes | are lost. | | +-------------------------------------------------------------------------+ This README file contains information for the following products and components: LINUX Specific ------------ DB2 Connect Personal Edition, V7.1 DB2 Connect Enterprise Edition, V7.1 DB2 Universal Database Personal Edition, V7.1 DB2 Universal Database Workgroup Edition, V7.1 DB2 Universal Database Enterprise Edition, V7.1 DB2 Universal Database Enterprise - Extended Edition, V7.1 DB2 Application Development Client, V7.1 DB2 Administration Client, V7.1 DB2 Runtime Client, V7.1 --------------------------------------------------------------------------- 1. Contents of FixPak 2. Installation Notes 2.1 Pre-requisites 2.1.1 Prerequisities for APAR IX73249 2.2 Prior to Installation 2.3 Installation Instructions 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.4 Loss of Control Center Functionality 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/IBMdb2/V7.1/Readme/%L/Release.Notes where %L is the locale name. =========================================================================== 2. Installation Notes 2.1 Pre-requisites You must have Korn Shell installed before installing DB2 on Linux You should have the DB2 UDB V7.1 already installed before installing this Fixpak. To determine if the the required pre-requistes are installed, issue the following command: rpm -qa | grep db2 The output of the command should include the following: "db2cliv71-7.1.0-x" where "x" is the fix level 2.1.1 Prerequisites for APAR IX73249 Prerequisites for APAR IX73249 Incorrect Output for DB2 LIST DCS APPLICATIONS SHOW DETAIL The DB2 for MVS APAR PQ11645 must be applied in conjunction with DB2 Connect APAR IX73249 in order to provide the meaningful correlation token display on both the LIST DCS APPLICATIONS and the DB2 MVS DSP THD commands. 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 exit where ioname is the instance owner name. Then, while still logged on as root, do the following: su - dasname . $HOME/sqllib/db2profile db2admin stop exit where dasname is the admin server name. 2.3 Installation Instructions To install the fixpak, su - root cd ./installpatch 2.4 After Installation 2.4.1 Update Instances For each instance, issue the command: Note that you need to be logged in as user root to update the instance /usr/IBMdb2/V7.1/instance/db2iupdt ioname where ioname 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/IBMdb2/V7.1/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" of the DB2 Connect User's Guide for a list of what bind files are used for your specific client operating system. If a bind file changes but 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.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. 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: 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-992-4777. 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 the Internet by either: (1) FTP to anonymous server ftp.software.ibm.com (previously known as ps.boulder.ibm.com) at 198.17.57.66. 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. db22v71, db2aixv71, etc.). or: (2) Use a World Wide Web (WWW) browser to connect to the DB2 Service and Support Page at: http://www-4.ibm.com/cqi-bin/db2www/data/db2/udb/winos2unix/support/index.d2w/report (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. ** ***************************************************************************