Showing posts with label 64bit. Show all posts
Showing posts with label 64bit. Show all posts

Tuesday, March 20, 2012

Connecting to Oracle from Windows 64bit IA server

I am trying to pull data from an Oracle 9i database to my SQL Server 2005 sp1 database on Windows 2003 64bit Itanium server. Each time I try to use the import wizard, select the Microsoft OLE DB driver for Oracle, I get an error message telling me that the Oracle client tools are not installed. This happened after I had already installed the 9i tools, tested the connection using TNSPING and confirmed the tnsnames file was correct. So, I uninstalled the 9i tools and then installed the 10g client tools. Tested everything after the install and then tried the import again selecting the MS OLE DB driver for Oracle. I again got the error message that the Oracle tools were not installed.

has anyone ran into this problem and if so, were you able to fix it?

It seems that there is an with how Oracle parses the Program Files (x86) directory. Has anyone heard of this?|||

This is a known Oracle bug, with plenty of information about the issue here -

Connecting to Oracle on 64-bit (x64) machine - MSDN Forums
(http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=159581&SiteID=1)

sqlsql

Friday, February 17, 2012

Connecting 32bit ASP to 64 bit SQL Server 2005

issue:

i have an ASP-Application running fine with both SQL Server 2000 and SQL 2005 (both 32 bit)

Now i have to attach a 64bit SQL-Server.

I have a problem with the connection:

This one runs fine with sql 2005 32bit

<%set myConn = Server.CreateObject("ADODB.Connection")

myConn.open "driver={SQL Native Client};server=<servername>;database=<dbname>;uid=<uid>;pwd=<pwd>" %>

but not with the 64-bit server:

ADODB.COnnection error "800a0ea9". Provider is not specified and there is no standard provider.

ok, i did some research and came up with the following:

<%set myConn = Server.CreateObject("ADODB.Connection")

myConn.open "PROVIDER=SQLOLEDB;DATA SOURCE=<serverip>,<serverport>;database=<dbname>;uid=<uid>;pwd=<pwd>" %>

thats fine, now i get a connect.

Unfortunately, this provider seems to behave different to the one i use in 32bit :

Lets say i have a stored procedure"

create spName as

select * from mytable

when i execute the following

<%sqlstr = "exec spname"

set myRecSet = CreateObject("ADODB.Recordset")

myRecSet.open SQLStr, myConn

response.write(myRecSet(0)) %>

it gives the first value of the first row with the Connection to a 32bit SQL-Server

but myRecSet seems to be empty on my 64bit SQL Server the response.write leads to an error message.

As far as i understand this, the provider used when connecting to a 32bit Server returns the records selected by the last row of the stored procedure into the recordset, but the provider when connecting to a 64bit server does not return these results.

What can i do, if i dont want to rewrite my asp-programming. I hope somebody has the correct naming / syntax for an connection string which allows me to connect my asp-application to the 64bit SQLServer which behaves like the "old" one for 32bit.

I hope my comments are clear enough - english is obviously not my mother-tongue - and somebody can give me a hint.

Thanks,

Heinrich

What is the error message?