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

Time-out occurred while waiting for buffer latch type 3 for page Expand / Collapse
Author
Message
Posted Friday, January 28, 2011 3:36 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, March 05, 2014 8:54 AM
Points: 294, Visits: 1,242
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 ?
Post #1055193
Posted Monday, January 31, 2011 4:10 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, March 05, 2014 8:54 AM
Points: 294, Visits: 1,242
***BUMP***
Post #1056065
Posted Monday, January 31, 2011 4:22 AM


SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: 2 days ago @ 11:10 PM
Points: 240, Visits: 2,391
I am not to sure.

Set up the database in single user mode and then take backup and then set up to multi user.
Post #1056072
Posted Monday, January 31, 2011 9:36 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, March 05, 2014 8:54 AM
Points: 294, Visits: 1,242
It won't change to single user model same problem
Post #1056267
Posted Tuesday, February 01, 2011 2:35 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, March 05, 2014 8:54 AM
Points: 294, Visits: 1,242
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.
Post #1056666
Posted Tuesday, February 01, 2011 7:11 AM


SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Today @ 5:07 PM
Points: 4,128, Visits: 5,840
Time for a call to Microsoft Support perhaps?

Best,

Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru at GMail
Post #1056789
Posted Tuesday, February 01, 2011 7:53 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: 2 days ago @ 3:46 PM
Points: 52, Visits: 815
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.)
Post #1056824
Posted Thursday, May 10, 2012 3:07 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, March 14, 2014 2:29 PM
Points: 2, Visits: 108
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.
Post #1297700
Posted Thursday, May 10, 2012 3:33 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Thursday, April 03, 2014 3:48 AM
Points: 2,274, Visits: 767
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
Post #1297707
Posted Monday, September 30, 2013 10:26 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, January 03, 2014 4:40 AM
Points: 8, Visits: 113
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
Post #1500101
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse