Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2001-07-25 : 01:12:16
|
| Mike writes "Operating System : NT 4.0 Enterprise Manager Service Pack 4Server Name : BANKSERVERDatabase : Microsoft SQL Server 7.0 Service Pack 2Our production database name is 'dbbank'Database file is 'e:\mssql7\data\dbbank.mdf'We take an error message along 12 days. It seems at Sql Error Logand NT Application Event Log.Error: 823, Severity: 24, State: 1I/O error (bad page ID) detected during read of BUF pointer = 0x12dc2600, page ptr = 0x27170000, pageid = (0x1:0x9ff18), dbid = 7, status = 0x801, file = e:\mssql7\data\dbbank.mdf. Error frequency is approximately every 10 seconds.We look at books online, it says :--- Beginning of SQL Error Log Message ---Error 823 Severity Level 24 Message Text I/O error %ls detected during %S_MSG of %S_BUF.ExplanationMicrosoft® SQL Server™ encountered an I/O error on a read or write request made to a device. This error usually indicates disk problems. The parameters in the error message refer to internal structures and don’t often help determine which device is involved. However, additional kernel messages in the error log, recorded before error 823, should indicate which device is involved.ActionCheck the accessibility and condition of the device in question. After you have identified and corrected the problem, execute DBCC CHECKDB to ensure that no other damage was caused by the bad device. For information about using DBCC CHECKDB, see DBCC CHECKDB. --- End of SQL Error Log Message ---But we haven't any disk error.On the other hand we run this statement:Dbcc CheckDb (Dbbank)The result is below.--- Beginning of Dbcc Result ---Msg 8998, Level 16, State 1, Server BANKSERVER, Procedure , Line 4[Microsoft][ODBC SQL Server Driver][SQL Server]Page corruptions on theGAM, SGAM, or PFS pages do not allow CHECKALLOC to verify database ID7 pages from (1:511232) to (1:669000). See other errors for cause.Msg 8909, Level 16, State 1, Server BANKSERVER, Procedure , Line 4[Microsoft][ODBC SQL Server Driver][SQL Server]Table Corrupt: ObjectID 0, index ID 0, page ID (1:655128). The PageId in the page header =(0:0).DBCC results for 'dbbank'.CHECKDB found 1 allocation errors and 1 consistency errors notassociated with any single object.DBCC results for 'sysobjects'.There are 2913 rows in 72 pages for object 'sysobjects'.DBCC results for 'sysindexes'.There are 1929 rows in 116 pages for object 'sysindexes'.DBCC results for 'syscolumns'.There are 21826 rows in 467 pages for object 'syscolumns'.DBCC results for 'systypes'.There are 296 rows in 5 pages for object 'systypes'.DBCC results for 'syscomments'.There are 3728 rows in 2644 pages for object 'syscomments'.DBCC results for 'sysfiles1'.There are 2 rows in 1 pages for object 'sysfiles1'.DBCC results for 'syspermissions'.There are 5049 rows in 21 pages for object 'syspermissions'.DBCC results for 'sysusers'.There are 669 rows in 9 pages for object 'sysusers'.DBCC results for 'sysdepends'.There are 47040 rows in 386 pages for object 'sysdepends'.DBCC results for 'sysreferences'.There are 4 rows in 1 pages for object 'sysreferences'.DBCC results for 'sysfulltextcatalogs'.There are 0 rows in 1 pages for object 'sysfulltextcatalogs'.DBCC results for 'sysfilegroups'.There are 1 rows in 1 pages for object 'sysfilegroups'.DBCC results for 'sysallocations'...User defined tables. (No error or warning message for these tables)..CHECKDB found 1 allocation errors and 1 consistency errors in database'dbbank'.DBCC execution completed. If DBCC printed error messages, contact yoursystem administrator.--- End of Dbcc Result ---Now, what should we do?What's the status of our database?What's your advice?" |
|
|
|
|
|
|
|
Error 823 in SQL Server Log and Result of DBCC CheckDb