Bursting Fails With File Is Not Accessible From Node/Machine

BI Publisher (formerly XML Publisher) – Version 12.0 to 12.2 [Release 12.0 to 12.2]
Information in this document applies to any platform.


Issue:

Bursting program failing with the following message:
null output =/app/oracle/inst/apps/EBSDEV02_ebsdevapp02/logs/appl/conc/out/o9381314.out
File /app/oracle/inst/apps/logs/appl/conc/out/o9381313.out is not accessible from node/machine
–Exception
File /app/oracle/inst/apps/logs/appl/conc/out/o9381313.out is not accessible from node/machine .
oracle.apps.fnd.cp.request.FileAccessException: File /app/oracle/inst/apps/logs/appl/conc/out/o9381313.out is not accessible from node/machine .
at oracle.apps.fnd.cp.request.RemoteFile.getFile(RemoteFile.java:440)
at oracle.apps.xdo.oa.cp.JCP4XDOBurstingEngine.runProgram(JCP4XDOBurstingEngine.java:233)
at oracle.apps.fnd.cp.request.Run.main(Run.java:157)
Solution:
1. Ensure that this concurrent program is not waiting for the output of another request. 
2. Check the Parent Concurrent program.
For example: if the bursting concurrent program (B) was submitted from another concurrent program (A). When submitting program B, program A will wait to see if it completed.
However, because program A is still running the output file will not be written and not found by program b.

3. Edit the concurrent program definitions and make the programs incompatible with each other so that each one must complete before the next program is started. 
4. Check the Temp Directory to ensure that it has enough free space and re-test.
Reference:
Bursting Fails With File Is Not Accessible From Node/Machine (Doc ID 1540005.1)
  • December 31, 2018 | 31 views
  • Comments