Oracle Linked Server on SQL Server 2005 64-bit

Hello,
we are trying to migrate from SQL Server 2000 to SQL Server 2005.
On an 64 bit Windows 2003 SP1 Server we have installed an SQL Server 2000
Enterprise Edition and an SQL Server Enterprise Edition 2005 (64bit), both as
named instances.
On both SQL Servers we have configured Oracle Linked Servers. While
distributed queries on the SQL Server 2000 are running fine, we get the
following error message on the SQL Server 2005:
Msg 7403, Level 16, State 1, Procedure v_extendedcustomer2, Line 6
The OLE DB provider "MSDAORA" has not been registered.
What could be the problem?
Thanks in advance
Detlef Herchen
Hi Detlef,
Welcome to use MSDN Managed Newsgroup!
From your descriptions, I understood you could quer
1. Is your SQL Server 2000 also 64 bit version?
2. Does your Oracle OLE DB provider supports 64-bit? You must download the
latest provider that supports 64 bit for SQL Server 2005 x64
3. You may also try using 32bit ODBC Configuration in the Windows Pro X64
to configure Access ODBC driver for your application. Launch the Panel with
command C:\WINDOWS\SysWow64\odbcad32.exe and you will see the Configuration
Dialog. (Note that this will run on WOW)
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.

Oracle Linked Server on SQL Server 2005 64-bit

Hello,
we are trying to migrate from SQL Server 2000 to SQL Server 2005.
On an 64 bit Windows 2003 SP1 Server we have installed an SQL Server 2000
Enterprise Edition and an SQL Server Enterprise Edition 2005 (64bit), both a
s
named instances.
On both SQL Servers we have configured Oracle Linked Servers. While
distributed queries on the SQL Server 2000 are running fine, we get the
following error message on the SQL Server 2005:
Msg 7403, Level 16, State 1, Procedure v_extendedcustomer2, Line 6
The OLE DB provider "MSDAORA" has not been registered.
What could be the problem?
Thanks in advance
Detlef HerchenHi Detlef,
Welcome to use MSDN Managed Newsgroup!
From your descriptions, I understood you could quer
1. Is your SQL Server 2000 also 64 bit version?
2. Does your Oracle OLE DB provider supports 64-bit? You must download the
latest provider that supports 64 bit for SQL Server 2005 x64
3. You may also try using 32bit ODBC Configuration in the Windows Pro X64
to configure Access ODBC driver for your application. Launch the Panel with
command C:\WINDOWS\SysWow64\odbcad32.exe and you will see the Configuration
Dialog. (Note that this will run on WOW)
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Dear Michael Cheng,
I'm using SQL Server 2005 64 Bit and having a problem when I try to
connect to Oracle 10G 64 Bit (installed on the same server). I'm using
"Oracle Provider for OLE DB" to connect but from what I've read in
Books Online that the provider doesn't support for Oracle 64 Bit. Can
you please tell me how to fix it ? Maybe I should install another
provider such as "Microsoft OLE DB Provider for Oracle" ? If so, where
can I find or download that provider for SQL 2005 64 Bit. Thanks.
Regards,
Albert
4lb3rt
---
4lb3rt's Profile: http://www.dbtalk.net/m925
View this thread: http://www.dbtalk.net/t155721

Oracle linked server (64-bit)

We have an active-active cluster on two 64-bit servers, with an
instance of SQL Server running on each node.
We installed the 64-bit oracle client and it works just fine using
Oracle's "SQL Plus" app. But when we add it as a linked server in SQL
Server, it hangs when we try to access it, whether in the Enterprise
Manager or executing "sp_catalogs". It then kicks us off and the node
has to be rebooted for all the services and groups to come back online
properly.
we have a linked server to Oracle on another 64-bit Sql Server (not
clustered) which works just fine for us.
Has anyone seen this? Any helpful thoughts?
bryan
Make sure the provider is setup to execute in-process with SQL Server, by
default it is not since it is not a Microsoft provider, but the Oracle
provider does not work correctly out of process.
See http://support.microsoft.com/default...B;EN-US;280106
NOTE : If you use a third-party Oracle provider and it is incapable of
running outside of a SQL Server process, allow it to run in-process by
changing the provider options. To change the provider options, change the
value of the AllowInProcess (DWORD) entry in the following registry key,
which is located under the corresponding provider name, to 1:
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2004 All rights reserved.
"bk" <r.bryan.kane@.gmail.com> wrote in message
news:1102633081.687411.319750@.f14g2000cwb.googlegr oups.com...
> We have an active-active cluster on two 64-bit servers, with an
> instance of SQL Server running on each node.
> We installed the 64-bit oracle client and it works just fine using
> Oracle's "SQL Plus" app. But when we add it as a linked server in SQL
> Server, it hangs when we try to access it, whether in the Enterprise
> Manager or executing "sp_catalogs". It then kicks us off and the node
> has to be rebooted for all the services and groups to come back online
> properly.
> we have a linked server to Oracle on another 64-bit Sql Server (not
> clustered) which works just fine for us.
> Has anyone seen this? Any helpful thoughts?
> bryan
>