SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Time-out occurred while waiting for buffer latch type 3 for page


Time-out occurred while waiting for buffer latch type 3 for page

Author
Message
MarvinTheAndriod
MarvinTheAndriod
SSC-Addicted
SSC-Addicted (462 reputation)SSC-Addicted (462 reputation)SSC-Addicted (462 reputation)SSC-Addicted (462 reputation)SSC-Addicted (462 reputation)SSC-Addicted (462 reputation)SSC-Addicted (462 reputation)SSC-Addicted (462 reputation)

Group: General Forum Members
Points: 462 Visits: 1291
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 ?
MarvinTheAndriod
MarvinTheAndriod
SSC-Addicted
SSC-Addicted (462 reputation)SSC-Addicted (462 reputation)SSC-Addicted (462 reputation)SSC-Addicted (462 reputation)SSC-Addicted (462 reputation)SSC-Addicted (462 reputation)SSC-Addicted (462 reputation)SSC-Addicted (462 reputation)

Group: General Forum Members
Points: 462 Visits: 1291
***BUMP***
Sachin Nandanwar
Sachin Nandanwar
Say Hey Kid
Say Hey Kid (679 reputation)Say Hey Kid (679 reputation)Say Hey Kid (679 reputation)Say Hey Kid (679 reputation)Say Hey Kid (679 reputation)Say Hey Kid (679 reputation)Say Hey Kid (679 reputation)Say Hey Kid (679 reputation)

Group: General Forum Members
Points: 679 Visits: 2633
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
MarvinTheAndriod
MarvinTheAndriod
SSC-Addicted
SSC-Addicted (462 reputation)SSC-Addicted (462 reputation)SSC-Addicted (462 reputation)SSC-Addicted (462 reputation)SSC-Addicted (462 reputation)SSC-Addicted (462 reputation)SSC-Addicted (462 reputation)SSC-Addicted (462 reputation)

Group: General Forum Members
Points: 462 Visits: 1291
It won't change to single user model same problem
MarvinTheAndriod
MarvinTheAndriod
SSC-Addicted
SSC-Addicted (462 reputation)SSC-Addicted (462 reputation)SSC-Addicted (462 reputation)SSC-Addicted (462 reputation)SSC-Addicted (462 reputation)SSC-Addicted (462 reputation)SSC-Addicted (462 reputation)SSC-Addicted (462 reputation)

Group: General Forum Members
Points: 462 Visits: 1291
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.
TheSQLGuru
TheSQLGuru
SSChampion
SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)

Group: General Forum Members
Points: 12295 Visits: 8546
Time for a call to Microsoft Support perhaps?

Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
Charlotte Bentley
Charlotte Bentley
SSC Journeyman
SSC Journeyman (75 reputation)SSC Journeyman (75 reputation)SSC Journeyman (75 reputation)SSC Journeyman (75 reputation)SSC Journeyman (75 reputation)SSC Journeyman (75 reputation)SSC Journeyman (75 reputation)SSC Journeyman (75 reputation)

Group: General Forum Members
Points: 75 Visits: 915
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.)
ismailshariff.a 71186
ismailshariff.a 71186
Forum Newbie
Forum Newbie (8 reputation)Forum Newbie (8 reputation)Forum Newbie (8 reputation)Forum Newbie (8 reputation)Forum Newbie (8 reputation)Forum Newbie (8 reputation)Forum Newbie (8 reputation)Forum Newbie (8 reputation)

Group: General Forum Members
Points: 8 Visits: 126
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.
MVDBA
MVDBA
Hall of Fame
Hall of Fame (3K reputation)Hall of Fame (3K reputation)Hall of Fame (3K reputation)Hall of Fame (3K reputation)Hall of Fame (3K reputation)Hall of Fame (3K reputation)Hall of Fame (3K reputation)Hall of Fame (3K reputation)

Group: General Forum Members
Points: 3047 Visits: 860
more info can be found here

http://connect.microsoft.com/SQLServer/feedback/details/715710/a-time-out-occurred-while-waiting-for-buffer-latch-type-3

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
priz
priz
Grasshopper
Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)

Group: General Forum Members
Points: 14 Visits: 187
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
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search