Configurations

DB System Configuration Overview

The DB system configuration is a collection of user, system, initialization, or service-specific variables that define the operation of the MySQL DB system.

The configuration is analogous to the my.ini or my.cnf files that you use in the local installation of the MySQL Server.

You can either select a default configuration or create a custom configuration for your DB system. The configuration is linked to the shape you select. Shapes define the resources available to your DB system. See Supported Shapes.

A DB system configuration has a default set of user and system variables assigned to them. You can edit the user variables while you cannot edit the system variables.

Note

Once you create a configuration, you cannot edit the variables. To add variables, you must create a new configuration with the desired variable definitions, or copy an existing configuration, edit it accordingly, and edit the DB system to use the new configuration.

Configuration Types

MySQL Database Service supports two types of configuration: default and custom configuration. You can either select the default configuration or create a new custom configuration.

  • Default Configuration: Each default configuration is designed for a specific shape and contains a default set of configuration variables.
  • Custom Configuration: You can create a new custom configuration, or copy an existing configuration, edit it, and edit the DB system to use the new configuration.

    When you create a new custom configuration, you select a shape for the DB system. The selected shape has a default configuration associated it. This default configuration becomes your custom configuration, and the DB system inherits all variables of the default configuration. For example, if you create a custom configuration and select the MySQL.VM.Standard.E3.1.8GB shape, the configuration of your new custom configuration is MySQL.VM.Standard.E3.1.8GB.Standalone. See Creating a Custom Configuration.

    If you create a configuration by copying an existing configuration, the original configuration is the parent to the copy. The copy inherits all variables defined on the parent.

    Note

    You can edit the values of the user variables, but can not remove them.

Related Topics

Configuration Variables

Configurations have a default set of user, system, initialization, or service-specific variables. You can edit the user, system, and initialization variables, but not the system variables.

Note

Once you create the configuration, you cannot edit the variables defined on the configuration using SET PERSIST or SET GLOBAL commands. To edit variables, create a new configuration with the desired variables, or copy an existing configuration, edit the variables, and edit the DB system to use the new configuration.

Configuration Variable Overview

Configuration variables can either be a user, system, initialization, or service-specific variables.

  • User Variables: You can edit the user variables when you create or copy a configuration. Some of the user variables are default user variables. You cannot remove these default user variables from your configuration. See User Variables and Default User Variables.
  • System Variables: Oracle defines the system variables according to the shape or requirements of the MySQL instance. You cannot edit the system variables. See System Variables.
  • Initialization Variables: These variables apply for the life span of the MySQL instance of your DB system. While you can edit configurations, and can update the DB systems with new configurations, you cannot change the initialization variables once you apply them. If you attempt to apply a new configuration to a running DB system, with a different initialization variable value, it results in an error. To apply a different initialization variable, create a backup of your DB system, restore it to a new DB system, and select a configuration that uses the required variable. See Initialization Variables.
  • Service-Specific Variables: These variables are specific to MySQL Database Service and are not included in the on-premises version of the MySQL server.

User Variables

User variables are those variables that you can edit when you create or copy a configuration. Some of the user variables are default user variables. You cannot remove these default user variables from your configuration.

Note

To view the minimum and maximum values of user variables, see REST API Configuration Variables.

Table 10-1 Default Values of User Variables

User Variable Default Value
autocommit ON
big_tables OFF
binlog_expire_logs_seconds See Default User Variables.
binlog_row_metadata MINIMAL
binlog_row_value_options See Default User Variables.
binlog_transaction_compression OFF
completion_type NO_CHAIN
connection_memory_chunk_size 8912
connection_memory_limit There is no default value.
connect_timeout 10
cte_max_recursion_depth 1000
default_authentication_plugin caching_sha2_password
foreign_key_checks ON
global_connection_memory_limit There is no default value.
global_connection_memory_tracking false
group_replication_consistency See Default User Variables.
information_schema_stats_expiry 86400
innodb_buffer_pool_dump_pct 25
innodb_buffer_pool_instances See Default User Variables.
innodb_buffer_pool_size See Default User Variables.
innodb_ddl_buffer_size 1048576
innodb_ddl_threads 4
innodb_ft_enable_stopword ON
innodb_ft_max_token_size 84
innodb_ft_min_token_size 3
innodb_ft_num_word_optimize 2000
innodb_ft_result_cache_limit See Default User Variables.
innodb_ft_server_stopword_table NULL
innodb_lock_wait_timeout 50
innodb_log_writer_threads ON
innodb_max_purge_lag 0
innodb_max_purge_lag_delay See Default User Variables.
innodb_stats_persistent_sample_pages 20
innodb_stats_transient_sample_pages 8
interactive_timeout 28800
local_infile See Default User Variables.
mandatory_roles See Default User Variables.
max_allowed_packet 67108864
max_binlog_cache_size See Default User Variables.
max_connect_errors 18446744073709551615
max_connections See Default User Variables.
max_execution_time 0
max_heap_table_size 16777216
max_prepared_stmt_count The default value for all shapes is 16382.

