RE: Data provider for Oracle and SQL 2005 on 64bit windows.

[Database Administrator]

I have installed the x64 Oracle 10g 2.0 client running on a EM64T server w/
Windows 2003 and SQL Server 2005 64-bit and it is connecting to remote Oracle
databases with no issues. Here is the download site--

http://www.oracle.com/technology/sof...inx64soft.html

I'm trying to get the 32-bit version of the Oracle ODAC / ODP.NET component
to work on this test system so that I build some SSIS packages to transfer
data from Oracle to SQL Server. Nothing I've seen so far that states this
won't work but I beginning to wonder. Here is the download site for the ODAC
/ OLE DB stuff--

http://www.oracle.com/technology/sof...net/index.html

VS 2005 on x64 supposedly provides .NET framework for both 64-bit and 32-bit
applications by default. Oracle stated in one of their docs that the 32-bit
ODP.NET components will run on x64 system.

These are the steps I took so far to get the Oracle components working on
the test server--

> Installed the x64 Oracle 10g 2.0 client and configured it to access remote databases. Tested w/ SQLPLUS.
• Installed the x86 version of .NET Framework SDK first
• Installed from the ODAC version and not the ODP.NET (ODAC w/ developer
tools) version
• Installed into a new folder under the Oracle product directory
• Set up TNS_ADMIN variable to point to the Oracle 10g client network admin
location and not the ODAC client location.
• Made sure the Oracle 10g client bin folder is first in the System Path
variable. Move the ODAC bin location to the second spot in the Path variable.
• Copied the sqlnet.ora, ldap.ora, and tnsnames.ora files from the Oracle
10g client network/admin folder to the ODAC network/admin folder.

When I tried to create a connection in SSIS using the Oracle OLE DB
Provider, I was getting an ORA-12157 protocol not loadable error but I was
able to resolve it by taking the steps listed above. Now I'm stuck with the
famous ORA-12154 TNS can't connect error. Everything runs perfectly from an
Oracle client perspective (sqlplus and tnsping). However, SSIS cannot make a
connection to a data source via Oracle OLE DB provider. I'll still missing a
configuration piece somewhere ...

Hope this helps but I may be fighting a losing battle. All of this stuff
works great on a WXP PC.

Brent



"David Gray" wrote:

>
> Hello all,
>
> Windows Server 2003 (Enterprise)
> AMD64 (Opeteron)
> SQL 2005
> Oracle 9i
>
>
> Please help. We are running SQL Server 2005 64bit on an Windows 2003
> Server Machine using AMD Opteron Processors. We are trying to setup
> linked servers to some Oracle 9i Databases on 32bit servers. We need
> to install ODBC/OLEDB providers for Oracle to achieve this. we are
> having difficulty finding out a few things :
>
> i. How to install Microsoft OLEDB for Oracle - we have MDAC 2.8
> installed, but still there is no provider. The question is what is the
> correct OLEDB provider and how do we get it and is there such a thing
> as 64bit MDAC ?
>
> ii. All literature suggests that 64bit version of these products are
> only available on Itanium 2 or higher processors. Is there any way to
> utilise these technologies on 64 bit Opteron.
>
> Your help would be much appreciated as we are at our wits end for what
> is turning out to be quite an expensive project (we are hiring the
> 64bit server).
>
> We currently have Linked servers configured on Win2003 (32bit) server
> and SQL 2000. These use "Microsoft OLEDB Provider for Oracle". Is
> this provider available for AMD64 architecture and if so where can we
> get it?
>
> Thanks in advance.
> Dave
>

[Database Administrator]

