January 9, 2012 at 5:32 am
I got below error in SQL server error . any help on this?
During undoing of a logged operation in database Dbname, an error occurred at log record ID (605859:16:154). 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.
January 9, 2012 at 5:35 am
is your database in suspect status?
Which version of sql server that you are using ?
January 9, 2012 at 12:29 pm
See if this helps
January 9, 2012 at 12:35 pm
Exactly what it says...
Satya_0000 (1/9/2012)
During undoing of a logged operation in database Dbname, an error occurred at log record ID (605859:16:154). 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.
You've got corruption in the transaction log, your database is likely suspect at this point. You won't be able to take a tail-log backup (because of the corruption) so restore full backup, the last differential if you're using them, then all log backups up to the last one you took.
Also, do some analysis of the IO subsystem, corruption is typically a problem of the IO subsystem
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 9, 2012 at 12:57 pm
GilaMonster (1/9/2012)
Exactly what it says...Satya_0000 (1/9/2012)
During undoing of a logged operation in database Dbname, an error occurred at log record ID (605859:16:154). 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.You've got corruption in the transaction log, your database is likely suspect at this point. You won't be able to take a tail-log backup (because of the corruption) so restore full backup, the last differential if you're using them, then all log backups up to the last one you took.
Also, do some analysis of the IO subsystem, corruption is typically a problem of the IO subsystem
Not necessarily. There is at least one known bug that can lead to these messages being logged, without IO problems, and without needing to restore the database. Reproduction script below:
USE master
CREATE DATABASE Bang
-- One or both of these options must be ON
ALTER DATABASE Bang SET ALLOW_SNAPSHOT_ISOLATION ON
ALTER DATABASE Bang SET READ_COMMITTED_SNAPSHOT ON
-- To show versioning not explicitly requested
SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED
GO
USE Bang
CREATE TABLE dbo.Test
(
col1 INTEGER NOT NULL,
col2 INTEGER NOT NULL,
col3 INTEGER NOT NULL
)
-- col2 is leading key in a multi-column clustered index
-- no problem if index is not clustered, uniqueness not important
CREATE CLUSTERED INDEX cx ON dbo.Test (col2, col3, col1)
-- Must add a row to initialize (error does not occur otherwise)
INSERT dbo.Test (col1, col2, col3) VALUES (0, 0, 0)
BEGIN TRANSACTION -- Txn required
-- Add a column
ALTER TABLE dbo.Test ADD col4 INTEGER NULL
GO
-- Update the new column
UPDATE dbo.Test SET col4 = 0
-- Redefine cx key to allow NULL
ALTER TABLE dbo.Test ALTER COLUMN col2 INTEGER NULL
GO
-- Add a row with NULL in key column
INSERT dbo.Test (col1, col2, col3)
VALUES (0, NULL, 0)
ROLLBACK -- Bang!
GO
-- Reconnect, and clean up
USE master
ALTER DATABASE Bang SET SINGLE_USER WITH ROLLBACK IMMEDIATE
DROP DATABASE Bang
Paul White
SQLPerformance.com
SQLkiwi blog
@SQL_Kiwi
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply