asked on Connecting Win7, 64 bit to Oracle
I know this will be odd, but we need to connect some new machines to an old database. Our new machines are Win7, 64 bit, Professional. We have a couple old Access databases which link to data on our Oracle server. HP-UX Oracle version 8.0.6. (Stop laughing)
Here is where I am at. I have managed to install the 8.0.6 client on these machines as well as 32 bit Win7 Pro. The 32 bit machines work without a hitch. On the 64 bit machines, I can successfully set up the DSN and retrieve data using the Oracle ODBC test app. I can also run Custom VB apps which use OLE to link to the Oracle data with success.
When I try and retrieve data in the Access database I receive an error 6413 Driver's SQLSetConnectAttr failed IM006.
I can not use the newer Oracle drivers as they will not connect to this older version of the database server.
Any thoughts are appreciated.
Here is where I am at. I have managed to install the 8.0.6 client on these machines as well as 32 bit Win7 Pro. The 32 bit machines work without a hitch. On the 64 bit machines, I can successfully set up the DSN and retrieve data using the Oracle ODBC test app. I can also run Custom VB apps which use OLE to link to the Oracle data with success.
When I try and retrieve data in the Access database I receive an error 6413 Driver's SQLSetConnectAttr failed IM006.
I can not use the newer Oracle drivers as they will not connect to this older version of the database server.
Any thoughts are appreciated.
Oracle DatabaseMicrosoft Access
Last Comment
slightwv (䄆 Netminder)
ASKER
I have tried versions of Access from 97 to 10, with no different results from any of them since they are all using the same Oracle ODBC driver.
I was thinking more along the lines of create an older version of access using an older verions of driver. I guess now that I type that out, it doesn't make sense since it would have to be on a different machine and probably couldn't be accessed from the local machine...
I'm sure other Experts will be around shortly and have more sound ideas...
I'm sure other Experts will be around shortly and have more sound ideas...
You can actually use Oracle 9i driver to downconnect to 8, if that helps. I also seem to recall that 10.0 driver worked against it as well. 10.2 does not.
The point is you are not limited to 8.0 driver.
On the 64-bit machines, check that you didn't install them into "Program Files (x86)" as the old drivers do not like parentheses in the Oracle home path name.
The point is you are not limited to 8.0 driver.
On the 64-bit machines, check that you didn't install them into "Program Files (x86)" as the old drivers do not like parentheses in the Oracle home path name.
ASKER
Will moving to the 9i client driver do anything for me? On our XP machines we have played some with the later drivers and did not see any change that warranted moving to them.
The client was not installed into the (x86) directory.
The client was not installed into the (x86) directory.
The issue is you need something the version of Access knows how to deal with. This version also needs to know how to talk to an Oracle 8.0 database.
We're thinking the 9i drivers and possible the 10.0 drivers might bridge that gap.
I was just trying to figure out a way to use the older versions without actually installing them on the new machines.
We're thinking the 9i drivers and possible the 10.0 drivers might bridge that gap.
I was just trying to figure out a way to use the older versions without actually installing them on the new machines.
ASKER
I tested another configuration on a second machine. I used the Oracle 9i client. It still only throws an error on the ODBC connection from within Access. The error is ORA-12154 with the exact same description of the error.
The ODBC test and OLE connection continue to function without problems.
The ODBC test and OLE connection continue to function without problems.
An ORA-12154 is a tnsnames.ora configuration issue not really a version issue.
You need to make sure every version of Oracle installed has a valid tnsnames.ora file or you have one common one and set an environment variable called TNS_ADMIN pointing the the folder where you put it.
You need to make sure every version of Oracle installed has a valid tnsnames.ora file or you have one common one and set an environment variable called TNS_ADMIN pointing the the folder where you put it.
ASKER
I've verified that the tnsnames.ora files are functional. I can get data through the SQL*Plus app as well.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
I guess I should also add: 64Bit Windows comes with two different versions of the ODBC administrator. The 32Bit one needs to be manually executed from the SysWoW64 folder.
http://support.microsoft.com/kb/942976
http://support.microsoft.com/kb/942976
ASKER
On each machine I have only the single version of Oracle installed.
I have become very familiar with the location of the ODBC 32 bit admin. (LOL)
I have become very familiar with the location of the ODBC 32 bit admin. (LOL)
Maybe mrjoltcola will be around later and can add to what you are now seeing with the ora-12154.
There is likely going to have to be some smoke and mirrors. I'm thinking an intermediate database.
Either a older version of Access that can connect/link to 8.0 then link the new access to the other database
Or, maybe a 9i Oracle database that will link to the 8.0. I don't think 10g will link to 8.0 but it might.