Update content

umn/source/account_management/creating_an_account.rst

@@ -31,10 +31,10 @@ Procedure
       |                                   |                                                                                                                                                       |
       |                                   | -  Must be case-sensitive.                                                                                                                            |
       |                                   | -  Can include 8 to 32 characters.                                                                                                                    |
-      |                                   | -  The password must contain at least three types of lowercase letters, uppercase letters, digits, and special characters ~! ``@#%^*-_=+?``           |
+      |                                   | -  Must contain at least three of the following character types: letters, digits, and special characters ``~!@#%^*-_=+?``                             |
       |                                   | -  Do not use weak or easy-to-guess passwords.                                                                                                        |
       +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------+
-      | Confirm Password                  | None                                                                                                                                                  |
+      | Confirm Password                  | The confirm password must be the same as the entered password.                                                                                        |
       +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------+
       | Schema                            | Schema to be associated with the account. You can select an existing schema from the drop-down list.                                                  |
       |                                   |                                                                                                                                                       |

umn/source/backups_and_restorations/consistent_backups.rst

@@ -1,8 +0,0 @@
-:original_name: ddm_12_0005.html
-
-.. _ddm_12_0005:
-
-Consistent Backups
-==================
-
-DDM replaces its consistent backup function with a new feature called "metadata restore" under Data Restoration. After the change, existing consistency backups cannot be used for restoration, and operations related to consistency backups are hidden You can restore data by referring to section "Restoring Metadata." If you have any questions, contact DDM technical support.

umn/source/backups_and_restorations/index.rst

@@ -5,7 +5,6 @@
 Backups and Restorations
 ========================
 
--  :ref:`Consistent Backups <ddm_12_0005>`
 -  :ref:`Restoring Data to a New Instance <ddm_0600016>`
 -  :ref:`Restoring Metadata <ddm_0600017>`
 
@@ -13,6 +12,5 @@ Backups and Restorations
    :maxdepth: 1
    :hidden: 
 
-   consistent_backups
    restoring_data_to_a_new_instance
    restoring_metadata

umn/source/backups_and_restorations/restoring_data_to_a_new_instance.rst

@@ -19,8 +19,6 @@ Constraints
 
 -  Restoring data to a new DDM instance will overwrite data on it and cause the instance to be unavailable during restoration.
 -  The new RDS for MySQL instances must have the same or later versions than the original ones, and their storage space must be greater than or equal to that of the original ones.
--  Data cannot be restored to a local RDS for MySQL instance.
--  Data cannot be restored to an RDS for MySQL instance that uses SSDs for storage.
 -  Restoration is not supported if the DDM instance is in the primary network and the destination RDS for MySQL instance is in the extended network.
 -  The source DDM instance must be of the version 2.3.2.11 or later, and the destination DDM instance must be of the version 3.0.8 or later.
 -  Time points that data can be restored to depend on the backup policy set on original data nodes.
@@ -58,4 +56,4 @@ Procedure
 
 #. On the displayed **Restore to New Instance** page, specify a time range and a point in time and select the DDM instance created in :ref:`1 <ddm_0600016__li4793191882712>` as the destination DDM instance.
 
-#. Select the RDS for MySQL instances created in :ref:`2 <ddm_0600016__li1017501443616>` as destination DB instances and check the confirmation box. Click **OK**. Wait for 1 to 3 minutes for the data restoration to complete.
+#. Select the RDS for MySQL instances created in :ref:`2 <ddm_0600016__li1017501443616>` as destination instances and check the confirmation box. Click **OK**. Wait for 1 to 3 minutes for the data restoration to complete.

umn/source/backups_and_restorations/restoring_metadata.rst

@@ -38,13 +38,13 @@ Restoring Metadata to a Point in Time
 
    Create a DDM instance. For details, see :ref:`Creating a DDM Instance <ddm_06_00017>`.
 
-#. In the DDM instance list, locate the newly-created instance and click its name.
+#. In the DDM instance list, locate the instance that needs to be restored and click its name.
 
 #. In the navigation pane on the left, choose **Backups & Restorations**. Click **Restore Metadata**.
 
 #. Specify a time point. DDM will select an appropriate DDM metadata backup closest to the time point.
 