The maximum value is dependent on the amount of RAM provided by the shape.

For standalone and high availability shapes, the maximum value is as follows:

  • 8GB shape - Maximum: 16382
  • 15GB shape - Maximum: 20000
  • 16GB shape - Maximum: 20000
  • 30GB shape - Maximum: 40000
  • 32GB shape - Maximum: 40000
  • 60GB shape - Maximum: 80000
  • 64GB shape - Maximum: 80000
  • 120GB shape - Maximum: 160000
  • 128GB shape - Maximum: 160000
  • 240GB shape - Maximum: 160000
  • 256GB shape - Maximum: 160000
  • 384GB shape - Maximum: 160000
  • 512GB shape - Maximum: 160000
  • 768GB shape - Maximum: 160000
  • 1024GB shape - Maximum: 160000

For HeatWave enabled shapes, the maximum value is as follows:

  • 512GB shape - Maximum: 80000
  • 2048GB shape - Maximum: 80000
mysql_firewall_mode ON
mysqlx_connect_timeout 30
mysqlx_deflate_default_compression_level 3
mysqlx_deflate_max_client_compression_level 5
mysqlx_interactive_timeout 28800
mysqlx_lz4_default_compression_level 2
mysqlx_lz4_max_client_compression_level 8
mysqlx_max_allowed_packet 67108864
mysqlx_read_timeout 28800
mysqlx_wait_timeout 28800
mysqlx_write_timeout 60
mysqlx_zstd_default_compression_level 3
mysqlx_zstd_max_client_compression_level 11
net_read_timeout 30
net_write_timeout 60
parser_max_mem_size 10000000
regexp_time_limit 32
sort_buffer_size 262144
sql_mode ERROR_FOR_DIVISION_BY_ZERO, NO_ENGINE_SUBSTITUTION, NO_ZERO_DATE, NO_ZERO_IN_DATE, ONLY_FULL_GROUP_BY, STRICT_TRANS_TABLES
sql_require_primary_key See Default User Variables.
sql_warnings OFF
thread_pool_dedicated_listeners OFF
thread_pool_max_transactions_limit 0
time_zone See Default User Variables.
tmp_table_size 16777216
transaction_isolation REPEATABLE-READ
wait_timeout 28800

Default User Variables

Default user variables are those user variables whose values are editable, but you cannot delete the variables from your configuration. The default user variable are associated with all configurations.

Note

To view the minimum and maximum values of default user variables, see REST API Configuration Variables.

Table 10-2 Default Values of Default User Variables

Default User Variable Default Value
binlog_expire_logs_seconds 3600
binlog_row_value_options PARTIAL_JSON
group_replication_consistency BEFORE_ON_PRIMARY_FAILOVER
innodb_buffer_pool_instances Dependent on the amount of RAM provisioned by the shape. The default values are as follows:
  • For shapes which provision 8-128GB RAM - 4
  • 256GB shapes - 8
  • 384GB shapes - 12
  • 512GB shapes - 16
  • 768GB shapes - 24
  • 1024GB shapes - 32
innodb_buffer_pool_size

Dependent on the amount of RAM provided by the shape.

