Results 1 to 4 of 4
  1. #1
    Join Date
    Aug 2003
    Posts
    2

    Unanswered: SQL Sever 6.5 corruptions ,Msg 2541, Level 16, State 1,etc,etc

    Someone can help me ,
    I have a sqlServer 6.5 SP5a , I have no support or Backups.

    Msg 2504, Level 16, State 1
    Msg 2543, Level 16, State 2
    Msg 2541, Level 16, State 1
    Msg 2531, Level 16, State 2
    Msg 2525, Level 16, State 1

    Where can i get thr rigjt information in oder to solve te problem
    thanks in advance
    Antonio

    When i do a
    dbcc newalloc
    i get


    ************************************************** *************
    TABLE: ALLDatosMiembrosUnidadFamiliar OBJID = 730589791
    INDID=1 FIRST=32568 ROOT=27123 DPAGES=1799 SORT=1
    Data level: 1. 1799 Data Pages in 226 extents.
    Indid : 1. 12 Index Pages in 2 extents.
    INDID=2 FIRST=33200 ROOT=33131 DPAGES=541 SORT=1
    Msg 2541, Level 16, State 1
    Table Corrupt: object id does not match between extent in allocation page and Sysindexes; check the following extent: alloc pg#=32256 extent#=32416 object id on extent=1528496624 (object name = ALLDatosExpedientes) object id in Sysindexes=730589791 (object name = ALLDatosMiembrosUnidadFamiliar)
    Indid : 2. 709 Index Pages in 0 extents.
    TOTAL # of extents = 228
    ************************************************** *************
    TABLE: ALLDatosExpedientes OBJID = 1528496624
    INDID=1 FIRST=7464 ROOT=6395 DPAGES=5338 SORT=1
    Data level: 1. 5338 Data Pages in 671 extents.
    Indid : 1. 49 Index Pages in 7 extents.
    INDID=2 FIRST=8472 ROOT=31483 DPAGES=210 SORT=1
    Msg 2504, Level 16, State 1
    Table Corrupt: The index id in alloc page does not match the index id in Sysindexes (alloc page#=27136; extent id=27208; index id in alloc=255; index id in Sysindexes=2)
    Msg 2543, Level 16, State 2
    Table Corrupt: Extent structures are linked incorrectly; check the following extent: alloc pg#=27136 extent#=27208 previous extent# on this extent=27288 previous extent should be=31408
    Indid : 2. 251 Index Pages in 0 extents.
    INDID=3 FIRST=37288 ROOT=16241 DPAGES=130 SORT=1
    Indid : 3. 132 Index Pages in 18 extents.
    INDID=4 FIRST=9864 ROOT=10019 DPAGES=205 SORT=1
    Indid : 4. 558 Index Pages in 71 extents.
    INDID=255 FIRST=488 ROOT=37152 DPAGES=0 SORT=0
    TOTAL # of extents = 3257
    ************************************************** *************
    TABLE: ALLDatosEnfermedades_old OBJID = 1647449043
    INDID=1 FIRST=11024 ROOT=10896 DPAGES=198 SORT=1
    Data level: 1. 167 Data Pages in 21 extents.
    Indid : 1. 2 Index Pages in 1 extents.
    INDID=255 FIRST=648 ROOT=648 DPAGES=0 SORT=0
    Msg 2541, Level 16, State 1
    Table Corrupt: object id does not match between extent in allocation page and Sysindexes; check the following extent: alloc pg#=16896 extent#=16936 object id on extent=-1528496624 (object name = -1528496624) object id in Sysindexes=1647449043 (object name = ALLDatosEnfermedades_old)
    TOTAL # of extents = 22
    ************************************************** *************
    TABLE: OLDDatosMiembrosUnidadFamiliar OBJID = 1723973318
    INDID=1 FIRST=5584 ROOT=3043 DPAGES=1895 SORT=1
    Msg 2541, Level 16, State 1
    Table Corrupt: object id does not match between extent in allocation page and Sysindexes; check the following extent: alloc pg#=5376 extent#=5584 object id on extent=1528496624 (object name = ALLDatosExpedientes) object id in Sysindexes=1723973318 (object name = OLDDatosMiembrosUnidadFamiliar)
    Msg 2531, Level 16, State 2
    Table Corrupt: Index id on extent should be 0; check the following page and ids: alloc page=5376 extent=5584 index id on extent=255
    Msg 2525, Level 16, State 1
    Table Corrupt: Object id wrong; tables: alloc page 5376 extent id=5584 l page#=5584 objid in ext=1528496624 (name = ALLDatosExpedientes) objid in page=1528496624 (name = ALLDatosExpedientes)objid in sysindexes=1723973318 (name = OLDDatosMiembrosUnidadFamiliar)
    Data level: 1. 0 Data Pages in 0 extents.
    INDID=2 FIRST=10432 ROOT=10475 DPAGES=308 SORT=1
    Indid : 2. 829 Index Pages in 104 extents.
    TOTAL # of extents = 104
    ************************************************** *************

  2. #2
    Join Date
    Jul 2003
    Location
    San Antonio, TX
    Posts
    3,662
    Did it report at the end that it fixed errors?

    Also, note the indexes and re-create them. Make sure that you backup the db after you drop them before you start CREATE statement script.

  3. #3
    Join Date
    Aug 2003
    Posts
    2
    Tne dbcc newalloc finish with a
    "Transaction has been aborted."
    and no error was fixed

    The tables have some index may i have to rebuild all of them?

  4. #4
    Join Date
    Jul 2003
    Location
    San Antonio, TX
    Posts
    3,662
    I absolutely will. But as I said earlier, make sure you backup the database ... actually, I would back it up before doing anything, right after dropping indexes, and of course, after indexes are recreated. Also, after you drop the indexes and backup the db, run newalloc and see if errors are still being reported. My hunch is that there won't be any errors at that point. If this is the case, analyze all the indexes that you're about to create and sequence them so that clustered indexes get created first.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •