On win 7 64 bit I have a local 64 bit database with 64 bit client.
B/cSql nav does not support 64 bit I have also installed 32 bit instant client light (11.2.0.2). I have added this instant client to PATH
Sqlnav cannot seem to find oci.dll, unless I start it from the directory where instant clent was unpacked.
I have also noticed that this instant client is not recognized by sqlnav as a valid home (BTW it is recognized by TOAD) :
SOFTWARE\ORACLE (Oracle Root)
ORACLE_HOME_NAME:
ORACLE_HOME:
ORACLE_SID:
NLS_LANG:
SQLPATH:
LOCAL:
Home directory does NOT exist!
Home is NOT valid!
Instant Client - 11.2.0.1.0
ORACLE_HOME_NAME: C:\Apps\Oracle\product\11.2.0\instantclient_11_2
ORACLE_HOME: C:\Apps\Oracle\product\11.2.0\instantclient_11_2
ORACLE_SID:
NLS_LANG:
SQLPATH:
LOCAL:
C:\Apps\Oracle\product\11.2.0\instantclient_11_2exists.
C:\Apps\Oracle\product\11.2.0\instantclient_11_2is in PATH.
Client DLL: C:\Apps\Oracle\product\11.2.0\instantclient_11_2\oci.dll
Client Version: 11.2.0.1.0
Home is NOT valid!
Instant Client Package - Basic Lite: Smaller version of the Basic, with only English error messages
and Unicode, ASCII, and Western European character set support (10.2 only)
Thank you very much for you the support bundle and your notes on the client on my envi.
We can confirm that we have issues in SQL Navigator to detect the 11g instant client as invalid. SQL Navigator is currently looking for oraociei10.dll, if the file is not there, it will assume the client is not valid. We will fix it for you in the next v6.6 release and it will be in the first v6.6 Beta drop.
The work around is to make a copy of oraociei11.dll and rename it to oraociei10.dll in the directory C:\Apps\Oracle\product\11.2.0\instantclient_11_2.
Please note that SQL Navigator can ONLY work with 1 instant client having it to be first in the path system variables, The instant client will be the default home.
Can you please make changes to your path to have the instant client path to be first in the list:
Thank you very much for you the support bundle and your notes on the client on my envi.
We can confirm that we have issues in SQL Navigator to detect the 11g instant client as invalid. SQL Navigator is currently looking for oraociei10.dll, if the file is not there, it will assume the client is not valid. We will fix it for you in the next v6.6 release and it will be in the first v6.6 Beta drop.
The work around is to make a copy of oraociei11.dll and rename it to oraociei10.dll in the directory C:\Apps\Oracle\product\11.2.0\instantclient_11_2.
Please note that SQL Navigator can ONLY work with 1 instant client having it to be first in the path system variables, The instant client will be the default home.
Can you please make changes to your path to have the instant client path to be first in the list:
Thanks, the workaround resolved my issue. One minor note - oraorciei11.dll does not exist in the home, the source dll name is oraocci11.dll
Funny thing is that on your screen shot the home is being recognized as 11.2.0.1 incorrectly (i assume you have downloaded the latest client from my link). Same thing exists for TOAD 11.2.0.2 instant client is recognized as 11.2.0.1 client.
On my machine the client is being recognized correctly as 11.2.0.2 :
SOFTWARE\ORACLE (Oracle Root)
ORACLE_HOME_NAME:
ORACLE_HOME:
ORACLE_SID:
NLS_LANG:
SQLPATH:
LOCAL:
Home directory does NOT exist!
Home is NOT valid!
Instant Client - 11.2.0.2.0
ORACLE_HOME_NAME: C:\Apps\Oracle\product\11.2.0\instantclient_11_2
ORACLE_HOME: C:\Apps\Oracle\product\11.2.0\instantclient_11_2
ORACLE_SID:
NLS_LANG:
SQLPATH:
LOCAL:
C:\Apps\Oracle\product\11.2.0\instantclient_11_2 exists.
C:\Apps\Oracle\product\11.2.0\instantclient_11_2 is in PATH.
Client DLL: C:\Apps\Oracle\product\11.2.0\instantclient_11_2\oci.dll
Client Version: 11.2.0.2.0
Home is valid.
As per my previous note, we will need to make more changes to check the version of Oracle instant client…In your environment, it shows the correct version since you use oraocci11.dll as the base of the work around. That dll has the correct version as 11.2.0.2
We will clean up the routine and the verison checking should work in the next release for you.