For standalone shapes, the default and maximum values are as follows:
  • 8GB shape - Default: 2GB, maximum: 2GB
  • 15GB shape - Default: 10GB, maximum: 10GB
  • 16GB shape - Default: 10GB, maximum: 10GB
  • 30GB shape - Default: 20GB, maximum: 20GB
  • 32GB shape - Default: 20GB, maximum: 20GB
  • 60GB shape - Default: 48GB, maximum: 57GB
  • 64GB shape - Default: 48GB, maximum: 57GB
  • 120GB shape - Default: 96GB, maximum: 115GB
  • 128GB shape - Default: 96GB, maximum: 115GB
  • 240GB shape - Default: 192GB, maximum: 230GB
  • 256GB shape - Default: 192GB, maximum: 230GB
  • 384GB shape - Default: 288GB, maximum: 345GB
  • 512GB shape - Default: 384GB, maximum: 460GB
  • 768GB shape - Default: 576GB, maximum: 691GB
  • 1024GB shape - Default: 768GB, maximum: 921GB
For high availability shapes, the default values are as follows:
Note

The maximum value of high availability shapes remains same as the standalone shapes.
  • 8GB shape - Default: 1.5GB
  • 16GB shape - Default: 8.5GB
  • 32GB shape - Default: 17GB
  • 64GB shape - Default:43GB
  • 128GB shape - Default: 89GB
  • 256GB shape - Default: 185GB
  • 384GB shape - Default: 282GB
  • 512GB shape - Default: 378GB
  • 768GB shape - Default: 570GB
  • 1024GB shape - Default: 752GB

For HeatWave enabled shapes, the default and maximum values are as follows:

  • 512GB shape - Default: 48GB, maximum: 48GB
  • 2048GB shape - Default: 192GB, maximum: 230GB
innodb_ft_result_cache_limit 33554432
innodb_max_purge_lag_delay 300000
local_infile OFF
mandatory_roles empty string
max_binlog_cache_size 4294967296
max_connections Dependent on shape. The default values per shape are:
  • 8GB shapes - 500
  • 16GB shapes - 1000
  • 32GB shapes - 2000
  • 64GB shapes - 4000
  • all shapes larger than 64GB - 8000
sql_require_primary_key (HA shapes only) ON
time_zone Sets the global timezone. The default value is UTC.

System Variables

Oracle defines the system variables according to the shape or requirements of the MySQL instance. You cannot edit the system variables.

Initialization Variables

Initialization variables apply for the life span of the MySQL instance and, once you apply it, you cannot change it later.

Note

To apply a different initialization variable, create a backup of your DB system, restore it to a new DB system, and select a configuration that uses the required variable. See Restoring From a Backup to a New DB System.

Table 10-4 Default Values of Initialization Variable

Initialization Variable Default Value
lower_case_table_name 0

If you set it to 1, the table and schema names are stored in lowercase on disk and comparisons are not case-sensitive.

Service-Specific Variables

Service-specific variables are those variables that are specific to MySQL Database Service and are not included in the on-premise version of MySQL Server.

thread_pool_dedicated_listeners

Enable the thread_pool_dedicated_listeners variable to dedicate a listener thread in each thread group to listen for network events from clients.

When you use the thread_pool_dedicated_listeners variable in conjunction with the thread_pool_max_transactions_limit variable, it ensures that the maximum number of query worker threads is no more than the value you specify in thread_pool_max_transactions_limit.

  • OFF: (Default) Disable the listener thread.
  • ON: Dedicate a listener thread in each thread group to listen for network events from clients and enforces the maximum transaction limit that you specify in the thread_pool_max_transactions_limit variable.

Table 10-5 thread_pool_dedicated_listeners

Parameter Value
Scope Global
Dynamic No
Type Boolean
Default value OFF
thread_pool_max_transactions_limit

Use the thread_pool_max_transactions_limit variable to specify how many open transactions to permit during thread pool operation.

The thread_pool_max_transactions_limit variable enables you to define the maximum number of open transactions the thread pool permits. Open transactions include both active (running) and inactive (not running) transactions. By default, there is no limit on the number of open transactions permitted during thread pool operation.

  • 0: Disable the transaction limit.
  • A nonzero value, greater than zero: Specify the maximum number of open transactions that can exist in the system. You need to set the thread_pool_dedicated_listeners variable to ON.

Table 10-6 thread_pool_max_transactions_limit

Parameter Value
Scope Global
Dynamic Yes
Type Integer
Default value 0

Creating a Custom Configuration

Use the Console to create a custom configuration for your DB system.

This task requires the following:
  • A policy that permits you to create configurations in the compartment or tenancy.
