March 27, 2003 at 1:45 pm
I am trying to re-index a table and get this back. Need help where to change the size of tackle this... Thanks
SQL 7.0 - NT server
Results:
Server: Msg 1540, Level 16, State 1, Line 1
Cannot sort a row of size 8192, which is greater than the allowable maximum of 8094.
Index (ID = 1) is being rebuilt.
March 27, 2003 at 2:32 pm
strange...run DBCC CheckTable on that table and tell us if it shows any errors.
March 27, 2003 at 3:10 pm
This is what I got...
**I have a strange feeling **
Any recommendations?
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 230448045, index ID 0: Page (1:100706) could not be processed. See other errors for details.
Server: Msg 8944, Level 16, State 1, Line 1
Table Corrupt: Object ID 230448045, index ID 0, page (1:100706), row 2. Test (hdr->r_offsetNull >= BASEOFFSET) failed. Values are 1 and 4.
DBCC results for 'ShopOrderAllocations'.
There are 28048 rows in 1222 pages for object 'ShopOrderAllocations'.
CHECKTABLE found 0 allocation errors and 2 consistency errors in table 'ShopOrderAllocations' (object ID 230448045).
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKTABLE (stl_prod25.dbo.ShopOrderAllocations ).
March 27, 2003 at 3:10 pm
This is what I got...
**I have a strange feeling **
Any recommendations?
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 230448045, index ID 0: Page (1:100706) could not be processed. See other errors for details.
Server: Msg 8944, Level 16, State 1, Line 1
Table Corrupt: Object ID 230448045, index ID 0, page (1:100706), row 2. Test (hdr->r_offsetNull >= BASEOFFSET) failed. Values are 1 and 4.
DBCC results for 'ShopOrderAllocations'.
There are 28048 rows in 1222 pages for object 'ShopOrderAllocations'.
CHECKTABLE found 0 allocation errors and 2 consistency errors in table 'ShopOrderAllocations' (object ID 230448045).
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKTABLE (stl_prod25.dbo.ShopOrderAllocations ).
March 27, 2003 at 4:46 pm
Just so you know...
I got this thing fixed. By running the CheckTable's option rapair_allow_data_loss.
Thanks
Oscar
April 1, 2003 at 9:27 am
Be carefule with the "DBCC... Repair Allow Data Loss." It can cause a loss of data in your table. In some cases (many?) you will need to restore from the last good backup to fully recover the data in your table. If your repair run got a message like "Repair: Page (xx:xxxxxxx) has been deallocated from object ID 9999999999, index ID 0" that is a good sign that the repair run dropped part of the table.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply