Interesting Maintenance Plan Problem

SQL Server 2005 - I created a maintenance plan to backup several
databases. The steps in the maintenance plan are very simple, first -
check database integrity, next reindex or reorganize the indexes, backup
the databases and finally remove backup files.
I set the schedule to begin at 12:05am and tested the process by
manually running (right-click on the job and start at step). The
process ran successfully, all steps.
That night, the process started at 12:05 and failed after the second
step with no indication why the process failed. I ran it manually and
it completed successfully. The following night the process failed after
the first step completed, again with no indication why the process
failed. Again, I ran the process manually and it completed all steps
successfully.
I modified the schedule to run at 12:30am instead - and all steps
completed successfully.
Does anybody have any ideas why the process would fail when scheduled to
run at 12:05, but not fail when scheduled to run at 12:30?
JeffDid something have the database in use?
Jeffrey Williams wrote:
> SQL Server 2005 - I created a maintenance plan to backup several
> databases. The steps in the maintenance plan are very simple, first -
> check database integrity, next reindex or reorganize the indexes, backup
> the databases and finally remove backup files.
> I set the schedule to begin at 12:05am and tested the process by
> manually running (right-click on the job and start at step). The
> process ran successfully, all steps.
> That night, the process started at 12:05 and failed after the second
> step with no indication why the process failed. I ran it manually and
> it completed successfully. The following night the process failed after
> the first step completed, again with no indication why the process
> failed. Again, I ran the process manually and it completed all steps
> successfully.
> I modified the schedule to run at 12:30am instead - and all steps
> completed successfully.
> Does anybody have any ideas why the process would fail when scheduled to
> run at 12:05, but not fail when scheduled to run at 12:30?
> Jeff
--
Brett I. Holcomb
brettholcomb@.R777bellsouth.net
Remove R777 to email|||Jeffrey
Have you looked at ERROR.LOG ? Any entries?
"Jeffrey Williams" <jeff.williams3188@.verizon.net> wrote in message
news:OeWJCO$nHHA.208@.TK2MSFTNGP05.phx.gbl...
> SQL Server 2005 - I created a maintenance plan to backup several
> databases. The steps in the maintenance plan are very simple, first -
> check database integrity, next reindex or reorganize the indexes, backup
> the databases and finally remove backup files.
> I set the schedule to begin at 12:05am and tested the process by manually
> running (right-click on the job and start at step). The process ran
> successfully, all steps.
> That night, the process started at 12:05 and failed after the second step
> with no indication why the process failed. I ran it manually and it
> completed successfully. The following night the process failed after the
> first step completed, again with no indication why the process failed.
> Again, I ran the process manually and it completed all steps successfully.
> I modified the schedule to run at 12:30am instead - and all steps
> completed successfully.
> Does anybody have any ideas why the process would fail when scheduled to
> run at 12:05, but not fail when scheduled to run at 12:30?
> Jeff|||Uri,
I looked in every log I could find - no errors, just the job stopped,
reporting a failure.
Jeff
Uri Dimant wrote:
> Jeffrey
> Have you looked at ERROR.LOG ? Any entries?
>
>
> "Jeffrey Williams" <jeff.williams3188@.verizon.net> wrote in message
> news:OeWJCO$nHHA.208@.TK2MSFTNGP05.phx.gbl...
>> SQL Server 2005 - I created a maintenance plan to backup several
>> databases. The steps in the maintenance plan are very simple, first -
>> check database integrity, next reindex or reorganize the indexes, backup
>> the databases and finally remove backup files.
>> I set the schedule to begin at 12:05am and tested the process by manually
>> running (right-click on the job and start at step). The process ran
>> successfully, all steps.
>> That night, the process started at 12:05 and failed after the second step
>> with no indication why the process failed. I ran it manually and it
>> completed successfully. The following night the process failed after the
>> first step completed, again with no indication why the process failed.
>> Again, I ran the process manually and it completed all steps successfully.
>> I modified the schedule to run at 12:30am instead - and all steps
>> completed successfully.
>> Does anybody have any ideas why the process would fail when scheduled to
>> run at 12:05, but not fail when scheduled to run at 12:30?
>> Jeff
>
>|||Brett,
There are no other scheduled jobs at that time, except for the
transaction log files that run every 15 minutes and take less than a
minute to run at that time (no users on the system at midnight).
Jeff
Brett I. Holcomb wrote:
> Did something have the database in use?
>
> Jeffrey Williams wrote:
>> SQL Server 2005 - I created a maintenance plan to backup several
>> databases. The steps in the maintenance plan are very simple, first
>> - check database integrity, next reindex or reorganize the indexes,
>> backup the databases and finally remove backup files.
>> I set the schedule to begin at 12:05am and tested the process by
>> manually running (right-click on the job and start at step). The
>> process ran successfully, all steps.
>> That night, the process started at 12:05 and failed after the second
>> step with no indication why the process failed. I ran it manually
>> and it completed successfully. The following night the process
>> failed after the first step completed, again with no indication why
>> the process failed. Again, I ran the process manually and it
>> completed all steps successfully.
>> I modified the schedule to run at 12:30am instead - and all steps
>> completed successfully.
>> Does anybody have any ideas why the process would fail when scheduled
>> to run at 12:05, but not fail when scheduled to run at 12:30?
>> Jeff
>|||How about the report file for the maint plan? Anything there?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Jeffrey Williams" <jeff.williams3188@.verizon.net> wrote in message
news:4659B188.5000608@.verizon.net...
> Uri,
> I looked in every log I could find - no errors, just the job stopped, reporting a failure.
> Jeff
> Uri Dimant wrote:
>> Jeffrey
>> Have you looked at ERROR.LOG ? Any entries?
>>
>>
>> "Jeffrey Williams" <jeff.williams3188@.verizon.net> wrote in message
>> news:OeWJCO$nHHA.208@.TK2MSFTNGP05.phx.gbl...
>> SQL Server 2005 - I created a maintenance plan to backup several databases. The steps in the
>> maintenance plan are very simple, first - check database integrity, next reindex or reorganize
>> the indexes, backup the databases and finally remove backup files.
>> I set the schedule to begin at 12:05am and tested the process by manually running (right-click
>> on the job and start at step). The process ran successfully, all steps.
>> That night, the process started at 12:05 and failed after the second step with no indication why
>> the process failed. I ran it manually and it completed successfully. The following night the
>> process failed after the first step completed, again with no indication why the process failed.
>> Again, I ran the process manually and it completed all steps successfully.
>> I modified the schedule to run at 12:30am instead - and all steps completed successfully.
>> Does anybody have any ideas why the process would fail when scheduled to run at 12:05, but not
>> fail when scheduled to run at 12:30?
>> Jeff
>>|||Tibor Karaszi wrote:
> How about the report file for the maint plan? Anything there?
>
Nothing there either - the job just stops. I even reviewed the default
trace file and did not find anything there.
I can schedule the process at 12:30am and leave it there, but I was
hoping somebody else had seen something like this. I will keep
researching to see if I can find anything.
Thanks,
Jeffsql