| || |
ClearQuest: SQL Native Error=4922 \"Database may be in an inconsistent state\"
User Mike Anderson (firstname.lastname@example.org) posted:
Greetings. Was modifying a ClearQuest schema when I received this error.
SQL Server 2000 has now locked my DB and no one can get in to issue
Software Probelm Reports.
This is halting maintenance on a production system. Any suggestions on
how to fix this? MS recommends restoration from backup...but I'm
wondering if there is a way around that?
Re: ClearQuest: SQL Native Error=4922 \"Database may be in an inconsistent state\"
User Sarah Hutchins (email@example.com) posted:
Undo the schema checkout, then delete that version of the schema (it'll
show up in the "View schema version" option in the checkout wizard). You
can also unlock the db manually if it's still being stubborn after that.
Were you upgrading the user db while people were in it?