Table of Contents

Search

  1. Preface
  2. Upgrade Overview
  3. Pre-Upgrade Tasks
  4. Database Tasks
  5. Application Server Tasks
  6. Hub Store Upgrade
  7. Hub Server Upgrade (In-place Upgrade)
  8. Process Server Upgrade (In-place Upgrade)
  9. Resource Kit Upgrade (In-place Upgrade)
  10. Post-Upgrade Tasks
  11. Search Configuration Upgrade
  12. ActiveVOS Post-Installation Tasks for the Application Server
  13. ActiveVOS Post-Upgrade Tasks for Business Entity Adapter
  14. ActiveVOS Post-Upgrade Tasks for Subject Areas Adapter
  15. Appendix A: Troubleshooting the Upgrade Process
  16. Appendix B: Frequently Asked Questions
  17. Appendix C: Processing Existing ActiveVOS Tasks
  18. Appendix D: Configuring Metadata Caching

Upgrading from Version 9.0.1 or 9.1.0 for Oracle

Upgrading from Version 9.0.1 or 9.1.0 for Oracle

Temporary Data Tables

Temporary Data Tables

The temporary data tables register issues that the readiness report identifies. The
readiness_start.sql
script creates the temporary tables each time you check the data or fix the data.
The script generates the following temporary tables when it creates the readiness report:
MI_D_<
timestamp
>
Contains registered data for issues related to duplicate ORIG_ROWID_OBJECT values in the cross-reference records and issues related to check code Q_HM_NULL. To fix these issues, run the
readiness_start.sql
script.
MI_F_<
timestamp
>
Contains registered data for issues related to check codes Q_HFKM_RMP and Q_HFKM_DUP. To fix these issues, run the
readiness_start.sql
script.
MI_I_<
timestamp
>
Contains registered data for issues related to check codes Q100_DEPR, Q101_DEPR, XREF_CUC_DUPL, and Q_DSI. To fix these issues, run the
readiness_start.sql
script.
MI_M_<
timestamp
>
Contains registered data for issues related to check code Q11.5. Fix these issues manually.
MI_R_<
timestamp
>
Contains registered data for issues related to check codes Q19.5, Q9, and Q5. Fix these issues manually.
MI_REPORT
Contains the data for the latest readiness report.
MI_FIX_IS_DONE
Contains information that is used by the
readiness_start.sql
. You can ignore this table.
MI_SQL_SAMPLES
Contains samples of the SQL code that the readiness script uses to identify issues, such as XREF_CUC_DUPL. You can modify these scripts to remove null values.

0 COMMENTS

We’d like to hear from you!