January 21, 2010 at 4:37 pm
I am doing an BEGIN TRANSACTION in Stored Procedure in SQL 2005
I am using an OPEN QUERY Call to an ORACLE Stored Procedure thru a Linked Server using MSDAORA OLEDB Driver
Functions work fine.
when attemting a ROLLBACK it is not rolling back on the ORACLE side
CAN YOU HELP?
January 22, 2010 at 5:54 am
This is a distributed transaction so you have to initiate it by issuing "BEGIN DISTRIBUTED TRANSACTION" ... check BOL for details 😉
_____________________________________
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.January 23, 2010 at 8:59 am
January 23, 2010 at 9:00 am
January 25, 2010 at 8:30 am
Thanks everyone for you comments.
I have solved the issue.
It had to do with the registry for MSDTC did not have the proper names of the ORACLE OLEDB Provider DLL's.
I believe the ORACLE 10g Client install should have updated these setting but did not.
Regards
Michael J. Hilligas
February 26, 2010 at 2:11 pm
rojen83 (1/23/2010)
When working with linked SQL Server tables, Office Access tries to create a ... against linked SQL Server tables can be updatable even if they do not select the .
:blink:
_____________________________________
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.February 26, 2010 at 2:12 pm
mhilligas (1/25/2010)
Thanks everyone for you comments.I have solved the issue.
It had to do with the registry for MSDTC did not have the proper names of the ORACLE OLEDB Provider DLL's.
I believe the ORACLE 10g Client install should have updated these setting but did not.
Regards
Michael J. Hilligas
Michael, Thank you for the feedback - sooner or later your post will benefit another person facing the same issue.
_____________________________________
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.Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply