IBM DB2 Universal Database* Version 6.1 para Windows 95** e Windows NT** PTF No: WR21302 VRMF: 06.01.0000.0060 +-- Nota: ----------------------------------------------------------------+ | | Para ler este arquivo mais facilmente, defina sua fonte para monospace. | | Se tiver recebido solu‡äes provis¢rias do suporte IBM ap¢s 04/01/2002 | entÆo entre em contato com eles, em vez de instalar este FixPak, para | solicitar uma versÆo atualizada das solu‡äes provis¢rias. Ao fazer isso, | vocˆ est  assegurando que seu sistema est  em estado consistente e que | nenhuma solu‡Æo provis¢ria foi perdida. | | Em todo este documento, X: ‚ usado para referˆncia … unidade de cdrom na qual | o CD do FixPak ‚ colocado e C:\SQLLIB ‚ o local onde os produtos DB2 | estÆo instalados. | | 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. | +-------------------------------------------------------------------------+ Este arquivo README cont‚m informa‡äes para os seguintes produtos e componentes: Espec¡fico do NT/95 ------------------- 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 Software Developer's Kit, V6.1 DB2 Datalinks Manager, V6.1 DB2 Administration Client, V6.1 DB2 Run-Time Client, V6.1 DB2 Satellite Edition, V6.1 DB2 Query Patroller, V6.1 --------------------------------------------------------------------------- 1. Conte£do dos FixPak 2. Notas da Instala‡Æo 2.1 Pr‚-requisitos 2.1.1 Pr‚-requisitos para o APAR IX73249 2.2 Antes da Instala‡Æo 2.3 Instru‡äes de Instala‡Æo 2.5 Instru‡äes de Instala‡Æo NÆo-assistida 2.5 Ap¢s a Instala‡Æo 2.5.1 Fazendo o rebind para banco de dados nÆo DRDA DB2 2.5.2 Fazendo o rebind do bancos de dados DRDA 2.5.3 Fazendo o rebind de Pacotes Espec¡ficos 2.5.4 Ferramenta de Administra‡Æo de Replica‡Æo DataJoiner 2.6 Notas de Desinstala‡Æo 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 Stored Procedures with PROGRAM TYPE MAIN 2.9 Java Method Signature in PARAMETER STYLE JAVA procedures and functions 3. Diversos 3.1 Biblioteca T‚cnica de Servi‡os e Produtos 3.2 Suporte ao Cliente 3.3 Servi‡o de Corre‡Æo 3.4 MIN_DEC_DIV_3 Database Configuration Parameter Para informa‡äes adicionais por favor veja os seguintes arquivos: C:\SQLLIB\RELEASE.TXT X:\APARLIST.TXT =========================================================================== 2. Notas da Instala‡Æo 2.1 Pr‚-requisitos Este Fixpak requer pelo menos uma VersÆo 6.1 do DB2 UDB para o produto NT/95 j  instalado no sistema. Para determinar a versÆo e o n¡vel do produto DB2 atualmente instalado, digite regedit em um prompt do MS-DOS e verifique os seguintes valores na chave de registro HKEY_LOCAL_MACHINE\SOFTWARE\IBM\DB2\\Current Version. Os valores devem ser os seguintes: VersÆo "6" Release "1" Modifica‡Æo "0" N¡vel de Servi‡o "WR21204" 2.1.1 Pr‚-requisitos para o APAR IX73249 Sa¡da Incorreta para DB2 LIST DCS APPLICATIONS SHOW DETAIL. O DB2 para MVS APAR PQ11645 deve ser aplicado em conjunto com o DB2 Connect APAR IX73249 para fornecer a exibi‡Æo de token de correla‡Æo significativa nas LIST DCS APPLICATIONS e nos comandos DB2 MVS DSP THD. 2.2 Antes da Instala‡Æo Vocˆ deve parar toda a atividade do banco de dados antes de aplicar este FixPak. Pare todas as aplica‡äes e emita os comandos: db2stop db2admin stop 2.3 Instru‡äes de Instala‡Æo Para iniciar o FixPak, execute X:\SETUP.EXE. 2.4 Instru‡äes de Instala‡Æo NÆo-assistida A versÆo do SETUP.EXE que acompanha este FixPak pode ser executada atrav‚s de uma op‡Æo de "instala‡Æo nÆo-assistida". A sintaxe desse recurso est  documentada no manual Quick Beginnings. Um arquivo de resposta de exemplo (DB2FIXPK.RSP) est  inclu¡do neste FixPak. 2.5 Ap¢s a Instala‡Æo Devido aos novos arquivos bind (.bnd) que foram enviados com este FixPak, vocˆ precisar  fazer o rebind dos utilit rios junto a todos os bancos de dados ap¢s a instala‡Æo do FixPak. Esta etapa ‚ necess ria para que as corre‡äes deste FixPak se efetivem. O procedimento de rebind, rascunhado abaixo, ‚ necess rio apenas uma vez por banco de dados. 2.5.1 Fazendo o rebind dos bancos de dados nÆo DRDA DB2 Ap¢s aplicar as corre‡äes, vocˆ deve fazer o seguinte: 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 Sendo que ‚ o nome de um banco de dados ao qual os utilit rios devem ser ligados. Consulte a vari vel de ambiente DB2PATH para determinar o caminho correto. DB2UBIND.LST e DB2CLI.LST contˆm listas de arquivos bind normalmente exigidos, usados para o DB2. Se for um banco de dados DB2 v1.x, nÆo fa‡a o bind de db2cli.lst. Ao inv‚s, use db2cliv1.lst ou, especificamente, efetue o bind de db2clics.bnd, db2cliur.bnd, db2clirr.bnd e de db2cliv1.bnd individualmente. 2.5.2 Fazendo o rebind dos bancos de dados DRDA Se estiver usando o DB2 Connect para acessar bancos de dados do host, ser  necess rio tamb‚m fazer o bind dos novos arquivos bind. Como mencionado acima, conecte-se ao banco de dados do host e, entÆo, fa‡a o bind dos utilit rios conforme segue: HOST COMANDO ===== =================================================================== 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 Fazendo o rebind de Pacotes Espec¡ficos Se deseja fazer o bind somente dos arquivos .bnd espec¡ficos para o banco de dados, emita o seguinte comando para cada banco de dados (sendo que ‚ o nome do arquivo bind e ‚ o nome do banco de dados). db2 terminate db2 CONNECT TO db2 BIND C:\SQLLIB\BND\ BLOCKING ALL GRANT PUBLIC db2 terminate 2.5.4 Ferramenta de Administra‡Æo de Replica‡Æo DatJoiner A localiza‡Æo da ferramenta DataJoiner Replication Administration (DJRA) (djra.exe) ‚ agora instalada no diret¢rio SQLLIB\DJRA. 2.6 Notas de Desinstala‡Æo Ao atualizar ou desinstalar o(s) produto(s) DB2 em um sistema Windows NT, vocˆ precisar  encerrar todos os servi‡os e processos DB2 na m quina. Se o arquivo psapi.dll existir no sistema em um dos diret¢rios armazenados na vari vel de ambiente, os servi‡os e processos devem ser encerrados automaticamente. Se psapi.dll nÆo existir no sistema, vocˆ ter  de encerrar manualmente todos os servi‡os DB2 antes de atualizar ou desinstalar. 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 Stored Procedures with PROGRAM TYPE MAIN To ensure family compatibility, PROGRAM TYPE MAIN stored procedures have been changed to pass in the procedure name as the first argument (ie, argv[0]). Existing PROGRAM TYPE MAIN stored procedures can be changed to use this feature by incrementing the indices used to access the argv[] argument array. Alternatively, the original behaviour of PROGRAM TYPE MAIN for Version 6.1 can be restored by turning on the registry variable DB2_RESTORE_PTMAIN_BEHAVIOUR 2.9 Java Method Signature in PARAMETER STYLE JAVA procedures and functions If specified after the Java method name in the EXTERNAL NAME clause of the CREATE PROCEDURE or CREATE FUNCTION statement, the Java method signature must correspond to the default Java type mapping for the sql signature specified after the procedure or function name. For example, the default Java mapping of the SQL type INTEGER is 'int', not 'java.lang.Integer'. If the signatures do not match, and exception will be raised when the procedure or function is invoked. 3. Diversos 3.1 Biblioteca T‚cnica de Produtos e Servi‡os Para obter uma fonte atualizada e completa de informa‡äes do DB2, incluindo informa‡äes sobre edi‡äes descobertas ap¢s a publica‡Æo deste readme, use a Biblioteca T‚cnica de Produtos e Servi‡os na World Wide Web em: http://www.software.ibm.com/data/db2/library 3.2 Suporte ao Cliente Para falar com um representante IBM referente a assistˆncia a este produto, chame 0-800-784-262. O suporte ao cliente tamb‚m ‚ fornecido via f¢rum de Perguntas e Respostas Eletr“nicas. Esses f¢runs sÆo acess¡veis atrav‚s da CompuServe, IBMLink e Usenet Newsgroup. (1) CompuServe - Para acessar os f¢runs em CompuServe, execute GO IBMDB2. - Se vocˆ nÆo tiver acesso … CompuServe, ligue para 1-800-848-8199 para obter informa‡äes sobre a associa‡Æo no Canad  ou nos EUA. (2) Usenet Newsgroup: comp.databases.ibm-db2 - Este Newsgroup da Internet ‚ um f¢rum geral para discutir questäes e/ou problemas encontrados na fam¡lia de produtos DB2. (3) (IBMLink) Talklink OS/2 BBS - Para acessar os f¢runs no IBMLink, v  para a se‡Æo OS2BBS. - Se vocˆ nÆo tiver acesso … IBMLink, ligue para 1-800-547-1283 para obter informa‡äes sobre a associa‡Æo no Canad  ou nos EUA. 3.3 Servi‡o de Corre‡Æo O servi‡o corretivo pode ser descarregado eletronicamente atrav‚s de: (1) FTP para servidor an“nimo ftp.software.ibm.com (anteriormente conhecido como ps.boulder.ibm.com) em 198.17.57.66. V  para ps/products/db2/fixes/%L/%P/ sendo que %L ‚ o local adequado (por exemplo, Inglˆs Americano, Espanhol, AlemÆo, etc.) e %P ‚ o nome/versÆo do produto (por exemplo, db22v5, db2aixv5, etc.). (2) Use um navegador World Wide Web (WWW) para conectar-se ao DB2 Service and Support Page em: http://www.software.ibm.com/data/db2/db2tech/index.html (3) No CompuServe, execute GO IBMDB2. EntÆo, v  para a biblioteca adequada para localizar o FixPak. (4) Na IBM PCC BBS (nos EUA), ligue para (919) 517-0001 (em Raleigh, Carolina do Norte) e digite "db2" no menu principal para localizar os FixPaks. Se nÆo tiver acesso a nenhuma das localiza‡äes acima, ligue para 0-800-784-262 para solicitar estes FixPaks por correio. Em outros pa¡ses, fora os EUA e o Canad , entre em contato com o n£mero do Servi‡o ao Cliente DB2 local para obter ajuda na aquisi‡Æo desses FixPaks. 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. --------------------------------------------------------------------------- * sÆo marcas ou marcas de servi‡o da IBM Corporation. ** sÆo marcas ou marcas de servi‡o de seus respectivos propriet rios. --------------------------------------------------------------------------- *************************************************************************** ** ** (c) COPYRIGHT INTERNATIONAL BUSINESS MACHINES CORPORATION 2001. ** TODOS OS DIREITOS RESERVADOS. ** ***************************************************************************