DSXchange: DataStage and IBM Websphere Data Integration Forum
View next topic
View previous topic
Add To Favorites
Author Message
venkates.dw
Participant



Joined: 22 Dec 2008
Posts: 67

Points: 585

Post Posted: Wed Oct 19, 2011 12:33 pm Reply with quote    Back to top    

DataStage® Release: 8x
Job Type: Parallel
OS: Unix
Hi,

I am using the WTX tool for parsing the XML messages. But for one message we have multiple XSD files. So while running the job am gettng below error.

Error Message: One or more inputs was invalid.

Please help me on this.

Thanks inadvance.
rep
Participant



Joined: 19 Jun 2007
Posts: 82
Location: New York City
Points: 1097

Post Posted: Mon Oct 24, 2011 6:38 am Reply with quote    Back to top    

The error message means that when the map validates the input document against the type tree, it does not fit the defined format. You need set the map trace file on and go through that to find what exactly is causing the error.

At least, this is what is done for non-XML data when this error occurs, but I have used it for XML data also. My experience with XML functions in WTX is limited, and I know a lot of functionality has been added to handle XML validation, functionality I have never used, and from what I’ve read, whether the type tree was built using Xerces or the older method, the results may be different.

Se the trace on and see if that helps. If you’re still have problems then, post back and let me know.
Rate this response:  
Not yet rated
venkates.dw
Participant



Joined: 22 Dec 2008
Posts: 67

Points: 585

Post Posted: Thu Nov 03, 2011 9:22 am Reply with quote    Back to top    

Thanks Rep. I have created the trace file. Please find below the log messgae in Trace file. ( I have used the Xerces option for the Validation)

