September 8, 2011 at 6:25 am
SQL 2008 SP1
Msg 3316, Level 21, State 2, Line 135During undo of a logged operation in database 'Remi', an error occurred at log record ID (101945:2157:177). The row was not found. Restore the database from a full backup, or repair the database.
Msg 3314, Level 21, State 4, Line 135
During undoing of a logged operation in database 'Remi', an error occurred at log record ID (101945:2157:177). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.
Msg 9001, Level 21, State 1, Line 135
The log for database 'Remi' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
Msg 3314, Level 21, State 5, Line 135
During undoing of a logged operation in database 'Remi', an error occurred at log record ID (101944:25130:1). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.
Msg 0, Level 20, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.
Database is marked suspect. I will make sure to post this again on the Connect item.
EDIT: On a whim, I changed some of the SELECT ... INTOs into INSERT statements and ran each statement individually. Nothing failed until I hit the Rollback statement. At that point, I got the failures and the database turned into suspect, just like before.
September 8, 2011 at 6:39 am
Brandie Tarvin (9/8/2011)
SQL 2008 SP1
Msg 3316, Level 21, State 2, Line 135During undo of a logged operation in database 'Remi', an error occurred at log record ID (101945:2157:177). The row was not found. Restore the database from a full backup, or repair the database.
Msg 3314, Level 21, State 4, Line 135
During undoing of a logged operation in database 'Remi', an error occurred at log record ID (101945:2157:177). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.
Msg 9001, Level 21, State 1, Line 135
The log for database 'Remi' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
Msg 3314, Level 21, State 5, Line 135
During undoing of a logged operation in database 'Remi', an error occurred at log record ID (101944:25130:1). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.
Msg 0, Level 20, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.
Database is marked suspect. I will make sure to post this again on the Connect item.
EDIT: On a whim, I changed some of the SELECT ... INTOs into INSERT statements and ran each statement individually. Nothing failed until I hit the Rollback statement. At that point, I got the failures and the database turned into suspect, just like before.
Thanks.
I needed this for product support (when you call directly MS). They are the ones handling the case now. The bug's now at the programmer level. What I don't link is the shorter repro script that MS made, it doesn't fail with begin tran, but mine does.
September 8, 2011 at 6:44 am
Brandie Tarvin (9/8/2011)
SQL 2008 SP1
Msg 3316, Level 21, State 2, Line 135During undo of a logged operation in database 'Remi', an error occurred at log record ID (101945:2157:177). The row was not found. Restore the database from a full backup, or repair the database.
Msg 3314, Level 21, State 4, Line 135
During undoing of a logged operation in database 'Remi', an error occurred at log record ID (101945:2157:177). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.
Msg 9001, Level 21, State 1, Line 135
The log for database 'Remi' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
Msg 3314, Level 21, State 5, Line 135
During undoing of a logged operation in database 'Remi', an error occurred at log record ID (101944:25130:1). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.
Msg 0, Level 20, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.
Database is marked suspect. I will make sure to post this again on the Connect item.
EDIT: On a whim, I changed some of the SELECT ... INTOs into INSERT statements and ran each statement individually. Nothing failed until I hit the Rollback statement. At that point, I got the failures and the database turned into suspect, just like before.
Saw the edit too late :-D.
Yes this is the behavior I'm seeing. I can throw all the dml and ddl I want in there and I see no problem. It's definitetly when I hit rollback that all hell breaks loose.
Ironically enough, commits works :-D.
December 16, 2011 at 5:39 am
Ninja's_RGR'us (8/19/2011)
Issue posted on connect
As of today, closed as won't fix!!!
You know, it's not like it causes corruption and kills your prod db or anything that serious :sick:
Time to speak up if you're as disgusted as I am.
Viewing 4 posts - 76 through 78 (of 78 total)
You must be logged in to reply to this topic. Login to reply