home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC98175 Status: Closed

Merge command with insert in an XML column returns error SQL16084N

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
When running a SQL command like example below with an insert 
using an 
xml 
column: 
 
MERGE INTO WHEN NOT MATCHED 
THEN INSERT (XML_column) VALUES ( '<Cust><addr></addr></Cust>') 
 
Return Error: 
 
DB21034E  The command was processed as an SQL statement because 
it was not a valid Command Line Processor command.  During SQL 
processing it returned: 
 
SQL16084N  An assigned value in the copy clause of a transform 
expression is not a sequence with exactly one item that is a 
node. Error QName=err:XUTY0013. SQLSTATE=10705
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 10.5 Fix Pack 3.                          * 
****************************************************************
Local Fix:
The error will stop happening after inserting the first 
record in 
the table with an xml column. After that the merge command can 
run 
without problem.
available fix packs:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Solution
First fixed in Version 10.5 Fix Pack 3.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
06.12.2013
28.12.2014
28.12.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.4 FixList