"Brent-GPTX" wrote in message
news:EAE6F6B9-8A62-4C76-B188-450DBA60DC34@microsoft.com...
>I have installed the x64 Oracle 10g 2.0 client running on a EM64T server w/
> Windows 2003 and SQL Server 2005 64-bit and it is connecting to remote
> Oracle
> databases with no issues. Here is the download site--
>
> http://www.oracle.com/technology/sof...inx64soft.html
>
> I'm trying to get the 32-bit version of the Oracle ODAC / ODP.NET
> component
> to work on this test system so that I build some SSIS packages to transfer
> data from Oracle to SQL Server. Nothing I've seen so far that states
> this
> won't work but I beginning to wonder. Here is the download site for the
> ODAC
> / OLE DB stuff--
>
> http://www.oracle.com/technology/sof...net/index.html
>
> VS 2005 on x64 supposedly provides .NET framework for both 64-bit and
> 32-bit
> applications by default. Oracle stated in one of their docs that the
> 32-bit
> ODP.NET components will run on x64 system.
>
> These are the steps I took so far to get the Oracle components working on
> the test server--
>
>> Installed the x64 Oracle 10g 2.0 client and configured it to
>> access remote databases. Tested w/ SQLPLUS.
> . Installed the x86 version of .NET Framework SDK first
> . Installed from the ODAC version and not the ODP.NET (ODAC w/ developer
> tools) version
> . Installed into a new folder under the Oracle product directory
> . Set up TNS_ADMIN variable to point to the Oracle 10g client network
> admin
> location and not the ODAC client location.
> . Made sure the Oracle 10g client bin folder is first in the System Path
> variable. Move the ODAC bin location to the second spot in the Path
> variable.
> . Copied the sqlnet.ora, ldap.ora, and tnsnames.ora files from the Oracle
> 10g client network/admin folder to the ODAC network/admin folder.
>
> When I tried to create a connection in SSIS using the Oracle OLE DB
> Provider, I was getting an ORA-12157 protocol not loadable error but I was
> able to resolve it by taking the steps listed above. Now I'm stuck with
> the
> famous ORA-12154 TNS can't connect error. Everything runs perfectly from
> an
> Oracle client perspective (sqlplus and tnsping). However, SSIS cannot
> make a
> connection to a data source via Oracle OLE DB provider. I'll still
> missing a
> configuration piece somewhere ...
>
> Hope this helps but I may be fighting a losing battle. All of this stuff
> works great on a WXP PC.
>
> Brent
>
>
>
> "David Gray" wrote:
>
>>
>> Hello all,
>>
>> Windows Server 2003 (Enterprise)
>> AMD64 (Opeteron)
>> SQL 2005
>> Oracle 9i
>>
>>
>> Please help. We are running SQL Server 2005 64bit on an Windows 2003
>> Server Machine using AMD Opteron Processors. We are trying to setup
>> linked servers to some Oracle 9i Databases on 32bit servers. We need
>> to install ODBC/OLEDB providers for Oracle to achieve this. we are
>> having difficulty finding out a few things :
>>
>> i. How to install Microsoft OLEDB for Oracle - we have MDAC 2.8
>> installed, but still there is no provider. The question is what is the
>> correct OLEDB provider and how do we get it and is there such a thing
>> as 64bit MDAC ?
>>
>> ii. All literature suggests that 64bit version of these products are
>> only available on Itanium 2 or higher processors. Is there any way to
>> utilise these technologies on 64 bit Opteron.
>>
>> Your help would be much appreciated as we are at our wits end for what
>> is turning out to be quite an expensive project (we are hiring the
>> 64bit server).
>>
>> We currently have Linked servers configured on Win2003 (32bit) server
>> and SQL 2000. These use "Microsoft OLEDB Provider for Oracle". Is
>> this provider available for AMD64 architecture and if so where can we
>> get it?
>>
>> Thanks in advance.
>> Dave
>>

The ORA-12154 TNS can't connect error is due to part of the Oracle Client
trying to access your "Program Files (x86)\oracle" folder, which Oracle is
aware of and hopefully in the process of creating a hotfix for. The reason
is due to the Oracle software not being able to handle the parenthesis in
the folder name. Another reason is you have multiple homes and the default
TNS names needs to be in the 10gR2 network\admin folder, which can be set
using the TNS_NAMES system variable.

If you have an OTN login, see this article:
http://forums.oracle.com/forums/thre...71760&#1271760

Copy below:
VS 2005 / XP 64 Bit OS / ODT
Posted: Apr 12, 2006 8:36 AM Reply


I installed the ODT for VS 2005 beta on a 64 Bit Windows XP machine. I
am unable to connect to a database using the oracle viewer, I receive a
ORA-12154 error.

