Limitations

IMPORT REPLACE does not honor the Not Logged Initially clause

The IMPORT command's REPLACE option does not honor the CREATE TABLE statement's 7NOT LOGGED INITIALLY (NLI) clause or the ALTER TABLE statement's ACTIVATE 7NOT LOGGED INITIALLY clause.

If an import with the REPLACE action is performed within the same transaction 7as a CREATE TABLE or ALTER TABLE statement where the NLI clause is invoked, 7the import will not honor the NLI clause. All inserts will be logged.

7

Workaround 1

7

Delete the contents of the table using the DELETE statement, then invoke 7the import with INSERT statement. 7

7

Workaround 2

7

Drop the table and recreate it, then invoke the import with INSERT statement. 7

7

This limitation applies to DB2 UDB Version 7 and DB2 UDB Version 8.

Data export with ODBC to file warehouse program

The Data export with ODBC to file warehouse program does not support the 7following Sybase data types:

7
• BIT
7
• BINARY
7
• VARBINARY

Structured types in the Development Center

The Development Center no longer supports the creation of structured types.

Development Center limitations for 64-bit operating systems

Debugging of Java stored procedures against a 64-bit server is not supported by the Development Center. Debugging SQL stored procedures is supported on 64-bit Windows operating systems. 6Developing OLE DB or XML User 6Defined Functions is not supported for 64-bit servers.

Development Center (Linux)

You cannot use the Development Center to debug Java stored procedures 2running on any of the Linux distributions (32-bit, 64-bit, Intel, 2zSeries^(R), or iSeries^(TM)).

Debugging stored procedures with double quotation marks

