Link to home
Start Free TrialLog in
Avatar of Projack
Projack

asked on

Database Integrity Check Task created with maintenance plan failed to run

I used the maintenance plan wizard to create Database Integrity Check Task and the job failed. The error message is:
OB RUN:      'Integrity Checks Job For FO_DB.Subplan_1' was run on 2/22/2009 at 12:05:00 AM
DURATION:      0 hours, 0 minutes, 2 seconds
STATUS:       Failed
MESSAGES:      The job failed.  The Job was invoked by Schedule 86 (Integrity Checks Job For FO_DB.Subplan_1).  The last step to run was step 1 (Subplan_1).

The event log, the job history and alert does not provide me with the information why the job failled.

How could I found out why the job failed?

Avatar of reb73
reb73
Flag of Ireland image

Edit the properties of the job (maintenance plan creates individual jobs for different actions) and log the history of the job step in a predefined file using the Advanced tab..

Execute the job and check the log file for a more accurate reporting of the actual error and post it here if necessary
Avatar of chapmandew
right click the job, go to history. find the step where the job failed and double click it...there you have details.
Avatar of Projack
Projack

ASKER

The error in the View history is, no detail

Step ID                 0
Server                   FOvB
Job Name              Integrity Checks Job For Fo_DB.Subplan_1
Step Name            (Job outcome)
Duration                00:00:02
Sql Severity           0
Sql Message ID               0
Retries Attempted           0
This si the message I found from the predetermine file I attached from the advanced tab

Started:  12:05:00 AM
DTExec: The package execution returned DTSER_FAILURE (1).
Started:  12:05:00 AM
Finished: 12:05:01 AM
Elapsed:  1.61 seconds
 
MessageThe job failed.  The Job was invoked by Schedule 86 (Integrity Checks Job For Fo_DB.Subplan_1).  The last step to run was step 1 (Subplan_1).
This is the log file report on the task
Microsoft(R) Server Maintenance Utility (Unicode) Version 10.0.1779
Report was generated on "FOvB".
Maintenance Plan: Integrity Checks Job For FO_DB
Duration: 00:00:01
Status: Warning: One or more tasks failed.
Details:
Check Database Integrity (FOvB)
Check Database integrity on Local server connection
Databases: FO_DB
Include indexes
Task start: 2009-02-22T00:05:00.
Task end: 2009-02-22T00:05:01.
Failed:(0) Alter failed for Server FOvB.
The is the message I foung in thr Error log at the time the task was suppose to be executed


2009-02-22 00:05:08.59 spid70      DBCC CHECKDB (mssqlsystemresource) WITH no_infomsgs executed by ASC_WEST\SQLAdmin found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 4 seconds.  
2009-02-22 00:30:01.03 spid61      Configuration option 'user options' changed from 0 to 0. Run the RECONFIGURE statement to install.
2009-02-22 00:30:01.03 spid61      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.2009-02-22 00:55:14.23 spid6s      SQL Server has encountered 412 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\Program Files\Microsoft SQL
I could I make a sense of this or what elese could I do?
 
ASKER CERTIFIED SOLUTION
Avatar of mastoo
mastoo
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial