locked
Maint Plan Suddenly Getting Errors and Failing RRS feed

  • Question

  • I have setup a Maint Plan on a SQL 2008R2 server running on 2008 SBS. The plan is backing up 3 databases as wel as preforming basic maint (checkdbcc, Rebuld Indexes, Maint Cleanup etc.). The plan has been working fine without errors for over a year and a half. Suddeenly about 2 weeks ago I noticed that the maint plan failed. I cannot figure out why and what the error messages mean. If anyone can decipher the log or offer any other insights, I would be very grateful.

    Thanks in advance.

    See attached Log

    Date,Source,Severity,Message
    08/07/2017 11:30:52,spid73,Unknown,DBCC CHECKDB (york2016) WITH no_infomsgs executed by E2user found 0 errors and repaired 0 errors. Elapsed time: 0 hours 3 minutes 10 seconds.  Internal database snapshot has split point LSN = 00002067:0000185e:0001 and first LSN = 00002067:0000185d:0001.  This is an informational message only. No user action is required.
    08/07/2017 11:27:40,spid73,Unknown,External dump process return code 0x20000001.<nl/>External dump process returned no errors.
    08/07/2017 11:27:36,spid73,Unknown,Stack Signature for the dump is 0x0000000000000304
    08/07/2017 11:27:36,spid73,Unknown,* Short Stack Dump
    08/07/2017 11:27:36,spid73,Unknown,* -------------------------------------------------------------------------------
    08/07/2017 11:27:36,spid73,Unknown,* *******************************************************************************
    08/07/2017 11:27:36,spid73,Unknown,*
    08/07/2017 11:27:36,spid73,Unknown,*             DBCC CHECKDB(N'York')  WITH NO_INFOMSGS
    08/07/2017 11:27:36,spid73,Unknown,* Input Buffer 104 bytes -
    08/07/2017 11:27:36,spid73,Unknown,*
    08/07/2017 11:27:36,spid73,Unknown,* DBCC database corruption
    08/07/2017 11:27:36,spid73,Unknown,*
    08/07/2017 11:27:36,spid73,Unknown,*   08/07/17 11:27:36 spid 73
    08/07/2017 11:27:36,spid73,Unknown,* BEGIN STACK DUMP:
    08/07/2017 11:27:36,spid73,Unknown,*
    08/07/2017 11:27:36,spid73,Unknown,* *******************************************************************************
    08/07/2017 11:27:36,spid73,Unknown,***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL10_50.GOLDMINE\MSSQL\LOG\SQLDump0023.txt
    08/07/2017 11:27:36,spid73,Unknown,**Dump thread - spid = 0<c/> EC = 0x0000000113EFA480
    08/07/2017 11:27:36,spid73,Unknown,Using 'dbghelp.dll' version '4.0.5'
    08/07/2017 11:27:36,spid73,Unknown,DBCC CHECKDB (York) WITH no_infomsgs executed by E2user found 5 errors and repaired 0 errors. Elapsed time: 0 hours 4 minutes 4 seconds.  Internal database snapshot has split point LSN = 000020ee:000049fb:0001 and first LSN = 000020ee:0000494e:0001.  This is an informational message only. No user action is required.
    08/07/2017 11:26:34,spid4s,Unknown,SQL Server has encountered 31 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [C:\Program Files\Microsoft SQL Server\MSSQL10_50.GOLDMINE\MSSQL\DATA\templog.ldf] in database [tempdb] (2).  The OS file handle is 0x0000000000000644.  The offset of the latest long I/O is: 0x0000000094c000
    08/07/2017 11:26:34,spid4s,Unknown,SQL Server has encountered 6721 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [C:\Program Files\Microsoft SQL Server\MSSQL10_50.GOLDMINE\MSSQL\DATA\tempdb.mdf] in database [tempdb] (2).  The OS file handle is 0x0000000000000640.  The offset of the latest long I/O is: 0x0000001f440000
    08/07/2017 11:23:29,spid73,Unknown,DBCC CHECKDB (York2014) WITH no_infomsgs executed by E2user found 0 errors and repaired 0 errors. Elapsed time: 0 hours 3 minutes 50 seconds.  Internal database snapshot has split point LSN = 00001a13:000019f5:0001 and first LSN = 00001a13:000019f4:0001.  This is an informational message only. No user action is required.
    08/07/2017 11:19:38,spid73,Unknown,DBCC CHECKDB (York2015) WITH no_infomsgs executed by E2user found 0 errors and repaired 0 errors. Elapsed time: 0 hours 4 minutes 8 seconds.  Internal database snapshot has split point LSN = 00001df5:00005024:0001 and first LSN = 00001df5:00005023:0001.  This is an informational message only. No user action is required.
    08/07/2017 11:18:29,Server,Unknown,Resource Monitor (0x820) Worker 0x00000000800121A0 appears to be non-yielding on Node 0. Memory freed: 3728 KB. Approx CPU Used: kernel 0 ms<c/> user 15 ms<c/> Interval: 60124.
    08/07/2017 11:17:43,spid4s,Unknown,SQL Server has encountered 18 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [C:\Program Files\Microsoft SQL Server\MSSQL10_50.GOLDMINE\MSSQL\DATA\templog.ldf] in database [tempdb] (2).  The OS file handle is 0x0000000000000644.  The offset of the latest long I/O is: 0x00000001d97000
    08/07/2017 11:17:41,spid4s,Unknown,SQL Server has encountered 770 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [C:\Program Files\Microsoft SQL Server\MSSQL10_50.GOLDMINE\MSSQL\DATA\tempdb.mdf] in database [tempdb] (2).  The OS file handle is 0x0000000000000640.  The offset of the latest long I/O is: 0x0000002bc30000
    08/07/2017 11:15:28,spid103,Unknown,DBCC CHECKDB (GoldMine) WITH no_infomsgs executed by E2user found 0 errors and repaired 0 errors. Elapsed time: 0 hours 4 minutes 55 seconds.  Internal database snapshot has split point LSN = 0001054c:00000f28:0001 and first LSN = 0001054c:00000f27:0001.  This is an informational message only. No user action is required.
    08/07/2017 11:10:33,spid103,Unknown,DBCC CHECKDB (ReportServer$GOLDMINETempDB) WITH no_infomsgs executed by E2user found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 0 seconds.  Internal database snapshot has split point LSN = 0000024b:00000170:0001 and first LSN = 0000024b:0000016f:0001.  This is an informational message only. No user action is required.
    08/07/2017 11:10:32,spid103,Unknown,DBCC CHECKDB (ReportServer$GOLDMINE) WITH no_infomsgs executed by E2user found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 0 seconds.  Internal database snapshot has split point LSN = 000000e9:000008d1:0001 and first LSN = 000000e9:000008d0:0001.  This is an informational message only. No user action is required.
    08/07/2017 11:10:32,spid103,Unknown,DBCC CHECKDB (msdb) WITH no_infomsgs executed by E2user found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 2 seconds.  Internal database snapshot has split point LSN = 00001b44:000000e0:0001 and first LSN = 00001b44:000000d8:0001.  This is an informational message only. No user action is required.
    08/07/2017 11:10:29,spid103,Unknown,DBCC CHECKDB (model) WITH no_infomsgs executed by E2user found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 0 seconds.  Internal database snapshot has split point LSN = 00000082:000001b8:0001 and first LSN = 00000082:000001b0:0001.  This is an informational message only. No user action is required.
    08/07/2017 11:10:28,spid103,Unknown,DBCC CHECKDB (mssqlsystemresource) WITH no_infomsgs executed by E2user found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 3 seconds.
    08/07/2017 11:10:24,spid103,Unknown,DBCC CHECKDB (master) WITH no_infomsgs executed by E2user found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 0 seconds.  Internal database snapshot has split point LSN = 000003fb:000001a0:0003 and first LSN = 000003fb:00000198:0001.  This is an informational message only. No user action is required.
    08/07/2017 11:10:24,spid101,Unknown,FILESTREAM: effective level = 0<c/> configured level = 0<c/> file system access share name = 'GOLDMINE'.
    08/07/2017 11:10:24,spid101,Unknown,Configuration option 'user options' changed from 0 to 0. Run the RECONFIGURE statement to install.
    08/07/2017 02:15:48,spid65,Unknown,DBCC CHECKDB (york2016) WITH no_infomsgs executed by E2user found 0 errors and repaired 0 errors. Elapsed time: 0 hours 2 minutes 36 seconds.  Internal database snapshot has split point LSN = 00002067:0000183a:0001 and first LSN = 00002067:00001839:0001.  This is an informational message only. No user action is required.
    08/07/2017 02:13:11,spid65,Unknown,External dump process return code 0x20000001.<nl/>External dump process returned no errors.
    08/07/2017 02:12:59,spid65,Unknown,Stack Signature for the dump is 0x0000000000000304
    08/07/2017 02:12:59,spid65,Unknown,* Short Stack Dump
    08/07/2017 02:12:59,spid65,Unknown,* -------------------------------------------------------------------------------
    08/07/2017 02:12:59,spid65,Unknown,* *******************************************************************************
    08/07/2017 02:12:59,spid65,Unknown,*
    08/07/2017 02:12:59,spid65,Unknown,*             DBCC CHECKDB(N'York')  WITH NO_INFOMSGS
    08/07/2017 02:12:59,spid65,Unknown,* Input Buffer 104 bytes -
    08/07/2017 02:12:59,spid65,Unknown,*
    08/07/2017 02:12:59,spid65,Unknown,* DBCC database corruption
    08/07/2017 02:12:59,spid65,Unknown,*
    08/07/2017 02:12:59,spid65,Unknown,*   08/07/17 02:12:59 spid 65
    08/07/2017 02:12:59,spid65,Unknown,* BEGIN STACK DUMP:
    08/07/2017 02:12:59,spid65,Unknown,*
    08/07/2017 02:12:59,spid65,Unknown,* *******************************************************************************
    08/07/2017 02:12:59,spid65,Unknown,***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL10_50.GOLDMINE\MSSQL\LOG\SQLDump0022.txt
    08/07/2017 02:12:59,spid65,Unknown,**Dump thread - spid = 0<c/> EC = 0x0000000081700480
    08/07/2017 02:12:59,spid65,Unknown,Using 'dbghelp.dll' version '4.0.5'
    08/07/2017 02:12:59,spid65,Unknown,DBCC CHECKDB (York) WITH no_infomsgs executed by E2user found 5 errors and repaired 0 errors. Elapsed time: 0 hours 2 minutes 47 seconds.  Internal database snapshot has split point LSN = 000020ee:00000767:0001 and first LSN = 000020ee:00000766:0001.  This is an informational message only. No user action is required.
    08/07/2017 02:12:14,spid4s,Unknown,SQL Server has encountered 44 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [C:\Program Files\Microsoft SQL Server\MSSQL10_50.GOLDMINE\MSSQL\DATA\templog.ldf] in database [tempdb] (2).  The OS file handle is 0x0000000000000644.  The offset of the latest long I/O is: 0x00000001200000
    08/07/2017 02:12:14,spid4s,Unknown,SQL Server has encountered 10321 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [C:\Program Files\Microsoft SQL Server\MSSQL10_50.GOLDMINE\MSSQL\DATA\tempdb.mdf] in database [tempdb] (2).  The OS file handle is 0x0000000000000640.  The offset of the latest long I/O is: 0x00000032160000
    08/07/2017 02:10:11,spid65,Unknown,DBCC CHECKDB (York2014) WITH no_infomsgs executed by E2user found 0 errors and repaired 0 errors. Elapsed time: 0 hours 3 minutes 22 seconds.  Internal database snapshot has split point LSN = 00001a13:000019c7:0001 and first LSN = 00001a13:000019c6:0001.  This is an informational message only. No user action is required.
    08/07/2017 02:06:48,spid65,Unknown,DBCC CHECKDB (York2015) WITH no_infomsgs executed by E2user found 0 errors and repaired 0 errors. Elapsed time: 0 hours 3 minutes 30 seconds.  Internal database snapshot has split point LSN = 00001df5:00004ff6:0001 and first LSN = 00001df5:00004ff5:0001.  This is an informational message only. No user action is required.
    08/07/2017 02:05:07,spid4s,Unknown,SQL Server has encountered 51 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [C:\Program Files\Microsoft SQL Server\MSSQL10_50.GOLDMINE\MSSQL\DATA\templog.ldf] in database [tempdb] (2).  The OS file handle is 0x0000000000000644.  The offset of the latest long I/O is: 0x000000008f2000
    08/07/2017 02:05:07,spid4s,Unknown,SQL Server has encountered 524 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [C:\Program Files\Microsoft SQL Server\MSSQL10_50.GOLDMINE\MSSQL\DATA\tempdb.mdf] in database [tempdb] (2).  The OS file handle is 0x0000000000000640.  The offset of the latest long I/O is: 0x0000003fb80000
    08/07/2017 02:03:17,spid65,Unknown,DBCC CHECKDB (GoldMine) WITH no_infomsgs executed by E2user found 0 errors and repaired 0 errors. Elapsed time: 0 hours 2 minutes 56 seconds.  Internal database snapshot has split point LSN = 00010548:0000156e:0001 and first LSN = 00010548:0000156d:0001.  This is an informational message only. No user action is required.
    08/07/2017 02:00:21,spid65,Unknown,DBCC CHECKDB (ReportServer$GOLDMINETempDB) WITH no_infomsgs executed by E2user found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 0 seconds.  Internal database snapshot has split point LSN = 0000024b:00000169:0001 and first LSN = 0000024b:00000168:0001.  This is an informational message only. No user action is required.
    08/07/2017 02:00:20,spid65,Unknown,DBCC CHECKDB (ReportServer$GOLDMINE) WITH no_infomsgs executed by E2user found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 0 seconds.  Internal database snapshot has split point LSN = 000000e9:000008ca:0001 and first LSN = 000000e9:000008c9:0001.  This is an informational message only. No user action is required.
    08/07/2017 02:00:19,spid65,Unknown,DBCC CHECKDB (msdb) WITH no_infomsgs executed by E2user found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 4 seconds.  Internal database snapshot has split point LSN = 00001b43:000002b8:0001 and first LSN = 00001b43:000002b0:0001.  This is an informational message only. No user action is required.
    08/07/2017 02:00:15,spid66,Unknown,DBCC CHECKDB (model) WITH no_infomsgs executed by E2user found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 0 seconds.  Internal database snapshot has split point LSN = 00000082:00000180:0001 and first LSN = 00000082:00000178:0001.  This is an informational message only. No user action is required.
    08/07/2017 02:00:14,spid65,Unknown,DBCC CHECKDB (mssqlsystemresource) WITH no_infomsgs executed by E2user found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 1 seconds.
    08/07/2017 02:00:12,spid65,Unknown,DBCC CHECKDB (master) WITH no_infomsgs executed by E2user found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 1 seconds.  Internal database snapshot has split point LSN = 000003fb:00000168:0003 and first LSN = 000003fb:00000160:0001.  This is an informational message only. No user action is required.
    08/07/2017 02:00:11,spid57,Unknown,FILESTREAM: effective level = 0<c/> configured level = 0<c/> file system access share name = 'GOLDMINE'.
    08/07/2017 02:00:11,spid57,Unknown,Configuration option 'user options' changed from 0 to 0. Run the RECONFIGURE statement to install.
    08/07/2017 00:00:13,spid28s,Unknown,This instance of SQL Server has been using a process ID of 852 since 9/9/2016 5:36:34 AM (local) 9/9/2016 9:36:34 AM (UTC). This is an informational message only; no user action is required.
    Monday, August 14, 2017 3:43 PM

All replies

  • >08/07/2017 02:12:14,spid4s,Unknown,SQL Server has encountered 44 occurrence(s) of I/O requests >taking longer than 15 seconds to complete on file [C:\Program Files\Microsoft SQL >Server\MSSQL10_50.GOLDMINE\MSSQL\DATA\templog.ldf] in database [tempdb] (2).  The OS file >handle is 0x0000000000000644.  The offset of the latest long I/O is: 0x00000001200000

    'I/O requests taking longer than 15 seconds to complete' errors, typically are symptom of problem with disk subsystem. 

    You're C drive could be going bad and should be checked and repaired, and or, replaced, if possible, before it fails, if it is determined to be going bad.

    This may or may not solve the failing maintenance plan issue, but is important enough that it deserves immediate attention.

    HTH,


    Phil Streiff, MCDBA, MCITP, MCSA

    • Edited by philfactor Monday, August 14, 2017 4:48 PM
    Monday, August 14, 2017 4:11 PM
  • 08/07/2017 11:27:36,spid73,Unknown,DBCC CHECKDB (York) WITH no_infomsgs executed by E2user found 5 errors and repaired 0 errors.

    08/07/2017 02:12:59,spid65,Unknown,DBCC CHECKDB (York) WITH no_infomsgs executed by E2user found 5 errors and repaired 0 errors.

    Hi,

    The maintenance plan failed because the database York is corrupt and checkdb found 5 error. Checkdb sometimes produces stack dump when it encounters corruption and this is the reason why whole MP failed.

    Your action should be to run below and see if this produces any useful about about what is corrupted and what is minimum repair level

    dbcc checkdb (db_name) 
    Do you have valid backup, keep is ready


    Cheers,

    Shashank

    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it

    My TechNet Wiki Articles

    MVP

    Monday, August 14, 2017 5:26 PM
  • ...and the databases may be getting corrupted because data files are sitting on bad sectors of the disk drive.

    HTH,


    Phil Streiff, MCDBA, MCITP, MCSA

    Monday, August 14, 2017 6:05 PM
  • Shashank,

    I was unable to post the full log file here due to character limitations, but there are 2 other db's that are part of the same plan, that are getting the exact same "database is corrupt and checkdb found 5 errors and repaired 0" messages. This makes lean more towards HTH post(s) regarding hard drive problems. The age of the server also leans towards the hard drive.

    Thanks so much for your input.

    Monday, August 14, 2017 6:36 PM
  • Hi, you can try to post via one drive for us.

    But after seeing the error message, the DB has been corrupted., if you have clean-backups you can do restore from them. If doesn't have valid backups., I am afraid to say you need to proceed the steps given by the below KB from MS.

    https://support.microsoft.com/en-in/help/2015748/how-to-troubleshoot-database-consistency-errors-reported-by-dbcc-check

    Thanks,

    Thanks, Satish Kumar. Please mark as this post as answered if my anser helps you to resolves your issue :)

    Tuesday, August 15, 2017 12:59 AM
  • Shashank,

    I was unable to post the full log file here due to character limitations, but there are 2 other db's that are part of the same plan, that are getting the exact same "database is corrupt and checkdb found 5 errors and repaired 0" messages. This makes lean more towards HTH post(s) regarding hard drive problems. The age of the server also leans towards the hard drive.

    Thanks so much for your input.


    Most prominent cause of corruption is bad storage I guess you MUST speak to the respective team there is something wrong somewhere specially storage. You must also look at the event viewer to get more information what caused corruption, I would bet on storage

    Cheers,

    Shashank

    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it

    My TechNet Wiki Articles

    MVP

    Tuesday, August 15, 2017 4:53 PM