QCsiteadmin database has gone to SUSPECT and is no longer accessible after failed patch attempt
Question ID: 106808
1
0

After attempted install of patch for ALM 11.52, I am now getting an error. It does not show it finished installing, got a failure. I tried doing a redeploy on ALM and it failed at the attempt to talk to qcsiteadmin database (said it was not accessible, cannot be opened). Upon logging into SQL Server, I see the qcsiteadmin_db is now listed as SUSPECT and it cannot be viewed.

How do I repair this? I have a backup I can fall back to but wanted to see if there was anything I could attempt before trying that.

Marked as spam
Posted by (Questions: 56, Answers: 1)
Asked on April 27, 2016 8:41 pm
36 views
Answers (1)
1
Private answer

Hello,

You might have to resort to the backup, but please try the following from your SQL server, logged in as SA user.

Open new query window and running the following commands:

Run EXEC sp_resetstatus 'DB_Name';

**This sp_resetstatus turns off the suspect flag on a database**

ALTER DATABASE DB_Name SET EMERGENCY;

**Sets EMERGENCY mode that is READ_ONLY copy and only sysadmin has access to do a repair**

DBCC checkdb('DB_Name');

**Performs Integrity check among all the objects**

ALTER DATABASE DB_Name SET SINGLE_USER WITH ROLLBACK IMMEDIATE;

**Sets the database to single user mode**

DBCC CheckDB ('DB_Name', REPAIR_ALLOW_DATA_LOSS);

**Repair the errors**

ALTER DATABASE DB_Name SET MULTI_USER;

**Sets the database to multi user mode, so that it can now be accessed by others**

At this point try a refresh in SQL Server and see if the qcsiteadmin_DB is now accessible.

If okay, would try to install the patch again.

Marked as spam
Posted by (Questions: 1, Answers: 116)
Answered on April 27, 2016 8:46 pm
0
That worked! The DB is now back to normal and all tables inside are able to be accessed. Nice!
( at April 27, 2016 9:16 pm)
EyeOnTesting

Welcome back to "EyeOnTesting" brought to you by Orasi Software, Inc.

X
Scroll to Top