 Sybase Tips & Tricks by Rob Verschoor | |||
|
|
|
|||||||||||||||||||||||
|
If you're running dbcc checkstorage on your databases (you are doing that, don't you?), database faults may be reported. The question is always what to do next when a fault is found -- typically, you'd start searching through the ASE Troubleshooting Guide to find the prescribed follow-up action. In ASE 12.5.0.3, this part of the documentation was moved into ASE by means of the stored procedure sp_dbcc_help_fault which resides in dbccdb. When called with a fault number (e.g. sp_dbcc_help_fault 100001, this procedure conveniently displays a description of that particular fault along with the recommended actions to fix it. When called without a parameter, it displays this information for all faults. Although sp_dbcc_help_fault was introduced in 12.5.0.3, most of this information is equally valid in pre-12.5.0.3. For the benefit of ASE DBAs who are running pre-12.5.0.3, the output of sp_dbcc_help_fault is included below. Some additional suggestions, submitted by readers are included as well -- thanks to Jeffrey Frankus). Click on a fault number: 100000 - 100001 - 100002 - 100003 - 100004 - 100005 - 100006 - 100007 - 100008 - 100009 - 100010 - 100011 - 100012 - 100013 - 100014 - 100015 - 100016 - 100017 - 100018 - 100019 - 100020 - 100021 - 100022 - 100023 - 100024 - 100025 - 100026 - 100027 - 100028 - 100029 - 100030 - 100031 - 100032 - 100033 - 100034 - 100035 - 100036 - 100037 - 100038 ASE 15.0: 100039 - 100040 ASE 15.0.3 ESD#1: 100041 Fault 100000 Description of the fault corresponding to checkstorage type_code 100000: - IO error attempting to access this page. Suggested corrective actions for the fault corresponding to checkstorage type_code 100000, listed in recommended order: - Check your operating system logs and correct all reported hardware problems on disks containing a Sybase device. - Reload the database from a clean backup. Contact Sybase Technical Support if the recommended corrective action does not resolve the faults. Fault 100001 Description of the fault corresponding to checkstorage type_code 100001: - The page id, next page, or previous page value in the page header is invalid. Recommended corrective action for the fault corresponding to checkstorage type_code 100001: - Reload the database from a clean backup. Contact Sybase Technical Support if the recommended corrective action does not resolve the faults. Fault 100002 Description of the fault corresponding to checkstorage type_code 100002: - The page free offset value in the page header is invalid. Suggested corrective actions for the fault corresponding to checkstorage type_code 100002, listed in recommended order: - Drop the table or index and recreate it. - Reload the database from a clean backup. Contact Sybase Technical Support if the recommended corrective action does not resolve the faults. Fault 100003 Description of the fault corresponding to checkstorage type_code 100003: - The object/index id in the page header is invalid. Suggested corrective actions for the fault corresponding to checkstorage type_code 100003, listed in recommended order: - Run dbcc tablealloc with the 'fix' option. - Run dbcc checktable. - Run dbcc checkalloc with the 'fix' option. Contact Sybase Technical Support if the recommended corrective action does not resolve the faults. Fault 100004 Description of the fault corresponding to checkstorage type_code 100004: - The timestamp value in the page header is invalid. Suggested corrective actions for the fault corresponding to checkstorage type_code 100004, listed in recommended order: - in 15.0.3 ESD#3 (or later) and 15.5 ESD#1 (or later), run fix_page( dbid|dbname, objid|objname, page_no, timestamp) (make sure the objectname or id is correct for the specified page number!) - Drop the table or index and recreate it. - Reload the database from a clean backup. Contact Sybase Technical Support if the recommended corrective action does not resolve the faults. Fault 100005 Description of the fault corresponding to checkstorage type_code 100005: - Allocation page is assigned to another database. Recommended corrective action for the fault corresponding to checkstorage type_code 100005: - Reload the database from a clean backup. Contact Sybase Technical Support if the recommended corrective action does not resolve the faults. Fault 100006 Description of the fault corresponding to checkstorage type_code 100006: - The object/index id does not match the id in its allocation extent. Recommended corrective action for the fault corresponding to checkstorage type_code 100006: - Run dbcc tablealloc with the 'fix' option. Contact Sybase Technical Support if the recommended corrective action does not resolve the faults. Fault 100007 Description of the fault corresponding to checkstorage type_code 100007: - Extent allocated to an unknown object/index. Recommended corrective action for the fault corresponding to checkstorage type_code 100007: - Run dbcc checkalloc with the 'fix' option. Contact Sybase Technical Support if the recommended corrective action does not resolve the faults. Fault 100008 Description of the fault corresponding to checkstorage type_code 100008: - Row format is inconsistent with page header. Recommended corrective action for the fault corresponding to checkstorage type_code 100008: - Run dbcc checktable. Contact Sybase Technical Support if the recommended corrective action does not resolve the faults. Fault 100009 Description of the fault corresponding to checkstorage type_code 100009: - Either the attribute offset table, or the adjust table, is inconsistent. Recommended corrective action for the fault corresponding to checkstorage type_code 100009: - Run dbcc checktable. Contact Sybase Technical Support if the recommended corrective action does not resolve the faults. Fault 100010 Description of the fault corresponding to checkstorage type_code 100010: - The row offset table is inconsistent. Recommended corrective action for the fault corresponding to checkstorage type_code 100010: - Run dbcc checktable. Contact Sybase Technical Support if the recommended corrective action does not resolve the faults. Fault 100011 Description of the fault corresponding to checkstorage type_code 100011: - Text column includes an invalid page reference. Suggested corrective actions for the fault corresponding to checkstorage type_code 100011, listed in recommended order: - Drop the table or index and recreate it. - Reload the database from a clean backup. Contact Sybase Technical Support if the recommended corrective action does not resolve the faults. Fault 100012 Description of the fault corresponding to checkstorage type_code 100012: - A page of wrong object type or format is linked to the chain. Suggested corrective actions for the fault corresponding to checkstorage type_code 100012, listed in recommended order: - Drop the table or index and recreate it. - Reload the database from a clean backup. Contact Sybase Technical Support if the recommended corrective action does not resolve the faults. Fault 100013 Description of the fault corresponding to checkstorage type_code 100013: - Non-OAM page is linked to the OAM chain. Suggested corrective actions for the fault corresponding to checkstorage type_code 100013, listed in recommended order: - Drop the table or index and recreate it. - Reload the database from a clean backup. Contact Sybase Technical Support if the recommended corrective action does not resolve the faults. Fault 100014 Description of the fault corresponding to checkstorage type_code 100014: - Page linked to more than one chain. Recommended corrective action for the fault corresponding to checkstorage type_code 100014: - Reload the database from a clean backup. Contact Sybase Technical Support if the recommended corrective action does not resolve the faults. Fault 100015 Description of the fault corresponding to checkstorage type_code 100015: - Page chain contains a loop. Suggested corrective actions for the fault corresponding to checkstorage type_code 100015, listed in recommended order: - Drop the table or index and recreate it. - Reload the database from a clean backup. Contact Sybase Technical Support if the recommended corrective action does not resolve the faults. Fault 100016 Description of the fault corresponding to checkstorage type_code 100016: - Page allocated but not linked to the chain. Recommended corrective action for the fault corresponding to checkstorage type_code 100016: - Run dbcc checktable. Contact Sybase Technical Support if the recommended corrective action does not resolve the faults. Fault 100017 Description of the fault corresponding to checkstorage type_code 100017: - OAM ring chain is malformed. Recommended corrective action for the fault corresponding to checkstorage type_code 100017: - Reload the database from a clean backup. Contact Sybase Technical Support if the recommended corrective action does not resolve the faults. Fault 100018 Description of the fault corresponding to checkstorage type_code 100018: - OAM entry is missing for this allocation page. Suggested corrective actions for the fault corresponding to checkstorage type_code 100018, listed in recommended order: - Run dbcc indexalloc with the 'fix' option. - Run dbcc tablealloc with the 'fix' option. - Run dbcc checkalloc with the 'fix' option. Contact Sybase Technical Support if the recommended corrective action does not resolve the faults. Fault 100019 Description of the fault corresponding to checkstorage type_code 100019: - OAM entry is present but there is no allocation. Suggested corrective actions for the fault corresponding to checkstorage type_code 100019, listed in recommended order: - Run dbcc tablealloc with the 'fix' option. - Run dbcc checkalloc with the 'fix' option. Contact Sybase Technical Support if the recommended corrective action does not resolve the faults. Fault 100020 Description of the fault corresponding to checkstorage type_code 100020: - Check aborted because the chain could not be followed. Recommended corrective action for the fault corresponding to checkstorage type_code 100020: - Rerun checkstorage. Contact Sybase Technical Support if the recommended corrective action does not resolve the faults. Fault 100021 Description of the fault corresponding to checkstorage type_code 100021: - Chain does not end on the expected page. Recommended corrective action for the fault corresponding to checkstorage type_code 100021: - Run dbcc checktable. Contact Sybase Technical Support if the recommended corrective action does not resolve the faults. Fault 100022 Description of the fault corresponding to checkstorage type_code 100022: - Chain start reference disagrees with page linkage. Recommended corrective action for the fault corresponding to checkstorage type_code 100022: - Run dbcc checktable. Contact Sybase Technical Support if the recommended corrective action does not resolve the faults. Fault 100023 Description of the fault corresponding to checkstorage type_code 100023: - OAM used pages count discrepancy exceeds threshold. Suggested corrective actions for the fault corresponding to checkstorage type_code 100023, listed in recommended order: - Run dbcc indexalloc with the 'fix' option. - Run dbcc tablealloc with the 'fix' option. - Run dbcc checkalloc with the 'fix' option. Contact Sybase Technical Support if the recommended corrective action does not resolve the faults. Fault 100024 Description of the fault corresponding to checkstorage type_code 100024: - OAM unused pages count discrepancy exceeds threshold. Suggested corrective actions for the fault corresponding to checkstorage type_code 100024, listed in recommended order: - Run dbcc indexalloc with the 'fix' option. - Run dbcc tablealloc with the 'fix' option. - Run dbcc checkalloc with the 'fix' option. Contact Sybase Technical Support if the recommended corrective action does not resolve the faults. Fault 100025 Description of the fault corresponding to checkstorage type_code 100025: - OAM row count discrepancy exceeds threshold. Recommended corrective action for the fault corresponding to checkstorage type_code 100025: - Run dbcc checktable. Contact Sybase Technical Support if the recommended corrective action does not resolve the faults. Fault 100026 Description of the fault corresponding to checkstorage type_code 100026: - Violation of the SERIALLOC rules on allocation page. Recommended corrective action for the fault corresponding to checkstorage type_code 100026: - Run dbcc checkalloc with the 'fix' option. Contact Sybase Technical Support if the recommended corrective action does not resolve the faults. Fault 100027 Description of the fault corresponding to checkstorage type_code 100027: - First and root page of a text index must be the same. Suggested corrective actions for the fault corresponding to checkstorage type_code 100027, listed in recommended order: - Drop the table or index and recreate it. - Reload the database from a clean backup. Contact Sybase Technical Support if the recommended corrective action does not resolve the faults. Fault 100028 Description of the fault corresponding to checkstorage type_code 100028: - The page is not located in the objects's reserved region. Recommended corrective action for the fault corresponding to checkstorage type_code 100028: - Bulk copy the data out, drop the object and recreate it, bulk copy the data back in. Contact Sybase Technical Support if the recommended corrective action does not resolve the faults. Fault 100029 Description of the fault corresponding to checkstorage type_code 100029: - Inconsistent status flags or values out of range. Suggested corrective actions for the fault corresponding to checkstorage type_code 100029, listed in recommended order: - Run dbcc checktable. - Bulk copy the data out and back in. Contact Sybase Technical Support if the recommended corrective action does not resolve the faults. Fault 100030 Description of the fault corresponding to checkstorage type_code 100030: - Page format errors on OAM or text pages. Suggested corrective actions for the fault corresponding to checkstorage type_code 100030, listed in recommended order: - Drop the table or index and recreate it (NB: when the index ID for this page is 255, this indicates a text/image page chain. You can run dbcc rebuild_text(tablename) to rebuild the text/image data). - Reload the database from a clean backup. Contact Sybase Technical Support if the recommended corrective action does not resolve the faults. Fault 100031 Description of the fault corresponding to checkstorage type_code 100031: - Page reached by the chain is not allocated. Suggested corrective actions for the fault corresponding to checkstorage type_code 100031, listed in recommended order: - Run dbcc tablealloc with the 'fix' option. - Run dbcc checkalloc with the 'fix' option. Contact Sybase Technical Support if the recommended corrective action does not resolve the faults. Fault 100032 Description of the fault corresponding to checkstorage type_code 100032: - Invalid or inconsistent page chain linkages. Suggested corrective actions for the fault corresponding to checkstorage type_code 100032, listed in recommended order: - Drop the table or index and recreate it. - Reload the database from a clean backup. Contact Sybase Technical Support if the recommended corrective action does not resolve the faults. Fault 100033 Description of the fault corresponding to checkstorage type_code 100033: - Invalid or inconsistent value for the non-contiguous free space on the page. Recommended corrective action for the fault corresponding to checkstorage type_code 100033: - Run the reorg command. Contact Sybase Technical Support if the recommended corrective action does not resolve the faults. Fault 100034 Description of the fault corresponding to checkstorage type_code 100034: - Invalid or inconsistent value for the contiguous free space on the page. Recommended corrective action for the fault corresponding to checkstorage type_code 100034: - Run the reorg command. Contact Sybase Technical Support if the recommended corrective action does not resolve the faults. Fault 100035 Description of the fault corresponding to checkstorage type_code 100035: - Inconsistency in the page fullness indicator. Recommended corrective action for the fault corresponding to checkstorage type_code 100035: - Run dbcc checktable with the 'fix_spacebits' option. Contact Sybase Technical Support if the recommended corrective action does not resolve the faults. Fault 100036 Description of the fault corresponding to checkstorage type_code 100036: - Invalid or inconsistent value for the deleted row count on the page. Recommended corrective action for the fault corresponding to checkstorage type_code 100036: - Run the reorg command. Contact Sybase Technical Support if the recommended corrective action does not resolve the faults. Fault 100037 Description of the fault corresponding to checkstorage type_code 100037: - Inconsistency between the forwarded rows indicator and the number of forwarded rows on the page. Recommended corrective action for the fault corresponding to checkstorage type_code 100037: - Run the reorg command. Contact Sybase Technical Support if the recommended corrective action does not resolve the faults. Fault 100038 Description of the fault corresponding to checkstorage type_code 100038: - Page header format indicator is set incorrectly. Suggested corrective actions for the fault corresponding to checkstorage type_code 100038, listed in recommended order: - Drop the table or index and recreate it. - Reload the database from a clean backup. Contact Sybase Technical Support if the recommended corrective action does not resolve the faults. Fault 100039 (ASE 15.0) Description of the fault corresponding to checkstorage type_code 100039: - Extent OAM page reference is set incorrectly. Recommended corrective action for the fault corresponding to checkstorage type_code 100039: - Run any of dbcc textalloc/indexalloc/tablealloc as appropriate in 'optimized' mode and with the 'fix' option. - For system tables, run: sp_fixindex db-name, table-name Contact Sybase Technical Support if the recommended corrective action does not resolve the faults. Fault 100040 (ASE 15.0) Description of the fault corresponding to checkstorage type_code 100040: - Non-first OAM page has non zero first OAM page specific data. Recommended corrective action for the fault corresponding to checkstorage type_code 100040: - This fault is harmless, no action is required.. Contact Sybase Technical Support if the recommended corrective action does not resolve the faults. Fault 100041 (ASE 15.0.3 ESD#1) Description of the fault corresponding to checkstorage type_code 100041: - Current syslogs free space does not match what dbcc counted. Recommended corrective action for the fault corresponding to checkstorage type_code 100041: - Run dbcc tablealloc with the 'fix' option. Contact Sybase Technical Support if the recommended corrective action does not resolve the faults. |
|||||||||||||||||||||||
|