home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC98170 Status: Geschlossen

MERGE COMMAND WITH INSERT IN XML COLUMN RETURN ERROR SQL16084N

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
Merge command with insert  in xml column return error SQL16084N. 
 
When run a sql command like example below with a insert in a 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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See problem description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.1FP4.                                      * 
****************************************************************
Local-Fix:
The error will stop to happen after inserting the first record 
in 
the table with xml column, after that the merge command can run 
without problem.
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
First fixed in Version 10.1FP4.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
06.12.2013
15.12.2014
15.12.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.4 FixList