Reference for MySQL HeatWave
This guide lists the predefined objects in Resource Analytics for MySQL HeatWave. You can find information about views, entity relationships, subject areas, and sample queries.
Views
This section provides information about views within Resource Analytics MySQL HeatWave and their columns, data types, keys, and the referred view and column names. The following views are available:
| Name | Description |
|---|---|
| MYSQL_BACKUP_DIM_V | This view stores information on full or incremental copies of a DB System which can be used to create a new DB System or recover a DB System. |
| MYSQL_CHANNEL_DIM_V | This view stores information on channels connecting a DB System to an external entity. |
| MYSQL_CONFIGURATION_DIM_V | This view stores information on the set of MySQL variables to be used when deploying a MySQL Database Service DB System. |
| MYSQL_DB_SYSTEM_DIM_V | This view stores information on MySQL DB Systems, which are the core logical unit of the MySQL Database Service. |
| MYSQL_HEATWAVE_CLUSTER_DIM_V | This view stores information on HeatWave clusters, which are the database accelerator for a DB System. |
| MYSQL_REPLICA_DIM_V | This view stores information on DB System read replicas. |
| MYSQL_BACKUP_FACT_V | Fact table for MySQL backups. |
| MYSQL_DB_SYSTEM_FACT_V | Fact table for MySQL DB System database systems. |
| MYSQL_HEATWAVE_CLUSTER_FACT_V | Fact table for MySQL DB Heatwave cluster. |
The suffixes in the view names specify the view type:
- FACT_V: Fact
- DIM_V: Dimension
Relationship Diagram
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: MySQL HeatWave views.
These diagrams show the relationship of the MySQL HeatWave fact views with different dimension views.



Relationships exist among dimensions. Dimensions can be joined directly to each other. These diagrams show the relationship between dimension views.


Sample Queries
Sample queries for MySQL HeatWave.
SELECT
BACKUP.DB_SYSTEM_ID,
BACKUP.BACKUP_SIZE_IN_GBS,
DB_SYSTEM.LIFECYCLE_STATE,
DB_SYSTEM.DISPLAY_NAME,
BACKUP.TIME_CREATED
FROM
OCIRA.MYSQL_BACKUP_FACT_V BACKUP
JOIN
OCIRA.MYSQL_DB_SYSTEM_FACT_V DB_SYSTEM
ON
BACKUP.OCIRA_DB_SYSTEM_KEY = DB_SYSTEM.OCIRA_DB_SYSTEM_KEY
WHERE
DB_SYSTEM.LIFECYCLE_STATE = 'ACTIVE';SELECT
DB_SYSTEM_ID,
DISPLAY_NAME,
ALLOCATED_STORAGE_SIZE_IN_GBS,
SUBNET_ID,
LIFECYCLE_STATE,
TIME_CREATED
FROM
OCIRA.MYSQL_DB_SYSTEM_FACT_V
WHERE
SUBNET_ID = '<YOUR_SUBNET_OCID>' -- replace with the target subnet OCID
AND LIFECYCLE_STATE = 'ACTIVE';SELECT
CLUSTER_ID,
DB_SYSTEM_ID,
CLUSTER_SIZE,
LIFECYCLE_STATE,
TIME_CREATED
FROM
OCIRA.MYSQL_HEATWAVE_CLUSTER_FACT_V
WHERE
LIFECYCLE_STATE = 'ACTIVE';Data Lineage
The Customer Experience Semantic Model Lineage spreadsheet and Metric Calculation Logic spreadsheet for MySQL HeatWave provides an end-to-end data lineage summary report for physical and logical relationships in your data.
For more information, see Data Lineage.
Subject Areas
This section provides information on the subject areas with data you maintain in MySQL HeatWave. 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.