Harvest

Tuesday Tip: CABI Returns a ORA-12154 error: "TNS:could not resolve the connect identifier specified . (WIS 10901)"

  • 1.  Tuesday Tip: CABI Returns a ORA-12154 error: "TNS:could not resolve the connect identifier specified . (WIS 10901)"

    Broadcom Employee
    Posted 02-12-2015 05:21 PM

    When trying to run a BusinessObjects report, the following error is returned:

    A database error occurred. The database error text is: ORA-12154: TNS:could not resolve the connect identifier specified . (WIS 10901)

     

    This was a case where the 32-bit Oracle 10g client was installed and configured correctly on the CABI server. Tnsping worked, connecting with sqlplus worked, and we could manually configure an ODBC data source that would connect with no problem.  The only way we had problems connecting to his database was through BusinessObjects.

     

    After a lot of internet searching I found the root cause of the problem.  It turns out that certain 32-bit versions of Oracle Client have problems dealing with BusinessObjects (and with 32-bit SCM server as I found out in my testing) if they are installed to the default "C:\Program Files (x86)\..." folder.  It's the parentheses in the folder name Oracle is having a problem with.  Here's a forum post that explains it:

    http://www.forumtopics.com/busobj/viewtopic.php?t=176780&sid=0b233501628105aa2f0d7308cd9f492b

     

    There are 3 different ways the problem can be solved:

     

    1. Uninstall BusinessObjects (or SCM Server) and reinstall to a folder that contains only alpha-numeric characters in the name (for example "C:\app\CA..." instead of "C:\Program Files (x86)\CA...")
    2. Locate and install the patch recommended in the forum post that corresponds with the installed version of the Oracle client.
    3. Upgrade the Oracle database to 11g so that the 11g Oracle client can be used instead. 

     

    The patches listed in the forum post are:

    For Windows 32-bit Oracle Client: 
    9.2.0.7.0 Patch 6: Apply Patch 4928723 or later
    10.2.0.1.0 Patch 4: Apply Patch 4923768 or later
    10.2.0.2.0 Patch 5: Apply Patch 5383042 or later
    10.2.0.3.0: Apply Patch 5337014 or later


    For Windows 64-bit AMD64 and INTEL EM64T Oracle Client
    10.2.0.1.0 Patch 4: Apply Patch 4923787 or later
    10.2.0.2.0 Patch 5: Apply Patch 5388871 or later
    10.2.0.3.0: Apply Patch 5337014 or later


    If possible, use a version of the Oracle software that contains the fix for Bug 3807408