I set up a test database to try and understand table partitioning. Since deleting the partition schemas, functions and all relevant info on the database properties page, I am getting the following errors during the weekly database integrity check:
Msg 8914, Level 16, State 1, Line 1
Incorrect PFS free space information for page (1:223) in object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). Expected value 0_PCT_FULL, actual value 100_PCT_FULL.
Can anyone suggest why this might be happening?
Thanks
Looks like database file corruption.
Try DBCC CHECKDB ( ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/tsqlref9/html/2c506167-0b69-49f7-9282-241e411910df.htm )
|||Thanks
I ran this with the
REPAIR_ALLOW_DATA_LOSS option and it sorted the problems. Not something I would like to do on a live database though.
Thanks for your help
Susan
|||I have the same error, already for the second times now, on a new installed SQL2005 sever running on a Win2003 X64 system.
2 times on a different Db. The Db was only created for a few days and already problems with the CheckDB.
I was lucky that the Db wasn't in use yet so I could solve it with the REPAIR_ALLOW_DATA_LOSS option.
I find this very disturbing because we are running SQL 7.0 and SQL 2000 now for more than 5 years and I never had to use this option on a DB and now it's already the second time that I see it on a fresh created, not used yet, database.
Did anyone has the same experience or is this a unique case?
Greetings,
Ludo
|||I'm getting the following message
Microsoft(R) Server Maintenance Utility (Unicode) Version 9.0.1399
Report was generated on "VUELOSDATA".
Maintenance Plan: MaintenancePlan
Duration: 00:02:02
Status: Warning: One or more tasks failed..
Details:
Check Database Integrity (VUELOSDATA)
Check Database integrity on Target server connection
Databases: All user databases
Include indexes
Task start: 3/26/2007 3:00 AM.
Task end: 3/26/2007 3:02 AM.
Failed-1073548784) Executing the query "DBCC CHECKDB WITH NO_INFOMSGS
" failed with the following error: "Incorrect PFS free space information for page (1:70) in object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). Expected value 0_PCT_FULL, actual value 100_PCT_FULL.
Incorrect PFS free space information for page (1:71) in object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). Expected value 0_PCT_FULL, actual value 100_PCT_FULL.
Incorrect PFS free space information for page (1:7394) in object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). Expected value 0_PCT_FULL, actual value 100_PCT_FULL.
CHECKDB found 0 allocation errors and 3 consistency errors in table 'sys.sysobjvalues' (object ID 60).
CHECKDB found 0 allocation errors and 3 consistency errors in database 'CFGlobal'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (CFGlobal).". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
How serious is this error?, and how do I repair the database?
www.freebiesms.co.uk
No comments:
Post a Comment