Error 605 database suspect
-
Hi there, just got off the plane(so to speak) and am currently trying to recover a corrupt database. the following are some of the event viewer error meaages. I know that I can recover by doing a full recovery, but was wonding if there is any other way. database is off suspect, but I can't see the data files. nor can I access the database through query analysis.
Error: 605, Severity: 21, State: 1
Attempt to fetch logical page (1:6790199) in database 'PROD_Datamarts' belongs to object 'F_GL', not to object 'F_Invoice_Tax'.
Error: 3314, Severity: 21, State: 3
Error while undoing logged operation in database 'PROD_Datamarts'. Error at log record ID (428928:8989:27).
Error: 3414, Severity: 21, State: 1
Database 'PROD_Datamarts' (database ID 12) could not recover. Contact Technical Support.
2004-05-10 13:15:24.40 spid16 Recovery of database 'PROD_Datamarts' (12) is 75% complete (approximately 111 more seconds) (Phase 2 of 3).
2004-05-10 13:15:27.85 spid16 Recovery of database 'PROD_Datamarts' (12) is 76% complete (approximately 106 more seconds) (Phase 2 of 3).
2004-05-10 13:15:31.03 spid16 Recovery of database 'PROD_Datamarts' (12) is 77% complete (approximately 101 more seconds) (Phase 2 of 3).
2004-05-10 13:15:59.65 spid16 Recovery of database 'PROD_Datamarts' (12) is 78% complete (approximately 97 more seconds) (Phase 2 of 3).
2004-05-10 13:15:59.65 spid16 37 transactions rolled forward in database 'PROD_Datamarts' (12).
2004-05-10 13:15:59.82 spid16 Recovery of database 'PROD_Datamarts' (12) is 78% complete (approximately 97 more seconds) (Phase 3 of 3).
2004-05-10 13:16:00.71 spid16 Getpage: bstat=0x9, sstat=0, cache
2004-05-10 13:16:00.73 spid16 pageno is/should be: objid is/should be:
2004-05-10 13:16:00.73 spid16 (1:6790199)/(1:6790199) 1611868809/1090818948
2004-05-10 13:16:00.85 spid16 ... IAM indicates that page is allocated to this object
2004-05-10 13:16:00.88 spid16 Error: 605, Severity: 21, State: 1
2004-05-10 13:16:00.88 spid16 Attempt to fetch logical page (1:6790199) in database 'PROD_Datamarts' belongs to object 'F_GL', not to object 'F_Invoice_Tax'..
2004-05-10 13:16:00.90 spid16 Error: 3314, Severity: 21, State: 3
2004-05-10 13:16:00.90 spid16 Error while undoing logged operation in database 'PROD_Datamarts'. Error at log record ID (428928:8989:27)..
2004-05-10 13:16:01.04 spid16 Error: 3414, Severity: 21, State: 1
2004-05-10 13:16:01.04 spid16 Database 'PROD_Datamarts' (database ID 12) could not recover. Contact Technical Support..
2004-05-10 13:16:47.42 spid3 Recovery complete.
2004-05-10 13:16:47.42 spid3 SQL global counter collection task is created.
2004-05-10 13:16:48.10 spid57 Using 'xpsqlbot.dll' version '2000.80.194' to execute extended stored procedure 'xp_qv'.
2004-05-10 13:31:53.84 spid55 Error: 15457, Severity: 0, State: 1
2004-05-10 13:31:53.84 spid55 Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install..
2004-05-10 13:31:53.92 spid55 Using 'xplog70.dll' version '2000.80.760' to execute extended stored procedure 'xp_msver'.
Please help. Thanks
-
Have a look at topic "Resetting the Suspect Status" in Books Online. It tells you how to change the status of a suspect database.
Also, have a look at the details of Error 605 in Books Online.
You might be able to get correct the problem but you may loose some of the data.
I would also be checking the Windows Event Log to see if Windows has reported an error with the disk(s) that you have your database on. If you see errors here, get them addressed otherwise your database will most likely have a problem in the very near future.
-
yes ran the sp_resetstatus, but the database is still not letting me attach to it through query anaylsis. saying that 'database status marked are suspect by recovery' (it doesn't say that in on the database). which means I can't run the dbcc checkdb with rebuild statement.
have now detached the database and tried to re-attach it, but no good. will restore from back up.
thank you for your help
-
Did you restart SQL after running sp_resetstatus
-
I rebooted the server. thought that might help, but even though it didn't have suspect in brackets next to the database, it kept giving me a error 927. "database thought suspect by recovery'.
In the process of restoring back up now. not too much data loss.
-
Good luck. Hopefully the problem was transient but a little paranoia is advisable. Make sure that the disk sub-system is stable otherwise you will be playing the same "Restore the database" game again in the near future
-
thanks for your help. seems to be coming up now, and have checked the machine to ensure that the disk is not corrupt
-
hi, got the same problem over here,
a suspect DB, already reset status, but when I ran DBCC CHECKDB, still got the error message.
is there a way out except recover DB from backup.
thanks,
-
Good evening all. I ran into this problem today as well, SQL 2000.
One person is blaming that a SHRINK LOG was run on that database, and this caused the start of the problem. There are other such errors; something about an index can not be located, or something to that effect.
We are restoring from a backup but have been down for hours. The same case however, ran the SP to force the DB out of SUSPECT however we still could not access it.
Question is what causes this to happen? The log file drive on this machine is down pretty low; 2.8 GB available and the database with the problem is 40 GB. We have had space warnings on a fairly regular basis and for this reason I try to shrink the log file on a regular basis, and even during the day if I am performing aggressive maintenance on some tables (ie: Deleting millions of records).
Again any input as to what might have caused something like this would be great.
<hr noshade size=1 width=250 color=#BBC8E5> Regards,Jeffery Williams http://www.linkedin.com/in/jwilliamsoh
-
The log file will increase significantly if the database is in full recovery, lots of activity and transaction logs backups are not performed or there are big transactions happening.
Since you are saying that you can shrink the log file, probably is the first.
Regarding the corruption of the database, hard to say, maybe if you can post the SQL Server log file.
-
Check in case if the drive on which u are having the log files is compression formatted.
Prasad Bhogadi
www.inforaise.com -
Log File from crash:
2006-01-19 12:23:07.81 backup Database log truncated: Database: current1sql.
2006-01-19 12:33:36.73 spid455 The index entry for row ID was not found in index ID 9, of table 107289775, in
2006-01-19 12:33:36.73 spid455 Error: 8646, Severity: 21, State: 1
2006-01-19 12:33:36.84 spid455 Using 'dbghelp.dll' version '4.0.5'...
2006-01-19 12:33:39.29 spid455 Stack Signature for the dump is 0x33F9377A
2006-01-19 12:33:39.31 spid455 Error: 3624, Severity: 20, State: 1.
2006-01-19 12:33:39.31 spid455 SQL Server Assertion: File: <scanrid.cpp>, line=321 ...
2006-01-19 12:33:42.37 spid455 An error occurred while processing the log for database 'current1sql'..
2006-01-19 12:33:42.37 spid455 Error: 9004, Severity: 23, State: 2
2006-01-19 12:33:42.38 spid455 Error while undoing logged operation in database 'current1sql'. Error at log re
2006-01-19 12:33:42.38 spid455 Error: 3314, Severity: 21, State: 4
2006-01-19 12:33:42.43 spid455 Using 'dbghelp.dll' version '4.0.5'...
2006-01-19 12:33:42.85 spid455 Stack Signature for the dump is 0xAFC95170
2006-01-19 12:33:42.87 spid455 SQL Server Assertion: File: <scanrid.cpp>, line=321 ...
2006-01-19 12:33:42.88 spid455 Could not find the index entry for RID '' in index page (1:1777637), index ID
2006-01-19 12:33:42.88 spid455 Error: 644, Severity: 21, State: 5
2006-01-19 12:33:45.95 spid455 An error occurred while processing the log for database 'current1sql'..
2006-01-19 12:33:45.95 spid455 Error: 9004, Severity: 23, State: 2
2006-01-19 12:33:45.96 spid455 The log for database 'current1sql' is not available..
2006-01-19 12:33:45.96 spid455 Error: 9001, Severity: 21, State: 1
2006-01-19 12:33:45.96 spid455 Error while undoing logged operation in database 'current1sql'. Error at log re
2006-01-19 12:33:45.96 spid455 Error: 3314, Severity: 21, State: 4
2006-01-19 12:33:49.13 spid455 An error occurred while processing the log for database 'current1sql'..
2006-01-19 12:33:49.13 spid455 Error: 9004, Severity: 23, State: 2
2006-01-19 12:33:49.15 spid455 Error while undoing logged operation in database 'current1sql'. Error at log re
2006-01-19 12:33:49.15 spid455 Error: 3314, Severity: 21, State: 5
2006-01-19 12:33:49.76 spid19 Database 'current1sql' cannot be opened. It has been marked SUSPECT by recovery
2006-01-19 12:33:49.76 spid19 Database 'current1sql' cannot be opened. It has been marked SUSPECT by recovery
2006-01-19 12:33:49.76 spid19 Database 'current1sql' cannot be opened. It has been marked SUSPECT by recovery
2006-01-19 12:33:50.27 spid19 Starting up database 'current1sql'.
2006-01-19 12:34:05.06 spid19 Analysis of database 'current1sql' (7) is 14% complete (approximately 3 more se
2006-01-19 12:34:09.54 spid19 Recovery of database 'current1sql' (7) is 0% complete (approximately 597 more s
2006-01-19 12:34:09.54 spid19 Analysis of database 'current1sql' (7) is 100% complete (approximately 0 more s
2006-01-19 12:34:31.16 spid19 Recovery of database 'current1sql' (7) is 3% complete (approximately 561 more s
2006-01-19 12:34:34.23 spid19 Recovery of database 'current1sql' (7) is 4% complete (approximately 556 more s
2006-01-19 12:34:34.81 spid19 39 transactions rolled forward in database 'current1sql' (7).
2006-01-19 12:34:34.81 spid19 Recovery of database 'current1sql' (7) is 4% complete (approximately 555 more s
2006-01-19 12:34:34.95 spid19 Recovery of database 'current1sql' (7) is 4% complete (approximately 555 more s
2006-01-19 12:34:35.04 spid19 Using 'dbghelp.dll' version '4.0.5'...
2006-01-19 12:34:35.45 spid19 Stack Signature for the dump is 0xF6820BE0
2006-01-19 12:34:35.46 spid19 Error while undoing logged operation in database 'current1sql'. Error at log re
2006-01-19 12:34:35.46 spid19 Error: 3314, Severity: 21, State: 3
2006-01-19 12:34:35.46 spid19 Error: 3624, Severity: 20, State: 1.
2006-01-19 12:34:35.46 spid19 Location: scanrid.cpp:321...
2006-01-19 12:34:35.46 spid19 SQL Server Assertion: File: <scanrid.cpp>, line=321 ...
2006-01-19 12:34:39.54 spid19 An error occurred while processing the log for database 'current1sql'..
2006-01-19 12:34:39.54 spid19 Error: 9004, Severity: 23, State: 2
2006-01-19 12:34:39.59 spid19 Database 'current1sql' (database ID 7) could not recover. Contact Technical Sup
2006-01-19 12:34:39.59 spid19 Error: 3414, Severity: 21, State: 1
<hr noshade size=1 width=250 color=#BBC8E5> Regards,Jeffery Williams http://www.linkedin.com/in/jwilliamsoh
-
See the
http://support.microsoft.com/default.aspx/kb/822756
http://www.sql-server-performance.com/forum/post.asp?method=TopicQuote&TOPIC_ID=6112&FORUM_ID=4
for the
2006-01-19 12:33:39.31 spid455 Error: 3624, Severity: 20, State: 1.
2006-01-19 12:33:39.31 spid455 SQL Server Assertion: File: <scanrid.cpp>, line=321 ...
Base on the
2006-01-19 12:33:36.73 spid455 The index entry for row ID was not found in index ID 9, of table 107289775, in
and
2006-01-19 12:33:45.95 spid455 An error occurred while processing the log for database 'current1sql'..
I think there were corruption on both data and log files. I personally would check first Event Viewer for any error messages and also the HDs and the controller(s) for any issues or firmware fixes.
-
Thank you for your help.
<hr noshade size=1 width=250 color=#BBC8E5> Regards,Jeffery Williams http://www.linkedin.com/in/jwilliamsoh
-
Hi all,
I am also facing the same type of error in one of our SQL Server 2000 Version.
When I check Logs it shows this:
'Error 605, Severity:21,State:1'
When I checked the database it is fine and not in SUSPECT mode.When I ran DBCC CHECKDB also it didn't showed any errors.Even I tried with the options REPAIR_BUILD and other options as well but no luck.
Now its decided to reboot the server.Is there any other way to resolve this issue.Instead of rebooting the machine.(Its a live server).
Thanks
Viewing 15 posts - 1 through 14 (of 14 total)
You must be logged in to reply to this topic. Login to reply