October 6, 2008 at 4:13 am
Hi Guys,
Does any body have any idea about the below error:
The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction.
What can possible reasons for such an error from an SP which is performing a data update on somewhere around 70K rows.
PS: YES, ALL MY CODE IS WRAPPED IN TRANSACTIONS.
October 6, 2008 at 4:19 am
arjun.tewari (10/6/2008)
Hi Guys,Does any body have any idea about the below error:
The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction.
What can possible reasons for such an error from an SP which is performing a data update on somewhere around 70K rows.
PS: YES, ALL MY CODE IS WRAPPED IN TRANSACTIONS.
Hey,
Sounds like you have a failed transaction within a TRY..CATCH block, which is causing overall transaction to fail. What are you trying to do within your transaction? In event of a failure, are you rolling-back the transaction? Also, as others have indicated, do you have enough log file space?
Thanks,
Phillip Cox
October 6, 2008 at 4:21 am
arjun.tewari (10/6/2008)
Hi Guys,Does any body have any idea about the below error:
The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction.
What can possible reasons for such an error from an SP which is performing a data update on somewhere around 70K rows.
PS: YES, ALL MY CODE IS WRAPPED IN TRANSACTIONS.
It could be that you ran out of space in the log file. You try and find out the exact error by modifying the catch block so it will show you all the error’s details or by using the profiler and catch the exceptions.
Adi
--------------------------------------------------------------
To know how to ask questions and increase the chances of getting asnwers:
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
October 6, 2008 at 4:26 am
I just got the error myself. There was a call made to an external procedure with in the proc. This call was also wrapped in the transaction and was covered by TRY... CATCH. This proc was failing and was responsible for the damage. :D. Anyways, Thanks a ton guys.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply