We've been getting 605 errors and 823 errors pretty
frequently for a few days now. They always occur on the
same database and they always happen during the same
job. The 605 errors are usually to the effect "attempt
to fetch logical page blabla in database 'x' belongs to
object A, not B. So we've done DBCC CHECKDB on the
database and it reports no errors. Then we do DBCC
CHECKTBL on B from the previous example error message,
and it's fine too. Initial investigation makes hardware
problems unlikely. Is there anything we're overlooking
in this situation? Thanks.
Re: DBCC CHECKDB Errors ... Here's a start if you have corruption of a suspect database:..."Prasad Koukuntla" wrote in message ... I got the following errors when I ran the DBCC Checkdb on my ... However, I am already running SQL SERVER SP3,... (microsoft.public.sqlserver.server)
Re: Attempt to fetch logical page ... You have a corruption in your database.... Second, if you are on SQL Server 2000, check the specific recommendations for your error. ... This error occurs when Microsoft® SQL ServerT detects database corruption....execute DBCC CHECKDB to determine the extent of the damage. ... (microsoft.public.sqlserver.server)
Re: Problem SQL 6.5 ... In SQL 6.5 the error 605 it is very hard to solve, Execute DBCC CHECKDB on ... the database and identify the table got corrupted. ...Script out the indexes of that table. ...rename the original table to tablename_old ... (microsoft.public.sqlserver.server)
Re: DBCC CHCECKTABLE faults go away after reboot? ... The database with corrupt sysindexes cannot be repaired and will need to be ... documented reasons not to run CHECKDB on a very busy system. ...Microsoft SQL Server Storage Engine... > - one database with sysindexes table failing DBCC CHECKDB,... (microsoft.public.sqlserver.server)
Re: Database recovery with data file only ... Although DBCC CHECKDB can detect physical corruption,... > up the database ken can execute a DBCC CHECKDB and confirm that database ... >> A preferable method is to restore from backup.... (microsoft.public.sqlserver.server)
