Troubleshooting Oracle BI Publisher with OBIEE
To troubleshoot Oracle BI Publisher (previously XML Publisher) Enterprise 10g issues with OBIEE, you should enable the debug feature in BI Publisher first.
Enabling the debug feature in Oracle BI Publisher Enterprise requires the creation of a special file which must be placed in a specific directory of the JDK installation on the application server.
Perform the following actions to enable debug and generate the debug files (depending on the Operating System):
1) Determine the path to the Java SE Development Kit (JDK) installation, e.g.:
Unix: /oracle/as10g/jdk1.5.0_10
Windows: D:\oracle\as10g\jdk1.5.0_10
2) Create a new temporary directory to hold the debug files:
Unix: $ mkdir /oracle/as10g/xmldebug
Windows: D:\> mkdir \oracle\as10g\xmldebug
3) Create a new file called xdodebug.cfg under the following directory (based on step 1):
Unix: /oracle/as10g/jdk1.5.0_10/jre/lib
Windows: D:\oracle\as10g\jdk1.5.0_10\jre\lib
4) Put the following two lines in the xdodebug.cfg file:
Unix: LogLevel=STATEMENT
LogDir=/oracle/as10g/xmldebug
Windows: LogLevel=STATEMENT
LogDir=D:\oracle\as10g\xmldebug
5) Restart the application server (required to have the JRE to pick up the new configuration file).
6) Reproduce the error.
7) Depending on the situation that is being investigated, the following debug files will be generated:
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)
8) Create a ZIP file of all the debug files that were generated under the temporary directory and then send them to Technical Support for analysis if required.