January 28, 2011 at 3:36 am
Getting this error message
Time-out occurred while waiting for buffer latch type 3 for page (1:738192), database ID **. when trying to backup a database. Can't kill of the process as it's a system preocess. Any ideas ?
January 31, 2011 at 4:10 am
***BUMP***
January 31, 2011 at 4:22 am
I am not to sure.
Set up the database in single user mode and then take backup and then set up to multi user.
--------------------------------------------------------------------------------------------------
I am just an another naive wannabe DBA trying to learn SQL Server
January 31, 2011 at 9:36 am
It won't change to single user model same problem
February 1, 2011 at 2:35 am
have also run a check db which failed with this error:
A database snapshot cannot be created because it failed to start. [SQLSTATE 42000] (Error 1823) 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. [SQLSTATE 42000] (Error 7928) The database could not be exclusively locked to perform the operation. [SQLSTATE 42000] (Error 5030) 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. [SQLSTATE 42000] (Error 7926). The step failed.
February 1, 2011 at 7:11 am
Time for a call to Microsoft Support perhaps?
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
February 1, 2011 at 7:53 am
We had a similar sounding problem once. We have a daily pair of jobs scheduled to create a snapshot and later delete the shapshot. One of the developers had manually run the create snapshot, and it stayed around for days accumulating updates until some particular system resource had been exhausted. (Don't remember why the delete snapshot job didn't run, but that was a separate problem.)
May 10, 2012 at 3:07 am
HI Team I am having the sam eissue on one of critical database can you please help me to resolve this issue ASAP.
I appreciate your help. thanks in Advance.
May 10, 2012 at 3:33 am
more info can be found here
the bottom post from the microsoft suppoort guy seems to indicate that you may have a slow IO issue - they suggest that when you get this error a mini-dump is performed and you can sent it to MS for analysis
MVDBA
September 30, 2013 at 10:26 am
We had the same issue, in our case the issues was caused by some corruption and the sql daemon process locking the latch. Also other issues we seen in this system was that we were not able to take a full backup or diff backups. Even though we could take tlog backups the pages were not getting release and tlog was getting large.
The steps we follow are:
Verify the backups and can restore the db using tlog backups
Verify the db is up-to-date
If there is a problem with the backups (in our case)
Stop all the connection to db
Restart the db
This will put the db in to recovery mode (this may take some time ….)
Backup the database
Check db, dbcc checkdb
if you still getting the same error, timeout on buffer……
restore the db using the backup
check the restored db
fix and errors
backup the db
put the db back to production
hope this help
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply