Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Sarat
Constraint Violating Yak Guru
265 Posts |
 Posted - 2002-09-20 : 12:49:03
|
| Hello, SQL Server 2000 - I have a maintenance job setup every night just before 1/2 hour of full prod db backup to perform db integrity check (Include Indexes option checked). The step failed but the job succeeded - so no error message was written to sql logs but because I had setup a net-send, I got message that said:"The job failed. The Job was invoked by Schedule 5 (Schedule 1). The last step to run was step 1 (Step 1)."Now I don't understand what went wrong but here are some things I noticed.1. I have a log backup occurring every hour. Weirdly, after 6 PM, the next log backup was at 8.30 PM instead of 7 PM. The CHECKDB step is also setup to occur at 8.30 PM.Did this cause problem because of locking (DML ok but no DDL)?2. Is it possible that if there is no database activity, the every hr log backup will not really happen every hour? I am unable to understand why there was no 7 PM or 8 PM backup or why the system waited so long from 6 PM to 8.30 PM to perform log backup. There was no user activity after 5.30 PM on the db.3. I have 30 GB space for my temp db on a different drive, day before I had to store a 15 GB file (now tempdb has 15 free space gb left).due to space constraints on a different box. -- Right now Tempdb.mdf = 3 GB and ldf = 512MB.Could this affect anything?Thanks,Sarat. |
|
|
jasper_smith
SQL Server MVP & SQLTeam MVY
846 Posts |
Posted - 2002-09-20 : 13:27:35
|
| You can usually find why it failed from either the SQl Error Log, The Maintenance Plan History or the Maintenance Plan Text Report if specified. Do you have the repair minor problems selected on the maintenance plan ?HTHJasper Smith |
 |
|
|
Sarat
Constraint Violating Yak Guru
265 Posts |
Posted - 2002-09-20 : 14:02:28
|
| No I don't have that option checked. First thing I checked was SQL Error Log and then Maintenance history, that error msg is the only thing I found on Maintenance History. It wasn't on Error Log which surprised me but I assumed that because the plan also included full backup which was successful, the step failed was not written to the error log.Sarat. |
|
|
|
|
|
|
DBCC CHECKDB Error & TempDB