-#. Select the destination instance created in :ref:`1 <ddm_0600017__li4793191882712>`. If there are no instances available, create an instance by referring to :ref:`Creating a DDM Instance <ddm_06_00017>`.
+#. Select the destination DDM instance created in :ref:`1 <ddm_0600017__li4793191882712>`.
 
 #. Select the RDS for MySQL instance that has PITR completed and click **OK**.
 

umn/source/conf.py

@@ -18,7 +18,7 @@ import os
 import sys
 
 extensions = [
-    'otcdocstheme'
+    'otcdocstheme',
 ]
 
 otcdocs_auto_name = False

umn/source/connection_management/changing_a_database_port.rst

@@ -19,13 +19,9 @@ Procedure
 
    For DDM instances, the database port number ranges from 1025 to 65534 except for ports 1033, 7009, 8888, and 12017 because they are in use by DDM. The default value is **5066**.
 
-   -  Specify a new port number and click |image2|.
+   -  Click |image2|.
 
-      -  In the dialog box, click **Yes**.
-
-         Changing the database port requires a restart of the DDM instance.
-
-      -  In the dialog box, click **No**.
+      Changing the database port requires a restart of the DDM instance. To continue the change, click **Yes** in the displayed dialog box. To cancel the change, click **No**.
 
    -  To cancel the change, click |image3|.
 

umn/source/connection_management/configuring_access_control.rst

@@ -13,13 +13,10 @@ DDM supports load balancing by default, but some regions may not support. If an
 Procedure
 ---------
 
-.. important::
+#. Log in to the DDM console and choose **Instances** in the navigation pane. In the instance list, locate the DDM instance that you want to configure access control for, and click its name.
 
-   After a read-only group is created, the entry for configuring access control will be moved to the operation column of the group.
+#. On the displayed **Basic Information** page, in the **Network Information** area, enable **Access Control**.
 
-#. On the DDM console, choose **Instances** in the navigation pane. In the instance list, locate the DDM instance that you want to scale out, and click its name. On the displayed **Basic Information** page, enable **Access Control** in the **Network Information** area.
-#. Click **Configure**. In the **Configure Access Control** dialog box, specify **Access Policy**, enter the required IP addresses, and click **OK**.
+   After a read-only group is created for a DDM instance, you can enable **Access Control** in the **Group Information** area on the **Basic Information** page.
 
-   .. note::
-
-      If read/write splitting is enabled, access control only takes effect for groups.
+#. Click **Configure** on the right of **Access Control**. In the **Configure Access Control** dialog box, specify **Access Policy**, enter the required IP addresses, and click **OK**.

umn/source/data_node_management/configuring_read_weights.rst

@@ -5,21 +5,35 @@
 Configuring Read Weights
 ========================
 
+If one DDM instance is associated with multiple data nodes, you can synchronize read weight settings of the first data node to other data nodes.
+
 Prerequisites
 -------------
 
 You have logged in to the DDM console.
 
-Scenarios
----------
+Precautions
+-----------
 
-If one DDM instance is associated with multiple data nodes, you can synchronize read weight settings of the first data node to other data nodes.
+The read weight can be 0 to 100.
 
 Procedure
 ---------
 
-#. In the instance list, locate the DDM instance whose data nodes you want to configure read weights for, and click its name.
-#. Choose **Data Nodes** in the left navigation pane and click **Configure Read Weight**.
-#. In the displayed **Configure Read Weight** dialog box, set the required parameters and click **OK**.
-#. Wait the request to configure read weights is submitted.
-#. Check whether read weights of read replicas are updated.
+#. In the instance list, locate the DDM instance whose data nodes you want to configure read weights for.
+#. Click the instance name to enter the **Basic Information** page.
+#. In the navigation pane, choose **Data Nodes**.
+#. Set read weights for associated instances.
+
+   -  Set read weights for multiple instances.
+
+      If you want to set read weights for multiple instances at a time, click **Configure Read Weight** on the **Data Nodes** page.
+
+      In the displayed dialog box, click **Synchronize** to apply the read weight of the first instance to other instances. This operation requires that read weights of all instances should be the same. Otherwise, you need to manually configure a read weight for each instance.
+
+   -  Set a read weight for an instance.
+
+      If you want to set the read weight of an instance, locate the target instance and click **Configure Read Weight** in the **Operation** column.
+
+#. Click **Yes**.
+#. After the read weight is configured successfully, you can view the updated read weight on the **Data Nodes** page.

