QC10 Corrupt Project.... NOT
Here's something to watch out for. When you upgrade, verify, or repair any project in QC10 you might end up with a message that says "project is corrupt" and because of that you cannot activate the project.
This happens if there are ANY additional tables, fields, etc in the schema of your project.
For example.. we were running TOAD to help with the performance issues we are seeing.. TOAD creates a table in the same schema as the project. Because of this 'new' table QC detected an invalid schema and marks the project as corrupt.
I feel this is a poor design on HP's part. They should only be concerned that 'their' tables, fields, etc exist and are to their design. They should not care if other tables, etc exist.
Fortunately there is a way to get your project to activate. You will need access to the SiteAdmin schema to modify a field in the Projects table.. PR_MAINTENANCE_STATE. Just remember not to run Verify or Repair again.. unless you have removed the 'extra' database objects.
Re: QC10 Corrupt Project.... NOT
In this case if you have backup of the project repository(Filesyatem) then delete the corrupt project and restore the project using dbid.xml file. After restoring, run the verify and upgrade tool.
Re: QC Performance
You mention performance problems - is that with V10 of QC? Many of my users are saying 10 is much slower than 9.2 ...