Reference for OCI Cache

This guide lists the predefined objects in Resource Analytics for Oracle OCI Cache. You can find information about views, entity relationships, subject areas, and sample queries.

Views

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

OCI Cache Views
NameDescription
OCI_CACHE_CONFIG_SET_DIM_VThis view stores information on the configurations for OCI Cache to manage the behavior, performance, and functionality of the underlying cache engine.
OCI_CACHE_CONFIG_SET_INFO_DIM_VThis view stores information on a configuration setting in the OCI Cache Config Set.
OCI_CACHE_NODE_SUMMARY_DIM_VThe details of each node in the cluster.
OCI_CACHE_REDIS_CLUSTER_DIM_VAn OCI Cache cluster is a memory-based storage solution.
OCI_CACHE_USER_DIM_VAn OCI cache user is required to connect to an OCI cache cluster.
OCI_CACHE_NODE_FACT_VFact table for OCI Cache nodes.
OCI_CACHE_REDIS_CLUSTER_FACT_VFact table for OCI Cache clusters.

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: OCI Cache views.

These diagrams show the relationship of the OCI Cache fact views with different dimension views.

OCI_CACHE_NODE_FACT_V
Relationship diagram showing the fact table, OCI_CACHE_NODE_FACT_V connected to five dimension tables, OCI_CACHE_NODE_SUMMARY_DIM_V, COMPARTMENT_DIM_V, OCI_CACHE_REDIS_CLUSTER_DIM_V, OCI_CACHE_CONFIG_SET_DIM_V, and VCN_SUBNET_DIM_V.

OCI_CACHE_REDIS_CLUSTER_FACT_V
Relationship diagram showing the fact table, OCI_CACHE_REDIS_CLUSTER_FACT_V connected to four dimension tables, OCI_CACHE_REDIS_CLUSTER_DIM_V, OCI_CACHE_CONFIG_SET_DIM_V, COMPARTMENT_DIM_V, and VCN_SUBNET_DIM_V.

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

OCI_CACHE_CONFIG_SET_INFO_DIM_V
Relationship diagram showing the dimension table, OCI_CACHE_CONFIG_SET_INFO_DIM_V connected to two dimension tables, OCI_CACHE_CONFIG_SET_DIM_V and COMPARTMENT_DIM_V.

OCI_CACHE_USER_DIM_V
Relationship diagram showing the dimension table, OCI_CACHE_USER_DIM_V connected to another dimension table, COMPARTMENT_DIM_V.

Sample Queries

Sample queries for OCI Cache.

List the number of nodes per cluster:
SELECT REDIS_CLUSTER_ID, COUNT(NODE_SUMMARY_ID)
FROM OCIRA.OCI_CACHE_NODE_FACT_V
GROUP BY REDIS_CLUSTER_ID;
List the number of clusters per compartment:
SELECT COMPARTMENT_ID, COUNT(REDIS_CLUSTER_ID)
FROM OCIRA.OCI_CACHE_REDIS_CLUSTER_FACT_V
GROUP BY COMPARTMENT_ID;
List the number of users in each region:
SELECT ENTITY_TYPE, VOLUME_ENTITY_ID, SIZE_IN_GBS
FROM OCIRA.BLOCK_VOLUME_FACT_V
WHERE COMPARTMENT_ID = '<insert compartment ID>';

Data Lineage

The Customer Experience Semantic Model Lineage spreadsheet and Metric Calculation Logic spreadsheet for OCI Cache 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 OCI Cache. 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.

The subject area is: