DSXchange

Hi All

I am trying to read the xml file

seq-> XMlinput -> dataset

seqfile
format i have mentioned record type implicit
delimeter none.

i am getting the error .can any body help what its regarding .

XML input document parsing failed. Reason: Xalan fatal error (publicId: , systemId: , line: 15, column: 4): Invalid character (Unicode: 0x0)

thanks

First correct your job design, particularly how you read from the source.

You need to validate it, get your hands on a tool (many are free) that will do that validation of how "well formed" it is. Do you have an xsd for it?

The first simple test is to make sure you can just open it in IE.

Also, it might be a code set issue also [you will need to do some research on the settings that are available in the header of an xml document as to things like UTF-8 or UTF-16, etc.].

Ernie

eostic wrote:The first simple test is to make sure you can just open it in IE.

Also, it might be a code set issue also [you will need to do some research on the settings that are available in the header of an xml document as to things like UTF-8 or UTF-16, etc.].

Ernie

Hi ,

after running the job i am getting follwing warnings:

ML input document parsing failed. Reason: Xalan fatal error (publicId: , systemId: , line: 1, column: 513): Invalid character (Unicode: 0x0)

and for the rest of the records I got these following errors

XML input document parsing failed. Reason: Xalan fatal error (publicId: , systemId: , line: 1, column: 3): There are more end tags than start tags


XML_Input_readTag: XML input document parsing failed. Reason: Xalan fatal error (publicId: , systemId: , line: 1, column: 1): Invalid document structure

Can you please help me what might be the problem.is that the import problem or xml problem .

please suggest me.

thanks

As noted, at the very least your XML document seems to be invalid. Get a corrected one from the source and try again. Did you open it in IE?

chulett wrote:As noted, at the very least your XML document seems to be invalid. Get a corrected one from the source and try again. Did you open it in IE? ...

Hi
I opend with IE it is opend correctly.

thanks

OK... teeth pulling time... let's start over.

What does your job design look like now? Did you get rid of the Sequential File stage as noted in the blog entry I linked you to? If not, do so now and then try it again. If it continues to fail, post all of these same details again, down to the settings / options used in the XMLInput stage.

chulett wrote:OK... teeth pulling time... let's start over.

What does your job design look like now? Did you get rid of the Sequential File stage as noted in the blog entry I linked you to? If not, do so now and then try it again. If it continues to fail, post all of these same details again, down to the settings / options used in the XMLInput stage.

please find the xml and xpath.please let me know is there any mistake in the xml or in my xpath or any suggestion

/ns1:ACORD/ns1:InsuranceSvcRs/ns1:AgencyHubInfo/ns1:NationwideInfos/ns1:NationwideInfo/ns1:Addr/ns1:Addr1/text()
/ns1:ACORD/ns1:InsuranceSvcRs/ns1:AgencyHubInfo/ns1:NationwideInfos/ns1:NationwideInfo/ns1:Addr/ns1:City/text()
/ns1:ACORD/ns1:InsuranceSvcRs/ns1:AgencyHubInfo/ns1:NationwideInfos/ns1:NationwideInfo/ns1:Addr/ns1:StateProv/text()
/ns1:ACORD/ns1:InsuranceSvcRs/ns1:AgencyHubInfo/ns1:NationwideInfos/ns1:NationwideInfo/ns1:Addr/ns1:PostalCode/text()
/ns1:ACORD/ns1:InsuranceSvcRs/ns1:AgencyHubInfo/ns1:NationwideInfos/ns1:NationwideInfo/ns1:Addr/ns1:CountryCd/text()


XML


<ACORD xmlns="http://www.ACORD.org/standards/PC_Suret ... 1.8.0/xml/">
<InsuranceSvcRs>
<AgencyHubInfo>
<NationwideInfos>
<NationwideInfo>
<Addr>
<Addr1> 99 TROY ROAD </Addr1>
<City> EAST GREENBUSH </City>
<StateProv> NY </StateProv>
<PostalCode> 12061 </PostalCode>
<CountryCd> US </CountryCd>
</Addr>
</NationwideInfo>
</NationwideInfos>
</AgencyHubInfo>
</InsuranceSvcRs>
</ACORD>

when i try to read this xml info i am getting the follwing warnings

XML_Input_6,0: Warning: sample.XML_Input_6: XML input document parsing failed. Reason: Xalan fatal error (publicId: , systemId: , line: 11, column: 20): Invalid character (Unicode: 0x0)

XML_Input_6,0: Warning: sample.XML_Input_6: XML input document parsing failed. Reason: Xalan fatal error (publicId: , systemId: , line: 2, column: 31): Expected comment or processing instruction

and i have given namespaces through load also

please suggest me how can i proceed further.


in xml tags i have mentioned spaces is that ok or wrong,because i am able to read the data for diferent data.


thanks

just guessing at this point, but the next suggestion is to start doing some unicode research for info that might need to be in the header....right now it appears that there is no header, but one might be needed based on the characters that may exist deep in your document. It looks like an ACORD insurance document....What country is it from?

Ernie

Please, for goodness sakes, answer my dang questions regarding your job design. If your design is wrong, we could be chasing wild geese that a simple redesign would solve.

chulett wrote:Please, for goodness sakes, answer my dang questions regarding your job design. If your design is wrong, we could be chasing wild geese that a simple redesign would solve.

Hi

The problem is solved .

Reason is seq stg is not reading the full xml file properly .so, we used path instaed of xml option in xml stg. now its working fine.

thanks for ur contribution criage and Ernie

Please mark this thread as Resolved using the green button at the top of this page.

Let this be a lesson to anyone who reads this thread in the future.......DON'T use the Sequential Stage in Parallel Jobs to read XML from disk. It's simply too unpredictable. Variable length strings, stray carriage returns and other xml "noise" characters etc can cause the Sequential Stage to mis-read your file. Use Folder on Server Jobs or External Source for EE. Period. MQ/Oracle/DB2, etc. with XML content are another story.

Thanks Craig, for getting us all back on track with the topology.

Ernie