问题排查的方式 是需要通过XDO.log 去看日志

XDO.log如何生成 可以参考以下官方提供步骤

the XML Publisher Core engine debug

             For the program involved set the debug mode checkbox in the program definition. The debug flag parameter should be set to 'Y' per the following steps:

            1. Login as 'System Adminstrator'

            2. Navigate to: Concurrent -> Program -> Define

            3. Query up the program shortname XDOREPPB

            4. Click on Parameters

            5. Scroll down for "Debug Flag".

            6. Enable this by clicking on the check option.

            7. In the Validation block, set the Default Value = Y.

 

 

Single step and two step publishing method, with concurrent processing:

Connect to the concurrent manager server as applmgr.

Create an $XDO_TOP/temp and an $XDO_TOP/resource directory.

Create an xdodebug.cfg file in the $XDO_TOP/resource directory, containing the following 2 lines:

LogLevel=STATEMENT

LogDir=[enter full path to XDO_TOP here]/temp

Restart the concurrent managers in case of single step publishing method (not required for two step publishing method).

Reproduce the problem.

Note: The xdodebug.cfg file can also be created in the $AF_JRE_TOP/jre/lib OR $AF_JRE_TOP/lib directory.

Direct report publishing via the XML Publisher Core APIs, without concurrent processing:

Connect to the Apache server as applmgr.

Create an $XDO_TOP/temp and an $XDO_TOP/resource directory.

Create an xdodebug.cfg file in the $XDO_TOP/resource directory, containing the following 2 lines:

LogLevel=STATEMENT

LogDir=[enter full path to XDO_TOP here]/temp

Restart the Apache server.

Reproduce the problem.

Note: The xdodebug.cfg file can also be created in the $OA_JRE_TOP/jre/lib directory.

All other situations, enabling debug via the JRE itself:

Connect to the server as 'applmgr'.

Run (source) the correct APPS*.env file to setup environment variables.

Create an $XDO_TOP/temp directory.

Execute these commands:

$ cd $OA_JRE_TOP/bin

$ ./java -verbose | grep jre

[Opened /oracle/vis/apps/tech_st/10.1.3/appsutil/jdk/jre/lib/rt.jar]

[Opened /oracle/vis/apps/tech_st/10.1.3/appsutil/jdk/jre/lib/jsse.jar]

[Opened /oracle/vis/apps/tech_st/10.1.3/appsutil/jdk/jre/lib/jce.jar]

[Opened /oracle/vis/apps/tech_st/10.1.3/appsutil/jdk/jre/lib/charsets.jar]

[Loaded sun.reflect.misc.ReflectUtil from /oracle/vis/apps/tech_st/10.1.3/appsutil/jdk/jre/lib/rt.jar]

    -jre-restrict-search | -jre-no-restrict-search

The location of the rt.jar file illustrates the real jre/lib directory in which the xdodebug.cfg file should be created.

Create an xdodebug.cfg file in the same directory as the rt.jar file, containing the following 2 lines:

LogLevel=STATEMENT

LogDir=[enter full path to XDO_TOP here]/temp

Reproduce the problem.

In each of the cases described above, several debug files will be created under the $XDO_TOP/temp directory after reproducing the problem:

xdo.log : XML Publisher Core engine debug log file

xdo_...xsl : XSL-FO version of the RTF template

xdo_...xml : XML data file

xdo_...fo : temporary file created by the FO Engine (only RTF / XSL templates)

xdo_...out : output file (may not exist in case of complete failure).

-- 刘轶鹤