This document has not been formally reviewed for accuracy and is provided "as is" for your convenience.
Summary
Verify fails with error "The task that failed belongs to ALM platform"
Error
Verifying "d1_history_volume2"...
2014-10-07 01:03:16.243 Trying to connect to database hcs_d1_history_volume2_db on server ITSUSMPW01198
2014-10-07 01:03:16.253 Connection established
2014-10-07 01:03:16.263 The project version is 11.50
2014-10-07 01:03:16.273 The project enabled extensions are: SPRINTER_EXTENSION_12.00; ANALYSIS_11.50; QUALITY_CENTER_11.50
2014-10-07 01:03:16.283 Checking if the project schema is not read-only ...
2014-10-07 01:03:16.297 Passed
2014-10-07 01:03:17.247 The task that failed belongs to ALM platform
2014-10-07 01:03:17.257 Error: null
2014-10-07 01:03:17.267 Stack: at
2014-10-07 01:03:17.273 Error: java.lang.NullPointerException
2014-10-07 01:03:17.283 Stack: com.mercury.dbupgrade.DBUQcActionRunner.getSchemaFromDB(DBUQcActionRunner.java:221)
2014-10-07 01:03:17.293 Stack: com.mercury.dbupgrade.DBUQcActionRunner.getSchemaFromDB(DBUQcActionRunner.java:211)
2014-10-07 01:03:17.303 Stack: com.mercury.dbverify.DBVGetSchemaHandlerRunnerUpgradeRunner.getTargetSchema(DBVGetSchemaHandlerRunnerUpgradeRunner.java:47)
2014-10-07 01:03:17.313 Stack: com.hp.alm.platform.db.verify.tasks.LoadTargetSchemaTask.doAll(LoadTargetSchemaTask.java:67)
2014-10-07 01:03:17.323 Stack: at
2014-10-07 01:03:17.333 Error: com.mercury.dbupgrade.DBUEnvironmentException: java.lang.NullPointerException
2014-10-07 01:03:17.343 Stack: com.mercury.dbverify.DBVGetSchemaHandlerRunnerUpgradeRunner.getTargetSchema(DBVGetSchemaHandlerRunnerUpgradeRunner.java:50)
2014-10-07 01:03:17.353 Stack: com.hp.alm.platform.db.verify.tasks.LoadTargetSchemaTask.doAll(LoadTargetSchemaTask.java:67)
2014-10-07 01:03:17.363 Stack: at
2014-10-07 01:03:17.373 Error:
2014-10-07 01:03:17.383 Stack: com.hp.alm.platform.db.verify.tasks.LoadTargetSchemaTask.doAll(LoadTargetSchemaTask.java:71)
2014-10-07 01:03:17.393
2014-10-07 01:03:17.403 verify.status.VERIFY_ABORTED
2014-10-07 01:03:17.41 For possible causes and solutions, refer to the errors in the upgrade log above, the ALM Site Administrator Guide, and the following knowledge base article:
2014-10-07 01:03:17.42 http://support.microfocus.com/kb/kmdoc.php?id=KM1281892
2014-10-07 01:03:17.43
Finished
Cause
Project database is corrupted
Fix
1. Backup of the database schema in ALM 11.52 must be taken and restored with a new name in database
2. The project should be restored in ALM without repository as it might increase the size of the project
3. Project should be exported to qcp file from Site admin
4. Project restored should be deleted
5. Import the project with the qcp file
6. This would create a database schema in database
7. Backup of this database should be done from ALM 11.5 DB and must be restored in ALM 12 with the repository
8. The project should be restored in ALM 12 and verify should work fine now.