QC10->QC11 Project Upgrade throws Oracle Index errors
| ♥ 0 |
We are migrating a project and upgrading from QC10 to QC11 and on a different Oracle instance. We were able to do the Oracle "original" export to DMP file, created our Schema-User and imported using IMP to get the Schema to the new Oracle instance. then after copying the projects QC10 repository and editing the DBID.xml file we successfully restored the project in the QC11 site administrator. When we do a Repair, we get these "index" errors, why? 14:58:11 Data repair starts 14:58:11 Repair duplicate IDs … 14:58:11 Repair duplicate values … 14:58:11 Repair sequence values … 14:58:11 Repair trees … 14:58:11 Exception occurred. 14:58:11 Error: Failed SQL: /* ~~QC */ UPDATE ANALYSIS_ITEM_FOLDERS SET AIF_PATH= WHERE AIF_ID= [Mercury][Oracle JDBC Driver][Oracle]ORA-01502: index … 14:58:11 ‘DEFAULT_myProject_TEMPLATE_DB.ANALYSIS_ITEM_FOLDERS_UIX2’ or partition of such index is in unusable state 14:58:11 Stack: com.mercury.optane.core.db.CAbsStatement.createSQLExceptionWithSQLStatement(CAbsStatement.java:214) 14:58:11 Stack: com.mercury.optane.core.db.CAbsStatement.doExecute(CAbsStatement.java:197) 14:58:11 Stack: com.mercury.optane.core.db.CAbsStatement.doExecute(CAbsStatement.java:133) 14:58:11 Stack: com.mercury.optane.core.db.CTdPreparedStatement.executeBatchCode(CTdPreparedStatement.java:1055) 14:58:11 Stack: com.mercury.optane.core.db.CTdPreparedStatement.executeBatch(CTdPreparedStatement.java:1043) 14:58:11 Stack: com.mercury.td.saserver.maintenance.repair.AnalysisFolderRepairer.executeBatch(AnalysisFolderRepairer.java:321) 14:58:11 Stack: com.mercury.td.saserver.maintenance.repair.AnalysisFolderRepairer.run(AnalysisFolderRepairer.java:165) Server exception. Process stopped 14:58:11 Exception occurred. Finished
Marked as spam
|
Posted by |
Private answer
Bill, Since you had Text Search (CTX) enabled on your old ORACLE instance, you should have it enabled on your new one. After that, have the DBA enable Text Search on the new ORACLE instance. The newly migrated project Schema still has bad/corrupt indexes related to text Search. the DBA should run these index and trigger ''drops'' against that Schema (in SQLPlus): DROP INDEX BG_TEXT_IDX; DROP INDEX CO_TEXT_IDX; DROP INDEX CS_TEXT_IDX; DROP INDEX DS_TEXT_IDX; DROP INDEX RQ_TEXT_IDX; DROP INDEX TS_TEXT_IDX; DROP TRIGGER BG_TEXT_SYNC_TRG; DROP TRIGGER CO_TEXT_SYNC_TRG; DROP TRIGGER CS_TEXT_SYNC_TRG; DROP TRIGGER DS_TEXT_SYNC_TRG; DROP TRIGGER RQ_TEXT_SYNC_TRG; DROP TRIGGER TS_TEXT_SYNC_TRG; Then, restore the project as you did earlier. Before you do ''Repair'', the ''Enable/Rebuild Text Search'' button should be active in the Project Details tab - run it. If Text search doesn't run for some reason, try running it after repair. Now Repair and Upgrade the project. Marked as spam
 Posted by pt-barnum (Questions: 4, Answers: 509) Answered on March 12, 2013 8:15 pm
|