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
.
Search the latest MI_I_<
timestamp
> temporary data tables identified in the readiness report for records affected by issue XREF_CUC_DUPL.
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.
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.
Search the latest detailed temporary data tables identified in the readiness report for records affected by issue Q_HM_NULL.
Enter the correct data for the records affected by issue Q_HM_NULL.