Data Loading Errors (RULE_ID_RFRNCED_COL_INVALID, RULE_ID_STD_CD_VALDTN_FAILED, RULE_ID_HIERARCHY_NOT_RESOLVED_IN_HDM, RULE_ID_INVALID_HIERARCHY) after Upgrading OHADI 2.0 to OHADI 3.0 (Doc ID 2092300.1)

Last updated on FEBRUARY 04, 2016

Applies to:

Oracle Healthcare Analytics Data Integration - Version 2.0.0 to 3.1 [Release 2.0.0 to 3.1]
Information in this document applies to any platform.

Symptoms

After upgrade, on the first execution of INITIAL_LOAD ETL Plan, containing Repository, Patient and first portions of INTVN and SRVY, the following exceptions can occur:

- RULE_ID_RFRNCED_COL_INVALID - Exception occurred due to non resolution of foreign key in HDM~(various_HDM_tables.various_IDs)

- RULE_ID_STD_CD_VALDTN_FAILED - Standardized Code is not associated with the specified code type(s)

- RULE_ID_HIERARCHY_NOT_RESOLVED_IN_HDM - Exception occurred because either for the valid code hierarchy, code should be resolved in HDM_CD_REPOSITORY OR for a valid party hierarchy, party should be resolved in HDM_PRTY

- RULE_ID_INVALID_HIERARCHY - Exception occurred because the hierarchy should be either code hierarchy or party hierarchy AND in case of party hierarchy, at most one party should be provided

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms