Skip to Content
Author's profile photo Manikandan Elumalai

Audit configuration for BI 4.1 with Oracle database

As we already know the Audit universe and reports needs to be deployed manually in BI platform as it is no longer out of box functionality in BI 4.x. For BI 4.0 Auditor configuration, I have already written a blog here

The difference between earlier blog and this blog is the deployment method. In BI 4.0 the Auditor will be configured by extracting from the file system (.unx universe & Crystal reports) but where as in BI 4.1 SPx we do have the LCMBIAR file which holds the required universe and reports. Please continue reading the blog for step by step procedure to configure auditor.

You can download all the required universe and reports from the document here

and make sure you enabled Auditor in CMC.  Refer here BusinessObjects Auditing – Considerations & Enabling

You need to select the appropriate .unx file according to your database middleware. Since I am going to deploy it in Oracle database I validated the supported Oracle client installation and the corresponding TNSNAMES.ora file with the Audit database service entry.


In order to import the LCMBIAR content, we are going to use command line batch file (LCM_CLI.bat) with .LCMBIAR file and a property file with import parameters.




Sample properties file















Run the LCM_CLI.bat file with the property file as a parameter something like below


The import status


Once the BIAR file is imported successfully, we need to modify the universe connection in such a way that it points to the right audit schema.

Furthermore, Create a Project in Information Design Tool and import the universe.








You should have Adobe flash player 11 or higher to launch the crystal reports from BI Launchpad.

Here is the deployed report for you.


Here are some of the blogs related to Auditing

BusinessObjects Administration – Audit reporting vs Metadata reporting

BusinessObjects Auditing – What is changed in BO 4.0?

BusinessObjects Auditing – Considerations & Enabling

BusinessObjects Administration – Extending capabilities of BI 4.x Audit reporting

Hope this could help people who are looking for BI 4.1 audit configuration. Thanks for reading!

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member

      Using your documentation (and after resolving an error not mentioned here) I was able to finally get to a point where I could (attempt to) test the universe connection (though the resolution was awful, so I had to guess at what you were selecting).  But when I try to test the connection using the Oracle (32-bit) ODBC connection and the Oracle Client connection, it fails.

      I am able to successfully connect to the db using the 32-bit ODBC connection in the ODBC connection administrator.

      The error with the ODBC connection test in IDT is: com/businessobjects/connectionserver/PropertySet%CancelSupportLevel.

      Author's profile photo Former Member
      Former Member

      Doesn't work for me....

      Author's profile photo Manikandan Elumalai
      Manikandan Elumalai
      Blog Post Author

      Could you brief bit more to understand the root cause of the issue

      Author's profile photo Former Member
      Former Member

      The Oracle Client (using tnsnames) uses 64-bit. (And I was told by tech support that using "Oracle Client" will not work (and it didn't).)

      The Universe needs a 32-bit connection. I have both the 64-bit and 32-bit Oracle clients installed because the CMS dbs need 64-bit.The Universe needs the 32-bit one. I can test the 32-bit ODBC client in ODBC Administrator, and it works fine. The thing is to get the Universe connection to use the 32-bit ODBC client. I moved it to the beginning of the path in the environmental variables, but that didn't work. I have all of the products installed on the same server.

      Author's profile photo Andreas J A Schneider
      Andreas J A Schneider

      To clarify:
      The universe itself does not need a 32-bit database driver, but the Information Design Tool, which is 32-bit Software used to modify a universe, does require a 32-bit data base driver.

      Author's profile photo Former Member
      Former Member

      Still, if both driver version are on the server, how do you get IDT to recognize the 32-bit driver? Tech support, even though they will not support the sample universes, eluded to having to get IDT to recognize the right driver. How do you do that? I tried moving the 32-bit entry in the Environmental Variables before the 64-bit driver, but it didn't work.  I have to pay for consulting services (which we may not be able to do) in order to find that out.(??) Surely someone else has run into the same issue.

      Author's profile photo Manikandan Elumalai
      Manikandan Elumalai
      Blog Post Author
      Author's profile photo Former Member
      Former Member

      I had to use the jdbc connection type.