Known problems and workarounds

SQL1224 error from DRDA wrapper (AIX)

If a 32-bit DB2 UDB server is run on an AIX system and an application running 7on the same system has more than one local database connection through the 7DRDA^(R) wrapper, then the application might get the following error:

SQL1822N  Unexpected error code "-1224" received from 
7data source "W3_SERVER2". 
7Associated text and tokens are 
7  func="DriverConnect" 
7  msg="SQL1224N  A database agent"
7SQLSTATE=560BD

To avoid this error, put the following entry in the federated configuration 7file (instance_directory/cfg/db2dj.ini):

EXTSHM=ON

Alternately, you can catalog the local DB2 UDB database as being on a TCP/IP 7node. For example:

CATALOG TCPIP NODE my_node REMOTE my_host SERVER 123;
7CATALOG DB mydb AT NODE my_node;
7CREATE WRAPPER drda;
7CREATE SERVER my_server TYPE DB2/UDB VERSION 8 WRAPPER drda
7   AUTHORIZATION "my_id" PASSWORD "my_pw"
7   OPTIONS(ADD DBNAME 'MYDB');

Hotkeys not working in Microsoft Visual Studio .NET Framework 1.1

If your hotkeys are not working in Microsoft Visual Studio .NET Framework 71.1, you can download a hotfix from the Microsoft Web site. You can find 7the hotfix in the Microsoft Knowledge Base, article Q836745.

The simplified Chinese locale (AIX)

3AIX has changed the code set bound to the simplified Chinese 3locale Zh_CN on:

3
• AIX Version 5.1.0000.0011 or later
3
• AIX Version 5.1.0 with maintenance level 2 or later

The code set has been changed from GBK (code page 1386) to GB18030 (code 3page 5488 or 1392). Since DB2 Universal Database for AIX supports the GBK 3code set natively and the GB18030 code set via Unicode, DB2 Universal Database 3will default the Zh_CN locale's code set to ISO 8859-1 (code page 819), and 3in some operations will also default the locale's territory to the United 3States (US).

To work around this limitation, you have two options:

• You can override the locale's code set from GB18030 to GBK and the territory from US to China (whose territory ID is CN and territory code is 86).
• You can use a different simplified Chinese locale.

If you choose to use the first option, issue the following commands:

db2set DB2CODEPAGE=1386
db2set DB2TERRITORY=86
db2 terminate
db2stop
db2start 

If you choose to use the second option, change your locale from Zh_CN to either ZH_CN or zh_CN. The ZH_CN locale's code set is Unicode (UTF-8), while the zh_CN locale's code set is eucCN (code page 1383).

5The simplified Chinese locale (Red Hat Linux)

5Red Hat Version 8 and later (including Red Hat Enterprise Linux 5[RHEL] versions 2.1 and 3) have changed the default code set for simplified 5Chinese from GBK (code page 1386) to GB18030 (code page 5488 or 1392).

3Since DB2 Universal Database for Linux supports the GBK code 3set natively and the GB18030 code set via Unicode, DB2 Universal Database 3will default its code set to ISO 8859-1 (code page 819), and in some operations 3will also default its territory to the United States (US).

3To work around this limitation, you have two options:

3
• You can override the Red Hat default code set from GB18030 to GBK and 3the territory from US to China (whose territory ID is CN and territory code 3is 86).
3
• You can use a different simplified Chinese locale.

If you choose to use the first option, issue the following commands:

db2set DB2CODEPAGE=1386
3db2set DB2TERRITORY=86
3db2 terminate
3db2stop
3db2start 

If you choose to use the second option, issue any one of the 3following commands:

export LANG=zh_CN.gbk
3export LANG=zh_CN
3export LANG=zh_CN.utf8

where the code set associated with zh_CN is eucCN 3or code page 1383, and with zh_CN.utf8 is code page 1208.

Merant Driver Manager incompatibility (UNIX)

There are incompatibilities with Unicode support when the Merant Driver 5Manager accesses the DB2 ODBC driver on UNIX. These incompatibilities cause 5the Merant Driver Manager to use Unicode even if the application did not request 5Unicode use. This situation can lead to problems with components such as the 5Data Warehouse Center, Information Catalog Manager, and MQSI, which require 5the Merant Driver Manager to support non-IBM data sources. You can use an 5alternate DB2 ODBC driver library without Unicode support enabled until a 5permanent solution is available.

An alternative DB2 ODBC driver library without Unicode support enabled 5is included with DB2 UDB Version 8.1 for AIX, HP-UX, and Solaris Operating 5Environment. To use this alternative library, you must create a copy of it, 5giving the copy the original DB2 ODBC driver library's name.

To switch to the non-Unicode ODBC library on AIX, HP-UX, or the Solaris 5Operating Environment, see the following instructions. Because this is a manual 5process, you must carry it out every time you update your product, including 5after the application of successive FixPaks or modification levels.

NFS APAR IY32512 - Unavailable threads (AIX)

AIX 5 NFS APAR IY32512 might cause the db2stop command 2to stop on systems with a large number of partitions.

On a server that is receiving large numbers of requests for blocking locks 2on files that are already locked, the lock daemon might become unresponsive. 2This situation occurs when all available locked threads are allocated to threads 2that are waiting for the locks to become available, so there is no thread 2available to pick up the work when the unlock request is made.

When this situation occurs the stopped nodes must be restarted. There 2is a DB2 UDB workaround for this situation by stopping the nodes one at a 2time using the NODENUM option of the db2stop command.

Data Links server backup fails using Tivoli Storage Manager archive server (AIX, Solaris Operating Environment)

Problem: When installing or migrating to DB2 Data Links Manager, Version 8.2, a Data Links File Manager (DLFM)-initiated backup of Data Links server data to a Tivoli Storage Manager archive server fails. One of the following sets of error messages display, either on-screen or on the installation status report:

DLFM129I: Automatic backup of DLFM_DB database has been triggered. 
          Please wait for the backup to complete.

DLFM901E: A system error occurred. Return code = "-2062".
          The current command cannot be processed.
          Refer to the db2diag.log file for additional information.

-- or --

DLFM811E: The current DLFM database could not be backed up. 
          SQL code = "-2062", Return code = "-2062"

DLFM901E: A system error occurred. Return code = "-2062".
          The current command cannot be processed.
          Refer to the db2diag.log file for additional information.

Cause: The DB2 Data Links Manager Installer program failed to set the variables required to use Tivoli Storage Manager as an archive (backup) server for a Data Links server.

Tip: If you want to use Tivoli Storage Manager as an archive server, and you have not yet installed or migrated to DB2 Data Links Manager, Version 8.2, you can prevent this problem from occurring. First, do not use the "Tivoli Storage Manager" backup option from the Installer program. Then, manually configure the Data Links Manager Administrator's profile to include the appropriate Tivoli Storage Manager variables, as described in step 2 that follows. After you have completed both tasks, you can proceed with the installation or migration.

Workaround: Perform the following tasks in the order listed.

1. Back up the DLFM database using the following command:

   db2 backup <dlfm_db><path>

   where:
   • <dlfm_db>is the name of the DLFM database. By default, the database is called DLFM_DB.
   • <path> is the directory path to the backup storage location of your choice.
2. Manually configure the Data Links Manager Administrator's profile to include the appropriate Tivoli Storage Manager variables. The manual configuration procedure and the required variables are described in the following documentation topics:
   • Using Tivoli Storage Manager as an archive server (AIX)
   • Using Tivoli Storage Manager as an archive server (Solaris Operating Environment)

   You can find these topics either online in the DB2 Information Center, or in the "System Management Options" chapter of the DB2 Data Links Manager Administration Guide and Reference.

   • If you are completing a new installation of DB2 Data Links Manager, Version 8.2, you are finished.
   • If you are migrating to DB2 Data Links Manager Version 8.2, rerun the Migration Utility program, db2dlmmg.

