11/13

6 Troubleshooting

This section discusses seed data troubleshooting.

6.1 Seed Data Procedure Parameter

Overwrite Flag

The overwrite flag, which is a parameter that is specified when running the seed data procedure can have two possible values Y and N:

• Y - When the seed data procedure is run with the parameter set to Y, it overwrites the existing non-Oracle seed data records in case of conflicts with Oracle provided seed data records. However, non conflicting records remain unaffected. The parameter does not let you selectively overwrite records. Depending on the error type, conflicts or errors can be logged in the error log table.

• N - When the seed data procedure is run with the parameter set to N, conflicts or errors are logged in the error log table which can then be reviewed. Selecting this parameter will not overwrite any customization or addition that you have made to seed data.

For more information on error logging, see Section 6.2.

6.2 Error Logging and Debugging

The errors that occur while populating seed data using seed data load procedures are logged inside the table HDM_X_SEED_DATA_ERR_LOG for HDWF and HDI_X_SEED_DATA_ERR_LOG for HDWF interface table.

The following are the key columns in the error log table (HDM_X_SEED_DATA_ERR_LOG or HDI_X_SEED_DATA_ERR_LOG):

• ERR_ID - Unique identifier for a record in the error log table.

• ERR_TBL_NM - Specifies the table name for which the error record is logged. For example, for an error in the HDM code repository will have a value HDM_CD_REPOSITORY in this column.

• ERR_TYP - Indicates the type of error that is logged. There are five types of errors that can be logged. For the different types of errors, see Seed Data Error Types.

• ERR_DESC - A short description of the error.

• ERR_INT_ID - Indicates the integration ID of the record for which the error is logged. This column along with the error table name (ERR_TBL_NM) can be used to debug the error. Integration ID for tables that are populated with seed data have the following pattern:

  Table 6-1 Pattern for Integration ID for Tables that are Populated with Seed Data

  Table Name	Columns to be Concatenated to Generate the Integration ID
  HDM_USER	LOGIN
  HDM_CD_SYS	SYS_CD~SYS_VERSION
  HDM_CD_REPOSITORY	CD~SYS_CD~SYS_VERSION
  HDM_CD_TYP	TYP_CD
  HDM_CD_REPOSITORY_CD_TYP	CD~SYS_CD~ SYS_VERSION~ TYP_CD

  
  

Seed Data Error Types

The following section describes the different error types that can be logged and the approach to understand and resolve them:

Note:

In the following section, Non-EHA user refers to individuals using the application.

• EHA_WARNING: Code name exists

• EHA_ERROR: Insert failed: Creation of version failed

• EHA_ERROR: Update failed

• EHA_ERROR: Insert failed: Duplicate integration ID

• PL/SQL_ERROR

Error Type

EHA_WARNING: Code name exists

Error Description

Code name: <CODE NAME> exists. New Oracle seed data record inserted with same code name.

Resolution for HDM

Identification

Search Code Repository for the record having the code name specified in the Error Description.

select *from HDM_CD_REPOSITORY WHERE CD_NM=<CODE NAME SPECIFIED IN THE ERROR STATEMENT>;

For example,

SQL> select *from HDM_CD_REPOSITORY WHERE CD_NM ='Patient Withdrew';

Resolution

After identifying the code name, you can select one of the following options:

• FORCE UPDATE: Delete the conflicting seed data record that you have inserted along with the one inserted by the Oracle seed data procedure. Then, run the seed data procedure again with the overwrite flag set to Y.

• SELECTIVE UPDATE: Delete the conflicting seed data record inserted by the Oracle seed data procedure and use your own seed data.

• Delete the seed data record that you have inserted which caused the code clash and instead use the Oracle seed data record.

Resolution for HDI

Identification

Search Code Repository for the record having the code name as specified in the error description.

select *from HDI_CD_REPOSITORY WHERE CD_NM=<CODE NAME SPECIFIED IN THE ERROR STATEMENT>;

For example,

SQL> select *from HDI_CD_REPOSITORY WHERE CD_NM ='Patient Withdrew';

Resolution

After identifying the code name, you can select one of the following options:

• FORCE UPDATE: Delete the conflicting seed data record that you have inserted along with the one inserted by the Oracle seed data procedure. Then, run the seed data procedure again with the overwrite flag set to Y.

• SELECTIVE UPDATE: Delete the conflicting seed data record inserted by the Oracle seed data procedure and use your own seed data.

• Delete the seed data record that you have inserted which caused the code clash and instead use the Oracle seed data record.

Error Type

EHA_ERROR: Insert failed: Creation of version failed

Error Description

Non-EHA user has versioned a record. Unable to create a new version of the record.

Resolution for HDM

Identification

Navigate to the table identified in HDM_X_SEED_DATA_ERR_LOG.ERR_TBL_NM and use HDM_X_SEED_DATA_ERR_LOG.ERR_INT_ID to identify the error record.

Select *from <HDM_X_SEED_DATA_ERR_LOG.ERR_TBL_NM> WHERE INTEGRATION_ID=<HDM_X_SEED_DATA_ERR_LOG.ERR_INT_ID> AND CURRENT_FLG='Y';

For example,

