Post reply

Restore could not start DB.

  • December 25, 2008 at 10:30 pm

    #128770

    A SS2K back up db is restoring on ss2k5 then error coming:

    Error:Restore could not start DB.

    Any help:

    Thnx

    Thanks

  • December 25, 2008 at 11:22 pm

    #917689

    Is there any explanation in the SQL Server Log?

    I think the orginal database (in SS2K) has issues. Have you run DBCC CHECKDB before taking backup?

  • December 26, 2008 at 12:00 am

    #917696

    Dear All

    on running DBCC CheckDB

    I got:

    Server: Msg 8928, Level 16, State 1, Line 1

    Object ID 293576084, index ID 0: Page (1:629) could not be processed. See other errors for details.

    Server: Msg 8939, Level 16, State 1, Line 1

    Table error: Object ID 293576084, index ID 0, page (1:629). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.

    Server: Msg 8928, Level 16, State 1, Line 1

    Object ID 293576084, index ID 0: Page (1:632) could not be processed. See other errors for details.

    DBCC results for 'postnet'.

    DBCC results for 'sysobjects'.

    There are 131 rows in 3 pages for object 'sysobjects'.

    DBCC results for 'sysindexes'.

    There are 256 rows in 11 pages for object 'sysindexes'.

    DBCC results for 'syscolumns'.

    There are 1453 rows in 27 pages for object 'syscolumns'.

    DBCC results for 'systypes'.

    There are 26 rows in 1 pages for object 'systypes'.

    DBCC results for 'syscomments'.

    There are 143 rows in 21 pages for object 'syscomments'.

    DBCC results for 'sysfiles1'.

    There are 2 rows in 1 pages for object 'sysfiles1'.

    DBCC results for 'syspermissions'.

    There are 49 rows in 1 pages for object 'syspermissions'.

    DBCC results for 'sysusers'.

    There are 14 rows in 1 pages for object 'sysusers'.

    DBCC results for 'sysproperties'.

    There are 0 rows in 0 pages for object 'sysproperties'.

    DBCC results for 'sysdepends'.

    There are 349 rows in 2 pages for object 'sysdepends'.

    DBCC results for 'sysreferences'.

    There are 0 rows in 0 pages for object 'sysreferences'.

    DBCC results for 'sysfulltextcatalogs'.

    There are 0 rows in 0 pages for object 'sysfulltextcatalogs'.

    DBCC results for 'sysfulltextnotify'.

    There are 0 rows in 0 pages for object 'sysfulltextnotify'.

    DBCC results for 'sysfilegroups'.

    There are 1 rows in 1 pages for object 'sysfilegroups'.

    DBCC results for 'M_Division'.

    There are 696 rows in 5 pages for object 'M_Division'.

    DBCC results for 'm_locationwiseequipment'.

    There are 6778 rows in 32 pages for object 'm_locationwiseequipment'.

    DBCC results for 'M_NicCo_Ord'.

    There are 696 rows in 5 pages for object 'M_NicCo_Ord'.

    DBCC results for 'm_postalblock_phaseI'.

    There are 1157 rows in 44 pages for object 'm_postalblock_phaseI'.

    DBCC results for 'postnet.m_postalblock_Binary'.

    There are 1127 rows in 41 pages for object 'postnet.m_postalblock_Binary'.

    DBCC results for 'postnet.m_postalblock_PartI'.

    There are 1127 rows in 43 pages for object 'postnet.m_postalblock_PartI'.

    DBCC results for 'M_PostOfficeTypeMaster'.

    There are 0 rows in 0 pages for object 'M_PostOfficeTypeMaster'.

    DBCC results for 'm_regionmaster'.

    There are 55 rows in 1 pages for object 'm_regionmaster'.

    DBCC results for 'M_StateMaster_phaseI'.

    There are 35 rows in 1 pages for object 'M_StateMaster_phaseI'.

    DBCC results for 'Rpt_Delivery_Install'.

    There are 32 rows in 1 pages for object 'Rpt_Delivery_Install'.

    DBCC results for 'Rpt_EquipmentVendor'.

    There are 544 rows in 20 pages for object 'Rpt_EquipmentVendor'.

    DBCC results for 'Seq_Faq'.

    There are 2 rows in 1 pages for object 'Seq_Faq'.

    DBCC results for 'SEQ_GEN'.

    There are 2 rows in 1 pages for object 'SEQ_GEN'.

    DBCC results for 'SEQ_GEN_Complaint'.

    There are 2 rows in 1 pages for object 'SEQ_GEN_Complaint'.

    DBCC results for 'postnet.TempLan_Details'.

    Server: Msg 8939, Level 16, State 98, Line 1

    Table error: Object ID 293576084, index ID 0, page (1:632). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.

    Server: Msg 8928, Level 16, State 1, Line 1

    Object ID 293576084, index ID 0: Page (1:636) could not be processed. See other errors for details.

    Server: Msg 8944, Level 16, State 1, Line 1

    Table error: Object ID 293576084, index ID 0, page (1:636), row 15. Test (columnOffsets->offTbl [varColumnNumber] >= priorOffset) failed. Values are 46 and 130.

    Server: Msg 8928, Level 16, State 1, Line 1

    Object ID 293576084, index ID 0: Page (1:642) could not be processed. See other errors for details.

    Server: Msg 8944, Level 16, State 1, Line 1

    Table error: Object ID 293576084, index ID 0, page (1:642), row 22. Test (columnOffsets->offTbl [varColumnNumber] >= priorOffset) failed. Values are 46 and 122.

    There are 416 rows in 12 pages for object 'postnet.TempLan_Details'.

    CHECKDB found 0 allocation errors and 8 consistency errors in table 'postnet.TempLan_Details' (object ID 293576084).

    DBCC results for 'TMP_SiteStatus'.

    There are 0 rows in 0 pages for object 'TMP_SiteStatus'.

    DBCC results for 'dtproperties'.

    There are 0 rows in 0 pages for object 'dtproperties'.

    DBCC results for 'RouterDtls'.

    There are 3872 rows in 17 pages for object 'RouterDtls'.

    DBCC results for 'Old_M_StateMaster'.

    There are 35 rows in 1 pages for object 'Old_M_StateMaster'.

    DBCC results for 'Old_M_DistrictMaster'.

    There are 659 rows in 15 pages for object 'Old_M_DistrictMaster'.

    DBCC results for 'm_statemaster_old'.

    There are 35 rows in 1 pages for object 'm_statemaster_old'.

    DBCC results for 'M_DistrictMaster'.

    There are 647 rows in 17 pages for object 'M_DistrictMaster'.

    DBCC results for 'm_postalblock'.

    There are 1949 rows in 83 pages for object 'm_postalblock'.

    DBCC results for 'custodian'.

    There are 1374 rows in 29 pages for object 'custodian'.

    DBCC results for 'today_po_details'.

    There are 4550 rows in 142 pages for object 'today_po_details'.

    DBCC results for 'today_m_locationwiseequipment'.

    There are 4550 rows in 21 pages for object 'today_m_locationwiseequipment'.

    DBCC results for 'ACCESSRECORD'.

    There are 20050 rows in 182 pages for object 'ACCESSRECORD'.

    DBCC results for 'Complaint_Remarks'.

    There are 34 rows in 1 pages for object 'Complaint_Remarks'.

    DBCC results for 'faqmenu'.

    There are 26 rows in 1 pages for object 'faqmenu'.

    DBCC results for 'FlowDetails'.

    There are 2 rows in 1 pages for object 'FlowDetails'.

    DBCC results for 'M_postalblock_cms'.

    There are 1914 rows in 89 pages for object 'M_postalblock_cms'.

    DBCC results for 'menuitems4po_old'.

    There are 14 rows in 1 pages for object 'menuitems4po_old'.

    DBCC results for 'ProblemReport'.

    There are 5 rows in 1 pages for object 'ProblemReport'.

    DBCC results for 'TroubleShoot_Menu'.

    There are 60 rows in 1 pages for object 'TroubleShoot_Menu'.

    DBCC results for 'SEQ_GEN_Workflow'.

    There are 1 rows in 1 pages for object 'SEQ_GEN_Workflow'.

    DBCC results for 'WorkFlow'.

    There are 3 rows in 1 pages for object 'WorkFlow'.

    DBCC results for 'complaints'.

    There are 12 rows in 1 pages for object 'complaints'.

    DBCC results for 'faq'.

    There are 81 rows in 8 pages for object 'faq'.

    DBCC results for 'M_EquipmentMaster'.

    There are 21 rows in 1 pages for object 'M_EquipmentMaster'.

    DBCC results for 'cms_equipmentmaster'.

    There are 21 rows in 1 pages for object 'cms_equipmentmaster'.

    DBCC results for 'cms_vendormaster'.

    There are 21 rows in 1 pages for object 'cms_vendormaster'.

    DBCC results for 'M_VendorMaster'.

    There are 21 rows in 1 pages for object 'M_VendorMaster'.

    DBCC results for 'Phase2'.

    There are 776 rows in 14 pages for object 'Phase2'.

    DBCC results for 'PHASE1'.

    There are 544 rows in 10 pages for object 'PHASE1'.

    DBCC results for 'm_statemaster'.

    There are 35 rows in 2 pages for object 'm_statemaster'.

    DBCC results for 'LAND_Details_OldRcd'.

    There are 636 rows in 17 pages for object 'LAND_Details_OldRcd'.

    DBCC results for 'LAN_DETAILS_Till22Aug08'.

    There are 685 rows in 17 pages for object 'LAN_DETAILS_Till22Aug08'.

    DBCC results for 'phase_dtls'.

    There are 3 rows in 1 pages for object 'phase_dtls'.

    DBCC results for 'LAN_DETAILS'.

    There are 1322 rows in 52 pages for object 'LAN_DETAILS'.

    DBCC results for 'menuitems4po'.

    There are 23 rows in 1 pages for object 'menuitems4po'.

    DBCC results for 'postalblockcount'.

    There are 539 rows in 3 pages for object 'postalblockcount'.

    DBCC results for 'postalblockcount_tmp'.

    There are 389 rows in 2 pages for object 'postalblockcount_tmp'.

    DBCC results for 'Loc_754'.

    There are 755 rows in 13 pages for object 'Loc_754'.

    DBCC results for 'postnet.chk_m_postalblock'.

    There are 1127 rows in 43 pages for object 'postnet.chk_m_postalblock'.

    DBCC results for 'Circle_Details'.

    There are 22 rows in 1 pages for object 'Circle_Details'.

    DBCC results for 'new_po'.

    There are 1359 rows in 19 pages for object 'new_po'.

    DBCC results for 'm_postalblock_24Sep08'.

    There are 1949 rows in 83 pages for object 'm_postalblock_24Sep08'.

    DBCC results for 'LAN_DETAILS_OLD'.

    There are 579 rows in 16 pages for object 'LAN_DETAILS_OLD'.

    DBCC results for 'CUSTODIAN_phaseI'.

    There are 574 rows in 11 pages for object 'CUSTODIAN_phaseI'.

    DBCC results for 'HOdatabase492'.

    There are 544 rows in 25 pages for object 'HOdatabase492'.

    DBCC results for 'po_details'.

    There are 6779 rows in 285 pages for object 'po_details'.

    DBCC results for 'LLStatusDetails'.

    There are 1318 rows in 76 pages for object 'LLStatusDetails'.

    DBCC results for 'M_DistrictMaster_PhaseI'.

    There are 519 rows in 11 pages for object 'M_DistrictMaster_PhaseI'.

    CHECKDB found 0 allocation errors and 8 consistency errors in database 'postnet'.

    repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (postnet ).

    DBCC execution completed. If DBCC printed error messages, contact your system administrator.

    Thanks

  • December 26, 2008 at 12:26 am

    #917699

    Table error: Object ID 293576084, index ID 0, page (1:636), row 15. Test (columnOffsets->offTbl [varColumnNumber] >= priorOffset) failed. Values are 46 and 130.

    Server: Msg 8928, Level 16, State 1, Line 1

    Object ID 293576084, index ID 0: Page (1:642) could not be processed. See other errors for details.

    Server: Msg 8944, Level 16, State 1, Line 1

    Table error: Object ID 293576084, index ID 0, page (1:642), row 22. Test (columnOffsets->offTbl [varColumnNumber] >= priorOffset) failed. Values are 46 and 122.

    There are 416 rows in 12 pages for object 'postnet.TempLan_Details'.

    CHECKDB found 0 allocation errors and 8 consistency errors in table 'postnet.TempLan_Details' (object ID 293576084).

    Some indexes a currupted. Rebuilding them may fix it.

  • December 26, 2008 at 12:30 am

    #917700

    The database displaying as : postnet(suspect)

    postnet is my databse name.

    Thanks

  • December 26, 2008 at 12:30 am

    #917701

    There is problem with the table 'postnet.TempLan_Details'

    Run DBCC CHECKTABLE on TempLan_Details' with REPAIR_REBUILD or REPAIR_FAST

    After this still if you are facing the problem,

    1. Drop and recreate the indexes on the table

    Take the backup of the database before doing all these things.

    Rajesh Kasturi

  • December 26, 2008 at 12:31 am

    #917702

    How 2 rebuild indexex?

    Thx..

    Thanks

  • December 26, 2008 at 12:39 am

    #917703

    use postnet

    go

    alter index all on TempLan_Details rebuild

  • December 26, 2008 at 1:55 am

    #917709

    Dear All

    Thx for suggestions...

    This database is very critical for us,Could it be possible that after reindexing it will be not responding....?

    Thx

    Thanks

  • December 26, 2008 at 3:24 am

    #917729

    Suresh B. (12/26/2008)

    use postnet

    go

    alter index all on TempLan_Details rebuild

    The below will drop and recreate the index.

    DBCC DBREINDEX (TempLan_Details , '', 70)

    Rajesh Kasturi

  • December 26, 2008 at 4:07 am

    #917736

    This database is very critical for us,Could it be possible that after reindexing it will be not responding....?

    No. Reindexing should not cause any problem.

  • December 27, 2008 at 3:23 am

    #918001

    Reindexing is not going to fix this. There's corruption in the data pages (index id 0). If it was only in the nonclustered indexes (index id 2 and higher) then a reindex would help. The only fix here is to either restore a clean backup, or run checkDB with repair (and allow it to delete some data)

    guptaajay: Do you have any idea when this corruption started? Do you have a clean (uncorrupted) backup?

    How critical is the table "TempLan_Details"? If you lost a bunch of rows from that table, would it be a disaster?

    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 28, 2008 at 7:37 am

    #918140

    I agree with Gail. That is why you should always check the database before you do a backup.



    My blog

  • December 28, 2008 at 8:35 am

    #918142

    no doubt about it, you should fix the db in sql2000 !

    btw: what service pack are you on (sql2K) ?

    Keep a copy of the backup of the corrupted database ! just in case.

    (possibly you might be able to restore it on SQL2k)

    Does this point to a table that contains text or image columns ?

    Try to export the data without these column, so you only lose the text/image stuff if these are broken.

    Johan

    Learn to play, play to learn !

    Dont drive faster than your guardian angel can fly ...
    but keeping both feet on the ground wont get you anywhere :w00t:

    - How to post Performance Problems
    - How to post data/code to get the best help[/url]

    - How to prevent a sore throat after hours of presenting ppt

    press F1 for solution, press shift+F1 for urgent solution 😀

    Need a bit of Powershell? How about this

    Who am I ? Sometimes this is me but most of the time this is me

  • December 28, 2008 at 10:27 am

    #918164

    ALZDBA (12/28/2008)

    Does this point to a table that contains text or image columns ?

    Try to export the data without these column, so you only lose the text/image stuff if these are broken.

    Unfortunately, it's not the image/text pages that are damaged. The checkDB output points to 4 pages of index 0 (the heap) that are the ones with problems. If it were the text/image pages, it would be index 255.

    The important lines of the checkdb output are the 4 below.

    Table error: Object ID 293576084, index ID 0, page (1:629). Test (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057 and -1.

    Table error: Object ID 293576084, index ID 0, page (1:632). Test (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057 and -1.

    Table error: Object ID 293576084, index ID 0, page (1:636), row 15. Test (columnOffsets->offTbl [varColumnNumber] >= priorOffset) failed. Values are 46 and 130.

    Table error: Object ID 293576084, index ID 0, page (1:642), row 22. Test (columnOffsets->offTbl [varColumnNumber] >= priorOffset) failed. Values are 46 and 122.

    From what I can tell from those errors, the options here are to restore a clean backup (if there is one) or run checkdb with the repair allow data loss option. Repair will discard the 4 pages listed above. Without more info of the table's structure, there's no way to say how many rows will be discarded by the repair.

    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

Viewing 15 posts - 1 through 15 (of 23 total)

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