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

Resolving Manual Fix Warnings

Resolving Manual Fix Warnings

You cannot run a script to fix the issues identified in the readiness report with a fix type of
manual
. You do not have to fix the issues identified in the
Manual Warnings
section of the readiness report before you upgrade unless they affect hierarchy manager relationship base objects.
The following check codes identify the data warnings:

Q_100_DEPR

Identifies objects that deprecated tables reference. You can fix Q_100_DEPR issues after the upgrade. These issues appear in the
Repository Manager
validation results until you resolve them.

Q_101_DEPR

Identifies the deprecated lookup and relationship combinations. You can fix Q_101_DEPR issues after the upgrade. These issues appear in the
Repository Manager
validation results until you resolve them.

Q11.5

Identifies child cross-reference records that have a foreign key value that does not exist in the parent cross-reference record. You need to resolve this issue before the upgrade if the issue affects a hierarchy manager relationship base objects. A HM_IND value of
1
in table MI_M_<
timestamp
> identifies a hierarchy manager relationship base object. Hierarchy manager relationship base objects that issue Q11.5 affects might cause the upgrade to fail. Search the latest MI_M_<
timestamp
> temporary data tables for records that issue Q11.5 affects.

Q19.5

Identifies the HMXR tables that contains extra rows. You can resolve Q19.5 issues before or after the upgrade. You need to resolve this issue before the upgrade if the issue affects a hierarchy manager relationship base objects. Hierarchy manager relationship base objects that issue Q19.5 affects might cause the upgrade to fail. If the affected tables are relationship tables and the value in the extra row is not valid, the upgrade process fails. Search the latest MI_R_<
timestamp
> temporary data tables for records that issue Q19.5 affects.

Q5

Identifies the base object records that contain a ROWID_OBJECT value that does not exist in a cross-reference record. Q5 issues do not affect the upgrade process. You can fix Q5 issues before or after the upgrade. Search the latest MI_R_<
timestamp
> temporary data tables for records that issue Q5 affects.

Q9

Identifies the cross-reference records that contain a ROWID_OBJECT value that does not exist in a base object record. You need to resolve this issue before the upgrade if the issue affects a hierarchy manager relationship base objects. Hierarchy manager relationship base objects affected by Q9 might cause the upgrade to fail. Search the latest MI_R_<
timestamp
> temporary data tables for records that issue Q9 affects.

0 COMMENTS

We’d like to hear from you!