Also if I build my application for x64 platform, I receive an error
"Could not load file or assembly 'Oracle.DataAccess....".

If I build the application for x86 platform the application will run
and connect to the database (I can also retrieve data from the database).

Are there known issues with the ODT for VS 2005 beta that would
prevent the tools from working when installed on a Windows XP 64 bit OS. I
am assuming this might be the same issue with my application when I try to
build it for x64 platforms?

Thanks



DataDevil

Posts: 7
Registered: 12/21/05
Re: VS 2005 / XP 64 Bit OS / ODT
Posted: Apr 14, 2006 12:00 AM in response to: user502913
Reply


Also getting the same error with beta for VS 2005 on an XP-x64
system.

"An error occurred while opening the connection:
ORA-12154: TNS:could not resolve the connection identifier
specified"

The connection fails with both the Oracle Explorer and the
built-in Visual Studio Server Explorer (same reason/error).

Is the problem with all 64-bit Windows operating systems or is
it just XP?

-iz




user505895

Posts: 2
Registered: 4/25/06
Re: VS 2005 / XP 64 Bit OS / ODT
Posted: May 6, 2006 5:58 AM in response to: user502913
Reply


I have the same question .

can anyone tell me why?

thanks

tom




cshay


Posts: 337
From: Oracle Corp
Registered: 1/10/01
Re: VS 2005 / XP 64 Bit OS / ODT
Posted: May 7, 2006 7:57 AM in response to: user505895
Reply


The Oracle Developer Tools and ODP.NET are only supported on 32
bit Windows.
Christian




meelisk

Posts: 1
Registered: 10/23/00
Re: VS 2005 / XP 64 Bit OS / ODT
Posted: May 8, 2006 3:21 AM in response to: user502913
Reply


from metalink, don't use standard installation path and it's
works:

ORA-12154: TNS:could not resolve the connect identifier
specified
or
ORA-6413: Connection not open.
Cause

64-bit Microsoft OS's install 32-bit applications into the
following location

"C:\Program Files (x86)\..."

rather than the typical location of

"C:\Program Files\..."

This causes an existing networking bug to occur where the
networking layer is unable to parse program locations that contain
parenthesis in the path to the executable which is attempting to connect to
Oracle.

The following bug has been filed to correct this behavior:

Bug 3807408 CANNOT EXTERNALLY AUTHENTICATE USER WITH QUOTE IN
USERNAME


Additional Information
-----------------------

The reason you receive an ORA-12154 vs. an ORA-6413 is generally
due to which programmatic interface you have chosen to use to connect to
Oracle.

The ORA-12154 is the typical error seen when connecting with
up-to-date interfaces using the latest version of the Oracle Call Interface
(OCI):

* Oracle ODBC Driver
* Oracle Provider for OLE DB
* Oracle Objects for OLE
* Oracle Data Provider for .NET (ODP.NET)
* Microsoft's .NET Managed Provider for Oracle

The ORA-6413 is typical of using older interfaces which make
legacy API calls such as Oracle's OCI Version 7 API:

* Microsoft ODBC Driver for Oracle
* Microsoft OLE DB Provider for Oracle

Solution

To resolve this problem try either of the following solutions:

SOLUTION 1:

* Use a version of the Oracle client AND database software that
contains the fix for Bug 3807408. This fix requires that both the client and
database software be patched.

NOTE: Currently this bug has not been resolved. See SOLUTION 2
for now.

SOLUTION 2:

* Find the location of the application that is generating the
error. Check the path to this location and see if it contains any
parenthesis. If so, you must relocate the application to a directory without
any parenthesis in the path.




--
Star Fleet Admiral Q @ your service!

Google is your Friend!
http://www.google.com

[Database Administrator]

Hi Brent,

Thanks for your response. A few more questions if you don't mind...

Are you using 'Linked Servers' within SQL2005 to access your remote
Oracle data? If so which Provider are you selected from the drop down
list in the 'New Linked Server' dialog box.

I've downloaded the files you suggeste which installs the Oracle OLEDB
provider but MS state you need to have "Microsoft OLEDB provider for
Oracle" in order to use Linked servers.

Struggling on but am starting to think we may have to come up with and
intermediate 32bit SQL server to host the connection to Oracle.

Regards
Dave



On Thu, 3 Aug 2006 21:25:33 -0400, "Admiral Q"
wrote:

>"Brent-GPTX" wrote in message
>news:EAE6F6B9-8A62-4C76-B188-450DBA60DC34@microsoft.com...
>>I have installed the x64 Oracle 10g 2.0 client running on a EM64T server w/
>> Windows 2003 and SQL Server 2005 64-bit and it is connecting to remote
>> Oracle
>> databases with no issues. Here is the download site--
>>
>> http://www.oracle.com/technology/sof...inx64soft.html
>>
>> I'm trying to get the 32-bit version of the Oracle ODAC / ODP.NET
>> component
>> to work on this test system so that I build some SSIS packages to transfer
>> data from Oracle to SQL Server. Nothing I've seen so far that states
>> this
>> won't work but I beginning to wonder. Here is the download site for the
>> ODAC
>> / OLE DB stuff--
>>
>> http://www.oracle.com/technology/sof...net/index.html
>>
>> VS 2005 on x64 supposedly provides .NET framework for both 64-bit and
>> 32-bit
>> applications by default. Oracle stated in one of their docs that the
>> 32-bit
>> ODP.NET components will run on x64 system.
>>
>> These are the steps I took so far to get the Oracle components working on
>> the test server--
>>
>>> Installed the x64 Oracle 10g 2.0 client and configured it to
>>> access remote databases. Tested w/ SQLPLUS.
>> . Installed the x86 version of .NET Framework SDK first
>> . Installed from the ODAC version and not the ODP.NET (ODAC w/ developer
>> tools) version
>> . Installed into a new folder under the Oracle product directory
>> . Set up TNS_ADMIN variable to point to the Oracle 10g client network
>> admin
>> location and not the ODAC client location.
>> . Made sure the Oracle 10g client bin folder is first in the System Path
>> variable. Move the ODAC bin location to the second spot in the Path
>> variable.
>> . Copied the sqlnet.ora, ldap.ora, and tnsnames.ora files from the Oracle
>> 10g client network/admin folder to the ODAC network/admin folder.
>>
>> When I tried to create a connection in SSIS using the Oracle OLE DB
>> Provider, I was getting an ORA-12157 protocol not loadable error but I was
>> able to resolve it by taking the steps listed above. Now I'm stuck with
>> the
>> famous ORA-12154 TNS can't connect error. Everything runs perfectly from
>> an
>> Oracle client perspective (sqlplus and tnsping). However, SSIS cannot
>> make a
>> connection to a data source via Oracle OLE DB provider. I'll still
>> missing a
>> configuration piece somewhere ...
>>
>> Hope this helps but I may be fighting a losing battle. All of this stuff
>> works great on a WXP PC.
>>
>> Brent
>>
>>
>>
>> "David Gray" wrote:
>>
>>>
>>> Hello all,
>>>
>>> Windows Server 2003 (Enterprise)
>>> AMD64 (Opeteron)
>>> SQL 2005
>>> Oracle 9i
>>>
>>>
>>> Please help. We are running SQL Server 2005 64bit on an Windows 2003
>>> Server Machine using AMD Opteron Processors. We are trying to setup
>>> linked servers to some Oracle 9i Databases on 32bit servers. We need
>>> to install ODBC/OLEDB providers for Oracle to achieve this. we are
>>> having difficulty finding out a few things :
>>>
>>> i. How to install Microsoft OLEDB for Oracle - we have MDAC 2.8
>>> installed, but still there is no provider. The question is what is the
>>> correct OLEDB provider and how do we get it and is there such a thing
>>> as 64bit MDAC ?
>>>
>>> ii. All literature suggests that 64bit version of these products are
>>> only available on Itanium 2 or higher processors. Is there any way to
>>> utilise these technologies on 64 bit Opteron.
>>>
>>> Your help would be much appreciated as we are at our wits end for what
>>> is turning out to be quite an expensive project (we are hiring the
>>> 64bit server).
>>>
>>> We currently have Linked servers configured on Win2003 (32bit) server
>>> and SQL 2000. These use "Microsoft OLEDB Provider for Oracle". Is
>>> this provider available for AMD64 architecture and if so where can we
>>> get it?
>>>
>>> Thanks in advance.
>>> Dave
>>>
>
>The ORA-12154 TNS can't connect error is due to part of the Oracle Client
>trying to access your "Program Files (x86)\oracle" folder, which Oracle is
>aware of and hopefully in the process of creating a hotfix for. The reason
>is due to the Oracle software not being able to handle the parenthesis in
>the folder name. Another reason is you have multiple homes and the default
>TNS names needs to be in the 10gR2 network\admin folder, which can be set
>using the TNS_NAMES system variable.
>
>If you have an OTN login, see this article:
>http://forums.oracle.com/forums/thre...71760&#1271760
>
>Copy below:
> VS 2005 / XP 64 Bit OS / ODT
> Posted: Apr 12, 2006 8:36 AM Reply
>
>
> I installed the ODT for VS 2005 beta on a 64 Bit Windows XP machine. I
>am unable to connect to a database using the oracle viewer, I receive a
>ORA-12154 error.
>
> Also if I build my application for x64 platform, I receive an error
>"Could not load file or assembly 'Oracle.DataAccess....".
>
> If I build the application for x86 platform the application will run
>and connect to the database (I can also retrieve data from the database).
>
> Are there known issues with the ODT for VS 2005 beta that would
>prevent the tools from working when installed on a Windows XP 64 bit OS. I
>am assuming this might be the same issue with my application when I try to
>build it for x64 platforms?
>
> Thanks
>
>
>
> DataDevil
>
> Posts: 7
> Registered: 12/21/05
> Re: VS 2005 / XP 64 Bit OS / ODT
> Posted: Apr 14, 2006 12:00 AM in response to: user502913
>Reply
>
>
> Also getting the same error with beta for VS 2005 on an XP-x64
>system.
>
> "An error occurred while opening the connection:
> ORA-12154: TNS:could not resolve the connection identifier
>specified"
>
> The connection fails with both the Oracle Explorer and the
>built-in Visual Studio Server Explorer (same reason/error).
>
> Is the problem with all 64-bit Windows operating systems or is
>it just XP?
>
> -iz
>
>
>
>
> user505895
>
> Posts: 2
> Registered: 4/25/06
> Re: VS 2005 / XP 64 Bit OS / ODT
> Posted: May 6, 2006 5:58 AM in response to: user502913
>Reply
>
>
> I have the same question .
>
> can anyone tell me why?
>
> thanks
>
> tom
>
>
>
>
> cshay
>
>
> Posts: 337
> From: Oracle Corp
> Registered: 1/10/01
> Re: VS 2005 / XP 64 Bit OS / ODT
> Posted: May 7, 2006 7:57 AM in response to: user505895
>Reply
>
>
> The Oracle Developer Tools and ODP.NET are only supported on 32
>bit Windows.
> Christian
>
>
>
>
> meelisk
>
> Posts: 1
> Registered: 10/23/00
> Re: VS 2005 / XP 64 Bit OS / ODT
> Posted: May 8, 2006 3:21 AM in response to: user502913
>Reply
>
>
> from metalink, don't use standard installation path and it's
>works:
>
> ORA-12154: TNS:could not resolve the connect identifier
>specified
> or
> ORA-6413: Connection not open.
> Cause
>
> 64-bit Microsoft OS's install 32-bit applications into the
>following location
>
> "C:\Program Files (x86)\..."
>
> rather than the typical location of
>
> "C:\Program Files\..."
>
> This causes an existing networking bug to occur where the
>networking layer is unable to parse program locations that contain
>parenthesis in the path to the executable which is attempting to connect to
>Oracle.
>
> The following bug has been filed to correct this behavior:
>
> Bug 3807408 CANNOT EXTERNALLY AUTHENTICATE USER WITH QUOTE IN
>USERNAME
>
>
> Additional Information
> -----------------------
>
> The reason you receive an ORA-12154 vs. an ORA-6413 is generally
>due to which programmatic interface you have chosen to use to connect to
>Oracle.
>
> The ORA-12154 is the typical error seen when connecting with
>up-to-date interfaces using the latest version of the Oracle Call Interface
>(OCI):
>
> * Oracle ODBC Driver
> * Oracle Provider for OLE DB
> * Oracle Objects for OLE
> * Oracle Data Provider for .NET (ODP.NET)
> * Microsoft's .NET Managed Provider for Oracle
>
> The ORA-6413 is typical of using older interfaces which make
>legacy API calls such as Oracle's OCI Version 7 API:
>
> * Microsoft ODBC Driver for Oracle
> * Microsoft OLE DB Provider for Oracle
>
> Solution
>
> To resolve this problem try either of the following solutions:
>
> SOLUTION 1:
>
> * Use a version of the Oracle client AND database software that
>contains the fix for Bug 3807408. This fix requires that both the client and
>database software be patched.
>
> NOTE: Currently this bug has not been resolved. See SOLUTION 2
>for now.
>
> SOLUTION 2:
>
> * Find the location of the application that is generating the
>error. Check the path to this location and see if it contains any
>parenthesis. If so, you must relocate the application to a directory without
>any parenthesis in the path.

