MySQL Database System Statements - Daily
The MySQL Statement Daily data object is a daily aggregated summary by digest for the most important statements executed during the day for every database in the database system. The content is derived from the MySQL performance_schema.events_statements_summary_by_digest table
Table 17-19 MySQL Database CPU, IO and Storage daily
| Field Name | Name | Column Type | Column Category | Description |
|---|---|---|---|---|
| ROLLUP_TIME_UTC | Rollup time (UTC) | TIMESTAMP | TIME_DIMENSION | End timestamp of the rollup period (UTC) |
| ENTITY_TYPE | External type | VARCHAR2 | DIMENSION | Resource external type |
| DB_SYSTEM_NAME | Database system resource name | VARCHAR2 | DIMENSION | Database system resource name |
| DB_SYSTEM_DISPLAY_NAME | Database system resource display name | VARCHAR2 | DIMENSION | Database system resource display name |
| ENTITY_SOURCE | Source type | VARCHAR2 | DIMENSION | Source of the database system resource, for example: MDS_MYSQL_DATABASE |
| OPSI_ENTITY_TYPE | Database system type | VARCHAR2 | DIMENSION | Database system type, for example: MDS-MYSQL |
| OPSI_ID | Resource OCID | VARCHAR2 | DIMENSION | OCID of the database system insight resource |
| ASSOCIATED_RESOURCE_ID | Cloud database system resource | VARCHAR2 | DIMENSION | OCID of the MySQL database system |
| DAY_OF_WEEK | Collection day of week | VARCHAR2 | DIMENSION | Collection day in weekly range 1-7 (Mon-Sun) |
| DAY_OF_MONTH | Collection day of month | VARCHAR2 | DIMENSION | Collection day in monthly range 1-31 |
| OCPU_CAPACITY | Allocated host CPUs | NUMBER | DIMENSION | Total number of CPUs for the MySQL DB system host running the deployed database system's primary instance |
| DB_SYSTEM_VERSION | Database system version | VARCHAR2 | DIMENSION | Database system version |
| IS_HEATWAVE_CLUSTER_ATTACHED | Heatwave attached | VARCHAR2 | DIMENSION | Indicates if the MySQL server has a HeatWave cluster attached |
| IS_HIGHLY_AVAILABLE | HA enabled | VARCHAR2 | DIMENSION | Indicates if the MySQL Server is enabled for high availability |
| SHAPE_NAME | VM Shape | VARCHAR2 | DIMENSION | VM configuration of the MySQL Server MySQL.VM.Standard.E4.1.8GB |
| COMMAND_NAME | Command name | VARCHAR2 | DIMENSION | command name, for example: SELECT UPDATE CREATE |
| DB_NAME | Database name | VARCHAR2 | DIMENSION | Database name for the statement |
| DIGEST | Digest | VARCHAR2 | DIMENSION | SHA-256 value of normalized statement text |
| DIGEST_TEXT | Statement text | VARCHAR2 | DIMENSION | Text of the normalized statement up to 1024 characters |
| EXEC_COUNT | Execution count | VARCHAR2 | DIMENSION | Number of times the statement has executed |
| TOTAL_LATENCY | Total latency (ps) | NUMBER | METRIC | Total wait time in picoseconds |
| LOCK_LATENCY | Lock latency (ps) | NUMBER | METRIC | Time spent waiting for locks in picosecond |
| ERR_COUNT | Error count | NUMBER | METRIC | Number of errors |
| ROWS_AFFECTED | Rows affected | NUMBER | METRIC | Number of rows affected |
| ROWS_SENT | Rows sent | NUMBER | METRIC | Number of rows returned |
| ROWS_EXAMINED | Rows examined | NUMBER | METRIC | Number of rows examined |
| TMP_DISK_TABLES | Temp disk tables | NUMBER | METRIC | Number of internal on-disk temporary tables created |
| TMP_TABLES | Temp tables | NUMBER | METRIC | Number of internal in-memory temporary tables created |
| SELECT_FULL_JOIN | Select full joins | NUMBER | METRIC | Number of joins that perform table scans because they do not use indexes. If this value is not 0, you should carefully check the indexes of your tables |
| SELECT_FULL_RANGE_JOIN | Select full range joins | NUMBER | METRIC | Number of joins that used a range search on a reference table |
| SELECT_RANGE | Select range | NUMBER | METRIC | Number of joins that used ranges on the first table. This is normally not a critical issue even if the value is quite large |
| SELECT_RANGE_CHECK | Select range check | NUMBER | METRIC | Number of joins without keys that check for key usage after each row. If this is not 0, you should carefully check the indexes of your tables |
| SELECT_SCAN | Select scan | NUMBER | METRIC | Number of joins that did a full scan of the first table |
| SORT_MERGE_PASSES | Sort merge passes | NUMBER | METRIC | Number of sort merge passes. If this value is large, you should consider increasing the value of the sort_buffer_size ystem variable |
| SORT_RANGE | Sort range | NUMBER | METRIC | Number of sorts that were done using ranges |
| ROWS_SORTED | Rows sorted | NUMBER | METRIC | Number of rows sorted |
| SORT_SCAN | Sort scan | NUMBER | METRIC | Number of sorts that were done by scanning the table |
| NO_INDEX_USED | No index used count | NUMBER | METRIC | Number occurrences of the statement which performed a table scan without using an index |
| NO_GOOD_INDEX_USED | No good index used count | NUMBER | METRIC | Number of occurences of the statement where the server found no good index to use |
| CPU_LATENCY | CPU latency (ps) | NUMBER | METRIC | Time spent on CPU in picoseconds |
| COUNT_SECONDARY | Count secondary | NUMBER | METRIC | Number of times a query was processed on the secondary engine (HEATWAVE) |