Skip Headers

Oracle® Argus Mart Administrator's Guide Release 1.0 Part Number E38589-01 |
Home | Book List | Contents | Index | Contact Us

Previous | Next
| View PDF

# 4 Troubleshooting AM

This chapter explains lists some of the error messages that might be displayed while working with AM, the cause for those messages, and the resolution.

The following is the list of error messages:

- MedDRA Mismatch Error

  Error Message:

  You can run the following query using the SQL developer to view the MedDRA mismatch warning message in the etl_mart_log table:

  select * from AM_MART_user.etl_mart_log where table_name = 'p_check_signal_meddra_schema' order by 1 desc;

  The following is the error message:

  Figure 4-1 MedDRA Mismatch Error

  Cause of Error:

  During the ETL process, a check is done between the Argus Safety and the AM database to ensure that they are using the same MedDRA version. This warning message is displayed when these values do not match.

  Resolution:

  You must update the value for the MedDRA version in the SIGNAL_MEDDRA_VER table to ensure that it matches with the Argus Safety database value.

- FR Consistency Log

  Error Message:

  You can run the following query using the SQL developer to view the FR Consistency warning message:

  SELECT enterprise_id, code_list_id, decode_context, code, fr_type, log_message, log_date_time FROM etl_fr_consistency_log ORDER BY enterprise_id, code_list_id

  The following is the error message:

  Figure 4-2 FR Consistency Error

  Cause of Error:

  The display value for a codelist is NULL in the rm_code_list_detail_discrete table in Argus Safety.

  Resolution:

  You must update the value for the codelist in the rm_code_list_detail_discrete table in Argus Safety and re-run the ETL.

- Dictionary Reload Error

  Error Message:

  The following error message is displayed during the ETL process, whenever the dictionary is reloaded in Argus Safety:

  Figure 4-3 Dictionary Reload Error Message

  You can also view this error message by logging on to the SQL Developer as the AM_MART_USER, as shown in the following figure:

  Figure 4-4 Dictionary Reload Error Message: SQL Developer

  Cause of Error:

  Whenever there is a dictionary reload in Argus Safety, some of the required privileges for the Argus Safety user, which you created using the Schema Creation Tool during the Installation Process, are lost.

  Resolution:

  You must give the required privileges to the Argus Safety user. To do so, click the Argus User Creation link on the Schema Creation Tool, select the user that you created during the installation process in the Argus Safety User Creation dialog box, enter the name of the log file and click OK to give the required privileges to the user.

  You can refer to Section 3.5.1, Creating User for the Argus Safety Database, for more information.

- ETL Execution Pre-Requisite Check Failed Error

  Error Message:

  There are some Pre-requisite checks that you must do before the execution of the ETL. The following is the error message, which is displayed if any of the Pre-requisites checks are not done:

  Figure 4-5 Pre-Requisite Check Failed Error

  Cause of Error:

  The following are the possible causes of this error message:

  - If you are trying to run the Initial ETL on a database again without executing the Re-initial script.

  - If you are trying to execute the Incremental ETL prior to the Initial ETL.

  - If you have not configured the First Human Language Profile Switch using the Argus Safety console for the enterprises configured in AM. You must not leave the value for the First Human Language Profile Switch, as Blank.

  - If the previous instance of the ETL is still not complete for the Load Plan.

  Resolution:

  To resolve this error message, you must:

  - Ensure that you run the Initial ETL on a database again only if you have already executed the Re-initial script. For more information on Re-initial script, refer to Re-initializing the ETL Process.

  - If you are trying to run the Incremental ETL on a database, ensure that the Initial ETL has already been executed on it.

  - Ensure that you have not left the value for the First Human Language Profile Switch for the enterprises configured in AM, as Blank.

  - Ensure that the Previous Instance of the ETL process is complete. You can either resume the ETL process if it is in Stopped state, or you can execute the re-initial script on the database and restart the ETL process from the first step.

    You can refer to Chapter 7 of the Installation Guide for information on resuming or restarting the ETL process.

- Multiple Enterprise Creation Validation Messages

  The following is the list of validation messages that are displayed while creating multiple enterprises in AM.

  Error Message:

  Given Source enterprise does not exist in Mart. Close the window and run application again.

  Cause of Error:

  While creating multiple enterprises in AM, you must enter an enterprise name which can be used as a template to create other enterprises. This enterprise is referred to as the Source Enterprise.

  If the name of the Source Enterprise that you have entered while creating multiple enterprises does not exist in AM, this validation message is displayed.

  Resolution:

  The name of the Source Enterprise that you enter while creating multiple enterprises must exist in AM.

  Error Message:

  From the list provided, no enterprise exists in Argus Safety. Close the window and run application again.

  Cause of Error:

  The name of the enterprises that you enter while creating multiple enterprises in AM must also exist in the Argus Safety database.

  If these enterprise names do not exist in Argus Safety, this validation message is displayed.

  Resolution:

  You must ensure that the name of the enterprises that you enter while creating multiple enterprises in AM exist in the Argus Safety database.

  Error Message:

  From the list provided, no enterprise is valid for configuration in Mart. Close the window and run application again.

  Cause of Error:

  This validation message is displayed if all the enterprise names that you have entered on the Multiple Enterprise Creation screen already exist in the AM database.

  Resolution:

  You must ensure that the enterprise names that you want to create in AM using the Multiple Enterprise Creation screen do not already exist in AM.

- SMQ-CMQ Loop Error Message

  Error Message:

  Error in p_set_Child_Record while processing term code self referencing parent child relationship leading to an infinite loop

  Cause of Error:

  There is an SMQ, which is a Parent in the hierarchy, and has also been referenced as a Child in the hierarchy. This is termed as the Self Referencing Parent Child relationship, which leads to an infinite loop.

  Resolution:

  You must ensure that an SMQ, which serves as a Parent in the hierarchy, must not also be present as a Child in the hierarchy.