SQL 2005 stops and restarts unexpectedly - Event ID:602

  • SQL server 2005 - SP2

    Server Stops and restarts unexpectedly.

    The error logged in windows is as follows:

    Event Type:Error

    Event Source:MSSQLSERVER

    Event Category:(2)

    Event ID:602

    Date:5/28/2011

    Time:10:55:47 PM

    User:N/A

    Computer:CUFDBP2

    Description:

    Could not find an entry for table or index with partition ID 489800837038080 in database 2. This error can occur if a stored procedure references a dropped table, or metadata is corrupted. Drop and re-create the stored procedure, or execute DBCC CHECKDB.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Data:

    0000: 5a 02 00 00 15 00 00 00 Z.......

    0008: 08 00 00 00 43 00 55 00 ....C.U.

    0010: 46 00 44 00 42 00 50 00 F.D.B.P.

    0018: 32 00 00 00 0c 00 00 00 2.......

    0020: 43 00 6f 00 6e 00 74 00 C.o.n.t.

    0028: 69 00 6e 00 75 00 75 00 i.n.u.u.

    0030: 6d 00 44 00 42 00 00 00 m.D.B...

    I found an KB article related to this event id here:

    http://support.microsoft.com/kb/937343

    They have a hot fix. When I tried to apply it it looked like it was already applied. Now I would assume next option is to install SP4?

    What do you think?

  • Does the SQL Server service start at all or does this occur when you're trying to access a specific database? Offhand I'd say it looks like you have database corruption on one of your system databases. Do you have recent backups of your system databases?

    =============================================================
    /* Backups are worthless, Restores are priceless */

    Get your learn on at SQL University!
    Follow me on Twitter | Connect on LinkedIn
    My blog: http://sqlchicken.com
    My book: Pro Server 2008 Policy-Based Management

  • That's a known bug. Patch your instance to the latest service pack.

    The fix is part of SP2 CU3, or just patch to SP4 straight.

    (http://support.microsoft.com/kb/939537/ ) Cumulative update package 3 for SQL Server 2005 Service Pack 2

    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
  • Sqlchicken (6/16/2011)


    Offhand I'd say it looks like you have database corruption on one of your system databases.

    TempDB.

    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
  • GilaMonster (6/16/2011)


    Sqlchicken (6/16/2011)


    Offhand I'd say it looks like you have database corruption on one of your system databases.

    TempDB.

    Ah ok, thanks. I knew the lower ones were system, can never remember which one is which (and honestly was too lazy to look it up :-P)

    =============================================================
    /* Backups are worthless, Restores are priceless */

    Get your learn on at SQL University!
    Follow me on Twitter | Connect on LinkedIn
    My blog: http://sqlchicken.com
    My book: Pro Server 2008 Policy-Based Management

  • Should I work on correcting the problems (if any in the temp DB), or just apply the service pack.

    We have an application that uses the database and it's aknown what an upgrade (with SP4) would do to it.

    So this is maybe our last resort. I am thinking maybe I can do a "'DBCC CHECKDB(''tempDB'')'?

  • techzone12 (6/16/2011)


    Should I work on correcting the problems (if any in the temp DB), or just apply the service pack.

    We have an application that uses the database and it's aknown what an upgrade (with SP4) would do to it.

    So this is maybe our last resort. I am thinking maybe I can do a "'DBCC CHECKDB(''tempDB'')'?

    You can't repair TempDB, and besides it's a bug so it'll come back.

    SP2 is long out of support, you really should be on SP4.

    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
  • OK. We are going to try Service Pack 4.

    Thanks for the help

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

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