molin 回复于：2002-11-21 11:18:07
Error 2540 Severity Level 16 Error Message Text Table Corrupt: Page is allocated but not linked; check the following pages and ids: allocation pg#=%ld extent id=%ld logical pg#=%ld object id on extent=%ld (object name = %S_OBJID) indid on extent=%ld Explanation This error occurs when dbcc checkalloc determines that a page is marked as allocated to an object but that page is not being used. There is no corruption or data loss associated with this error. Each 2540 error means the loss of one blank data page. A few 2540 errors are no cause for concern. However, if many of these errors occur, the amount of "lost" disk space could be significant. Note:The instructions below are for fixing 2540 errors once they have occurred. Two easy-to-use strategies exist for detecting this error sooner in the future. Refer to "Detecting Allocation Errors as Early as Possible" for information about these strategies. Action Occasionally dbcc checkalloc reports this error when no real error condition exists. You can either check to determine whether the error is real, or continue with this section and take action to correct it, whether or not it reflects a real allocation error. Because the process used to discover whether or not the error is real can be time-consuming, you may want to go directly to "Error Resolution" now. Verifying That the Error Is Real Run dbcc checkalloc in single-user mode if you suspect the 2540 error messages are incorrect. If the error is in master, use the section "How to Start SQL Server in Single-User Mode" for instructions about how to invoke SQL Server in single-user mode. Refer to "dbcc" in the SQL Server Reference Manual for information about dbcc checkalloc. Error Resolution If many of these errors are occurring, it is possible to clear them all at once by using the dbcc checkalloc and dbcc checkalloc with fix option commands. Refer to "How to Fix and Prevent Allocation Errors" for information about using dbcc checkalloc. If the text of the error message includes a real object name, not a number, then the error is on an existing object which the system catalog has correct references to, and you should continue now to "Identify Table: User or System Table". If a number appears instead of the object name, then that object only partially exists and the error must be corrected using the procedure described in "How to Fix and Prevent Allocation Errors". Identify Table: User or System Table Look at the value for "object id on extent" in the error message. If it is 100 or greater, continue with "Action for User Tables". If the "object id on extent" is below 100, it is a system table and requires a different procedure as described in the section "Action for System Tables". Action for User Tables If the "object id on extent" in the error message is 100 or greater, follow these steps to correct the error: 1.Check the value of the "indid on extent" in the error message to determine whether it is a table (value = 0) or an index (value > 0). 2.Run dbcc tablealloc or dbcc indexalloc, depending on whether the object named in the 2540 error message is a table or an index. Before you run the appropriate command, keep the following in mind: - dbcc tablealloc corrects this problem on a table or an index, but if the problem is on an index, you can avoid affecting the entire table by using dbcc indexalloc. If the table is large or heavily used, it may be more practical to use dbcc indexalloc. - These commands can correct the error only when run in the full or optimized mode, and with the nofix option not specified, the default for user tables. - You can use the object name or object ID in the following commands where the argument "object_name" appears. Use the command appropriate for your situation: For Tables (index id in extent = 0) For Indexes (0 < index id in extent < 255) 1> dbcc tablealloc (object_name) 2> go 1> dbcc indexalloc (object_name, 2> indid_on_extent) 3> go Refer to "dbcc" in the SQL Server Reference Manual and "Checking Database Consistency" in the System Administration Guide for information about dbcc tablealloc and dbcc indexalloc. Action for System Tables If the "object id on extent" in the error message is less than 100, follow these steps to correct the error: 1.Put the affected database in single-user mode: - If the database is master, use the procedure in "How to Start SQL Server in Single-User Mode", and then go to step 2. - If the database is not master, use the sp_dboption stored proce
注：本站部分文章源于互联网，版权归原作者所有！如有侵权，请原作者与本站联系，本站将立即删除！ 本站文章除特别注明外均可转载，但需注明出处！ [MinTao学以致用网] 
