17.1 Prerequisites
The following executions must be performed before using the Metadata Report utility:
- Before executing MDB Publish and Data Elements Wrapper Batch, ensure the
following:
- Tablespace Requirement:
- Ensure that the USERS tablespace have a minimum of 150 GB available.
- Ensure that the TEMP tablespace is a minimum of 45 GB available.
- Execute the following Gather Stat command for the mentioned tables:
BEGIN DBMS_STATS.GATHER_TABLE_STATS(USER, 'TABLE_NAME'); END;
- Config Schema:
- AAI_OBJECT_B
- AAI_OBJECT_TL
- AAI_DMT_DEFINITION
- AAI_DMT_DEF_SOURCE_ENTITY
- AAI_DMT_MAPPING_DETAILS
- PR2_RULE_B
- PR2_RULE_MAP
- PR2_RULE_OBJECT
- PR2_RULE_OBJECT_MEMBER
- PR2_OBJECT_TL
- PR2_OBJECT_TRACE
- BATCH_MASTER
- BATCH_TASK_MASTER
- BATCH_PARAMETER_MASTER
- METADATA_MASTER
- METADATA_ELEMENT_MASTER
- METADATA_LOCALE_MASTER
- METADATA_TYPE_MASTER
- METADATA_ATTRIBUTE_MASTER
- AAI_WF_PROCESS_B
- AAI_WF_PROCESS_TL
- AAI_WF_ACTIVITY_B
- AAI_WF_ACTIVITY_TL
- AAI_WF_APPLICATION_API_B
- AAI_WF_APPLICATION_API_TL
- AAI_WF_ACTIVITY_TASK_TL
- AAI_WF_TRANSITION_B
- AAI_WF_TRANSITION_TL
- AAI_WF_ACTIVITY_TASK_USER_MAP
- AAI_WF_ACTUAL_PARAMS
- AAI_WF_ACTIVITY_SUBPROCESS
- AAI_WF_ATTR_COMPONENT
- AAI_WF_ATTR_COMP_VAR_MAPPING
- AAI_WF_PROCESS_DETAIL_FILTER
- AAI_WF_PROCESS_FILTER
- Config Schema:
- Tablespace Requirement:
- MDB Publish: To publish the MDB, follow these steps:
- Log in to Oracle Financial Services Analytical Applications interface with your credentials.
- From the LHS Menu, click Financial Services Data Foundation, and then click Metadata Browser.
- Click the Publish button on the Metadata Browser
screen.
Figure 17-1 Metadata Browser
- Click OK.
- Click the Refresh button to view the latest status.
- After Executing MDB Publish and Data Element Wrapper Batch, ensure the following:
- Execute the following Gather Stat command for the mentioned tables:
BEGIN DBMS_STATS.GATHER_TABLE_STATS(USER, 'TABLE_NAME'); END;
- Atomic Schema:
FSI_DE_RUN_LINEAGE_METADATA
- Atomic Schema:
- Execute the following Gather Stat command for the mentioned tables:
- Logs: MDB logs are generated under deployed area
/Context_Name/logs/MDB_XXXX.log
Data Elements Wrapper Execution: After MDB Publish is completed successfully with the message “Metadata publishing is finished.” in the
/Context_Name/logs/MDB_XXXX.log
, you must execute the Data Elements Utility with the following seeded batch to get the Data Lineage for each Metadata in OFSAA:<INFODOM>_POP_DATA_ELEMENTS_DGS
This execution requires adequate tablespace. Ensure that your Atomic Schema is having enough table space in TEMP and USERS.
- Parameters used in
<INFODOM>_POP_DATA_ELEMENTS_DGS
BatchThe default parameters used in the <INFODOM>_POP_DATA_ELEMENTS_DGS batch are:
Excluding Irrelevant Data Flows from Lineage Reports: For each Run, some of the Data Mappings can be functionally irrelevant. For these cases for any Run, the customer can opt for removing these Data Flow from Lineage Reports as an exclusion by inputting the same in the FSI_DE_RUN_FLOW_REMOVAL table.
Enabling Reports for REPORT Parsing: Every execution for REPORT Parsing requires a minimum of one Report to be enabled in theFSI_DE_POP_REPORT_LIST
table in the Atomic Schema. By default, the following Reports are enabled for US FED Jurisdiction.Table 17-2 Dashboard ID Details
DASHBOARD ID JURISDICTION CODE REPORT CODE INCLUDE REPORT 1 USFED FRY-9C Y 2 USFED FRY-9LP Y 3 USFED FRY-11 Y 4 USFED FRY-11s Y 5 USFED FR-2314 Y 6 USFED FR-2314s Y 7 USFED FFIEC-031 Y 8 USFED FFIEC-041 Y 9 USFED FRY-7N Y 10 USFED FRY-7NS Y By Default All Dashboards are enabled and if you wish to parse particular Dashboards, modify the FSI_DE_POP_REPORT_LIST table in the Atomic Schema by enabling/disabling the “Include Report Column”.
- Parameters used in