SQLFLAG (STD) precompiler option error

If the SQLFLAG(STD) precompile option is enabled, it will cause the following 4error: Abend C6 occurred while running Precompile program DSNHPC

Remove the SQLFLAG (STD) precompile option when using the Development Center 4to create SQL stored procedures to run on DB2 for z/OS, Version 8.

DB2 Connect Custom Advisor

Despite being documented in the DB2 Connect User's 7Guide, the DB2 Connect Custom Advisor is no longer supported in Version 78.2.

Displaying Indic characters in the DB2 GUI tools

If you have problems displaying Indic characters when using the DB2 GUI tools, you might not have the required fonts installed on your system.

DB2 Universal Database has packaged the following IBM TrueType and OpenType proportional Indic language fonts for your use. You can find these fonts in the font directory on any of the following CDs:

7 7
• 7IBM Developer Kit, Java Technology Edition 7(64-bit) for AIX 5L7
7
• 7DB2 Embedded Application Server and applications 7(XML registry, Web Administration tools and Java distributed debugger) for 7your operating system7

These fonts are to be used only in conjunction with DB2 UDB. You cannot engage in the general or unrestricted sale or distribution of these fonts:

Detailed instructions on how to install the fonts and modify the font.properties file can be found in the Internationalization section of the IBM Development Kit for Java documentation.

In addition, the following Microsoft products come with Indic fonts that can be used with DB2 GUI tools:

• Microsoft Windows 2000 operating system
• Microsoft Windows XP operating system
• Microsoft Publisher
• Microsoft Office

GUI tools are not supported for zSeries servers (Linux)

With the exception of the DB2 Setup wizard, the GUI tools will not work on zSeries servers running the Linux operating system. This limitation includes any items normally launched from the Installation launchpad, such as the Quick Tour.

If you want to use the GUI tools with one of these systems, install the administrative tools on a client system with a different system configuration, and use this client to connect to your zSeries server.

Enclose DB2 Information Center search terms within quotation marks 7if they contain numbers

To get accurate search results in the DB2 Information Center you must enclose 7search terms that include numbers within quotation marks.

For example, if you search for the following term you will receive no results:

  1.4.1

However, if you enclose the term within quotation marks, you receive the 7appropriate results:

  "1.4.1"

A search for the following term will return extra topics:

  DB20000I

But a search on the following term works properly:

  "DB20000I"

Information Catalog Center log file not generated when importing tag 4language files

If an Information Catalog Center log file is not generated when you import 4tag language files to the Information Catalog Center, perform the following 4troubleshooting steps:

4

When running db2icmimport from a command line:

4

4

4
• If output files were not generated (.xml, .out, .err, .log), there is 4probably an error on the command line. Verify that the first five arguments, 4which are UserId, Password, Database, Catalog, and Tagfile, are correct. View 4the syntax by entering the db2icmimport command. 4If this does not solve the problem, modify db2icmimport to capture the output of the db2javit command 4by using the -g option to save the output to a file. For example: 4

  db2javit -j:com.ibm.db2.common.icm.tag.IcmImport -w: -i: 
  4   -o:"-Xmx128m -Xms32m" -g:"d:\temp\myimport.trc" ...

4
• If a log file was not generated, there is usually a parsing error. Look 4at the .xml file and the .out file. If you can, insert a ":COMMIT.CHKPID(DEBUG)" 4command at the beginning of the tag language file. This command generates 4debug report messages and checks the .xml and .out files for parsing errors.
4
• After parsing, errors should appear in the .log file. When the debug report 4is being generated, look at the .log file and the .out file for information.
4
• Always check the .err file to see if there is a run time error.

4

4

4

When importing tag language files using the Information Catalog 4Center GUI:

4

4

