1 2 Previous Next 20 Replies Latest reply: Oct 8, 2012 9:12 AM by 961018 Go to original post RSS
      • 15. Re: Error Loading XSD documents 11g
        odie_63
        From the links you provided what i could get is like the XSD gets converted in to an internal representation.
        The api which our product calls for loading the xsd is XmlSchemaLoad()

        +"this function converts the DOM representation into an internal schema representation. The schema document can be provided as a URI or directly a DOM representation. In the URI case, this function reads the input stream and builds a DOM representation of the schema before converting it into internal representation"+

        So during this interanl representation conversion the NCS reference (& #x0410;-& #x044F;) for А-я is not getting identified. So internally parsing should happen for this conversion is what i am thinking.
        I think you're missing the point.

        Maybe if you'd care answering this question we could get somewhere :
        So, at any point, do you use the database to parse XML documents or not?
        The program you're using doesn't run inside the database, right?
        The setting Mark gave you - as far as I know - only affects the internal database parser, not programs based on external libraries.
        • 16. Re: Error Loading XSD documents 11g
          961018
          Dear Odie,

          Sorry i missed that question.

          The program which loads the xsd doesnt run in DB.
          So you are telling the DB xml parser doesnt have anything to do with the xsd conversion/loading by the XmlSchemaLoad() , which means the command gave by mark wont have any impact :( .

          Any more info you need to get an idea on whats happening, plz ask. I am not in a situation to proactievly provide inputs as am not sure about the working.

          Thanks and Regards
          Milash
          • 17. Re: Error Loading XSD documents 11g
            961018
            Dear All,

            I tried with

            alter system set events='31156 trace name context forever, level 0x400' ; just in case :) ... but still the same error.

            we have rasied an SR 3-6240152721 for this issue.

            Mark/Marc,

            Just for my info, from where does XDB gets the xdbconfig.xsd and other xsd docs.Read that xdbconfig.xsd is Oracle XML DB supplied XML schema. For all 10g DB which i checked none of the xdbconfig.xsd file have the prologue. But all the xsd(acl.xsd,xdbconfig.xd,csx.xml.xsd etc) in 11g (the data which i got from dba_xml_schemas )have the below prologue

            *<?xml version="1.0" encoding="WINDOWS-1252"?>*

            From where does the xdbconfig.xsd gets this prologue.

            Thanks and Regards
            Milash
            • 18. Re: Error Loading XSD documents 11g
              Marco Gralike
              958015 wrote:
              *<?xml version="1.0" encoding="WINDOWS-1252"?>*

              From where does the xdbconfig.xsd gets this prologue.
              Are you sure this is (also) not just a client issue.
              Have a look here (OTN XMLDB FAQ via the mainpage info) via the direct link: Conversion UTF-8 -> WINDOWS-1250

              Edited by: Marco Gralike on Sep 25, 2012 10:18 AM
              • 19. Re: Error Loading XSD documents 11g
                odie_63
                *<?xml version="1.0" encoding="WINDOWS-1252"?>*

                From where does the xdbconfig.xsd gets this prologue.
                As Marco said, it's all about your client configuration.
                Your client tool (SQL*Plus?) adds the prolog to reflect the NLS_LANG setting when fetching the XMLType.
                • 20. Re: Error Loading XSD documents 11g
                  961018
                  Hi Marc/Mark,

                  Back after some time :)

                  This is whats happening code - wise

                  int fin_XmlSchemaLoad(char* uri)
                  {
                  xmlerr err = 0;
                  void *schemaCntxt    = NULL;
                  void *xmlCntxtptr    = NULL;
                  schemaCntxt = fin_XmlSchemaCreate(xmlCntxtptr);
                  fin_XmlSchemaClean(schemaCntxt);

                  ub4 sizeBefore = XmlSchemaLoadedList(schemaCntxt,NULL);

                  err = XmlSchemaLoad(schemaCntxt, (oratext )uri, NULL);*

                  ub4 sizeAfter = XmlSchemaLoadedList(schemaCntxt,NULL);

                  if(sizeBefore == sizeAfter)
                  {
                  return 1;
                  }
                  return 0;
                  }

                  void * fin_XmlSchemaCreate(void *xctxPtr)
                  {
                  xmlerr err = 0;
                  xsdctx *sctx;
                  sctx = XmlSchemaCreate(xctxPtr, &err, NULL);
                  return sctx;
                  }
                  err = XmlSchemaLoad(schemaCntxt, (oratext )uri, NULL); this function returns error -15*



                  When i run the xml utilitie of xdk

                  xml errorgivingxsd.xsd it gave below error

                  xml cbr_ed_basetypes_v2.4.0.xsd
                  In line 55 of cbr_ed_basetypes_v2.4.0.xsd:
                  LPX-00217: invalid character 1040 (U+0410)

                  this is that line in xsd
                  *<xs:pattern value="[&#x0020;]*[&#x0021;-&#x007E;&#x0410;-&#x044F;][&#x0020;-&#x007E;&#x0410;-&#x044F;]*">* <xs:annotation>
                  <xs:documentation>Ðàçðåøåííûå ñèìâîëû (ñèìâîëû ñ êîäàìè 32-126, ðóññêèå áóêâû: À-ß à-ÿ, êðîìå áóêâû ¨
                  /¸)</xs:documentation>
                  </xs:annotation>
                  </xs:pattern>

                  locale of client
                  LANG=en_US.utf8
                  LC_COLLATE="EN_US.UTF-8"
                  LC_CTYPE="EN_US.UTF-8"
                  LC_MONETARY="EN_US.UTF-8"
                  LC_NUMERIC="EN_US.UTF-8"
                  LC_TIME="EN_US.UTF-8"
                  LC_MESSAGES="EN_US.UTF-8"
                  LC_ALL=EN_US.UTF-8

                  if i use oraxml command, its showimg parsed susccesfuly, but if i use schema or xml command it gives error
                  oraxml cbr_ed_basetypes_v2.4.0.xsd
                  The input XML file is parsed without errors using partial validation mode


                  schema cbr_ed_basetypes_v2.4.0.xsd
                  In line 55 of cbr_ed_basetypes_v2.4.0.xsd:
                  LPX-00217: invalid character 1040 (U+0410)
                  Parse of cbr_ed_basetypes_v2.4.0.xsd failed, error 217

                  Regards
                  Milash
                  1 2 Previous Next