Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

sysjobhistory is not updated

Status
Not open for further replies.

MissTipps

Programmer
May 20, 2002
91
GB
Hi

Last night, for no apparent reason, our production server stopped logging job execution to the sysjobhistory table. I have checked the following:

1. Job owner account
2. Space in sysjobhistory table
3. Jobs are actually completing (tested with backups), but no log is written to sysjobhistory and also e-mail notifications are not sending.
4. No errors are being written to either the SQL Server log or the Windows App Log.

Any thoughts would be greatly appreciated - 2 DBAs are going crazy here.

Many thanks



MissTipps

CISSP, CEH, CEI, MCT, MCDBA, MCSE 2K3, CTT+, ECSA, Security+
 
Hi MissTipps,

this is only a wild stab in the dark, but worth throwing any ideas in.......Is the msdb (or the disk it is on) full (i.e. no free space to write to)?
 
Hi

Thanks for the suggestion, but no, thats not the problem. It seems that none of the completion steps to update system tables are running and I've no idea why. Basically the last job step runs and thats it. On completion it should run the sp_sqlagent_log_jobhistory then run a couple more updates to system tables, but it doesn't.

Thanks

MissTipps

CISSP, CEH, CEI, MCT, MCDBA, MCSE 2K3, CTT+, ECSA, Security+
 
Restart the agent?

Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005) / MCITP Database Administrator (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)
[noevil]
 
You might also want to monitor the tempdb with Profiler during the actual job executions. If the tempdb is filling up the disk during the running of the job, it might cause problems with MSDB being able to function properly.

And since the tempdb dumps after it's use, depending on how you have your optimizations set up, you might never "see" the HD getting full because it'll be back to normal size by morning.

Just another bizzare thought. @=)


Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top