Before using this information and the product it supports, be sure to read the general information under Notices.
This document contains proprietary information of IBM. It is provided under a license agreement and is protected by copyright law. The information contained in this publication does not include any product warranties, and any statements provided in this manual should not be interpreted as such.
You can order IBM publications online or through your local IBM representative.
To order DB2 publications from DB2 Marketing and Sales in the United States or Canada, call 1-800-IBM-4YOU (426-4968).
When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you.
The Release Notes contain information about known problems and documentation updates for DB2(R) Version 9 for Linux(R), UNIX(R), and Windows(R) and for DB2 Connect(TM) Version 9.
The chapter on known problems includes information about:
The chapter on documentation updates includes late-breaking additions or corrections to product documentation.
The primary source of DB2 product documentation is the DB2 Information Center. You can find this online at http://publib.boulder.ibm.com/infocenter/db2help/index.jsp.
Alternatively, you can install a local copy of the DB2 Information Center, which is included with the product as a separately installable image. If you install a local copy, you should download the latest update before using your local copy. Updating your Information Center will provide a complete copy of the documentation also adds capabilities that improve searches for DB2 message information. For instructions, see Updating the DB2 Information Center installed on your computer or intranet server.
The list below highlights topics in the DB2 Information Center of particular interest for product installation and troubleshooting:
In addition, support and troubleshooting assistance is available on the DB2 Support Web site. This site includes technotes and service flashes that describe changes to the documentation and information about known limitations discovered after the creation of the Release Notes. The DB2 Support Web site address is http://www.ibm.com/software/data/db2/udb/support.html.
Windows systems use backslashes (\) to delimit directories in a directory path. Linux and UNIX systems use forward slashes (/) as delimiters. The Release Notes use these conventions when the information is platform specific. However, when the information is platform independent, the Release Notes use the Windows convention, so if you are running on a Linux or UNIX system, you must enter directory paths differently than shown.
This section includes information about:
In some cases, the information states that a particular aspect of a feature is not supported or that a performing a particular action with a feature might result in problems. In these cases, attempts to use the feature might fail, or the results might be useless or harmful.
The db2sampl command might fail with a SQL0443 error if:
Try one of the following:
Beta and non-beta versions of DB2 Version 9 cannot coexist on a system. This problem applies to both client and server components of the product.
Uninstall the beta version of DB2 Version 9 before installing the non-beta version.
When you install the DB2 Information Center, you can choose a service name and port number rather than accepting the default values. If you choose a service name that already exists in the services file on the system and only change the port number, you might receive an error that states The service name specified is in use.
Solution 1: Use the default values.
Solution 2: Use a service name and port number that are both already in the services file.
Solution 3: Add a service name and port number to the service file using values that are not already used.
You cannot install a DB2 product in a path whose name contains National Language characters.
Install your DB2 product in a path whose name does not contain National Language characters.
National Language characters are characters not found in the English (en_US) character set.
The DB2 Setup Launchpad does not display if you do not set the
TEMPdirectory system variable.
Solution 1: Set the TEMP directory system variable for the current session by entering the following command from a command prompt:
set TEMP=directory name
For example, set TEMP=c:\temp .
Solution 2: Set the TEMP directory system variable as system-wide variable. To do this:
Installing a DB2 Universal Database (UDB) Version 8 product is not supported if a DB2 Version 9 product is already installed on the system. This problem applies to both client and server installations.
To install a copy of DB2 UDB Version 8 when DB2 Version 9 is already installed:
The DB2 UDB Version 8 DB2 Setup Launchpad does not prevent you from installing Version 8 when Version 9 is already installed. However, doing so will cause problems.
You cannot use regular (non-Administrator) user accounts to run the db2start and db2stop commands on Windows 2000.
Solution 1: Use a Windows Power User account or a Windows Administrator account.
Solution 2: Install a newer version of the Windows operating system.
On a Windows Server 2003 computer, you cannot install a DB2 client if you do not have Administrator authority.
A System Group Policy needs to be changed by an Administrator user before a non-Administrator user can install a client. To do this, an Administrator user needs to enable the 'Disable Windows Installer' policy. To access this setting, enter gpedit.msc to launch the Group Policy Object Editor then select Computer Configuration, then Administrative Templates, then Windows Components, then Windows Installer. Set this value to Never.
You might see an error message in the installation log that refers to the SRSetRestorePoint API. The message text reads in part: ...Calling SRSetRestorePoint API...The call to SRSetRestorePoint API failed.
Ignore this error message, which is caused by a Windows Installer error.
Asian characters might not display properly.
Obtain and install the required fonts. For details, see the DB2 documentation topic entitled Availability of Asian fonts (Linux).
The maximum length for the installation path name is approximately 100 bytes on AIX(R) and HP-UX PA-RISC platforms.
None
For details on the problem, see the Technote # 1239797 entitled Maximum length of DB2 9 installation path on UNIX and Linux platforms .
The command to uninstall the DB2 Embedded Application Server (EAS) component of the DB2 product does not uninstall the component completely. The registry entry and file system directory remain.
A solution is provided for each platform.
Solution (Windows):
Solution (Linux and UNIX):
This command displays the content of the registries. The entry for EAS is shown below:
S,DB2EAS,6.1.0.0,AppServer_install_path,,,,,,,where AppServer_install_path is the actual path where EAS is installed.
where AppServer_install_path is the path where EAS is installed
During a non-GUI DB2 product installation, it is possible to see corrupted text if you use particular combinations of locales and code sets. The following combinations are known to display corrupted text:
One message known to display corrupted text is the message that states that an SMTP server wasn't specified.
None
The types of installation affected are db2_install and db2setup -r
<response file>on Linux and UNIX and
setup /u <response file>on Windows.
The uncorrupted version of the SMTP server message reads as follows: Notification SMTP server has not been specified. Notifications cannot be sent to contacts in your contact list until this is specified. For more information see the DB2 administration documentation.
Use of the Decimal Float data type in CLI applications is subject to the following temporary restrictions:
None
Use of the DB2DecimalFloat class in DB2 .NET Data Provider is subject to the following temporary restrictions:
None
In DB2 Version 9, the name of the DB2 Universal JDBC Driver changed to the IBM(R) DB2 Driver for JDBC and SQLJ. However, the JDBC DatabaseMetaData.getDriverName method returns the string "IBM DB2 JDBC Universal Driver Architecture" for the driver name.
None
Issuing an ALTER DATABASE PARTITION GROUP statement to add a range of database partitions that includes database partition n and then issuing another ALTER DATABASE PARTITION GROUP statement to add a different range of database partitions can cause problems. These problems occur when the second statement includes a LIKE DBPARTITIONNUM n clause. For example:
ALTER DATABASE PARTITION GROUP <db-partition-name>
ADD DBPARTITIONNUMS (
<db-partition-number1> TO <db-partition-number2>
-- a range that includes database partition number <n>
) WITHOUT TABLESPACES
ALTER DATABASE PARTITION GROUP <db-partition-name>
ADD DBPARTITIONNUMS (
<db-partition-number1> TO <db-partition-number2>
-- a range that is different from the range specified in the previous statement
) LIKE DBPARTITIONNUM <n>
If you execute this sequence of statements, your instance is suspended and the database is marked bad.
None.
To use the CREATE DATABASE ON path command on Windows, you need to first perform some setup.
Enable the feature by setting a new registry variable, DB2_CREATE_DB_ON_PATH, to "ON."
Error messages might be received when the following conditions are met:
The registry variable DB2_CREATE_DB_ON_PATH is also part of the SAP aggregate registry variable DB2_WORKLOAD. The DB2_CREATE_DB_ON_PATH registry variable is "ON" by default for SAP.
If you use path support when creating new databases, applications written before Version 9 that use the db2DbDirGetNextEntry () API (or an older version of the API) might not work correctly. Refer to Technote # 1238742 for details
The following database macros and structures are deprecated beginning in DB2 Version 9, that is they might be removed in a future release. (Replacements appear in brackets following each deprecated item if there is a replacement available.) The replacements are common to both Windows and UNIX platforms:
Indic characters might not display properly in GUI tools.
Obtain and install the required fonts. For details, see the DB2 documentation topic entitled Displaying Indic characters in the DB2 GUI tools.
The View Storage function of the Control Center does not support the new XML storage object. This problem occurs in XML-enabled databases only.
None
The Query Patroller scheduling feature cannot save schedules to a file in this version.
None
The problem is due to an incompatibility with the IBM Software Developer's Kit for Java(TM) level used in this version of the DB2 product.
The new capability to create trusted connections using the IBM DB2 Driver for JDBC and SQLJ does not support CLI, including XA connections.
None
The What's New information includes a section on functionality that is discontinued in this release. Some descriptions of functionality that is discontinued still appear in other parts of the product documentation; ignore these references.
Any important, late changes to the product error messages are available in DB2 Service Technote #1238566.
The product documentation on migration considerations for DB2 Connect should include the following details:
If you migrate from a release prior to DB2 Connect Version 8.2.2 (equivalent to Version 8.1 FixPak 9), the authentication type specified in the database directory entry at the gateway overrides the authentication type cataloged at a DB2 client. If you did not specify an authentication type for the client, the default authentication type is SERVER. Ensure that the authentication type at the gateway is compatible with the client and the server. For more information, see Security types supported with DB2 Connect.
The documentation on installing the IBM DB2 Driver for ODBC and CLI should include the following details:
The zip or tar.Z file that contains the driver is located in the installation CD directory (CD Top)/db2/(platform)/clidriver.
The documentation on the DB2Xml interface contains some incorrect information. The following DB2Xml interface methods have been renamed:
The documentation related to JDBC connection pooling contains some information about functionality that is discontinued in this release:
recycleDB2Connection: public void recycleDB2Connection() reuseDB2Connection (untrusted reuse without reauthentication): public DB2Connection reuseDB2Connection() public DB2Connection reuseDB2Connection( int connectionReuseProtocol, java.util.Properties properties) public DB2Connection reuseDB2Connection( int connectionReuseProtocol)
getDB2Connection (untrusted reuse without reauthentication): public DB2Connection reuseDB2Connection( int connectionReuseProtocol, java.util.Properties properties) recycleDB2Connection: public void recycleDB2Connection()
Documentation related to the useTargetColumnEncoding property for DataSource is obsolete. This property has been removed from the IBM DB2 Driver for JDBC and SQLJ.
The What's New documentation regarding changes in existing functionality should include the following text:
In DB2 Version 9, the value returned from the CURRENT TIMESTAMP special register might not be unique, even for requests from the same application on a single database partition. There has never been a documented guarantee that requests return unique CURRENT TIMESTAMP values and changes in DB2 Version 9 increase the possibility that two requests might return the same value. This change in behavior will not impact an application unless the application uses the CURRENT TIMESTAMP special register value with an expectation that two requests would never return the same value.
Possible approaches for applications requiring unique values include:
The documentation contains information that is incorrect. The text should state:
If the tabschema is empty (") or you specify NULL and tabname, an error is returned. To retrieve information for a specific table, you must identify the table by both schema and table name.
The product documentation topic High Availability should include the following details:
In a clustered environment, you should not specify the DB2 server's transferable IP address, or any hostname that resolves to this address, in the db2nodes.cfg file. Use of these addresses or names in the db2nodes.cfg file can prevent DB2 database partitions from successfully relocating after a computer failure.
The current documentation is incorrect. The text describing this parameter should read:
The upper limit of the log file size, combined with the upper limit of the number of log files (logprimary + logsecond), gives an upper limit of 512 GB of active log space. As well, the range of valid values for the logfilsiz parameter is [4 - 524286].
Because DB2 Version 9 contains significantly more functionality than previous DB2 releases did, DB2 Version 9 memory requirements are greater than those of previous releases. In particular, the basic memory requirement has typically increased by between 0.5 and 1.5 MB per connection, depending on the operating system. This basic memory requirement is for the memory that the operating system allocates for each connection and is independent of the dynamically allocated memory, such as the application heap and sort heap, that each connection uses. If you migrate to DB2 Version 9, you might need to adjust your memory allocation parameters to accommodate the somewhat larger per-connection footprint of DB2 Version 9.
To contact IBM in your country or region, check the IBM Directory of Worldwide Contacts at http://www.ibm.com/planetwide
To learn more about DB2 products, go to http://www.ibm.com/software/data/db2/.
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.
Company, product, or service names identified in the documents of the DB2 Version 9 documentation library may be trademarks or service marks of International Business Machines Corporation or other companies. Information on the trademarks of IBM Corporation in the United States, other countries, or both is located at http://www.ibm.com/legal/copytrade.shtml.
The following terms are trademarks or registered trademarks of other companies and have been used in at least one of the documents in the DB2 documentation library:
Microsoft(R), Windows, Windows NT(R), and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.
Intel(R), Itanium(R), Pentium(R), and Xeon(R) are trademarks of Intel Corporation in the United States, other countries, or both.
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Linux is a trademark of Linus Torvalds in the United States, other countries, or both.
Other company, product, or service names may be trademarks or service marks of others.