Reference for Full Stack Disaster Recovery

This section provides information about views within Resource Analytics Full Stack Disaster Recovery and their columns, data types, keys, and the referred view and column names. The following views are available:

The suffixes in the view names specify the view type:

• FACT_V: Fact
• DIM_V: Dimension

This section provides diagrams that define the logical relationship of a fact table with different dimension tables.

The contents of each view and their relationships are listed in the following file: Full Stack Disaster Recovery views.

This diagram shows the relationship of the Full Stack Disaster Recovery fact view with different dimension views.

DISASTER_RECOVERY_PLAN_EXECUTION_FACT_V

Sample queries for Full Stack Disaster Recovery.

SELECT
    PE.PLAN_EXECUTION_ID,
    PE.DISPLAY_NAME,
    PE.PLAN_EXECUTION_TYPE,
    PE.LIFECYCLE_STATE,
    PE.EXECUTION_DURATION_IN_SEC,
    PE.TIME_CREATED,
    PL.PLAN_ID,
    PL.DISPLAY_NAME,
    PL.DR_PROTECTION_GROUP_ID,
    PL.PEER_DR_PROTECTION_GROUP_ID,
    PL.PEER_REGION,
    PL.TYPE
FROM
    OCIRA.DISASTER_RECOVERY_PLAN_EXECUTION_FACT_V PE
JOIN
    OCIRA.DISASTER_RECOVERY_PLAN_DIM_V PL
ON
    PE.OCIRA_PLAN_KEY = PL.OCIRA_PLAN_KEY
WHERE
    PE.LIFECYCLE_STATE = 'SUCCEEDED';

The Customer Experience Semantic Model Lineage spreadsheet and Metric Calculation Logic spreadsheet for Full Stack Disaster Recovery provides an end-to-end data lineage summary report for physical and logical relationships in your data.

For more information, see Data Lineage.

This section provides information on the subject areas with data you maintain in Full Stack Disaster Recovery. These subject areas, with their corresponding data, are available for you to use when creating and editing analyses and reports. The information for each subject area includes:

• Description of the subject area.

• Business questions that can be answered by data in the subject area, with a link to more detailed information about each business question.

• Job-specific groups and duty roles that can be used to secure access to the subject area, with a link to more detailed information about each job role and duty role.

• Primary navigation to the work area that's represented by the subject area.

• Time reporting considerations in using the subject area, such as whether the subject area reports historical data or only the current data. Historical reporting refers to reporting on historical transactional data in a subject area. With a few exceptions, all dimensional data are current as of the primary transaction dates or system date.

• The lowest grain of transactional data in a subject area. The lowest transactional data grain decides how data are joined in a report.

• Special considerations, tips, and things to look out for in using the subject area to create analyses and reports.