3 Argus Mart Internal Switches

There are certain Common Profile Switches that cannot be configured using the Argus Safety Console. These switches are referred to as Internal Profile Switches in this document.

Oracle Recommends:

You must not change the values set for these Profile Switches without consulting Oracle.

This chapter comprises the following sub-sections:

3.1 Global Switches

The following are the Global Internal Common Profile Switches for Argus Mart that belong to the RM_CMN_PROFILE_GLOBAL table:

3.1.1 AM_APP_OWNER

Section Database
Key AM_APP_OWNER
Default Value &sm_app.
Description Defines Argus application schema name.

3.1.2 AM_BI_OWNER

Section Database
Key AM_BI_OWNER
Default Value &bi_user.
Description Defines BI schema name.

3.1.3 AM_DDL_VER

Section Database
Key AM_DDL_VER
Default Value 8.1.1
Description Defines the currently installed version of Argus Mart.

3.1.4 AM_ETL_OWNER

Section Database
Key AM_ETL_OWNER
Description Defines Argus Mart user who has administrator rights to process an ETL.

3.1.5 AM_LAST_DDL_VER

Section Database
Key AM_LAST_DDL_VER
Description This switch represents the previously installed version of Argus Mart.

During fresh installation the value of this switch is same as AM_DDL_VER.


3.1.6 AM_MART_OWNER

Section Database
Key AM_MART_OWNER
Description Defines the Argus Mart schema name.

3.1.7 AM_STAGE_OWNER

Section Database
Key AM_STAGE_OWNER
Description Defines the Argus Staging schema name.

3.1.8 APPLICATION_TYPE

Section Database
Key APPLICATION_TYPE
Description Defines the type of installation for Argus Mart.

0 represents Single-tenant installation

1 represents Multi-tenant installation


3.1.9 DEFAULT_ENTERPRISE

Section System
Key DEFAULT_ENTERPRISE
Description Defines the default enterprise ID for Argus Mart.

3.1.10 DEFAULT_SECURITY_ACCESS

Section Database
Key DEFAULT_SECURITY_ACCESS
Default Value 0
Description Specifies the default security access level for APP user of Argus Mart.

3.1.11 ETL_COMPUTE_MART_USER_STATISTICS

Section Database
Key ETL_COMPUTE_MART_USER_STATISTICS
Default Value 1
Description This switch is used to control the Mart Schema Tables Statistics gathering.

0 represents Do Not Gather Statistics

1 represents Gather Statistics


3.1.12 ETL_COMPUTE_STAGE_USER_STATISTICS

Section Database
Key ETL_COMPUTE_STAGE_USER_STATISTICS
Default Value 1
Description This switch is used to control the Stage Schema Tables Statistics gathering.

0 represents Do Not Gather Statistics

1 represents Gather Statistics


3.1.13 ETL_FR_CONSISTENCY_CHECK

Section Database
Key ETL_FR_CONSISTENCY_CHECK
Default Value 1
Description This switch is used to enable or disable consistency check of code list data during Incremental ETL run.

0 represents Disable consistency check

1 represents Enable consistency check


3.1.14 ETL_PROCESS_FR_REF_DATA

Section Database
Key ETL_PROCESS_FR_REF_DATA
Default Value 1
Description This switch is used to enable or disable processing of cases impacted due to a change in code list data during Incremental ETL run.

0 represents Disable

1 represents Enable


3.1.15 ETL_PROCESS_LM_CFG_REF_DATA

Section Database
Key ETL_PROCESS_LM_CFG_REF_DATA
Default Value 1
Description This switch is used to enable or disable processing of cases impacted due to a change in LM/CFG data during Incremental ETL run.

0 represents Disable

1 represents Enable


3.1.16 ETL_PROCESS_SMQ_CMQ_REF_DATA

Section Database
Key ETL_PROCESS_SMQ_CMQ_REF_DATA
Default Value 1
Description This switch is used to enable or disable processing of cases impacted due to a change in SMQ/CMQ data during Incremental ETL run.

0 represents Disable

1 represents Enable


3.1.17 ETL_SM_ITERATION_NUMBER

Section Database
Key ETL_SM_ITERATION_NUMBER
Default Value NULL
Description This switch represents the SM Iteration Number during ETL execution.

3.1.18 ETL_STATS_CASCADE_OPTION

Section Database
Key ETL_STATS_CASCADE_OPTION
Default Value TRUE (Statistics should be gathered for all indexes on the table currently being analyzed)
Description This switch is used to define CASCADE parameter for DBMS_STATS, while gathering statistics of Stage and Mart Schema.

