January 18, 2010 at 8:15 am
Dear Team,
My MPlan have failed stating the below error,as I ran DBCC Checkdb('dbname')with no_infomsgs,all_errormsg to check any errors,I didnt get any errors except the "commands completed succesfully" any suggestion!!
Executed as user: XXXX\SQLADMIN. ... complete End Progress Progress: 2010-01-17 00:20:01.33
Source: Check Database Integrity Executing query "USE [P1] ".: 50% complete End Progress
Progress: 2010-01-17 00:20:07.79 Source: Check Database Integrity
Executing query "DBCC CHECKDB WITH NO_INFOMSGS ".: 100% complete End Progress
Progress: 2010-01-17 00:20:07.80 Source: Check Database Integrity
Executing query "USE [D1] ".: 50% complete End Progress
Progress: 2010-01-17 00:20:23.50 Source: Check Database Integrity
Executing query "DBCC CHECKDB WITH NO_INFOMSGS ".: 100% complete End Progress
Progress: 2010-01-17 00:20:23.52 Source: Check Database Integrity
Executing query "USE [S1] ".: 50% complete End Progress
Progress: 2010-01-17 00:20:29.16 Source: Check Database Integrity
Executing query "DBCC CHECKDB WITH NO_INFOMSGS ".: 100% complete End Progress
Progr... The package execution fa... The step failed.
January 18, 2010 at 8:35 am
What's in the error log? CheckDB results are logged to the error log, so you should be able to see what ran.
Do you have the maint plan logging output to a file? If so, what's in there?
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
January 18, 2010 at 9:10 am
Gail,
Ididnt find any error mess on the eror logs except these statements for all DB's
DBCC CHECKDB (P1) WITH no_infomsgs executed by XXXXX\SQLADMIN found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 4 seconds.
My Mplan contains steps as
CheckDBIntegrity
Reorganize Index
Rebuild Index
Update Stats
McleanUp task
January 18, 2010 at 9:17 am
Then the failure was from one of the later tasks. You need to log the output of the maintenance plan to tell exactly where.
btw, why on earth are you both rebuilding the indexes and reorganising them. Bit of a waste of time there.
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
January 18, 2010 at 9:56 am
Gail,
I found on the error log output as below.
Date,Source,Severity,Message
01/15/2010 23:45:10,Backup,Unknown,Database backed up. Database: model<c/> creation date(time): 2003/04/08(09:13:36)<c/> pages dumped: 344<c/> first LSN: 176:208:37<c/> last LSN: 176:232:1<c/> number of dump devices: 1<c/> device information: (FILE=1<c/> TYPE=VIRTUAL_DEVICE: {'SQLBACKUP_A739B070-3D03-48B8-A4B5-AB3759509C6A'}). This is an informational message only. No user action is required.
01/15/2010 23:45:09,Backup,Unknown,Database backed up. Database: msdb<c/> creation date(time): 2005/10/14(01:54:05)<c/> pages dumped: 20064<c/> first LSN: 42334:16:275<c/> last LSN: 42334:144:1<c/> number of dump devices: 1<c/> device information: (FILE=1<c/> TYPE=VIRTUAL_DEVICE: {'SQLBACKUP_6BEA6865-0869-4F15-931A-11ACFDEBB056'}). This is an informational message only. No user action is required.
01/15/2010 23:45:04,Backup,Unknown,Database backed up. Database: master<c/> creation date(time): 2009/12/10(14:15:57)<c/> pages dumped: 600<c/> first LSN: 6437:280:61<c/> last LSN: 6437:312:1<c/> number of dump devices: 1<c/> device information: (FILE=1<c/> TYPE=VIRTUAL_DEVICE: {'SQLBACKUP_FE6B9E12-72EB-4B28-8D03-8E684F4E80DA'}). This is an informational message only. No user action is required.
01/15/2010 19:32:40,spid2s,Unknown,SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [f:\sqldata\templog.ldf] in database [tempdb] (2). The OS file handle is 0x00000608. The offset of the latest long I/O is: 0x000000188a1000
01/15/2010 19:32:20,spid2s,Unknown,SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [F:\SQLData\P12_NEW_log1.ldf] in database [P12] (18). The OS file handle is 0x00000980. The offset of the latest long I/O is: 0x00000032bc8800
01/15/2010 18:53:14,spid68,Unknown,DBCC CHECKDB (P1) WITH no_infomsgs executed by XXXXX\SQLADMIN found 0 errors and repaired 0 errors. Elapsed time: 0 hours 2 minutes 23 seconds.
01/15/2010 18:50:49,spid68,Unknown,DBCC CHECKDB (P2) WITH no_infomsgs executed by XXXXX\SQLADMIN found 0 errors and repaired 0 errors. Elapsed time: 0 hours 2 minutes 12 seconds.
01/15/2010 18:48:36,spid68,Unknown,DBCC CHECKDB (P3) WITH no_infomsgs executed by XXXXX\SQLADMIN found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 4 seconds.
01/15/2010 18:48:31,spid68,Unknown,DBCC CHECKDB (P4) WITH no_infomsgs executed by XXXXX\SQLADMIN found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 5 seconds.
01/15/2010 18:48:25,spid68,Unknown,DBCC CHECKDB (P5) WITH no_infomsgs executed by XXXXX\SQLADMIN found 0 errors and repaired 0 errors. Elapsed time: 0 hours 7 minutes 54 seconds.
01/15/2010 18:40:29,spid68,Unknown,DBCC CHECKDB (P6) WITH no_infomsgs executed by XXXXX\SQLADMIN found 0 errors and repaired 0 errors. Elapsed time: 0 hours 1 minutes 3 seconds.
01/15/2010 18:39:24,spid68,Unknown,DBCC CHECKDB (P7) WITH no_infomsgs executed by XXXXX\SQLADMIN found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 33 seconds.
01/15/2010 18:38:48,spid73,Unknown,DBCC CHECKDB (P8) WITH no_infomsgs executed by XXXXX\SQLADMIN found 0 errors and repaired 0 errors. Elapsed time: 0 hours 3 minutes 41 seconds.
01/15/2010 18:35:06,spid68,Unknown,DBCC CHECKDB (P9) WITH no_infomsgs executed by XXXXX\SQLADMIN found 0 errors and repaired 0 errors. Elapsed time: 0 hours 2 minutes 52 seconds.
01/15/2010 18:32:12,spid68,Unknown,DBCC CHECKDB (P10) WITH no_infomsgs executed by XXXXX\SQLADMIN found 0 errors and repaired 0 errors. Elapsed time: 0 hours 2 minutes 44 seconds.
01/15/2010 18:29:26,spid68,Unknown,DBCC CHECKDB (P11) WITH no_infomsgs executed by XXXXX\SQLADMIN found 0 errors and repaired 0 errors. Elapsed time: 0 hours 2 minutes 3 seconds.
01/15/2010 18:27:22,spid68,Unknown,DBCC CHECKDB (P12) WITH no_infomsgs executed by XXXXX\SQLADMIN found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 38 seconds.
01/15/2010 18:26:42,spid68,Unknown,DBCC CHECKDB (P13) WITH no_infomsgs executed by XXXXX\SQLADMIN found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 26 seconds.
01/15/2010 18:26:15,spid68,Unknown,DBCC CHECKDB (P14) WITH no_infomsgs executed by XXXXX\SQLADMIN found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 28 seconds.
01/15/2010 18:25:46,spid68,Unknown,DBCC CHECKDB (P15) WITH no_infomsgs executed by XXXXX\SQLADMIN found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 28 seconds.
01/15/2010 18:25:16,spid68,Unknown,DBCC CHECKDB (P16) WITH no_infomsgs executed by XXXXX\SQLADMIN found 0 errors and repaired 0 errors. Elapsed time: 0 hours 1 minutes 15 seconds.
01/15/2010 18:24:00,spid68,Unknown,DBCC CHECKDB (P17) WITH no_infomsgs executed by XXXXX\SQLADMIN found 0 errors and repaired 0 errors. Elapsed time: 0 hours 2 minutes 43 seconds.
01/15/2010 18:21:15,spid68,Unknown,DBCC CHECKDB (P18) WITH no_infomsgs executed by XXXXX\SQLADMIN found 0 errors and repaired 0 errors. Elapsed time: 0 hours 2 minutes 41 seconds.
01/15/2010 18:18:33,spid68,Unknown,DBCC CHECKDB (P19) WITH no_infomsgs executed by XXXXX\SQLADMIN found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 8 seconds.
01/15/2010 18:18:24,spid69,Unknown,DBCC CHECKDB (P20) WITH no_infomsgs executed by XXXXX\SQLADMIN found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 7 seconds.
01/15/2010 18:18:17,spid69,Unknown,DBCC CHECKDB (P21) WITH no_infomsgs executed by XXXXX\SQLADMIN found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 6 seconds.
01/15/2010 18:18:10,spid69,Unknown,DBCC CHECKDB (P22) WITH no_infomsgs executed by XXXXX\SQLADMIN found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 5 seconds.
01/15/2010 18:18:04,spid69,Unknown,DBCC CHECKDB (P23) WITH no_infomsgs executed by XXXXX\SQLADMIN found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 7 seconds.
01/15/2010 18:17:57,spid69,Unknown,DBCC CHECKDB (P24) WITH no_infomsgs executed by XXXXX\SQLADMIN found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 6 seconds.
01/15/2010 18:17:51,spid69,Unknown,DBCC CHECKDB (P25) WITH no_infomsgs executed by XXXXX\SQLADMIN found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 4 seconds.
01/15/2010 18:17:47,spid69,Unknown,DBCC CHECKDB (P26) WITH no_infomsgs executed by XXXXX\SQLADMIN found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 6 seconds.
01/15/2010 18:17:39,spid69,Unknown,DBCC CHECKDB (P27) WITH no_infomsgs executed by XXXXX\SQLADMIN found 0 errors and repaired 0 errors. Elapsed time: 0 hours 7 minutes 22 seconds.
01/15/2010 18:10:15,spid69,Unknown,DBCC CHECKDB (P28) WITH no_infomsgs executed by XXXXX\SQLADMIN found 0 errors and repaired 0 errors. Elapsed time: 0 hours 7 minutes 20 seconds.
01/15/2010 18:02:53,spid73,Unknown,DBCC CHECKDB (P29) WITH no_infomsgs executed by XXXXX\SQLADMIN found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 57 seconds.
01/15/2010 18:01:54,spid73,Unknown,DBCC CHECKDB (P30) WITH no_infomsgs executed by XXXXX\SQLADMIN found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 57 seconds.
01/15/2010 18:00:57,spid70,Unknown,Configuration option 'user options' changed from 0 to 0. Run the RECONFIGURE statement to install.
January 18, 2010 at 10:05 am
Yup, that's the SQL error log. It indicates exactly what I said earlier, the error was not in theDB integrity step (all the CheckDBs finished successfully), it was in one of the later tasks. To find out which one you will need to enable logging on the maintenance plan (or the job that runs it) to get the complete output. That should tell you what failed and why.
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
January 19, 2010 at 11:30 am
Hi Gail,
I got the same eror mess
. ...complete End Progress Progress: 2010-01-18 20:06:05.69 Source: Check Database Integrity Executing query "USE [P1] ".: 50% complete End Progress Progress: 2010-01-18 20:06:11.58 Source: Check Database Integrity Executing query "DBCC CHECKDB WITH NO_INFOMSGS ".: 100% complete End Progress Progress: 2010-01-18 20:06:11.60 Source: Check Database Integrity Executing query "USE [P2] ".: 50% complete End Progress Progress: 2010-01-18 20:06:18.41 Source: Check Database Integrity Executing query "DBCC CHECKDB WITH NO_INFOMSGS ".: 100% complete End Progress Progress: 2010-01-18 20:06:18.41 Source: Check Database Integrity Executing query "USE [P3] ".: 50% complete End Progress Progress: 2010-01-18 20:06:23.72 Source: Check Database Integrity Executing query "DBCC CHECKDB WITH NO_INFOMSGS ".: 100% complete End Progress Progre... The package execution fa... The step failed.
January 19, 2010 at 12:08 pm
That's not a compete output and I cannot see from that what's wrong. Where did that come from? Looks like just the job history.
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
January 19, 2010 at 12:16 pm
That is either the job history or the Job execution logged to a text file.
To find which piece of the maint plan is failing, you will need to enable logging from within the maint plan as Gail as said.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
January 19, 2010 at 12:46 pm
In the MPlan all the checkDb tasks are working fine,even i found no error messages in errorlog,how can i enable logging for it?
January 19, 2010 at 1:01 pm
dba_neo (1/19/2010)
In the MPlan all the checkDb tasks are working fine,even i found no error messages in errorlog,how can i enable logging for it?
It's not the CheckDB tasks - it is one of your other tasks that you have in the maint plan.
This article discusses one option for setting the log.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
January 19, 2010 at 2:58 pm
Team,
I got error as fallows.for reorganizing index.
Executing the query "ALTER INDEX [PK_ume] ON [dbo].[ume] REORGANIZE WITH ( LOB_COMPACTION = ON )
" failed with the following error: "A severe error occurred on the current command. The results, if any, should
be discarded.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly,
parameters not set correctly, or connection not established correctly.
For the Cleanup task Errror MSG:
Executing the query "EXECUTE master.dbo.xp_delete_file 1,N'',N'txt',N'2009-12-22T01:28:11'
" failed with the following error: "Error executing extended stored procedure: Invalid Parameter". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
January 19, 2010 at 3:44 pm
For the Index reorg task, do you get the same error if you disable the "Compact large objects" option?
For the cleanup task, what kinds of files are you attempting to delete? This one seems like a permissions issue.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
January 20, 2010 at 10:35 am
will there be any problem in disabling compact large objects as all my databases contain that table.If not how to disable it and what are the use/disadvantage of disabling?
January 20, 2010 at 11:09 pm
Compact Large Objects is an option in your maintenance plan. It is not required to be enabled. Thus, you should be safe in disabling it.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
Viewing 15 posts - 1 through 14 (of 14 total)
You must be logged in to reply to this topic. Login to reply