4
• When you import tag language files using the GUI interface, no .out or 4.err files are generated.
4
• If a .log or .xml file is generated, try to debug by using those files.
4
• If a .log or .xml file is not generated or does not help, run the import 4process from a command line to get more information.

4

4

Binding Query Patroller packages

If the Query Patroller packages are not bound after applying a fixpak, 6a user without DBADM authority or proper Query Patroller privileges can encounter 6the following error when using the Query Patroller Center or Query Patroller 6command line:

SQL0001N - Binding or precompilation did not complete successfully.

If you are using the Query Patroller Center, the SQL0001N error is logged 6in qpdiag.log file. If you are using the Query Patroller command line, the 6SQL0001N is returned to the console

Auto-bind code exists to initiate automatic binding. However, the automatic 6binding fails when the connecting user does not have the necessary privileges 6to execute all statements in the Query Patroller packages. A symptom of this 6problem is missing folders in the Query Patroller Center.

To avoid this problem, the qpserver.lst packages should be bound manually 6by a user with DBADM authority or necessary privileges after applying a fixpak.

Unavailability of ports with Query Patroller (Windows)

Submitted queries in Query Patroller might receive SQL code -29007 when 7there are no more available ports on Windows XP or Windows 2003. The likelihood 7of this error increases with an increasing number of clients accessing Query 7Patroller. If this situation happens, set the following registry variables 7as follows:

   MaxUserPort=65534
7   TcpTimedWaitDelay=30 

and restart your system for the changes to take effect.

Secure environments (Windows)

You might experience file permission problems if you are using DB2 Universal 1Database on Windows and are not an administrator on the Windows system. If 1you receive an SQL1035N, SQL1652N, or SQL5005C error message, possible causes 1and workarounds are shown in the following information:

XML Extender sample programs renamed

Some XML Extender sample programs might have the same name as other installed 2programs. Accidentally invoking another program with the same name as an 2XML Extender sample program can damage your XML files. The following list 2shows the old XML Extender sample program names as well as new replacement 2program names that are less likely to cause conflicts. Make sure you use 2the new sample program names instead of the old ones to prevent damaging your 2XML files.

Using the new sample programs with the sample sqx files

The source code (.sqx files) for the executables listed previously are 2located in the samples\db2xml\c directory of your installation. 2The source files are still labeled with their old names. If you make changes 2to the source code, copy your newly compiled executables (with the old names) 2to the sqllib\bin directory. On Windows platforms, you must make 2an additional copy, rename it with its new name above, and copy it to the 2bin directory. Both copies replace the existing files in the bin directory. 2For example, after compiling your new version of shred.exe, you need to make 2two copies and replace the files in the bin directory: one labeled shred.exe 2and the other renamed dxxshrd.exe. On UNIX platforms, you need only to replace 2the file with the old name with your newly compiled version. If you create 2new executable files from these samples, you must copy the new files from 2the \SQLLIB\samples\db2xml\c\ directory into the \SQLLIB\bin\ directory, and then make an additional copy, renaming them according 2to the previous table.

Decomposing documents in XML Extender that contain non unique attribute 4and element names

You can now decompose documents that contain non-unique attributes or non-unique 4element names that map to different columns (of the same or different tables) 4without receiving the DXXQ045E error. The following is an example of an XML 4document with non-unique attributes and non-unique element names:

<Order ID="0001-6789">
4       <!-- Note: attribute name ID is non-unique -->
4       <Customer ID="1111">
4                    <Name>John Smith</Name>
4       </Customer>
4       <!-- Note: element name Name is non_unique -->
4       <Salesperson ID="1234"> 
4              <Name>Jane Doe</Name>
4       </Salesperson>
4       <OrderDetail>
4              <ItemNo>xxxx-xxxx</ItemNo>
4              <Quantity>2</Quantity>
4              <UnitPrice>12.50</UnitPrice>
4       </OrderDetail>
4       <OrderDetail>
4              <ItemNo>yyyy-yyyy</ItemNo>
4              <Quantity>4</Quantity>
4              <UnitPrice>24.99</UnitPrice>
4       </OrderDetail>       
4</Order>

The accompanying DAD, which maps the duplicate elements and 4attributes to different columns, looks like this:

<element_node name="Order">
4  <RDB_node>
4    <table name="order_tab" key="order_id"/>
4    <table name="detail_tab"/>
4    <condition>
4      order_tab.order_id=detail_tab.order_id
4    </condition>
4  </RDB_node>
4
4  <!--attribute ID duplicated below, but mapped to a different col-->
4  <attribute_node name="ID">
4    <RDB_node>
4      <table name="order_tab" />
4      <column name="order_id" type="char(9)"/>
4    </RDB_node>
4  </attribute_node>
4  
4  <element_node name="Customer">
4    <!--attribute ID duplicated above, but mapped to a different col-->
4    <attribute_node name="ID">
4      <RDB_node>
4        <table name="order_tab" />
4        <column name="cust_id" type="integer"/>
4      </RDB_node>
4    </attribute_node>
4
4    <!--element name duplicated below, but mapped to a different col-->
4    <element_node name="Name"> 
4      <text_node>
4        <RDB_node>
4          <table name="order_tab" />
4          <column name="cust_name" type="char(20)" />
4        </RDB_node>
4      </text_node>
4    </element_node>
4  </element_node>
4    
4  <element_node name="Salesperson">
4    <!--attribute ID duplicated above, but mapped to a different col-->
4    <attribute_node name="ID">
4      <RDB_node>
4        <table name="order_tab" />
4        <column name="salesp_id" type="integer"/>
4      </RDB_node>
4    </attribute_node>
4          
4    <!--element name duplicated above, but mapped to a different col--> 
4    <element_node name="Name"> 
4      <text_node>
4        <RDB_node>
4          <table name="order_tab" />
4          <column name="salesp_name" type="char(20)" />
4        </RDB_node>
4      </text_node>
4    </element_node>
4  </element_node>
4    
4  <element_node name="OrderDetail" multi_occurrence="YES">
4    <element_node name="ItemNo">
4      <text_node>
4        <RDB_node>
4          <table name="detail_tab" />
4          <column name="itemno" type="char(9)"/>
4        </RDB_node>
4      </text_node>
4    </element_node>
4    <element_node name="Quantity">
4      <text_node>
4        <RDB_node>
4          <table name="detail_tab" />
4          <column name="quantity" type="integer"/>
4        </RDB_node>
4      </text_node>
4    </element_node>
4    <element_node name="UnitPrice">
4      <text_node>
4        <RDB_node>detail_tab" />
4          <table name="detail_tab" />        
4          <column name="unit_price" type="decimal(7,2)"/>
4        </RDB_node>
4      </text_node>
4    </element_node>
4  </element_node>
4</element_node>

The contents of the tables would look like the following 4sample after the preceding document is decomposed:

ORDER _TAB:
4
4ORDER_ID       CUST_ID       CUST_NAME       SALESP_ID       SALESP_NAME
40001-6789      1111          John Smith      1234            Jane Doe
4
4DETAIL_TAB:
4
4ORDER_ID          ITEMNO         QUANTITY          UNIT_PRICE
40001-6789         xxxx-xxxx      2                 12.50
40001-6789         yyyy-yyyy      4                 24.99

Differences between SNA and TCP/IP when using DB2 Connect

When connecting to an OS/390 system using SNA, the host VTAM^(R) layer automatically 5 flows a commit when a new connection is made. The automatic commit allows 5the host side thread state to be inactive, and the thread immediately becomes 5 inactive.

However, when connecting to an OS/390 system using TCP/IP, there is no 5automatic commit. The application itself must flow an explicit commit after 5the connection to allow the thread to be inactive on the host. Without the 5explicit commit, the thread is subject to an idle thread time out.

The suggested workaround is to rewrite the application so that it will 5perform an explicit commit if the connection goes idle after the connection.