Error 625 very often occuring in sql 7.0 | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

Error 625 very often occuring in sql 7.0

We are getting the error 625 with severity 20 state 1 Could not retrieve row from logical page (0:75839) by RID because the entry in the offset table (16) for that RID (444244036) is less than or equal to 0.. If we run dbcc checkdb we found no errors. What could be the problem and With this how can we find the object id Rushendra
quote:…one of the KBA
(don’t have number for reference) Explanation This error occurs when an object to which this row belongs is in error.
The problem was detected during the reading of a specific row from that logical page.
This error can occur as a result of: Hardware problems, especially problems with the hard drive, controller or hardware
write caching. Other errors in the database. Action Execute DBCC CHECKDB to determine the full
extent of the error. Also check the error log for other errors such as 25xx messages,
which often accompany this error. If DBCC CHECKDB issues other error messages, resolving those messages first may take
care of this error. Execute DBCC CHECKDB with the REPAIR_REBUILD clause to repair
the damage. Important If executing DBCC CHECKDB with the REPAIR_REBUILD clause does not correct
the index problem or if you are unsure what effect DBCC CHECKDB with the
REPAIR_REBUILD clause has on your data, contact your primary support provider. If executing DBCC CHECKDB with the REPAIR_REBUILD clause does not resolve all table
error problems, determine which table is affected by examining the page in the error
message. If the page is associated with an index, you may be able to resolve the
problem by dropping and then re- creating the index. If the page is a data page and a
clean current backup is available, restore the database from the backup. If no backup is available, select the table into another table or bulk copy data out
of the table, drop the table, re-create it, and then select data back into the table. If you suspect a hardware problem, run hardware diagnostics and correct any problems.
You might find it beneficial to perform a completely new setup, including
reformatting the disk drives and reinstalling the operating system. Also examine the
Microsoft® Windows NT® application log to see if the error occurred as the result of
hardware failure. Finally, be sure that your system does not have write caching enabled on the disk
controller. If you suspect this to be the problem, contact your hardware vendor.

Satya SKJ

You will find the text for the article on MSDN online at this URL:] NHO