3.1.19 ETL_STATS_ESTIMATE_PERCENT

Section Database
Key ETL_STATS_ESTIMATE_PERCENT
Default Value 1
Description This switch is used to define ESTIMATE_PERCENT parameter for DBMS_STATS, while gathering statistics of Stage and Mart Schema.

3.1.20 ETL_STATS_METHOD_OPT

Section Database
Key ETL_STATS_METHOD_OPT
Default Value FOR ALL COLUMNS SIZE AUTO
Description This switch is used to define METHOD_OPT parameter for DBMS_STATS, while gathering statistics of Stage and Mart Schema.

3.1.21 ETL_STATS_PARALLEL_DEGREE

Section Database
Key ETL_STATS_PARALLEL_DEGREE
Default Value NULL
Description This switch is used to define DEGREE of Parallelism for DBMS_STATS, while gathering statistics of Stage and Mart Schema.

3.1.22 ETL_STATUS

Section Database
Key ETL_STATUS
Default Value 0
Description This switch represents the current status of ETL.

0 represents No ETL is executed

-1 represents Initial ETL is running

1 represents Initial ETL is completed

-2 represents Incremental ETL is running

2 represents Incremental ETL is completed


3.1.23 GMT_OFFSET

Section Database
Key GMT_OFFSET
Default Value NULL
Description This switch, which is updated by Mart ETL, stores the GMT Offset Value based on Argus Safety Setup.

3.1.24 LOG_ETL_SQL

Section Database
Key LOG_ETL_SQL
Default Value 0
Description This switch is used to enable or disable logging of dynamic SQL queries generated during ETL execution.

0 represents Do not log Queries

1 represents Log Queries


3.1.25 MEMORY_MODEL

Section Database
Key MEMORY_MODEL
Default Value 1
Description This switch is internally used by Schema Creation Tool.

(For Oracle internal use only.)


3.1.26 ODI_ETL_STATUS

Section Database
Key ODI_ETL_STATUS
Default Value 0
Description This switch is used to prevent parallel ETL executions. The default value of the switch is 0 and is updated as 1 during ETL execution. This value is reset to 0 on successful completion of ETL.

3.1.27 RLS_OWNER

Section Database
Key RLS_OWNER
Description Defines the Argus Mart Virtual Private Database (VPD) schema name.

3.1.28 SAFETY_DDL_VER

Section Database
Key SAFETY_DDL_VER
Description Specifies the current version of Argus Safety.

3.2 Enterprise-specific Switches

The following are the Enterprise-specific Internal Common Profile Switches for Argus Mart that belong to the RM_CMN_PROFILE_ENTERPRISE table:

3.2.1 START DATE OF CURRENT DATA SUPPORT

Section Database
Key START_DATE_CURRENT_DATA_SUPPORT
Default Value Blank
Description FOR FUTURE USE—When the system is first instantiated, this switch represents the minimum EFFECTIVE_START_DATE of the Case Revisions processed by the Initial ETL for each enterprise. Later (in future releases), after archiving or cleaning up of revisions, this value can be set to a later date.

3.2.2 START DATE OF LOCKED REVISION SUPPORT

Section Database
Key START_DATE_LOCKED_REVISION_SUPPORT
Default Value Blank
Description FOR FUTURE USE—When the system is first instantiated, this switch represents the minimum EFFECTIVE_START_DATE of the Case Revisions processed by the Initial ETL for each enterprise. Later (in future releases), after archiving or cleaning up of revisions, this value can be set to a later date. In this release, this date is same as Start Date of Current Data Support.

3.2.3 LATEST DATE FOR CURRENT DATA AND LOCKED REVISION SUPPORT

Section Database
Key LATEST_DATE_CURRENT_LOCKED_REV_SUPPORT
Default Value Blank
Description This switch represents the Maximum EFFECTIVE_START_DATE of the Case Revisions processed by the Initial/Incremental ETL for each enterprise. If the ETL does not update any case, this date must not change. This value must be updated as the last step of a successful ETL. It must not be updated if the ETL fails due to an error.

3.2.4 LAST ETL COMPLETION DATE

Section Database
Key LAST_ETL_COMPLETION_DATE
Default Value Blank
Description This switch represents the date and time (sysdate of Argus Mart database) of the last successfully completed ETL for each enterprise. The last successfully completed ETL must be updated, even if the ETL does not update any case. It must be maintained for administrative purpose only and must not be used for any as-of query.