|
sql
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
SQL Server 2005 Maintenance Plan ErrorIntegrity task set to: Target server connection, All user databases, Include Indexes. It claims to run OK but then viewing the history shows it has failed with the error "Alter failed for Server 'XYZDB02'" Is this just a crappy error message or is there more meaning to it? Running the plan manually gives the following and I understand that it is back up time followed by a checkdb recover, but I don't understand the message in the history viewer. The T-SQL generated for the plan is USE [ReportServer] GO DBCC CHECKDB WITH NO_INFOMSGS GO USE [ReportServerTempDB] GO DBCC CHECKDB WITH NO_INFOMSGS GO USE [navisioncz] GO DBCC CHECKDB WITH NO_INFOMSGS GO USE [comlinks] GO DBCC CHECKDB WITH NO_INFOMSGS And it reports: Msg 8914, Level 16, State 1, Line 1 Incorrect PFS free space information for page (1:487) 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. Msg 8914, Level 16, State 1, Line 1 Incorrect PFS free space information for page (1:504) 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 2 consistency errors in table 'sys.sysobjvalues' (object ID 60). Msg 8914, Level 16, State 1, Line 1 Incorrect PFS free space information for page (3:42) in object ID 373576369, index ID 1, partition ID 72057594038452224, alloc unit ID 72057594044547072 (type LOB data). Expected value 0_PCT_FULL, actual value 100_PCT_FULL. Msg 8914, Level 16, State 1, Line 1 Incorrect PFS free space information for page (3:44) in object ID 373576369, index ID 1, partition ID 72057594038452224, alloc unit ID 72057594044547072 (type LOB data). Expected value 0_PCT_FULL, actual value 100_PCT_FULL. CHECKDB found 0 allocation errors and 2 consistency errors in table 'Object' (object ID 373576369). CHECKDB found 0 allocation errors and 4 consistency errors in database 'navisioncz'. repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (navisioncz). How about updating your database statistics?
-- Show quoteEkrem Önsoy "NigelA" <discussion@microsoft.newsgroups> wrote in message news:eaJ9lJeMIHA.1208@TK2MSFTNGP03.phx.gbl... >I have tried to run a maintenance plan which is just a Check Database >Integrity task set to: Target server connection, All user databases, >Include Indexes. It claims to run OK but then viewing the history shows it >has failed with the error "Alter failed for Server 'XYZDB02'" > > Is this just a crappy error message or is there more meaning to it? > > Running the plan manually gives the following and I understand that it is > back up time followed by a checkdb recover, but I don't understand the > message in the history viewer. > > The T-SQL generated for the plan is > USE [ReportServer] > > GO > > DBCC CHECKDB WITH NO_INFOMSGS > > GO > > USE [ReportServerTempDB] > > GO > > DBCC CHECKDB WITH NO_INFOMSGS > > GO > > USE [navisioncz] > > GO > > DBCC CHECKDB WITH NO_INFOMSGS > > GO > > USE [comlinks] > > GO > > DBCC CHECKDB WITH NO_INFOMSGS > > > > And it reports: > > Msg 8914, Level 16, State 1, Line 1 > > Incorrect PFS free space information for page (1:487) 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. > > Msg 8914, Level 16, State 1, Line 1 > > Incorrect PFS free space information for page (1:504) 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 2 consistency errors in table > 'sys.sysobjvalues' (object ID 60). > > Msg 8914, Level 16, State 1, Line 1 > > Incorrect PFS free space information for page (3:42) in object ID > 373576369, index ID 1, partition ID 72057594038452224, alloc unit ID > 72057594044547072 (type LOB data). Expected value 0_PCT_FULL, actual > value 100_PCT_FULL. > > Msg 8914, Level 16, State 1, Line 1 > > Incorrect PFS free space information for page (3:44) in object ID > 373576369, index ID 1, partition ID 72057594038452224, alloc unit ID > 72057594044547072 (type LOB data). Expected value 0_PCT_FULL, actual > value 100_PCT_FULL. > > CHECKDB found 0 allocation errors and 2 consistency errors in table > 'Object' (object ID 373576369). > > CHECKDB found 0 allocation errors and 4 consistency errors in database > 'navisioncz'. > > repair_allow_data_loss is the minimum repair level for the errors found by > DBCC CHECKDB (navisioncz). > > > > > > Thanks but why would that help with a message like 'Alter failed for
Server...' Nigel Ainscoe Show quote "Ekrem Önsoy" <ek***@btegitim.com> wrote in message news:B579B3AC-FE5A-4303-85A6-5BE05384BCD5@microsoft.com... > How about updating your database statistics? > > -- > Ekrem Önsoy > > > > "NigelA" <discussion@microsoft.newsgroups> wrote in message > news:eaJ9lJeMIHA.1208@TK2MSFTNGP03.phx.gbl... >>I have tried to run a maintenance plan which is just a Check Database >>Integrity task set to: Target server connection, All user databases, >>Include Indexes. It claims to run OK but then viewing the history shows it >>has failed with the error "Alter failed for Server 'XYZDB02'" >> >> Is this just a crappy error message or is there more meaning to it? >> >> Running the plan manually gives the following and I understand that it is >> back up time followed by a checkdb recover, but I don't understand the >> message in the history viewer. >> >> The T-SQL generated for the plan is >> USE [ReportServer] >> >> GO >> >> DBCC CHECKDB WITH NO_INFOMSGS >> >> GO >> >> USE [ReportServerTempDB] >> >> GO >> >> DBCC CHECKDB WITH NO_INFOMSGS >> >> GO >> >> USE [navisioncz] >> >> GO >> >> DBCC CHECKDB WITH NO_INFOMSGS >> >> GO >> >> USE [comlinks] >> >> GO >> >> DBCC CHECKDB WITH NO_INFOMSGS >> >> >> >> And it reports: >> >> Msg 8914, Level 16, State 1, Line 1 >> >> Incorrect PFS free space information for page (1:487) 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. >> >> Msg 8914, Level 16, State 1, Line 1 >> >> Incorrect PFS free space information for page (1:504) 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 2 consistency errors in table >> 'sys.sysobjvalues' (object ID 60). >> >> Msg 8914, Level 16, State 1, Line 1 >> >> Incorrect PFS free space information for page (3:42) in object ID >> 373576369, index ID 1, partition ID 72057594038452224, alloc unit ID >> 72057594044547072 (type LOB data). Expected value 0_PCT_FULL, actual >> value 100_PCT_FULL. >> >> Msg 8914, Level 16, State 1, Line 1 >> >> Incorrect PFS free space information for page (3:44) in object ID >> 373576369, index ID 1, partition ID 72057594038452224, alloc unit ID >> 72057594044547072 (type LOB data). Expected value 0_PCT_FULL, actual >> value 100_PCT_FULL. >> >> CHECKDB found 0 allocation errors and 2 consistency errors in table >> 'Object' (object ID 373576369). >> >> CHECKDB found 0 allocation errors and 4 consistency errors in database >> 'navisioncz'. >> >> repair_allow_data_loss is the minimum repair level for the errors found >> by DBCC CHECKDB (navisioncz). >> >> >> >> >> >> > I thought this message "Incorrect PFS free space information for page ..."
could be related to statistics. -- Show quoteEkrem Önsoy "NigelA" <discussion@microsoft.newsgroups> wrote in message news:uSuByheMIHA.5360@TK2MSFTNGP03.phx.gbl... > Thanks but why would that help with a message like 'Alter failed for > Server...' > > Nigel Ainscoe > > > "Ekrem Önsoy" <ek***@btegitim.com> wrote in message > news:B579B3AC-FE5A-4303-85A6-5BE05384BCD5@microsoft.com... >> How about updating your database statistics? >> >> -- >> Ekrem Önsoy >> >> >> >> "NigelA" <discussion@microsoft.newsgroups> wrote in message >> news:eaJ9lJeMIHA.1208@TK2MSFTNGP03.phx.gbl... >>>I have tried to run a maintenance plan which is just a Check Database >>>Integrity task set to: Target server connection, All user databases, >>>Include Indexes. It claims to run OK but then viewing the history shows >>>it has failed with the error "Alter failed for Server 'XYZDB02'" >>> >>> Is this just a crappy error message or is there more meaning to it? >>> >>> Running the plan manually gives the following and I understand that it >>> is back up time followed by a checkdb recover, but I don't understand >>> the message in the history viewer. >>> >>> The T-SQL generated for the plan is >>> USE [ReportServer] >>> >>> GO >>> >>> DBCC CHECKDB WITH NO_INFOMSGS >>> >>> GO >>> >>> USE [ReportServerTempDB] >>> >>> GO >>> >>> DBCC CHECKDB WITH NO_INFOMSGS >>> >>> GO >>> >>> USE [navisioncz] >>> >>> GO >>> >>> DBCC CHECKDB WITH NO_INFOMSGS >>> >>> GO >>> >>> USE [comlinks] >>> >>> GO >>> >>> DBCC CHECKDB WITH NO_INFOMSGS >>> >>> >>> >>> And it reports: >>> >>> Msg 8914, Level 16, State 1, Line 1 >>> >>> Incorrect PFS free space information for page (1:487) 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. >>> >>> Msg 8914, Level 16, State 1, Line 1 >>> >>> Incorrect PFS free space information for page (1:504) 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 2 consistency errors in table >>> 'sys.sysobjvalues' (object ID 60). >>> >>> Msg 8914, Level 16, State 1, Line 1 >>> >>> Incorrect PFS free space information for page (3:42) in object ID >>> 373576369, index ID 1, partition ID 72057594038452224, alloc unit ID >>> 72057594044547072 (type LOB data). Expected value 0_PCT_FULL, actual >>> value 100_PCT_FULL. >>> >>> Msg 8914, Level 16, State 1, Line 1 >>> >>> Incorrect PFS free space information for page (3:44) in object ID >>> 373576369, index ID 1, partition ID 72057594038452224, alloc unit ID >>> 72057594044547072 (type LOB data). Expected value 0_PCT_FULL, actual >>> value 100_PCT_FULL. >>> >>> CHECKDB found 0 allocation errors and 2 consistency errors in table >>> 'Object' (object ID 373576369). >>> >>> CHECKDB found 0 allocation errors and 4 consistency errors in database >>> 'navisioncz'. >>> >>> repair_allow_data_loss is the minimum repair level for the errors found >>> by DBCC CHECKDB (navisioncz). >>> >>> >>> >>> >>> >>> >> > > Also one of the messages:
CHECKDB found 0 allocation errors and 2 consistency errors in table > 'Object' (object ID 373576369). Is very cryptic - how can I discover what this object is? If I have to run a repair_allow_data_loss I would like to know what is at risk :-( TIA Nigel Ainscoe Show quote "NigelA" <discussion@microsoft.newsgroups> wrote in message news:eaJ9lJeMIHA.1208@TK2MSFTNGP03.phx.gbl... >I have tried to run a maintenance plan which is just a Check Database >Integrity task set to: Target server connection, All user databases, >Include Indexes. It claims to run OK but then viewing the history shows it >has failed with the error "Alter failed for Server 'XYZDB02'" > > Is this just a crappy error message or is there more meaning to it? > > Running the plan manually gives the following and I understand that it is > back up time followed by a checkdb recover, but I don't understand the > message in the history viewer. > > The T-SQL generated for the plan is > USE [ReportServer] > > GO > > DBCC CHECKDB WITH NO_INFOMSGS > > GO > > USE [ReportServerTempDB] > > GO > > DBCC CHECKDB WITH NO_INFOMSGS > > GO > > USE [navisioncz] > > GO > > DBCC CHECKDB WITH NO_INFOMSGS > > GO > > USE [comlinks] > > GO > > DBCC CHECKDB WITH NO_INFOMSGS > > > > And it reports: > > Msg 8914, Level 16, State 1, Line 1 > > Incorrect PFS free space information for page (1:487) 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. > > Msg 8914, Level 16, State 1, Line 1 > > Incorrect PFS free space information for page (1:504) 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 2 consistency errors in table > 'sys.sysobjvalues' (object ID 60). > > Msg 8914, Level 16, State 1, Line 1 > > Incorrect PFS free space information for page (3:42) in object ID > 373576369, index ID 1, partition ID 72057594038452224, alloc unit ID > 72057594044547072 (type LOB data). Expected value 0_PCT_FULL, actual > value 100_PCT_FULL. > > Msg 8914, Level 16, State 1, Line 1 > > Incorrect PFS free space information for page (3:44) in object ID > 373576369, index ID 1, partition ID 72057594038452224, alloc unit ID > 72057594044547072 (type LOB data). Expected value 0_PCT_FULL, actual > value 100_PCT_FULL. > > CHECKDB found 0 allocation errors and 2 consistency errors in table > 'Object' (object ID 373576369). > > CHECKDB found 0 allocation errors and 4 consistency errors in database > 'navisioncz'. > > repair_allow_data_loss is the minimum repair level for the errors found by > DBCC CHECKDB (navisioncz). > > > > > > Run this in the db in question:
SELECT OBJECT_NAME(373576369) -- Show quoteAndrew J. Kelly SQL MVP Solid Quality Mentors "NigelA" <discussion@microsoft.newsgroups> wrote in message news:upio7meMIHA.4752@TK2MSFTNGP05.phx.gbl... > Also one of the messages: > > CHECKDB found 0 allocation errors and 2 consistency errors in table >> 'Object' (object ID 373576369). > > Is very cryptic - how can I discover what this object is? If I have to run > a repair_allow_data_loss I would like to know what is at risk :-( > > TIA > Nigel Ainscoe > > > "NigelA" <discussion@microsoft.newsgroups> wrote in message > news:eaJ9lJeMIHA.1208@TK2MSFTNGP03.phx.gbl... >>I have tried to run a maintenance plan which is just a Check Database >>Integrity task set to: Target server connection, All user databases, >>Include Indexes. It claims to run OK but then viewing the history shows it >>has failed with the error "Alter failed for Server 'XYZDB02'" >> >> Is this just a crappy error message or is there more meaning to it? >> >> Running the plan manually gives the following and I understand that it is >> back up time followed by a checkdb recover, but I don't understand the >> message in the history viewer. >> >> The T-SQL generated for the plan is >> USE [ReportServer] >> >> GO >> >> DBCC CHECKDB WITH NO_INFOMSGS >> >> GO >> >> USE [ReportServerTempDB] >> >> GO >> >> DBCC CHECKDB WITH NO_INFOMSGS >> >> GO >> >> USE [navisioncz] >> >> GO >> >> DBCC CHECKDB WITH NO_INFOMSGS >> >> GO >> >> USE [comlinks] >> >> GO >> >> DBCC CHECKDB WITH NO_INFOMSGS >> >> >> >> And it reports: >> >> Msg 8914, Level 16, State 1, Line 1 >> >> Incorrect PFS free space information for page (1:487) 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. >> >> Msg 8914, Level 16, State 1, Line 1 >> >> Incorrect PFS free space information for page (1:504) 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 2 consistency errors in table >> 'sys.sysobjvalues' (object ID 60). >> >> Msg 8914, Level 16, State 1, Line 1 >> >> Incorrect PFS free space information for page (3:42) in object ID >> 373576369, index ID 1, partition ID 72057594038452224, alloc unit ID >> 72057594044547072 (type LOB data). Expected value 0_PCT_FULL, actual >> value 100_PCT_FULL. >> >> Msg 8914, Level 16, State 1, Line 1 >> >> Incorrect PFS free space information for page (3:44) in object ID >> 373576369, index ID 1, partition ID 72057594038452224, alloc unit ID >> 72057594044547072 (type LOB data). Expected value 0_PCT_FULL, actual >> value 100_PCT_FULL. >> >> CHECKDB found 0 allocation errors and 2 consistency errors in table >> 'Object' (object ID 373576369). >> >> CHECKDB found 0 allocation errors and 4 consistency errors in database >> 'navisioncz'. >> >> repair_allow_data_loss is the minimum repair level for the errors found >> by DBCC CHECKDB (navisioncz). >> >> >> >> >> >> > > Brilliant Andrew.
Except it returns 'Object'. More research required me thinks. Nigel Ainscoe Show quote "Andrew J. Kelly" <sqlmvpnooospam@shadhawk.com> wrote in message news:uHZvG6eMIHA.6100@TK2MSFTNGP03.phx.gbl... > Run this in the db in question: > > SELECT OBJECT_NAME(373576369) > > -- > Andrew J. Kelly SQL MVP > Solid Quality Mentors > > > "NigelA" <discussion@microsoft.newsgroups> wrote in message > news:upio7meMIHA.4752@TK2MSFTNGP05.phx.gbl... >> Also one of the messages: >> >> CHECKDB found 0 allocation errors and 2 consistency errors in table >>> 'Object' (object ID 373576369). >> >> Is very cryptic - how can I discover what this object is? If I have to >> run a repair_allow_data_loss I would like to know what is at risk :-( >> >> TIA >> Nigel Ainscoe >> >> >> "NigelA" <discussion@microsoft.newsgroups> wrote in message >> news:eaJ9lJeMIHA.1208@TK2MSFTNGP03.phx.gbl... >>>I have tried to run a maintenance plan which is just a Check Database >>>Integrity task set to: Target server connection, All user databases, >>>Include Indexes. It claims to run OK but then viewing the history shows >>>it has failed with the error "Alter failed for Server 'XYZDB02'" >>> >>> Is this just a crappy error message or is there more meaning to it? >>> >>> Running the plan manually gives the following and I understand that it >>> is back up time followed by a checkdb recover, but I don't understand >>> the message in the history viewer. >>> >>> The T-SQL generated for the plan is >>> USE [ReportServer] >>> >>> GO >>> >>> DBCC CHECKDB WITH NO_INFOMSGS >>> >>> GO >>> >>> USE [ReportServerTempDB] >>> >>> GO >>> >>> DBCC CHECKDB WITH NO_INFOMSGS >>> >>> GO >>> >>> USE [navisioncz] >>> >>> GO >>> >>> DBCC CHECKDB WITH NO_INFOMSGS >>> >>> GO >>> >>> USE [comlinks] >>> >>> GO >>> >>> DBCC CHECKDB WITH NO_INFOMSGS >>> >>> >>> >>> And it reports: >>> >>> Msg 8914, Level 16, State 1, Line 1 >>> >>> Incorrect PFS free space information for page (1:487) 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. >>> >>> Msg 8914, Level 16, State 1, Line 1 >>> >>> Incorrect PFS free space information for page (1:504) 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 2 consistency errors in table >>> 'sys.sysobjvalues' (object ID 60). >>> >>> Msg 8914, Level 16, State 1, Line 1 >>> >>> Incorrect PFS free space information for page (3:42) in object ID >>> 373576369, index ID 1, partition ID 72057594038452224, alloc unit ID >>> 72057594044547072 (type LOB data). Expected value 0_PCT_FULL, actual >>> value 100_PCT_FULL. >>> >>> Msg 8914, Level 16, State 1, Line 1 >>> >>> Incorrect PFS free space information for page (3:44) in object ID >>> 373576369, index ID 1, partition ID 72057594038452224, alloc unit ID >>> 72057594044547072 (type LOB data). Expected value 0_PCT_FULL, actual >>> value 100_PCT_FULL. >>> >>> CHECKDB found 0 allocation errors and 2 consistency errors in table >>> 'Object' (object ID 373576369). >>> >>> CHECKDB found 0 allocation errors and 4 consistency errors in database >>> 'navisioncz'. >>> >>> repair_allow_data_loss is the minimum repair level for the errors found >>> by DBCC CHECKDB (navisioncz). >>> >>> >>> >>> >>> >>> >> >> > Hmm... and the other object referred to, object id 60 returns sysobjvalues
which I can't find anywhere in the database. Very perplexing. Any hints most welcome. Nigel Ainscoe Show quote "Andrew J. Kelly" <sqlmvpnooospam@shadhawk.com> wrote in message news:uHZvG6eMIHA.6100@TK2MSFTNGP03.phx.gbl... > Run this in the db in question: > > SELECT OBJECT_NAME(373576369) > > -- > Andrew J. Kelly SQL MVP > Solid Quality Mentors > > > "NigelA" <discussion@microsoft.newsgroups> wrote in message > news:upio7meMIHA.4752@TK2MSFTNGP05.phx.gbl... >> Also one of the messages: >> >> CHECKDB found 0 allocation errors and 2 consistency errors in table >>> 'Object' (object ID 373576369). >> >> Is very cryptic - how can I discover what this object is? If I have to >> run a repair_allow_data_loss I would like to know what is at risk :-( >> >> TIA >> Nigel Ainscoe >> >> >> "NigelA" <discussion@microsoft.newsgroups> wrote in message >> news:eaJ9lJeMIHA.1208@TK2MSFTNGP03.phx.gbl... >>>I have tried to run a maintenance plan which is just a Check Database >>>Integrity task set to: Target server connection, All user databases, >>>Include Indexes. It claims to run OK but then viewing the history shows >>>it has failed with the error "Alter failed for Server 'XYZDB02'" >>> >>> Is this just a crappy error message or is there more meaning to it? >>> >>> Running the plan manually gives the following and I understand that it >>> is back up time followed by a checkdb recover, but I don't understand >>> the message in the history viewer. >>> >>> The T-SQL generated for the plan is >>> USE [ReportServer] >>> >>> GO >>> >>> DBCC CHECKDB WITH NO_INFOMSGS >>> >>> GO >>> >>> USE [ReportServerTempDB] >>> >>> GO >>> >>> DBCC CHECKDB WITH NO_INFOMSGS >>> >>> GO >>> >>> USE [navisioncz] >>> >>> GO >>> >>> DBCC CHECKDB WITH NO_INFOMSGS >>> >>> GO >>> >>> USE [comlinks] >>> >>> GO >>> >>> DBCC CHECKDB WITH NO_INFOMSGS >>> >>> >>> >>> And it reports: >>> >>> Msg 8914, Level 16, State 1, Line 1 >>> >>> Incorrect PFS free space information for page (1:487) 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. >>> >>> Msg 8914, Level 16, State 1, Line 1 >>> >>> Incorrect PFS free space information for page (1:504) 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 2 consistency errors in table >>> 'sys.sysobjvalues' (object ID 60). >>> >>> Msg 8914, Level 16, State 1, Line 1 >>> >>> Incorrect PFS free space information for page (3:42) in object ID >>> 373576369, index ID 1, partition ID 72057594038452224, alloc unit ID >>> 72057594044547072 (type LOB data). Expected value 0_PCT_FULL, actual >>> value 100_PCT_FULL. >>> >>> Msg 8914, Level 16, State 1, Line 1 >>> >>> Incorrect PFS free space information for page (3:44) in object ID >>> 373576369, index ID 1, partition ID 72057594038452224, alloc unit ID >>> 72057594044547072 (type LOB data). Expected value 0_PCT_FULL, actual >>> value 100_PCT_FULL. >>> >>> CHECKDB found 0 allocation errors and 2 consistency errors in table >>> 'Object' (object ID 373576369). >>> >>> CHECKDB found 0 allocation errors and 4 consistency errors in database >>> 'navisioncz'. >>> >>> repair_allow_data_loss is the minimum repair level for the errors found >>> by DBCC CHECKDB (navisioncz). >>> >>> >>> >>> >>> >>> >> >> > sysobjvalues is a system table, and in SQL 2005, system tables are not
visible by default. If you run sp_help or select * from sys.all_objects you should see the name. You can only see the data in this table if you are using the Dedicated Administrator Connection, which you can read about in the Books Online. Show quote "NigelA" <discussion@microsoft.newsgroups> wrote in message news:u5xdxFgMIHA.4228@TK2MSFTNGP02.phx.gbl... > Hmm... and the other object referred to, object id 60 returns sysobjvalues > which I can't find anywhere in the database. Very perplexing. Any hints > most welcome. > > Nigel Ainscoe > > > "Andrew J. Kelly" <sqlmvpnooospam@shadhawk.com> wrote in message > news:uHZvG6eMIHA.6100@TK2MSFTNGP03.phx.gbl... >> Run this in the db in question: >> >> SELECT OBJECT_NAME(373576369) >> >> -- >> Andrew J. Kelly SQL MVP >> Solid Quality Mentors >> >> >> "NigelA" <discussion@microsoft.newsgroups> wrote in message >> news:upio7meMIHA.4752@TK2MSFTNGP05.phx.gbl... >>> Also one of the messages: >>> >>> CHECKDB found 0 allocation errors and 2 consistency errors in table >>>> 'Object' (object ID 373576369). >>> >>> Is very cryptic - how can I discover what this object is? If I have to >>> run a repair_allow_data_loss I would like to know what is at risk :-( >>> >>> TIA >>> Nigel Ainscoe >>> >>> >>> "NigelA" <discussion@microsoft.newsgroups> wrote in message >>> news:eaJ9lJeMIHA.1208@TK2MSFTNGP03.phx.gbl... >>>>I have tried to run a maintenance plan which is just a Check Database >>>>Integrity task set to: Target server connection, All user databases, >>>>Include Indexes. It claims to run OK but then viewing the history shows >>>>it has failed with the error "Alter failed for Server 'XYZDB02'" >>>> >>>> Is this just a crappy error message or is there more meaning to it? >>>> >>>> Running the plan manually gives the following and I understand that it >>>> is back up time followed by a checkdb recover, but I don't understand >>>> the message in the history viewer. >>>> >>>> The T-SQL generated for the plan is >>>> USE [ReportServer] >>>> >>>> GO >>>> >>>> DBCC CHECKDB WITH NO_INFOMSGS >>>> >>>> GO >>>> >>>> USE [ReportServerTempDB] >>>> >>>> GO >>>> >>>> DBCC CHECKDB WITH NO_INFOMSGS >>>> >>>> GO >>>> >>>> USE [navisioncz] >>>> >>>> GO >>>> >>>> DBCC CHECKDB WITH NO_INFOMSGS >>>> >>>> GO >>>> >>>> USE [comlinks] >>>> >>>> GO >>>> >>>> DBCC CHECKDB WITH NO_INFOMSGS >>>> >>>> >>>> >>>> And it reports: >>>> >>>> Msg 8914, Level 16, State 1, Line 1 >>>> >>>> Incorrect PFS free space information for page (1:487) 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. >>>> >>>> Msg 8914, Level 16, State 1, Line 1 >>>> >>>> Incorrect PFS free space information for page (1:504) 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 2 consistency errors in table >>>> 'sys.sysobjvalues' (object ID 60). >>>> >>>> Msg 8914, Level 16, State 1, Line 1 >>>> >>>> Incorrect PFS free space information for page (3:42) in object ID >>>> 373576369, index ID 1, partition ID 72057594038452224, alloc unit ID >>>> 72057594044547072 (type LOB data). Expected value 0_PCT_FULL, actual >>>> value 100_PCT_FULL. >>>> >>>> Msg 8914, Level 16, State 1, Line 1 >>>> >>>> Incorrect PFS free space information for page (3:44) in object ID >>>> 373576369, index ID 1, partition ID 72057594038452224, alloc unit ID >>>> 72057594044547072 (type LOB data). Expected value 0_PCT_FULL, actual >>>> value 100_PCT_FULL. >>>> >>>> CHECKDB found 0 allocation errors and 2 consistency errors in table >>>> 'Object' (object ID 373576369). >>>> >>>> CHECKDB found 0 allocation errors and 4 consistency errors in database >>>> 'navisioncz'. >>>> >>>> repair_allow_data_loss is the minimum repair level for the errors found >>>> by DBCC CHECKDB (navisioncz). >>>> >>>> >>>> >>>> >>>> >>>> >>> >>> >> > > Thanks Kalen
I have just done some rooting around and I get the new way they have done the system metadata in tables only accessible via the DAC and I can find my both my damaged objects. Nigel Ainscoe Show quote "Kalen Delaney" <replies@public_newsgroups.com> wrote in message news:%23iVfRMgMIHA.5860@TK2MSFTNGP04.phx.gbl... > sysobjvalues is a system table, and in SQL 2005, system tables are not > visible by default. > If you run sp_help or select * from sys.all_objects you should see the > name. > > You can only see the data in this table if you are using the Dedicated > Administrator Connection, which you can read about in the Books Online. > > -- > HTH > Kalen Delaney, SQL Server MVP > www.InsideSQLServer.com > http://sqlblog.com > > > "NigelA" <discussion@microsoft.newsgroups> wrote in message > news:u5xdxFgMIHA.4228@TK2MSFTNGP02.phx.gbl... >> Hmm... and the other object referred to, object id 60 returns >> sysobjvalues which I can't find anywhere in the database. Very >> perplexing. Any hints most welcome. >> >> Nigel Ainscoe >> >> >> "Andrew J. Kelly" <sqlmvpnooospam@shadhawk.com> wrote in message >> news:uHZvG6eMIHA.6100@TK2MSFTNGP03.phx.gbl... >>> Run this in the db in question: >>> >>> SELECT OBJECT_NAME(373576369) >>> >>> -- >>> Andrew J. Kelly SQL MVP >>> Solid Quality Mentors >>> >>> >>> "NigelA" <discussion@microsoft.newsgroups> wrote in message >>> news:upio7meMIHA.4752@TK2MSFTNGP05.phx.gbl... >>>> Also one of the messages: >>>> >>>> CHECKDB found 0 allocation errors and 2 consistency errors in table >>>>> 'Object' (object ID 373576369). >>>> >>>> Is very cryptic - how can I discover what this object is? If I have to >>>> run a repair_allow_data_loss I would like to know what is at risk :-( >>>> >>>> TIA >>>> Nigel Ainscoe >>>> >>>> >>>> "NigelA" <discussion@microsoft.newsgroups> wrote in message >>>> news:eaJ9lJeMIHA.1208@TK2MSFTNGP03.phx.gbl... >>>>>I have tried to run a maintenance plan which is just a Check Database >>>>>Integrity task set to: Target server connection, All user databases, >>>>>Include Indexes. It claims to run OK but then viewing the history shows >>>>>it has failed with the error "Alter failed for Server 'XYZDB02'" >>>>> >>>>> Is this just a crappy error message or is there more meaning to it? >>>>> >>>>> Running the plan manually gives the following and I understand that it >>>>> is back up time followed by a checkdb recover, but I don't understand >>>>> the message in the history viewer. >>>>> >>>>> The T-SQL generated for the plan is >>>>> USE [ReportServer] >>>>> >>>>> GO >>>>> >>>>> DBCC CHECKDB WITH NO_INFOMSGS >>>>> >>>>> GO >>>>> >>>>> USE [ReportServerTempDB] >>>>> >>>>> GO >>>>> >>>>> DBCC CHECKDB WITH NO_INFOMSGS >>>>> >>>>> GO >>>>> >>>>> USE [navisioncz] >>>>> >>>>> GO >>>>> >>>>> DBCC CHECKDB WITH NO_INFOMSGS >>>>> >>>>> GO >>>>> >>>>> USE [comlinks] >>>>> >>>>> GO >>>>> >>>>> DBCC CHECKDB WITH NO_INFOMSGS >>>>> >>>>> >>>>> >>>>> And it reports: >>>>> >>>>> Msg 8914, Level 16, State 1, Line 1 >>>>> >>>>> Incorrect PFS free space information for page (1:487) 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. >>>>> >>>>> Msg 8914, Level 16, State 1, Line 1 >>>>> >>>>> Incorrect PFS free space information for page (1:504) 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 2 consistency errors in table >>>>> 'sys.sysobjvalues' (object ID 60). >>>>> >>>>> Msg 8914, Level 16, State 1, Line 1 >>>>> >>>>> Incorrect PFS free space information for page (3:42) in object ID >>>>> 373576369, index ID 1, partition ID 72057594038452224, alloc unit ID >>>>> 72057594044547072 (type LOB data). Expected value 0_PCT_FULL, actual >>>>> value 100_PCT_FULL. >>>>> >>>>> Msg 8914, Level 16, State 1, Line 1 >>>>> >>>>> Incorrect PFS free space information for page (3:44) in object ID >>>>> 373576369, index ID 1, partition ID 72057594038452224, alloc unit ID >>>>> 72057594044547072 (type LOB data). Expected value 0_PCT_FULL, actual >>>>> value 100_PCT_FULL. >>>>> >>>>> CHECKDB found 0 allocation errors and 2 consistency errors in table >>>>> 'Object' (object ID 373576369). >>>>> >>>>> CHECKDB found 0 allocation errors and 4 consistency errors in database >>>>> 'navisioncz'. >>>>> >>>>> repair_allow_data_loss is the minimum repair level for the errors >>>>> found by DBCC CHECKDB (navisioncz). >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>> >> >> > > Thanks for everones comments on this. I have a couple of other question
around it. First, one of the tables that reports 2 consistency errors is sys.sysobjvalues. As Kalen points out this is a system metadata table. Does anyone have a feel for what 2 consistency errors on this table means? Is it the end of the world or do people usually get away with it? Second, what are the usual causes of these errors? TIA Nigel Ainscoe P.S. I found the answer to the original question about "Failed:(0) Alter failed for Server xyz". It's caused by the Allow Updates sys.configurations setting being changed from 0 to 1 which makes the RECONFIGURE statement fail. See http://sqljunkies.com/WebLog/acalvett/archive/2006/02/13/17999.aspx for the lowdown Show quote "NigelA" <discussion@microsoft.newsgroups> wrote in message news:eaJ9lJeMIHA.1208@TK2MSFTNGP03.phx.gbl... >I have tried to run a maintenance plan which is just a Check Database >Integrity task set to: Target server connection, All user databases, >Include Indexes. It claims to run OK but then viewing the history shows it >has failed with the error "Alter failed for Server 'XYZDB02'" > > Is this just a crappy error message or is there more meaning to it? > > Running the plan manually gives the following and I understand that it is > back up time followed by a checkdb recover, but I don't understand the > message in the history viewer. > > The T-SQL generated for the plan is > USE [ReportServer] > > GO > > DBCC CHECKDB WITH NO_INFOMSGS > > GO > > USE [ReportServerTempDB] > > GO > > DBCC CHECKDB WITH NO_INFOMSGS > > GO > > USE [navisioncz] > > GO > > DBCC CHECKDB WITH NO_INFOMSGS > > GO > > USE [comlinks] > > GO > > DBCC CHECKDB WITH NO_INFOMSGS > > > > And it reports: > > Msg 8914, Level 16, State 1, Line 1 > > Incorrect PFS free space information for page (1:487) 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. > > Msg 8914, Level 16, State 1, Line 1 > > Incorrect PFS free space information for page (1:504) 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 2 consistency errors in table > 'sys.sysobjvalues' (object ID 60). > > Msg 8914, Level 16, State 1, Line 1 > > Incorrect PFS free space information for page (3:42) in object ID > 373576369, index ID 1, partition ID 72057594038452224, alloc unit ID > 72057594044547072 (type LOB data). Expected value 0_PCT_FULL, actual > value 100_PCT_FULL. > > Msg 8914, Level 16, State 1, Line 1 > > Incorrect PFS free space information for page (3:44) in object ID > 373576369, index ID 1, partition ID 72057594038452224, alloc unit ID > 72057594044547072 (type LOB data). Expected value 0_PCT_FULL, actual > value 100_PCT_FULL. > > CHECKDB found 0 allocation errors and 2 consistency errors in table > 'Object' (object ID 373576369). > > CHECKDB found 0 allocation errors and 4 consistency errors in database > 'navisioncz'. > > repair_allow_data_loss is the minimum repair level for the errors found by > DBCC CHECKDB (navisioncz). > > > > > > Have a look at these blog posts:
http://blogs.msdn.com/sqlserverstorageengine/archive/tags/DBCC+CHECKDB+Series/default.aspx -- Show quoteAndrew J. Kelly SQL MVP Solid Quality Mentors "NigelA" <discussion@microsoft.newsgroups> wrote in message news:eq71PzgMIHA.3516@TK2MSFTNGP02.phx.gbl... > Thanks for everones comments on this. I have a couple of other question > around it. > > First, one of the tables that reports 2 consistency errors is > sys.sysobjvalues. As Kalen points out this is a system metadata table. > Does anyone have a feel for what 2 consistency errors on this table means? > Is it the end of the world or do people usually get away with it? > > Second, what are the usual causes of these errors? > > TIA > Nigel Ainscoe > > P.S. I found the answer to the original question about "Failed:(0) Alter > failed for Server xyz". It's caused by the Allow Updates > sys.configurations setting being changed from 0 to 1 which makes the > RECONFIGURE statement fail. See > http://sqljunkies.com/WebLog/acalvett/archive/2006/02/13/17999.aspx for > the lowdown > > > > > > > "NigelA" <discussion@microsoft.newsgroups> wrote in message > news:eaJ9lJeMIHA.1208@TK2MSFTNGP03.phx.gbl... >>I have tried to run a maintenance plan which is just a Check Database >>Integrity task set to: Target server connection, All user databases, >>Include Indexes. It claims to run OK but then viewing the history shows it >>has failed with the error "Alter failed for Server 'XYZDB02'" >> >> Is this just a crappy error message or is there more meaning to it? >> >> Running the plan manually gives the following and I understand that it is >> back up time followed by a checkdb recover, but I don't understand the >> message in the history viewer. >> >> The T-SQL generated for the plan is >> USE [ReportServer] >> >> GO >> >> DBCC CHECKDB WITH NO_INFOMSGS >> >> GO >> >> USE [ReportServerTempDB] >> >> GO >> >> DBCC CHECKDB WITH NO_INFOMSGS >> >> GO >> >> USE [navisioncz] >> >> GO >> >> DBCC CHECKDB WITH NO_INFOMSGS >> >> GO >> >> USE [comlinks] >> >> GO >> >> DBCC CHECKDB WITH NO_INFOMSGS >> >> >> >> And it reports: >> >> Msg 8914, Level 16, State 1, Line 1 >> >> Incorrect PFS free space information for page (1:487) 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. >> >> Msg 8914, Level 16, State 1, Line 1 >> >> Incorrect PFS free space information for page (1:504) 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 2 consistency errors in table >> 'sys.sysobjvalues' (object ID 60). >> >> Msg 8914, Level 16, State 1, Line 1 >> >> Incorrect PFS free space information for page (3:42) in object ID >> 373576369, index ID 1, partition ID 72057594038452224, alloc unit ID >> 72057594044547072 (type LOB data). Expected value 0_PCT_FULL, actual >> value 100_PCT_FULL. >> >> Msg 8914, Level 16, State 1, Line 1 >> >> Incorrect PFS free space information for page (3:44) in object ID >> 373576369, index ID 1, partition ID 72057594038452224, alloc unit ID >> 72057594044547072 (type LOB data). Expected value 0_PCT_FULL, actual >> value 100_PCT_FULL. >> >> CHECKDB found 0 allocation errors and 2 consistency errors in table >> 'Object' (object ID 373576369). >> >> CHECKDB found 0 allocation errors and 4 consistency errors in database >> 'navisioncz'. >> >> repair_allow_data_loss is the minimum repair level for the errors found >> by DBCC CHECKDB (navisioncz). >> >> >> >> >> >> > >  |
|||||||||||||||||||||||
Other interesting topics