Skip to Content

BOBI 4.1 SP2 Oracle client installation on server

Hi,

   In my landscape, we have installed BOBI 4.1 SP2 on windows 2008 and the oracle version is 11g. Everything is working fine except audit configuration. Actually SAP recommended to install both 32 bit oracle and 64 bit oracle client in server. But if we install both version on server then how it will works and how can we set env. variables and TNS entry. Totally confused and am not good at oracle. Any one input is highly appreciated.

Thankig you in anticipation.

Obinna.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    avatar image
    Former Member
    Mar 26, 2014 at 06:10 AM

    If you do not have separated installations (CMS server and Application server) and would like to have both 64-bit and 32-bit installed on your server, you may face issue with your CMS.

    To have both 64-bit and 32-bit installed and avoid CMS issue, please set your environment

    Variables as indicated below:

    # In BI 4.0, in order to connect with CMS database it is required to have 64-bit client installed on the server.

    # If you have also installed 32-bit Oracle client for Crystal reports 2011 along with the 64-bit Oracle client, Check if the following Environment variables are set properly:

    Environment Variable to be set:

    1. 1. ORACLE_HOME=<64-bit version of the Oracle client path>
    2. 2. ORACLE_HOME32=<32-bit version>
    3. 3. TNS_ADMIN=<64-bit version>
    4. 4. TNS_ADMIN32=<32-bit version>
    5. 5. BOE_USE_32BIT_ENV_FOR=ORACLE_HOME,TNS_ADMIN

    Mention Oracle 64 path first in the PATH environment variable and then the Oracle 32 bit path.

    Reboot server once completed above and make sure cms.exe is running after restart.

    Add comment
    10|10000 characters needed characters exceeded

    • If the reports/universes are using a Native Oracle connection, then the TNS entry should work.  You only need to create ODBC connections if the reports and/or universes use that type of connection instead.  From my experience, the Native Oracle connection is more stable and reliable than trying to use ODBC.

      -Dell