July 11, 2006 at 10:30 am
I have created a Linked Server on a Windows 2003 server with MSSQL2000 server running. I installed the oracle client tools (oracle 9.1) and made the following registry updates.
HKEY_LOCAL_MACHINE\software\microsoft\msdtc\mtxoci
oracleOcLIB (data) oci.dll
OracleSqlLib (data) orasql9.dll
OracleXaLib (data) oraclient9.dll
The TNSORA_Name is correct in the system environment variables. I can launch pl/sql and connect to the db with the same username as I use in the linked server.
I have the exact server set up on a replica server that I use for TEST and it works correctly. The problem I have is in PROD. But, I have had it working fine for about 2 years. Then about a month or two ago, for whatever reason, the linked server quits and I receive the below error:
Error 7399: OLEDB providor 'MSDAORA' reported an error: OLE DB error trace [OLE/DB Provider 'MSDAORA' IDBinitialize::initalize returned 0x80004005:]
The set up I used when creating the linked server (and worked for 2 years and on TEST are below)
Product Name: Microsoft OLEDB Provider for Oracle
Product Name: Oracle
Data Source: PROD
Provider string: MSDAORA
In the security tab I have the last option and hard code the username and pwd.
Has any experienced this problem. I just don't understand how it can work for 2 years and just not one day. Have I missed something? Any help is greatly appreciated.
July 12, 2006 at 7:51 am
0x80004005 is access denied. This is definitely a permissions problem. Verify that the username and password are correct and that the user account is working properly on your Oracle server. Also, you can look at this MSKB article for other troubleshooting steps:
http://support.microsoft.com/kb/280106/EN-US/
Joshua Perry
http://www.greenarrow.net
June 3, 2008 at 8:12 am
Hello,
Any update on this problem?
Were you able to solve it?
We have the same problem.
Regards,
Hugo.
June 4, 2008 at 12:37 am
Try to ping the URL / IP address which you have entered into TNSNames.ORA and check the PORT and connect data have entered correctly. If it gives response check the Username and Password credentials for that linked server.
Hope this helps
[font="Comic Sans MS"]Sara[/font]
A ship in the harbour is safe . . . but that's not what ships were made for. 😀
June 4, 2008 at 2:38 am
Hello,
The linked servers sometimes work and sometimes don't...
When they don't work we restart the server and they start working again. :ermm: we can't explain it...
I can tnsping and sqlplus to the oracle database server.
I've already asked Microsoft for support and we're trying somethings, I'll let you know what, if it works.
🙂
regards
Hugo
June 4, 2008 at 12:38 pm
It might be solved by increasing the mem to leave area to 512mb instead of the default 128mb.
-g 512
July 30, 2008 at 3:34 pm
We have had the same issue and narrowed it down to the installation of security patch KB948111. When we remove the patch, the linked server connection works. We are talking with Microsoft to try to determine why this is happening.
Michael
August 27, 2008 at 2:50 am
Hello,
We still haven't found a solution, however today I discover something.
To me this always seemed to be a network problem, and lately I've found out that the tnsnames.ora has a domain set that exists, but only as a "backup zone" on "another" server (network admin lingo... :crazy: ), therefore dns querys of the servers (instances) in the tnsnames.ora take a little longer. This can be the problem, or not... I'm having trouble finding out because this only happens on a production server.
Regards,
Hugo
P.S. - We didn't installed security patch KB948111
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply