So i have been fighting this same thing for a week now and maybe some of my findings will help here.
I have a Terminal server running X64 2003.
I have the Oracle universal installer 2.2
Running the Oracle 9i Client with a couple patches as well
I am running MDAC 2.8 SP2 on Windows Server 2003 SP1 (2.82.1830.0)
I am running TOAD 7.6.0.11 which is working with Oracle 9i on other machines.
When i installed Oracle I wanted to avoid the Program Files(X86) issue and changed the install location to c:\oracle which didnt seem to help either.
The error i get when using TOAD to connect to an oracle database is ORA-1215: TNS:could not resolve the service name.
The tnsnames.ora file is the same file from a 32bit 2003 server where it works fine.
When I looked at the ODBC Data Source Administrator under Drivers all I have is the SQL Server driver (2000.86.1830) So this is how i ran across this thread to try and install the ODBC drivers for Oracle.
I still havent been able to do this because when I went to the oracle site to try and download the 10g instaclient
http://www.oracle.com/technology/tech/oci/instantclient/instantclient.html
But there is only a Windows 32 bit and an Itanium 64bit. There isnt a X64 client and the Itanium client doesnt work on a non-itanium server.
Now I also had a problem with SQL on X64 as well. When I would create a SQL Alias using the client network utility it would create the alias just fine but when i used enterprise manager or SQL Query analyzer the alias would not work.
I found that when using the client network utility it was putting the alias in the registry in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectTo
But when using SQL Enterprise manager the system was looking for the alias in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MSSQLServer\Client\ConnectTo
So i ended up exporting the registry and importing the aliases into the other key in Wow6432 and they worked.
I am wondering if there might be something similar going on with Oracle.
Message was edited by:
user484076