Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 General SQL Server Forums
 Data Corruption Issues
 Msg 2515 and Msg 7995

Author  Topic 

bsockel
Starting Member

1 Post

Posted - 2007-04-26 : 00:40:26
We have a SQL 2005 Server Running on A win2k SP4 Box. we have a gotten some db corruption and not sure how to fix it, or if it can be fixed.

Here is the output from the DBCC CheckDB:

DBCC results for 'GIS2_Ltd__MSCRM'.
Msg 2515, Level 16, State 1, Line 1
Page (1:35326), object ID 4, index ID 1, partition ID 262144, alloc unit ID 262144 type In-row data) has been modified but is not marked modified in the differential backup bitmap.
The repair level on the DBCC statement caused this repair to be bypassed.
There are de6733 rows in 70 pages for object "sys.sysrowsetcolumns".
CHECKDB found 0 allocation errors and 1 consistency errors in table 'sys.sysrowsetcolumns' (object ID 4).
Msg 7995, Level 16, State 1, Line 1
Database 'GIS2_Ltd__MSCRM': consistency errors in system catalogs prevent further DBCC checkdb processing.
CHECKDB found 0 allocation errors and 1 consistency errors in table 'ALLOCATION' (object ID 99).
CHECKDB found 0 allocation errors and 2 consistency errors in database 'GIS2_Ltd__MSCRM'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (GIS2_Ltd__MSCRM, repair_rebuild).
DBCC execution completed. If DBCC printed error messages, contact your system administrator.

We noticed the problem this afternoon, but appears to be going back to saturday. We run nightly full backups through our back up software, but would like to try and recover the data if possible.

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2007-04-26 : 12:03:01
I'll rebuild indexes first then run 'dbcc checkdb' again.
Go to Top of Page

paulrandal
Yak with Vast SQL Skills

899 Posts

Posted - 2007-04-27 : 14:25:51
Completely useless advice - sys.sysrowsetcolumns is an unbindable system table and index rebuilding is not permitted on system tables like this anyway.

There are two options here - first one is a single bit problem with the differential bitmap at the start of the MDF file, and the second one is a bug with tracking changed extents in the diff map. I'm not aware of anything around the second. Are there any signs of h/w issues in the SQL error log or Windows event log?

The diff map should be cleared every time you take a full backup - there's no data loss possible from this UNLESS you take diff backups and need to do a point-in-time restore before the next full backup is taken.

When you say the problem goes back to Saturday, do you mean the same error is present when you restore previous backups? Do you do any other backups between the nightly fulls?

Thanks

Paul Randal
Principal Lead Program Manager, Microsoft SQL Server Core Storage Engine
(Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.)
http://blogs.msdn.com/sqlserverstorageengine/default.aspx
Go to Top of Page
   

- Advertisement -