XML Publisher Reports Fail with java.io.FileNotFoundException on Temp Directory After Cloning
(Doc ID 1189764.1)
Last updated on MAY 19, 2023
Applies to:
BI Publisher (formerly XML Publisher) - Version 11.5 and laterOracle Payments - Version 12.2.7 to 12.2.7 [Release 12.2]
Information in this document applies to any platform.
Symptoms
After cloning it is not possible to view the XML output for XML Publisher reports resulting in the following error:
Template code: XLAACCPB01
Template app: XLA
Language: en
Territory: US
Output type: RTF
java.io.FileNotFoundException : /usr/tmp/XXXXXX/xxffffxxxxyyyy.fo (No such file or directory)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
at oracle.apps.xdo.common.tmp.TmpFile.createTmpFileJDK118(TmpFile.java:146)
at oracle.apps.xdo.common.tmp.TmpFile.createTmpFile(TmpFile.java:113)
at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:987)
at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:212)
at oracle.apps.xdo.template.FOProcessor.createFO(FOProcessor.java:1659)
at oracle.apps.xdo.template.FOProcessor.generate(FOProcessor.java:969)
at oracle.apps.xdo.oa.schema.server.TemplateHelper.runProcessTemplate(TemplateHelper.java:5926)
at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:3458)
at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:3547)
at oracle.apps.fnd.cp.opp.XMLPublisherProcessor.process(XMLPublisherProcessor.java:259)
at oracle.apps.fnd.cp.opp.OPPRequestThread.run(OPPRequestThread.java:172)
Template app: XLA
Language: en
Territory: US
Output type: RTF
java.io.FileNotFoundException : /usr/tmp/XXXXXX/xxffffxxxxyyyy.fo (No such file or directory)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
at oracle.apps.xdo.common.tmp.TmpFile.createTmpFileJDK118(TmpFile.java:146)
at oracle.apps.xdo.common.tmp.TmpFile.createTmpFile(TmpFile.java:113)
at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:987)
at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:212)
at oracle.apps.xdo.template.FOProcessor.createFO(FOProcessor.java:1659)
at oracle.apps.xdo.template.FOProcessor.generate(FOProcessor.java:969)
at oracle.apps.xdo.oa.schema.server.TemplateHelper.runProcessTemplate(TemplateHelper.java:5926)
at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:3458)
at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:3547)
at oracle.apps.fnd.cp.opp.XMLPublisherProcessor.process(XMLPublisherProcessor.java:259)
at oracle.apps.fnd.cp.opp.OPPRequestThread.run(OPPRequestThread.java:172)
The issue can be reproduced at will with the following steps:
1. Clone an environment.
2. Run XML Publisher.
3. View the Output.
4. Output only displays the raw xml tags.
Due to this issue, users cannot view XML Output on the cloned environment
Cause
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
Symptoms |
Cause |
Solution |
References |