Do the following to create a custom configuration using the console:
  1. Open the navigation menu and select Databases. Under MySQL, click Configurations.
  2. Click Create Configuration.
  3. In the Create Configuration panel, on the Configuration Information section, provide the following details:
    • Name: Specify a user-friendly display name for the configuration. The name does not need to be unique. An Oracle Cloud Identifier (OCID) uniquely identifies the configuration.
    • Description: (Optional) Specify a description of the configuration.
    • Configure placement and hardware:
      • Select a Compartment: (Optional) If you want to create the configuration in a different compartment, select the required compartment.
      • Select a Shape: (Optional) Specify the shape associated with the configuration. Click Change Shape to open the Browse All Shapes dialog box. Select the required shape and click Select a Shape.
    • Show Advanced Options:
      • Tags: (Optional) Specify a Tag Namespace, Tag Key, and Tag Value.
  4. Click Next.
  5. In the Variables Information section, provide the following details:
    • Initialization Variables: (Optional) Enable Ignore case in table and schema names to disable case sensitivity. See Initialization Variables.
    • User Variables: (Optional) Select the variable you want to add in Variable Names drop down list, and specify the Variable Value. To add another variable to your configuration, click +Another Variable .
      Note

      Every configuration has a set of default system and user variables. If you do not select any variable, Oracle adds these default variables to your Configuration. See Configuration Variables. See System Variables and User Variables.
  6. Click Create.
    Note

    Once you create the configuration, you cannot edit the variables defined on the configuration. To edit variables, create a new configuration with the desired variables, or copy an existing configuration, edit the variables, and edit the DB system to use the new configuration. See Updating a DB System Configuration.

Creating a Custom Configuration Using the CLI

Use the command-line interface to create a custom configuration.

This task requires the following:
  • A compartment Oracle Cloud Indetifier (OCID).
  • A policy that permits you to create configurations in the compartment or tenancy.
  • A properly configured CLI installation and the requisite SSH keys. See Command Line Interface.
Create a custom configuration using the CLI either using a JSON payload or from a single command without using a JSON payload:
  1. Using a JSON payload: Open a command prompt and run the following command:
    oci  mysql configuration create 
         -compartment-id <CompartmentOCID>
         --description "<UserDescription>"
         --display-name <UserDisplayName> 
         --shape-name <ShapeName> 
         --variables <JSONPayload>
    • compartment-id: Specify the OCID of the compartment in you create your configuration..
    • description: (Optional) Specify a brief description of the configuration.
    • display-name: (Optional) Specify the display name of the configuration. If you do not define a display name, Oracle generates one for you in the mysqlconfigurationYYYYMMDDHHMMSS format.
    • shape-name: Specify the name of the shape. For example, VM.Standard.E2.1.
    • variables: (Optional) Specify the JSON payload. For example, file://config.json. In the JSON payload, specify the variables in the "name":value format:
      {
          "autocommit": true,
          "connectTimeout": 20,
          "sql-require-primary-key": true
      } 
  2. (Optional) Without using a JSON payload: You can run the command from a single command line rather than using a JSON payload.
    oci mysql configuration create -c <CompartmentOCID>
         --description "<UserDescription>"
         --display-name <UserDisplayName>  
         --shape-name <ShapeName> 
         --variables '{ "autocommit": true, "connectTimeout": 20, "sql-require-primary-key": true }'       
