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 section on known problems includes information about:
The section 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 provides a current copy of the documentation and 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, migration, usage, and troubleshooting:
Additional resources are available for product installation, migration, usage, and troubleshooting:
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 (create sample database) command might fail with an SQL0443 error if you:
Try one of the following:
Beta and non-beta versions of DB2 Version 9 cannot coexist on a system. This restriction 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.
Try one of the following:
You cannot install a DB2 product in a path whose name contains National Language characters. National Language characters are characters not found in the English (en_US) character set.
Install your DB2 product in a path whose name does not contain National Language characters.
The command to uninstall the DB2 Embedded Application Server (EAS) component 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):
S,DB2EAS,6.1.0.0,AppServer_install_path,,,,,,,where AppServer_install_path is the path where EAS is installed.
where AppServer_install_path is the path where EAS is installed.
During a non-GUI DB2 product installation, corrupted text might be displayed if you use particular combinations of locales and code sets on some platforms. 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 has not been specified.
The types of installation affected are db2_install and db2setup -r response file on the Linux and UNIX platforms and setup -u response file on the Windows platform.
None.
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.
The DB2 First Steps fails to launch if the default browser is Microsoft Internet Explorer Beta 7.
Solution 1: Use another supported browser as the default browser, such as Internet Explorer Version 6.
Solution 2: Run regedit and update the registry entry HKEY_CLASSES_ROOT\htmlfile\shell\open\command to use lowercase letters. For example, change
"C:\Program Files\Internet Explorer\IEXPLORE.EXE" -nohome
to the following text:
"C:\Program Files\Internet Explorer\iexplore.exe" -nohome
The DB2 Setup Launchpad is not displayed if you do not set the TEMP directory 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 to a system-wide variable by completing the following steps:
Installing a DB2 UDB Version 8 product on a system is not supported if a DB2 Version 9 product is already installed on that 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:
For DB2 UDB Version 8 Fix Pack 11 and earlier releases, 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.
By default on a Windows Server 2003 computer, you cannot install a DB2 client if you do not have Administrator authority.
An Administrator user must change a System Group Policy before a non-Administrator user can install a client. To do this, an Administrator user needs to enable the 'Disable Windows Installer' setting by completing the following steps:
Asian characters might not be displayed 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 and HP-UX PA-RISC platforms. For details on the problem, see the Technote # 1239797 entitled Maximum length of installation path on UNIX and Linux platforms .
None.
Use of the DB2DecimalFloat class in DB2 .NET Data Provider is subject to the following temporary restrictions:
None. Refer to APAR JR25094 to track the removal of these restrictions.
In DB2 Version 9, the name of the DB2 Universal JDBC Driver changed to the IBM DB2 Driver for JDBC and SQLJ. However, the JDBC DatabaseMetaData.getDriverName method returns the string "IBM(R) DB2 JDBC Universal Driver Architecture" for the driver name.
None.
When running with a new deadlock event monitor that tracks all statements (and optionally data values) it becomes possible for a badly behaving application (one with very high number of statements in a unit of work) to exhaust the system monitor heap. It is also possible for the monitor heap to become exhausted if there are a large number of applications executing concurrently.
To ease the consumption of space, inactive statements are written out to the event monitor when the number of statements for a particular application reaches a defined threshold. After being written to the event monitor, the memory consumed by these inactive statements is released. In addition, an application will write out all of its current inactive statements to the event monitor if at any time it is unable to acquire memory from the system monitor heap. The application will then attempt to acquire memory again. If the second attempt fails, a message is logged, and the information that was to be saved in the memory is not included in the statement history information being gathered for the unit of work (UOW) in which the application is processing.
The default limit on the number of inactive statements kept by any one application is 250. This default value is overridden by using the registry variable DB2_MAX_INACT_STMTS to specify a different value. You may want to choose a different value for the limit to either increase or reduce the amount of system monitor heap used for inactive statement information.
With this behavior, an application might now record its statement history entries to the deadlock event monitor outside the context of a deadlock (when one of the thresholds mentioned above is reached). When this occurs, there is a way to associate these entries to the list of statements recorded at the time of a deadlock for analysis. To do this, you must look for any statement history entries that have one of the following values:
Any entries in the event monitor output that do not meet this criteria can be ignored for the purposes of diagnosing the deadlock.
In the case when writing to a table event monitor, the number of evmon_activates will also need to be checked.
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, the instance is suspended and the database is marked bad if you issue this sequence of statements:
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>
None.
To use the CREATE DATABASE command with the ON path option 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 returned 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, and might be removed in a future release. The replacement appears in parentheses following each deprecated item. The replacements are common to the Windows, Linux and UNIX platforms:
Indic characters might not be displayed 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.
Clicking the Contacts icon or using the Contacts choice from the Tools menu on the Task Center causes the Task Center to hang and requires the Control Center to be restarted.
To create or change a notification contact:
The Query Patroller scheduling feature cannot save schedules to a file. 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
None.
Submitted queries in Query Patroller might receive SQL code -29007 when there are no available ports on Windows XP or Windows 2003. The likelihood of this error increases as the number of clients accessing Query Patroller increases.
Set the following Windows registry variables as follows:
MaxUserPort=65534 TcpTimedWaitDelay=30
and restart your system for the changes to take effect.
You can find details about setting Windows registry variables on the Microsoft Help and Support Web site at http://support.microsoft.com/.
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 data in the SALES table included in the SAMPLE database has been updated for Version 9, but the description of this table in the documentation does not show the updated values.
The "What's new in Fix Pack 1" summary topic is missing information about new DB2Binder options for the IBM DB2 Driver for JDBC and SQLJ. For details on these new options, see the Java topic in the "Application Development" documentation updates section.
You can download the IBM DB2 LDAP authentication plug-in modules, samples, and documentation on the configuration and usage of the plug-ins from www14.software.ibm.com/webapp/iwm/web/preLogin.do?lang=en_US&source=swg-dm-db2ldap.
In this document, DB2 Connect users should review the topics in the "Application development" sections (known problems and documentation updates).
An incorrect warning message is returned when you use the Query Patroller Center or Query Patroller command line to perform one of the following tasks while the Query Patroller server is running:
The warning message is as follows:
DQP1024W Creation, change, or removal of a query class will not take effect until the Query Patroller server is restarted.
This message is no longer accurate. The three query class tasks will take effect immediately unless there are queued or running queries. If there are queued or running queries, including newly submitted queries, the query class changes will take effect when the queued or running queries complete. If you do not want to wait for all queued and running queries to be completed, you must restart the Query Patroller server.
The documentation is missing information that can help clarify the choices in the Submitter Profile to Use drop-down list in the Query Submission Preferences window of the Query Patroller Center.
If you are logged in, but do not have either DBADM authority or Edit privilege for Query Patroller user administration, you can only add or update a submission preference for yourself. In this case, the Submitter Profile to Use drop-down list contains existing submitter profiles of the DB2 groups that you belong to, instead of just the operating system groups that you belong to.
If you are logged in, and have either DBADM authority or Edit privilege for Query Patroller user administration, you can add or update submission preferences for other users. In this case, the Submitter Profile to Use drop-down list contains all existing group submitter profiles.
The Query Patroller documentation is missing the following information:
The Query Patroller documentation is missing the following information:
When you define a new table space during Query Patroller installation in a partitioned environment, you can select an existing database partition group. Alternatively, you can set up a new database partition group for the new table space. If you choose to set up a new database partition group, you can select only one database partition from the list on the install panel for that new database partition group. If you want to add partitions into the new database partition group, you must add them manually after the installation is complete.
The Query Patroller documentation is missing the following information:
You do not need to install Query Patroller Client Tools on a DB2 client if you only want to submit queries from that client to the Query Patroller server. You only need to install Query Patroller Client tools on a DB2 client if you need to run the Query Patroller client tools from that client machine.
The Query Patroller documentation is missing the following information:
The capability to create trusted connections using CLI is available with Fix Pack 1. The restriction documented in the previous version of the Release Notes no longer applies. For information on this feature, see the DB2 Information Center at http://publib.boulder.ibm.com/infocenter/db2help/index.jsp.
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 "DB2Binder utility" topic is missing the following documentation for three new binder options available with Fix Pack 1:
The following changes apply to the documentation on registry variables:
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.