TroubleShooting - POXMLP - PO_DISPATCH Fails With XML File Could Not Be Opened For Mode A As A File Of Charset UTF -8
(Doc ID 2570056.1)
Last updated on SEPTEMBER 07, 2021
Applies to:PeopleSoft Enterprise SCM Purchasing - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
POXMLP - PO_DISPATCH fails with XML file could not be opened for mode a as a file of charset UTF -8
On average, about once a week the POXMLP PO_DISPATCH BI Publisher fails with the following message:
d:\fn92\temp\PODISPATCH_PRN_ENG__1510141.xml could not be opened for mode a as a file of charset UTF -8 (2,668). PO_DISPATCH.PO_XMLP_XMLFile.OnExecute Name:populateXMLFile PCPC:61391 Statement:836 Called from:PO_DISPATCH.PO_Dispatch.OnExecute Name:writeXMLFile Statement:21 Called from:PO_DISPATCH.PO_Dispatch.OnExecute Name:XMLPdispatch Statement:48 Called from:PO_DISPATCH.PO_Dispatch_Print.OnExecute Name:dispatch Statement:30 Called from:PO_DISPATCH.EMAIL.GBL.default.1900-01-01.Step01.OnExecute
This BI Publisher is contained within a scheduled job with PO_AUTO_SRC, a query, POXMLP PO_DISPATCH, another query, and IN_PUB_MSG processes. The job runs to success most days...at least 4 out of 5 days a week. The day it fails is not consistent, therefore, it's not as if there is something else on schedule in conflict with this job, the database, or server. When the process in the job fails, most times we can restart the process and it runs successfully. Occasionally, it fails again trying to insert duplicate rows into a temp table. If we clear the temp table, the process runs to success.
The error appears to be that the XML file can't be opened for read/write. Since these processes could potentially run on 3 different servers, We have set the Server option to force each step to run on one server. We hoped this would eliminate a potential problem where the process was trying to open a file on one server, but the file actually resided on one of the other two servers. The change to force server did not fix this issue.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document