Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Backup Failure - "Could not clear 'DIFFERENTIAL' bitmap"

Status
Not open for further replies.

MissTipps

Programmer
May 20, 2002
91
GB
Hi

I have a database which has started generating the following backup error:

Msg 18273, Sev 16, State 1, Line 1 : Could not clear 'DIFFERENTIAL' bitmap in database '' because of error 5242. As a result, the differential or bulk-logged bitmap overstates the amount of change that will occur with the next differential or log backup. This discrepancy might slow down later differential or log backup operations and cause the backup sets to be larger than necessary. Typically, the cause of this error is insufficient resources. Investigate the failure and resolve the cause. If the errorMsg 3013, Sev 16, State 1, Line 1 : BACKUP DATABASE is terminating abnormally. [SQLSTATE 42000]

So far I've tried:
1. Running a CHECKDB against it with every possible repair mode
2. Taking a COPY_ONLY backup and restoring it to a different server


Does anyone have any suggestions on how to clear this?

Many thanks



MissTipps

CISSP, CEH, CEI, MCT, MCDBA, MCSE 2K3, CTT+, ECSA, Security+
 
I'd start by trying a full backup. This should reset the differential bitmap.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)
[noevil]
 
This IS the error I received when trying to run a full backup

MissTipps

CISSP, CEH, CEI, MCT, MCDBA, MCSE 2K3, CTT+, ECSA, Security+
 
I found another thread over on SQLServerCentral.com on this error. The user said that Microsoft recommended a detach and attach of the effected database.

This thread is from 2004, so it's most likly a SQL 2000 server. If you have SQL 2005 I would assume that this would still be the case.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)
[noevil]
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top