Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

LINK SERVER ERROR FROM SQL TO ORACLE using ODAC component Expand / Collapse
Author
Message
Posted Wednesday, February 1, 2012 3:31 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Thursday, March 27, 2014 4:36 PM
Points: 11, Visits: 125
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.
Post #1244943
Posted Monday, February 6, 2012 6:47 AM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Tuesday, January 28, 2014 8:15 AM
Points: 3,068, Visits: 4,639
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.
Post #1247305
Posted Wednesday, February 22, 2012 2:41 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, April 17, 2012 4:41 AM
Points: 3, Visits: 20
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
Post #1255795
Posted Wednesday, February 22, 2012 9:26 AM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Wednesday, July 16, 2014 3:55 PM
Points: 3,084, Visits: 1,431
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
Post #1256095
Posted Friday, April 13, 2012 1:37 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, April 13, 2012 1:34 AM
Points: 1, Visits: 0
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?
Post #1282946
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse