September 8, 2014 at 9:25 am
EDIT: removed company information
Again, I've received another notification that just doesn't give me a warm and fuzzy feeling, despite the final message. I ran a CHECKDB on a large database last night (about 2TB), got the following messages:
The operating system returned error 1450(Insufficient system resources exist to complete the requested service.) to SQL Server during a write at offset 0x00002516b1c000 in file 'H:\MYDB.mdf:MSSQL_DBCC37'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Error: 17053, Severity: 16, State: 1.
H:\MYDB.mdf:MSSQL_DBCC37: Operating system error 1450(Insufficient system resources exist to complete the requested service.) encountered.
The operating system returned error 1450(Insufficient system resources exist to complete the requested service.) to SQL Server during a write at offset 0x00002516b1c000 in file 'H:\MYDB.mdf:MSSQL_DBCC37'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Error: 17053, Severity: 16, State: 1.
H:\MYDB.mdf:MSSQL_DBCC37: Operating system error 1450(Insufficient system resources exist to complete the requested service.) encountered.
Yet, here's the part that confuses me:
DBCC CHECKDB (MYDB) WITH all_errormsgs, no_infomsgs executed by COMPANY\F1Onsitelog found 0 errors and repaired 0 errors. Elapsed time: 2 hours 52 minutes 30 seconds. Internal database snapshot has split point LSN = 000a866b:006105c6:0001 and first LSN = 000a866b:006105c5:0001.
I realize this could be a sparse file problem, but I have over 300 GB of free space on the drive and tempdb has about 300GB free as well. Running an ESTIMATEONLY shows that the process should only take approximately 742 MB of space.
I had a similar thing happen last week with another database, and after a series of running various forms of CHECKDB, the end result came back clean with no errors - Is there a potential disk issue here?
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
September 8, 2014 at 9:29 am
Can you try running a checkDB with Tablock (will need exclusive access)?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
September 9, 2014 at 6:53 pm
2 days after-the-fact, a full check returns no errors
DBCC CHECKDB ('MYDB') WITH ALL_ERRORMSGS, NO_INFOMSGS
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply