Oracle Linked Server on Windows 2003

We have SQL 2000 SP3a installed on a Windows 2003 server.
We are trying to add an Oracle 8.1.7 linked server.
On W2003, the error message below appears when trying to view tables with th
e exact same connection parameters work on several servers that are running
SQL 2000 on Windows 2000.
Parameters are
Other Data Source: Microsoft OLE DB Provider for Oracle
Product name: Oracle
Data Source: <same as on working W2K server>
Data Source: <same as on working W2K server>
Server Options: Data Access, RPC, RPC Out, Use Remote Collation enabled
Be made in this security context: <same Username/PW that are working on W2K
server>
Error message:
Error 7399: OLE DB provider 'MSDAORA' reported an error.
OLE DB error trace [OLE/DB Provider 'MSDAORA' IDBInitialize::Initialize
returned 0x80004005: ].
How can we get SQL 2000 on W2003 to link to the Oracle server?Did you restart the server after installing the Oracle client?
The recommended steps are:
1. Install Oracle client
2. Reinstall MDAC
3. Reboot the server
Also you cannot use multiple Oracle homes, this is not supported from
the OLE DB provider.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!|||Hi,
I am having an issue while trying to install the Orcale Client 8.1.7 on a
Windows 2003 Server Standard Edition...Nothing happens and the install
doesn't complete? Is there a switch I need to check to allow the
installation?
Thanks,
Warren
"mt69clp" wrote:

> Did you restart the server after installing the Oracle client?
> The recommended steps are:
> 1. Install Oracle client
> 2. Reinstall MDAC
> 3. Reboot the server
> Also you cannot use multiple Oracle homes, this is not supported from
> the OLE DB provider.
>
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
>|||Why do you choose Client 8.1.7? Try installing the newest 9.X client. It
is backward compatible and you will have less trouble wit Windows 2003.
The 10.X should do it also but I think it is not tested by Microsoft
until now.
I use the 9.0.1.0 client to connect to a 8.1.7.4 database and it works
fine.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!|||Hi,
I tried to install the 9.x Client and still can't. I don't get an error, it
just says press next once the installation is complete and it just stops? I
s
there a setting in Windows 2003 server that I need to address to allow the
install?
Thanks,
Warren
"mt69clp" wrote:

> Why do you choose Client 8.1.7? Try installing the newest 9.X client. It
> is backward compatible and you will have less trouble wit Windows 2003.
> The 10.X should do it also but I think it is not tested by Microsoft
> until now.
> I use the 9.0.1.0 client to connect to a 8.1.7.4 database and it works
> fine.
>
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
>|||Hello, I was wondering if anyone was able to run the Oracle 8i v8.1.7 databa
se on the Windows 2003 Server? Also, do you know where i could find additio
nal information for other applications (such as Websphere 5.0.2 and the J2EE
Architecture) running on Windows 2003 Server? Any help is appreciated.
Thanks,
Jason

quote:

---

Originally posted by mt69clp
Why do you choose Client 8.1.7? Try installing the newest 9.X client. It
is backward compatible and you will have less trouble wit Windows 2003.
The 10.X should do it also but I think it is not tested by Microsoft
until now.
I use the 9.0.1.0 client to connect to a 8.1.7.4 database and it works
fine.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!

---

|||I just opened a crit sit with MS with regards to this issue. Here is
how to fix it with Windows 2003, SQL 2000, and Oracle 9i:
This is discussed in Q193893 and according to this the registry key "
& #91;HKEY_LOCAL_MACHINE\SOFTWARE\Microsof
t\MSDTC\MTxOCI] " should have
following
entries.
"OracleXaLib"="oraclient9.dll"
"OracleSqlLib"="orasql9.dll"
"OracleOciLib"="oci.dll"
I hope this helps.
Carrie
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!

Oracle linked server

Hello,
I have a SQL 2003 SP3a on Windows 2003 and am connecting to an Oracle 9i
database.
I've set up the linked server and necessary permissions and it has been
working successfully for months. However occasionally after rebooting the
machine I receive this message when attempting a query from the linked
server:
Server: Msg 7399, Level 16, State 1, Line 3
OLE DB provider 'MSDAORA' reported an error.
[OLE/DB provider returned message: Oracle client and networking components
were not found. These components are supplied by Oracle Corporation and are
part of the Oracle Version 7.3.3 or later client software installation.
Provider is unable to function until these components are installed.]
OLE DB error trace [OLE/DB Provider 'MSDAORA' IDBInitialize::Initialize
returned 0x80004005: ].
I can still connect successfully through either Oracle Net Configuration
Assistant or an ODBC DSN and the only way I know how to solve this is by
stopping and restarting the SQL Server instance. The only thing I can think
of is that during server startup, the SQL Service gets started before the
oracle service starts, and somehow SQL caches this connection.
Has anyone experienced this? If so, what's the best way to deal with this
without stopping the server?
Thank you,
Aaron Lowe
In some similar situations, reinstalling the Oracle client
on the server when logged in using the service account has
fixed this issue.
-Sue
On Tue, 12 Apr 2005 10:28:46 -0500, "Aaron M. Lowe"
<alowe@.uic.edu> wrote:

>Hello,
>I have a SQL 2003 SP3a on Windows 2003 and am connecting to an Oracle 9i
>database.
>I've set up the linked server and necessary permissions and it has been
>working successfully for months. However occasionally after rebooting the
>machine I receive this message when attempting a query from the linked
>server:
>Server: Msg 7399, Level 16, State 1, Line 3
>OLE DB provider 'MSDAORA' reported an error.
>[OLE/DB provider returned message: Oracle client and networking components
>were not found. These components are supplied by Oracle Corporation and are
>part of the Oracle Version 7.3.3 or later client software installation.
>Provider is unable to function until these components are installed.]
>OLE DB error trace [OLE/DB Provider 'MSDAORA' IDBInitialize::Initialize
>returned 0x80004005: ].
>I can still connect successfully through either Oracle Net Configuration
>Assistant or an ODBC DSN and the only way I know how to solve this is by
>stopping and restarting the SQL Server instance. The only thing I can think
>of is that during server startup, the SQL Service gets started before the
>oracle service starts, and somehow SQL caches this connection.
>Has anyone experienced this? If so, what's the best way to deal with this
>without stopping the server?
>Thank you,
>Aaron Lowe
>

Oracle linked server

Hello,
I have a SQL 2003 SP3a on Windows 2003 and am connecting to an Oracle 9i
database.
I've set up the linked server and necessary permissions and it has been
working successfully for months. However occasionally after rebooting the
machine I receive this message when attempting a query from the linked
server:
Server: Msg 7399, Level 16, State 1, Line 3
OLE DB provider 'MSDAORA' reported an error.
[OLE/DB provider returned message: Oracle client and networking componen
ts
were not found. These components are supplied by Oracle Corporation and are
part of the Oracle Version 7.3.3 or later client software installation.
Provider is unable to function until these components are installed.]
OLE DB error trace [OLE/DB Provider 'MSDAORA' IDBInitialize::Initialize
returned 0x80004005: ].
I can still connect successfully through either Oracle Net Configuration
Assistant or an ODBC DSN and the only way I know how to solve this is by
stopping and restarting the SQL Server instance. The only thing I can think
of is that during server startup, the SQL Service gets started before the
oracle service starts, and somehow SQL caches this connection.
Has anyone experienced this? If so, what's the best way to deal with this
without stopping the server?
Thank you,
Aaron LoweIn some similar situations, reinstalling the Oracle client
on the server when logged in using the service account has
fixed this issue.
-Sue
On Tue, 12 Apr 2005 10:28:46 -0500, "Aaron M. Lowe"
<alowe@.uic.edu> wrote:

>Hello,
>I have a SQL 2003 SP3a on Windows 2003 and am connecting to an Oracle 9i
>database.
>I've set up the linked server and necessary permissions and it has been
>working successfully for months. However occasionally after rebooting the
>machine I receive this message when attempting a query from the linked
>server:
>Server: Msg 7399, Level 16, State 1, Line 3
>OLE DB provider 'MSDAORA' reported an error.
>[OLE/DB provider returned message: Oracle client and networking compone
nts
>were not found. These components are supplied by Oracle Corporation and are
>part of the Oracle Version 7.3.3 or later client software installation.
>Provider is unable to function until these components are installed.]
>OLE DB error trace [OLE/DB Provider 'MSDAORA' IDBInitialize::Initialize
>returned 0x80004005: ].
>I can still connect successfully through either Oracle Net Configuration
>Assistant or an ODBC DSN and the only way I know how to solve this is by
>stopping and restarting the SQL Server instance. The only thing I can think
>of is that during server startup, the SQL Service gets started before the
>oracle service starts, and somehow SQL caches this connection.
>Has anyone experienced this? If so, what's the best way to deal with this
>without stopping the server?
>Thank you,
>Aaron Lowe
>