SQL> SQL> create table NSB_TABLE of XMLTYPE ORA-31038: Invalid enumeration value: "GB" Insert into TEST_TABLE values ( xmlType('GB')) SQL> insert into TEST_TABLE values ( xmlType('GB')) SQL> select XMLSerialize(DOCUMENT OBJECT_VALUE AS CLOB NO INDENT) SQL> connect &USERNAME/&PASSWORDġ0 ENABLEHIERARCHY => DBMS_XMLSCHEMA.ENABLE_HIERARCHY_NONEġ7 '/xsd:schema/xsd:simpleType/xsd:restriction/xsd:enumeration' I then used OBJECT_VALUE.schemavalidate to identify the complained about invalid "MO" enumeration.It is indeed "MO", not "M0" in both xsd and xml.
The FAQ thread can be found on the main page of this forum To expand on Marco's questions, does it validate correctly with AL? Does the schema contain M instead of the letter? We are using 10.2.0.3.It failed to enalbe the check constraint ( using xmlisvalid) of the xmltable which had xml instance loaded. Jasmine How do you validate? What database version are you on / using? Can you provide some testcode?ĭid you have a look at the XMLDB Forum FAQ thread regarding lazy and strict validation. We have all the states from "AL" to "WY" listed as enumeration values.but the xml instance failed to pass validation with "MO", which is part of the enumeration list.Īny one can think of any reasons? We are going live next week with this. I have a schema which has StateCode element. HELP!!! Failed validation for emueration value which IS in the schema! - XML DB I am so troubled by this and hope someone can shed some light:
0 kommentar(er)
