IBM DB2 Universal Database* for HP-UX** (64-bits) Version 7.1 PTF: U474026 VRMF: 07.01.0001.0020 +-- Note: --------------------------------------------------------------------+ | | To read this file more easily, set your font to monospace. | | If you have received interim fixes from IBM support after 12/22/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. | | Note: The following problem will be encountered unless you have downloaded this FixPak from the | web. | | Due to very long names of "tivready" files, | to mount the CD_ROM you have to run the following commands. Otherwise, files | with long names can not be read. | | "TO MOUNT" (go to /usr/sbin/ and run this command) | | pfs_mountd & | pfsd 4 & | pfs_mount -t rrip /dev/dsk/ /SD_CDROM | | where is the mounting point (eg. /dev/dsk/c2t2d0) | | "TO UNMOUNT" | | pfs_umount /SD_CDROM | ps -fe | grep pfs* | kill -9 | | (check to see if any pfs* processes are running. is the pfs* process ID | number. If you didn't terminate all the ptf* processes, the CD_ROM will | not be released) +-----------------------------------------------------------------------------+ This README file contains information for the following products and components: HP-UX Specific ---------------- DB2 Administration Client, V7.1 DB2 Application Development Client, V7.1 DB2 Connect Enterprise Edition, V7.1 DB2 Query Patroller Client, V7.1 DB2 Query Patroller Server, V7.1 DB2 Run-Time Client, V7.1 DB2 UDB Workgroup Edition, V7.1 DB2 UDB Enterprise Edition, V7.1 DB2 UDB Enterprise - Extended Edition, 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 HP-UX 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 Enabling the New SQL Built-in Scalar Functions 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 3. Service 3.1 Product and Service Technical Library 3.2 Customer Support 3.3 Corrective Service 3.4 DB2 OLAP Starter Kit for Universal Database 7.1 Fixpak 1 3.5 Loss of Control Center Functionality For additional information on changes to the product, please review the product Release Notes: /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 above products to already be installed on the machine: at the level: 07.01.0000.X To determine if the required pre-requisites are installed, issue the following command: swlist -l product "DB2*" The output of the command should include the following: DB2V7CAE 7.1.0.x where x must be less than the product fix level. You can find the product fix level from the VRMF specified at the top of this readme, for example if VRMF is 07.01.0000.0020, then x must be less than 20 (x < 20) in order to apply the Fixpak. 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 owner name. Then, while still logged on as root, do the following: su - aname . $HOME/sqllib/db2profile db2admin stop exit where aname is the admin server name. 2.3 Installation Instructions run (as root) cd ./installpatch 2.4 Migration to 64-bit HP-UX To start using 64-bit DB2 on HP-UX, you must download and install the 64-bit HP-UX 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 HP-UX with all the prerequisites in apply state, run the `installpatch` 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. 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. 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 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.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 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.4.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: 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. db2hp64v71, 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. 3.5 Loss of Control Center Functionality There should be no problems introduced against downlevel Control Center clients by applying this fixpak to a DB2 server. However, the next refresh of DB2, version 7.2, will break downlevel Control Center clients - the CC 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 be upgraded to fixpak 2 or later. ------------------------------------------------------------------------------- * 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. ** *******************************************************************************