LINK SERVER ERROR FROM SQL TO ORACLE using ODAC component

Question

LINK SERVER ERROR FROM SQL TO ORACLE using ODAC component

gajananhatkar

Mr or Mrs. 500

Points: 541
More actions
February 1, 2012 at 3:31 am

#256023

OLE DB provider "OraOLEDB.Oracle" for linked server "ORAFINNONE" returned message "New transaction cannot enlist in the specified transaction coordinator. ".
Msg 7391, Level 16, State 2, Line 1
The operation could not be performed because OLE DB provider "OraOLEDB.Oracle" for linked server "ORAFINNONE" was unable to begin a distributed transaction.

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

PaulB-TheOneAndOnly SSC Guru Points: 66772 More actions · Answer 1

gajananhatkar (2/1/2012)
OLE DB provider "OraOLEDB.Oracle" for linked server "ORAFINNONE" returned message "New transaction cannot enlist in the specified transaction coordinator. ".
Msg 7391, Level 16, State 2, Line 1
The operation could not be performed because OLE DB provider "OraOLEDB.Oracle" for linked server "ORAFINNONE" was unable to begin a distributed transaction.

http://support.microsoft.com/kb/887111

_____________________________________
Pablo (Paul) Berzukov

Author of Understanding Database Administration available at Amazon and other bookstores.

Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.

ramprasad1485 Valued Member Points: 59 More actions · Answer 2

Hi Gajanan.

Verify that your network name resolution works. Verify that the servers can communicate with one another by name, not just by IP address. Check in both directions (for example, from server A to server B and from server B to server A). You must resolve all name resolution problems on the network before you run your distributed query. This may involve updating WINS, DNS, or LMHost files.

i think helpful this below link.

http://support.microsoft.com/kb/306212

.

http://support.microsoft.com/kb/922430

Ignacio A. Salom Rangel SSC-Insane Points: 20443 More actions · Answer 3

Could you please let us know if you were able to solve the issue? and if so could you please mention how you did it? Thanks in advance!

My blog

wim 18116 SSC Enthusiast Points: 103 More actions · Answer 4

Anyone found a solution for this issue? I'm facing a similar/the same problem:

I'm executing a SQL2008 stored procedure, which executes a SQL2005 stored procedure (via LINKED SERVER), which, in turn, executes a SELECT on an Oracle DB on a UNIX server (also via LINKED SERVER).

I get the same error:

{"The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction.\rPR_PTT_GET_LOTTRACE_PRM, Msg 7391, Line 1: The operation could not be performed because OLE DB provider \"MSDAORA\" for linked server \"U03P\" was unable to begin a distributed transaction. ((null))\rTransaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = 1, current count = 0."}

Any ideas?