This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

ORACLE CONNECTION

Hi Guys, I want to use an oracle connection in Microstation.

My Oracle Client is here : c:\oracle\product\11.2.0\client_1 .

MS_ORACLE_HOME also is set to c:\oracle\product\11.2.0\client_1.

As this client is NOT my preferred client for other programs that connect to Oracle, it is not published in the PATH Variable or at least not published first place.

When I want to connect, using SESSION DEBUG ON , then MS shouts unable to load  c:\oracle\product\11.2.0\client_1\bin\orasql11.dll

This is urgent. Could anyone please tell me whats going on?

Regards, Stefan.

Parents
  • Hello Stefan,

    If the problem remains unresolved, please let us know your:

    MicroStation version: (e.g. 08.xx.xx.xx)

    OS: (e.g. Windows 7 Pro SP2 X32)

    Please consider, and let us know:

    - Is MS_ORACLE_HOME set within the Oracle.cfg file?

    -- Please confirm (via Workspace>Configuration) that this remains set, after the failure is experienced?

    - Is the installed client the 32 or 64 bit version?

    Does the file specified exist in the specified location?

    [c:\oracle\product\11.2.0\client_1\bin\orasql11.dll]

    I’ve located the file within a 32bit client:

    [ ...\ORACLE\product\11.2.0\clientx86\BIN\orasql11.dll]

    If yours is similar, you may need to set the MS_ORACLE_HOME definition to:

    [  ...\ORACLE\product\11.2.0\clientx86 ]

    +++

  • - Is MS_ORACLE_HOME set within the Oracle.cfg file?

    No, it is set in a custom.cfg in cofig/appl.

    - Is the installed client the 32 or 64 bit version?

    It is 32 bit.

    - Does the file specified exist in the specified location?

    Yes.

  • I am able to replicate your issue, we will investigating further. So far I have not been able to found a workaround.



  • Some other questions for the group....

    Can you run SQLPlus from the command prompt ? Probably not since the client Oracle home is not in the path....

    Do you have more than one Oracle Client installed ?

    Are we sure the MS_ORACLE_HOME configuration variable gets set correctly ? Run Microstation/Workspace with the -debug command line variable and review the msdebg.txt file for possible anomalies.

     

  • > Do you have more than one Oracle Client installed ?

    Yes.

    >Are we sure the MS_ORACLE_HOME configuration variable gets set correctly ?

    Yes. Checked it with -debug and reviewed under Workspace/Configuration.

  • We've found Stefan's case to be representative of a problem within MicroStation, when multiple Oracle clients are installed and included within the OS path definition.  This occurs despite appropriate definition of MS_ORACLE_HOME, when the/an undesired client path takes precedence within the OS path statement.  i.e. : is listed first.  Defect #87352 has been filed to address this issue. 

    The hallmark of the issue is revealled within a session debug of the failing connection.  Herein we see that EXTSERVER has located the specified Oracle client (line 8), but is unable to load the files subsequently requested (line 10), despite thier presence in that location:

     8 EXTSERVER: Found Oracle Client: c:\oracle\product\11.2.0\client_1\bin\oraclient11.dll
     9 MDL:CallBack for DebugMessage
    10 EXTSERVER: Unable to load c:\oracle\product\11.2.0\client_1\bin\orasql11.dll

    The workaround for the problem is to reorder, or completely remove the undesired client path from the path statement utilized by the MicroStation session. 

    This can be accomplished most simply by launching MicroStation from the OS command line, *.bat or *.cmd file as may be appropriate, with the modified PATH= statement.  In the example below, we remove an undesired Oracle 10.2.0 client, to allow succesfull connection to the Oracle 11.2.0 client:

     

    (reorder)

    SET PATH=C:\oracle\product\11.2.0\client_1\bin;C:\oracle\product\10.2.0\Ora102010_32\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem

    (removal)

    SET PATH=C:\oracle\product\11.2.0\client_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem

    then:

    CALL "C:\081109357 MicroStation V8i (SELECTseries)\MicroStation\ustation.exe"

     

    Answer Verified By: Nelson Hobdell 

Reply
  • We've found Stefan's case to be representative of a problem within MicroStation, when multiple Oracle clients are installed and included within the OS path definition.  This occurs despite appropriate definition of MS_ORACLE_HOME, when the/an undesired client path takes precedence within the OS path statement.  i.e. : is listed first.  Defect #87352 has been filed to address this issue. 

    The hallmark of the issue is revealled within a session debug of the failing connection.  Herein we see that EXTSERVER has located the specified Oracle client (line 8), but is unable to load the files subsequently requested (line 10), despite thier presence in that location:

     8 EXTSERVER: Found Oracle Client: c:\oracle\product\11.2.0\client_1\bin\oraclient11.dll
     9 MDL:CallBack for DebugMessage
    10 EXTSERVER: Unable to load c:\oracle\product\11.2.0\client_1\bin\orasql11.dll

    The workaround for the problem is to reorder, or completely remove the undesired client path from the path statement utilized by the MicroStation session. 

    This can be accomplished most simply by launching MicroStation from the OS command line, *.bat or *.cmd file as may be appropriate, with the modified PATH= statement.  In the example below, we remove an undesired Oracle 10.2.0 client, to allow succesfull connection to the Oracle 11.2.0 client:

     

    (reorder)

    SET PATH=C:\oracle\product\11.2.0\client_1\bin;C:\oracle\product\10.2.0\Ora102010_32\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem

    (removal)

    SET PATH=C:\oracle\product\11.2.0\client_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem

    then:

    CALL "C:\081109357 MicroStation V8i (SELECTseries)\MicroStation\ustation.exe"

     

    Answer Verified By: Nelson Hobdell 

Children
No Data