umn/source/data_node_management/index.rst

@@ -6,8 +6,9 @@ Data Node Management
 ====================
 
 -  :ref:`Overview <ddm_10_1001>`
--  :ref:`Configuring Read Weights <ddm_10_1002>`
 -  :ref:`Synchronizing Data Node Information <ddm_10_1003>`
+-  :ref:`Configuring Read Weights <ddm_10_1002>`
+-  :ref:`Splitting Read and Write Requests <ddm_06_0012>`
 -  :ref:`Reloading Table Data <ddm_03_0059>`
 
 .. toctree::
@@ -15,6 +16,7 @@ Data Node Management
    :hidden: 
 
    overview
-   configuring_read_weights
    synchronizing_data_node_information
+   configuring_read_weights
+   splitting_read_and_write_requests
    reloading_table_data

umn/source/data_node_management/reloading_table_data.rst

@@ -19,7 +19,4 @@ Procedure
 ---------
 
 #. Choose **Instances** on the left navigation pane, in the instance list, locate the instance whose information is changed and click the instance name.
-
 #. Choose **More** > **Reload Table Data** in the **Operation** column.
-
-   A message is returned, indicating that table data of instance *XXX* has been reloaded.

umn/source/data_node_management/splitting_read_and_write_requests.rst

@@ -0,0 +1,39 @@
+:original_name: ddm_06_0012.html
+
+.. _ddm_06_0012:
+
+Splitting Read and Write Requests
+=================================
+
+Read/write splitting offloads read requests from primary instances to read replicas on a data node at a ratio, improving processing of read/write transactions. This function is transparent to applications, and you do not need to modify service code. Configure read weights of primary instances and their read replicas on the DDM console, and read traffic will be distributed at the preset ratio and write traffic will be forwarded to the primary instances by default. The ratio is generally based on service requirements and loads of associated data nodes.
+
+Data is asynchronously replicated from the primary instance to read replicas, and there is a delay between them in milliseconds. Set weights of the primary instance and its read replicas to 0 and 100, respectively, that is, distribute all read requests to read replicas if sub-second latency is allowed for read requests and these requests require high query costs that may impact read/write transactions. In other scenarios, adjust the ratio based on service requirements.
+
+Precautions
+-----------
+
+-  The SELECT statements that contain hints or modify data in transactions are all executed by the primary instances.
+-  If the associated primary instance becomes faulty and parameter **Seconds_Behind_Master** on its read replicas is set to **NULL**, read-only requests are still forwarded to the primary instance. Recover the faulty instance as soon as possible.
+
+Prerequisites
+-------------
+
+-  You have created a DDM instance and a data node with read replicas.
+-  You have created a schema.
+
+Procedure
+---------
+
+#. On the **Instances** page, locate the required DDM instance and click its name.
+#. In the navigation pane, choose **Data Nodes**.
+#. On the displayed page, locate the target instance and click **Configure Read Weight** in the **Operation** column.
+
+   -  The read weight ranges from 0 to 100.
+
+   -  If you create a read replica for the associated instance, the read replica will handle all separated read requests by default. To re-assign read/write requests, you can configure read weights of the associated instance and its read replica.
+
+   -  After the read weights are configured, the primary instance and its read replica will handle read requests according to the ratio: Read weight of primary instance/Total read weights of primary instance and read replica: Read weight of read replica/Total read weights of primary instance and read replica.
+
+      For example: If an RDS for MySQL instance contains one primary instance and one read replica and read weights of the primary instance and its read replica are 20 and 80 respectively, they will process read requests in the ratio of 1:4. In other words, the primary instance processes 1/4 of read requests and read replica processes 3/4. Write requests are automatically routed to the primary instance.
+
+#. After the read weights are configured successfully, you can view the weights on the **Data Nodes** page.

umn/source/faqs/connection_management/how_can_i_handle_garbled_characters_generated_when_i_connect_a_mysql_instance_to_a_ddm_instance.rst

@@ -13,4 +13,4 @@ Example:
 
 .. code-block::
 
-   mysql -h 127.0.0.1 -P 5066 -D database --default-character-set=utf8 -u ddmuser -p password
+   mysql -h 127.0.0.1 -P 5066 -D database --default-character-set=utf8 -u ddmuser

