Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

BACKUP DATABASE is terminating abnormally Expand / Collapse
Author
Message
Posted Monday, September 24, 2012 1:39 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Today @ 9:10 PM
Points: 251, Visits: 757
Dear All,

Could someone please advice on this.

Msg 3013, Level 16, State 1, Line 1
BACKUP DATABASE is terminating abnormally.
Msg 845, Level 17, State 1, Line 1
Time-out occurred while waiting for buffer latch type 3 for page (1:23723), database ID 6.

------------------


Msg 1823, Level 16, State 2, Line 1
A database snapshot cannot be created because it failed to start.
Msg 7928, Level 16, State 1, Line 1
The database snapshot for online checks could not be created. Either the reason is given in a previous error or one of the underlying volumes does not support sparse files or alternate streams. Attempting to get exclusive access

to run checks offline.
Msg 5030, Level 16, State 12, Line 1
The database could not be exclusively locked to perform the operation.
Msg 7926, Level 16, State 1, Line 1
Check statement aborted. The database could not be checked as a database snapshot could not be created and the database or table could not be locked. See Books Online for details of when this behavior is expected and what workarounds exist. Also see previous errors for more details.
Msg 845, Level 17, State 1, Line 1
Time-out occurred while waiting for buffer latch type 3 for page (1:23723), database ID 6.

Thanks and Regards,
Ravi.
Post #1363353
Posted Wednesday, September 26, 2012 3:56 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, November 6, 2014 8:19 PM
Points: 121, Visits: 1,251
This problem occurs if the following conditions are true:

* At least one other connection is using the database against which you run the DBCC CHECK command.
* The database contains at least one file group that is marked as read-only.

Starting with SQL Server 2005, DBCC CHECK commands create and use an internal database snapshot for consistency purposes when the command performs any checks. If a read-only file group exists in the database, the internal database snapshot is not created. To continue to perform the checks, the DBCC CHECK command tries to acquire an EX database lock. If other users are connected to this database, this attempt to acquire an EX lock fails. Therefore, you receive an error message.

To resolve this problem, follow these steps instead of running the DBCC CHECK command against the database:

1. Create a database snapshot of the database for which you want to perform the checks. For more information about how to create a database snapshot, see the "How to: Create a Database Snapshot (Transact-SQL)" topic in SQL Server 2005 Books Online.
2. Run the DBCC CHECK command against the database snapshot.
3. Drop the database snapshot after the DBCC CHECK command is completed.

Ref: http://support.microsoft.com/kb/928518


SQL Database Recovery Expert
Post #1364540
Posted Wednesday, November 28, 2012 6:13 AM
Say Hey Kid

Say Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey Kid

Group: General Forum Members
Last Login: Monday, November 24, 2014 3:46 AM
Points: 709, Visits: 1,442
Previous post reported as spam.

For the OP's issue, it looks like there the is a system latch on the database preventing the snapshot from occurring at that time. Can you research what other activity may be going on during the time that you are trying to run a DBCC Checkdb?


Joie Andrew
"Since 1982"
Post #1389695
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse