Post reply

Msg 5245 sys.sysschobjs SQL2008

  • December 20, 2010 at 10:55 am

    #230899

    I run a "dbcc checkdb with physical_only" using sp_msforeachdb and the process has started failing on TempDB, unable to obtain a lock on sys.sysschobjs. The same process runs successfully in all my other SQL2005 and SQL2008 instances. Any ideas on what the problem might be? Is it just too much TempDB activity while I'm trying to run the check?

    The failing instance is SQL2008-EE, sp1 (10.00.4000)

    Thanks in advance,

    Dale

  • December 20, 2010 at 11:27 am

    #1264727

    Is it just too much TempDB activity while I'm trying to run the check?

    I guess so.

    The failing instance is SQL2008-EE, sp1 (10.00.4000)

    FYI, 4000 is SP2.

  • December 20, 2010 at 11:57 am

    #1264738

    Yes, SP2. Fat-fingered.:alien:

  • December 20, 2010 at 1:40 pm

    #1264785

    Post the exact errors please.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • December 20, 2010 at 1:51 pm

    #1264793

    DBCC could not obtain a lock on this object because the lock request timeout period was exceeded. This object has been skipped and will not be processed. [SQLSTATE 42000] (Error 5245).

    This error has been consistent over the past few week's job runs.

    Thanks.

  • February 27, 2014 at 2:53 am

    #1692589

    Hi Dale

    Did you ever find a fix / cause for this issue?

    We're seeing the exact same error on our nightly consistency checks (for the past 3 nights consistently - never occurred prior to that):

    Unable to run DBCC on database tempdb: Object ID 34 (object 'sys.sysschobjs'): DBCC could not obtain a lock on this object because the lock request timeout period was exceeded. This object has been skipped and will not be processed.

    SQL Version: 10.50.4000

    Knock Knock, Who's There?, sp underscore, sp underscore who?
    spid1, spid2, spid3....

  • February 27, 2014 at 6:14 am

    #1692628

    I'm sure I would have posted the fix here if I had one at the time. Sorry, I don't remember what server I was getting this on so I can't for certain tell you a specific upgrade or patch that may have been applied, or if whatever was causing the error just stopped preventing the lock.

    If you do find a specific fix, please post it here so others like yourself might benefit.

    Thanks and good luck.

    Dale.

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply