DB2 - Problembeschreibung
Problem IC62754 | Status: Geschlossen |
SQL16163N RECEIVED DURING SCHEMA REGISTRATION WITH SAME ELEMENT NAMES IN DIFFERENT COMPLEXTYPES | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
Completing a schema registration fails with SQL16163N even though duplicate elements names in different complex types is supported. For example in the following schemas (foo1.xsd, foo2.xsd and bar1.xsd), an ellement named "childElement" exists in both "complexType1" and "complexType2". Schema registration should complete successfully, however, registration fails with the following error if foo1.xsd or foo2.xsd are the primary document. SQL16163N XML document contains a duplicate element declarationfor "childElement". SQLSTATE=2200M foo1.xsd ----------- <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://example.org/common"> <xsd:import namespace="http://example.org/order"/> <xsd:include schemaLocation="foo2.xsd"/> </xsd:schema> foo2.xsd ---------- <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:common="http://example.org/common" targetNamespace="http://example.org/common"> <xsd:complexType name="complexType1"> <xsd:sequence> <xsd:element name="childElement" type="xsd:string"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="complexType2"> <xsd:sequence> <xsd:element name="childElement" type="xsd:integer"/> </xsd:sequence> </xsd:complexType> </xsd:schema> bar1.xsd ----------- <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:common="http://example.org/common" targetNamespace="http://example.org/order"> <xsd:import namespace="http://example.org/common"/> <xsd:complexType name="complexType3"> <xsd:sequence> <xsd:element name="element1" type="common:complexType1"/> <xsd:element name="element2" type="common:complexType2"/> </xsd:sequence> </xsd:complexType> </xsd:schema> | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * Completing a schema registration fails with SQL16163N even * * though duplicate elements names in different complex types * * is * * supported. * **************************************************************** * RECOMMENDATION: * * Upgrade to V9.7 Fix Pak 1 * **************************************************************** | |
Local-Fix: | |
Try using a different schema as the primary schema. For the example above, schema registration completes successfully when bar1.xsd is used as the primary schema. | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows | |
Lösung | |
Problem was first fixed in Version 9.7 Fix Pack 1 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 25.08.2009 04.01.2010 04.01.2010 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7., 9.7.FP1 | |
Problem behoben lt. FixList in der Version | |
9.7.0.1 |