umn/source/faqs/ddm_usage/what_should_i_do_if_an_error_message_is_returned_when_i_specify_an_auto-increment_primary_key_during_migration.rst

@@ -9,4 +9,4 @@ Execute the following SQL statement to modify the start value of the auto-increm
 
 .. code-block::
 
-   ALTER SEQUENCE Database name.SEQ name START WITH New start value
+   ALTER SEQUENCE <Database_name>.<SEQ_name> START WITH <New_start_value>

umn/source/faqs/rds-related_questions/what_risky_operations_on_rds_for_mysql_will_affect_ddm.rst

@@ -16,6 +16,8 @@ What Risky Operations on RDS for MySQL Will Affect DDM?
    +============================================+========================================================================+==================================================================================================================================================================================================+
    | Operations on the RDS for MySQL console    | Deleting an RDS for MySQL instance                                     | After an RDS for MySQL instance is deleted, all schemas and logical tables of the DDM instance associated with the RDS instance become unavailable.                                              |
    +--------------------------------------------+------------------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+   |                                            | Stopping an RDS for MySQL instance                                     | After an RDS for MySQL instance is stopped, all schemas and logical tables of the DDM instance associated with the RDS instance become unavailable.                                              |
+   +--------------------------------------------+------------------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
    |                                            | Performing the primary/standby switchover of an RDS for MySQL instance | RDS for MySQL may be intermittently interrupted during the primary/standby switchover. In addition, a small amount of data may be lost in case of long delay in primary/standby synchronization. |
    |                                            |                                                                        |                                                                                                                                                                                                  |
    |                                            |                                                                        | -  Creating schemas or logical tables is not allowed on DDM during the primary/standby switchover of the RDS for MySQL instance.                                                                 |
@@ -23,7 +25,7 @@ What Risky Operations on RDS for MySQL Will Affect DDM?
    +--------------------------------------------+------------------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
    |                                            | Restarting an RDS for MySQL instance                                   | The restart of an RDS for MySQL instance makes itself unavailable and will also affect the associated DDM instance.                                                                              |
    +--------------------------------------------+------------------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-   |                                            | Resetting a password                                                   | After the RDS for MySQL instance password is reset, enter the new password on DDM when you create a schema.                                                                                      |
+   |                                            | Resetting a password                                                   | After the password of an RDS for MySQL instance is reset, enter the new password on the **DB Instance Connection** page when creating a DDM schema.                                              |
    +--------------------------------------------+------------------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
    |                                            | Modifying a parameter template                                         | The following parameters are set to fixed values. If their values are modified, DDM will not function properly.                                                                                  |
    |                                            |                                                                        |                                                                                                                                                                                                  |

umn/source/getting_started/overview.rst

@@ -22,7 +22,7 @@ Process of Using DDM
 :ref:`Step 4: Log In to the DDM Schema <ddm_02_0005>`
 
 
-.. figure:: /_static/images/en-us_image_0000001475213541.png
+.. figure:: /_static/images/en-us_image_0000001628646381.png
    :alt: **Figure 1** Flowchart for using DDM
 
    **Figure 1** Flowchart for using DDM

umn/source/getting_started/step_1_create_a_ddm_instance_and_an_rds_for_mysql_instance.rst

@@ -41,7 +41,6 @@ Procedure
       |                                   | -  Must start with a letter.                                                                                                                                                                                                                                                  |
       |                                   | -  Must be 4 to 64 characters long.                                                                                                                                                                                                                                           |
       |                                   | -  Can contain only letters, digits, and hyphens (-).                                                                                                                                                                                                                         |
-      |                                   | -  Cannot contain other special characters.                                                                                                                                                                                                                                   |
       +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
       | Node Class                        | Class of the DDM instance node. You can select **General-enhanced** or **Kunpeng general computing-plus** and then specify a node class.                                                                                                                                      |
       |                                   |                                                                                                                                                                                                                                                                               |
@@ -80,15 +79,17 @@ Procedure
 
 #. To view and manage the instance, go to the **Instances** page.
 
-   The default database port is **5066** and cab be changed after a DDM instance is created.
+   The default database port is **5066** and can be changed after a DDM instance is created.
 
    For details, see :ref:`Changing a Database Port <ddm_06_0036>`.
 
 #. Switch to the RDS console, click **Create** **DB Instance** in the upper right corner, specify the required information, and click **Next**.
 