(Level 0: Offset 0, len 56, comp 1 of 0, #1, DI 00000001:)
Data at offset 0 ('<ns:rbcml xmlns:...') is INVALID data of TYPE
X'0002' (Doc XSD).

(Level 0: Offset 0, len 56, comp 1 of 0, #1, DI 00000002:)
External Parser returned Error:
TYPE X'0002' (Error (-1), "XMLParser: Input XML data is invalid."
SAXParseException, Fatal error [line: 1 column: 57] The schemaLocation attribute does not contain pairs of values.).

INPUT 1 exists, but its type is in error.
End of Validation messages for INPUT CARD 1.
End of Execution messages.

If i use the Classic as validation type am getting the below log message in Trace file.


(Level 4: Offset 16, len 2, comp 1 of 2, #1, DI 00000001:)
Data at offset 16 ('ns') was found to be of TYPE
X'000B' (Prefix XMLS XSD).

(Level 4: Offset 20, len 34, comp 2 of 2, #1, DI 00000002:)
Data at offset 20 ('http://xmlns.rbc...') was found to be of TYPE
X'000C' (Uri XMLS XSD).

(Level 3: Offset 9, len 46, comp 1 of 3, #1, DI 00000003:)
Data at offset 9 (' xmlns:ns="http:...') was found to be of TYPE
X'000A' (Xmlns XMLS XSD).

(Level 4: Offset 55, len 0, comp 1 of 2, #1, DI 00000004:)
Data at offset 55 ('><CR><LF> <ns:header><CR>...') does not match INITIATOR '<WSP>xmlns<IGNORE...>'
of TYPE X'000B' (Prefix XMLS XSD).

(Level 4: Offset 55, len 0, comp 1 of 2, #1, DI 00000004:)
COMPONENT number 1 of TYPE X'000A' (Xmlns XMLS XSD)
is required, but does not exist.

(Level 3: Offset 55, len 0, comp 2 of 3, #1, DI 00000004:)
Data at offset 55 ('><CR><LF> <ns:header><CR>...') does not match INITIATOR '<WSP><IGNORE...><NULL>schemaLocation<OWSP>=<OWSP>'
of TYPE X'000D' (Sl XMLS XSD).

(Level 3: Offset 55, len 0, comp 3 of 3, #1, DI 00000004:)
Data at offset 55 ('><CR><LF> <ns:header><CR>...') does not match INITIATOR '<WSP><IGNORE...><NULL>nil<OWSP>=<OWSP>'
of TYPE X'000E' (Nil XMLS XSD).

(Level 2: Offset 9, len 46, comp 1 of 2, #1, DI 00000004:)
Data at offset 9 (' xmlns:ns="http:...') was found to be of TYPE
X'0008' (AttrList RbcmlMessage Type XSD).

(Level 7: Offset 69, len 0, comp 1 of 2, #1, DI 00000005:)
Data at offset 69 ('><CR><LF> <ns:message...') does not match INITIATOR '<WSP>xmlns<IGNORE...>'
of TYPE X'000B' (Prefix XMLS XSD).

(Level 7: Offset 69, len 0, comp 1 of 2, #1, DI 00000005:)
COMPONENT number 1 of TYPE X'000A' (Xmlns XMLS XSD)
is required, but does not exist.

(Level 6: Offset 69, len 0, comp 2 of 3, #1, DI 00000005:)
Data at offset 69 ('><CR><LF> <ns:message...') does not match INITIATOR '<WSP><IGNORE...><NULL>schemaLocation<OWSP>=<OWSP>'
of TYPE X'000D' (Sl XMLS XSD).

(Level 6: Offset 69, len 0, comp 3 of 3, #1, DI 00000005:)
Data at offset 69 ('><CR><LF> <ns:message...') does not match INITIATOR '<WSP><IGNORE...><NULL>nil<OWSP>=<OWSP>'
of TYPE X'000E' (Nil XMLS XSD).

(Level 5: Offset 69, len 0, comp 1 of 2, #1, DI 00000005:)
Data at offset 69 ('><CR><LF> <ns:message') was found to be of TYPE
X'0019' (AttrList MessageHeader Type XSD).

(Level 10: Offset 87, len 0, comp 1 of 2, #1, DI 00000005:)
Data at offset 87 ('><CR><LF> <ns:id>FEA...') does not match INITIATOR '<WSP>xmlns<IGNORE...>'
of TYPE X'000B' (Prefix XMLS XSD).

(Level 10: Offset 87, len 0, comp 1 of 2, #1, DI 00000005:)
COMPONENT number 1 of TYPE X'000A' (Xmlns XMLS XSD)
is required, but does not exist.

(Level 9: Offset 87, len 0, comp 2 of 3, #1, DI 00000005:)
Data at offset 87 ('><CR><LF> <ns:id>FEA...') does not match INITIATOR '<WSP><IGNORE...><NULL>schemaLocation<OWSP>=<OWSP>'
of TYPE X'000D' (Sl XMLS XSD).

(Level 9: Offset 87, len 0, comp 3 of 3, #1, DI 00000005:)
Data at offset 87 ('><CR><LF> <ns:id>FEA...') does not match INITIATOR '<WSP><IGNORE...><NULL>nil<OWSP>=<OWSP>'
of TYPE X'000E' (Nil XMLS XSD).

(Level 8: Offset 87, len 0, comp 1 of 2, #1, DI 00000005:)
Data at offset 87 ('><CR><LF> <ns:id>FEA') was found to be of TYPE
X'0020' (AttrList MessageId Type XSD).

(Level 9: Offset 100, len 36, comp 1 of 2, #1, DI 00000005:)
Data at offset 100 ('FEA1120E-15F6-46...') was found to be of TYPE
X'0023' (id Comp MessageId Type XSD).

(Level 9: Offset 144, len 0, comp 2 of 2, #1, DI 00000006:)
Data at offset 144 ('<CR><LF> </ns:message...') does not match INITIATOR '<OWSP><<IGNORE...><NULL>sequenceNo<OWSP>>'
of TYPE X'0024' (sequenceNo Comp MessageId Type XSD).

(Level 9: Offset 144, len 0, comp 2 of 2, #1, DI 00000006:)
COMPONENT number 2 of TYPE X'0021' (Seq MessageId Type XSD):
occurrence 1 is optional and does not exist.

(Level 9: Offset 144, len 0, comp 3 of 2, #1, DI 00000006:)
Data at offset 144 ('<CR><LF> </ns:message...') does not match INITIATOR '<OWSP><?'
of TYPE X'0011' (PI NonDocData XSD).

(Level 9: Offset 144, len 0, comp 3 of 2, #1, DI 00000006:)
Data at offset 144 ('<CR><LF> </ns:message...') does not match INITIATOR '<OWSP><!--'
of TYPE X'0012' (Comment NonDocData XSD).

(Level 9: Offset 144, len 0, comp 3 of 2, #1, DI 00000006:)
Data at offset 144 ('<CR><LF> </ns:message...') does not match INITIATOR '<OWSP><![CDATA['
of TYPE X'0013' (CDATA NonDocData XSD).

(Level 9: Offset 144, len 0, comp 3 of 2, #1, DI 00000006:)
Data at offset 144 ('<CR><LF> </ns:message...') failed PARTITIONing for TYPE
X'0010' (NonDocData XSD).

(Level 8: Offset 88, len 56, comp 2 of 2, #1, DI 00000006:)
Data at offset 88 ('<CR><LF> <ns:id>FEA1...') was found to be of TYPE
X'0021' (Seq MessageId Type XSD).

(Level 7: Offset 87, len 63, comp 1 of 1, #1, DI 00000007:)
Data at offset 87 ('><CR><LF> <ns:id>FEA...') was found to be of TYPE
X'001F' (TypeDef MessageId Type XSD).

(Level 7: Offset 150, len 13, comp 2 of 1, #2, DI 00000008:)
TERMINATOR ('Terminator messageId Comp MessageHeader Type XSD') found; has value '<IGNORE...>messageId><NULL><NULL><NULL><NULL><NULL><NULL><NULL><NULL>'.

(Level 7: Offset 150, len 13, comp 2 of 1, #2, DI 00000008:)
Data at offset 150 ('ns:messageId>') was found to be of TYPE
X'0025' (Terminator messageId Comp MessageHeader Type XSD).

(Level 6: Offset 87, len 63, comp 1 of 19, #1, DI 00000009:)
Data at offset 87 ('><CR><LF> <ns:id>FEA...') was found to be of TYPE
X'001D' (ElemDecl messageId Comp MessageHeader Type XSD).

(Level 6: Offset 163, len 0, comp 2 of 19, #1, DI 0000000A:)
Data at offset 163 ('<CR><LF> <ns:messageA...') does not match INITIATOR '<OWSP><<IGNORE...><NULL>correlationId<OWSP>>'
of TYPE X'0026' (correlationId Comp MessageHeader Type XSD).

(Level 6: Offset 163, len 0, comp 2 of 19, #1, DI 0000000A:)
COMPONENT number 2 of TYPE X'001A' (Seq MessageHeader Type XSD):
occurrence 1 is optional and does not exist.

(Level 10: Offset 188, len 0, comp 1 of 2, #1, DI 0000000A:)
Data at offset 188 ('>NOTIFY</ns:mess...') does not match INITIATOR '<WSP>xmlns<IGNORE...>'
of TYPE X'000B' (Prefix XMLS XSD).

(Level 10: Offset 188, len 0, comp 1 of 2, #1, DI 0000000A:)
COMPONENT number 1 of TYPE X'000A' (Xmlns XMLS XSD)
is required, but does not exist.

(Level 9: Offset 188, len 0, comp 2 of 3, #1, DI 0000000A:)
Data at offset 188 ('>NOTIFY</ns:mess...') does not match INITIATOR '<WSP><IGNORE...><NULL>schemaLocation<OWSP>=<OWSP>'
of TYPE X'000D' (Sl XMLS XSD).

(Level 9: Offset 188, len 0, comp 3 of 3, #1, DI 0000000A:)
Data at offset 188 ('>NOTIFY</ns:mess...') does not match INITIATOR '<WSP><IGNORE...><NULL>nil<OWSP>=<OWSP>'
of TYPE X'000E' (Nil XMLS XSD).

(Level 8: Offset 188, len 0, comp 1 of 2, #1, DI 0000000A:)
Data at offset 188 ('>NOTIFY</ns:mess') was found to be of TYPE
X'002B' (AttrList MessageActionEnum Type XSD).

(Level 8: Offset 189, len 6, comp 2 of 2, #1, DI 0000000A:)
Data at offset 189 ('NOTIFY') was found to be of TYPE
X'002C' (Value MessageActionEnum Type XSD).

(Level 7: Offset 188, len 9, comp 1 of 1, #1, DI 0000000B:)
Data at offset 188 ('>NOTIFY</') was found to be of TYPE
X'002A' (TypeDef MessageActionEnum Type XSD).

(Level 7: Offset 197, len 21, comp 2 of 1, #2, DI 0000000C:)
TERMINATOR ('Terminator messageActionType Comp MessageHeader Type XSD') found; has value '<IGNORE...>messageActionType><NULL><NULL><NULL><NULL><NULL><NULL><NULL><NULL>'.

(Level 7: Offset 197, len 21, comp 2 of 1, #2, DI 0000000C:)
Data at offset 197 ('ns:messageAction...') was found to be of TYPE
X'002D' (Terminator messageActionType Comp MessageHeader Type XSD).

(Level 6: Offset 188, len 9, comp 3 of 19, #1, DI 0000000D:)
Data at offset 188 ('>NOTIFY</') was found to be of TYPE
X'0028' (ElemDecl messageActionType Comp MessageHeader Type XSD).

(Level 6: Offset 249, len 14, comp 4 of 19, #1, DI 0000000E:)
Data at offset 249 ('REFERENCE_DATA') was found to be of TYPE
X'002E' (messagePayloadCategory Comp MessageHeader Type XSD).

(Level 6: Offset 318, len 12, comp 5 of 19, #1, DI 0000000F:)
Data at offset 318 ('POSITION_EOD') was found to be of TYPE
X'002F' (messagePayloadType Comp MessageHeader Type XSD).

(Level 6: Offset 354, len 0, comp 6 of 19, #1, DI 00000010:)
Data at offset 354 ('<CR><LF> <ns:sourceSy...') does not match INITIATOR '<OWSP><<IGNORE...><NULL>messagePayloadSubType<OWSP>>'
of TYPE X'0030' (messagePayloadSubType Comp MessageHeader Type XSD).

(Level 6: Offset 354, len 0, comp 6 of 19, #1, DI 00000010:)
COMPONENT number 6 of TYPE X'001A' (Seq MessageHeader Type XSD):
occurrence 1 is optional and does not exist.

(Level 10: Offset 374, len 0, comp 1 of 2, #1, DI 00000010:)
Data at offset 374 ('>OTIS</ns:source...') does not match INITIATOR '<WSP>xmlns<IGNORE...>'
of TYPE X'000B' (Prefix XMLS XSD).

(Level 10: Offset 374, len 0, comp 1 of 2, #1, DI 00000010:)
COMPONENT number 1 of TYPE X'000A' (Xmlns XMLS XSD)
is required, but does not exist.

(Level 9: Offset 374, len 0, comp 2 of 3, #1, DI 00000010:)
Data at offset 374 ('>OTIS</ns:source...') does not match INITIATOR '<WSP><IGNORE...><NULL>schemaLocation<OWSP>=<OWSP>'
of TYPE X'000D' (Sl XMLS XSD).

(Level 9: Offset 374, len 0, comp 3 of 3, #1, DI 00000010:)
Data at offset 374 ('>OTIS</ns:source...') does not match INITIATOR '<WSP><IGNORE...><NULL>nil<OWSP>=<OWSP>'
of TYPE X'000E' (Nil XMLS XSD).

(Level 8: Offset 374, len 0, comp 1 of 2, #1, DI 00000010:)
Data at offset 374 ('>OTIS</ns:source') was found to be of TYPE
X'0035' (AttrList SystemEnum Type XSD).

(Level 8: Offset 375, len 4, comp 2 of 2, #1, DI 00000010:)
Data at offset 375 ('OTIS') was found to be of TYPE
X'0036' (Value SystemEnum Type XSD).

(Level 7: Offset 374, len 7, comp 1 of 1, #1, DI 00000011:)
Data at offset 374 ('>OTIS</') was found to be of TYPE
X'0034' (TypeDef SystemEnum Type XSD).

(Level 7: Offset 381, len 16, comp 2 of 1, #2, DI 00000012:)
TERMINATOR ('Terminator sourceSystem Comp MessageHeader Type XSD') found; has value '<IGNORE...>sourceSystem><NULL><NULL><NULL><NULL><NULL><NULL><NULL><NULL>'.

(Level 7: Offset 381, len 16, comp 2 of 1, #2, DI 00000012:)
Data at offset 381 ('ns:sourceSystem>') was found to be of TYPE
X'0037' (Terminator sourceSystem Comp MessageHeader Type XSD).

(Level 6: Offset 374, len 7, comp 7 of 19, #1, DI 00000013:)
Data at offset 374 ('>OTIS</') was found to be of TYPE
X'0032' (ElemDecl sourceSystem Comp MessageHeader Type XSD).

(Level 10: Offset 426, len 0, comp 1 of 2, #1, DI 00000014:)
Data at offset 426 ('><CR><LF> <ns:name>I...') does not match INITIATOR '<WSP>xmlns<IGNORE...>'
of TYPE X'000B' (Prefix XMLS XSD).

(Level 10: Offset 426, len 0, comp 1 of 2, #1, DI 00000014:)
COMPONENT number 1 of TYPE X'000A' (Xmlns XMLS XSD)
is required, but does not exist.

(Level 9: Offset 426, len 0, comp 2 of 3, #1, DI 00000014:)
Data at offset 426 ('><CR><LF> <ns:name>I...') does not match INITIATOR '<WSP><IGNORE...><NULL>schemaLocation<OWSP>=<OWSP>'
of TYPE X'000D' (Sl XMLS XSD).

(Level 9: Offset 426, len 0, comp 3 of 3, #1, DI 00000014:)
Data at offset 426 ('><CR><LF> <ns:name>I...') does not match INITIATOR '<WSP><IGNORE...><NULL>nil<OWSP>=<OWSP>'
of TYPE X'000E' (Nil XMLS XSD).

(Level 8: Offset 426, len 0, comp 1 of 2, #1, DI 00000014:)
Data at offset 426 ('><CR><LF> <ns:name>I') was found to be of TYPE
X'003C' (AttrList SecondarySourceSystem Type XSD).

(Level 9: Offset 441, len 11, comp 1 of 2, #1, DI 00000014:)
Data at offset 441 ('IPV_MISTRAL') was found to be of TYPE
X'003F' (name Comp SecondarySourceSystem Type XSD).

(Level 9: Offset 476, len 8, comp 2 of 2, #1, DI 00000015:)
Data at offset 476 ('POSITION') was found to be of TYPE
X'0040' (type Comp SecondarySourceSystem Type XSD).

(Level 9: Offset 494, len 0, comp 3 of 2, #2, DI 00000016:)
Data at offset 494 ('<CR><LF> </ns:seconda...') does not match INITIATOR '<OWSP><?'
of TYPE X'0011' (PI NonDocData XSD).

(Level 9: Offset 494, len 0, comp 3 of 2, #2, DI 00000016:)
Data at offset 494 ('<CR><LF> </ns:seconda...') does not match INITIATOR '<OWSP><!--'
of TYPE X'0012' (Comment NonDocData XSD).

(Level 9: Offset 494, len 0, comp 3 of 2, #2, DI 00000016:)
Data at offset 494 ('<CR><LF> </ns:seconda...') does not match INITIATOR '<OWSP><![CDATA['
of TYPE X'0013' (CDATA NonDocData XSD).

(Level 9: Offset 494, len 0, comp 3 of 2, #2, DI 00000016:)
Data at offset 494 ('<CR><LF> </ns:seconda...') failed PARTITIONing for TYPE
X'0010' (NonDocData XSD).

(Level 8: Offset 427, len 67, comp 2 of 2, #1, DI 00000016:)
Data at offset 427 ('<CR><LF> <ns:name>IP...') was found to be of TYPE
X'003D' (Seq SecondarySourceSystem Type XSD).

(Level 7: Offset 426, len 74, comp 1 of 1, #1, DI 00000017:)
Data at offset 426 ('><CR><LF> <ns:name>I...') was found to be of TYPE
X'003B' (TypeDef SecondarySourceSystem Type XSD).

(Level 7: Offset 500, len 25, comp 2 of 1, #2, DI 00000018:)
TERMINATOR ('Terminator secondarySourceSystem Comp MessageHeader Type XSD') found; has value '<IGNORE...>secondarySourceSystem><NULL><NULL><NULL><NULL><NULL><NULL><NULL><NULL>'.

(Level 7: Offset 500, len 25, comp 2 of 1, #2, DI 00000018:)
Data at offset 500 ('ns:secondarySour...') was found to be of TYPE
X'0041' (Terminator secondarySourceSystem Comp MessageHeader Type XSD).

(Level 6: Offset 426, len 74, comp 8 of 19, #1, DI 00000019:)
Data at offset 426 ('><CR><LF> <ns:name>I...') was found to be of TYPE
X'0039' (ElemDecl secondarySourceSystem Comp MessageHeader Type XSD).

(Level 6: Offset 525, len 0, comp 8 of 19, #2, DI 0000001A:)
Data at offset 525 ('<CR><LF> <ns:creation...') does not match INITIATOR '<OWSP><<IGNORE...><NULL>secondarySourceSystem'
of TYPE X'0039' (ElemDecl secondarySourceSystem Comp MessageHeader Type XSD).

(Level 6: Offset 525, len 0, comp 8 of 19, #2, DI 0000001A:)
COMPONENT number 8 of TYPE X'001A' (Seq MessageHeader Type XSD):
occurrence 2 is optional and does not exist.

(Level 6: Offset 551, len 29, comp 9 of 19, #1, DI 0000001A:)
Data at offset 551 ('2011-06-06T16:25...') was found to be of TYPE
X'0042' (creationTimestamp Comp MessageHeader Type XSD).

(Level 6: Offset 618, len 34, comp 10 of 19, #1, DI 0000001B:)
Data at offset 618 ('http://xmlns.rbc...') was found to be of TYPE
X'0043' (schema Comp MessageHeader Type XSD).

(Level 6: Offset 686, len 1, comp 11 of 19, #1, DI 0000001C:)
Data at offset 686 ('4') was found to be of TYPE
X'0044' (schemaVersion Comp MessageHeader Type XSD).

(Level 6: Offset 731, len 1, comp 12 of 19, #1, DI 0000001D:)
Data at offset 731 ('3') was found to be of TYPE
X'0045' (schemaSubVersion Comp MessageHeader Type XSD).

(Level 6: Offset 769, len 4, comp 13 of 19, #1, DI 0000001E:)
Data at offset 769 ('OTIS') was found to be of TYPE
X'0046' (sentBy Comp MessageHeader Type XSD).

(Level 6: Offset 785, len 0, comp 14 of 19, #1, DI 0000001F:)
Data at offset 785 ('<CR><LF> </ns:header><CR>...') does not match INITIATOR '<OWSP><<IGNORE...><NULL>conversationId'
of TYPE X'0048' (ElemDecl conversationId Comp MessageHeader Type XSD).

(Level 6: Offset 785, len 0, comp 14 of 19, #1, DI 0000001F:)
COMPONENT number 14 of TYPE X'001A' (Seq MessageHeader Type XSD):
occurrence 1 is optional and does not exist.

(Level 6: Offset 785, len 0, comp 15 of 19, #1, DI 0000001F:)
Data at offset 785 ('<CR><LF> </ns:header><CR>...') does not match INITIATOR '<OWSP><<IGNORE...><NULL>copyTo<OWSP>>'
of TYPE X'004E' (copyTo Comp MessageHeader Type XSD).

(Level 6: Offset 785, len 0, comp 15 of 19, #1, DI 0000001F:)
COMPONENT number 15 of TYPE X'001A' (Seq MessageHeader Type XSD):
occurrence 1 is optional and does not exist.

(Level 6: Offset 785, len 0, comp 16 of 19, #1, DI 0000001F:)
Data at offset 785 ('<CR><LF> </ns:header><CR>...') does not match INITIATOR '<OWSP><<IGNORE...><NULL>sendTo<OWSP>>'
of TYPE X'004F' (sendTo Comp MessageHeader Type XSD).

(Level 6: Offset 785, len 0, comp 16 of 19, #1, DI 0000001F:)
COMPONENT number 16 of TYPE X'001A' (Seq MessageHeader Type XSD):
occurrence 1 is optional and does not exist.

(Level 6: Offset 785, len 0, comp 17 of 19, #1, DI 0000001F:)
Data at offset 785 ('<CR><LF> </ns:header><CR>...') does not match INITIATOR '<OWSP><<IGNORE...><NULL>expiryTimestamp<OWSP>>'
of TYPE X'0050' (expiryTimestamp Comp MessageHeader Type XSD).

(Level 6: Offset 785, len 0, comp 17 of 19, #1, DI 0000001F:)
COMPONENT number 17 of TYPE X'001A' (Seq MessageHeader Type XSD):
occurrence 1 is optional and does not exist.

(Level 6: Offset 785, len 0, comp 18 of 19, #1, DI 0000001F:)
Data at offset 785 ('<CR><LF> </ns:header><CR>...') does not match INITIATOR '<OWSP><<IGNORE...><NULL>InReplyTo'
of TYPE X'0052' (ElemDecl InReplyTo Comp MessageHeader Type XSD).

(Level 6: Offset 785, len 0, comp 18 of 19, #1, DI 0000001F:)
COMPONENT number 18 of TYPE X'001A' (Seq MessageHeader Type XSD):
occurrence 1 is optional and does not exist.

(Level 6: Offset 785, len 0, comp 19 of 19, #1, DI 0000001F:)
Data at offset 785 ('<CR><LF> </ns:header><CR>...') does not match INITIATOR '<OWSP><<IGNORE...><NULL>acknowledgement'
of TYPE X'005F' (ElemDecl acknowledgement Comp MessageHeader Type XSD).

(Level 6: Offset 785, len 0, comp 19 of 19, #1, DI 0000001F:)
COMPONENT number 19 of TYPE X'001A' (Seq MessageHeader Type XSD):
occurrence 1 is optional and does not exist.

(Level 6: Offset 785, len 0, comp 20 of 19, #1, DI 0000001F:)
Data at offset 785 ('<CR><LF> </ns:header><CR>...') does not match INITIATOR '<OWSP><?'
of TYPE X'0011' (PI NonDocData XSD).

(Level 6: Offset 785, len 0, comp 20 of 19, #1, DI 0000001F:)
Data at offset 785 ('<CR><LF> </ns:header><CR>...') does not match INITIATOR '<OWSP><!--'
of TYPE X'0012' (Comment NonDocData XSD).

(Level 6: Offset 785, len 0, comp 20 of 19, #1, DI 0000001F:)
Data at offset 785 ('<CR><LF> </ns:header><CR>...') does not match INITIATOR '<OWSP><![CDATA['
of TYPE X'0013' (CDATA NonDocData XSD).

(Level 6: Offset 785, len 0, comp 20 of 19, #1, DI 0000001F:)
Data at offset 785 ('<CR><LF> </ns:header><CR>...') failed PARTITIONing for TYPE
X'0010' (NonDocData XSD).

(Level 5: Offset 70, len 715, comp 2 of 2, #1, DI 0000001F:)
Data at offset 70 ('<CR><LF> <ns:messageI...') was found to be of TYPE
X'001A' (Seq MessageHeader Type XSD).

(Level 4: Offset 69, len 721, comp 1 of 1, #1, DI 00000020:)
Data at offset 69 ('><CR><LF> <ns:message...') was found to be of TYPE
X'0018' (TypeDef MessageHeader Type XSD).

(Level 4: Offset 790, len 10, comp 2 of 1, #2, DI 00000021:)
TERMINATOR ('Terminator header Comp RbcmlMessage Type XSD') found; has value '<IGNORE...>header><NULL><NULL><NULL><NULL><NULL><NULL><NULL><NULL>'.

(Level 4: Offset 790, len 10, comp 2 of 1, #2, DI 00000021:)
Data at offset 790 ('ns:header>') was found to be of TYPE
X'0095' (Terminator header Comp RbcmlMessage Type XSD).

(Level 3: Offset 69, len 721, comp 1 of 3, #1, DI 00000022:)
Data at offset 69 ('><CR><LF> <ns:message...') was found to be of TYPE
X'0016' (ElemDecl header Comp RbcmlMessage Type XSD).

(Level 4: Offset 815, len 0, comp 1 of 1, #1, DI 00000023:)
Data at offset 815 ('<CR><LF> <ns:position...') does not match INITIATOR '<OWSP><any<OWSP>>'
of TYPE X'0098' (anyElem payload Comp RbcmlMessage Type XSD).

(Level 4: Offset 815, len 0, comp 1 of 1, #1, DI 00000023:)
Data at offset 815 ('<CR><LF> <ns:position...') does not match INITIATOR '<OWSP><?'
of TYPE X'0011' (PI NonDocData XSD).

(Level 4: Offset 815, len 0, comp 1 of 1, #1, DI 00000023:)
Data at offset 815 ('<CR><LF> <ns:position...') does not match INITIATOR '<OWSP><!--'
of TYPE X'0012' (Comment NonDocData XSD).

(Level 4: Offset 815, len 0, comp 1 of 1, #1, DI 00000023:)
Data at offset 815 ('<CR><LF> <ns:position...') does not match INITIATOR '<OWSP><![CDATA['
of TYPE X'0013' (CDATA NonDocData XSD).

(Level 4: Offset 815, len 0, comp 1 of 1, #1, DI 00000023:)
Data at offset 815 ('<CR><LF> <ns:position...') failed PARTITIONing for TYPE
X'0010' (NonDocData XSD).

(Level 4: Offset 815, len 0, comp 1 of 1, #1, DI 00000023:)
COMPONENT number 1 of TYPE X'0097' (ElemDecl payload Comp RbcmlMessage Type XSD)
is required, but does not exist.

(Level 3: Offset 800, len 0, comp 2 of 3, #1, DI 00000023:)
Data at offset 800 ('<CR><LF> <ns:payload><CR>...') does not match INITIATOR '<OWSP><?'
of TYPE X'0011' (PI NonDocData XSD).

(Level 3: Offset 800, len 0, comp 2 of 3, #1, DI 00000023:)
Data at offset 800 ('<CR><LF> <ns:payload><CR>...') does not match INITIATOR '<OWSP><!--'
of TYPE X'0012' (Comment NonDocData XSD).

(Level 3: Offset 800, len 0, comp 2 of 3, #1, DI 00000023:)
Data at offset 800 ('<CR><LF> <ns:payload><CR>...') does not match INITIATOR '<OWSP><![CDATA['
of TYPE X'0013' (CDATA NonDocData XSD).

(Level 3: Offset 800, len 0, comp 2 of 3, #1, DI 00000023:)
Data at offset 800 ('<CR><LF> <ns:payload><CR>...') failed PARTITIONing for TYPE
X'0010' (NonDocData XSD).

(Level 3: Offset 800, len 0, comp 2 of 3, #1, DI 00000023:)
COMPONENT number 2 of TYPE X'000F' (Seq RbcmlMessage Type XSD)
is required, but does not exist.

(Level 2: Offset 55, len 0, comp 2 of 2, #1, DI 00000005:)
COMPONENT number 2 of TYPE X'0007' (TypeDef RbcmlMessage Type XSD)
is required, but does not exist.

(Level 1: Offset 9, len 0, comp 1 of 1, #1, DI 00000001:)
COMPONENT number 1 of TYPE X'0004' (ElemDecl rbcml Element XSD)
is required, but does not exist.

(Level 1: Offset 9, len 0, comp 1 of 1, #1, DI 00000001:)
Data at offset 9 (' xmlns:ns="http:') is INVALID data of TYPE
X'0007' (TypeDef RbcmlMessage Type XSD).

(Level 0: Offset 0, len 0, comp 1 of 0, #1, DI 00000001:)
Data at offset 0 ('<ns:rbcml xmlns:') is INVALID data of TYPE
X'0004' (ElemDecl rbcml Element XSD).

INPUT 1 exists, but its type is in error.
End of Validation messages for INPUT CARD 1.
End of Execution messages.

Please let me know how do i need resolve this issue..
Rate this response:  
Not yet rated
rep
Participant



Joined: 19 Jun 2007
Posts: 82
Location: New York City
Points: 1097

Post Posted: Wed Nov 09, 2011 1:09 pm Reply with quote    Back to top    

venkates.dw, some errors in the trace file are easy to find, such as if the input file had text in a numeric field. You open the trace file and do a search on INVALID, and it brings you right to the field and data in error.

When I get a similar error in a big file and can not identify it quickly, what I do, as I’m sure anyone who uses WTX a lot is; you open the file that is giving you problems, you open the trace file, and you open the type tree….well, actually, I don’t open the type tree, what I do is open the map designer and look at the type tree in the input card. For me it is a bit easier then viewing it in the Type Tree Designer.

Once you have all three open for viewing, go through the trace file field by field, trying to understand how the map is validating the data. It can be a tedious chore, but if you plan on using WTX yourself, and really using it, knowing how to read the trace file will be of utmost importance. It took me years, literally, to be able to read the trace file as easy I can now to find errors, but I still need the data and the type tree to do so.

So what needs to be done is; open all three, and even if it takes a lot of time, go through it field by field. See the value in the trace file the map is validating, find the value in the input data, and match it to the type tree. It is much, much easier with flat files then it is with XML also, but if you plan on becoming an expert in WTX, you will need to know how to do this. If you are not familiar with viewing trace files yet, you may want to practice on a map that uses flat file data, not XML. Once you get the hang of it, then move on to XML.

Looking at the trace file you posted, it’s easy to see that it would be impossible for me to identify the problem by just using it. I would need the type tree and the input data. I may be willing to look at it this one time if you post them if I have time, and if you are allowed to post the data on this site for the entire world to see.
Rate this response:  
Not yet rated
jvmerc
Participant



Joined: 02 Dec 2003
Posts: 94

Points: 812

Post Posted: Wed Nov 16, 2011 3:25 pm Reply with quote    Back to top    

Agree, you need to compare the data to the type tree. The interesting thing is it that the first one tells you the issue is a offset 0 while the second one tells you the offsets with issues are at 0 and 9.

Looking at your trace file a little closer you'll notice the map seems to do fine until it was working on 'anyElem payload Comp RbcmlMessage Type XSD' or offset 815. This would seem to indicate the problem has something to do with a terminator, delimiter or data that occurred somewhere around the element found at offset 815. Everything else was good til then. Once it found the problem it started back out analysis and indicated the 'invalid' at an earlier data point. How specific the trace gets is partially due to the structure of the type tree.
Rate this response:  
Not yet rated
Display posts from previous:       

Add To Favorites
View next topic
View previous topic
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum



Powered by phpBB © 2001, 2002 phpBB Group
Theme & Graphics by Daz :: Portal by Smartor
All times are GMT - 6 Hours