If the command validates and runs successfully, you get a response similar to the following, which summarizes the request and creates your configuration:
{
  "data": {
    "compartment-id": "ocid1.compartment.oc1..longAlphanumericString",
    "defined-tags": {
      "Oracle-Tags": {
        "CreatedBy": "userName",
        "CreatedOn": "2020-07-07T11:01:19.623Z"
      }
    },
    "description": this is a user-defined configuration,
    "display-name": "UserConfig001",
    "freeform-tags": {},
    "id": "ocid1.mysqlconfiguration.oc1.iad.longAlphanumericString",
    "lifecycle-state": "ACTIVE",
    "parent-configuration-id": null,
    "shape-name": "VM.Standard.E2.1",
    "time-created": "2020-07-07T11:01:19.635000+00:00",
    "time-updated": "2020-07-07T11:01:19.635000+00:00",
    "type": "CUSTOM",
    "variables": {
      "autocommit": true,
      "binlog-expire-logs-seconds": 3600,
      "completion-type": null,
      "connect-timeout": 20,
      "cte-max-recursion-depth": null,
      "default-authentication-plugin": null,
      "foreign-key-checks": null,
      "generated-random-password-length": null,
      "information-schema-stats-expiry": null,
      "innodb-buffer-pool-instances": 4,
      "innodb-buffer-pool-size": 3758096384,
      "innodb-ft-enable-stopword": null,
      "innodb-ft-max-token-size": null,
      "innodb-ft-min-token-size": null,
      "innodb-ft-num-word-optimize": null,
      "innodb-ft-result-cache-limit": 33554432,
      "innodb-ft-server-stopword-table": null,
      "innodb-lock-wait-timeout": null,
      "innodb-max-purge-lag": null,
      "innodb-max-purge-lag-delay": 300000,
      "local-infile": true,
      "mandatory-roles": "public",
      "max-connections": 1000,
      "max-execution-time": null,
      "max-prepared-stmt-count": null,
      "mysql-firewall-mode": null,
      "mysql-zstd-default-compression-level": null,
      "mysqlx-connect-timeout": null,
      "mysqlx-deflate-default-compression-level": null,
      "mysqlx-deflate-max-client-compression-level": null,
      "mysqlx-document-id-unique-prefix": null,
      "mysqlx-enable-hello-notice": null,
      "mysqlx-idle-worker-thread-timeout": null,
      "mysqlx-interactive-timeout": null,
      "mysqlx-lz4-default-compression-level": null,
      "mysqlx-lz4-max-client-compression-level": null,
      "mysqlx-max-allowed-packet": null,
      "mysqlx-min-worker-threads": null,
      "mysqlx-read-timeout": null,
      "mysqlx-wait-timeout": null,
      "mysqlx-write-timeout": null,
      "mysqlx-zstd-max-client-compression-level": null,
      "parser-max-mem-size": null,
      "query-alloc-block-size": null,
      "query-prealloc-size": null,
      "sql-mode": null,
      "sql-require-primary-key": true,
      "sql-warnings": null,
      "transaction-isolation": null
    }
  }
}

Editing a Custom Configuration

Use the Console to edit the name, description and tags of a custom configuration. You cannot edit the default configuration.

Note

Once you create the configuration, you cannot edit the variables defined on the configuration. To edit variables, create a new configuration with the desired variables, or copy an existing configuration, edit the variables, and edit the DB system to use the new configuration. See Updating a DB System Configuration.
  1. Open the navigation menu and select Databases. Under MySQL, click Configurations.
  2. Locate the custom configuration you want to edit and do one of the following:
    • Click the Actions menu and select Edit to open the Edit MySQL Configuration dialog box.
    • Click the name of the configuration to open the Configuration Details page and click Edit.
  3. In the Edit Configuration dialog box, edit the configuration name, description, and tags.
  4. Click Save Changes.

Copying a Configuration

Use the Console to copy either an existing custom configuration or a default configuration, and create your a new custom configuration.

  1. Open the navigation menu and select Databases. Under MySQL, click Configurations.
  2. Click the Actions menu on the same line as the configuration you want to copy, and select Copy Configuration.
  3. In the Copy Configuration panel, in the Configuration Information section, provide the following details:
    • Name: Specify a user-friendly display name for the configuration. The name does not need to be unique. An Oracle Cloud Identifier (OCID) uniquely identifies the configuration.
    • Description: (Optional) Specify a description of the configuration.
    • Configure placement and hardware:
      • Select a Compartment: (Optional) If you want to create the configuration in a different compartment, select the required compartment.
      • Select a Shape: You cannot change the shape associated with the configuration.
    • Show Advanced Options:
      • Tags: (Optional) Specify a Tag Namespace, Tag Key, and Tag Value.
  4. Click Next.
  5. In the Variables Information section, provide the following details:
    • Initialization Variables: (Optional) Enable Ignore case in table and schema names to disable case sensitivity. See Initialization Variables.
    • User Variables: (Optional) Select the variable you want to add in Variable Names drop down list, and specify the Variable Value. To add another variable to your configuration, click +Another Variable .
      Note

      Every configuration has a set of default user variables. If you do not select any variable, Oracle adds the default variables to your Configuration. See Configuration Variables. See User Variables.
    • System Variables: You cannot edit the system variables. See System Variables.
  6. Click Copy.
    Note

    Once you create the configuration, you cannot edit the variables defined on the configuration. To edit variables, create a new configuration with the desired variables, or copy an existing configuration, edit the variables, and edit the DB system to use the new configuration.