+   For details about how to create an RDS for MySQL instance, see `Create a DB Instance <https://docs.otc.t-systems.com/en-us/usermanual/rds/rds_02_0008.html>`__.
+
    .. caution::
 
-      The RDS for MySQL instance you will buy must be in the same VPC and subnet as your DDM instance. If they are not in the same subnet, configure routes to ensure network connectivity.
+      The RDS for MySQL instance must be in the same VPC and subnet as your DDM instance. If they are not in the same subnet, configure routes to ensure network connectivity.
 
 #. After confirming the settings, click **Submit**. Wait 1 to 3 minutes till the instance is created.
 

umn/source/getting_started/step_2_create_a_schema_and_associate_it_with_an_rds_for_mysql_instance.rst

@@ -5,55 +5,35 @@
 Step 2: Create a Schema and Associate It with an RDS for MySQL Instance
 =======================================================================
 
-You can create a schema on the **Instances** or **Schemas** page. This section uses the **Instances** page as an example to describe how to create a schema.
-
-
-.. figure:: /_static/images/en-us_image_0000001475213493.png
-   :alt: **Figure 1** Instances page
-
-   **Figure 1** Instances page
-
-
-.. figure:: /_static/images/en-us_image_0000001475132933.png
-   :alt: **Figure 2** Schemas page
-
-   **Figure 2** Schemas page
-
 Procedure
 ---------
 
 #. Log in to the DDM console, and in the navigation pane, choose **Instances**. In the instance list, locate the required DDM instance and click **Create Schema** in the **Operation** column.
-
 #. On the displayed page, specify a sharding mode, enter a schema name, set the number of shards, select the required DDM accounts, and click **Next**.
 
+   .. table:: **Table 1** Parameter description
 
-   .. figure:: /_static/images/en-us_image_0000001475012977.png
-      :alt: **Figure 3** Creating a schema
+      +-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+      | Parameter                         | Description                                                                                                                                                                                                              |
+      +===================================+==========================================================================================================================================================================================================================+
+      | Sharding                          | -  **Sharded**: indicates that one schema can be associated with multiple data nodes, and all shards will be evenly distributed across the nodes.                                                                        |
+      |                                   | -  **Unsharded**: indicates that one schema can be associated with only one data node, and only one shard can be created on the data node.                                                                               |
+      +-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+      | Schema                            | The name contains 2 to 48 characters and must start with a lowercase letter. Only lowercase letters, digits, and underscores (_) are allowed.                                                                            |
+      +-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+      | Account                           | The DDM account that needs to be associated with the schema.                                                                                                                                                             |
+      +-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+      | Data Nodes                        | Select only the data nodes that are in the same VPC as your DDM instance and not in use by other data nodes. DDM will create databases on the selected data nodes without affecting their existing databases and tables. |
+      +-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+      | Shards                            | The total shards are the shards on all data nodes. There cannot be more data nodes than there are shards in the schema. Each data node must have at least one shard assigned. Recommended shards per data node: 8 to 64. |
+      +-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
 
-      **Figure 3** Creating a schema
-
-   .. note::
-
-      -  DDM supports two sharding options:
-
-         -  **Sharded**: indicates that one schema can be associated with multiple data nodes, and all shards will be evenly distributed across the nodes.
-         -  **Unsharded**: indicates that one schema can be associated with only one data node, and only one shard can be created on that instance.
-
-      -  **Schema Name**: indicates the name of the schema. The name contains 2 to 48 characters and must start with a lowercase letter. Only lowercase letters, digits, and underscores (_) are allowed.
-      -  **Shards**: indicates the total number of shards that can be created in the schema. The number of shards on a data node cannot exceed 64. If more than 64 shards are required, contact DDM technical support.
-
-#. Enter a database account with the required permissions and click **Test Connection**.
+#. On the **DB Instance Connection** page, enter a database account with the required permissions and click **Test Connection**.
 
    .. note::
 
       Required permissions: SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, RELOAD, PROCESS, REFERENCES, INDEX, ALTER, SHOW DATABASES, CREATE TEMPORARY TABLES, LOCK TABLES, EXECUTE, REPLICATION SLAVE, REPLICATION CLIENT, CREATE VIEW, SHOW VIEW, CREATE ROUTINE, ALTER ROUTINE, CREATE USER, EVENT, TRIGGER WITH GRANT OPTION
 
