IBM DB2 Universal Database Version 6.1 til Windows 95 og Windows NT PTF No: WR21302 VRMF: 06.01.0000.0060 +-- Bem‘rk: --------------------------------------------------------------+ | | Det anbefales at v‘lge en font med ens skriftbredde, s† filen er lettere | at l‘se. | | Hvis du har modtaget midlertidige programrettelser fra IBM efter den | 01-04-2002, skal du kontakte IBM-forhandleren i stedet for at installere | denne fixpakke for at f† en opdateret udgave af de midlertidige | programrettelser. Dermed sikrer du, at dit system er fuldt opdateret, | og at ingen midlertidige rettelser g†r tabt. | | I dette dokument benyttes x: til at referere til det cd-drev, | hvor cd'en med rettelserne er placeret, og C:\SQLLIB refererer | til det drev og bibliotek, hvor DB2-programmerne er installeret. | | 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. | +-------------------------------------------------------------------------+ Denne README-fil indeholder oplysninger om f›lgende programmer og komponenter: Til NT/95 --------- DB2 Connect Personal Edition Version 6.1 DB2 Connect Enterprise Edition Version 6.1 DB2 Universal Database Enterprise Edition Version 6.1 DB2 Universal Database Workgroup Edition Version 6.1 DB2 Universal Database Personal Edition Version 6.1 DB2 Software Developer's Kit Version 6.1 DB2-administrationsklient Version 6.1 DB2-klient (Run-Time) Version 6.1 DB2 Satellite Edition, V6.1 DB2 Query Patroller, V6.1 --------------------------------------------------------------------------- 1. Fixpakkens indhold 2. Installationsnoter 2.1 Foruds‘tninger 2.1.1 Foruds‘tninger for APAR IX73249 2.2 F›r installationen 2.3 Installationsvejledning 2.4 Vejledning i uoverv†get installation 2.5 Efter installationen 2.5.1 Opret ny binding af ikke-DRDA DB2-databaser 2.5.2 Opret ny binding af DRDA-databaser 2.5.3 Opret ny binding af bestemte pakker 2.5.4 DataJoiner Replication-administrationsv‘rkt›j 2.6 Fjern installation 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 3. Diverse 3.1 Tekniske oplysninger p† WWW 3.2 Kundeservice 3.3 Programrettelser 3.4 MIN_DEC_DIV_3 Database Configuration Parameter Der er flere oplysninger i f›lgende filer: C:\SQLLIB\RELEASE.TXT X:\APARLIST.TXT =========================================================================== 2. Installationsnoter 2.1 Foruds‘tninger Fixpakken kr‘ver, at mindst ‚t DB2 UDB Version 6.1-program til NT/95 er installeret p† systemet. Du kan se versionsnummeret p† installerede DB2-programmer ved at udf›re kommandoen REGEDIT fra en MS DOS-kommandolinie og finde v‘rdierne for n›gleordet HKEY_LOCAL_MACHINE\SOFTWARE\IBM\DB2\\. Der skal v‘re f›lgende v‘rdier: Version "6" Release "1" Modification "0" Service Level "WR21163" 2.1.1 Foruds‘tninger for APAR IX73249 Forkert output fra DB2 LIST DCS APPLICATIONS SHOW DETAIL APAR PQ11645 til DB2 til MVS skal installeres sammen med APAR IX73249 til DB2 Connect, s† korrelationen mellem elementer i b†de kommandoerne LIST DCS APPLICATIONS og DB2 MVS DSP THD giver mening. 2.2 Inden installationen Al databaseaktivitet skal stoppes, f›r du installerer denne fixpakke. Stop alle applikationer, og afsend f›lgende kommandoer: db2stop db2admin stop 2.3 Installationsvejledning Start installationen af fixpakken ved at k›re X:\SETUP.EXE. 2.4 Vejledning i uoverv†get installation Den version af SETUP.EXE, der leveres med fixpakken, kan udf›res i uoverv†get tilstand. Funktionen er beskrevet i brugervejledningen. Der leveres en svarfil (DB2FIXPK.RSP) med fixpakken. 2.5 Efter installationen Da der er nye bindefiler (.bnd) i denne fixpakke, skal du binde DB2-funktionerne til alle databaser efter installationen af fixpakken. Dette trin er n›dvendigt for at aktivere rettelserne. Genbindingsproceduren, som beskrives nedenfor, skal kun udf›res ‚n gang for hver database. 2.5.1 Opret ny binding til ikke-DRDA DB2-databaser N†r programrettelserne er installeret, skal du udf›re f›lgende kommandoer: 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 Hvor er navnet p† en database, som funktionerne skal bindes til. Brug systemvariablen DB2PATH til at se den korrekte sti. DB2UBIND.LST og DB2CLI.LST indeholder en liste over de n›dvendige bindefiler til DB2. Hvis er en DB2 version 1.x-database, skal du ikke binde DB2CLI.LST. Du skal i stedet bruge DB2CLIV1.LST eller binde DB2CLICS.BND, DB2CLIUR.BND, DB2CLIRR.BND og DB2CLIV1.BND separat. 2.5.2 Opret ny binding til DRDA-databaser Hvis du bruger DB2 til at f† adgang til databaser p† et v‘rtssystem, skal du ogs† binde de nye bindefiler p† v‘rtssystemet. Opret forbindelse til v‘rtsdatabasen som ovenfor, og bind derefter funktionerne p† f›lgende m†de: V’RTSSYSTEM KOMMANDO =========== =================================================================== 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 Opret ny binding af bestemte pakker Hvis du kun vil binde enkelte BND-filer til databasen, skal du udf›re nedenst†ende kommandoer for hver database (hvor er navnet p† bindefilen, og er navnet p† databasen). db2 terminate db2 CONNECT TO db2 BIND C:\SQLLIB\BND\ BLOCKING ALL GRANT PUBLIC db2 terminate 2.5.4 DataJoiner Replication-administrationsv‘rkt›j Administrationsv‘rkt›jet til DataJoiner Replication (DJRA) er nu placeret i biblioteket SQLLIB\DJRA (filen djra.exe). 2.6 Fjern installation N†r du opgraderer eller fjerner installationen af et DB2-program p† et Windows NT-system, skal du manuelt lukke alle DB2-serviceprogrammer og -processer p† maskinen. Hvis filen psapi.dll findes p† systemet i et af bibliotekerne i systemvariablen PATH, skulle serviceprogrammer og processer blive lukket automatisk. Hvis psapi.dll ikke findes p† systemet, skal du manuelt lukke alle DB2-serviceprogrammer, f›r du kan opgradere eller fjerne et installeret program. 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. 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. Diverse 3.1 Tekniske oplysninger p† WWW I Product and Service Technical Library p† World Wide Web er der fuldst‘ndige og opdaterede oplysninger om DB2, herunder oplysninger, der er frigivet, efter at denne README-fil er udgivet. Adressen er: http://www.software.ibm.com/data/db2/library 3.2 Kundeservice Kontakt din IBM-forhandler, hvis du har brug for hj‘lp til programmet. Du kan s›ge svar p† sp›rgsm†l i forbindelse med DB2 via elektroniske sp›rgsm†l og svar-fora. Der er adgang til disse fora via CompuServe, IBMLink og Usenet-nyhedsgruppen. (1) CompuServe - GO IBMDB2 for at f† adgang til fora p† CompuServe. (2) Usenet-nyhedsgruppe: comp.databases.ibm-db2 - Denne nyhedsgruppe p† Internet er et generelt forum til sp›rgsm†l og/eller problemer i forbindelse med DB2-programmer. (3) (IBMLink) Talklink OS/2 BBS - Skift til afsnittet OS2BBS for at f† adgang til fora p† IBMLink. 3.3 Programrettelser Programrettelser kan overf›res elektronisk fra Internettet p† en af f›lgende m†der: (1) Benyt FTP som bruger anonymous til serveren ftp.software.ibm.com (tidligere kendt som ps.boulder.ibm.com) med IP-adressen 198.17.57.66. Skift til ps/products/db2/fixes/%L/%P/, hvor %L er det relevante sprog (locale), og %P er programnavn og -version, f.eks. db22v5, db2aixv5 osv. (2) Benyt en Web-browser til at oprette forbindelse til IBM's service- og support-side p† adressen: http://www.software.ibm.com/data/db2/db2tech/index.html (3) Udf›r GO IBMDB2 p† CompuServe. G† derefter til det relevante katalog, hvor fixpakken findes. (4) IBM PCC BBS (i USA): Ring (919) 517-0001 (i Raleigh, North Carolina), og skriv "DB2" p† hovedmenuen for at finde fixpakkerne. Brugere i USA, der ikke har adgang til nogen af ovenst†ende steder, kan ringe til 1-800-992C-4777 og bede om at f† tilsendt fixspakkerne pr. post. Brugere i andre lande end USA og Canada skal kontakte IBM-forhandleren for at f† disse rettelser. 3.4 MIN_DEC_DIV_3 Database Configuration Parameter The addition of the MIN_DEC_DIV_3 database configuration parameter is provided as a quick way to enable a change to computation of the scale for decimal division in SQL. It is possible that this may not continue as this exact same database configuration parameter in the future. Default=NO. Values: YES, NO. This db cfg parameter changes the resulting scale of a decimal arithmetic operation involving division. If the value is NO, the scale is calculated as 31-p+s-s' (see SQL Reference, Chapter 3, "Decimal Arithmetic in SQL"). If set to YES, the scale is calculated as MAX(3, 31-p+s-s'). This causes the result of decimal division to always have a scale of at least 3 (precision is always 31). Attention: Changing this db cfg parameter may cause changes to applications for existing databases. This can occur when the resulting scale for decimal division would be impacted by changing this db cfg parameter. Here are some possible scenarios that may impact applications. A view that was defined in an environment with one setting could fail with SQLCODE -344 when referenced after the db cfg parameter was changed to the other setting if the resulting scale of one of the view columns is changed. The message SQL0344N refers to recursive common table expressions, however, if the object name (first token) is a view, then you will need to drop the view and create it again to avoid the error. A static package will not change behaviour until the package is rebound, either implicitly or explicitly. For example, after changing from NO to YES, the additional scale digits may not be included in the results until rebind occurs. For any static packages that may experience this change, an explicit rebind command can be used to force a rebind. A check contraint involving a decimal division may restrict some values that were previously accepted by the check constraint. Such rows now violate the constraint but will not be detected until the one of the columns involved in the check constraint row is updated or SET INTEGRITY with IMMEDIATE CHECKED is processed. To force checking of such a constraint, ALTER TABLE to DROP the check constraint and then ALTER TABLE to ADD the constraint again. If any of these scenarios are possible on a database server with existing databases, the implications of changing the MIN_DEC_DIV_3 setting should be carefully considered. Also Note: there are no new message text for this parameter in the v6 or v71 timeframe. This implies the following two limitations: 1) The command "GET DB CFG FOR " will not display the MIN_DEC_DIV_3 setting. The best way to determine the current setting is to observe the side-effect of a decimal division result. For example, if the following db2 statement: VALUES (DEC(1,31,0)/DEC(1,31,5)) Returns sqlcode sql0419n, then the database does not have MIN_DEC_DIV_3 support or it is set to OFF. But if the statement returns "1.000", then MIN_DEC_DIV_3 is ON. 2) The command "? UPDATE DB CFG" displays a list of "config-keywords". MIN_DEC_DIV_3 does not appear in the list. --------------------------------------------------------------------------- Varem‘rket IBM DB2 Universal Database tilh›rer IBM Corporation. Alle andre varem‘rker anerkendes. --------------------------------------------------------------------------- *************************************************************************** ** ** (c) COPYRIGHT INTERNATIONAL BUSINESS MACHINES CORPORATION 2001. ** ALL RIGHTS RESERVED. ** (c) COPYRIGHT IBM DANMARK 2001. ** ***************************************************************************