The Development Center does not support debugging for any stored procedure 4with double quotation marks (") in the stored procedure name, schema, 4or specific name.

Path settings needed to enable Java routines to compile in the Development Center

The Development Center cannot compile Java routines unless it knows where your developer kit versions are installed. Default directories for your developer kit versions are written to your $HOME/.ibm/db2/dc/DB2DC.settings file when the Development Center starts for the first time. You can copy these directories into your $USER.settings file and modify them with a Unicode editor, or you can create symbolic links to your developer kit directories in the default locations.

Development Center limitations to run and debug Java stored procedures 6simultaneously

The Development Center does not support running and debugging Java stored 6procedures simultaneously. In the Development Center, you can either run multiple 6Java stored procedures at the same time or debug a single Java stored procedure; 6you cannot run a Java stored procedure while debugging another Java stored 6procedure. By default, the KEEPFENCED database manager configuration keyword 6is set to KEEPFENCED=YES as required for debugging SQL stored procedures. 6When the keyword KEEPFENCED has the default value YES, the routine process 6is kept active and JVM port conflicts will occur. Java stored procedures will 6cause a JVM exception and will fail in any of the following circumstances 6when the default KEEPFENCED=YES database manager configuration setting is 6used:

6
• Building a Java stored procedure in the Development Center then debugging 6it
6
• One user running a Java stored procedure and another user debugging a 6Java stored procedure while the initial Java stored procedure is still running
6
• One user debugging a Java stored procedure and another user running a 6Java stored procedure while the initial Java stored procedure is being debugged

To work around this limitation, ensure that the KEEPFENCED database manager 6configuration keyword is set to KEEPFENCED=NO by running the following commands:

   db2 update dbm cfg using KEEPFENCED NO
6   db2stop
6   db2start

When KEEPFENCED is set to NO, the db2fmp process will shut down when a 6Java stored procedure call is finished, and DB2 UDB will start a new db2fmp 6process to handle the next routine call. This ensures that there will be no 6existing JVM in debug mode when you start to debug a Java stored procedure.

The KEEPFENCED=YES setting is required to build SQL stored procedures for 6debugging and to debug SQL stored procedures. When KEEPFENCED=NO, you can 6still build and execute SQL stored procedures but you cannot debug them.

Cursors in PHP applications

When the PHP interpreter creates a cursor on behalf of an application, 7it is created by default as a Scrollable Keyset-driven cursor. In certain 7cases, this might cause unexpected results to be returned. In order to avoid 7this situation, explicitly specify the "FOR READ ONLY" clause for 7all SELECT statements that are used to update data. Other alternatives include 7setting the CLI Configuration parameters "Patch2=6", "Patch2=42", 7or "DisableKeysetCursor=1". However, each of these might have other 7consequences. Refer to the CLI Guide and Reference documentation for details regarding these configuration keywords.

Four unsupported SQL administrative routines

The following SQL administrative routines are not supported in this release:

7
• APP procedure
7
• INSTALLAPP procedure
7
• SERVER procedure
7
• UNINSTALLAPP procedure

Bind option limitations for CLI packages

Some bind options might not take effect when binding CLI packages with 7any of the following list files: db2cli.lst, ddcsmvs.lst, ddcs400.lst, ddcsvm.lst, or ddcsvse.lst. Because CLI packages are used by CLI, ODBC, JDBC, OLE DB, 7.NET, and ADO applications, any changes made to the CLI packages affect all 7applications of these types. Only a subset of bind options are therefore 7supported by default when binding CLI packages. The supported options are: 7ACTION, COLLECTION, CLIPKG, OWNER, and REPLVER. All other bind options that 7impact CLI packages are ignored.

To create CLI packages with bind options that are not supported by default, 7specify the COLLECTION bind option with a collection ID that is different 7from the default collection ID, NULLID. Any bind options specified are then 7accepted. For example, to create CLI packages with the KEEPDYNAMIC YES bind 7option, which is not supported by default, issue the following command:

db2 bind @db2cli.lst collection newcolid keepdynamic yes

In order for CLI/ODBC applications to access the CLI packages created in 7the new collection, set the CurrentPackageSet CLI/ODBC keyword in the db2cli.ini initialization file to the new collection ID.

To overwrite CLI packages that already exist under a particular collection 7ID, perform either of the following actions:

7
• Drop the existing CLI package before issuing the bind command for this 7collection ID
7
• Specify the ACTION REPLACE bind option when issuing the bind command

CLI LOAD restriction for specifying column names

If the INSERT statement supplied to the CLI LOAD utility includes a VALUES 7clause, target columns cannot be specified. For example, the following statement 7is supported by CLI LOAD:

INSERT into tableA VALUES (?, ?, ?)

This statement, however, that specifies target columns is not supported 7for use with the CLI LOAD utility:

INSERT into tableA (col1, col2, col3) VALUES (?, ?, ?)

Failures when reporting a successful login during a connection 5attempt (AIX)

When using OS authentication on AIX, DB2 UDB attempts to report a successful 5login to AIX upon successful authentication during a connection attempt. 5Prior to Version 8 FixPak 5, if DB2 UDB was unable to report a successful 5login, the connection would fail despite the user being authenticated. Starting 5with Version 8 FixPak 5, the connection is allowed to continue and the failure 5is logged in the db2diag.log file.

SNA support limitations in Version 8

The following support has been withdrawn from DB2 Universal Database Enterprise 3Server Edition (ESE) Version 8 for Windows and UNIX operating systems, and 3from DB2 Connect Enterprise Edition (CEE) Version 8 for Windows and UNIX operating 3systems:

3
• Multisite update (two-phase commit) capability using SNA cannot be used. 3Applications that require multisite update (two-phase commit) must use TCP/IP connectivity. Multisite update (two-phase commit) using 3TCP/IP to a host or iSeries database server has been available for several 3releases. Host or iSeries applications that require multisite update (two-phase 3commit) support can use the new capability of TCP/IP multisite update (two-phase 3commit) support within DB2 Universal Database ESE, Version 8.
3
• DB2 Universal Database ESE or DB2 CEE servers no longer accept client 3connections using SNA. As of version 8, FixPak 1, DB2 Universal Database allows 3the 32-bit version of AIX, Solaris Operating Environment, HP-UX, and Windows 3applications to access host- or iSeries database servers using SNA. This support 3allows applications access to host or iSeries database servers using SNA, 3but using only one-phase commit.
3
• Sysplex support with DB2 Universal Database for z/OS is only available 3using TCP/IP. Sysplex support is not provided using SNA connectivity.
3
• Change password support is no longer available using SNA connectivity 3to host database servers.
3
• All SNA support will be withdrawn in the next version of DB2 Universal 3Database and DB2 Connect.

Tools catalog database creation not supported (Linux AMD64)

The creation of the tools catalog database under a 64-bit DB2 UDB instance 5on Linux (AMD64) is not supported. Do not attempt to create the tools catalog 5under a 64-bit instance using any of the following methods:

5
• Installing DB2 UDB
5
• Updating a 64-bit instance using the db2isetup command
5
• Issuing the CREATE TOOLS CATALOG CLP command 5after the installation is finished.

The creation of the tools catalog database under a 32-bit instance on 5Linux (AMD64) is supported as of Version 8.1.4.

Tools catalog database creation not supported (AIX, Solaris Operating 5Environments, and HP-UX)

The creation of the tools catalog is not supported during the installation 5of DB2 UDB against 64-bit instances on the hybrid 64-bit platforms. The hybrid 5platforms are:

5
• AIX
5
• Solaris Operating Environments
5
• HP-UX
5
• Other platforms that support both 32-bit and 64-bit instances

If you want to create a tools catalog against a 64-bit instance, this 5can be done after the installation of DB2 UDB either through the Command Line 5Processor using the CREATE TOOLS CATALOG CLP command 5or using the Control Center. You will also need to install a 64-bit IBM Developer 5Kit for Java for this operation. Refer to the DB2 Administration Server section 5of the DB2 Administration Guide for more details.

Scheduling a warehouse process to run at intervals

When scheduling a warehouse process to run at intervals, you must determine the longest time it takes to run all the production steps in the process and schedule the intervals accordingly. If a process exceeds the scheduled time interval, all subsequently scheduled occurrences of that process will not run and will not be rescheduled.

Load and Import Columns page does not support DBCS characters in IXF files

If you use the Load wizard or Import notebook to set up a load or import from an IXF input file containing DBCS characters, the Columns page will not correctly display the column names contained in the file.

Two-part user ID not supported (Windows ME)

The two-part user ID for the CONNECT statement and ATTACH command, such 7as domainname\username, is not supported on Windows ME.

Minimum display settings for GUI tools

For the GUI tools such as the Control Center to work properly, you must have a screen resolution of at least 800 by 600 and use a display palette of at least 32 colors.

Do not partition Information Catalog Center tables

Tables that the Information Catalog Manager uses must be contained within 2a single database partition. Numerous methods are available to put the tables 2within a single partition. The following procedure is one approach that works.

2
1. Open a DB2 Command Line Processor and issue these commands: 2
   2
   1. 2

      CREATE DATABASE PARTITION GROUP partition_group_name 
      2     ON DBPARTITIONNUM partition_number

   2
   2. 2

      CREATE REGULAR TABLESPACE tablespace_name 
      2     IN DATABASE PARTITION GROUP partition_group_name
      2     MANAGED BY SYSTEM USING ('cname')

   where partition_group_name is the same in 2both commands.
2
2. Click Start -> Programs -> IBM DB2 -> Set-up Tools -> 2Manage Information Catalog Wizard.
2
3. On the Options page, specify the table space name in the Table space field.

Improper display of GB18030 characters in the title bar of a window

If you have characters from the GB18030 Chinese character encoding standard 7in the title bar of a window, they might appear as questions marks or squares.

Query Patroller limitations when DYN_QUERY_MGMT is disabled

Query Patroller cannot perform the following actions if the database configuration 5parameter DYN_QUERY_MGMT is disabled:

5
• Release queries from a held state
5
• Make a running or queued query run in the background when the query is 5in the foreground

If you attempt to release a query from held state, or change a foreground 5query to a background query when DYN_QUERY_MGMT is set to DISABLE, an error 5message will be displayed and the state of the query will not change. If held 5queries are scheduled to run and DYN_QUERY_MGMT is disabled at the time they 5start running, an error message is written to the qpdiag.log file and the 5queries are left in held state.

Query Patroller result tables now use DB2QPRT schema

Starting with FixPak 5, all new result tables are created in the schema 5DB2QPRT rather than in the schema of the submitter.

DROPIN privilege on the DB2QPRT schema is granted to operators whose profiles 5were created prior to installation of FixPak 5 and had either:

5
• The MONITORING privilege with edit authority
5
• The HISTORICAL ANALYSIS privilege with edit authority

DROPIN privilege on the DB2QPRT schema is granted the first time Query 5Patroller creates a result table in this schema.

Operators who are given MONITORING privilege with edit authority or HISTORICAL 5ANALYSIS privilege with edit authority after the installation of FixPak 5 5are also granted DROPIN privilege on the DB2QPRT schema upon creation or update 5of their profiles.

Health indicator restrictions

2The health monitor is unable to execute actions for the db2.db2_op_status health indicator if the indicator enters the down state. 2This state can be caused, for example, when an instance that the indicator 2is monitoring becomes inactive because of an explicit stop request or an abnormal 2termination. If you want to have the instance restart automatically after 2any abnormal termination, you must configure the fault monitor to keep the 2instance highly available.