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. Troubleshooting the Upgrade Process
  16. Frequently Asked Questions
  17. Processing Existing ActiveVOS Tasks
  18. 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 Mandatory Fix Data Issues

Resolving Manual Mandatory Fix Data Issues

You cannot run a script to fix the issues with a fix type of
manual
. You must resolve the issues identified in the
Manual Mandatory Fix
section of the readiness report before you upgrade. Contact Informatica Global Customer Support if you need assistance to resolve these issues.
The following check codes identify the data issues that you must fix manually:

Q_DSI

The existing column names that conflict with the column names introduced by the upgrade must be changed before you upgrade. Rename any existing column names that conflict with the following column names:
  • STG_ROWID_TABLE column name in the cross-reference tables
  • The S_, S__, and S_S_ prefix for column names in the cross-reference tables
  • _GOV postfix for column names in the cross-reference tables
  • ORIG_ROWID_OBJECT column name in the cross-reference tables

XREF_CUC_DUPL

Multiple cross-reference records cannot share the same custom unique key value. These issues do not affect the upgrade process.
Do not fix cross-reference records that are a result of an edit. Cross-reference records that are the result of an edit have a source of
SYS0
and a Put_Update_Merge_Ind value of
1
.
  1. Search the latest MI_I_<
    timestamp
    > temporary data tables identified in the readiness report for records affected by issue XREF_CUC_DUPL.
  2. See the SQL code samples in the MI_SQL_SAMPLES table for samples of the SQL code that the readiness script uses to identify XREF_CUC_DUPL issues.
  3. Ensure multiple cross-reference records do not share the same custom unique key value.

Q_HM_NULL

Identifies the relationship base objects and the hierarchy manager columns that have NULL values. Q_HM_NULL issues have a fix type of
auto
, but you must manually fix any Q_HM_NULL issues that remain after you run the
readiness_start.sql
script to fix issues.
  1. Search the latest detailed temporary data tables identified in the readiness report for records affected by issue Q_HM_NULL.
  2. Enter the correct data for the records affected by issue Q_HM_NULL.

0 COMMENTS

We’d like to hear from you!