IBM DB2 Universal Database* Version 6.1 for Windows 95/98** and NT** PTF No: WR21178s +-- Note: ----------------------------------------------------------------+ | | To read this file more easily, set your font to monospace. | | This is the officially approved DB2 fixpack for "Siebel 2000.0.1.x". | | If you have received interim fixes from IBM support after 04/03/00, 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. | | Throughout this document X: is used to refer to the cdrom drive into | which the FixPak CD is placed and C:\SQLLIB is where the DB2 products | are installed. | +-------------------------------------------------------------------------+ This README file contains information for the following products and components: NT/95 Specific -------------- DB2 Connect Personal Edition, V6.1 DB2 Connect Enterprise Edition, V6.1 DB2 Universal Database Enterprise Edition, V6.1 DB2 Universal Database Workgroup Edition, V6.1 DB2 Universal Database Personal Edition, V6.1 DB2 Universal Database Extended Enterprise Edition, V6.1 DB2 Universal Database Satellite Edition, V6.1 DB2 Software Developer's Kit, V6.1 DB2 Datalinks Manager, V6.1 DB2 Administration Client, V6.1 DB2 Run-Time Client, V6.1 DB2 Query Patroller, V6.1 --------------------------------------------------------------------------- 1. Contents of FixPak 2. Installation Notes 2.1 Pre-requisites 2.1.1 Prerequisites for APAR IX73249 2.2 Prior to Installation 2.3 Installation Instructions 2.3.1 Applying Fixpak for Data Links Manager 2.4 Unattended Install Instructions 2.5 After Installation 2.5.1 Rebinding to non-DRDA DB2 databases 2.5.2 Rebinding to DRDA databases 2.5.3 Rebinding Specific Packages 2.5.4 DataJoiner Replication Administration Tool 2.5.5 Rerun db2classes.exe on the web server 2.6 Uninstallation Notes 2.7 Satellite Information 2.7.1 Changes to the Generalize Function for V6.1 FixPak 2 2.7.2 Execution of the Update Batch Step Containing the asnsat Command 2.8 Correction of CREATE TABLE statement 3. Miscellaneous 3.1 Product and Service Technical Library 3.2 Customer Support 3.3 Corrective Service 3.4 Binding Database Utilities Using the Run-Time Client For additional information please see the following files: C:\SQLLIB\RELEASE.TXT X:\APARLIST.TXT =========================================================================== 2. Installation Notes 2.1 Pre-requisites This Fixpak requires that at least one Version 6.1 DB2 UDB for NT/95 product be already installed on your system. To determine the version and level of the currently installed DB2 product, type regedit from an MS-DOS prompt and check the following values under the registry key HKEY_LOCAL_MACHINE\SOFTWARE\IBM\DB2\\CurrentVersion. The values should be the following: Version "6" Release "1" Modification "0" Service Level "" 2.1.1 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 It is recommended you stop all database activity before applying this FixPak. To do this, please stop all applications and issue the commands: db2stop db2admin stop 2.3 Installation Instructions To start the FixPak, run X:\SETUP.EXE. NOTE: Once you installed a fixpak, you cannot uninstall it. 2.3.1 Applying Fixpak for Data Links Manager 1. As the DB2 Data Links Manager Administrator(dlmadmin) bring down the DB2 Data Links Manager by stopping the DB2 Data Links Manager service: Start->Settings->Control Panel->services Stop DB2 Data Links Manager Ensure that there are no other DB2 processes remaining, by issuing a db2stop for each instance. 2. Install the Fixpak 3. As the DB2 Data Links Manager Administrator, run the following commands to bring up the DB2 Data Links Manager: dlfm bind dlfm start Check the db2diag.log to ensure that the Data Links Manager is started properly. 2.4 Unattended Install Instructions The version of SETUP.EXE shipped with this FixPak is capable of running via an "unattended install" option. The syntax for this feature is documented in the Quick Beginnings book. A sample response file (DB2FIXPK.RSP) is included in this FixPak: 2.5 After Installation Due to the new bind (.bnd) files that have been shipped with this FixPak, you will need to rebind your 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.1 Rebinding to non-DRDA DB2 databases After applying fixes, you must do the following: db2 terminate db2 CONNECT TO db2 BIND C:\SQLLIB\BND\@db2ubind.lst GRANT PUBLIC db2 BIND C:\SQLLIB\BND\@db2cli.lst GRANT PUBLIC db2 terminate Where is the name of a database to which the utilities should be bound. 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. If is a DB2 v1.x database, do not bind db2cli.lst. Instead, use the db2cliv1.lst or specifically bind db2clics.bnd, db2cliur.bnd, db2clirr.bnd, and db2cliv1.bnd individually. 2.5.2 Rebinding to DRDA databases If you are using DB2 Connect to access host databases, you will also need to bind the new bind files. As above, connect to the host database, and then bind the utilities as follows: HOST COMMAND ===== =================================================================== MVS BIND C:\SQLLIB\BND\@ddcsmvs.lst BLOCKING ALL SQLERROR CONTINUE GRANT PUBLIC VM BIND C:\SQLLIB\BND\@ddcsvm.lst BLOCKING ALL SQLERROR CONTINUE GRANT PUBLIC VSE BIND C:\SQLLIB\BND\@ddcsvse.lst BLOCKING ALL SQLERROR CONTINUE GRANT PUBLIC OS400 BIND C:\SQLLIB\BND\@ddcs400.lst BLOCKING ALL SQLERROR CONTINUE GRANT PUBLIC 2.5.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). db2 terminate db2 CONNECT TO db2 BIND C:\SQLLIB\BND\ BLOCKING ALL GRANT PUBLIC db2 terminate 2.5.4 DataJoiner Replication Administration Tool The location of the DataJoiner Replication Administration (DJRA) tool (djra.exe) is now installed in the directory SQLLIB\DJRA. 2.5.5 Rerun db2classes.exe on the web server If the Control Center was served as an applet using the V6.1 GA of DB2 UDB on Win32 platforms, after installing the fixpak you must re-run db2classes.exe on the web server. 2.6 Uninstallation Notes When upgrading or uninstalling the DB2 product(s) on a Windows NT system, it is recommended that you manually shut down all DB2 services and processes on your machine. 2.7 Satellite Information The sections that follow provide information that applies to the satellite environment. 2.7.1 Changes to the Generalize Function for V6.1 FixPak 2 For FixPak 2, a number of enhancements have been made to the generalize function. 2.7.1.1 Automatic Cataloging of the Replication Target, Control, and Source Servers When you generalize a replication subscription, the Satellite Administration Center requires that connections be made to the replication control, source, and target servers when it generalizes the replication subscriptions for an application version. In addition, when a satellite replicates data, it needs to connect to the replication control and source servers. At the FixPak 1 level, you had to catalog the replication control, source, and target servers at the DB2 control server instance (that is, the instance where the SATCTLDB resides). You also had to catalog the replication control and source servers at the satellite. For FixPak 2, the generalize function will attempt to catalog the replication control, source, and target servers at the DB2 control server instance. The generalize function will also create a batch step that catalogs the replication control and source servers on the satellite. The satellite will execute this batch step when it synchronizes. TCP/IP is the only supported communications protocol between the satellite and its replication control and source servers. If a replication control or source server does not support TCP/IP communications, the generalize function does not return an error when it attempts to create the cataloging batch step. If a replication control or source server is not enabled for TCP/IP communications, and you generalize the replication subscription, the generalize action will not fail, but, if you examine the batch step that sets up the cataloging, you will notice that the batch step does not contain all the catalog statements that are required for the satellite to replicate data when it synchronizes. If a replication control or source server does not support TCP/IP communications, you must delete the replication subscriptions that you generalized for the application version. Then enable the replication server for TCP/IP communications. Finally, generalize the replication subscription again for the application version. If any of the replication control, source, or target servers are instances that are remote to the Control Center, they are likely already set up for TCP/IP communications. If, however, any of these instances are local to the machine where Control Center is running, and in a different instance than that from which the Control Center is run (likely DB2), the TCP/IP protocol may not be configured for the other instance. If TCP/IP is not set up, you will receive the following error: [IBM][CLI Driver][DB2/NT] SQL0902C A system error (reason code = "-20475") occurred. Subsequent SQL statements cannot be processed. SQLSTATE=58005 You can use the Control Center to set up the instance for TCP/IP communications as follows. For this example, the name of the instance that is the replication server is assumed to be REPLINST. 1. Right click on the REPLINST instance in the object tree, and select Communications from the pop-up menu. 2. On the Setup Communications window, click on the Properties button for TCP/IP. 3. On the Configure TCP/IP window, click Default, then click OK. You will receive a message confirming that the TCP/IP configuration is complete. Close the message window. 4. On the Setup Communications window, click OK. 5. Right click on the REPLINST instance, and select Stop from the pop-up menu. 6. Right click on the REPLINST instance, and select Start from the pop-up menu. The restart of the instance activates the TCP/IP listeners. The REPLINST instance is now configured for TCP/IP communications. 2.7.1.2 Reverse Engineering of the Model Replication Target for the Satellite At the FixPak 1 level, you had to set up the replication target, and any associated database objects on the satellite. For FixPak 2, the generalize function reverse engineers the model replication target and its associated database objects. That is, the generalize function will generate the CREATE DATABASE command, and any DDL statements (for example, CREATE TABLESPACE, CREATE TABLE (and so on)) that are required to set up the replication target on the satellite. Note that the generalize function can only reverse engineer the model replication target if the target is a database that is a DB2 Universal Database database that runs on a workstation. If the satellite participates in an update anywhere replication scenario, you must retain the logs so that the Capture program has access to the changes that occur to the target on the satellite. For more information, see "Retaining Logs for Update Anywhere Replication." 2.7.1.3 Toleration of Pre-Existing Replication Targets If you generalize the replication subscription using the FixPak 2 generalize function, and the replication target already exists on the satellite, the generalize function will still reverse engineer the model replication target. The existing target on the satellite, however, will be tolerated. 2.7.1.4 Retaining Logs for Update Anywhere Replication If your satellites participate in an update anywhere replication scenario, you must configure the satellite to retain the logs. The Capture program uses the logs to replicate data that is on the satellite. Two options are available for you to retain the logs: - If you require that the satellite database be enabled for forward recovery, you must set the LOGRETAIN database configuration parameter to either ON or RECOVERY. After changing the database configuration, you must take a backup of the database. - If you do not require forward recovery for the satellite database, set LOGRETAIN to CAPTURE. You cannot have LOGRETAIN set to the default value of OFF because the Capture program cannot capture changes that are made to replica tables in the satellite database. You can use the Satellite Administration Center to make the change to the database configuration on the satellite. You can add an operating system script to the test level that is created (or modified) by the generalize function. The script should contain one or both of the following commands (if LOGRETAIN=RECOVERY, the script must contain both commands): DB2 UPDATE DB CFG FOR USING LOGRETAIN DB2 BACKUP DB Ensure that the name of the script has an extension of .bat (all satellite platforms) or .cmd (for Windows NT satellite platforms only). Add this command (or commands) to the setup batch after the operating system script that contains the DB2 CREATE DATABASE command. For more information about the LOGRETAIN configuration parameter, refer to the Administration Guide. 2.7.2 Execution of the Update Batch Step Containing the asnsat Command On Windows 95 and Windows 98, the execution of an operating system script in a batch step is performed by the command interpreter, command.com. The command interpreter, however, always issues a return code of 0 (zero) when it completes, regardless of whether the scripts in the batch step completed with a return code of 0. When you generalize the replication subscription, the generalization procedure puts the asnsat command (which initiates data replication on the satellite) into an operating system script within a batch step of the update batch. Because the command interpreter always returns 0 when it executes an operating system script, the batch step that contains the asnsat command is executed directly (that is, the command interpreter is bypassed). Because the command interpreter is bypassed, the correct asnsat return code can be written to the satellite's synchronization logs. (The asnsat return code is written as an external code.) The command interpreter is only bypassed if the asnsat command is the only command in the operating system script. If the script that contains the asnsat command is modified to include additional commands, the command interpreter is not bypassed. 2.8 Correction of CREATE TABLE statement In the CREATE TABLE IN tablespace1 statement, the algorithm for determining the tablespace chosen should read as follows: IF table space in the IBMDEFAULTGROUP nodegroup over which the user has USE privilege exists with sufficient page size THEN use it ELSE IF a table space over which the user has USE privilege exists with sufficient page size THEN use it ELSE issue an error (SQLSTATE 42727). 3. Miscellaneous 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: http://www.software.ibm.com/data/db2/library 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 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. db22v5, db2aixv5, etc.). (2) Use a World Wide Web (WWW) browser to connect to the DB2 Service and Support Page at: http://www.software.ibm.com/data/db2/db2tech/index.html (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 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. --------------------------------------------------------------------------- * 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. ** ***************************************************************************