-      Create a special account and assign it the above permissions as required. Then use the account to create a schema for later operations.
-
-
-   .. figure:: /_static/images/en-us_image_0000001425254180.png
-      :alt: **Figure 4** Testing the connection
-
-      **Figure 4** Testing the connection
+      You can create a database account for the RDS for MySQL instance and assign it the above permissions in advance.
 
 #. After the test becomes successful, click **Finish**.

umn/source/getting_started/step_3_create_a_ddm_account.rst

@@ -24,10 +24,10 @@ Procedure
       | Password                          | Password of the account. The password:                                                                                                                |
       |                                   |                                                                                                                                                       |
       |                                   | -  Can include 8 to 32 characters.                                                                                                                    |
-      |                                   | -  Must contain at least three of the following character types: letters, digits, swung dashes (~), and exclamation marks (!). @ # % ^ \* - \_ = + ?  |
+      |                                   | -  Must contain at least three of the following character types: letters, digits, and special characters ``~!@#%^*-_=+?``                             |
       |                                   | -  Cannot be a weak password. It cannot be overly simple and easily guessed.                                                                          |
       +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------+
-      | Confirm Password                  | ``-``                                                                                                                                                 |
+      | Confirm Password                  | The confirm password must be the same as the entered password.                                                                                        |
       +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------+
       | Schema                            | Schema to be associated with the DDM account. You can select an existing schema from the drop-down list.                                              |
       |                                   |                                                                                                                                                       |

umn/source/getting_started/step_4_log_in_to_the_ddm_schema.rst

@@ -82,12 +82,12 @@ Using the MySQL CLI to Log In to a Schema
 
    .. code-block::
 
-      mysql -h ${DDM_SERVER_ADDRESS} -P${DDM_SERVER_PORT} -u${DDM_USER} -p [-D${DDM_DBNAME}] [--default-character-set=utf8][--default_auth=mysql_native_password]
+      mysql -h ${DDM_SERVER_ADDRESS} -P ${DDM_SERVER_PORT} -u ${DDM_USER} -p [-D ${DDM_DBNAME}] [--default -character -set=utf8][--default_auth=mysql_native_password]
 
    .. table:: **Table 1** Parameter description
 
       +------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+
-      | Example Parameter                  | Description                                                                                                                                            | Example Value         |
+      | Parameter                          | Description                                                                                                                                            | Example Value         |
       +====================================+========================================================================================================================================================+=======================+
       | DDM_SERVER_ADDRESS                 | IP address of the DDM instance                                                                                                                         | 192.168.0.200         |
       +------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+
@@ -101,18 +101,16 @@ Using the MySQL CLI to Log In to a Schema
       |                                    |                                                                                                                                                        |                       |
       |                                    | Configure this parameter if garbled characters are displayed during parsing due to inconsistency between MySQL connection code and actually used code. |                       |
       +------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+
-      | default_auth=mysql_native_password | The password authentication plug-in is used by default.                                                                                                | ``-``                 |
+      | default_auth=mysql_native_password | (Optional) The password authentication plug-in is used by default.                                                                                     | ``-``                 |
+      |                                    |                                                                                                                                                        |                       |
+      |                                    | If you use the MySQL 8.0 client, this parameter is required.                                                                                           |                       |
       +------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+
 
-   .. note::
-
-      If you use the MySQL 8.0 client, set **default_auth** to **mysql_native_password**.
-
 #. View the command output. The following is an example output of running a MySQL command in the Windows CLI.
 
    .. code-block::
 
-      C:\Users\testDDM>mysql -h192.168.0.200 -P5066 -Ddb_5133 -udbuser01 -p
+      C:\Users\testDDM>mysql -h 192.168.0.200 -P 5066 -D db_5133 -u dbuser01 -p
       Enter password:
       Reading table information for completion of table and column names
       You can turn off this feature to get a quicker startup with -A
@@ -144,7 +142,7 @@ Using a JDBC Driver to Log In to a Schema
 
    .. note::
 
-      JDBC drivers 5.1.35 to 5.1.45 are recommended.
+      JDBC drivers 5.1.49 or later are recommended.
 
 #. Create a database connection.
 
@@ -174,7 +172,7 @@ Using a JDBC Driver to Log In to a Schema
 
    .. code-block::
 
