June 23, 2009 at 9:35 am
1.Date6/8/2009 12:01:13 AM
LogSQL Server (Current - 6/23/2009 10:52:00 AM)
Sourcespid1211
Message
(1:1410)/(1:1410)2137058649/2089058478
2.Date6/8/2009 12:01:13 AM
LogSQL Server (Current - 6/23/2009 10:52:00 AM)
Sourcespid1211
Message
pageno is/should be:objid is/should be:
3.Date6/8/2009 12:01:13 AM
LogSQL Server (Current - 6/23/2009 10:52:00 AM)
Sourcespid1211
Message
Getpage: bstat=0x9, sstat=0x2800, cache
4.Date6/8/2009 12:01:13 AM
LogSQL Server (Current - 6/23/2009 10:52:00 AM)
Sourcespid1211
Message
Attempt to fetch logical page (1:1410) in database 'msdb' belongs to object 'sysjobsteps', not to object 'sysjobsteps'..
June 23, 2009 at 10:11 am
Sometimes this error goes way after restarting sql server.
Run dbcc checkdb in msdb database.
if you see any allocation or consistency errors refer to this doc (only if you have backups) on how to restore MSDB.
http://msdn.microsoft.com/en-us/library/ms190749.aspx
June 23, 2009 at 10:23 am
CHECKDB found 0 allocation errors and 0 consistency errors in database 'msdb'. So is this mean that these error happend after restarting. I have transaction job running at that time
June 23, 2009 at 10:52 am
Do you still see these errors when you run that transaction job?
If yes and if there are more and more errors this post might be helpful
http://www.sqlservercentral.com/Forums/Topic653669-265-1.aspx
Refer to this article on how to rebuild MSDB
http://blogs.msdn.com/sqlserverstorageengine/archive/2006/06/06/619304.aspx
June 23, 2009 at 11:12 am
try this:
DBCC TRACEON (first run this) then
DBCC TRACESTATUS(-1)
and post the results (if any)
Maninder
www.dbanation.com
June 23, 2009 at 11:48 am
No, I don't see any errors anymore this is was only one time when transaction job ran.I wanted to know why is this happening and do I need to do anything?Thank you
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply