Uploading Siebel reports to BI Publisher – Error creating local file cache directory

If you’re using BI Publisher as the report server for Siebel, you might end up having integration issues somewhere in time.

The most common issues are the errors uploading he reports (in fact, the templates) to the report server.

With Siebel 8.1.1.8, and maybe with all other Siebel 8 versions that use the new OUI setups, you’ll probably will face a new error when trying to upload the reports:

Error creating local file cache directory (SBL-SVC-00156)

This is quite easy to solve. How?

Using the Windows Explorer or the Unix/Linux command prompt, go to TEMP folder of the Siebel Servers (something like C:\Siebel\siebsrvr\TEMP) and create a new folder called “XMLP”. Simple as that.

Now try the upload again. The expect result would be the message below:

Upload successful (SBL-RPT-50566)

Rendering Large Reports

From my experience, rendering a really large report in BI Publisher 10g is a big headache. Either you’ll get "Java Heap Space" exception, or the browser will hang with a blank page and no error.

If your BI Publisher server is 32-bit, and if you try to increase the heap size you’d might end up not being able to start the Java EE server (in my case, OC4J), or making it crash at some point of the report execution.

If you are able to migrate the application to a 64-bit server, then that would be the best solution. JVM does not work well in 32-bit, and surely have a limit of less than 2 GB of heap space (around 1,5 GB). On a 64-bit server, this limit is much higher. I’m already using more than 10 GB, and… so far so good.

But either with 32 or 64-bit, there are some actions you can take to achieve a better performance and reliability for large reports:

Set the temporary folder

Setting a temporary folder for report execution will help handling large sets of data and its merge into report templates.

1) In each server where you have BI Publisher installed, create a folder that will be used for the application temporary files. Make sure it has a lot of space and that the user running the JVM for BI Publisher has permissions to write in it. This folder can be created inside the BI Publisher installation folders, but in that case I recommend using the application’s root folder.

2) Login in BI Publisher administrator user

3) Navigate to Admin > System Maintenance > Server Configuration

4) At General Properties section, in the System Temporary Directory selection box, add the full path to the folder. In a Windows system, make sure that you use slash (“/”) and not backslash (“\”).

5) Click the Apply button, and check if the confirmation message appears at the top of the screen:

Confirmation Settings saved successfully. Any changes will not take effect until the application is restarted.

Change Properties

There are 3 properties that normally help rendering large reports.

1) Login in BI Publisher administrator user

2) Navigate to Admin > Runtime Configuration > Properties

3) Set this properties to TRUE

      - Use BI Publisher's XSLT processor

      - Enable scalable feature of XSLT processor
      - Enable XSLT runtime optimization

4) Click the Apply button, and check if the confirmation message appears at the top of the screen:

Confirmation Settings saved successfully. Any changes will not take effect until the application is restarted.

BI Publisher 10g - Activate Debug Mode

Troubleshooting: that day will surely come, no matter which application you're using.
For BI Publisher, one of the best troubleshooting tools is the debug mode. This activates detailed logs and temporary files, which allow

How to activate the debug mode


1) Login in BI Publisher with an administrator user

2) Go to Admin tab > System Maintenance > Server Configuration 
3) In the General Properties section, change the Debug Level value to Debug 
4) In the Output Formats section, select all output formats by checking all boxes
5) Click the Apply button
6) Check the confirmation message at the top left of the screen:

Confirmation Settings saved successfully. Any changes will not take effect until the application is restarted.

7) Inside the BI Publisher installation folder, create a subfolder called xmlpdebug (this will be used to hold xdo.log and other debug files)
8) Create a new file called xmlpdebug.cfg with the following content:

LogLevel=DEBUG LogDir=C:\BIPublisher\xmlpdebug

9) Place this file inside the JRE lib folder of the JVM in use by BI Publisher (example: C:\Java64bit\jdk1.6.0_37\jre\lib)
10) Restart BI Publisher
11) Now, open the BI Publisher login page and check the bottom right information. You should be able to see the version and the build number.