How to get rid of messge
- Thread starter SSuhaib
- Start date
Rob Fitzpatrick
ProgressTalk.com Sponsor
Do you know why someone felt the need to force access to the database? You may now have logical corruption in the database that an index rebuild will not fix.
Do you have a good backup you can restore?
Do you have a good backup you can restore?
TheMadDBA
Active Member
Like Rob said... the message is the least of your worries, your database is in an inconsistent state and needs to be restored from a backup. Thankfully this is just your development database.
You really need to worry that somebody decided (and had the ability) to start it with the -F option without knowing what that meant.
You really need to worry that somebody decided (and had the ability) to start it with the -F option without knowing what that meant.
TomBascom
Curmudgeon
Rebuilding the indexes will not fix the problem. Neither does dumping and loading. Either approach may make the message go away but the issues are still there.
When someone uses -F the database is hosed. Do not be fooled -- even if it seems that most of your data is intact or you cannot find any specific error -- the database was indeed compromised.
-F means "forget about all of those consistency checks -- toss out the transaction log and do whatever you can to startup". Which means that updates and rollbacks are only partially completed and in an inconsistent state. There is no way to determine what data is valid and what data is invalid.
The only correct solution is to restore from backup and roll forward.
When someone uses -F the database is hosed. Do not be fooled -- even if it seems that most of your data is intact or you cannot find any specific error -- the database was indeed compromised.
-F means "forget about all of those consistency checks -- toss out the transaction log and do whatever you can to startup". Which means that updates and rollbacks are only partially completed and in an inconsistent state. There is no way to determine what data is valid and what data is invalid.
The only correct solution is to restore from backup and roll forward.