BI Publisher (MOSC)

MOSC Banner

Howcan I identify the problematic POID that causes the error for a corrupt XML?

edited Nov 12, 2013 6:01AM in BI Publisher (MOSC) 14 commentsAnswered
In our implementation BRM sends invoices in the range of a given POID to BI Publisher. If there is a corrupted or a broken XML format, BIP throws an exception like below but we can not understand for which POID that exception is thrown. Can anybody direct me to find that problematic POID?

[2013-09-27T12:05:23.391+00:00] [bi_server1] [WARNING] [] [oracle.xdo] [tid: 33] [userId: BISystemUser] [ecid: 0000K5U8aj99d_g5lFt1iZ1IHIU2000002,1:27239] [APP: bipublisher#11.1.1] !!!!!!! BurstingDataProcessor.process :: Data processor failed::[INSTANCE_JOB_ID=48379]data file has invalid xml format::/tmp/48379/newcob3-brm01.1377766585352/t8/bipM3icn0NTwg3058362266888255174.tmp::oracle.xml.parser.v2.XMLParseException: End tag does not match start tag 'invoice'.[[

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

EBS BI Publisher Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center