SQL> select *from HDM_CD_REPOSITORY where INTEGRATION_ID ='SPCMN_TYP_CD_IVFEHA_CUSTOM_CD_SYS1.0' and CURRENT_FLG='Y';

Resolution:

After identifying the code name, you can choose one of the following options:

• DO NOTHING: Ignore the Oracle provided seed data.

• Run the procedure with overwrite flag = Y to overwrite all conflicting seed data with Oracle seed data.

Resolution for HDI

Identification

Navigate to the table identified in HDI_X_SEED_DATA_ERR_LOG.ERR_TBL_NM and use HDI_X_SEED_DATA_ERR_LOG.ERR_INT_ID to identify the error record.

Select *from <HDI_X_SEED_DATA_ERR_LOG.ERR_TBL_NM> t1 WHERE INT_ID=<HDI_X_SEED_DATA_ERR_LOG.ERR_INT_ID> AND SRC_CHANGED_ON_DT=(select max(SRC_CHANGED_ON_DT) from <HDI_X_SEED_DATA_ERR_LOG.ERR_TBL_NM> t2 where t1.int_id =t2.int_id);

For example,

SQL> select *from HDI_CD_REPOSITORY cr1 where INT_ID ='SPCMN_TYP_CD_IVFEHA_CUSTOM_CD_SYS1.0' and SRC_CHANGED_ON_DT =(select max(SRC_CHANGED_ON_DT) from HDI_CD_REPOSITORY cr2 where cr1.int_id =cr2.int_id);

Resolution

After identifying the code name, you can choose one of the following options:

• DO NOTHING: Ignore the Oracle provided seed data.

• Run the procedure with overwrite flag = Y to overwrite all conflicting seed data with Oracle seed data.

Error Type

EHA_ERROR: Update failed

Error Description

Non-EHA user has changed the record. Unable to update the record.

Resolution for HDM

Identification

Navigate to the table identified in HDM_X_SEED_DATA_ERR_LOG.ERR_TBL_NM and use HDM_X_SEED_DATA_ERR_LOG.ERR_INT_ID to identify the error record.

Select *from <HDM_X_SEED_DATA_ERR_LOG.ERR_TBL_NM> WHERE INTEGRATION_ID=<HDM_X_SEED_DATA_ERR_LOG.ERR_INT_ID> AND CURRENT_FLG='Y';

For example,

SQL> select *from HDM_CD_REPOSITORY where INTEGRATION_ID ='SPCMN_TYP_CD_IVFEHA_CUSTOM_CD_SYS1.0' and CURRENT_FLG='Y';

Resolution

After identifying the code name, you can choose one of the following options:

• DO NOTHING: Ignore the Oracle provided seed data.

• Run the procedure with overwrite flag = Y to overwrite all conflicting seed data with Oracle seed data.

Resolution for HDI

This error does not occur in HDI as no updates are supported in HDI.

Error Type

EHA_ERROR: Insert failed: Duplicate integration ID

Error Description

Non-EHA user has created a record with the same integration ID. Unable to create a new record.

Resolution for HDM

Identification

Navigate to the table identified in HDM_X_SEED_DATA_ERR_LOG.ERR_TBL_NM and use HDM_X_SEED_DATA_ERR_LOG.ERR_INT_ID to identify the error record.

Select *from <HDM_X_SEED_DATA_ERR_LOG.ERR_TBL_NM> WHERE INTEGRATION_ID=<HDM_X_SEED_DATA_ERR_LOG.ERR_INT_ID> AND CURRENT_FLG='Y' ;

For example,

SQL> select *from HDM_CD_REPOSITORY where INTEGRATION_ID ='SPCMN_TYP_CD_IVFEHA_CUSTOM_CD_SYS1.0' and CURRENT_FLG='Y ';

Resolution

To insert Oracle seed data, modify the integration ID of the conflicting record that you have inserted and run the seed data procedure again.

Resolution for HDI

Identification

Navigate to the table identified in HDI_X_SEED_DATA_ERR_LOG.ERR_TBL_NM and use HDI_X_SEED_DATA_ERR_LOG.ERR_INT_ID to identify the error record.

Select *from <HDI_X_SEED_DATA_ERR_LOG.ERR_TBL_NM> t1 WHERE INT_ID=<HDI_X_SEED_DATA_ERR_LOG.ERR_INT_ID> AND SRC_CHANGED_ON_DT=(select max(SRC_CHANGED_ON_DT) from <HDI_X_SEED_DATA_ERR_LOG.ERR_TBL_NM> t2 where t1.int_id =t2.int_id) ;

For example,

SQL> select *from HDI_CD_REPOSITORY cr1 where INT_ID ='SPCMN_TYP_CD_IVFEHA_CUSTOM_CD_SYS1.0' and SRC_CHANGED_ON_DT =(select max(SRC_CHANGED_ON_DT) from HDI_CD_REPOSITORY cr2 where cr1.int_id =cr2.int_id) ;

Resolution

To insert Oracle seed data, modify the integration ID of the conflicting record that you have inserted and run the seed data procedure again.

Error Type

PL/SQL_ERROR

Resolution for HDM

Other PL SQL errors that are encountered when inserting seed data.

Resolution for HDI

Other PL SQL errors that are encountered when inserting seed data.