[Database Administrator]

I'm new to SQL Server 2005 so I haven't looked at linked servers yet.

I was able to solve the ORA-12154 problem. I had load both the 32-bit and
64-bit
Oracle 10g clients on the same server (64-bit version needed to enable the DB
connect functionality w/in SAP BW and 32-bit version needed for SSIS which
looks like it can only handle 32-bit objects).

Here is the MSDN forum post on the topic if anyone is interested--
http://forums.microsoft.com/MSDN/Sho...59581&SiteID=1

I loaded the 32-bit version over the ODAC Oracle location and then patched
it with
Oracle patch 5059238.

Good luck,
Brent


"David Gray" wrote:

> Hi Brent,
>
> Thanks for your response. A few more questions if you don't mind...
>
> Are you using 'Linked Servers' within SQL2005 to access your remote
> Oracle data? If so which Provider are you selected from the drop down
> list in the 'New Linked Server' dialog box.
>
> I've downloaded the files you suggeste which installs the Oracle OLEDB
> provider but MS state you need to have "Microsoft OLEDB provider for
> Oracle" in order to use Linked servers.
>
> Struggling on but am starting to think we may have to come up with and
> intermediate 32bit SQL server to host the connection to Oracle.
>
> Regards
> Dave
>
>
>
> On Thu, 3 Aug 2006 21:25:33 -0400, "Admiral Q"
> wrote:
>
> >"Brent-GPTX" wrote in message
> >news:EAE6F6B9-8A62-4C76-B188-450DBA60DC34@microsoft.com...
> >>I have installed the x64 Oracle 10g 2.0 client running on a EM64T server w/
> >> Windows 2003 and SQL Server 2005 64-bit and it is connecting to remote
> >> Oracle
> >> databases with no issues. Here is the download site--
> >>
> >> http://www.oracle.com/technology/sof...inx64soft.html
> >>
> >> I'm trying to get the 32-bit version of the Oracle ODAC / ODP.NET
> >> component
> >> to work on this test system so that I build some SSIS packages to transfer
> >> data from Oracle to SQL Server. Nothing I've seen so far that states
> >> this
> >> won't work but I beginning to wonder. Here is the download site for the
> >> ODAC
> >> / OLE DB stuff--
> >>
> >> http://www.oracle.com/technology/sof...net/index.html
> >>
> >> VS 2005 on x64 supposedly provides .NET framework for both 64-bit and
> >> 32-bit
> >> applications by default. Oracle stated in one of their docs that the
> >> 32-bit
> >> ODP.NET components will run on x64 system.
> >>
> >> These are the steps I took so far to get the Oracle components working on
> >> the test server--
> >>
> >>> Installed the x64 Oracle 10g 2.0 client and configured it to
> >>> access remote databases. Tested w/ SQLPLUS.
> >> . Installed the x86 version of .NET Framework SDK first
> >> . Installed from the ODAC version and not the ODP.NET (ODAC w/ developer
> >> tools) version
> >> . Installed into a new folder under the Oracle product directory
> >> . Set up TNS_ADMIN variable to point to the Oracle 10g client network
> >> admin
> >> location and not the ODAC client location.
> >> . Made sure the Oracle 10g client bin folder is first in the System Path
> >> variable. Move the ODAC bin location to the second spot in the Path
> >> variable.
> >> . Copied the sqlnet.ora, ldap.ora, and tnsnames.ora files from the Oracle
> >> 10g client network/admin folder to the ODAC network/admin folder.
> >>
> >> When I tried to create a connection in SSIS using the Oracle OLE DB
> >> Provider, I was getting an ORA-12157 protocol not loadable error but I was
> >> able to resolve it by taking the steps listed above. Now I'm stuck with
> >> the
> >> famous ORA-12154 TNS can't connect error. Everything runs perfectly from
> >> an
> >> Oracle client perspective (sqlplus and tnsping). However, SSIS cannot
> >> make a
> >> connection to a data source via Oracle OLE DB provider. I'll still
> >> missing a
> >> configuration piece somewhere ...
> >>
> >> Hope this helps but I may be fighting a losing battle. All of this stuff
> >> works great on a WXP PC.
> >>
> >> Brent
> >>
> >>
> >>
> >> "David Gray" wrote:
> >>
> >>>
> >>> Hello all,
> >>>
> >>> Windows Server 2003 (Enterprise)
> >>> AMD64 (Opeteron)
> >>> SQL 2005
> >>> Oracle 9i
> >>>
> >>>
> >>> Please help. We are running SQL Server 2005 64bit on an Windows 2003
> >>> Server Machine using AMD Opteron Processors. We are trying to setup
> >>> linked servers to some Oracle 9i Databases on 32bit servers. We need
> >>> to install ODBC/OLEDB providers for Oracle to achieve this. we are
> >>> having difficulty finding out a few things :
> >>>
> >>> i. How to install Microsoft OLEDB for Oracle - we have MDAC 2.8
> >>> installed, but still there is no provider. The question is what is the
> >>> correct OLEDB provider and how do we get it and is there such a thing
> >>> as 64bit MDAC ?
> >>>
> >>> ii. All literature suggests that 64bit version of these products are
> >>> only available on Itanium 2 or higher processors. Is there any way to
> >>> utilise these technologies on 64 bit Opteron.
> >>>
> >>> Your help would be much appreciated as we are at our wits end for what
> >>> is turning out to be quite an expensive project (we are hiring the
> >>> 64bit server).
> >>>
> >>> We currently have Linked servers configured on Win2003 (32bit) server
> >>> and SQL 2000. These use "Microsoft OLEDB Provider for Oracle". Is
> >>> this provider available for AMD64 architecture and if so where can we
> >>> get it?
> >>>
> >>> Thanks in advance.
> >>> Dave
> >>>
> >
> >The ORA-12154 TNS can't connect error is due to part of the Oracle Client
> >trying to access your "Program Files (x86)\oracle" folder, which Oracle is
> >aware of and hopefully in the process of creating a hotfix for. The reason
> >is due to the Oracle software not being able to handle the parenthesis in
> >the folder name. Another reason is you have multiple homes and the default
> >TNS names needs to be in the 10gR2 network\admin folder, which can be set
> >using the TNS_NAMES system variable.
> >
> >If you have an OTN login, see this article:
> >http://forums.oracle.com/forums/thre...71760&#1271760
> >
> >Copy below:
> > VS 2005 / XP 64 Bit OS / ODT
> > Posted: Apr 12, 2006 8:36 AM Reply
> >
> >
> > I installed the ODT for VS 2005 beta on a 64 Bit Windows XP machine. I
> >am unable to connect to a database using the oracle viewer, I receive a
> >ORA-12154 error.
> >
> > Also if I build my application for x64 platform, I receive an error
> >"Could not load file or assembly 'Oracle.DataAccess....".
> >
> > If I build the application for x86 platform the application will run
> >and connect to the database (I can also retrieve data from the database).
> >
> > Are there known issues with the ODT for VS 2005 beta that would
> >prevent the tools from working when installed on a Windows XP 64 bit OS. I
> >am assuming this might be the same issue with my application when I try to
> >build it for x64 platforms?
> >
> > Thanks
> >
> >
> >
> > DataDevil
> >
> > Posts: 7
> > Registered: 12/21/05
> > Re: VS 2005 / XP 64 Bit OS / ODT
> > Posted: Apr 14, 2006 12:00 AM in response to: user502913
> >Reply
> >
> >
> > Also getting the same error with beta for VS 2005 on an XP-x64
> >system.
> >
> > "An error occurred while opening the connection:
> > ORA-12154: TNS:could not resolve the connection identifier
> >specified"
> >
> > The connection fails with both the Oracle Explorer and the
> >built-in Visual Studio Server Explorer (same reason/error).
> >
> > Is the problem with all 64-bit Windows operating systems or is
> >it just XP?
> >
> > -iz
> >
> >
> >
> >
> > user505895
> >
> > Posts: 2
> > Registered: 4/25/06
> > Re: VS 2005 / XP 64 Bit OS / ODT
> > Posted: May 6, 2006 5:58 AM in response to: user502913
> >Reply
> >
> >
> > I have the same question .
> >
> > can anyone tell me why?
> >
> > thanks
> >
> > tom
> >
> >
> >
> >
> > cshay
> >
> >
> > Posts: 337
> > From: Oracle Corp
> > Registered: 1/10/01
> > Re: VS 2005 / XP 64 Bit OS / ODT
> > Posted: May 7, 2006 7:57 AM in response to: user505895
> >Reply
> >
> >
> > The Oracle Developer Tools and ODP.NET are only supported on 32
> >bit Windows.
> > Christian
> >
> >
> >
> >
> > meelisk
> >
> > Posts: 1
> > Registered: 10/23/00
> > Re: VS 2005 / XP 64 Bit OS / ODT
> > Posted: May 8, 2006 3:21 AM in response to: user502913
> >Reply
> >
> >
> > from metalink, don't use standard installation path and it's
> >works:
> >
> > ORA-12154: TNS:could not resolve the connect identifier
> >specified
> > or
> > ORA-6413: Connection not open.
> > Cause
> >
> > 64-bit Microsoft OS's install 32-bit applications into the
> >following location
> >
> > "C:\Program Files (x86)\..."
> >
> > rather than the typical location of
> >
> > "C:\Program Files\..."
> >
> > This causes an existing networking bug to occur where the
> >networking layer is unable to parse program locations that contain
> >parenthesis in the path to the executable which is attempting to connect to
> >Oracle.
> >
> > The following bug has been filed to correct this behavior:
> >
> > Bug 3807408 CANNOT EXTERNALLY AUTHENTICATE USER WITH QUOTE IN
> >USERNAME
> >
> >
> > Additional Information
> > -----------------------
> >
> > The reason you receive an ORA-12154 vs. an ORA-6413 is generally
> >due to which programmatic interface you have chosen to use to connect to
> >Oracle.
> >
> > The ORA-12154 is the typical error seen when connecting with
> >up-to-date interfaces using the latest version of the Oracle Call Interface
> >(OCI):
> >
> > * Oracle ODBC Driver
> > * Oracle Provider for OLE DB
> > * Oracle Objects for OLE
> > * Oracle Data Provider for .NET (ODP.NET)
> > * Microsoft's .NET Managed Provider for Oracle
> >
> > The ORA-6413 is typical of using older interfaces which make
> >legacy API calls such as Oracle's OCI Version 7 API:
> >
> > * Microsoft ODBC Driver for Oracle
> > * Microsoft OLE DB Provider for Oracle
> >
> > Solution
> >
> > To resolve this problem try either of the following solutions:
> >
> > SOLUTION 1:
> >
> > * Use a version of the Oracle client AND database software that
> >contains the fix for Bug 3807408. This fix requires that both the client and
> >database software be patched.
> >
> > NOTE: Currently this bug has not been resolved. See SOLUTION 2
> >for now.
> >
> > SOLUTION 2: