1. Analytical Application Infrastructure User Guide
  2. Data Management Framework
  3. DMT Configurations
  4. Performance Optimizations

Performance Optimizations

This feature allows you to externalize the Optimization parameters like Source Hint, Source Prescript, Target Hint, and Target Prescript for OOB metadata definition. Since these parameters are external to the metadata definition, they will not be overridden by OOB metadata during an upgrade, and as a result the customized data will remain intact.
The Optimization parameters can be set from the following windows:
  1. From the Data Mapping window, while creating the Data Mapping definition.
  2. From the DMT Configurations > Optimizations tab, set the optimization parameters in the Performance Parameter Table (AAI_DMT_PERFORMANCE_PARAMS) at following levels:
    • OFSAA_INSTANCE level
    • INFODOM level
    • Definition level
  3. From the Task Definition window, at execution parameter level. For more information, see Component: LOAD DATA section.
    Precedence
    Following is the precedence in the descending order:
    1. Task level square bracket parameters from the Task Definition window
    2. Definition level parameters from DMT Configurations>Optimizations tab
    3. Definition level parameters from the Data Mapping window
    4. INFODOM level parameters from DMT Configurations>Optimizations tab
    5. OFSAA_Instance/setup level parameters from DMT Configurations>Optimizations tab

    Note:

    1. Precedence is at the parameter level and not at the definition level (record level). That is, you can override only the Target Hint from the Optimizations tab, and still use Target Prescript from the Data Mapping Definition.
    2. For the CPP Engine, the OracleDB.conf parameters get fired at first and then the Optimization parameters from the Performance Parameter table (AAI_DMT_PERFORMANCE_PARAMS) get fired.
    3. For the ORACLE database, Prescripts must start with ALTER SESSION and for the HIVE database, Prescripts must start with SET; otherwise, those will be skipped.
    4. Source Hint and Source Prescript are not relevant at Infodom and OFSAA Instance level.

    Figure 7-34 DMT Configurations window - Optimizations


    This image displays the DMT Configurations window - Optimizations.

    The Optimizations tab displays all active Data Mapping definitions available in the setup. Additionally, an entry for OFSAA instance and Information Domain will be also be present. It displays Data Mapping definition details such as Code, Name, Source Prescript, Source Hint, Target Prescript, and Target Hint. You can edit, view and delete performance parameters.