Upgrading from Version 9.0.1 or 9.1.0 for Oracle

10.3 HotFix 1

Back Next

Readiness Report Check Codes

The readiness reports organizes the data issues by check code. Each check code corresponds with a specific data issue. Check codes can have a fix type of

auto

manual

The following table outlines the possible issues that the readiness report identifies:

Check Code	Description	Fix Type
Q0	Multiple ROWID_XREFs have the same HMXR.SRC_ROWID_OBJECT value. The SRC_ROWID_OBJECT column provides the original ROWID_OBJECT value for the XREF.ORIG_ROWID_OBJECT column. Each cross-reference table must have unique values in the ORIG_ROWID_OBJECT column.	Auto
Q19 and Q19_2	The HMXR table lineage exists for cross-reference records but this lineage represents the same ORIG_ROWID_OBJECT value for multiple cross-reference records.	Auto
Q2_9, Q2_9_DR, Q2_9_M, and Q2_9_U	Merged cross-reference records have no lineage in the HMXR table. Duplicate ORIG_ROWID_OBJECT values exist for multiple cross-reference records.	Auto
Q2_inc	Merged records do not have lineage in the HMXR table. The value of HMXR.TGT_ROWID_OBJECT does not equal the value of XREF.ROWID_OBJECT. Duplicate records exist because of the history data and cross-reference data is not consistent.	Auto
Q3_E	Merged records do not have lineage in the HMXR table. The XREF.PUT_UPDATE_MERGE value is 1. Duplicate records exist. The value of XREF.ROWID_OBJECT does not match HMXR.TGT_ROWID_OBJECT.	Auto
Q10	The base object record foreign key and the cross-reference record foreign key are not consistent. The foreign keys have a valid relationship to the parent record.	TBD
Q10.CBN	The base object foreign key and the cross-reference record foreign key are not consistent. The base object foreign key does not have a valid relationship to the parent cross-reference record.	TBD
Q10.PBN	The base object foreign key and cross-reference record foreign key are not consistent. The cross-reference foreign key does not have a valid relationship to the parent base object.	TBD
Q10.NE	The base object foreign key and cross-reference record foreign key are not consistent. The foreign keys have relationships to different parent base objects.	TBD
Q11	The base object foreign key and cross-reference record foreign key are not consistent. The child base object has a valid relationship to the parent cross-reference record and the parent base object record.	TBD
Q11.NE	The base object foreign key and cross-reference record foreign key are not consistent. The child base object has a valid relationship to the parent cross-reference record but not to the parent base object record.	TBD
Q_HFKM_DUPL	The lineage of a cross-reference table ROWID_XREF value is tracked multiple times in the HFKM table.	Auto
Q_HFKM_RMP	The HFKM table lineage of the foreign key is not correct. The value of HFKM.AFFECTED_TGT_VALUE does not equal the value of the child cross-reference foreign key.	Auto
Q_HM_NULL	Some Hierarchy Manager columns for a relationship base object have NULL values. If you still have columns with this error after you run the readiness_start.sql script to fix data issues, you must fix these columns manually because there is not enough information for the script to assign values to these columns. Some relationship base objects have NULL values for one or more of the following Hierarchy Manager columns: Entity base object 1 Entity base object 2 Hierarchy foreign key column - type CODE Rel type foreign key column - type CODE	Auto
XREF_CUC_DUPL	A custom unique column has duplicate values in multiple base object records at the cross-reference level. Cross-reference records that belong to multiple base object records cannot share the same custom unique column value.	Manual
Q_DSI	Column names in the database conflict with temporary columns or permanent columns that the migration process introduces.	Manual
Q100_DEPR	The schema has objects that have dependencies on deprecated tables and deprecated sequences. The following relationships and lookup definitions are deprecated: A relationship on a custom unique field and a lookup on a custom unique field that is not in the same relationship. A relationship on a custom unique field and a lookup on ROWID_OBJECT. To use objects with issue Q100_DUP after you upgrade, you must resolve the dependencies.	Manual
Q101_DEPR	The customer schema has objects that have deprecated lookup and relationship combinations.	Manual
Q11.5	The foreign key in a child cross-reference record does not exist in the parent cross-reference record.	Manual
Q19.5	The HMXR table has more than the expected number of records. The extra records likely have values that are not valid.	Manual
Q5	A ROWID_OBJECT value exists in a base object record that does not exist in a cross-reference record.	Manual
Q9	A ROWID_OBJECT value exists in a cross-reference that does not exist in a base object record.	Manual