ContentsIBM DB2 Universal Database* for OS/2* Version 7 FixPak 13 and later Contents About this FixPak readme for IBM DB2 Universal Database* for OS/2* Version 7 FixPak 13 and later 1.1 About this readme 1.2 Who should read this readme file 1.3 How to get help OS/2 installation notes 2.1 Prerequisites 2.2 Installation instructions 2.3 Unattended installation instructions 2.4 After installation 2.4.1 Enabling the new SQL built-in scalar functions 2.4.2 Rebinding bind files 2.4.2.1 Rebinding to non-DRDA DB2 databases 2.4.2.2 Rebinding to DRDA databases 2.4.2.3 Rebinding specific packages 2.4.2.4 Binding db2sch.bnd to existing databases 2.5 Alternate Unicode conversion tables for CCSID 943 2.6 Version 7 FixPak 10a Updates 2.6.1 Longer than normal database activations or first connects 2.6.2 Search Discovery Listener Denial of Service Vulnerability 2.6.3 db2job security exposure 2.6.4 db2licm buffer overflow 2.7 Known problems and workarounds (this FixPak) 2.7.1 2.8 Known problems and workarounds (prior to this FixPak) 2.8.1 Differences between SNA and TCP/IP when using DB2 Connect 2.8.2 Restriction on the db2look command 2.8.3 Additional command modifiers 2.8.4 Using APPC listener 2.8.5 Correction to Performance Variable 2.8.6 Informix Federated support for DB2 Information Integrator 2.8.7 Data corruption after moving from DB2 Version 7 FixPak 8 or earlier 2.8.8 Application Development and supported software update 2.8.9 Informix Federated support for DB2 Relational Connect 2.8.10 Loss of Control Center functionality 2.8.11 Restoring backup images created under FixPak 4 or greater 2.8.12 Updates into local tables in federated systems Notices About this FixPak readme for IBM DB2 Universal Database* for OS/2* Version 7 FixPak 13 and later IBM DB2 Universal Database* for OS/2* Version 7 FixPak 13 and later PTF No: WR21344 VRMF: 7.1.0.103 Note: If you have received special fixes from IBM support, you must contact IBM support before you install this FixPak to check if you need an updated version of the special fixes. This helps ensure that your system is in a consistent state and that no special fixes are lost. This readme file contains information for the following products and components: DB2 Administration Client, Version 7.2 DB2 Application Development Client, Version 7.2 DB2 Connect Personal Edition, Version 7.2 DB2 Connect Enterprise Edition, Version 7.2 DB2 Run-Time Client, Version 7.2 DB2 UDB Enterprise Edition, Version 7.2 DB2 UDB Personal Edition, Version 7.2 DB2 UDB Workgroup Edition, Version 7.2 DB2 Warehouse Manager, Version 7.2 Before installing this DB2 for OS/2 FixPak, ensure that the line in your CONFIG.SYS file which initializes the HPFS file system is at the beginning of the file (if HPFS is being used). You can identify this line by looking for one similar to the following: IFS=C:\OS2\HPFS.IFS /CACHE:2048 /CRECL:4 /AUTOCHECK:CDE If it is not at the beginning of your CONFIG.SYS file, move it there before the DB2 FixPak installation. Throughout this document X: is used to refer to the CD-ROM drive into which the FixPak CD is placed and $DB2DIR is where the DB2 products are installed. By default, $DB2DIR is C:\SQLLIB. 1.1 About this readme This FixPak Readme has been updated up to FixPak 13. The information contained here is valid for users of FixPak 13 and later. The Release Notes have not been updated in this FixPak. See the Release Notes for Version 7 FixPak 8 which is included in this FixPak. 1.2 Who should read this readme file The information in this readme file should be read by database administrators who seek to upgrade their present version of DB2 products to the latest FixPak level. This readme file contains platform specific information about the latest changes and known problems and workarounds for DB2 products. 1.3 How to get help Web-based support for DB2 products, including documentation, FixPaks, and APAR information, is provided at http://www.ibm.com/software/data/db2/udb/support.html. DB2 FixPaks can also be downloaded from IBM's anonymous FTP server at ftp.software.ibm.com. Go to ps/products/db2/fixes/%L/%P/ where %L is the appropriate locale (for example, english-us, spanish, german), and %P is the product name/version (for example db2os2v7). The main Usenet newsgroup for DB2-related questions is comp.databases.ibm-db2. To contact DB2 Customer Service by phone: In North America, call 1-800-IBM-SERV. Outside North America, contact your local IBM office. For information on IBM offices in your country or region, consult the IBM Directory of Worldwide Contacts at http://www.ibm.com/planetwide For additional information on changes to the product, review the product Release Notes: X:\RELEASE.TXT OS/2 installation notes 2.1 Prerequisites Before installing this FixPak you must have DB2 UDB Version 7.2 or DB2 UDB Version 7.1 with FixPak 3 or later installed. To determine if the required prerequisites are installed, do the following: Double-click on the Installation Utility icon in the IBM DB2 folder. Select View, Installed Products Select the appropriate DB2 product. Select Details, Product Status. The version should be 07.02.04 2.2 Installation instructions Stop all database activity before applying this FixPak. To stop all database activity, issue these commands: db2stop db2admin stop To install the FixPak, type X:\DB2\\INSTALL\INSTALL where is the appropriate language directory. You will be presented with a list of products that are currently installed. Select a product and then select UPDATE from the Action menu. You must install the FixPak for every product listed (it is not necessary to reboot after each one, even if the completion message says so, it is sufficient to reboot after all products have been updated). If you use ODBC applications, rerun the ODBC Installer after rebooting, by double-clicking on the icon. Note: Do not select the Save a backup version? check box. This will not properly backup the changes and restoring from the backup may damage the installed DB2 UDB product(s). 2.3 Unattended installation instructions The FixPak install program (INSTALL.EXE) supports unattended installation using a response file. The syntax for this feature is documented in the Quick Beginnings book. A response file (DB2FIXPK.RSP) is provided for your convenience. It can be used without modification. Each product must be updated separately. Every DB2 UDB product that is installed on the system must be updated with this FixPak at the same time. You cannot mix service levels between the products. A /P:"product name" command line parameter is required. The following sample command files are provided with the FixPak for your convenience: DB2CONPE.CMD DB2 Connect Personal Edition DB2CONEE.CMD DB2 Connect Enterprise Edition DB2UDBEE.CMD DB2 Universal Database Enterprise Edition DB2UDBWE.CMD DB2 Universal Database Workgroup Edition DB2UDBPE.CMD DB2 Universal Database Personal Edition DB2SDK.CMD DB2 Application Development Client DB2ADMCL.CMD DB2 Administration Client DB2RTCL.CMD DB2 Run-Time Client DB2UDBWM.CMD DB2 Database Warehouse Manager 2.4 After installation 2.4.1 Enabling the new SQL built-in scalar functions FixPak 2 and later of Version 7 delivers new SQL built-in scalar functions. Refer to the SQL Reference and 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 or later 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. For example, db2updv7 -d -u -p . Note: FixPak 8 is the minimum prerequisite if you want to use a Version 8 client to connect to a Version 7 server. Therefore, anyone updating to FixPak 8 will also have to run the db2updv7 command. ATTENTION : If you intend to issue the db2updv7 command, it will change the database so it runs 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. You must perform a full offline backup of the database prior to running db2updv7 in order to have the ability to restore to a previous FixPak level. 2.4.2 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, which follows, only needs to be performed once per database. 2.4.2.1 Rebinding to non-DRDA DB2 databases After applying fixes, you must do the following: db2 terminate db2 CONNECT TO db2 BIND $DB2DIR\BND\@db2ubind.lst GRANT PUBLIC db2 BIND $DB2DIR\BND\@db2cli.lst GRANT PUBLIC db2 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. If you are prompted for a username and password on the CONNECT TO statement, the syntax of the statement is: CONNECT TO USER USING . DB2UBIND.LST and DB2CLI.LST contain lists of commonly required bind files that are used for DB2. 2.4.2.2 Rebinding to DRDA databases If you are using DB2 Connect 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 $DB2DIR\BND\@ddcsmvs.lst BLOCKING ALL SQLERROR CONTINUE GRANT PUBLIC VM BIND $DB2DIR\BND\@ddcsvm.lst BLOCKING ALL SQLERROR CONTINUE GRANT PUBLIC VSE BIND $DB2DIR\BND\@ddcsvse.lst BLOCKING ALL SQLERROR CONTINUE GRANT PUBLIC OS400 BIND $DB2DIR\BND\@ddcs400.lst BLOCKING ALL SQLERROR CONTINUE GRANT PUBLIC 2.4.2.3 Rebinding specific packages If you want to bind only the specific .bnd files to the database, issue the following commands for each database. db2 terminate db2 CONNECT TO db2 BIND $DB2DIR\BND\ BLOCKING ALL GRANT PUBLIC db2 terminate where represents the name of the bind file, and represents the name of your database. If you are prompted for a username and password on the CONNECT TO statement, the syntax of the statement is: CONNECT TO USER USING . 2.4.2.4 Binding db2sch.bnd to existing databases For FixPak installations on the server, an additional bind file needs to be bound to existing databases after applying the FixPak. This requirement does not apply to clients. This additional bind file is db2sch.bnd. Prerequisites If support for DB2 Version 8.1 clients is required, the db2updv7 command must be run following the installation of FixPak 8 or 9. If support for DB2 Version 8.1 clients is not needed, then db2sch.bnd does not need to be bound to existing databases. Procedure To bind db2sch.bnd on the server, execute these commands: At a command prompt: db2 terminate db2 CONNECT TO db2 BIND /db2sch.bnd BLOCKING ALL GRANT PUBLIC sqlerror continue db2 terminate or, At the DB2 command line: TERMINATE CONNECT TO BIND /db2sch.bnd BLOCKING ALL GRANT PUBLIC sqlerror continue TERMINATE where represents the name of a database to which the utilities should be bound, and where represents the full path name of the directory where the bind files are located. If you are prompted for a username and password on the CONNECT TO statement, the syntax of the statement is: CONNECT TO USER USING . 2.5 Alternate Unicode conversion tables for CCSID 943 Some characters in CCSID 943 have two code points each: "NEC" code point "IBM" code point Some other characters are also represented two code points each: a "NEC" code point and a "JIS" code point. For example, both X'8754' ("NEC") and X'FA4A' ("IBM") refer to the same Roman numeral one character in CCSID 943; and both X'879C' ("NEC") and X'81BE' ("JIS") refer to the same mathematical union symbol in CCSID 943. When using the DB2 default CCSID 943 to Unicode conversion table, both the "NEC" and "IBM"/"JIS" code points are converted to the same Unicode character; but on the reverse, the Unicode character is converted to the "IBM"/"JIS" code point. When using the Microsoft version of the CCSID 943 to Unicode conversion table, both "NEC" and "IBM"/"JIS" code points are also converted to the same Unicode character; but on reverse, the Unicode character is converted to the "NEC"/"JIS" code point. For example: X'8754'or X'FA4A' ==> U+2160 ==> X'FA4A' (using the DB2 default CCSID 943<-->Unicode conversion tables) X'8754'or X'FA4A' ==> U+2160 ==> X'8754'(using the Microsoft version of CCSID 943<-->Unicode conversion tables) X'879C' or X'81BE' ==> U+222A ==> X'81BE' (using either the DB2 default or Microsoft version of CCSID 943<-->Unicode conversion tables) There are also some characters in CCSID 943 that can be converted into two different Unicode characters, depending on whether the DB2 default conversion table or the Microsoft version of the conversion table is used. For example, the double-byte dash character X'815C' in CCSID 943 is converted to the Unicode character U+2014 when using the DB2 default CCSID 943 to Unicode conversion table, but X'815C' is converted to the Unicode character U+2015 instead when using the Microsoft version of the conversion table. If you want DB2 to use the Microsoft version of the conversion tables, follow the procedure below after installation is complete. Prerequisites Before replacing the existing external code page conversion table files in the sqllib/conv directory, you may want to back them up first. On UNIX, sqllib/conv/ is linked to the install path of DB2. Procedure To use the Microsoft version of the CCSID 943 to/from Unicode conversion table files: Copy: sqllib/conv/ms/0943ucs2.cnv to sqllib/conv/0943ucs2.cnv sqllib/conv/ms/ucs20943.cnv to sqllib/conv/ucs20943.cnv sqllib/conv/ms/0941ucs2.cnv to sqllib/conv/0941ucs2.cnv sqllib/conv/ms/ucs20941.cnv to sqllib/conv/ucs20941.cnv Restart DB2. The use of these Microsoft conversion tables is restricted to closed environment between DB2 943 database and DB2 943 clients using the Microsoft version of the conversion tables. If we have a DB2 943 client using the default DB2 conversion tables, and another DB2 943 client using the Microsoft version of the conversion tables, and both clients are connected to the same DB2 943 database, then the same character may be stored as two different code points in the DB2 943 database. 2.6 Version 7 FixPak 10a Updates 2.6.1 Longer than normal database activations or first connects If you have recoverable logging configured (LOGRETAIN=ON or USEREXIT=ON) and more than 4 GB of log space configured ( (LOGPRIMARY+LOGSECOND) * LOGFILSIZ * 4K ), you may experience longer than normal database activations or first connects. If the database is consistent at the time of activation, DB2 will unnecessarily reallocate log files, which is the reason for slow activation. This behavior may lead to rollforward or crash recovery failures. If these reallocated log files are used during a rollforward, the rollforward will fail with SQL1265 - archive log file is not associated with the current log sequence. A previous log file reallocation may result in the recreated log file not chained correctly with the previous log file. Rollforward fails when trying to process this log file. Crash recovery may fail when running a very large transaction requiring log space that spans across greater than 4 GB of active log space. This causes a wrong log sequence number to be written to the transaction logs on disk, which will cause DB2 crash recovery to fail. 2.6.2 Search Discovery Listener Denial of Service Vulnerability A vulnerability exists in the DB2 "Discovery" service that allows a skilled remote user to cause the Discovery service to stop responding by sending a malicious network packet. This creates a denial of service situation for the Discovery service only. If search discovery was being relied on to find DB2 servers on a local subnet, these would not be found after the listener was disabled. The only interim workaround is to preemptively disable discovery services. 2.6.3 db2job security exposure An exposure exists in the db2job and db2job2 programs that could allow a skilled user with local login access to a UNIX system where DB2 is installed to obtain system administrator ("root") privileges. An interim workaround exists and involves disabling job scheduling. For each instance: cd $HOME/sqllib/adm chmod 000 db2job db2job2 2.6.4 db2licm buffer overflow A buffer overflow vulnerability exists in the db2licm program that would allow a skilled user with local login access to a UNIX system where DB2 is installed to obtain system administrator ("root") privileges. An interim workaround exists which involves disabling the ability to install licenses. For each instance: cd $HOME/sqllib/adm chmod u-s db2licm To re-enable the ability to install licenses, run the following command: chmod u+s db2licm 2.7 Known problems and workarounds (this FixPak) 2.7.1 There are no known problems and workarounds for this FixPak. 2.8 Known problems and workarounds (prior to this FixPak) 2.8.1 Differences between SNA and TCP/IP when using DB2 Connect When connecting to an OS/390 system using SNA, the host VTAM layer automatically flows a commit when a new connection is made. The automatic commit allows the host side thread state to be inactive, and the thread immediately becomes inactive. However, when connecting to an OS/390 system using TCP/IP, there is no automatic commit. The application itself must flow an explicit commit after the connection to allow the thread to be inactive on the host. Without the explicit commit, the thread is subject to an idle thread time out. The suggested workaround is to rewrite the application so that it will perform an explicit commit if the connection goes idle after the connection. 2.8.2 Restriction on the db2look command You cannot use the "-f" option of the db2look command from a DB2 Version 7. 2 client at any Version 7 FixPak level. This restriction has been removed in DB2 Version 8. 2.8.3 Additional command modifiers Modifiers have been added to the EXPORT, IMPORT, and LOAD commands. The EXPORT command has the additional modifiers: Table 1. Additional File Type Modifiers (Export) Modifier Description striplzeros Removes the leading zeros from all exported decimal columns. db2 create table decimalTable ( c1 decimal( 31, 2 )) db2 insert into decimalTable values ( 1.1 ) db2 export to data of del select * from decimalTable Content of Exported file data +00000000000000000000000000001.10 db2 export to data of del modified by STRIPLZEROS select * from decimalTable Content of Exported file data +1.10 The IMPORT command has the following additional modifiers: Table 2. Additional File Type Modifiers (Import) Modifier Description timestampformat="x" x is the format of the time stamp in the source file.4 Valid time stamp elements are: YYYY - Year (four digits ranging from 0000 - 9999) M - Month (one or two digits ranging from 1 - 12) MM - Month (two digits ranging from 01 - 12; mutually exclusive with M and MMM) D - Day (one or two digits ranging from 1 - 31) DD - Day (two digits ranging from 01 - 31; mutually exclusive with D) DDD - Day of the year (three digits ranging from 001 - 366; mutually exclusive with other day or month elements) H - Hour (one or two digits ranging from 0 - 12 for a 12 hour system, and 0 - 24 for a 24 hour system) HH - Hour (two digits ranging from 0 - 12 for a 12 hour system, and 0 - 24 for a 24 hour system; mutually exclusive with H) M - Minute (one or two digits ranging from 0 - 59) MM - Minute (two digits ranging from 0 - 59; mutually exclusive with M, minute) S - Second (one or two digits ranging from 0 - 59) SS - Second (two digits ranging from 0 - 59; mutually exclusive with S) SSSSS - Second of the day after midnight (5 digits ranging from 00000 - 86399; mutually exclusive with other time elements) UUUUUU - Microsecond (6 digits ranging from 000000 - 999999; mutually exclusive with all other microsecond elements) UUUUU - Microsecond (5 digits ranging from 00000 - 99999, maps to range from 000000 - 999990; mutually exclusive with all other microseond elements) UUUU - Microsecond (4 digits ranging from 0000 - 9999, maps to range from 000000 - 999900; mutually exclusive with all other microseond elements) UUU - Microsecond (3 digits ranging from 000 - 999, maps to range from 000000 - 999000; mutually exclusive with all other Microseond elements) UU - Microsecond (2 digits ranging from 00 - 99, maps to range from 000000 - 990000; mutually exclusive with all other microseond elements) U - Microsecond (1 digits ranging from 0 - 9, maps to range from 000000 - 900000; mutually exclusive with all other Microseond elements) TT - Meridian indicator (AM or PM) A default value of 1 is assigned for unspecified YYYY, M, MM, D, DD, or DDD elements. A default value of 0 is assigned for all other unspecified elements. Following is an example of a time stamp format: "YYYY/MM/DD HH:MM:SS.UUUUUU" The following example illustrates how to import data containing user-defined date and time formats into a table called 'schedule': db2 import from delfile2 of del modified by timestampformat="yyyy.mm.dd hh:mm tt" insert into schedule The LOAD command has the following additional modifiers: Table 3. Additional File Type Modifiers (Load) Modifier Description timestampformat="x" x is the format of the time stamp in the source file.4 Valid time stamp elements are: YYYY - Year (four digits ranging from 0000 - 9999) M - Month (one or two digits ranging from 1 - 12) MM - Month (two digits ranging from 01 - 12; mutually exclusive with M and MMM) D - Day (one or two digits ranging from 1 - 31) DD - Day (two digits ranging from 01 - 31; mutually exclusive with D) DDD - Day of the year (three digits ranging from 001 - 366; mutually exclusive with other day or month elements) H - Hour (one or two digits ranging from 0 - 12 for a 12 hour system, and 0 - 24 for a 24 hour system) HH - Hour (two digits ranging from 0 - 12 for a 12 hour system, and 0 - 24 for a 24 hour system; mutually exclusive with H) M - Minute (one or two digits ranging from 0 - 59) MM - Minute (two digits ranging from 0 - 59; mutually exclusive with M, minute) S - Second (one or two digits ranging from 0 - 59) SS - Second (two digits ranging from 0 - 59; mutually exclusive with S) SSSSS - Second of the day after midnight (5 digits ranging from 00000 - 86399; mutually exclusive with other time elements) UUUUUU - Microsecond (6 digits ranging from 000000 - 999999; mutually exclusive with all other microsecond elements) UUUUU - Microsecond (5 digits ranging from 00000 - 99999, maps to range from 000000 - 999990; mutually exclusive with all other microseond elements) UUUU - Microsecond (4 digits ranging from 0000 - 9999, maps to range from 000000 - 999900; mutually exclusive with all other microseond elements) UUU - Microsecond (3 digits ranging from 000 - 999, maps to range from 000000 - 999000; mutually exclusive with all other Microseond elements) UU - Microsecond (2 digits ranging from 00 - 99, maps to range from 000000 - 990000; mutually exclusive with all other microseond elements) U - Microsecond (1 digits ranging from 0 - 9, maps to range from 000000 - 900000; mutually exclusive with all other Microseond elements) TT - Meridian indicator (AM or PM) A default value of 1 is assigned for unspecified YYYY, M, MM, D, DD, or DDD elements. A default value of 0 is assigned for all other unspecified elements. Following is an example of a time stamp format: "YYYY/MM/DD HH:MM:SS.UUUUUU" The following example illustrates how to import data containing user-defined date and time formats into a table called 'schedule': db2 import from delfile2 of del modified by timestampformat="yyyy.mm.dd hh:mm tt" insert into schedule 2.8.4 Using APPC listener If you have APPC listener started for your DB2 instance, stop your DB2 instance before stopping your APPC/SNA software. 2.8.5 Correction to Performance Variable Starting in the Release Notes for Version 7 FixPak 6 (and in FixPaks 7 and 8), there is an error in a performance variable name. In "Chapter 13. Configuring DB2" the section "DB2 Registry and Environment Variables" lists Table 5 Performance Variables. In this table a registry variable name is incorrect. The correction is: the variable name DB2_MINIMIZE_LIST_PREFETCH should be DB2_MINIMIZE_LISTPREFETCH. This correction affects FixPak 6, 7, and 8. 2.8.6 Informix Federated support for DB2 Information Integrator The Informix Federated support for DB2 Information Integrator was added starting in DB2 UDB Version 7 FixPak 4. If you have problems installing and configuring it (that is, informix script or related libraries are not installed), you should call the DB2 Support Team for help. 2.8.7 Data corruption after moving from DB2 Version 7 FixPak 8 or earlier This corruption problem affects data moved from DB2 Version 7 FixPak 8 or earlier to any of the following: Version 7 FixPak 9 or later Version 8 Version 8 FixPak 1 or later DB2 UDB Version 7 FixPak 9 and higher corrects a data corruption error. The corruption was originally caused in previous versions of DB2 by a double conversion of data sent from a client to a DB2 UDB Unicode database via a JTA connection. Any data other than ASCII invariant characters (hexadecimal value between 00 and 7F) that existed prior to Version 7 FixPak 9 is affected. After applying Version 7 FixPak 9 or later , the data corruption becomes visible upon retrieval of the CHAR, VARCHAR, and CLOB data. To fix the previously corrupted data: Export data using the same code page that the client used to put the data into the database. Migrate the database to the later version of DB2. Import the data from Step 1 using the Unicode code page 1208. For more information, refer to the "Data corruption after moving from DB2 Version 7 FixPak 8 or earlier to a later Version 7 FixPak or to DB2 Version 8" technote. 2.8.8 Application Development and supported software update For application development and supported software updates, visit the DB2 application development Web site at: http://www.ibm.com/software/data/db2/udb/ad/v7 2.8.9 Informix Federated support for DB2 Relational Connect Informix Federated support for DB2 Relational Connect was added in DB2 FixPak 4. If you have problems during installation or configuration (informix script and/or related libraries not installed with FixPak 4), you should call DB2 Support Team for help. 2.8.10 Loss of Control Center functionality There should be no problems introduced against back-level Control Center clients by applying FixPak 2 or FixPak 3 to a DB2 server. However, in DB2 Version 7.2, back-level Control Center clients will lose nearly all functionality. Back-level 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. 2.8.11 Restoring backup images created under FixPak 4 or greater When the RELOCATE USING option is used with the db2inidb command, the user provided configuration file is copied into the database directory (for example, SQL00001) and is renamed db2path.cfg. If the database was initialized as a snapshot, then the db2path.cfg file is removed after the necessary crash recovery completes. However, if the database was initialized as a standby, then the file will only be removed after the database is taken out of the rollforward pending or in-progress state (by stopping or cancelling the rollforward). Standby databases that do not contain SMS table spaces can be backed up when in the rollforward pending or in-progress state. If the db2path.cfg file exists for such a database, then it will be included in the backup image. Because this file is new to V7 beginning with FixPak 4, a restoration of an image containing this file will fail on any V7 level earlier than FixPak 4. If restoring from such a backup image, the instance must be running with a DB2 level of FixPak 4 or greater. 2.8.12 Updates into local tables in federated systems You can perform insert, update, and delete operations into local tables in an MPP federated environment. Although a workaround for INSERT statements was provided in FixPak 4, the workaround is no longer needed. This capability is fully enabled in FixPak 9. Notices IBM may not offer the products, services, or features discussed in this document in all countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country/region or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106, Japan The following paragraph does not apply to the United Kingdom or any other country/region where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions; therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product, and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information that has been exchanged, should contact: IBM Canada Limited Office of the Lab Director 8200 Warden Avenue Markham, Ontario L6G 1C7 CANADA Such information may be available, subject to appropriate terms and conditions, including in some cases payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems, and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements, or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility, or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information may contain examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious, and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information may contain sample application programs, in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. Each copy or any portion of these sample programs or any derivative work must include a copyright notice as follows: (C) (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. (C) Copyright IBM Corp. _enter the year or years_. All rights reserved. IBM, DB2, Universal Database, and S/390 are trademarks of International Business Machines Corporation in the United States, other countries, or both. Windows is a registered trademark of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Other company, product, or service names may be trademarks or service marks of others. ------------------------------------------------------------------------------- * are trademarks or registered trademarks of IBM Corporation. ** are trademarks or registered trademarks of their respective owners. ------------------------------------------------------------------------------- ******************************************************************************* ** ** (c) COPYRIGHT INTERNATIONAL BUSINESS MACHINES CORPORATION 1999-2004. ** ALL RIGHTS RESERVED. ** *******************************************************************************