Updating a DB System Configuration

Once you have saved a DB system configuration, you cannot edit the variables of the configuration. To apply a new set of configuration variables to a DB system, create a new configuration using the variables you require, and then apply this new configuration to the DB system.

To update the configuration of a DB system, see the following:
Note

You cannot update the configuration if there is an active channel connected to the DB system. Stop the channel to update the configuration.

Updating a DB System Configuration Using the CLI

Use the command-line interface to update the configuration of a DB system. You can use an already existing configuration or create a new configuration using the variables you require. Once you save the configuration, you can not edit the variables of the configuration.

This task requires the following:
  • A DB system Oracle Cloud Identifier (OCID).
  • A MySQL configuration OCID.
  • A properly configured CLI installation and the requisite SSH keys. See Command Line Interface.
  1. (Optional) Create a new configuration. See Creating a Custom Configuration Using the CLI.
  2. Open a command prompt and run the following command:
    oci mysql db-system update 
         --db-system-id <DBSystemOCID>
         --configuration-id <ConfigurationOCID>
    • db-system-id: Specify the OCID of the DB system you want to update.
    • configuration-id: Specify the OCID of the configuration with which you want to replace the existing configuration.
    This command stops the running MySQL server and restarts it with the new configuration values.

Comparing Configurations

Use the Console to compare the shapes, initialization variables, and user variables of two configurations.

  1. Open the navigation menu and select Databases. Under MySQL, click Configurations.
  2. Select the check box of the two configurations you want to compare, click the Actions button at the top of the page, and then click Compare.
  3. In the Compare configurations panel, click either of the following option buttons:
    • Show configuration differences: Displays the differences in the shapes, initialization variables, and user variables.
    • Show all configuration information: Displays all information related to shapes, initialization variables, and user variables of the two configurations.
  4. Click Close.

Changing a DB System Timezone Using a Command-Line Client

Use a command-line client such as MySQL Client or MySQL Shell to change the timezone of a DB system. You can change the timezone of the current session only, and upon restart, the timezone reverts to the value you specify in the configuration of the DB system.

Note

To change the timezone of a DB system completely, update the configuration of the DB system with a new configuration that contains the required time_zone value. See Editing a DB System.
Note

All commands are run in the SQL execution mode.
  1. Connect to your DB system using a command-line client, and run the following command:
    set time_zone='<TimezoneName>';
    You can specify the following in <TimezoneName>:
    • Any timezone such as GMT, HST, and PST. The default timezone is UTC.
    • Timezone in the following format: GMT+7:00, PST-4.00, -7:00 , and +3:00.
  2. (Optional) To view the global and session time_zone values, run the following command:
    SELECT @@GLOBAL.time_zone, @@SESSION.time_zone;
    You get a response similar to the following:
    +--------------------+---------------------+
    | @@GLOBAL.time_zone | @@SESSION.time_zone |
    +--------------------+---------------------+
    | UTC                | UTC                 |
    +--------------------+---------------------+

MySQL Configuration Details

The MySQL Configuration Details page lists all relevant information and functionality for the selected MySQL Configuration,

Table 10-7 Configuration Information

Field Description
OCID The unique identifier of the MySQL configuration.
Description Description of the MySQL configuration.
Shape The shape type the configuration is associated with. Each configuration can only be used with a specific shape..
State Lifecycle state.
Source Configuration Name of the configuration this configuration is based on. If you created a new configuration, this field displays the name of the default configuration associated with the shape you selected. If you copied the configuration from an existing configuration, this field displays the name of the parent configuration.
Compartment The compartment in which the configuration was created.
Type The type of configuration, Default or Custom. Where Default is provided with the service, and Custom is user-created.
Created Date and time the configuration was created.
Last Updated The date and time the configuration was last updated.

Configuration Resources

Resources section of the Configuration Details page.

Table 10-8 Configuration Details Resources

Resource Name Description
Variables Lists the following:
  • Name: the name of the variable.
  • Value: the value of the variable.
  • User defined: whether the variable's value is user defined, or not.
For more information on MySQL variables, see the following resources:
Associated DB Systems Lists the following:
  • Name: the name of the DB System using this configuration.
  • DB System State: the current state of the DB System.
  • Created: the date and time the DB System was created.