-      loadBalanceAutoCommitStatementThreshold=5&loadBalanceHostRemovalGracePeriod=15000&loadBalanceBlacklistTimeout=60000&loadBalancePingTimeout=5000&retriesAllDown=10&connectTimeout=10000";
+      loadBalanceAutoCommitStatementThreshold=5&loadBalanceHostRemovalGracePeriod=15000&loadBalanceBlacklistTimeout=60000&loadBalancePingTimeout=5000&retriesAllDown=10&connectTimeout=10000
 
    .. note::
 
@@ -184,7 +182,7 @@ Using a JDBC Driver to Log In to a Schema
       -  **loadBalanceBlacklistTimeout**: indicates the time in milliseconds between checks of servers which are unavailable, by controlling how long a server lives in the global blacklist.
       -  **loadBalancePingTimeout**: indicates the time in milliseconds that the connection will wait for a response to a ping operation when you set **loadBalanceValidateConnectionOnSwapServer** to **true**.
       -  **retriesAllDown**: indicates the maximum number of connection attempts before an exception is thrown when a valid host is searched. SQLException will be returned if the threshold of retries is reached with no valid connections obtained.
-      -  **connectTimeout**: indicates the maximum amount of time in milliseconds that the JDBC driver is willing to wait to set up a socket connection. **0** indicates that the connection does not time out. Only JDK-1.4 or later is supported. The default value **0**.
+      -  **connectTimeout**: indicates the maximum amount of time in milliseconds that the JDBC driver is willing to wait to set up a socket connection. **0** indicates that the connection does not time out. This parameter is available to JDK-1.4 or later versions. The default value is **0**.
 
 .. _ddm_02_0005__section144072633313:
 

umn/source/instance_management/deleting_a_ddm_instance.rst

@@ -5,21 +5,21 @@
 Deleting a DDM Instance
 =======================
 
-Prerequisites
--------------
+You can delete instances that are no longer needed.
 
-You have logged in to the DDM console.
+Precautions
+-----------
 
-.. important::
-
-   Deleted DDM instances cannot be recovered. Exercise caution when performing this operation.
+-  Deleted instances cannot be recovered. Exercise caution when performing this operation.
+-  Deleting a DDM instance will not affect its associated RDS instances.
+-  Deleting a DDM instance involves deleting its associated schemas and DDM accounts.
+-  If you need to delete data stored on the associated data nodes when deleting a DDM instance, select **Delete data on data nodes**.
 
 Procedure
 ---------
 
 #. In the instance list, locate the DDM instance that you want to delete and choose **More** > **Delete** in the **Operation** column.
+
 #. In the displayed dialog box, click **Yes**.
 
-   .. note::
-
-      -  To delete data stored on data nodes, select **Delete data on data nodes**.
+   To delete data stored on the associated data nodes, select **Delete data on data nodes**.

umn/source/instance_management/index.rst

@@ -13,7 +13,6 @@ Instance Management
 -  :ref:`Restarting a DDM Instance <ddm_06_0004>`
 -  :ref:`Deleting a DDM Instance <ddm_06_0005>`
 -  :ref:`Modifying Parameters of a DDM Instance <ddm_03_0058>`
--  :ref:`Splitting Read and Write Requests <ddm_06_0012>`
 -  :ref:`Configuring a Parameter Template <ddm_06_0020>`
 -  :ref:`Administrator Account <ddm_06_0021>`
 
@@ -29,6 +28,5 @@ Instance Management
    restarting_a_ddm_instance/index
    deleting_a_ddm_instance
    modifying_parameters_of_a_ddm_instance
-   splitting_read_and_write_requests
    configuring_a_parameter_template
    administrator_account

umn/source/instance_management/restarting_a_ddm_instance/restarting_a_ddm_instance.rst

@@ -5,15 +5,15 @@
 Restarting a DDM Instance
 =========================
 
+You may need to restart an instance to perform maintenance.
+
+The DDM instance is not available during restart, and the restart operation cannot be undone. Exercise caution when performing this operation.
+
 Prerequisites
 -------------
 
 -  You have logged in to the DDM console.
--  The DDM instance that you want to restart is in the **Running** state.
-
-   .. important::
-
-      The DDM instance is not available during restart, and the restart operation cannot be undone. Exercise caution when performing this operation.
+-  The instance is in the **Available** status.
 
 Procedure
 ---------