DWS UMN 801 version

Reviewed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com> Co-authored-by: Lu, Huayi <luhuayi@huawei.com> Co-committed-by: Lu, Huayi <luhuayi@huawei.com>
2022-12-13 12:47:57 +00:00 · 2022-12-13 12:47:57 +00:00 · c5fcb46315
commit c5fcb46315
parent 3b1f73dece
505 changed files with 17016 additions and 0 deletions
--- a/docs/dws/umn/.placeholder
+++ b/docs/dws/umn/.placeholder
--- a/docs/dws/umn/ALL_META.TXT.json
+++ b/docs/dws/umn/ALL_META.TXT.json
--- a/docs/dws/umn/CLASS.TXT.json
+++ b/docs/dws/umn/CLASS.TXT.json
--- a/docs/dws/umn/PARAMETERS.txt
+++ b/docs/dws/umn/PARAMETERS.txt
@ -0,0 +1,3 @@
 version=""
 language="en-us"
 type=""
--- a/docs/dws/umn/dws_01_00013.html
+++ b/docs/dws/umn/dws_01_00013.html
@ -0,0 +1,30 @@
 <a name="EN-US_TOPIC_0000001134560554"></a><a name="EN-US_TOPIC_0000001134560554"></a>
 <h1 class="topictitle1">Application Scenarios</h1>
 <div id="body1487833114714"><ul id="EN-US_TOPIC_0000001134560554__ul63398097103119"><li id="EN-US_TOPIC_0000001134560554__li2990020414625">Enhanced ETL + Real-time BI analysis<div class="fignone" id="EN-US_TOPIC_0000001134560554__fig10356183316362"><span class="figcap"><b>Figure 1 </b>ETL + BI analysis</span><br><span><img id="EN-US_TOPIC_0000001134560554__image3620017193616" src="figure/en-us_image_0000001134400982.png" width="465.5" height="302.503845" title="Click to enlarge" class="imgResize"></span></div>
 <p id="EN-US_TOPIC_0000001134560554__p1487069514223">The data warehouse is the pillar of the Business Intelligence (BI) system for collecting, storing, and analyzing massive amounts of data. It provides powerful business analysis support for IoT, mobile Internet, gaming, and Online to Offline (O2O) industries.</p>
 <p id="EN-US_TOPIC_0000001134560554__p1491915714476">Advantages of GaussDB(DWS) are as follows:</p>
 <ul id="EN-US_TOPIC_0000001134560554__ul1166406014838"><li id="EN-US_TOPIC_0000001134560554__li3097810514836"><strong id="EN-US_TOPIC_0000001134560554__b4939163741710">Data migration</strong>: efficient and real-time data import in batches from multiple data sources</li><li id="EN-US_TOPIC_0000001134560554__li3982912914836"><strong id="EN-US_TOPIC_0000001134560554__b275074518176">High performance</strong>: cost-effective PB-level data storage and second-level response to correlation analysis of trillions of data records</li><li id="EN-US_TOPIC_0000001134560554__li2550945814836"><strong id="EN-US_TOPIC_0000001134560554__b94980510179">Real-time</strong>: real-time consolidation of service data for timely optimization and adjustment of operation decision-making</li></ul>
 </li><li id="EN-US_TOPIC_0000001134560554__li3988477114756"><strong id="EN-US_TOPIC_0000001134560554__b842352706172112">E-commerce</strong><div class="fignone" id="EN-US_TOPIC_0000001134560554__fig1375462765610"><span class="figcap"><b>Figure 2 </b>E-commerce</span><br><span><img id="EN-US_TOPIC_0000001134560554__image934014635615" src="figure/en-us_image_0000001134400970.png" width="465.5" height="327.648027" title="Click to enlarge" class="imgResize"></span></div>
 <p id="EN-US_TOPIC_0000001134560554__p267414614531">Data of online retailers is mainly used for marketing recommendation, operating and customer analysis, and full text search.</p>
 <p id="EN-US_TOPIC_0000001134560554__p44234596144737">Advantages of GaussDB(DWS) are as follows:</p>
 <ul id="EN-US_TOPIC_0000001134560554__ul53253714141729"><li id="EN-US_TOPIC_0000001134560554__li34309479141724"><strong id="EN-US_TOPIC_0000001134560554__b1389663091813">Multi-dimensional analysis</strong>: analysis from products, users, operation, and regions</li><li id="EN-US_TOPIC_0000001134560554__li58061297141724"><strong id="EN-US_TOPIC_0000001134560554__b1227394218184">Scale-out as the business grows</strong>: on-demand cluster scale-out as the business grows</li><li id="EN-US_TOPIC_0000001134560554__li35317396141724"><strong id="EN-US_TOPIC_0000001134560554__b13473248161814">High reliability</strong>: long-term stable running of the e-commerce system</li></ul>
 </li><li id="EN-US_TOPIC_0000001134560554__li43666413141741"><strong id="EN-US_TOPIC_0000001134560554__b842352706172142">IoT</strong><div class="fignone" id="EN-US_TOPIC_0000001134560554__fig86019153713"><span class="figcap"><b>Figure 3 </b>IoT</span><br><span><img id="EN-US_TOPIC_0000001134560554__image680583153710" src="figure/en-us_image_0000001180440339.png" width="465.5" height="371.924126" title="Click to enlarge" class="imgResize"></span></div>
 <p id="EN-US_TOPIC_0000001134560554__p5259425141748">GaussDB(DWS) helps you analyze massive amounts of data from IoT in real time and perform optimization based on the results. It is widely used in industrial IoT, O2O service system, and IoV solutions.</p>
 <p id="EN-US_TOPIC_0000001134560554__p6342437144750">Advantages of GaussDB(DWS) are as follows:</p>
 <ul id="EN-US_TOPIC_0000001134560554__ul32394809141827"><li id="EN-US_TOPIC_0000001134560554__li42381797141741"><strong id="EN-US_TOPIC_0000001134560554__b1761123413253">Real-time archiving of stream data</strong>: importing stream data from IoT devices and the gateway to GaussDB(DWS) using DIS</li><li id="EN-US_TOPIC_0000001134560554__li6336331299"><strong id="EN-US_TOPIC_0000001134560554__b185714252518">Device monitoring and prediction</strong>: device monitoring, control, optimization, supply, self-diagnosis, and self-healing based on data analysis and prediction</li><li id="EN-US_TOPIC_0000001134560554__li44626134141741"><strong id="EN-US_TOPIC_0000001134560554__b1520116507253">Information recommendation</strong>: tailed recommendation based on data of users' connected devices</li></ul>
 </li></ul>
 </div>
 <div>
 <div class="familylinks">
 <div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_index.html">Service Overview</a></div>
 </div>
 </div>
 <script language="JavaScript">
 <!--
 image_size('.imgResize');
 var msg_imageMax = "view original image";
 var msg_imageClose = "close";
 //--></script>
--- a/docs/dws/umn/dws_01_00014.html
+++ b/docs/dws/umn/dws_01_00014.html
@ -0,0 +1,27 @@
 <a name="EN-US_TOPIC_0000001134400712"></a><a name="EN-US_TOPIC_0000001134400712"></a>
 <h1 class="topictitle1">Databases Monitoring</h1>
 <div id="body8662426"></div>
 <div>
 <ul class="ullinks">
 <li class="ulchildlink"><strong><a href="dws_01_00131.html">Database Monitoring Overview</a></strong><br>
 </li>
 <li class="ulchildlink"><strong><a href="dws_01_00136.html">Monitoring Metrics</a></strong><br>
 </li>
 <li class="ulchildlink"><strong><a href="dws_01_00132.html">Cluster Overview</a></strong><br>
 </li>
 <li class="ulchildlink"><strong><a href="dws_01_00133.html">Monitoring</a></strong><br>
 </li>
 <li class="ulchildlink"><strong><a href="dws_01_00175.html">Utilities</a></strong><br>
 </li>
 <li class="ulchildlink"><strong><a href="dws_01_00135.html">Settings</a></strong><br>
 </li>
 <li class="ulchildlink"><strong><a href="dws_01_00137.html">Typical Scenarios</a></strong><br>
 </li>
 </ul>
 <div class="familylinks">
 <div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0162.html">Monitoring and Alarms</a></div>
 </div>
 </div>
--- a/docs/dws/umn/dws_01_0002.html
+++ b/docs/dws/umn/dws_01_0002.html
@ -0,0 +1,85 @@
 <a name="EN-US_TOPIC_0000001134400792"></a><a name="EN-US_TOPIC_0000001134400792"></a>
 <h1 class="topictitle1">What Is GaussDB(DWS)?</h1>
 <div id="body1487833114713"><p id="EN-US_TOPIC_0000001134400792__p8060118">GaussDB(DWS) is an online data processing database that runs on the <span id="EN-US_TOPIC_0000001134400792__text89601850204412">cloud</span> infrastructure to provide scalable, fully-managed, and out-of-the-box analytic database service, freeing you from complex database management and monitoring. It is a native cloud service based on the converged data warehouse GaussDB, and is fully compatible with the standard ANSI SQL 99 and SQL 2003, as well as the PostgreSQL and Oracle ecosystems. GaussDB(DWS) provides competitive solutions for PB-level big data analysis in various industries.</p>
 <div class="section" id="EN-US_TOPIC_0000001134400792__section1034911345011"><h4 class="sectiontitle">Architecture</h4><p id="EN-US_TOPIC_0000001134400792__p7364115591818">GaussDB(DWS) employs the shared-nothing architecture and the massively parallel processing (MPP) engine, and consists of numerous independent logical nodes that do not share the system resources such as CPUs, memory, and storage. In such a system architecture, service data is separately stored on numerous nodes. Data analysis tasks are executed in parallel on the nodes where data is stored. The massively parallel data processing significantly improves response speed.</p>
 <div class="fignone" id="EN-US_TOPIC_0000001134400792__fig611912135220"><span class="figcap"><b>Figure 1 </b>Architecture</span><br><span><img id="EN-US_TOPIC_0000001134400792__image1768425814502" src="figure/en-us_image_0000001180320405.png" width="465.5" height="236.19962100000004" title="Click to enlarge" class="imgResize"></span></div>
 <ul id="EN-US_TOPIC_0000001134400792__ul15238115215170"><li id="EN-US_TOPIC_0000001134400792__li19238352141718"><strong id="EN-US_TOPIC_0000001134400792__b154010476114">Application layer</strong><p id="EN-US_TOPIC_0000001134400792__p1166063971818">Data loading tools, extract, transform, and load (ETL) tools, business intelligence (BI) tools, as well as data mining and analysis tools, can be integrated with GaussDB(DWS) through standard APIs. GaussDB(DWS) is compatible with the PostgreSQL ecosystem, and the SQL syntax is compatible with Oracle and Teradata. Applications can be smoothly migrated to GaussDB(DWS) with few changes.</p>
 </li><li id="EN-US_TOPIC_0000001134400792__li1325785591710"><strong id="EN-US_TOPIC_0000001134400792__b49673015432">API</strong><p id="EN-US_TOPIC_0000001134400792__p8538852240">Applications can connect to GaussDB(DWS) through the standard Java Database Connectivity (JDBC) 4.0 and Open Database Connectivity (ODBC) 3.5.</p>
 </li><li id="EN-US_TOPIC_0000001134400792__li6199158161720"><strong id="EN-US_TOPIC_0000001134400792__b123737206527">GaussDB(DWS) (MPP cluster)</strong><p id="EN-US_TOPIC_0000001134400792__p1966115320510">A GaussDB(DWS) cluster contains nodes of the same flavor in the same subnet. These nodes jointly provide services. Datanodes (DNs) in a cluster store data on disks. Coordinators (CNs) receive access requests from applications and return the execution results to clients. In addition, a CN splits and distributes tasks to the DNs for parallel processing.</p>
 </li><li id="EN-US_TOPIC_0000001134400792__li83237214181"><strong id="EN-US_TOPIC_0000001134400792__b756013533143">Automatic data backup</strong><p id="EN-US_TOPIC_0000001134400792__p7284341913">Cluster snapshots can be automatically backed up to the EB-level Object Storage Service (OBS), which facilitates periodic backup of the cluster during off-peak hours, ensuring data recovery after a cluster exception occurs.</p>
 <p id="EN-US_TOPIC_0000001134400792__p6197529362">A snapshot is a complete backup of GaussDB(DWS) at a specific time point, including the configuration data and service data of a cluster.</p>
 </li><li id="EN-US_TOPIC_0000001134400792__li7698141614356"><strong id="EN-US_TOPIC_0000001134400792__b84235270617464">Tool chain</strong><p id="EN-US_TOPIC_0000001134400792__p1270512016915">The parallel data loading tool General Data Service (GDS), SQL syntax migration tool Database Schema Convertor (DSC), and SQL development tool Data Studio are provided. The cluster O&amp;M can be monitored on a console.</p>
 </li></ul>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001134400792__section156354374156"><h4 class="sectiontitle">Logical Cluster Architecture</h4><p id="EN-US_TOPIC_0000001134400792__p116354375155"><a href="#EN-US_TOPIC_0000001134400792__fig9635133716155">Figure 2</a> shows the logical architecture of a GaussDB(DWS) cluster. For details about instances, see <a href="#EN-US_TOPIC_0000001134400792__en-us_topic_0059778972_tf208b79c11514cb9ae9d57ba2bef8ec9">Table 1</a>.</p>
 <div class="fignone" id="EN-US_TOPIC_0000001134400792__fig9635133716155"><a name="EN-US_TOPIC_0000001134400792__fig9635133716155"></a><a name="fig9635133716155"></a><span class="figcap"><b>Figure 2 </b>Logical cluster architecture</span><br><span><img id="EN-US_TOPIC_0000001134400792__image86362379151" src="figure/en-us_image_0000001154106106.jpg" height="275.45033269962005" width="523.6875" title="Click to enlarge" class="imgResize"></span></div>
 <div class="tablenoborder"><a name="EN-US_TOPIC_0000001134400792__en-us_topic_0059778972_tf208b79c11514cb9ae9d57ba2bef8ec9"></a><a name="en-us_topic_0059778972_tf208b79c11514cb9ae9d57ba2bef8ec9"></a><table cellpadding="4" cellspacing="0" summary="" id="EN-US_TOPIC_0000001134400792__en-us_topic_0059778972_tf208b79c11514cb9ae9d57ba2bef8ec9" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Cluster architecture description</caption><thead align="left"><tr id="EN-US_TOPIC_0000001134400792__en-us_topic_0059778972_r31478130a1a742ca98dc7e9b20ecdac1"><th align="left" class="cellrowborder" valign="top" width="10.9%" id="mcps1.3.3.4.2.4.1.1"><p id="EN-US_TOPIC_0000001134400792__en-us_topic_0059778972_a52d62fedf62c4535b647ffbb692d6af9">Name</p>
 </th>
 <th align="left" class="cellrowborder" valign="top" width="35.709999999999994%" id="mcps1.3.3.4.2.4.1.2"><p id="EN-US_TOPIC_0000001134400792__en-us_topic_0059778972_a42fc055331ab4fe4b0d0f03b8a4eddee">Description</p>
 </th>
 <th align="left" class="cellrowborder" valign="top" width="53.39%" id="mcps1.3.3.4.2.4.1.3"><p id="EN-US_TOPIC_0000001134400792__en-us_topic_0059778972_p1975868134855">Remarks</p>
 </th>
 </tr>
 </thead>
 <tbody><tr id="EN-US_TOPIC_0000001134400792__en-us_topic_0059778972_r01c4f62cc0d24b0e859ac2d154b99d71"><td class="cellrowborder" valign="top" width="10.9%" headers="mcps1.3.3.4.2.4.1.1 "><p id="EN-US_TOPIC_0000001134400792__en-us_topic_0059778972_ad4573e78f711427ebe634933c8fc6316">Global Transaction Manager (GTM)</p>
 </td>
 <td class="cellrowborder" valign="top" width="35.709999999999994%" headers="mcps1.3.3.4.2.4.1.2 "><p id="EN-US_TOPIC_0000001134400792__en-us_topic_0059778972_p57045919142055">Generates and maintains the globally unique information, such as the transaction ID, transaction snapshot, and timestamp.</p>
 </td>
 <td class="cellrowborder" valign="top" width="53.39%" headers="mcps1.3.3.4.2.4.1.3 "><p id="EN-US_TOPIC_0000001134400792__en-us_topic_0059778972_p41221967135025">The cluster includes only one pair of GTMs: one primary GTM and one standby GTM.</p>
 </td>
 </tr>
 <tr id="EN-US_TOPIC_0000001134400792__en-us_topic_0059778972_rc559714676a24e88959dd96c6fcf3ed0"><td class="cellrowborder" valign="top" width="10.9%" headers="mcps1.3.3.4.2.4.1.1 "><p id="EN-US_TOPIC_0000001134400792__en-us_topic_0059778972_a05bcdf822cc649e799f328b4a0a5c186">Workload Manager (WLM)</p>
 </td>
 <td class="cellrowborder" valign="top" width="35.709999999999994%" headers="mcps1.3.3.4.2.4.1.2 "><p id="EN-US_TOPIC_0000001134400792__en-us_topic_0059778972_adf4e98251a8c4262a99378daab4429d0">WLM controls allocation of system resources to prevent service congestion and system crash resulting from excessive workload.</p>
 </td>
 <td class="cellrowborder" valign="top" width="53.39%" headers="mcps1.3.3.4.2.4.1.3 "><p id="EN-US_TOPIC_0000001134400792__en-us_topic_0059778972_p34338187134855">You do not need to specify names of hosts where WLMs are to be deployed, because the installation program automatically installs a WLM on each host.</p>
 </td>
 </tr>
 <tr id="EN-US_TOPIC_0000001134400792__en-us_topic_0059778972_rf49a3a51a72e413a872f64e4f6213190"><td class="cellrowborder" valign="top" width="10.9%" headers="mcps1.3.3.4.2.4.1.1 "><p id="EN-US_TOPIC_0000001134400792__en-us_topic_0059778972_a9ae468a09d4d4e148d4b779e34772d5a">Coordinator (CN)</p>
 </td>
 <td class="cellrowborder" valign="top" width="35.709999999999994%" headers="mcps1.3.3.4.2.4.1.2 "><p id="EN-US_TOPIC_0000001134400792__en-us_topic_0059778972_a2a8f3893dd5c4d049d06a79600bf4af6">A CN receives access requests from applications, and returns execution results to the client; splits tasks and allocates task fragments to different DNs for parallel processing.</p>
 </td>
 <td class="cellrowborder" valign="top" width="53.39%" headers="mcps1.3.3.4.2.4.1.3 "><p id="EN-US_TOPIC_0000001134400792__en-us_topic_0059778972_p17443385135113">CNs in a cluster have equivalent roles and return the same result for the same DML statement. Load balancers can be added between CNs and applications to ensure that CNs are transparent to applications. If a CN is faulty, the load balancer connects its applications to another CN.</p>
 <p id="EN-US_TOPIC_0000001134400792__p35494487201349">CNs need to connect to each other in the distributed transaction architecture. To reduce heavy load caused by excessive threads on GTMs, no more than 10 CNs should be configured in a cluster.</p>
 <p id="EN-US_TOPIC_0000001134400792__p6552761911195">GaussDB(DWS) handles the global resource load in a cluster using the Central Coordinator (CCN) for adaptive dynamic load management. When the cluster is started for the first time, the CM selects the CN with the smallest ID as the CCN. If the CCN is faulty, CM replaces it with a new one.</p>
 </td>
 </tr>
 <tr id="EN-US_TOPIC_0000001134400792__en-us_topic_0059778972_r2f8cae55ffca40aeb341d719a8c6f40a"><td class="cellrowborder" valign="top" width="10.9%" headers="mcps1.3.3.4.2.4.1.1 "><p id="EN-US_TOPIC_0000001134400792__en-us_topic_0059778972_a417416a2bca649198ca004a07cd239f7">Datanode (DN)</p>
 </td>
 <td class="cellrowborder" valign="top" width="35.709999999999994%" headers="mcps1.3.3.4.2.4.1.2 "><p id="EN-US_TOPIC_0000001134400792__en-us_topic_0059778972_a56328aee18ec418bb7573975145e44f5">A DN stores service data by column or row or in the hybrid mode, executes data query tasks, and returns execution results to CNs.</p>
 </td>
 <td class="cellrowborder" valign="top" width="53.39%" headers="mcps1.3.3.4.2.4.1.3 "><p id="EN-US_TOPIC_0000001134400792__p12119124413">A cluster consists of multiple DNs and each DN stores part of data. If no HA solution is available for DNs, data cannot be accessed when a DN is faulty.</p>
 <p id="EN-US_TOPIC_0000001134400792__en-us_topic_0059778972_p48985960135125"></p>
 </td>
 </tr>
 <tr id="EN-US_TOPIC_0000001134400792__en-us_topic_0059778972_ra41c3ee320ba4e22a0a5b0c2d8bf14bf"><td class="cellrowborder" valign="top" width="10.9%" headers="mcps1.3.3.4.2.4.1.1 "><p id="EN-US_TOPIC_0000001134400792__en-us_topic_0059778972_ab7085c16abd94fd9a223a5d97205d698">Storage</p>
 </td>
 <td class="cellrowborder" valign="top" width="35.709999999999994%" headers="mcps1.3.3.4.2.4.1.2 "><p id="EN-US_TOPIC_0000001134400792__en-us_topic_0059778972_af842f867408b4c64afeef3f91cf7f529">Functions as the server's local storage resources to store data permanently.</p>
 </td>
 <td class="cellrowborder" valign="top" width="53.39%" headers="mcps1.3.3.4.2.4.1.3 "><p id="EN-US_TOPIC_0000001134400792__en-us_topic_0059778972_p8701423134855">-</p>
 </td>
 </tr>
 </tbody>
 </table>
 </div>
 <p id="EN-US_TOPIC_0000001134400792__p2640133713152">DNs in a cluster store data on disks. <a href="#EN-US_TOPIC_0000001134400792__fig138416215395">Figure 3</a> describes the objects on each DN and the relationships among them logically.</p>
 <ul id="EN-US_TOPIC_0000001134400792__ul1064013710156"><li id="EN-US_TOPIC_0000001134400792__li11640143711518">A database manages various data objects and is isolated from other databases.</li><li id="EN-US_TOPIC_0000001134400792__li76408374159">A datafile segment stores data in only one table. A table containing more than 1 GB of data is stored in multiple data file segments.</li><li id="EN-US_TOPIC_0000001134400792__li2640193718155">A table belongs only to one database.</li><li id="EN-US_TOPIC_0000001134400792__li1641163711159">A block is the basic unit of database management, with a default size of 8 KB.</li></ul>
 <p id="EN-US_TOPIC_0000001134400792__p5641837101516">Data can be distributed in replication, round-robin, or hash mode. You can specify the distribution mode during table creation.</p>
 <div class="fignone" id="EN-US_TOPIC_0000001134400792__fig138416215395"><a name="EN-US_TOPIC_0000001134400792__fig138416215395"></a><a name="fig138416215395"></a><span class="figcap"><b>Figure 3 </b>Logical database architecture</span><br><span><img id="EN-US_TOPIC_0000001134400792__image5842102173913" src="figure/en-us_image_0000001200065787.png" height="302.53177500000004" width="332.1675" title="Click to enlarge" class="imgResize"></span></div>
 </div>
 </div>
 <div>
 <div class="familylinks">
 <div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_index.html">Service Overview</a></div>
 </div>
 </div>
 <script language="JavaScript">
 <!--
 image_size('.imgResize');
 var msg_imageMax = "view original image";
 var msg_imageClose = "close";
 //--></script>
--- a/docs/dws/umn/dws_01_0003.html
+++ b/docs/dws/umn/dws_01_0003.html
@ -0,0 +1,30 @@
 <a name="EN-US_TOPIC_0000001134400796"></a><a name="EN-US_TOPIC_0000001134400796"></a>
 <h1 class="topictitle1">Related Services</h1>
 <div id="body1487833114714"><p id="EN-US_TOPIC_0000001134400796__p1740316229236"></p>
 <div class="section" id="EN-US_TOPIC_0000001134400796__section4573770192847"><h4 class="sectiontitle">IAM</h4><p id="EN-US_TOPIC_0000001134400796__p1054201119298">GaussDB(DWS) uses Identity and Access Management (IAM) for authentication and authorization.</p>
 <p id="EN-US_TOPIC_0000001134400796__p59253374111244">Users who have the <strong id="EN-US_TOPIC_0000001134400796__b76144512286">DWS Administrator</strong> permissions can fully utilize GaussDB(DWS). To obtain the permissions, contact a user with the <strong id="EN-US_TOPIC_0000001134400796__b8494105912287">Security Administrator</strong> permissions or directly create a user with the <strong id="EN-US_TOPIC_0000001134400796__b048331018290">DWS Administrator</strong> permissions. Users granted the <strong id="EN-US_TOPIC_0000001134400796__b127144043010">DWS Database Access</strong> permissions can generate temporary database user credentials based on IAM users to connect to databases in the data warehouse clusters.</p>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001134400796__section26050418152457"><h4 class="sectiontitle">ECS</h4><p id="EN-US_TOPIC_0000001134400796__p63865863152554">GaussDB(DWS) uses an ECS as a cluster node. </p>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001134400796__section43260061153951"><h4 class="sectiontitle">VPC</h4><p id="EN-US_TOPIC_0000001134400796__p4117294215403">GaussDB(DWS) uses the Virtual Private Cloud (VPC) service to provide a network topology for clusters to isolate clusters and control access.</p>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001134400796__section39167995154954"><h4 class="sectiontitle">OBS</h4><p id="EN-US_TOPIC_0000001134400796__p660248115502">GaussDB(DWS) uses OBS to convert cluster data and external data, satisfying the requirements for secure, reliable, and cost-effective storage.</p>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001134400796__section10180113633117"><h4 class="sectiontitle">MRS</h4><p id="EN-US_TOPIC_0000001134400796__p7445125465412">Data can be migrated from MRS to GaussDB(DWS) clusters for analysis after the data is processed by Hadoop.</p>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001134400796__section5873320693514"><h4 class="sectiontitle">Cloud Eye</h4><p id="EN-US_TOPIC_0000001134400796__p1688976593530">GaussDB(DWS) uses Cloud Eye to monitor cluster performance metrics, delivering status information in a concise and efficient manner. Cloud Eye supports alarm customization so that you are notified of the exception instantly.</p>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001134400796__section5427009410155"><h4 class="sectiontitle">CTS</h4><p id="EN-US_TOPIC_0000001134400796__p49497466101520">GaussDB(DWS) uses Cloud Trace Service (CTS) to audit your non-query operations on the management console to ensure that no invalid or unauthorized operations are performed, enhancing service security management.</p>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001134400796__section0933831312"><h4 class="sectiontitle">TMS</h4><p id="EN-US_TOPIC_0000001134400796__p165281097610">With Tag Management Service (TMS), GaussDB(DWS) can provide centralized tag management and resource classification functions across regions and services. You can customize tags to classify and locate resources.</p>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001134400796__section54601222115912"><h4 class="sectiontitle">DNS</h4><p id="EN-US_TOPIC_0000001134400796__p102263561013">GaussDB(DWS) uses Domain Name Service (DNS) to provide the cluster IP addresses mapped from domain names.</p>
 </div>
 </div>
 <div>
 <div class="familylinks">
 <div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_index.html">Service Overview</a></div>
 </div>
 </div>
--- a/docs/dws/umn/dws_01_0004.html
+++ b/docs/dws/umn/dws_01_0004.html
@ -0,0 +1,17 @@
 <a name="EN-US_TOPIC_0000001134560542"></a><a name="EN-US_TOPIC_0000001134560542"></a>
 <h1 class="topictitle1">Concepts</h1>
 <div id="body1487833114713"></div>
 <div>
 <ul class="ullinks">
 <li class="ulchildlink"><strong><a href="dws_01_0005.html">GaussDB(DWS) Management Concepts</a></strong><br>
 </li>
 <li class="ulchildlink"><strong><a href="dws_01_0006.html">GaussDB(DWS) Database Concepts</a></strong><br>
 </li>
 </ul>
 <div class="familylinks">
 <div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_index.html">Service Overview</a></div>
 </div>
 </div>
--- a/docs/dws/umn/dws_01_0005.html
+++ b/docs/dws/umn/dws_01_0005.html
@ -0,0 +1,20 @@
 <a name="EN-US_TOPIC_0000001180320183"></a><a name="EN-US_TOPIC_0000001180320183"></a>
 <h1 class="topictitle1">GaussDB(DWS) Management Concepts </h1>
 <div id="body1487833114713"><div class="section" id="EN-US_TOPIC_0000001180320183__section17248514161134"><h4 class="sectiontitle">Cluster</h4><p id="EN-US_TOPIC_0000001180320183__p54952384161134">A cluster is a server group that consists of multiple nodes. GaussDB(DWS) is organized using clusters. A data warehouse cluster contains nodes with the same flavor in the same subnet. These nodes work together to provide services.</p>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001180320183__section2062812517412"><h4 class="sectiontitle">Node</h4><p id="EN-US_TOPIC_0000001180320183__p4766913717414">Each data warehouse cluster contains at least three nodes, all of which support data storage and analysis.</p>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001180320183__section33777514161134"><h4 class="sectiontitle">Flavor</h4><p id="EN-US_TOPIC_0000001180320183__p51624102161134">You need to specify the node flavors when you create a data warehouse cluster. CPU, memory, and storage resources vary depending on node flavors.</p>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001180320183__section17640691161134"><h4 class="sectiontitle">Snapshot</h4><p id="EN-US_TOPIC_0000001180320183__p1922013546820">You can create snapshots to back up GaussDB(DWS) cluster data. A snapshot is retained until you delete it on the management console. Automated snapshots cannot be manually deleted. Snapshots will occupy your OBS quotas.</p>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001180320183__section25776682114018"><h4 class="sectiontitle">Project</h4><p id="EN-US_TOPIC_0000001180320183__p50745405114023">Projects are used to group and isolate OpenStack resources (computing resources, storage resources, and network resources). A project can be a department or a project team. Multiple projects can be created for one account.</p>
 </div>
 </div>
 <div>
 <div class="familylinks">
 <div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0004.html">Concepts</a></div>
 </div>
 </div>
--- a/docs/dws/umn/dws_01_0006.html
+++ b/docs/dws/umn/dws_01_0006.html
@ -0,0 +1,24 @@
 <a name="EN-US_TOPIC_0000001134560598"></a><a name="EN-US_TOPIC_0000001134560598"></a>
 <h1 class="topictitle1">GaussDB(DWS) Database Concepts</h1>
 <div id="body1487898419737"><div class="section" id="EN-US_TOPIC_0000001134560598__section4715959816640"><h4 class="sectiontitle">Database</h4><p id="EN-US_TOPIC_0000001134560598__p494262216642">A data warehouse cluster is an analysis-oriented relational database platform that supports online analysis.</p>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001134560598__section53675525104036"><h4 class="sectiontitle">OLAP</h4><p id="EN-US_TOPIC_0000001134560598__p63990931104052">OLAP is a major function of data warehouse clusters. It supports complex analysis, provides decision-making support tailored to analysis results, and delivers intuitive query results.</p>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001134560598__section2895605910396"><h4 class="sectiontitle">MPP</h4><p id="EN-US_TOPIC_0000001134560598__p10392978103911">On each node in the data warehouse cluster, memory computing and disk storage systems are independent from each other. With MPP, GaussDB(DWS) distributes service data to different nodes based on the database model and application characteristics. Nodes are connected through the network and collaboratively process computing tasks as a cluster and provide database services that meet service needs.</p>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001134560598__section3099522411559"><h4 class="sectiontitle">Shared-Nothing Architecture</h4><p id="EN-US_TOPIC_0000001134560598__p2758518511559">The shared-nothing architecture is a distributed computing architecture. Each node is independent so that nodes do not compete for resources, which improves work efficiency.</p>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001134560598__section62224423104913"><h4 class="sectiontitle">Database Version</h4><p id="EN-US_TOPIC_0000001134560598__p17815638104934">Each data warehouse cluster has a specific database version. You can check the version when creating a data warehouse cluster.</p>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001134560598__section63032001112247"><h4 class="sectiontitle">Database Connection</h4><p id="EN-US_TOPIC_0000001134560598__p59259113112251">You can use a client to connect to a GaussDB(DWS) cluster in the <span id="EN-US_TOPIC_0000001134560598__text20373145314355">cloud</span> and over the Internet.</p>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001134560598__section2400664121910"><h4 class="sectiontitle">Database User</h4><p id="EN-US_TOPIC_0000001134560598__p40041287121913">You can add and control users who can access the database of a data warehouse cluster by assigning specific permissions to them. The database administrator generated when you create a cluster is the default database user.</p>
 </div>
 </div>
 <div>
 <div class="familylinks">
 <div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0004.html">Concepts</a></div>
 </div>
 </div>
--- a/docs/dws/umn/dws_01_0007.html
+++ b/docs/dws/umn/dws_01_0007.html
@ -0,0 +1,31 @@
 <a name="EN-US_TOPIC_0000001180320213"></a><a name="EN-US_TOPIC_0000001180320213"></a>
 <h1 class="topictitle1">Advantages</h1>
 <div id="body1558517676664"><p id="EN-US_TOPIC_0000001180320213__p6031243294447">GaussDB(DWS) uses the GaussDB database kernel and is compatible with PostgreSQL 9.2.4. It transforms from a single OLTP database to an enterprise-level distributed OLAP database oriented to massive data analysis based on the massively parallel processing (MPP) architecture.</p>
 <p id="EN-US_TOPIC_0000001180320213__p6100864594526">Unlike conventional data warehouses, GaussDB(DWS) excels in massive data processing and general platform management with the following benefits:</p>
 <p id="EN-US_TOPIC_0000001180320213__p1770113116457"><strong id="EN-US_TOPIC_0000001180320213__b1624163732316">Ease of use</strong></p>
 <ul id="EN-US_TOPIC_0000001180320213__ul1192714140543"><li id="EN-US_TOPIC_0000001180320213__li5927714155412">Visualized one-stop management<p id="EN-US_TOPIC_0000001180320213__p207810184319"><a name="EN-US_TOPIC_0000001180320213__li5927714155412"></a><a name="li5927714155412"></a>GaussDB(DWS) allows you to easily complete the entire process from project concept to production deployment. With the GaussDB(DWS) management console, you can obtain a high-performance and highly available enterprise-level data warehouse cluster within several minutes. Data warehouse software or data warehouse servers are not required.</p>
 <p id="EN-US_TOPIC_0000001180320213__p19993162895416">With just a few clicks, you can easily connect applications to the data warehouse, back up data, restore data, and monitor data warehouse resources and performance.</p>
 </li><li id="EN-US_TOPIC_0000001180320213__li6829173814559">Seamless integration with big data<p id="EN-US_TOPIC_0000001180320213__p18654440135512"><a name="EN-US_TOPIC_0000001180320213__li6829173814559"></a><a name="li6829173814559"></a>Without the need to migrate data, you can use standard SQL statements to directly query data on HDFS and OBS.</p>
 </li><li id="EN-US_TOPIC_0000001180320213__li13567101967">Heterogeneous database migration tools<p id="EN-US_TOPIC_0000001180320213__p11138183363"><a name="EN-US_TOPIC_0000001180320213__li13567101967"></a><a name="li13567101967"></a>GaussDB(DWS) provides various migration tools to migrate SQL scripts of Oracleand Teradata to GaussDB(DWS).</p>
 </li></ul>
 <p id="EN-US_TOPIC_0000001180320213__p14986129145017"><strong id="EN-US_TOPIC_0000001180320213__b16541250172518">High performance</strong></p>
 <ul id="EN-US_TOPIC_0000001180320213__ul16978146191611"><li id="EN-US_TOPIC_0000001180320213__li587015410166">Cloud-based distributed architecture<p id="EN-US_TOPIC_0000001180320213__p2384185618165"><a name="EN-US_TOPIC_0000001180320213__li587015410166"></a><a name="li587015410166"></a>GaussDB(DWS) adopts the MPP-based database so that service data is separately stored on numerous nodes. Data analysis tasks are executed in parallel on the nodes where data is stored. The massively parallel data processing significantly improves response speed.</p>
 </li><li id="EN-US_TOPIC_0000001180320213__li1997813467167">Query response to trillions of data records within seconds<p id="EN-US_TOPIC_0000001180320213__p131041658141720"><a name="EN-US_TOPIC_0000001180320213__li1997813467167"></a><a name="li1997813467167"></a>GaussDB(DWS) improves data query performance by executing multi-thread operators in parallel, running commands in registers in parallel with the vectorized computing engine, and reducing redundant judgment conditions using LLVM.</p>
 <p id="EN-US_TOPIC_0000001180320213__p1426423173218">GaussDB(DWS) provides you with a better data compression ratio (column-store), better indexing (column-store), and higher point update and query (row-store) performance.</p>
 </li><li id="EN-US_TOPIC_0000001180320213__li6828131174311">Fast data loading<p id="EN-US_TOPIC_0000001180320213__p3228133419433"><a name="EN-US_TOPIC_0000001180320213__li6828131174311"></a><a name="li6828131174311"></a>GDS is a tool that helps you with high-speed massively parallel data loading.</p>
 </li></ul>
 <p id="EN-US_TOPIC_0000001180320213__p1158713055011"><strong id="EN-US_TOPIC_0000001180320213__b2855114411256">High scalability</strong></p>
 <ul id="EN-US_TOPIC_0000001180320213__ul78605212443"><li id="EN-US_TOPIC_0000001180320213__li138611021134415">On-demand scale-out: With the shared-nothing open architecture, nodes can be added at any time to enhance the data storage, query, and analysis capabilities of the system.</li><li id="EN-US_TOPIC_0000001180320213__li20861521114410">Enhanced linear performance after scale-out: The capacity and performance increase linearly with the cluster scale. The linear rate is 0.8.</li><li id="EN-US_TOPIC_0000001180320213__li1861112115446">Service continuity: During scale-out, data can be added, deleted, modified, and queried, and DDL operations (<strong id="EN-US_TOPIC_0000001180320213__b193984207321">DROP</strong>/<strong id="EN-US_TOPIC_0000001180320213__b18749141893217">TRUNCATE</strong>/<strong id="EN-US_TOPIC_0000001180320213__b188631315113217">ALTER TABLE</strong>) can be performed. Online table-level scale-out ensures service continuity.</li></ul>
 <p id="EN-US_TOPIC_0000001180320213__p165903323451"><strong id="EN-US_TOPIC_0000001180320213__b201191347143213">Robust reliability</strong></p>
 <ul id="EN-US_TOPIC_0000001180320213__ul82779085716"><li id="EN-US_TOPIC_0000001180320213__li476413451473">ACID<p id="EN-US_TOPIC_0000001180320213__p39168473713"><a name="EN-US_TOPIC_0000001180320213__li476413451473"></a><a name="li476413451473"></a>Support for the atomicity, consistency, isolation, and durability (ACID) feature, which ensures strong data consistency for distributed transactions.</p>
 </li><li id="EN-US_TOPIC_0000001180320213__li15287142010580">Comprehensive HA design<p id="EN-US_TOPIC_0000001180320213__p1961452325818"><a name="EN-US_TOPIC_0000001180320213__li15287142010580"></a><a name="li15287142010580"></a>All software processes of GaussDB(DWS) are in active/standby mode. Logical components such as the CNs and DNs of each cluster also work in active/standby mode. This ensures data reliability and consistency when any single point of failure (SPOF) occurs.</p>
 </li><li id="EN-US_TOPIC_0000001180320213__li2074831872312">High security<p id="EN-US_TOPIC_0000001180320213__p74322163241"><a name="EN-US_TOPIC_0000001180320213__li2074831872312"></a><a name="li2074831872312"></a>GaussDB(DWS) supports transparent data encryption and can interconnect with the Database Security Service (DBSS) to better protect user privacy and data security with network isolation and security group rule setting options. In addition, GaussDB(DWS) supports automatic full and incremental backup of data, improving data reliability.</p>
 </li></ul>
 </div>
 <div>
 <div class="familylinks">
 <div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_index.html">Service Overview</a></div>
 </div>
 </div>
--- a/docs/dws/umn/dws_01_0008.html
+++ b/docs/dws/umn/dws_01_0008.html
@ -0,0 +1,34 @@
 <a name="EN-US_TOPIC_0000001180440157"></a><a name="EN-US_TOPIC_0000001180440157"></a>
 <h1 class="topictitle1">Cluster Upgrade</h1>
 <div id="body1532402323813"><p id="EN-US_TOPIC_0000001180440157__p184711857102810">After you create a data warehouse cluster, the system automatically configures a random maintenance window for the cluster. Alternatively, you can customize a maintenance window as required. For details about how to view and configure the maintenance window, see <a href="#EN-US_TOPIC_0000001180440157__section1583412504297">Configuring the Maintenance Window</a>.</p>
 <p id="EN-US_TOPIC_0000001180440157__p8060118">The validity period of the maintenance window (maximum maintenance duration) is 4 hours. During this period, you can upgrade the cluster, install operating system patches, and harden the system. If no maintenance tasks are performed within the planned maintenance window, the cluster continues to run properly until the next maintenance window. GaussDB(DWS) will notify you of any cluster O&amp;M operation by sending SMS messages. Exercise caution when performing operations on the cluster during the O&amp;M period.</p>
 <p id="EN-US_TOPIC_0000001180440157__p417322713614">If the upgrade affects the current query requests or service running, contact technical support for emergency handling.</p>
 <p id="EN-US_TOPIC_0000001180440157__p761016102454">A cluster is charged by hour as long as it is in the <strong id="EN-US_TOPIC_0000001180440157__b113120414382">Available</strong> state. Since the cluster is charged by hour, you will not see any difference in the bills if a faulty node or system upgrade causes a short interruption, for example, 15 minutes. If such events cause major system interruption, which is a very rare case, you will not be charged for those downtime hours.</p>
 <div class="section" id="EN-US_TOPIC_0000001180440157__section820391923314"><h4 class="sectiontitle">Upgrading a Cluster</h4><p id="EN-US_TOPIC_0000001180440157__p4388530815716">You do not need to care about GaussDB(DWS) cluster patching or upgrading because GaussDB(DWS) will handle version upgrade automatically. After GaussDB(DWS) is upgraded, the service automatically upgrades the clusters to the latest version within the maintenance window. During the upgrade, the cluster is automatically restarted and cannot provide services for a short period of time. Therefore, you are advised to set a suitable time range when the number of connected users and the number of active tasks are small.</p>
 <div class="note" id="EN-US_TOPIC_0000001180440157__note18499153772516"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001180440157__p1149913715257">After the cluster is upgraded, it cannot be rolled back.</p>
 </div></div>
 <p id="EN-US_TOPIC_0000001180440157__p1448801517493">The following figure shows the cluster version.</p>
 <div class="fignone" id="EN-US_TOPIC_0000001180440157__fig20809175412226"><span class="figcap"><b>Figure 1 </b>Version description</span><br><span><img id="EN-US_TOPIC_0000001180440157__image9910157182211" src="figure/en-us_image_0000001134400976.png" width="234.41250000000002" height="178.6722" title="Click to enlarge" class="imgResize"></span></div>
 <ul id="EN-US_TOPIC_0000001180440157__ul17243116115012"><li id="EN-US_TOPIC_0000001180440157__li67071942414"><strong id="EN-US_TOPIC_0000001180440157__b14754131912712">Service patch upgrade</strong>: The last digit of cluster version <em id="EN-US_TOPIC_0000001180440157__i842352697165623_1">X.X.X</em> is changed. For example, the cluster is upgraded from 1.1.0 to 1.1.1.<ul id="EN-US_TOPIC_0000001180440157__ul3865489315824"><li id="EN-US_TOPIC_0000001180440157__li1027067015824">Duration: The whole process will take less than 10 minutes.</li><li id="EN-US_TOPIC_0000001180440157__li857124515824">Impact on services: During this period, services will be interrupted for 1 to 3 minutes.</li></ul>
 </li><li id="EN-US_TOPIC_0000001180440157__li42438160505"><strong id="EN-US_TOPIC_0000001180440157__b33671010911">Service upgrade</strong>: The first two digits of cluster version <em id="EN-US_TOPIC_0000001180440157__i7521510392">X.X.X</em> are changed. For example, the cluster is upgraded from 1.1.0 to 1.2.0.<ul id="EN-US_TOPIC_0000001180440157__ul5315405915828"><li id="EN-US_TOPIC_0000001180440157__li1360771515828">Duration: The whole process will take less than 30 minutes.</li><li id="EN-US_TOPIC_0000001180440157__li2543351815828">Impact on services: During this period, the database cannot be accessed.</li></ul>
 </li></ul>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001180440157__section1583412504297"><a name="EN-US_TOPIC_0000001180440157__section1583412504297"></a><a name="section1583412504297"></a><h4 class="sectiontitle">Configuring the Maintenance Window</h4><ol id="EN-US_TOPIC_0000001180440157__ol1169623853011"><li id="EN-US_TOPIC_0000001180440157__li186964380309"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001180440157__li169613833019"><span>Click <span class="uicontrol" id="EN-US_TOPIC_0000001180440157__uf249e9a432364710a9c31a3f5d8a6aad"><b>Clusters</b></span>.</span></li><li id="EN-US_TOPIC_0000001180440157__li97131838203014"><span>In the cluster list, click the name of the target cluster. The <span class="parmname" id="EN-US_TOPIC_0000001180440157__parmname10416912115225"><b>Basic Information</b></span> page is displayed.</span><p><p id="EN-US_TOPIC_0000001180440157__p1471393819303">In the <span class="parmname" id="EN-US_TOPIC_0000001180440157__parmname1740518172203"><b>Cluster Information</b></span> area, you can view the maintenance window.</p>
 </p></li><li id="EN-US_TOPIC_0000001180440157__li1840025516559"><span>Click <span class="uicontrol" id="EN-US_TOPIC_0000001180440157__uicontrol5861112852015"><b>Configure</b></span> next to <span class="parmname" id="EN-US_TOPIC_0000001180440157__parmname18868112892012"><b>Maintenance Window</b></span>.</span></li><li id="EN-US_TOPIC_0000001180440157__li179481727102815"><span>In the dialog box that is displayed, configure the maintenance window.</span><p><div class="fignone" id="EN-US_TOPIC_0000001180440157__fig37133387306"><span class="figcap"><b>Figure 2 </b>Configuring the maintenance window</span><br><span><img id="EN-US_TOPIC_0000001180440157__image152641152001" src="figure/en-us_image_0000001134560768.png" width="465.5" height="275.500057" title="Click to enlarge" class="imgResize"></span></div>
 </p></li><li id="EN-US_TOPIC_0000001180440157__li3361142018292"><span>Click <span class="uicontrol" id="EN-US_TOPIC_0000001180440157__uicontrol724010315539"><b>OK</b></span>.</span></li></ol>
 </div>
 </div>
 <div>
 <div class="familylinks">
 <div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0600.html">Clusters</a></div>
 </div>
 </div>
 <script language="JavaScript">
 <!--
 image_size('.imgResize');
 var msg_imageMax = "view original image";
 var msg_imageClose = "close";
 //--></script>
--- a/docs/dws/umn/dws_01_00081.html
+++ b/docs/dws/umn/dws_01_00081.html
@ -0,0 +1,29 @@
 <a name="EN-US_TOPIC_0000001134560564"></a><a name="EN-US_TOPIC_0000001134560564"></a>
 <h1 class="topictitle1">DR Overview</h1>
 <div id="body0000001082434743"><div class="section" id="EN-US_TOPIC_0000001134560564__section2604638151110"><h4 class="sectiontitle">Overview</h4><p id="EN-US_TOPIC_0000001134560564__p4976204281119">A homogeneous GaussDB(DWS) DR cluster is deployed in another AZ. If the production cluster fails to provide read and write services due to natural disasters in the specified region or cluster internal faults, the DR cluster becomes the production cluster to ensure service continuity. The following figure shows the architecture.</p>
 <p id="EN-US_TOPIC_0000001134560564__p4243512435"><span><img id="EN-US_TOPIC_0000001134560564__image19724223458" src="figure/en-us_image_0000001172481700.png" width="420.94500000000005" height="308.73728900000003" title="Click to enlarge" class="imgResize"></span></p>
 <div class="note" id="EN-US_TOPIC_0000001134560564__note127521947567"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001134560564__ul19922571937"><li id="EN-US_TOPIC_0000001134560564__li6922176312">This feature is supported only in cluster version 8.1.1 or later.</li></ul>
 </div></div>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001134560564__section252739164515"><h4 class="sectiontitle">DR Features</h4><ul id="EN-US_TOPIC_0000001134560564__ul1423621715215"><li id="EN-US_TOPIC_0000001134560564__li102364175525">Multi-form DR<ul id="EN-US_TOPIC_0000001134560564__ul77261722185217"><li id="EN-US_TOPIC_0000001134560564__li19236217205219">Cross-AZ DR</li><li id="EN-US_TOPIC_0000001134560564__li923651795219">Multiple data synchronization modes: synchronization layer based on mutual trust</li></ul>
 </li><li id="EN-US_TOPIC_0000001134560564__li7237817105217">Low TCO<ul id="EN-US_TOPIC_0000001134560564__ul53251526135218"><li id="EN-US_TOPIC_0000001134560564__li623713172523">Heterogeneous deployment (logical homogeneity)</li><li id="EN-US_TOPIC_0000001134560564__li723721715522">Cluster-level DR</li></ul>
 </li><li id="EN-US_TOPIC_0000001134560564__li7237161735210">Visual console<ul id="EN-US_TOPIC_0000001134560564__ul1574016296521"><li id="EN-US_TOPIC_0000001134560564__li1823812173526">Automatic and one-click DR drills</li></ul>
 </li></ul>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001134560564__section41301536181415"><h4 class="sectiontitle">Constraints and Limitations</h4><ul id="EN-US_TOPIC_0000001134560564__ul15658181972013"><li id="EN-US_TOPIC_0000001134560564__li665881912012">During data synchronization, the DR cluster cannot provide read or write services.</li><li id="EN-US_TOPIC_0000001134560564__li665951972017">When the DR task is stopped or abnormal but the DR cluster is normal, the DR cluster can provide the read service. After the DR switchover is successful, the DR cluster can provide the read and write services.</li><li id="EN-US_TOPIC_0000001134560564__li10659151913204">When the DR task is created, the snapshot function of the production cluster is normal, but that of the DR cluster is disabled. Besides, snapshot restoration of both clusters is disabled.</li><li id="EN-US_TOPIC_0000001134560564__li365919197202">Logical clusters are not supported.</li><li id="EN-US_TOPIC_0000001134560564__li3659419172019">DR refers to dual-cluster DR of the same tenant.</li><li id="EN-US_TOPIC_0000001134560564__li106852025155210">The production cluster and DR cluster are in the same VPC and of the same version.</li></ul>
 </div>
 </div>
 <div>
 <div class="familylinks">
 <div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0080.html">Cluster DR</a></div>
 </div>
 </div>
 <script language="JavaScript">
 <!--
 image_size('.imgResize');
 var msg_imageMax = "view original image";
 var msg_imageClose = "close";
 //--></script>
--- a/docs/dws/umn/dws_01_00082.html
+++ b/docs/dws/umn/dws_01_00082.html
@ -0,0 +1,34 @@
 <a name="EN-US_TOPIC_0000001134400768"></a><a name="EN-US_TOPIC_0000001134400768"></a>
 <h1 class="topictitle1">Creating a DR Task</h1>
 <div id="body0000001082434745"><div class="section" id="EN-US_TOPIC_0000001134400768__section13159138192819"><h4 class="sectiontitle">Prerequisites</h4><p id="EN-US_TOPIC_0000001134400768__p1340684692818">You can create a DR task only when the cluster is in the <strong id="EN-US_TOPIC_0000001134400768__b135771451205617">Available</strong> or <strong id="EN-US_TOPIC_0000001134400768__b06007547569">Unbalanced</strong> state.</p>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001134400768__section1696913483283"><h4 class="sectiontitle">Procedure</h4><ol id="EN-US_TOPIC_0000001134400768__ol7180115316295"><li id="EN-US_TOPIC_0000001134400768__li1118010535295"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001134400768__li5180135315292"><span>In the navigation pane on the left, click <strong id="EN-US_TOPIC_0000001134400768__b1282816511795">DR Tasks</strong>.</span></li><li id="EN-US_TOPIC_0000001134400768__li1818085372917"><span>On the displayed page, click <strong id="EN-US_TOPIC_0000001134400768__b05016231512">Create</strong>.</span></li><li id="EN-US_TOPIC_0000001134400768__li318118534294"><span>Select the type and enter the name of the DR task to be created.</span><p><ul id="EN-US_TOPIC_0000001134400768__ul1618111537294"><li id="EN-US_TOPIC_0000001134400768__li1818135372914"><strong id="EN-US_TOPIC_0000001134400768__b19316173385820">Type</strong>: <strong id="EN-US_TOPIC_0000001134400768__b147344171510">Cross-AZ DR</strong></li><li id="EN-US_TOPIC_0000001134400768__li2181145382918"><strong id="EN-US_TOPIC_0000001134400768__b1563164065813">Name</strong>: Enter 4 to 64 case-insensitive characters, starting with a letter. Only letters, digits, hyphens (-), and underscores (_) are allowed.<p id="EN-US_TOPIC_0000001134400768__p1818295342911"><span><img id="EN-US_TOPIC_0000001134400768__image15182155311294" src="figure/en-us_image_0000001134560730.png" height="101.78795900000001" width="473.8125" title="Click to enlarge" class="imgResize"></span></p>
 </li></ul>
 </p></li><li id="EN-US_TOPIC_0000001134400768__li2018255311294"><span>Configure the production cluster.</span><p><ul id="EN-US_TOPIC_0000001134400768__ul0182105310296"><li id="EN-US_TOPIC_0000001134400768__li1182953112920">Select a created production cluster from the drop-down list.</li><li id="EN-US_TOPIC_0000001134400768__li161821753112910">After a production cluster is selected, the system automatically displays its AZ.<p id="EN-US_TOPIC_0000001134400768__p11821953132918"><a name="EN-US_TOPIC_0000001134400768__li161821753112910"></a><a name="li161821753112910"></a><span><img id="EN-US_TOPIC_0000001134400768__image1318210536294" src="figure/en-us_image_0000001134400948.png" height="109.79682000000001" width="469.82250000000005" title="Click to enlarge" class="imgResize"></span></p>
 </li></ul>
 </p></li><li id="EN-US_TOPIC_0000001134400768__li15183353192913"><span>Configure the DR cluster.</span><p><ul id="EN-US_TOPIC_0000001134400768__ul111831553112919"><li id="EN-US_TOPIC_0000001134400768__li14183125312297">Select the AZ associated with the region where the DR cluster resides.<div class="note" id="EN-US_TOPIC_0000001134400768__note111837539291"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001134400768__p1618316538295">The production cluster AZ will be filtered out from the available DR cluster AZs.</p>
 </div></div>
 </li><li id="EN-US_TOPIC_0000001134400768__li2183353142916">After you select an AZ for the DR cluster, homogeneous DR clusters will be displayed. If no DR cluster is available, create a cluster with the same configurations as the production cluster.<p id="EN-US_TOPIC_0000001134400768__p111832053192910"><a name="EN-US_TOPIC_0000001134400768__li2183353142916"></a><a name="li2183353142916"></a><span><img id="EN-US_TOPIC_0000001134400768__image1818310537291" src="figure/en-us_image_0000001180440313.png" height="128.772196" width="490.77000000000004" title="Click to enlarge" class="imgResize"></span></p>
 </li></ul>
 </p></li><li id="EN-US_TOPIC_0000001134400768__li151831553102916"><span>Configure advanced parameters. Select <strong id="EN-US_TOPIC_0000001134400768__b68542021152911">Default</strong> to keep the default values of the advanced parameters. You can also select <strong id="EN-US_TOPIC_0000001134400768__b962174210306">Custom</strong> to modify the values.</span><p><ul id="EN-US_TOPIC_0000001134400768__ul61841153152919"><li id="EN-US_TOPIC_0000001134400768__li418455302915">The DR synchronization period indicates the interval for synchronizing incremental data from the production cluster to the DR cluster. Set this parameter based on the actual service data volume.<p id="EN-US_TOPIC_0000001134400768__p16184165320295"><a name="EN-US_TOPIC_0000001134400768__li418455302915"></a><a name="li418455302915"></a><span><img id="EN-US_TOPIC_0000001134400768__image318475322918" src="figure/en-us_image_0000001134400946.png" height="100.02730500000001" width="470.82000000000005" title="Click to enlarge" class="imgResize"></span></p>
 <div class="note" id="EN-US_TOPIC_0000001134400768__note1818445372913"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001134400768__p41841553152920">The default DR synchronization period is 30 minutes.</p>
 </div></div>
 </li></ul>
 </p></li><li id="EN-US_TOPIC_0000001134400768__li1218455314294"><span>Click <strong id="EN-US_TOPIC_0000001134400768__b5644182313207">OK</strong>.</span><p><p id="EN-US_TOPIC_0000001134400768__p518513532294">The DR status will then change to <strong id="EN-US_TOPIC_0000001134400768__b93194182410">Creating</strong>. Wait until the creation is complete, and the DR status will change to <strong id="EN-US_TOPIC_0000001134400768__b182332311257">Not Started</strong>.</p>
 </p></li></ol>
 </div>
 </div>
 <div>
 <div class="familylinks">
 <div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0080.html">Cluster DR</a></div>
 </div>
 </div>
 <script language="JavaScript">
 <!--
 image_size('.imgResize');
 var msg_imageMax = "view original image";
 var msg_imageClose = "close";
 //--></script>
--- a/docs/dws/umn/dws_01_00083.html
+++ b/docs/dws/umn/dws_01_00083.html
@ -0,0 +1,21 @@
 <a name="EN-US_TOPIC_0000001180440103"></a><a name="EN-US_TOPIC_0000001180440103"></a>
 <h1 class="topictitle1">Viewing DR Information</h1>
 <div id="body0000001082533733"><ol id="EN-US_TOPIC_0000001180440103__ol1940917434130"><li id="EN-US_TOPIC_0000001180440103__li6029015714233"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001180440103__li3542231993721"><span>In the navigation pane on the left, click <strong id="EN-US_TOPIC_0000001180440103__en-us_topic_0000001134400768_b1282816511795">DR Tasks</strong>.</span></li><li id="EN-US_TOPIC_0000001180440103__li129678548177"><span>In the DR list, click the name of a DR task.</span><p><p id="EN-US_TOPIC_0000001180440103__p9578839982">On the page that is displayed, view the following information:</p>
 <ul id="EN-US_TOPIC_0000001180440103__ul4673331171818"><li id="EN-US_TOPIC_0000001180440103__li2099613441113"><strong id="EN-US_TOPIC_0000001180440103__b16596614102713">DR Information</strong>: You can view the DR ID, DR name, DR creation time, and DR status.</li><li id="EN-US_TOPIC_0000001180440103__li14997534151116"><strong id="EN-US_TOPIC_0000001180440103__b5826216132716">Production Cluster Information</strong>: You can view the production cluster ID, cluster name, AZ, used storage capacity, cluster DR status, and the time of the latest successful DR task.</li><li id="EN-US_TOPIC_0000001180440103__li599714346111"><strong id="EN-US_TOPIC_0000001180440103__b184413316506">DR Cluster Information</strong>: You can view the DR cluster ID, cluster name, AZ, used storage capacity, cluster DR status, and the time of the latest successful DR task.</li><li id="EN-US_TOPIC_0000001180440103__li967353119187"><strong id="EN-US_TOPIC_0000001180440103__b26621747152712">DR Configurations</strong>: You can view and modify the DR synchronization period.</li></ul>
 <p id="EN-US_TOPIC_0000001180440103__p6190163032018"><span><img id="EN-US_TOPIC_0000001180440103__image81901530162010" src="figure/en-us_image_0000001134560676.png" height="211.433159" width="444.88500000000005" title="Click to enlarge" class="imgResize"></span></p>
 </p></li></ol>
 </div>
 <div>
 <div class="familylinks">
 <div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0080.html">Cluster DR</a></div>
 </div>
 </div>
 <script language="JavaScript">
 <!--
 image_size('.imgResize');
 var msg_imageMax = "view original image";
 var msg_imageClose = "close";
 //--></script>
--- a/docs/dws/umn/dws_01_00084.html
+++ b/docs/dws/umn/dws_01_00084.html
@ -0,0 +1,44 @@
 <a name="EN-US_TOPIC_0000001180320249"></a><a name="EN-US_TOPIC_0000001180320249"></a>
 <h1 class="topictitle1">DR Management</h1>
 <div id="body0000001082738789"><div class="section" id="EN-US_TOPIC_0000001180320249__section4432124194612"><a name="EN-US_TOPIC_0000001180320249__section4432124194612"></a><a name="section4432124194612"></a><h4 class="sectiontitle">Starting a DR Task</h4><ol id="EN-US_TOPIC_0000001180320249__ol6493175563012"><li id="EN-US_TOPIC_0000001180320249__li24941355193017"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001180320249__li94951155143018"><span>In the navigation pane on the left, click <strong id="EN-US_TOPIC_0000001180320249__en-us_topic_0000001134400768_b1282816511795">DR Tasks</strong>.</span></li><li id="EN-US_TOPIC_0000001180320249__li25916796163327"><span>Click <strong id="EN-US_TOPIC_0000001180320249__b1184412317246">Start</strong> in the <strong id="EN-US_TOPIC_0000001180320249__b739983415240">Operation</strong> column of the target DR task.</span></li><li id="EN-US_TOPIC_0000001180320249__li48630339105019"><span>In the dialog box that is displayed, click <span class="uicontrol" id="EN-US_TOPIC_0000001180320249__uicontrol1310109410525"><b>OK</b></span>.</span><p><p id="EN-US_TOPIC_0000001180320249__p48075126123536">The DR status will change to <strong id="EN-US_TOPIC_0000001180320249__b75720470323">Starting</strong>. The process will take some time. After the task is started, the DR status will change to <strong id="EN-US_TOPIC_0000001180320249__b185741624113316">Running</strong>.</p>
 <div class="note" id="EN-US_TOPIC_0000001180320249__note982425211381"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001180320249__ul69231148191018"><li id="EN-US_TOPIC_0000001180320249__li1793023585010">You can start a DR task that is in the <strong id="EN-US_TOPIC_0000001180320249__b1729217329133">Not started</strong>/<strong id="EN-US_TOPIC_0000001180320249__b929812326136">Startup failed</strong>/<strong id="EN-US_TOPIC_0000001180320249__b162982320132">Stopped</strong> state.</li><li id="EN-US_TOPIC_0000001180320249__li1092311489109">After you start the DR task, you cannot perform operations, including restoration, scale-out, upgrade, restart, and node replacement, on the production cluster and DR cluster. Backup is also not allowed on the DR cluster. Exercise caution when performing this operation.</li></ul>
 </div></div>
 </p></li></ol>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001180320249__section68813160462"><h4 class="sectiontitle">Stopping the DR Task</h4><ol id="EN-US_TOPIC_0000001180320249__ol611651411421"><li id="EN-US_TOPIC_0000001180320249__li9116171494216"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001180320249__li811681414421"><span>In the navigation pane on the left, click <strong id="EN-US_TOPIC_0000001180320249__en-us_topic_0000001134400768_b1282816511795_1">DR Tasks</strong>.</span></li><li id="EN-US_TOPIC_0000001180320249__li195271723124216"><span>Click <strong id="EN-US_TOPIC_0000001180320249__b7302203412014">Stop</strong> in the <strong id="EN-US_TOPIC_0000001180320249__b13025343204">Operation</strong> column of the target DR task.</span></li><li id="EN-US_TOPIC_0000001180320249__li02629218477"><span>In the dialog box that is displayed, click <span class="uicontrol" id="EN-US_TOPIC_0000001180320249__uicontrol1243181611478"><b>OK</b></span>.</span><p><p id="EN-US_TOPIC_0000001180320249__p1432111614716">The DR status will change to <strong id="EN-US_TOPIC_0000001180320249__b33911242113410">Stopping</strong>. The process will take some time. After the DR task is stopped, the status will change to <strong id="EN-US_TOPIC_0000001180320249__b1929010483520">Stopped</strong>.</p>
 <div class="note" id="EN-US_TOPIC_0000001180320249__note198814654210"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001180320249__ul5775134318106"><li id="EN-US_TOPIC_0000001180320249__li1099695645110">Only DR tasks in the <strong id="EN-US_TOPIC_0000001180320249__b43510392134">Running</strong> or <strong id="EN-US_TOPIC_0000001180320249__b74153951313">Stop failed</strong> state can be stopped.</li><li id="EN-US_TOPIC_0000001180320249__li19775174301012">Data cannot be synchronized after a DR task is stopped.</li></ul>
 </div></div>
 </p></li></ol>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001180320249__section186421928164617"><h4 class="sectiontitle">Switching to the DR Cluster</h4><ol id="EN-US_TOPIC_0000001180320249__ol16599224443"><li id="EN-US_TOPIC_0000001180320249__li459914214411"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001180320249__li10599172114419"><span>In the navigation pane on the left, click <strong id="EN-US_TOPIC_0000001180320249__en-us_topic_0000001134400768_b1282816511795_2">DR Tasks</strong>.</span></li><li id="EN-US_TOPIC_0000001180320249__li196001234413"><span>Click <strong id="EN-US_TOPIC_0000001180320249__b141791153132516">Switch to DR Cluster</strong> in the <strong id="EN-US_TOPIC_0000001180320249__b8179135322514">Operation</strong> column of the target DR task.</span></li><li id="EN-US_TOPIC_0000001180320249__li91130154816"><span>In the dialog box that is displayed, click <span class="uicontrol" id="EN-US_TOPIC_0000001180320249__uicontrol1872016482"><b>OK</b></span>.</span><p><p id="EN-US_TOPIC_0000001180320249__p10871120487">The DR status will change to <strong id="EN-US_TOPIC_0000001180320249__b19646184092713">DR switching</strong>.</p>
 <p id="EN-US_TOPIC_0000001180320249__p458415421692">After the switchover is successful, the DR status will change to the original status.</p>
 <div class="note" id="EN-US_TOPIC_0000001180320249__note206009220442"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001180320249__ul682023717106"><li id="EN-US_TOPIC_0000001180320249__li534343517530">You can perform a DR switchover when the DR task is in the <strong id="EN-US_TOPIC_0000001180320249__b188905017144">Running</strong> or <strong id="EN-US_TOPIC_0000001180320249__b17890704148">Abnormal</strong> state.</li><li id="EN-US_TOPIC_0000001180320249__li1082615373105">During a switchover, the original production cluster is not available.</li><li id="EN-US_TOPIC_0000001180320249__li11162143121313">RPO of DR switchover:<ul id="EN-US_TOPIC_0000001180320249__ul5735135051312"><li id="EN-US_TOPIC_0000001180320249__li105191115131612">Production cluster in the <strong id="EN-US_TOPIC_0000001180320249__b73842527378">Available</strong> state: RPO = 0</li><li id="EN-US_TOPIC_0000001180320249__li29571937409">Production cluster in the <strong id="EN-US_TOPIC_0000001180320249__b18372115105316">Unavailable</strong> state: A zero RPO may not be achieved, but data can at least be restored to that of the latest successful DR synchronization (<strong id="EN-US_TOPIC_0000001180320249__b124595516232">Last DR Succeeded</strong>). For details, see <a href="dws_01_00083.html">Viewing DR Information</a>.</li></ul>
 </li></ul>
 </div></div>
 </p></li></ol>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001180320249__section1869120274302"><h4 class="sectiontitle">Updating DR Configurations</h4><ol id="EN-US_TOPIC_0000001180320249__ol71803891610"><li id="EN-US_TOPIC_0000001180320249__li6029015714233"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001180320249__li38983837105359"><span>In the navigation pane on the left, click <strong id="EN-US_TOPIC_0000001180320249__en-us_topic_0000001134400768_b1282816511795_3">DR Tasks</strong>.</span></li><li id="EN-US_TOPIC_0000001180320249__li129909103263"><span>In the DR list, click the DR name to go to the DR information page.</span></li><li id="EN-US_TOPIC_0000001180320249__li29903558266"><span>In the <strong id="EN-US_TOPIC_0000001180320249__b1448119322283">DR Configurations</strong> area, click <strong id="EN-US_TOPIC_0000001180320249__b13407415284">Modify</strong>.</span><p><p id="EN-US_TOPIC_0000001180320249__p3404013193011"><span><img id="EN-US_TOPIC_0000001180320249__image940414134307" src="figure/en-us_image_0000001134401018.png" height="147.63" width="523.6875" title="Click to enlarge" class="imgResize"></span></p>
 <div class="note" id="EN-US_TOPIC_0000001180320249__note1088013810209"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001180320249__ul1225716581118"><li id="EN-US_TOPIC_0000001180320249__li66781220125416">Only DR tasks in the <strong id="EN-US_TOPIC_0000001180320249__b19921132391415">Not started</strong> or <strong id="EN-US_TOPIC_0000001180320249__b1692118234144">Stopped</strong> state can be modified.</li><li id="EN-US_TOPIC_0000001180320249__li525815161110">The new configuration takes effect after DR is restarted.</li></ul>
 </div></div>
 </p></li></ol>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001180320249__section1631535174714"><a name="EN-US_TOPIC_0000001180320249__section1631535174714"></a><a name="section1631535174714"></a><h4 class="sectiontitle">Deleting DR Tasks</h4><ol id="EN-US_TOPIC_0000001180320249__ol7234135954410"><li id="EN-US_TOPIC_0000001180320249__li523455918442"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001180320249__li11234195914442"><span>In the navigation pane on the left, click <strong id="EN-US_TOPIC_0000001180320249__en-us_topic_0000001134400768_b1282816511795_4">DR Tasks</strong>.</span></li><li id="EN-US_TOPIC_0000001180320249__li112351559144413"><span>Click <strong id="EN-US_TOPIC_0000001180320249__b3751191052515">Delete</strong> in the <strong id="EN-US_TOPIC_0000001180320249__b17751101072518">Operation</strong> column of the target DR task.</span></li><li id="EN-US_TOPIC_0000001180320249__li14164315489"><span>In the dialog box that is displayed, click <span class="uicontrol" id="EN-US_TOPIC_0000001180320249__uicontrol13421636144810"><b>OK</b></span>.</span><p><div class="p" id="EN-US_TOPIC_0000001180320249__p181117546484">The DR status will change to <strong id="EN-US_TOPIC_0000001180320249__b19358101282910">Deleting</strong>.<div class="note" id="EN-US_TOPIC_0000001180320249__note20651543124819"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001180320249__ul25943216112"><li id="EN-US_TOPIC_0000001180320249__li1269162595510">You can delete a DR task when <strong id="EN-US_TOPIC_0000001180320249__b1172104171410">DR Status</strong> is <strong id="EN-US_TOPIC_0000001180320249__b1178174141410">Creation failed</strong>, <strong id="EN-US_TOPIC_0000001180320249__b6179174111147">Not started</strong>, <strong id="EN-US_TOPIC_0000001180320249__b717974151416">Startup failed</strong>, <strong id="EN-US_TOPIC_0000001180320249__b1217974113147">Stopped</strong>, <strong id="EN-US_TOPIC_0000001180320249__b6179124141418">Stop failed</strong>, or <strong id="EN-US_TOPIC_0000001180320249__b1018014412142">Abnormal</strong>.</li><li id="EN-US_TOPIC_0000001180320249__li18595142181115">Data cannot be synchronized after a DR task is deleted, and the deleted task cannot be restored.</li></ul>
 </div></div>
 </div>
 </p></li></ol>
 </div>
 </div>
 <div>
 <div class="familylinks">
 <div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0080.html">Cluster DR</a></div>
 </div>
 </div>
 <script language="JavaScript">
 <!--
 image_size('.imgResize');
 var msg_imageMax = "view original image";
 var msg_imageClose = "close";
 //--></script>
--- a/docs/dws/umn/dws_01_00085.html
+++ b/docs/dws/umn/dws_01_00085.html
@ -0,0 +1,23 @@
 <a name="EN-US_TOPIC_0000001180320159"></a><a name="EN-US_TOPIC_0000001180320159"></a>
 <h1 class="topictitle1">Mutually Exclusive DR Cases</h1>
 <div id="body0000001096920089"><div class="section" id="EN-US_TOPIC_0000001180320159__section590914492476"><h4 class="sectiontitle">Case 1: How Do I Scale out a Cluster in the DR State?</h4><ol id="EN-US_TOPIC_0000001180320159__ol11819411242"><li id="EN-US_TOPIC_0000001180320159__li161811412410"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001180320159__li12183492413"><span>In the navigation pane on the left, click <span class="uicontrol" id="EN-US_TOPIC_0000001180320159__uicontrol13132164852011"><b>Clusters</b></span>.</span></li><li id="EN-US_TOPIC_0000001180320159__li14182402410"><span>In the cluster list, if <strong id="EN-US_TOPIC_0000001180320159__b16291110112112">Task Information</strong> of the cluster you want to scale out is <strong id="EN-US_TOPIC_0000001180320159__b1776715133217">DR not started</strong>, perform <a href="#EN-US_TOPIC_0000001180320159__li18914144545215">5</a> and <a href="#EN-US_TOPIC_0000001180320159__li51916418241">7</a>.</span></li><li id="EN-US_TOPIC_0000001180320159__li16791602612"><span>If the <strong id="EN-US_TOPIC_0000001180320159__b1849416611227">Task Information</strong> is other than <strong id="EN-US_TOPIC_0000001180320159__b2889781224">DR not started</strong>, delete the DR task. For details, see <a href="dws_01_00084.html#EN-US_TOPIC_0000001180320249__section1631535174714">Deleting DR Tasks</a>.</span></li><li id="EN-US_TOPIC_0000001180320159__li18914144545215"><a name="EN-US_TOPIC_0000001180320159__li18914144545215"></a><a name="li18914144545215"></a><span>In the <strong id="EN-US_TOPIC_0000001180320159__b1570611413223">Operation</strong> column of the production and DR clusters, choose <strong id="EN-US_TOPIC_0000001180320159__b1533125115228">More</strong> &gt; <strong id="EN-US_TOPIC_0000001180320159__b835414219230">Scale Out</strong>.</span><p><p id="EN-US_TOPIC_0000001180320159__p13604164995215"></p>
 <p id="EN-US_TOPIC_0000001180320159__p17671551134419"><span><img id="EN-US_TOPIC_0000001180320159__image8443230133710" src="figure/en-us_image_0000001432860233.png" width="353.115" height="94.757845" title="Click to enlarge" class="imgResize"></span></p>
 </p></li><li id="EN-US_TOPIC_0000001180320159__li1186517402503"><span>Create a DR task. For details, see <a href="dws_01_00082.html">Creating a DR Task</a>.</span></li><li id="EN-US_TOPIC_0000001180320159__li51916418241"><a name="EN-US_TOPIC_0000001180320159__li51916418241"></a><a name="li51916418241"></a><span>Start the DR task. For details, see <a href="dws_01_00084.html#EN-US_TOPIC_0000001180320249__section4432124194612">Starting a DR Task</a>.</span><p><div class="note" id="EN-US_TOPIC_0000001180320159__note114141555115311"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001180320159__p541211552534">After scale-out, the number of DNs in the production cluster must be the same as that in the DR cluster.</p>
 </div></div>
 </p></li></ol>
 </div>
 </div>
 <div>
 <div class="familylinks">
 <div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0080.html">Cluster DR</a></div>
 </div>
 </div>
 <script language="JavaScript">
 <!--
 image_size('.imgResize');
 var msg_imageMax = "view original image";
 var msg_imageClose = "close";
 //--></script>
--- a/docs/dws/umn/dws_01_0009.html
+++ b/docs/dws/umn/dws_01_0009.html
@ -0,0 +1,36 @@
 <a name="EN-US_TOPIC_0000001142315616"></a><a name="EN-US_TOPIC_0000001142315616"></a>
 <h1 class="topictitle1">GaussDB(DWS) Access</h1>
 <div id="body8662426"><p id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_p52051556114557">The following figure shows how to use GaussDB(DWS).</p>
 <div class="fignone" id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_fig102092934419"><span class="figcap"><b>Figure 1 </b>Process for using GaussDB(DWS)</span><br><span><img id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_image3222134620373" src="figure/en-us_image_0000001188355709.png" width="465.5" height="366.96921100000003" title="Click to enlarge" class="imgResize"></span></div>
 <div class="section" id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_section9564628121817"><h4 class="sectiontitle">Accessing a Cluster</h4><p id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_p185859251535">GaussDB(DWS) provides a web-based management console and HTTPS-compliant APIs for you to manage data warehouse clusters.</p>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_section247336101912"><h4 class="sectiontitle">Accessing the Database in a Cluster</h4><div class="p" id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_p15871825195311">GaussDB(DWS) supports database access using the following methods:<ul id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_ul18312947778"><li id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_li33127471471">GaussDB(DWS) clients<p id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_p41791739101020"><a name="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_li33127471471"></a><a name="en-us_topic_0000001098656876_li33127471471"></a>Access the cluster database using GaussDB(DWS) clients. For details, see Connecting to Clusters" in the <em id="EN-US_TOPIC_0000001142315616__i91537314438">Data Warehouse Service (DWS) User Guide</em>.</p>
 </li><li id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_li2061495291519">Open-source PostgreSQL clients<div class="p" id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_p864815221511"><a name="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_li2061495291519"></a><a name="en-us_topic_0000001098656876_li2061495291519"></a>The following lists compatible open-source clients:<ul id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_u42c9c994ab1f48e18ee641dd587ddcce"><li id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_la9b72d7be5ef43b9ac80dff7c89dcce7">PostgreSQL psql 9.2.4 or later<p id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_a5ea19981098c4d8e9642224cad0b64d6"><a name="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_la9b72d7be5ef43b9ac80dff7c89dcce7"></a><a name="en-us_topic_0000001098656876_la9b72d7be5ef43b9ac80dff7c89dcce7"></a>For more information, see <a href="https://www.postgresql.org/" target="_blank" rel="noopener noreferrer">https://www.postgresql.org/</a>.</p>
 </li><li id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_l38632b3bc7ba4707a1504713ba48f931">pgadmin<p id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_ae86c7495b3294441be79a727f14f473e"><a name="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_l38632b3bc7ba4707a1504713ba48f931"></a><a name="en-us_topic_0000001098656876_l38632b3bc7ba4707a1504713ba48f931"></a>For more information, see <a href="https://www.pgadmin.org/" target="_blank" rel="noopener noreferrer">https://www.pgadmin.org/</a>.</p>
 </li><li id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_lc9d38e168a6f4f49925989494d656fb0">dbeaver<p id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_ad7582c34c2bd4a3b8dc8a8f70af00f54"><a name="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_lc9d38e168a6f4f49925989494d656fb0"></a><a name="en-us_topic_0000001098656876_lc9d38e168a6f4f49925989494d656fb0"></a>For more information, see <a href="https://dbeaver.jkiss.org/download/" target="_blank" rel="noopener noreferrer">https://dbeaver.jkiss.org/download/</a>.</p>
 </li></ul>
 </div>
 </li><li id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_li83122471278">JDBC and ODBC API calling<p id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_p820217395261"><a name="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_li83122471278"></a><a name="en-us_topic_0000001098656876_li83122471278"></a>You can call standard APIs, such as JDBC and ODBC, to access databases in clusters.</p>
 <p id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_p857045014151">For details, see "Using the JDBC and ODBC Drivers to Connect to a Cluster" in the <em id="EN-US_TOPIC_0000001142315616__i181605169468">Data Warehouse Service (DWS) User Guide</em>.</p>
 </li></ul>
 </div>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_section14800923145413"><h4 class="sectiontitle">End-to-End Data Analysis Process</h4><p id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_p1537148201412">GaussDB(DWS) has been seamlessly integrated with other services on the <span id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_text798606471">cloud</span>, helping you rapidly deploy end-to-end data analysis solutions.</p>
 <p id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_p0537204841410">The following figure shows the end-to-end data analysis process. Services in use during each process are also displayed.</p>
 <div class="fignone" id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_fig85581940163219"><span class="figcap"><b>Figure 2 </b>End-to-end data analysis process</span><br><span><img id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_image1411052611811" src="figure/en-us_image_0000001142155952.png" height="194.83569" width="463.83750000000003" title="Click to enlarge" class="imgResize"></span></div>
 </div>
 </div>
 <div>
 <div class="familylinks">
 <div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_index.html">Service Overview</a></div>
 </div>
 </div>
 <script language="JavaScript">
 <!--
 image_size('.imgResize');
 var msg_imageMax = "view original image";
 var msg_imageClose = "close";
 //--></script>
--- a/docs/dws/umn/dws_01_0010.html
+++ b/docs/dws/umn/dws_01_0010.html
@ -0,0 +1,11 @@
 <a name="EN-US_TOPIC_0000001180320161"></a><a name="EN-US_TOPIC_0000001180320161"></a>
 <h1 class="topictitle1">Restrictions</h1>
 <div id="body1487841436167"><ul id="EN-US_TOPIC_0000001180320161__ul61383469111152"><li id="EN-US_TOPIC_0000001180320161__li38097050111152">You can manage clusters only and cannot directly access nodes in a cluster. You can use a cluster's IP address and port to access the database in the cluster.</li><li id="EN-US_TOPIC_0000001180320161__li36526166111152">You cannot change the flavor of an existing cluster. If you need nodes with a higher flavor, create a new one.</li><li id="EN-US_TOPIC_0000001180320161__li21829368111152">If you use a client to connect to a cluster, its VPC subnet must be the same as that of the cluster.</li><li id="EN-US_TOPIC_0000001180320161__li17624906111152">If you copy commands from the document to the operating environment, the text wraps automatically, causing command execution failures. To solve the problem, delete the line break.</li></ul>
 </div>
 <div>
 <div class="familylinks">
 <div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_index.html">Service Overview</a></div>
 </div>
 </div>
--- a/docs/dws/umn/dws_01_00113.html
+++ b/docs/dws/umn/dws_01_00113.html
--- a/docs/dws/umn/dws_01_0013.html
+++ b/docs/dws/umn/dws_01_0013.html
@ -0,0 +1,61 @@
 <a name="EN-US_TOPIC_0000001134400820"></a><a name="EN-US_TOPIC_0000001134400820"></a>
 <h1 class="topictitle1">Step 2: Creating a Cluster</h1>
 <div id="body1488272827608"><p id="EN-US_TOPIC_0000001134400820__p291616474813">Before using GaussDB(DWS) to analyze data, create a cluster. A cluster consists of multiple nodes in the same subnet. These nodes together provide services. This section describes how to create a GaussDB(DWS) cluster.</p>
 <div class="section" id="EN-US_TOPIC_0000001134400820__section104149431131"><h4 class="sectiontitle">Creating a Cluster</h4><ol id="EN-US_TOPIC_0000001134400820__ol1649726614233"><li id="EN-US_TOPIC_0000001134400820__li6029015714233"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001134400820__li226234352"><span>Choose <span class="uicontrol" id="EN-US_TOPIC_0000001134400820__uicontrol1743558195311"><b>Clusters</b></span> in the navigation pane on the left.</span></li><li id="EN-US_TOPIC_0000001134400820__li63277252161245"><span>On the <span class="wintitle" id="EN-US_TOPIC_0000001134400820__wintitle174201315530"><b>Clusters</b></span> page, click <strong id="EN-US_TOPIC_0000001134400820__b2773104918208">Create Cluster</strong> in the upper right corner.</span></li><li id="EN-US_TOPIC_0000001134400820__li1422605291313"><span>Select the region to which the cluster to be created belongs.</span><p><ul id="EN-US_TOPIC_0000001134400820__ul2673243141713"><li id="EN-US_TOPIC_0000001134400820__li0591886205"><strong id="EN-US_TOPIC_0000001134400820__b9652420192017">Region</strong>: Select the current working area of the cluster.</li><li id="EN-US_TOPIC_0000001134400820__li768864321715"><strong id="EN-US_TOPIC_0000001134400820__b8587164614190">AZ</strong>: Retain the default value.</li></ul>
 </p></li><li id="EN-US_TOPIC_0000001134400820__li3509811181412"><span>Configure node parameters.</span><p><ul id="EN-US_TOPIC_0000001134400820__ul3617182404112"><li id="EN-US_TOPIC_0000001134400820__li125151717114915"><strong id="EN-US_TOPIC_0000001134400820__b34841625102618">Cluster Type</strong>: For example, <span class="parmname" id="EN-US_TOPIC_0000001134400820__parmname164871525192617"><b>Standard</b></span>.</li><li id="EN-US_TOPIC_0000001134400820__li12608533142115"><strong id="EN-US_TOPIC_0000001134400820__b106646351267">CPU Architecture</strong>: Select a CPU architecture based on your requirements, for example, <strong id="EN-US_TOPIC_0000001134400820__b14664183511265">x86</strong>.</li><li id="EN-US_TOPIC_0000001134400820__li174125558519"><strong id="EN-US_TOPIC_0000001134400820__b108993477207">Node Flavor</strong>: Retain the default value.</li><li id="EN-US_TOPIC_0000001134400820__li1363312424111"><strong id="EN-US_TOPIC_0000001134400820__b18633253159">Nodes</strong>: Retain the default value. At least <strong id="EN-US_TOPIC_0000001134400820__b122512111846">3</strong> nodes are required.</li></ul>
 <div class="fignone" id="EN-US_TOPIC_0000001134400820__fig1236785221310"><span class="figcap"><b>Figure 1 </b>Configuring node parameters</span><br><span><img id="EN-US_TOPIC_0000001134400820__image6966015171415" src="figure/en-us_image_0000001180320497.png" height="123.22915499999999" width="459.8475" title="Click to enlarge" class="imgResize"></span></div>
 </p></li><li id="EN-US_TOPIC_0000001134400820__li250803614263"><span>Configure cluster parameters.</span><p><ul id="EN-US_TOPIC_0000001134400820__ul132177543292"><li id="EN-US_TOPIC_0000001134400820__li721765419298"><strong id="EN-US_TOPIC_0000001134400820__b16036229252">Cluster Name</strong>: Enter <strong id="EN-US_TOPIC_0000001134400820__b34153269254">dws-demo</strong>.</li><li id="EN-US_TOPIC_0000001134400820__li132295612719"><strong id="EN-US_TOPIC_0000001134400820__b982211416481">Cluster Version</strong>: The current cluster version is displayed and cannot be changed.</li><li id="EN-US_TOPIC_0000001134400820__li132331754192915"><strong id="EN-US_TOPIC_0000001134400820__b9837143942513">Default Database</strong>: The value is <strong id="EN-US_TOPIC_0000001134400820__b136722023419"><span id="EN-US_TOPIC_0000001134400820__text1287103795414">gaussdb</span></strong>, which cannot be changed.</li><li id="EN-US_TOPIC_0000001134400820__li1224918542292"><strong id="EN-US_TOPIC_0000001134400820__b79781929142612">Administrator Account</strong>: The default value is <strong id="EN-US_TOPIC_0000001134400820__b12853163612269">dbadmin</strong>. Use the default value. After a cluster is created, the client uses this account and its password to connect to the cluster's database.</li><li id="EN-US_TOPIC_0000001134400820__li12249954192911"><strong id="EN-US_TOPIC_0000001134400820__b46931626115914">Administrator Password</strong>: Enter the password.</li><li id="EN-US_TOPIC_0000001134400820__li326314541299"><strong id="EN-US_TOPIC_0000001134400820__b377523253011">Confirm Password</strong>: Enter the password again.</li><li id="EN-US_TOPIC_0000001134400820__li12263154172918"><strong id="EN-US_TOPIC_0000001134400820__b13527436304">Database Port</strong>: Use the default port number. This port is used by the client or application to connect to the cluster's database.</li></ul>
 <div class="fignone" id="EN-US_TOPIC_0000001134400820__fig8713143792811"><span class="figcap"><b>Figure 2 </b>Configuring the cluster</span><br><span><img id="EN-US_TOPIC_0000001134400820__image164010498163" src="figure/en-us_image_0000001134401058.png" width="465.5" height="321.034469" title="Click to enlarge" class="imgResize"></span></div>
 </p></li><li id="EN-US_TOPIC_0000001134400820__li123915537131"><span>Configure network parameters.</span><p><ul id="EN-US_TOPIC_0000001134400820__ul12330104953110"><li id="EN-US_TOPIC_0000001134400820__li12345144913118"><strong id="EN-US_TOPIC_0000001134400820__b95040215231">VPC</strong>: You can select an existing VPC from the drop-down list. If no VPC has been configured, click <strong id="EN-US_TOPIC_0000001134400820__b55104218233">View VPC</strong> to enter the VPC management console to create one, for example, <strong id="EN-US_TOPIC_0000001134400820__b7511621152316">vpc-dws</strong>. Then, go back to the page for creating a cluster on the GaussDB(DWS) management console, click <span><img id="EN-US_TOPIC_0000001134400820__image0584421174519" src="figure/en-us_image_0000001180320487.png"></span> next to the <span class="parmname" id="EN-US_TOPIC_0000001134400820__parmname18621165214224"><b>VPC</b></span> drop-down list, and select the new VPC.</li><li id="EN-US_TOPIC_0000001134400820__li936111493311"><strong id="EN-US_TOPIC_0000001134400820__b115255215450">Subnet</strong>: When you create a VPC, a subnet is created by default. You can select the corresponding subnet.</li><li id="EN-US_TOPIC_0000001134400820__li5378124919315"><strong id="EN-US_TOPIC_0000001134400820__b1067772324620">Security Group</strong>: Select <span class="parmvalue" id="EN-US_TOPIC_0000001134400820__parmvalue85217455468"><b>Automatic creation</b></span>.<p id="EN-US_TOPIC_0000001134400820__p1439310499315">The automatically created security group is named <strong id="EN-US_TOPIC_0000001134400820__b5899171819170">GaussDB(DWS)</strong>-&lt;<em id="EN-US_TOPIC_0000001134400820__i139006183174">Cluster name</em>&gt;-&lt;<em id="EN-US_TOPIC_0000001134400820__i129001318121712">GaussDB(DWS) cluster database port</em>&gt;. The outbound allows all access requests, while the inbound enables only <strong id="EN-US_TOPIC_0000001134400820__b0900218181711">Database Port</strong> for access requests from clients or applications.</p>
 <p id="EN-US_TOPIC_0000001134400820__p10928141314713">If you select a custom security group, add an inbound rule to it to enable <strong id="EN-US_TOPIC_0000001134400820__b426010387576">Database Port</strong> for client hosts to access GaussDB(DWS). <a href="#EN-US_TOPIC_0000001134400820__table19508017113430">Table 1</a> shows an example. For details about how to add an inbound rule, see "Security &gt; Security Group &gt; Adding a Security Group Rule" in the <em id="EN-US_TOPIC_0000001134400820__i4561624851">Virtual Private Cloud User Guide</em>.</p>
 <div class="tablenoborder"><a name="EN-US_TOPIC_0000001134400820__table19508017113430"></a><a name="table19508017113430"></a><table cellpadding="4" cellspacing="0" summary="" id="EN-US_TOPIC_0000001134400820__table19508017113430" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Inbound rule example</caption><thead align="left"><tr id="EN-US_TOPIC_0000001134400820__row23155325113430"><th align="left" class="cellrowborder" valign="top" width="30.64%" id="mcps1.3.2.2.7.2.1.3.5.2.3.1.1"><p id="EN-US_TOPIC_0000001134400820__p43667920113430"><strong id="EN-US_TOPIC_0000001134400820__en-us_topic_0111441330_b63022988143745">Parameter</strong></p>
 </th>
 <th align="left" class="cellrowborder" valign="top" width="69.36%" id="mcps1.3.2.2.7.2.1.3.5.2.3.1.2"><p id="EN-US_TOPIC_0000001134400820__p24312498113430"><strong id="EN-US_TOPIC_0000001134400820__en-us_topic_0111441330_b1200428498185923">Example Value</strong></p>
 </th>
 </tr>
 </thead>
 <tbody><tr id="EN-US_TOPIC_0000001134400820__row3891192113430"><td class="cellrowborder" valign="top" width="30.64%" headers="mcps1.3.2.2.7.2.1.3.5.2.3.1.1 "><p id="EN-US_TOPIC_0000001134400820__p63642012113430">Protocol/Application</p>
 </td>
 <td class="cellrowborder" valign="top" width="69.36%" headers="mcps1.3.2.2.7.2.1.3.5.2.3.1.2 "><p id="EN-US_TOPIC_0000001134400820__p54729336113430">TCP</p>
 </td>
 </tr>
 <tr id="EN-US_TOPIC_0000001134400820__row58663991113430"><td class="cellrowborder" valign="top" width="30.64%" headers="mcps1.3.2.2.7.2.1.3.5.2.3.1.1 "><p id="EN-US_TOPIC_0000001134400820__p46516451113430">Port</p>
 </td>
 <td class="cellrowborder" valign="top" width="69.36%" headers="mcps1.3.2.2.7.2.1.3.5.2.3.1.2 "><p id="EN-US_TOPIC_0000001134400820__p9736197113430">8000</p>
 <div class="note" id="EN-US_TOPIC_0000001134400820__note50434516113430"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="EN-US_TOPIC_0000001134400820__p20516916113430">Enter the value of <span class="parmname" id="EN-US_TOPIC_0000001134400820__parmname8228641206"><b>Database Port</b></span> set when creating the GaussDB(DWS) cluster. This port is used for receiving client connections to GaussDB(DWS). The default port number is 8000.</p>
 </div></div>
 </td>
 </tr>
 <tr id="EN-US_TOPIC_0000001134400820__row24697782113430"><td class="cellrowborder" valign="top" width="30.64%" headers="mcps1.3.2.2.7.2.1.3.5.2.3.1.1 "><p id="EN-US_TOPIC_0000001134400820__p58213876113430">Source</p>
 </td>
 <td class="cellrowborder" valign="top" width="69.36%" headers="mcps1.3.2.2.7.2.1.3.5.2.3.1.2 "><p id="EN-US_TOPIC_0000001134400820__p17703505113430">Select <strong id="EN-US_TOPIC_0000001134400820__b147691752191610">IP address</strong>, and enter the IP address and subnet mask of the client host that accesses GaussDB(DWS), for example, <strong id="EN-US_TOPIC_0000001134400820__b1098613187177">192.168.0.10/16</strong>.</p>
 </td>
 </tr>
 </tbody>
 </table>
 </div>
 </li><li id="EN-US_TOPIC_0000001134400820__li04241449103116"><strong id="EN-US_TOPIC_0000001134400820__b51088291812">EIP</strong>: Select <span class="parmvalue" id="EN-US_TOPIC_0000001134400820__parmvalue31149294119"><b>Automatically assign</b></span> to apply for a cluster EIP as the public network IP address of the cluster. In addition, set the EIP bandwidth.</li></ul>
 <div class="fignone" id="EN-US_TOPIC_0000001134400820__fig746874172719"><span class="figcap"><b>Figure 3 </b>Configuring the network</span><br><span><img id="EN-US_TOPIC_0000001134400820__image1946874132714" src="figure/en-us_image_0000001134560836.png" height="156.093854" width="464.83500000000004" title="Click to enlarge" class="imgResize"></span></div>
 </p></li><li id="EN-US_TOPIC_0000001134400820__li936871610170"><span>Configure the enterprise project to which the cluster belongs. You can configure this parameter only when the Enterprise Project Management service is enabled. The default value is <strong id="EN-US_TOPIC_0000001134400820__b123293559253">default</strong>.</span><p><p id="EN-US_TOPIC_0000001134400820__p237117168171">An enterprise project facilitates project-level management and grouping of cloud resources and users.</p>
 <p id="EN-US_TOPIC_0000001134400820__p149417121983">You can select the default enterprise project (<span class="parmvalue" id="EN-US_TOPIC_0000001134400820__parmvalue13693123317274"><b>default</b></span>) or other existing enterprise projects. To create an enterprise project, log in to the Enterprise Management console. For details, see the <em id="EN-US_TOPIC_0000001134400820__i193180207287">Enterprise Management User Guide</em>.</p>
 </p></li><li id="EN-US_TOPIC_0000001134400820__li12731024123113"><span>Select <span class="parmname" id="EN-US_TOPIC_0000001134400820__parmname199906301105"><b>Default</b></span> for <strong id="EN-US_TOPIC_0000001134400820__b537753715815">Advanced Settings</strong> in this example.</span><p><ul id="EN-US_TOPIC_0000001134400820__ul5460153173816"><li id="EN-US_TOPIC_0000001134400820__li1446015343814"><strong id="EN-US_TOPIC_0000001134400820__b153054615712">Default</strong>: indicates that the following advanced settings use the default configurations.<ul id="EN-US_TOPIC_0000001134400820__ul1986713232429"><li id="EN-US_TOPIC_0000001134400820__li1720613145311"><strong id="EN-US_TOPIC_0000001134400820__b770594219579">Automated Snapshot</strong>: By default, the policy for automatically creating cluster snapshots is enabled.</li><li id="EN-US_TOPIC_0000001134400820__li4252191818248"><strong id="EN-US_TOPIC_0000001134400820__b1527715250365">CNs</strong>: Three CNs are deployed by default.</li><li id="EN-US_TOPIC_0000001134400820__li830142017172"><strong id="EN-US_TOPIC_0000001134400820__b1460604119344">Parameter Template</strong>: The default database parameter template is associated with the cluster.</li><li id="EN-US_TOPIC_0000001134400820__li6380852173414"><strong id="EN-US_TOPIC_0000001134400820__b1384220244151">Tag</strong>: By default, no tag is added to the cluster.</li></ul>
 </li><li id="EN-US_TOPIC_0000001134400820__li3460133384"><strong id="EN-US_TOPIC_0000001134400820__b1944710225020">Custom</strong>: Select this option to configure the following advanced parameters: <strong id="EN-US_TOPIC_0000001134400820__b19998759125214">Automated Snapshot</strong>, <strong id="EN-US_TOPIC_0000001134400820__b199825917526">CNs</strong>, <strong id="EN-US_TOPIC_0000001134400820__b4243121219261">Parameter Template</strong>, <strong id="EN-US_TOPIC_0000001134400820__b127981427105317">Tag</strong></li></ul>
 </p></li><li id="EN-US_TOPIC_0000001134400820__li36258555152115"><span>Click <strong id="EN-US_TOPIC_0000001134400820__b742032741412">Create Now</strong>. The <strong id="EN-US_TOPIC_0000001134400820__b629483015144">Confirm</strong> page is displayed.</span></li><li id="EN-US_TOPIC_0000001134400820__li47734902152356"><span>Click <strong id="EN-US_TOPIC_0000001134400820__b817385610281">Submit</strong>.</span><p><p id="EN-US_TOPIC_0000001134400820__en-us_topic_0106894662_p4318009414">After the submission is successful, the creation starts. Click <span class="uicontrol" id="EN-US_TOPIC_0000001134400820__uicontrol69391146151"><b>Back to Cluster List</b></span>. The <strong id="EN-US_TOPIC_0000001134400820__b294614181515">Clusters</strong> page is displayed. The initial status of the cluster is <span class="parmvalue" id="EN-US_TOPIC_0000001134400820__parmvalue169465410159"><b>Creating</b></span>. Cluster creation takes some time. Wait for a while. Clusters in the <span class="parmname" id="EN-US_TOPIC_0000001134400820__parmname769647905151646"><b>Available</b></span> state are ready for use.</p>
 </p></li></ol>
 </div>
 </div>
 <div>
 <div class="familylinks">
 <div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0078.html">Getting Started</a></div>
 </div>
 </div>
 <script language="JavaScript">
 <!--
 image_size('.imgResize');
 var msg_imageMax = "view original image";
 var msg_imageClose = "close";
 //--></script>
--- a/docs/dws/umn/dws_01_00131.html
+++ b/docs/dws/umn/dws_01_00131.html
@ -0,0 +1,16 @@
 <a name="EN-US_TOPIC_0000001134560590"></a><a name="EN-US_TOPIC_0000001134560590"></a>
 <h1 class="topictitle1">Database Monitoring Overview</h1>
 <div id="body8662426"><div class="section" id="EN-US_TOPIC_0000001134560590__en-us_topic_0000001076801429_section1734710315317"><h4 class="sectiontitle">Overview</h4><p id="EN-US_TOPIC_0000001134560590__p10989102113415">DMS is provided by GaussDB(DWS) to ensure the fast and stable running of databases. It collects, monitors, and analyzes the disk, network, and OS metric data used by the service database, as well as key performance metric data of cluster running. It also diagnoses database hosts, instances, and service SQL statements based on the collected metrics to expose key faults and performance problems in a database in a timely manner, and guides customers to optimize and resolve the problems.</p>
 <div class="note" id="EN-US_TOPIC_0000001134560590__note756531276"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001134560590__p185941428971">The database monitoring function is supported by 8.1.1.200 and later versions.</p>
 </div></div>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001134560590__en-us_topic_0000001076801429_section31552182412"><h4 class="sectiontitle">Entering the Database Monitoring Page</h4><ol id="EN-US_TOPIC_0000001134560590__en-us_topic_0000001076801429_o4d27c72c9c5b483283c532fd703af879"><li id="EN-US_TOPIC_0000001134560590__en-us_topic_0000001076801429_l3bf4b8bc45d343b6aec0b48be7dfc1aa"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001134560590__en-us_topic_0000001076801429_li11952509114244"><span>On the <span class="uicontrol" id="EN-US_TOPIC_0000001134560590__uicontrol34878639641520"><b>Clusters</b></span> page, locate the target cluster.</span></li><li id="EN-US_TOPIC_0000001134560590__en-us_topic_0000001076801429_li167917216818"><span>In the <strong id="EN-US_TOPIC_0000001134560590__b69816700441520">Operation</strong> column of the target cluster, choose <strong id="EN-US_TOPIC_0000001134560590__b176556676741520">Monitoring Panel</strong>. The database monitoring page is displayed.</span></li></ol>
 </div>
 </div>
 <div>
 <div class="familylinks">
 <div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_00014.html">Databases Monitoring</a></div>
 </div>
 </div>
--- a/docs/dws/umn/dws_01_00132.html
+++ b/docs/dws/umn/dws_01_00132.html
@ -0,0 +1,36 @@
 <a name="EN-US_TOPIC_0000001134560606"></a><a name="EN-US_TOPIC_0000001134560606"></a>
 <h1 class="topictitle1">Cluster Overview</h1>
 <div id="body8662426"><div class="section" id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_section3960135142513"><h4 class="sectiontitle">Cluster Overview</h4><ol id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_o4d27c72c9c5b483283c532fd703af879"><li id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_l3bf4b8bc45d343b6aec0b48be7dfc1aa"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_li11952509114244"><span>On the <span class="uicontrol" id="EN-US_TOPIC_0000001134560606__uicontrol11222797241014"><b>Clusters</b></span> page, locate the target cluster.</span></li><li id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_li8798326172918"><span>In the <strong id="EN-US_TOPIC_0000001134560606__b177592955841014">Operation</strong> column of the target cluster, click <strong id="EN-US_TOPIC_0000001134560606__b2820549941014">Monitoring Panel</strong>. The database monitoring page is displayed.</span></li><li id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_li32311493910"><span>In the navigation pane on the left, click <strong id="EN-US_TOPIC_0000001134560606__b1635119231621">Cluster Overview</strong>.</span><p><p id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_p61281626122220">On the page that is displayed, you can view the cluster status, real-time resource consumption, top SQL statements, cluster resource consumption, and key database metrics.</p>
 </p></li></ol>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_section640611565244"><h4 class="sectiontitle">Cluster Status</h4><p id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_p6765322135216">In the <strong id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_b1961612314104">Cluster Status</strong> area, you can view the status of the current cluster and the number of available resources, including the numbers of nodes, CNs, and databases.</p>
 <p id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_p12165137811"><span><img id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_image1096912131199" src="figure/en-us_image_0000001180320467.png" width="421.9425" height="190.05567000000002" title="Click to enlarge" class="imgResize"></span></p>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_section11820721193713"><h4 class="sectiontitle">Resource Consumption</h4><p id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_p169219520540">In <strong id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_b247395535614">Resource Consumption</strong>, you can view the real-time resource consumption of the current cluster, including <strong id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_b4669915185719">Memory Usage</strong>, <strong id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_b1771221813577">Disk Usage</strong>, <strong id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_b78347225576">CPU Usage</strong>, <strong id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_b15769202575719">Disk I/O (KB/s)</strong>, and <strong id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_b1034613327576">Network I/O (KB/s)</strong>.</p>
 <p id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_p79420394373"><span><img id="EN-US_TOPIC_0000001134560606__image1391820247" src="figure/en-us_image_0000001180440403.png" width="498.75" height="224.66187100000002" title="Click to enlarge" class="imgResize"></span></p>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_section20821161416386"><h4 class="sectiontitle">TOP SQL</h4><p id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_p182956415588">In the <strong id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_b11465162121220">TOP SQL</strong> area, you can query the SQL statements that take the longest time and have the largest amount of data flushed to disks in the current cluster.</p>
 <p id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_p13945164120432"></p>
 <p id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_p18121103110105"><span><img id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_image15561133271012" src="figure/en-us_image_0000001180440401.png" width="463.83750000000003" height="69.645317" title="Click to enlarge" class="imgResize"></span></p>
 <div class="note" id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_note673633183611"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_p29271356183614">Top 5 SQL statement query is implemented by <strong id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_b16588153414410">max_ctime</strong>, which displays the query duration and the amount of data written to disks in the current collection period. If no query is executed during off-peak hours, the top 5 time-consuming query page will not be refreshed.</p>
 </div></div>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_section134244517473"><h4 class="sectiontitle">Key Metrics</h4><p id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_p64580343418">On the <strong id="EN-US_TOPIC_0000001134560606__b4839162106">Cluster Overview</strong> page, you can also view the database metrics of the current cluster, including <strong id="EN-US_TOPIC_0000001134560606__b82701232151016">Sessions</strong> and <strong id="EN-US_TOPIC_0000001134560606__b1214873414103">Queries</strong>.</p>
 <p id="EN-US_TOPIC_0000001134560606__p6956153917485"><span><img id="EN-US_TOPIC_0000001134560606__image895911399484" src="figure/en-us_image_0000001152748072.png" width="431.9175" height="164.979451" title="Click to enlarge" class="imgResize"></span></p>
 <p id="EN-US_TOPIC_0000001134560606__p15299192884913"><span><img id="EN-US_TOPIC_0000001134560606__image930012285496" src="figure/en-us_image_0000001152588340.png" width="411.96750000000003" height="161.575981" title="Click to enlarge" class="imgResize"></span></p>
 </div>
 </div>
 <div>
 <div class="familylinks">
 <div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_00014.html">Databases Monitoring</a></div>
 </div>
 </div>
 <script language="JavaScript">
 <!--
 image_size('.imgResize');
 var msg_imageMax = "view original image";
 var msg_imageClose = "close";
 //--></script>
--- a/docs/dws/umn/dws_01_00133.html
+++ b/docs/dws/umn/dws_01_00133.html
@ -0,0 +1,27 @@
 <a name="EN-US_TOPIC_0000001134400706"></a><a name="EN-US_TOPIC_0000001134400706"></a>
 <h1 class="topictitle1">Monitoring</h1>
 <div id="body8662426"></div>
 <div>
 <ul class="ullinks">
 <li class="ulchildlink"><strong><a href="dws_01_1331.html">Node Monitoring</a></strong><br>
 </li>
 <li class="ulchildlink"><strong><a href="dws_01_1337.html">Performance Monitoring</a></strong><br>
 </li>
 <li class="ulchildlink"><strong><a href="dws_01_1332.html">Database Monitoring</a></strong><br>
 </li>
 <li class="ulchildlink"><strong><a href="dws_01_1333.html">Session Monitoring</a></strong><br>
 </li>
 <li class="ulchildlink"><strong><a href="dws_01_1334.html">Query Monitoring</a></strong><br>
 </li>
 <li class="ulchildlink"><strong><a href="dws_01_1338.html">Instance Monitoring</a></strong><br>
 </li>
 <li class="ulchildlink"><strong><a href="dws_01_1339.html">Load Monitoring</a></strong><br>
 </li>
 </ul>
 <div class="familylinks">
 <div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_00014.html">Databases Monitoring</a></div>
 </div>
 </div>
--- a/docs/dws/umn/dws_01_00134.html
+++ b/docs/dws/umn/dws_01_00134.html
@ -0,0 +1,45 @@
 <a name="EN-US_TOPIC_0000001134400694"></a><a name="EN-US_TOPIC_0000001134400694"></a>
 <h1 class="topictitle1">SQL Diagnosis</h1>
 <div id="body8662426"><div class="section" id="EN-US_TOPIC_0000001134400694__section319918146483"><h4 class="sectiontitle">Prerequisites</h4><p id="EN-US_TOPIC_0000001134400694__p1251662120482">To enable SQL diagnosis, enable monitoring on real-time and historical queries on the <strong id="EN-US_TOPIC_0000001134400694__b6495133912583">Queries</strong> and <strong id="EN-US_TOPIC_0000001134400694__b1081423755817">History</strong> tabs, respectively. For details, see .</p>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_section754243519236"><h4 class="sectiontitle">Viewing SQL Diagnosis</h4><ol id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_ol1482535782316"><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li3826105742313"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li1382685717234"><span>On the <span class="uicontrol" id="EN-US_TOPIC_0000001134400694__uicontrol164390960141226"><b>Clusters</b></span> page, locate the target cluster.</span></li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li118261257172315"><span>In the <strong id="EN-US_TOPIC_0000001134400694__b1251372210376">Operation</strong> column of the target cluster, click <strong id="EN-US_TOPIC_0000001134400694__b951322293715">Monitoring Panel</strong>.</span></li><li id="EN-US_TOPIC_0000001134400694__li645764432318"><span>In the navigation pane on the left, choose <strong id="EN-US_TOPIC_0000001134400694__b711712314515">Utilities</strong> &gt; <strong id="EN-US_TOPIC_0000001134400694__b788033654518">SQL Diagnosis</strong>. The metrics include:</span><p><ul id="EN-US_TOPIC_0000001134400694__ul1153203522418"><li id="EN-US_TOPIC_0000001134400694__li35324352248">Query ID</li><li id="EN-US_TOPIC_0000001134400694__li115321835142416">Database</li><li id="EN-US_TOPIC_0000001134400694__li18532163515240">Schema Name</li><li id="EN-US_TOPIC_0000001134400694__li35330356248">User Name</li><li id="EN-US_TOPIC_0000001134400694__li0533135122419">Client</li><li id="EN-US_TOPIC_0000001134400694__li16533153513249">Client IP Address</li><li id="EN-US_TOPIC_0000001134400694__li2533193515249">Running Time (ms)</li><li id="EN-US_TOPIC_0000001134400694__li5533113510247">CPU Time (ms)</li><li id="EN-US_TOPIC_0000001134400694__li18534235182412">Scale-Out Started</li><li id="EN-US_TOPIC_0000001134400694__li553423520248">Completed</li><li id="EN-US_TOPIC_0000001134400694__li1553493518248">Details</li></ul>
 </p></li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li8826165722320"><span>On the <strong id="EN-US_TOPIC_0000001134400694__b114256187541226">SQL Diagnosis</strong> page, you can view the SQL diagnosis information. In the <strong id="EN-US_TOPIC_0000001134400694__b85696733441226">Details</strong> column of a specified query ID, click <strong id="EN-US_TOPIC_0000001134400694__b184726947641226">View</strong> to view the detailed SQL diagnosis result, including:</span><p><ul id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_ul1826185742314"><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li1182635752315">Diagnosis Type</li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li28261157122311">Alarm Information</li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li12826135712318">SQL Statement</li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li5826175710232">Execution Plan</li></ul>
 <p id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_p4827185742312"><span><img id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_image782795742311" src="figure/en-us_image_0000001180320279.png" height="155.61" width="523.6875" title="Click to enlarge" class="imgResize"></span></p>
 </p></li></ol>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_section3665174263916"><a name="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_section3665174263916"></a><a name="en-us_topic_0000001076708521_section3665174263916"></a><h4 class="sectiontitle">Setting GUC Parameters</h4><p id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_p13607195214215">GUC parameters related to SQL diagnosis are as follows. For details, see "GUC Parameters" in the <em id="EN-US_TOPIC_0000001134400694__i921403194914">Data Warehouse Service (DWS) Developer Guide</em>.</p>
 <ul id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_ul7398112214435"><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li1039862211433"><strong id="EN-US_TOPIC_0000001134400694__b1263020504301">enable_resource_track</strong><ul id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_ul202211650124615"><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li5317031194713">Value range: boolean</li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li122811949467">Default value: <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b93482320537">on</strong></li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li162811140461">Expected DMS value: <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b185636561487">on</strong> (for reference only)</li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li152812434616">Function: Specifies whether to enable the real-time resource monitoring function.<div class="notice" id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_note123131752102517"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_p93131252112515">If this parameter is enabled without other GUC-related parameters correctly configured, real-time resource consumption cannot be recorded.</p>
 </div></div>
 </li></ul>
 </li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li7398322174317"><strong id="EN-US_TOPIC_0000001134400694__b2947115723813">resource_track_cost</strong><ul id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_ul7398132284315"><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li239813223439">Value range: an integer ranging from –1 to INT_MAX</li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li21884511488">Default value: <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b569231115413">100000</strong></li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li5398112244318">Expected DMS value: <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b14139151515420">0</strong> (for reference only)</li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li157155259447">Function: Specifies the minimum execution cost of statement resource monitoring for the current session. This parameter is valid only when <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b155164925518">enable_resource_track</strong> is <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b4168155110550">on</strong>.<div class="notice" id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_note1572611109254"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_p11726151012519">If this parameter is set to a small value, more statements will be recorded, causing record expansion and affecting cluster performance.</p>
 </div></div>
 </li></ul>
 </li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li1539862218434"><strong id="EN-US_TOPIC_0000001134400694__b175171235153919">resource_track_level</strong><ul id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_ul839812212439"><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li123706145215">Value range: enumerated type</li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li13457165345112">Default value: <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b22601016135619">query</strong></li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li13398172284314">Expected DMS value: <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b167885605616">query</strong> (for reference only)</li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li939862212431">Function: Specifies the resource monitoring level for the current session. This parameter is valid only when <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b131216113571">enable_resource_track</strong> is <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b1197781410571">on</strong>.<div class="notice" id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_note177951620112715"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_p37961120132717">If the resource monitoring is set to operator-level, performance will be greatly affected.</p>
 </div></div>
 </li></ul>
 </li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li113990225430"><strong id="EN-US_TOPIC_0000001134400694__b174777293433">resource_track_duration</strong><ul id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_ul5399192219438"><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li117094186536">Value range: an integer ranging from 0 to INT_MAX, in seconds</li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li1739910224431">Default value: <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b248432617582">60</strong>.</li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li03997221439">Expected DMS value: <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b9711143318580">0</strong> (for reference only)</li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li93999225432">Function: Specifies the minimum statement execution time that determines whether information about jobs of a statement recorded in the real-time view will be dumped to a historical view after the statement is executed. That is, only statements whose execution time exceeds the specified time are recorded in the historical view. This parameter is valid only when <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b10990522151">enable_resource_track</strong> is <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b49944221657">on</strong>.<div class="notice" id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_note3671193717277"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_p9692103732718">If this parameter is set to a small value, the batch processing mechanism for dumping kernel statements becomes invalid, affecting the kernel performance.</p>
 </div></div>
 </li></ul>
 </li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li193991922194314"><strong id="EN-US_TOPIC_0000001134400694__b16841030184413">topsql_retention_time</strong><ul id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_ul43990225434"><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li19601622135412">Value range: an integer ranging from 0 to 3650, in days</li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li1539922214315">Default value: <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b113471159854">0</strong></li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li9399122114314">Expected DMS value: <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b1498612181963">1</strong> (for reference only)</li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li7399422104318">Function: Specifies the aging time of <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b61309324619">pgxc_wlm_session_info</strong> data in the view.<div class="notice" id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_note46231565297"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_p56452062292">If this parameter is set to <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b178808441266">0</strong>, data will not be aged, which will cause storage expansion.</p>
 </div></div>
 </li></ul>
 </li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li1739919228434"><strong id="EN-US_TOPIC_0000001134400694__b19445172317459">enable_resource_record</strong><ul id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_ul1839972264315"><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li1354205155511">Value range: boolean</li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li239972217437">Default value: <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b157860521666">off</strong></li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li14399132274320">Expected DMS value: <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b131801582620">on</strong> (for reference only)</li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li193991122154314">Function: Specifies whether to enable the archiving function for resource monitoring records. When this function is enabled, records in the history views (<strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b1986311017911">GS_WLM_SESSION_HISTORY</strong> and <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b119821538915">GS_WLM_OPERATOR_HISTORY</strong>) are archived to the info views (<strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b2893291093">GS_WLM_SESSION_INFO</strong> and <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b16774812598">GS_WLM_OPERATOR_INFO</strong>) every 3 minutes. After the archiving, records in the history views are deleted.<div class="notice" id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_note42186208303"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_p14911102714305">When this parameter is enabled, you are advised to set <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b1297917372303">topsql_retention_time</strong> properly to configure the aging time. Otherwise, data in the <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b56665711312">GS_WLM_SESSION_INFO</strong> or <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b14234211133118">GS_WLM_OPERATOR_INFO</strong> table will expand.</p>
 </div></div>
 </li></ul>
 </li></ul>
 </div>
 </div>
 <div>
 <div class="familylinks">
 <div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_00175.html">Utilities</a></div>
 </div>
 </div>
 <script language="JavaScript">
 <!--
 image_size('.imgResize');
 var msg_imageMax = "view original image";
 var msg_imageClose = "close";
 //--></script>
--- a/docs/dws/umn/dws_01_00135.html
+++ b/docs/dws/umn/dws_01_00135.html
@ -0,0 +1,29 @@
 <a name="EN-US_TOPIC_0000001180320167"></a><a name="EN-US_TOPIC_0000001180320167"></a>
 <h1 class="topictitle1">Settings</h1>
 <div id="body8662426"><p id="EN-US_TOPIC_0000001180320167__en-us_topic_0000001076708691_p3469165714610">The <strong id="EN-US_TOPIC_0000001180320167__en-us_topic_0000001076708691_b9150125812432">Monitoring</strong> page displays the collection period and data aging period of monitoring metrics.</p>
 <div class="note" id="EN-US_TOPIC_0000001180320167__en-us_topic_0000001076708691_note211041641515"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001180320167__en-us_topic_0000001076708691_ul1779182553417"><li id="EN-US_TOPIC_0000001180320167__en-us_topic_0000001076708691_li1477922523411">The cluster monitoring function is enabled by default.</li><li id="EN-US_TOPIC_0000001180320167__en-us_topic_0000001076708691_li677982513417">Disable the function if the cluster is being recovered. Enable the function when the fault is rectified.</li><li id="EN-US_TOPIC_0000001180320167__en-us_topic_0000001076708691_li14538104683317">When a node in the cluster is powered off or the management IP address of the cluster is unavailable, the cluster monitoring switch and the button for configuring cluster indicator collection are unavailable.</li></ul>
 </div></div>
 <div class="section" id="EN-US_TOPIC_0000001180320167__en-us_topic_0000001076708691_section149871230683"><a name="EN-US_TOPIC_0000001180320167__en-us_topic_0000001076708691_section149871230683"></a><a name="en-us_topic_0000001076708691_section149871230683"></a><h4 class="sectiontitle">Monitoring Collection</h4><ol id="EN-US_TOPIC_0000001180320167__en-us_topic_0000001076708691_o4d27c72c9c5b483283c532fd703af879"><li id="EN-US_TOPIC_0000001180320167__en-us_topic_0000001076708691_l3bf4b8bc45d343b6aec0b48be7dfc1aa"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001180320167__en-us_topic_0000001076708691_li11952509114244"><span>On the <span class="uicontrol" id="EN-US_TOPIC_0000001180320167__en-us_topic_0000001076708691_uicontrol18681912302"><b>Clusters</b></span> page, locate the target cluster.</span></li><li id="EN-US_TOPIC_0000001180320167__en-us_topic_0000001076708691_li8798326172918"><span>In the <strong id="EN-US_TOPIC_0000001180320167__b9498559124914">Operation</strong> column of the target cluster, choose <strong id="EN-US_TOPIC_0000001180320167__b1549819593491">Monitoring Panel</strong>. The database monitoring page is displayed.</span></li><li id="EN-US_TOPIC_0000001180320167__en-us_topic_0000001076708691_li32311493910"><span>In the navigation pane on the left, choose <strong id="EN-US_TOPIC_0000001180320167__b7556181411504">Settings</strong> &gt; <strong id="EN-US_TOPIC_0000001180320167__b451418196503">Monitoring</strong>. You can reconfigure the collection frequency or disable the collection of the monitoring item.</span><p><p id="EN-US_TOPIC_0000001180320167__en-us_topic_0000001076708691_p1428184522919"><span><img id="EN-US_TOPIC_0000001180320167__en-us_topic_0000001076708691_image11824651309" src="figure/en-us_image_0000001180440311.png" width="442.89000000000004" height="203.58975" title="Click to enlarge" class="imgResize"></span></p>
 <div class="note" id="EN-US_TOPIC_0000001180320167__note1539832716207"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001180320167__p1239842732012">Click <strong id="EN-US_TOPIC_0000001180320167__b14557192491614">Update</strong> of <strong id="EN-US_TOPIC_0000001180320167__b1504105316197">DDL Audit</strong> to reset the automatic audit frequency or audit items.</p>
 <p id="EN-US_TOPIC_0000001180320167__p2305186162118"><span><img id="EN-US_TOPIC_0000001180320167__image114451137507" src="figure/en-us_image_0000001148353740.png" width="329.175" height="116.10806900000001" title="Click to enlarge" class="imgResize"></span></p>
 </div></div>
 </p></li></ol>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001180320167__en-us_topic_0000001076708691_section448614529112"><h4 class="sectiontitle">Collection Storage</h4><ol id="EN-US_TOPIC_0000001180320167__en-us_topic_0000001076708691_ol1113412515125"><li id="EN-US_TOPIC_0000001180320167__en-us_topic_0000001076708691_li1040416861710"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001180320167__en-us_topic_0000001076708691_li14404488172"><span>On the <span class="uicontrol" id="EN-US_TOPIC_0000001180320167__uicontrol12430573244946"><b>Clusters</b></span> page, locate the target cluster.</span></li><li id="EN-US_TOPIC_0000001180320167__en-us_topic_0000001076708691_li15632517113712"><span>In the <strong id="EN-US_TOPIC_0000001180320167__b174831115511">Operation</strong> column of the target cluster, choose <strong id="EN-US_TOPIC_0000001180320167__b24848118511">Monitoring Panel</strong>. The database monitoring page is displayed.</span></li><li id="EN-US_TOPIC_0000001180320167__en-us_topic_0000001076708691_li21344514125"><span>In the navigation pane on the left, choose <strong id="EN-US_TOPIC_0000001180320167__b1739042419517">Settings</strong> &gt; <strong id="EN-US_TOPIC_0000001180320167__b157902715116">Monitoring</strong> and switch to the <strong id="EN-US_TOPIC_0000001180320167__b487817348517">Collection Storage</strong> tab page. Update the retention days.</span><p><p id="EN-US_TOPIC_0000001180320167__en-us_topic_0000001076708691_p15589124016144"><span><img id="EN-US_TOPIC_0000001180320167__en-us_topic_0000001076708691_image5589204001418" src="figure/en-us_image_0000001134400944.png" height="201.21676399999998" width="478.8" title="Click to enlarge" class="imgResize"></span></p>
 </p></li></ol>
 </div>
 </div>
 <div>
 <div class="familylinks">
 <div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_00014.html">Databases Monitoring</a></div>
 </div>
 </div>
 <script language="JavaScript">
 <!--
 image_size('.imgResize');
 var msg_imageMax = "view original image";
 var msg_imageClose = "close";
 //--></script>
--- a/docs/dws/umn/dws_01_00136.html
+++ b/docs/dws/umn/dws_01_00136.html
--- a/docs/dws/umn/dws_01_00137.html
+++ b/docs/dws/umn/dws_01_00137.html
@ -0,0 +1,17 @@
 <a name="EN-US_TOPIC_0000001180320135"></a><a name="EN-US_TOPIC_0000001180320135"></a>
 <h1 class="topictitle1">Typical Scenarios</h1>
 <div id="body8662426"></div>
 <div>
 <ul class="ullinks">
 <li class="ulchildlink"><strong><a href="dws_01_01372.html">SQL Diagnosis</a></strong><br>
 </li>
 <li class="ulchildlink"><strong><a href="dws_01_01373.html">Top Time-Consuming SQL Statements Viewing</a></strong><br>
 </li>
 </ul>
 <div class="familylinks">
 <div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_00014.html">Databases Monitoring</a></div>
 </div>
 </div>
--- a/docs/dws/umn/dws_01_00175.html
+++ b/docs/dws/umn/dws_01_00175.html
@ -0,0 +1,18 @@
 <a name="EN-US_TOPIC_0000001147519336"></a><a name="EN-US_TOPIC_0000001147519336"></a>
 <h1 class="topictitle1">Utilities</h1>
 <div id="body0000001147519336"><p id="EN-US_TOPIC_0000001147519336__p8060118"></p>
 </div>
 <div>
 <ul class="ullinks">
 <li class="ulchildlink"><strong><a href="dws_01_00134.html">SQL Diagnosis</a></strong><br>
 </li>
 <li class="ulchildlink"><strong><a href="dws_01_01752.html">DDL Audit</a></strong><br>
 </li>
 </ul>
 <div class="familylinks">
 <div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_00014.html">Databases Monitoring</a></div>
 </div>
 </div>
--- a/docs/dws/umn/dws_01_0018.html
+++ b/docs/dws/umn/dws_01_0018.html
@ -0,0 +1,85 @@
 <a name="EN-US_TOPIC_0000001134560514"></a><a name="EN-US_TOPIC_0000001134560514"></a>
 <h1 class="topictitle1">Process for Using GaussDB(DWS)</h1>
 <div id="body1487833114714"><p id="EN-US_TOPIC_0000001134560514__p119261179247">GaussDB(DWS) is an online data processing database that uses the <span id="EN-US_TOPIC_0000001134560514__text12968717112010">cloud</span> infrastructure to provide scalable, fully-managed, and out-of-the-box analytic database service, freeing you from complex database management and monitoring. It is a native cloud service based on the converged data warehouse GaussDB, and is fully compatible with the standard ANSI SQL 99 and SQL 2003, as well as the PostgreSQL and Oracle ecosystems. GaussDB(DWS) provides competitive solutions for PB-level big data analysis in various industries.</p>
 <p id="EN-US_TOPIC_0000001134560514__p144744461214">GaussDB(DWS) provides an easy-to-use management console, allowing you to quickly create clusters and easily manage data warehouses.</p>
 <div class="section" id="EN-US_TOPIC_0000001134560514__section9634183414258"><h4 class="sectiontitle">Process Description</h4><div class="fignone" id="EN-US_TOPIC_0000001134560514__fig186511135153710"><span class="figcap"><b>Figure 1 </b>Process for using GaussDB(DWS)</span><br><span><img id="EN-US_TOPIC_0000001134560514__image57911942162113" src="figure/en-us_image_0000001180440277.png" width="NaN" height="NaN"></span></div>
 <div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="EN-US_TOPIC_0000001134560514__table118042014131911" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Process description</caption><thead align="left"><tr id="EN-US_TOPIC_0000001134560514__row980471411194"><th align="left" class="cellrowborder" valign="top" width="16.41%" id="mcps1.3.3.3.2.5.1.1"><p id="EN-US_TOPIC_0000001134560514__p180431491916">Process</p>
 </th>
 <th align="left" class="cellrowborder" valign="top" width="16.88%" id="mcps1.3.3.3.2.5.1.2"><p id="EN-US_TOPIC_0000001134560514__p18804201401918">Task</p>
 </th>
 <th align="left" class="cellrowborder" valign="top" width="35.27%" id="mcps1.3.3.3.2.5.1.3"><p id="EN-US_TOPIC_0000001134560514__p18804514181919">Description</p>
 </th>
 <th align="left" class="cellrowborder" valign="top" width="31.44%" id="mcps1.3.3.3.2.5.1.4"><p id="EN-US_TOPIC_0000001134560514__p68040141197">Operation Instruction</p>
 </th>
 </tr>
 </thead>
 <tbody><tr id="EN-US_TOPIC_0000001134560514__row569524210342"><td class="cellrowborder" valign="top" width="16.41%" headers="mcps1.3.3.3.2.5.1.1 "><p id="EN-US_TOPIC_0000001134560514__p13695174233413">Make preparations.</p>
 </td>
 <td class="cellrowborder" valign="top" width="16.88%" headers="mcps1.3.3.3.2.5.1.2 "><p id="EN-US_TOPIC_0000001134560514__p1069513425343">-</p>
 </td>
 <td class="cellrowborder" valign="top" width="35.27%" headers="mcps1.3.3.3.2.5.1.3 "><p id="EN-US_TOPIC_0000001134560514__p2962165851212">Before using GaussDB(DWS), select an open port on your firewall as the database port of your data warehouse cluster.</p>
 </td>
 <td class="cellrowborder" valign="top" width="31.44%" headers="mcps1.3.3.3.2.5.1.4 "><p id="EN-US_TOPIC_0000001134560514__p1869515425343"><a href="dws_01_0154.html">Preparations</a></p>
 </td>
 </tr>
 <tr id="EN-US_TOPIC_0000001134560514__row1780491461916"><td class="cellrowborder" valign="top" width="16.41%" headers="mcps1.3.3.3.2.5.1.1 "><p id="EN-US_TOPIC_0000001134560514__p13805171415198">Create a cluster.</p>
 </td>
 <td class="cellrowborder" valign="top" width="16.88%" headers="mcps1.3.3.3.2.5.1.2 "><p id="EN-US_TOPIC_0000001134560514__p47593523814">-</p>
 </td>
 <td class="cellrowborder" valign="top" width="35.27%" headers="mcps1.3.3.3.2.5.1.3 "><p id="EN-US_TOPIC_0000001134560514__p126301614114213">Create a cluster before using GaussDB(DWS) to execute data analysis tasks. A GaussDB(DWS) cluster contains nodes in the same subnet. These nodes jointly provide services. During cluster creation, the system creates a default database.</p>
 </td>
 <td class="cellrowborder" valign="top" width="31.44%" headers="mcps1.3.3.3.2.5.1.4 "><p id="EN-US_TOPIC_0000001134560514__p83996438911"><a href="dws_01_0019.html">Creating a Cluster</a></p>
 </td>
 </tr>
 <tr id="EN-US_TOPIC_0000001134560514__row7867168102818"><td class="cellrowborder" valign="top" width="16.41%" headers="mcps1.3.3.3.2.5.1.1 "><p id="EN-US_TOPIC_0000001134560514__p10115122932111">Connect to the cluster.</p>
 </td>
 <td class="cellrowborder" valign="top" width="16.88%" headers="mcps1.3.3.3.2.5.1.2 "><p id="EN-US_TOPIC_0000001134560514__p208671189283">-</p>
 </td>
 <td class="cellrowborder" valign="top" width="35.27%" headers="mcps1.3.3.3.2.5.1.3 "><p id="EN-US_TOPIC_0000001134560514__p7189125020373">After the data warehouse cluster is successfully created, use the SQL client tool or a third-party driver such as JDBC or ODBC to connect to the database in the cluster. You can download the SQL client tool and JDBC/ODBC driver on the <strong id="EN-US_TOPIC_0000001134560514__b148471359182814">Connection Management</strong> page of the GaussDB(DWS) management console.</p>
 </td>
 <td class="cellrowborder" valign="top" width="31.44%" headers="mcps1.3.3.3.2.5.1.4 "><p id="EN-US_TOPIC_0000001134560514__p142272563325"><a href="dws_01_0137.html">Methods of Connecting to a Cluster</a></p>
 </td>
 </tr>
 <tr id="EN-US_TOPIC_0000001134560514__row193781041152120"><td class="cellrowborder" valign="top" width="16.41%" headers="mcps1.3.3.3.2.5.1.1 "><p id="EN-US_TOPIC_0000001134560514__p837864152110">Access the database.</p>
 </td>
 <td class="cellrowborder" valign="top" width="16.88%" headers="mcps1.3.3.3.2.5.1.2 "><p id="EN-US_TOPIC_0000001134560514__p10378114132116">-</p>
 </td>
 <td class="cellrowborder" valign="top" width="35.27%" headers="mcps1.3.3.3.2.5.1.3 "><p id="EN-US_TOPIC_0000001134560514__p173788411212">After connecting to the cluster, you can create and manage databases, manage users and permissions, import and export data, and query and analyze data.</p>
 </td>
 <td class="cellrowborder" valign="top" width="31.44%" headers="mcps1.3.3.3.2.5.1.4 "><p id="EN-US_TOPIC_0000001134560514__p31831083427">Data Warehouse Service (DWS) Developer Guide</p>
 </td>
 </tr>
 <tr id="EN-US_TOPIC_0000001134560514__row860511553219"><td class="cellrowborder" rowspan="3" valign="top" width="16.41%" headers="mcps1.3.3.3.2.5.1.1 "><p id="EN-US_TOPIC_0000001134560514__p860513551216">Manage and monitor the cluster.</p>
 <p id="EN-US_TOPIC_0000001134560514__p1786973731516"></p>
 <p id="EN-US_TOPIC_0000001134560514__p38691437161517"></p>
 </td>
 <td class="cellrowborder" valign="top" width="16.88%" headers="mcps1.3.3.3.2.5.1.2 "><p id="EN-US_TOPIC_0000001134560514__p156054553217">Manage the cluster.</p>
 </td>
 <td class="cellrowborder" valign="top" width="35.27%" headers="mcps1.3.3.3.2.5.1.3 "><p id="EN-US_TOPIC_0000001134560514__p2580842184411">View the cluster status, modify cluster configurations, add cluster tags, and scale out, restart, and delete the cluster.</p>
 </td>
 <td class="cellrowborder" valign="top" width="31.44%" headers="mcps1.3.3.3.2.5.1.4 "><p id="EN-US_TOPIC_0000001134560514__p6913258125512"><a href="dws_01_0157.html">Managing clusters</a></p>
 </td>
 </tr>
 <tr id="EN-US_TOPIC_0000001134560514__row18970322194014"><td class="cellrowborder" valign="top" headers="mcps1.3.3.3.2.5.1.1 "><p id="EN-US_TOPIC_0000001134560514__p59704229407">Manage the snapshot.</p>
 </td>
 <td class="cellrowborder" valign="top" headers="mcps1.3.3.3.2.5.1.2 "><p id="EN-US_TOPIC_0000001134560514__p10970522124011">Create snapshots to back up and restore the cluster.</p>
 </td>
 <td class="cellrowborder" valign="top" headers="mcps1.3.3.3.2.5.1.3 "><p id="EN-US_TOPIC_0000001134560514__p49701122144018"><a href="dws_01_0151.html">Managing snapshots</a></p>
 </td>
 </tr>
 <tr id="EN-US_TOPIC_0000001134560514__row10253419154015"><td class="cellrowborder" valign="top" headers="mcps1.3.3.3.2.5.1.1 "><p id="EN-US_TOPIC_0000001134560514__p5254101913407">Perform O&amp;M and monitoring.</p>
 </td>
 <td class="cellrowborder" valign="top" headers="mcps1.3.3.3.2.5.1.2 "><p id="EN-US_TOPIC_0000001134560514__p72541519114012">View the running status and performance of the cluster through monitoring, log auditing, event notification, and resource load management.</p>
 </td>
 <td class="cellrowborder" valign="top" headers="mcps1.3.3.3.2.5.1.3 "><ul id="EN-US_TOPIC_0000001134560514__ul8102554205215"><li id="EN-US_TOPIC_0000001134560514__li1010212542521"><a href="dws_01_0022.html">Monitoring Clusters Using Cloud Eye</a></li><li id="EN-US_TOPIC_0000001134560514__li1410395435212"><a href="dws_01_0119.html">Audit Logs</a></li><li id="EN-US_TOPIC_0000001134560514__li53651214014">"Resource Load Management"<p id="EN-US_TOPIC_0000001134560514__p470532310018"><a name="EN-US_TOPIC_0000001134560514__li53651214014"></a><a name="li53651214014"></a>For details, see "Resource Load Management" in the <em id="EN-US_TOPIC_0000001134560514__i13105163282415">Data Warehouse Service (DWS) Developer Guide</em>.</p>
 </li></ul>
 </td>
 </tr>
 </tbody>
 </table>
 </div>
 </div>
 </div>
--- a/docs/dws/umn/dws_01_0019.html
+++ b/docs/dws/umn/dws_01_0019.html
--- a/docs/dws/umn/dws_01_0020.html
+++ b/docs/dws/umn/dws_01_0020.html
--- a/docs/dws/umn/dws_01_0021.html
+++ b/docs/dws/umn/dws_01_0021.html
@ -0,0 +1,70 @@
 <a name="EN-US_TOPIC_0000001180320191"></a><a name="EN-US_TOPIC_0000001180320191"></a>
 <h1 class="topictitle1">Viewing Snapshot Information</h1>
 <div id="body1489028034712"><p id="EN-US_TOPIC_0000001180320191__p9879121461112">This section describes how to view snapshot information on the <strong id="EN-US_TOPIC_0000001180320191__b5779114220582">Snapshots</strong> page.</p>
 <div class="section" id="EN-US_TOPIC_0000001180320191__section604430709348"><h4 class="sectiontitle">Viewing Snapshot Information</h4><ol id="EN-US_TOPIC_0000001180320191__ol6700273593546"><li id="EN-US_TOPIC_0000001180320191__li6029015714233"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001180320191__li3542231993721"><span>In the navigation pane on the left, choose <strong id="EN-US_TOPIC_0000001180320191__b1092754510116">Snapshots</strong>.</span><p><p id="EN-US_TOPIC_0000001180320191__p2374663163311">In the snapshot list, all snapshots are displayed by default. Click <span><img id="EN-US_TOPIC_0000001180320191__image10984101511227" src="figure/en-us_image_0000001180440325.jpg"></span> next to the snapshot name to display the snapshot details.</p>
 <p id="EN-US_TOPIC_0000001180320191__p181061038902"><span><img id="EN-US_TOPIC_0000001180320191__image14406913102311" src="figure/en-us_image_0000001277273485.png" width="460.845" height="100.850176" title="Click to enlarge" class="imgResize"></span></p>
 </p></li><li id="EN-US_TOPIC_0000001180320191__li25916796163327"><span>You can view <span class="parmname" id="EN-US_TOPIC_0000001180320191__parmname1321316399125"><b>Snapshot Name</b></span>, <span class="parmname" id="EN-US_TOPIC_0000001180320191__parmname32192039181219"><b>Snapshot Status</b></span>, <span class="parmname" id="EN-US_TOPIC_0000001180320191__parmname14219173913126"><b>Cluster Name</b></span>, <span class="parmname" id="EN-US_TOPIC_0000001180320191__parmname921917396123"><b>Snapshot Type</b></span>, and <span class="parmname" id="EN-US_TOPIC_0000001180320191__parmname82201639141215"><b>Snapshot Created</b></span> of snapshots.</span><p><p id="EN-US_TOPIC_0000001180320191__p3166646315049">You can also enter a snapshot name or cluster name in the upper right corner of the snapshot list and click <span><img id="EN-US_TOPIC_0000001180320191__image3902143220267" src="figure/en-us_image_0000001134560756.jpg"></span> to search for the specified snapshot. GaussDB(DWS) supports fuzzy search.</p>
 <p id="EN-US_TOPIC_0000001180320191__p57036249163450"><a href="#EN-US_TOPIC_0000001180320191__table3259774163926">Table 1</a> describes snapshot status.</p>
 <div class="tablenoborder"><a name="EN-US_TOPIC_0000001180320191__table3259774163926"></a><a name="table3259774163926"></a><table cellpadding="4" cellspacing="0" summary="" id="EN-US_TOPIC_0000001180320191__table3259774163926" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Snapshot status</caption><thead align="left"><tr id="EN-US_TOPIC_0000001180320191__r2d963a51fa864b3689b04a5b8cd5c0dd"><th align="left" class="cellrowborder" valign="top" width="30.64%" id="mcps1.3.2.2.3.2.3.2.3.1.1"><p id="EN-US_TOPIC_0000001180320191__a3267bb5462e64bb7b240d5ca758c980f"><strong id="EN-US_TOPIC_0000001180320191__a816cb4668a2f4064a090e5167d622d2c">Status</strong></p>
 </th>
 <th align="left" class="cellrowborder" valign="top" width="69.36%" id="mcps1.3.2.2.3.2.3.2.3.1.2"><p id="EN-US_TOPIC_0000001180320191__ac1719acbd21949f484d02c841c2fd893"><strong id="EN-US_TOPIC_0000001180320191__aa595a4cbe8d8489aa0d5bc7186ea6229">Description</strong></p>
 </th>
 </tr>
 </thead>
 <tbody><tr id="EN-US_TOPIC_0000001180320191__row43721954155529"><td class="cellrowborder" valign="top" width="30.64%" headers="mcps1.3.2.2.3.2.3.2.3.1.1 "><p id="EN-US_TOPIC_0000001180320191__p51817418155529"><strong id="EN-US_TOPIC_0000001180320191__b842352706141552">Available</strong></p>
 </td>
 <td class="cellrowborder" valign="top" width="69.36%" headers="mcps1.3.2.2.3.2.3.2.3.1.2 "><p id="EN-US_TOPIC_0000001180320191__p36461314155529">Indicates that the existing snapshot works properly.</p>
 </td>
 </tr>
 <tr id="EN-US_TOPIC_0000001180320191__r2f616610d43e4a66b61fce44aeede3d0"><td class="cellrowborder" valign="top" width="30.64%" headers="mcps1.3.2.2.3.2.3.2.3.1.1 "><p id="EN-US_TOPIC_0000001180320191__ac91a5857075b42c987315a0e3e60c702"><span class="parmvalue" id="EN-US_TOPIC_0000001180320191__pdcd12a9aeb7a4cbc8d0c9e21d71cb997"><b>Creating</b></span></p>
 </td>
 <td class="cellrowborder" valign="top" width="69.36%" headers="mcps1.3.2.2.3.2.3.2.3.1.2 "><p id="EN-US_TOPIC_0000001180320191__a0a59338e592f49a58a8653bd27a2fd01">Indicates that a snapshot is being created.</p>
 </td>
 </tr>
 <tr id="EN-US_TOPIC_0000001180320191__r4c26567fb82b4add8f1faf6f2f92e6cd"><td class="cellrowborder" valign="top" width="30.64%" headers="mcps1.3.2.2.3.2.3.2.3.1.1 "><p id="EN-US_TOPIC_0000001180320191__a18b35dcdcf864203a88a224f36603c18"><span class="parmname" id="EN-US_TOPIC_0000001180320191__parmname769647905144421"><b>Unavailable</b></span></p>
 </td>
 <td class="cellrowborder" valign="top" width="69.36%" headers="mcps1.3.2.2.3.2.3.2.3.1.2 "><p id="EN-US_TOPIC_0000001180320191__a129f02cb13d54d139fb03118f587cfe8">Indicates that the existing snapshot cannot provide services.</p>
 </td>
 </tr>
 </tbody>
 </table>
 </div>
 <p id="EN-US_TOPIC_0000001180320191__p46754595416"><a href="#EN-US_TOPIC_0000001180320191__table875924217540">Table 2</a> describes the snapshot types.</p>
 <div class="tablenoborder"><a name="EN-US_TOPIC_0000001180320191__table875924217540"></a><a name="table875924217540"></a><table cellpadding="4" cellspacing="0" summary="" id="EN-US_TOPIC_0000001180320191__table875924217540" frame="border" border="1" rules="all"><caption><b>Table 2 </b>Snapshot types</caption><thead align="left"><tr id="EN-US_TOPIC_0000001180320191__row2075914275411"><th align="left" class="cellrowborder" valign="top" width="31%" id="mcps1.3.2.2.3.2.5.2.3.1.1"><p id="EN-US_TOPIC_0000001180320191__p87601142155410"><strong id="EN-US_TOPIC_0000001180320191__b842352706101017">Type</strong></p>
 </th>
 <th align="left" class="cellrowborder" valign="top" width="69%" id="mcps1.3.2.2.3.2.5.2.3.1.2"><p id="EN-US_TOPIC_0000001180320191__p17760342165417"><strong id="EN-US_TOPIC_0000001180320191__b842352706191716">Description</strong></p>
 </th>
 </tr>
 </thead>
 <tbody><tr id="EN-US_TOPIC_0000001180320191__row376084214544"><td class="cellrowborder" valign="top" width="31%" headers="mcps1.3.2.2.3.2.5.2.3.1.1 "><p id="EN-US_TOPIC_0000001180320191__p47604425546"><strong id="EN-US_TOPIC_0000001180320191__b1148661513127">Manual</strong></p>
 </td>
 <td class="cellrowborder" valign="top" width="69%" headers="mcps1.3.2.2.3.2.5.2.3.1.2 "><p id="EN-US_TOPIC_0000001180320191__p2760144211543">Indicates the snapshot that you manually create through the GaussDB(DWS) management console or using APIs. You can delete the snapshots that are manually created.</p>
 </td>
 </tr>
 <tr id="EN-US_TOPIC_0000001180320191__row11760174213546"><td class="cellrowborder" valign="top" width="31%" headers="mcps1.3.2.2.3.2.5.2.3.1.1 "><p id="EN-US_TOPIC_0000001180320191__p476074211545"><strong id="EN-US_TOPIC_0000001180320191__b2811171711213">Automated</strong></p>
 </td>
 <td class="cellrowborder" valign="top" width="69%" headers="mcps1.3.2.2.3.2.5.2.3.1.2 "><p id="EN-US_TOPIC_0000001180320191__p11760104265413">Indicates the snapshot that is automatically created after the automated snapshot backup policy is enabled. You cannot delete the snapshots that are automatically created. The system automatically deletes the snapshots whose retention duration expires.</p>
 </td>
 </tr>
 </tbody>
 </table>
 </div>
 </p></li></ol>
 </div>
 </div>
 <div>
 <div class="familylinks">
 <div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0800.html">Snapshots</a></div>
 </div>
 </div>
 <script language="JavaScript">
 <!--
 image_size('.imgResize');
 var msg_imageMax = "view original image";
 var msg_imageClose = "close";
 //--></script>
--- a/docs/dws/umn/dws_01_0022.html
+++ b/docs/dws/umn/dws_01_0022.html
--- a/docs/dws/umn/dws_01_0023.html
+++ b/docs/dws/umn/dws_01_0023.html
@ -0,0 +1,30 @@
 <a name="EN-US_TOPIC_0000001180320133"></a><a name="EN-US_TOPIC_0000001180320133"></a>
 <h1 class="topictitle1">Cluster Scale-out</h1>
 <div id="body1488961602332"><p id="EN-US_TOPIC_0000001180320133__p8402182983118">As your data warehouse capacity and performance requirements change, you can adjust the sizes of existing clusters on the management console to utilize compute and storage resources provided by GaussDB(DWS).</p>
 <p id="EN-US_TOPIC_0000001180320133__p134408218445">After the data in a data warehouse is deleted, the occupied disk space may not be released, resulting in dirty data and disk waste. Therefore, if you need to scale out your cluster due to insufficient storage capacity, run the <strong id="EN-US_TOPIC_0000001180320133__b17795171015526">VACUUM</strong> command to reclaim the storage space first. If the used storage capacity is still high after you run the <strong id="EN-US_TOPIC_0000001180320133__b515936173214">VACUUM</strong> command, you can scale out your cluster. For details about <strong id="EN-US_TOPIC_0000001180320133__b445612102311">VACUUM</strong>, see "SQL Reference &gt; SQL Syntax &gt; VACUUM" in the <em id="EN-US_TOPIC_0000001180320133__i14466127231">Data Warehouse Service (DWS) Developer Guide</em>.</p>
 <div class="section" id="EN-US_TOPIC_0000001180320133__section60787995155336"><h4 class="sectiontitle">Impact on the System</h4><ul id="EN-US_TOPIC_0000001180320133__ul57109303161336"><li id="EN-US_TOPIC_0000001180320133__li1348416015143">Before the scale-out, exit the client connections that have created temporary tables because temporary tables created before or during the scale-out will become invalid and operations performed on these temporary tables will fail. Temporary tables created after the scale-out will not be affected.</li><li id="EN-US_TOPIC_0000001180320133__li61556958161336">During the scale-out, you cannot restart or scale a cluster, create a snapshot, reset a password, or delete a cluster.</li><li id="EN-US_TOPIC_0000001180320133__li93111498188">During the scale-out, the cluster automatically restarts. Therefore, the cluster stays <span class="parmname" id="EN-US_TOPIC_0000001180320133__parmname171311012115312"><b>Unavailable</b></span> for a period of time. After the cluster is restarted, the status becomes <strong id="EN-US_TOPIC_0000001180320133__b1113119129538">Available</strong>. After scale-out, the system dynamically redistributes user data among all nodes in the cluster.</li></ul>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001180320133__section6414583815542"><h4 class="sectiontitle">Prerequisites</h4><ul id="EN-US_TOPIC_0000001180320133__ul112577415568"><li id="EN-US_TOPIC_0000001180320133__li6030891915568">The cluster to be scaled out is in the <span class="parmname" id="EN-US_TOPIC_0000001180320133__parmname769647905164153"><b>Available</b></span> or <span class="parmname" id="EN-US_TOPIC_0000001180320133__parmname769647905164223"><b>Unbalanced</b></span> state.</li><li id="EN-US_TOPIC_0000001180320133__li1296127115568">The number of nodes to be added must be less than or equal to the available nodes. Otherwise, system scale-out is not allowed.</li></ul>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001180320133__section31992607155626"><h4 class="sectiontitle">Scaling Out a Cluster</h4><div class="note" id="EN-US_TOPIC_0000001180320133__note9257111105018"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001180320133__ul202301236904"><li id="EN-US_TOPIC_0000001180320133__li32306361500">A cluster becomes read-only during scale-out. Exercise caution when performing this operation.</li><li id="EN-US_TOPIC_0000001180320133__li8230173611019">To ensure data security, create a manual snapshot before scaling. For details about how to create a snapshot, see <a href="dws_01_0028.html">Manually Creating a Snapshot</a>.</li></ul>
 </div></div>
 <ol id="EN-US_TOPIC_0000001180320133__ol54072799155641"><li id="EN-US_TOPIC_0000001180320133__li391312411317"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001180320133__li11952509114244"><span>Choose <span class="uicontrol" id="EN-US_TOPIC_0000001180320133__uicontrol71966413309"><b>Clusters</b></span>.</span><p><p id="EN-US_TOPIC_0000001180320133__p2374663163311">All clusters are displayed by default.</p>
 </p></li><li id="EN-US_TOPIC_0000001180320133__li25916796163327"><span>In the <span class="parmname" id="EN-US_TOPIC_0000001180320133__parmname134851019185216"><b>Operation</b></span> column of the target cluster, choose <span class="menucascade" id="EN-US_TOPIC_0000001180320133__menucascade94921719115218"><b><span class="uicontrol" id="EN-US_TOPIC_0000001180320133__uicontrol12491191955211">More</span></b> &gt; <b><span class="uicontrol" id="EN-US_TOPIC_0000001180320133__uicontrol64921019155215">Scale Out</span></b></span>.</span><p><p id="EN-US_TOPIC_0000001180320133__p67015478161155">On the page that is displayed, the <strong id="EN-US_TOPIC_0000001180320133__b157761814539">Automated Backup</strong> button is enabled by default.</p>
 <p id="EN-US_TOPIC_0000001180320133__p5477131313118"></p>
 </p></li><li id="EN-US_TOPIC_0000001180320133__li11046151161353"><span>Specify the number of nodes to be added.</span><p><ul id="EN-US_TOPIC_0000001180320133__ul335865953115"><li id="EN-US_TOPIC_0000001180320133__li1844172816614">The number of nodes after scale-out must be at least three nodes more than the original number. The maximum number of nodes that can be added depends on the available quota. In addition, the number of nodes after the scale-out cannot exceed 256.<p id="EN-US_TOPIC_0000001180320133__p65621308611"><a name="EN-US_TOPIC_0000001180320133__li1844172816614"></a><a name="li1844172816614"></a>If the node quota is insufficient, click <strong id="EN-US_TOPIC_0000001180320133__b3232144134719">Increase quota</strong> to submit a service ticket and apply for higher node quota.</p>
 </li><li id="EN-US_TOPIC_0000001180320133__li435814595318">Flavor of the new nodes must be the same as that of existing nodes in the cluster.</li><li id="EN-US_TOPIC_0000001180320133__li435835913111">The VPC, subnet, and security group of the cluster with new nodes added are the same as those of the original cluster.</li></ul>
 </p></li><li id="EN-US_TOPIC_0000001180320133__li1283703664815"><a name="EN-US_TOPIC_0000001180320133__li1283703664815"></a><a name="li1283703664815"></a><span>Configure advanced parameters. If you choose <strong id="EN-US_TOPIC_0000001180320133__b4380537165717">Custom</strong>, you can enable <strong id="EN-US_TOPIC_0000001180320133__b12381143710579">Online Scale-out</strong> and <strong id="EN-US_TOPIC_0000001180320133__b5381123775718">Auto Redistribution</strong>, and set <strong id="EN-US_TOPIC_0000001180320133__b93811937145712">Redistribution Mode</strong> to <strong id="EN-US_TOPIC_0000001180320133__b163811937155710">Online</strong>. Click <strong id="EN-US_TOPIC_0000001180320133__b838163725710">OK</strong> if a message is prompted.</span><p><p id="EN-US_TOPIC_0000001180320133__p11838163615489">If you choose <strong id="EN-US_TOPIC_0000001180320133__b223010492578">Default</strong>, <strong id="EN-US_TOPIC_0000001180320133__b19230149145717">Online Scale-out</strong> will be disabled, <strong id="EN-US_TOPIC_0000001180320133__b1023011492578">Auto Redistribution</strong> will be enabled, and <strong id="EN-US_TOPIC_0000001180320133__b14230204916579">Redistribution Mode</strong> will be <strong id="EN-US_TOPIC_0000001180320133__b1023074918577">Offline</strong> by default.</p>
 </p></li><li id="EN-US_TOPIC_0000001180320133__li1730493616170"><span>Click <strong id="EN-US_TOPIC_0000001180320133__b3970237203211">Next: Confirm</strong>.</span></li><li id="EN-US_TOPIC_0000001180320133__li14228155311269"><span>Click <span class="uicontrol" id="EN-US_TOPIC_0000001180320133__uicontrol560935258173140"><b>Scale Out Now</b></span>.</span><p><div class="note" id="EN-US_TOPIC_0000001180320133__note16842317193715"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001180320133__en-us_topic_0106894662_p11100461860">If the number of requested nodes, vCPU (cores), or memory (GB) exceed the user's remaining quota, a warning dialog box is displayed, indicating that the quota is insufficient and displaying the detailed remaining quota and the current quota application. You can click <strong id="EN-US_TOPIC_0000001180320133__b161991632203114">Increase quota</strong> in the warning dialog box to submit a service ticket and apply for higher node quota.</p>
 <p id="EN-US_TOPIC_0000001180320133__en-us_topic_0106894662_p059217011304">For details about quotas, see <a href="dws_03_0034.html">What Is the User Quota?</a>.</p>
 </div></div>
 </p></li><li id="EN-US_TOPIC_0000001180320133__li47734902152356"><span>Click <span class="uicontrol" id="EN-US_TOPIC_0000001180320133__uicontrol14581747163911"><b>Submit</b></span>.</span><p><ul id="EN-US_TOPIC_0000001180320133__ul4088238314358"><li id="EN-US_TOPIC_0000001180320133__li686436714536">After you submit the scale-out application, task information of the cluster changes to <span class="uicontrol" id="EN-US_TOPIC_0000001180320133__uicontrol230942777171033"><b>Scaling out</b></span> and the process will take several minutes. During the scale-out, the cluster automatically restarts. Therefore, the cluster status will stay <span class="parmname" id="EN-US_TOPIC_0000001180320133__parmname574935810188"><b>Unavailable</b></span> for a while. After the cluster is restarted, the status will change to <strong id="EN-US_TOPIC_0000001180320133__b1232629101912">Available</strong>. In the last phase of scale-out, the system dynamically redistributes user data in the cluster, during which the cluster is in the <strong id="EN-US_TOPIC_0000001180320133__b16142135619322">Read-only</strong> state.</li><li id="EN-US_TOPIC_0000001180320133__li3129985914358">A cluster is successfully scaled out only when the cluster is in the <span class="uicontrol" id="EN-US_TOPIC_0000001180320133__uicontrol99151461661"><b>Available</b></span> state and task information <span class="uicontrol" id="EN-US_TOPIC_0000001180320133__uicontrol109213462614"><b>Scaling out</b></span> is not displayed. Then you can use the cluster.</li><li id="EN-US_TOPIC_0000001180320133__li4727440814358">If <strong id="EN-US_TOPIC_0000001180320133__b0887213715">Scale-out failed</strong> is displayed, the cluster fails to be scaled out.</li></ul>
 </p></li></ol>
 </div>
 </div>
 <div>
 <div class="familylinks">
 <div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0600.html">Clusters</a></div>
 </div>
 </div>
--- a/docs/dws/umn/dws_01_0024.html
+++ b/docs/dws/umn/dws_01_0024.html
@ -0,0 +1,18 @@
 <a name="EN-US_TOPIC_0000001134560520"></a><a name="EN-US_TOPIC_0000001134560520"></a>
 <h1 class="topictitle1">Cluster Restart</h1>
 <div id="body1489027756989"><p id="EN-US_TOPIC_0000001134560520__p1339352416305">If a cluster is in the <strong id="EN-US_TOPIC_0000001134560520__b3991499361">Unbalanced</strong> state or cannot work properly, you may need to restart it for restoration. After modifying a cluster's configurations, such as security settings and parameters in the parameter template, manually restart the cluster to make the configurations take effect.</p>
 <div class="section" id="EN-US_TOPIC_0000001134560520__section33979687105031"><h4 class="sectiontitle">Impact on the System</h4><ul id="EN-US_TOPIC_0000001134560520__ul2692121616"><li id="EN-US_TOPIC_0000001134560520__li22239498495">A cluster cannot provide services during the restart. Therefore, before the restart, ensure that no task is running and all data is saved.<p id="EN-US_TOPIC_0000001134560520__p106801824145115"><a name="EN-US_TOPIC_0000001134560520__li22239498495"></a><a name="li22239498495"></a>If the cluster is processing service data, such as importing data, querying data, creating snapshots, or restoring snapshots, cluster restarting will cause file damage or restart failure. You are advised to stop all cluster tasks before restarting the cluster.</p>
 <p id="EN-US_TOPIC_0000001134560520__p040875705210">View the <span class="parmvalue" id="EN-US_TOPIC_0000001134560520__parmvalue124102576527"><b>Session Count</b></span> and <span class="parmvalue" id="EN-US_TOPIC_0000001134560520__parmvalue34109575524"><b>Active SQL Count</b></span> metrics to check whether the cluster has active events. For details, see <a href="dws_01_0022.html">Monitoring Clusters Using Cloud Eye</a>.</p>
 </li><li id="EN-US_TOPIC_0000001134560520__li156911151617">The time required for restarting a cluster depends on the cluster scale and services. Generally, it takes about 3 minutes to restart a cluster. The duration does not exceed 20 minutes.</li><li id="EN-US_TOPIC_0000001134560520__li1669141181616">If the restart fails, the cluster may be unavailable. Try again later or contact technical support.</li></ul>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001134560520__section59074732104918"><h4 class="sectiontitle">Procedure</h4><ol id="EN-US_TOPIC_0000001134560520__ol53148594104951"><li id="EN-US_TOPIC_0000001134560520__li1790212596317"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001134560520__li640122716457"><span>Click <span class="uicontrol" id="EN-US_TOPIC_0000001134560520__uicontrol5761104616457"><b>Clusters</b></span>.</span></li><li id="EN-US_TOPIC_0000001134560520__li28325161164515"><span>In the <strong id="EN-US_TOPIC_0000001134560520__b842352706154943">Operation</strong> column of the cluster to be restarted, click <strong id="EN-US_TOPIC_0000001134560520__b842352706155026">Restart</strong>.</span></li><li id="EN-US_TOPIC_0000001134560520__li48630339105019"><span>In the dialog box that is displayed, click <span class="uicontrol" id="EN-US_TOPIC_0000001134560520__uicontrol1345370416853"><b>Yes</b></span>.</span><p><p id="EN-US_TOPIC_0000001134560520__p3369423610522"><span class="parmname" id="EN-US_TOPIC_0000001134560520__parmname769647905102435"><b>Task Information</b></span> changes to <span class="parmvalue" id="EN-US_TOPIC_0000001134560520__parmvalue555125744102457"><b>Restarting</b></span>. When <span class="parmname" id="EN-US_TOPIC_0000001134560520__parmname1323243201091"><b>Cluster Status</b></span> changes to <span class="parmvalue" id="EN-US_TOPIC_0000001134560520__parmvalue555125744102546"><b>Available</b></span> again, the cluster is successfully restarted.</p>
 </p></li></ol>
 </div>
 </div>
 <div>
 <div class="familylinks">
 <div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0600.html">Clusters</a></div>
 </div>
 </div>
--- a/docs/dws/umn/dws_01_0025.html
+++ b/docs/dws/umn/dws_01_0025.html
@ -0,0 +1,28 @@
 <a name="EN-US_TOPIC_0000001180440139"></a><a name="EN-US_TOPIC_0000001180440139"></a>
 <h1 class="topictitle1">Deleting Clusters</h1>
 <div id="body1490579992871"><p id="EN-US_TOPIC_0000001180440139__p5309913114">If you do not need to use a cluster, perform the operations in this section to delete it.</p>
 <div class="section" id="EN-US_TOPIC_0000001180440139__section6977716114930"><h4 class="sectiontitle">Impact on the System</h4><p id="EN-US_TOPIC_0000001180440139__p18466637114935">Deleted clusters cannot be recovered. Additionally, you cannot access user data and automated snapshots in a deleted cluster because the data and snapshots are automatically deleted. If you delete a cluster, its manual snapshots will not be deleted.</p>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001180440139__section13594386114220"><h4 class="sectiontitle">Deleting a Cluster</h4><ol id="EN-US_TOPIC_0000001180440139__ol65599416114244"><li id="EN-US_TOPIC_0000001180440139__li1793484014417"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001180440139__li99391743172913"><span>Click <span><img id="EN-US_TOPIC_0000001180440139__image16795151617455" src="figure/en-us_image_0000001180320367.png"></span> in the upper left corner of the management console to select a region.</span></li><li id="EN-US_TOPIC_0000001180440139__li11952509114244"><span>On the <span class="uicontrol" id="EN-US_TOPIC_0000001180440139__uicontrol26231314813"><b>Clusters</b></span> page, locate the cluster to be deleted.</span></li><li id="EN-US_TOPIC_0000001180440139__li25916796163327"><span>Locate the row that contains the target cluster, and choose <span class="menucascade" id="EN-US_TOPIC_0000001180440139__menucascade18256683145811"><b><span class="uicontrol" id="EN-US_TOPIC_0000001180440139__uicontrol30092420145811">More</span></b> &gt; <b><span class="uicontrol" id="EN-US_TOPIC_0000001180440139__uicontrol2396330145811">Delete</span></b></span>.</span><p><p id="EN-US_TOPIC_0000001180440139__p193839413277"><span><img id="EN-US_TOPIC_0000001180440139__image66124032715" src="figure/en-us_image_0000001450747689.png" width="475.8075" height="144.951646" title="Click to enlarge" class="imgResize"></span></p>
 </p></li><li id="EN-US_TOPIC_0000001180440139__li74701137202918"><span>In the displayed dialog box, confirm the deletion. You can determine whether to perform the following operations:</span><p><ul id="EN-US_TOPIC_0000001180440139__ul9917131012373"><li id="EN-US_TOPIC_0000001180440139__li79171310173719">Create a snapshot for the cluster.<p id="EN-US_TOPIC_0000001180440139__p1753343293714"><a name="EN-US_TOPIC_0000001180440139__li79171310173719"></a><a name="li79171310173719"></a>If the cluster status is normal, you can click <span class="uicontrol" id="EN-US_TOPIC_0000001180440139__uicontrol1520727143715"><b>Create Snapshot</b></span>. In the dialog box that is displayed, enter the snapshot name and click <strong id="EN-US_TOPIC_0000001180440139__b188956219114">OK</strong> to create a snapshot for the cluster to be deleted. After the snapshot is created, go back to the <strong id="EN-US_TOPIC_0000001180440139__b1823919161116">Clusters</strong> page and delete the cluster.</p>
 </li><li id="EN-US_TOPIC_0000001180440139__li19917510193711">Release the EIP bound to the cluster.<p id="EN-US_TOPIC_0000001180440139__p20939112014615"><a name="EN-US_TOPIC_0000001180440139__li19917510193711"></a><a name="li19917510193711"></a>If the cluster is bound with an EIP, you can click <span class="uicontrol" id="EN-US_TOPIC_0000001180440139__uicontrol2361849985918"><b>Release the EIP bound to the cluster</b></span> to release the EIP of the cluster to be deleted. </p>
 </li></ul>
 <p id="EN-US_TOPIC_0000001180440139__p0163144020351"><span><img id="EN-US_TOPIC_0000001180440139__image195121641153520" src="figure/en-us_image_0000001450883809.png" width="423.9375" height="134.085945" title="Click to enlarge" class="imgResize"></span></p>
 </p></li><li id="EN-US_TOPIC_0000001180440139__li5202642114647"><span>Click <span class="uicontrol" id="EN-US_TOPIC_0000001180440139__uicontrol1389081034510"><b>Yes</b></span>.</span><p><p id="EN-US_TOPIC_0000001180440139__p1155820538397">If the cluster to be deleted uses an automatically created security group that is not used by other clusters, the security group is automatically deleted after the cluster is deleted.</p>
 </p></li></ol>
 </div>
 </div>
 <div>
 <div class="familylinks">
 <div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0600.html">Clusters</a></div>
 </div>
 </div>
 <script language="JavaScript">
 <!--
 image_size('.imgResize');
 var msg_imageMax = "view original image";
 var msg_imageClose = "close";
 //--></script>
--- a/docs/dws/umn/dws_01_0026.html
+++ b/docs/dws/umn/dws_01_0026.html
@ -0,0 +1,26 @@
 <a name="EN-US_TOPIC_0000001180440053"></a><a name="EN-US_TOPIC_0000001180440053"></a>
 <h1 class="topictitle1">Password Reset</h1>
 <div id="body1505702483110"><p id="EN-US_TOPIC_0000001180440053__p1995114013172">GaussDB(DWS) allows you to reset the password of the database administrator. If a database administrator forgets their password or the account is locked because the number of consecutive incorrect password attempts reaches the upper limit, the database administrator can reset the password on the <span class="parmname" id="EN-US_TOPIC_0000001180440053__parmname72851312453"><b>Clusters</b></span> page. After the password is reset, the account can be automatically unlocked. You can set the maximum number of incorrect password attempts (10 by default) by configuring the <a href="dws_01_0152.html#EN-US_TOPIC_0000001134560528__section926416313488">failed_login_attempts</a> parameter on the <strong id="EN-US_TOPIC_0000001180440053__b115002242598">Parameter Modifications</strong> tab of the cluster. For details, see <a href="dws_01_0152.html">Modifying Database Parameters</a>.</p>
 <div class="section" id="EN-US_TOPIC_0000001180440053__section59074732104918"><h4 class="sectiontitle">Resetting a Password</h4><ol id="EN-US_TOPIC_0000001180440053__ol53148594104951"><li id="EN-US_TOPIC_0000001180440053__li14267203810115"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001180440053__li640122716457"><span>Choose <span class="uicontrol" id="EN-US_TOPIC_0000001180440053__uicontrol85961931977"><b>Clusters</b></span>.</span></li><li id="EN-US_TOPIC_0000001180440053__li28325161164515"><span>In the <strong id="EN-US_TOPIC_0000001180440053__b842352706111636">Operation</strong> column of the target cluster, choose <span class="uicontrol" id="EN-US_TOPIC_0000001180440053__uicontrol230942777111927"><b>More</b></span> &gt; <span class="uicontrol" id="EN-US_TOPIC_0000001180440053__uicontrol230942777111937"><b>Reset Password</b></span>.</span><p><div class="fignone" id="EN-US_TOPIC_0000001180440053__fig6184953135917"><span class="figcap"><b>Figure 1 </b>Password resetting</span><br><span><img id="EN-US_TOPIC_0000001180440053__image5536648135918" src="figure/en-us_image_0000001134400838.png" width="465.5" height="309.45668600000005" title="Click to enlarge" class="imgResize"></span></div>
 </p></li><li id="EN-US_TOPIC_0000001180440053__li4507328414055"><span>On the displayed <span class="uicontrol" id="EN-US_TOPIC_0000001180440053__uicontrol1392361118173711"><b>Reset Password</b></span> page, set a new password, confirm the password, and then click <span class="uicontrol" id="EN-US_TOPIC_0000001180440053__uicontrol409515376173711"><b>OK</b></span>.</span><p><div class="p" id="EN-US_TOPIC_0000001180440053__p28582013103116">The password complexity requirements are as follows:<ul id="EN-US_TOPIC_0000001180440053__ue389ad2f3aa5470484fa087e28427ed7"><li id="EN-US_TOPIC_0000001180440053__en-us_topic_0106894662_li14183138142">Contains 8 to 32 characters.</li><li id="EN-US_TOPIC_0000001180440053__l74fe7d31380b48208fb0ff63c167c83d">Cannot be the username or the username spelled backwards.</li><li id="EN-US_TOPIC_0000001180440053__l67a2f75d35aa4f77bfba2654af9a7980">Must contain at least three of the following character types: uppercase letters, lowercase letters, digits, and special characters (~!`?,.:;-_'"(){}[]/&lt;&gt;@#%^&amp;*+|\=)</li><li id="EN-US_TOPIC_0000001180440053__l7db73fd0c15f463b8c0c82f13969046a">Passes the weak password check.</li></ul>
 </div>
 <ul id="EN-US_TOPIC_0000001180440053__ul34947930165918"><li id="EN-US_TOPIC_0000001180440053__li5310473315382">Cannot be the same as the old password and cannot be the reverse of the old password.</li><li id="EN-US_TOPIC_0000001180440053__li43440644165918">Cannot use a historical password.</li></ul>
 <div class="note" id="EN-US_TOPIC_0000001180440053__note3679362819227"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001180440053__p38221833192213">If the default cluster administrator account is deleted or renamed, password resetting fails.</p>
 </div></div>
 </p></li></ol>
 </div>
 </div>
 <div>
 <div class="familylinks">
 <div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0600.html">Clusters</a></div>
 </div>
 </div>
 <script language="JavaScript">
 <!--
 image_size('.imgResize');
 var msg_imageMax = "view original image";
 var msg_imageClose = "close";
 //--></script>
--- a/docs/dws/umn/dws_01_0028.html
+++ b/docs/dws/umn/dws_01_0028.html
@ -0,0 +1,26 @@
 <a name="EN-US_TOPIC_0000001134400690"></a><a name="EN-US_TOPIC_0000001134400690"></a>
 <h1 class="topictitle1">Manually Creating a Snapshot</h1>
 <div id="body1489028034712"><div class="section" id="EN-US_TOPIC_0000001134400690__section1477216229438"><h4 class="sectiontitle">Prerequisites</h4><p id="EN-US_TOPIC_0000001134400690__p1065715319430">A snapshot is a complete backup that records point-in-time configuration data and service data of a GaussDB(DWS) cluster. This section describes how to create a snapshot on the <span class="parmname" id="EN-US_TOPIC_0000001134400690__parmname66577316438"><b>Snapshots</b></span> page to back up cluster data.</p>
 <p id="EN-US_TOPIC_0000001134400690__p16338147171311">A manual snapshot can be created at any time. It will be retained until it is deleted from the GaussDB (DWS) console. Manual snapshots are full backups, which takes a long time to create.</p>
 <div class="note" id="EN-US_TOPIC_0000001134400690__note166571431154313"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001134400690__ul15451824182318"><li id="EN-US_TOPIC_0000001134400690__li1654542410236">Manual snapshots can be backed up to OBS.</li><li id="EN-US_TOPIC_0000001134400690__li1727592842316">Snapshots can be created only for clusters in <strong id="EN-US_TOPIC_0000001134400690__b2729821114910">Available</strong>, <strong id="EN-US_TOPIC_0000001134400690__b67594231498">Read-only</strong>, or <strong id="EN-US_TOPIC_0000001134400690__b54231826184918">Unbalanced</strong> state.</li></ul>
 </div></div>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001134400690__section11322194214310"><h4 class="sectiontitle">Impact on the System</h4><p id="EN-US_TOPIC_0000001134400690__p18083415240">If a snapshot is being created for a cluster, the cluster cannot be restarted, scaled, its password cannot be reset, and its configurations cannot be modified.</p>
 <div class="note" id="EN-US_TOPIC_0000001134400690__note7511115534315"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001134400690__p9680205553411">To ensure the integrity of snapshot data, do not write data during snapshot creation.</p>
 </div></div>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001134400690__section16983121394412"><h4 class="sectiontitle">Procedure</h4><ol id="EN-US_TOPIC_0000001134400690__ol18177133210270"><li id="EN-US_TOPIC_0000001134400690__li16457172684412"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001134400690__li2457102615443"><span>In the navigation pane, choose <strong id="EN-US_TOPIC_0000001134400690__b877610141634">Snapshots</strong>.</span></li><li id="EN-US_TOPIC_0000001134400690__li12457226134410"><span>Click <strong id="EN-US_TOPIC_0000001134400690__b112151931834">Create Snapshot</strong> and enter snapshot information.</span><p><ul id="EN-US_TOPIC_0000001134400690__ul1249818102816"><li id="EN-US_TOPIC_0000001134400690__li1745716266444"><span class="parmname" id="EN-US_TOPIC_0000001134400690__parmname17432173614314"><b>Cluster Name</b></span>: Select a GaussDB(DWS) cluster from the drop-down list. The drop-down list only displays clusters that are in the <span class="parmvalue" id="EN-US_TOPIC_0000001134400690__parmvalue21781766175737"><b>Available</b></span> state.</li><li id="EN-US_TOPIC_0000001134400690__li16457112684411"><strong id="EN-US_TOPIC_0000001134400690__b16471071344">Snapshot Name</strong>: Enter a snapshot name. The snapshot name must be 4 to 64 characters in length and start with a letter. It is case-insensitive and contains only letters, digits, hyphens (-), and underscores (_).</li><li id="EN-US_TOPIC_0000001134400690__li3491018182816"><strong id="EN-US_TOPIC_0000001134400690__b51131940412">Snapshot Description</strong>: Enter the snapshot information. This parameter is optional. Snapshot information contains 0 to 256 characters and does not support the following special characters: !&lt;&gt;'=&amp;"</li></ul>
 <div class="fignone" id="EN-US_TOPIC_0000001134400690__fig123933161931"><span class="figcap"><b>Figure 1 </b>Creating a snapshot</span><br><span><img id="EN-US_TOPIC_0000001134400690__image155965014316" src="figure/en-us_image_0000001231733612.png" width="NaN" height="NaN"></span></div>
 </p></li><li id="EN-US_TOPIC_0000001134400690__li10757512816"><span>Click <strong id="EN-US_TOPIC_0000001134400690__b1856514542412">OK</strong>.</span><p><p id="EN-US_TOPIC_0000001134400690__p1745872694420">The task status of the cluster for which you are creating a snapshot is <span class="parmvalue" id="EN-US_TOPIC_0000001134400690__parmvalue12728490775737"><b>Creating snapshot</b></span>. The status of the snapshot that is being created is <span class="parmvalue" id="EN-US_TOPIC_0000001134400690__parmvalue125500610975737"><b>Creating</b></span>. After the snapshot is created, its status becomes <span class="parmvalue" id="EN-US_TOPIC_0000001134400690__parmvalue98023720075737"><b>Available</b></span>.</p>
 <div class="note" id="EN-US_TOPIC_0000001134400690__note124581926104417"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001134400690__p1145818267444">If the snapshot size is much greater than that of the data stored in the cluster, the data is possibly labeled with a deletion tag, but is not cleared and reclaimed. Clear the data and recreate a snapshot. For details, see <a href="dws_03_0033.html">How Can I Clear and Reclaim Storage?</a></p>
 </div></div>
 </p></li></ol>
 </div>
 </div>
 <div>
 <div class="familylinks">
 <div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0092.html">Manual Snapshots</a></div>
 </div>
 </div>
--- a/docs/dws/umn/dws_01_0029.html
+++ b/docs/dws/umn/dws_01_0029.html
@ -0,0 +1,58 @@
 <a name="EN-US_TOPIC_0000001180320217"></a><a name="EN-US_TOPIC_0000001180320217"></a>
 <h1 class="topictitle1">Restoring a Snapshot to a New Cluster</h1>
 <div id="body1490579992871"><div class="section" id="EN-US_TOPIC_0000001180320217__section197315504370"><h4 class="sectiontitle">Scenario</h4><p id="EN-US_TOPIC_0000001180320217__p8060118">This section describes how to restore a snapshot to a new cluster when you want to check point-in-time snapshot data of the cluster.</p>
 <p id="EN-US_TOPIC_0000001180320217__p044212315597">When a snapshot is restored to a new cluster, the restoration time is determined by the amount of data backed up by the snapshot. If a snapshot contains a large amount of data, the restoration will be slow. A small snapshot can be quickly restored.</p>
 <p id="EN-US_TOPIC_0000001180320217__p13264151563816">Automatic snapshots are incremental backups. When restoring a snapshot to a new cluster, GaussDB(DWS) uses all snapshots between the latest full backup and the current snapshot. You can configure the backup frequency. If snapshots are backed up only once a week, the backup will be slow if the incremental data volume is large. You are advised to increase the backup frequency.</p>
 <div class="notice" id="EN-US_TOPIC_0000001180320217__note182641215143812"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><ul id="EN-US_TOPIC_0000001180320217__ul6264181513386"><li id="EN-US_TOPIC_0000001180320217__li14264181593815">Currently, you can only use the snapshots stored in OBS to restore data to a new cluster.</li><li id="EN-US_TOPIC_0000001180320217__li201078341115">By default, the new cluster created during restoration has the same specifications and node quantity as the original cluster.</li><li id="EN-US_TOPIC_0000001180320217__li18413205913342">Restoring data to a new cluster does not affect the services running in the original cluster.</li><li id="EN-US_TOPIC_0000001180320217__li784317167201">If cold and hot tables are used, snapshots cannot be used to restore cold data to a new cluster.</li></ul>
 </div></div>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001180320217__section7335122917"><h4 class="sectiontitle">Prerequisites</h4><ul id="EN-US_TOPIC_0000001180320217__ul9708105143016"><li id="EN-US_TOPIC_0000001180320217__li128011511524">The resources required for restoring data to a new cluster do not exceed your available resource quota.</li><li id="EN-US_TOPIC_0000001180320217__li387171343010">The snapshot is in the <strong id="EN-US_TOPIC_0000001180320217__b59171013461">Available</strong> state.</li></ul>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001180320217__section3487218143910"><h4 class="sectiontitle">Procedure</h4><ol id="EN-US_TOPIC_0000001180320217__ol12013513315"><li id="EN-US_TOPIC_0000001180320217__li185333863918"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001180320217__li985319381394"><span>In the navigation pane, choose <strong id="EN-US_TOPIC_0000001180320217__b897061410466">Snapshots</strong>. All snapshots are displayed by default.</span></li><li id="EN-US_TOPIC_0000001180320217__li344634433115"><span>In the <strong id="EN-US_TOPIC_0000001180320217__b535122015465">Operation</strong> column of a snapshot, click <strong id="EN-US_TOPIC_0000001180320217__b10361520104615">Restore</strong>.</span><p><p id="EN-US_TOPIC_0000001180320217__p154851351173117"><span><img id="EN-US_TOPIC_0000001180320217__image17457113773114" src="figure/en-us_image_0000001276994681.png" width="427.9275" height="56.283073" title="Click to enlarge" class="imgResize"></span></p>
 </p></li><li id="EN-US_TOPIC_0000001180320217__li8160533194219"><span>Configure the parameters of the new cluster, as shown in the following figure.</span><p><p id="EN-US_TOPIC_0000001180320217__p137778510424"></p>
 <p id="EN-US_TOPIC_0000001180320217__p1391418416426"><span><img id="EN-US_TOPIC_0000001180320217__image145460431427" src="figure/en-us_image_0000001381824320.png" width="437.90250000000003" height="346.07171900000003" title="Click to enlarge" class="imgResize"></span></p>
 <p id="EN-US_TOPIC_0000001180320217__p1112719920170">You can modify cluster parameters. For details, see <a href="#EN-US_TOPIC_0000001180320217__table2991343171911">Table 1</a>. By default, other parameters are the same as those in the snapshot. For details, see <a href="dws_01_0089.html#EN-US_TOPIC_0000001231278872__table1355651818416">Table 2</a>.</p>
 <div class="tablenoborder"><a name="EN-US_TOPIC_0000001180320217__table2991343171911"></a><a name="table2991343171911"></a><table cellpadding="4" cellspacing="0" summary="" id="EN-US_TOPIC_0000001180320217__table2991343171911" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Parameters for the new cluster</caption><thead align="left"><tr id="EN-US_TOPIC_0000001180320217__row19991204317197"><th align="left" class="cellrowborder" valign="top" width="21.22%" id="mcps1.3.3.2.4.2.4.2.3.1.1"><p id="EN-US_TOPIC_0000001180320217__p2099124351916">Category</p>
 </th>
 <th align="left" class="cellrowborder" valign="top" width="78.78%" id="mcps1.3.3.2.4.2.4.2.3.1.2"><p id="EN-US_TOPIC_0000001180320217__p169911443111916">Operation</p>
 </th>
 </tr>
 </thead>
 <tbody><tr id="EN-US_TOPIC_0000001180320217__row11991194316199"><td class="cellrowborder" valign="top" width="21.22%" headers="mcps1.3.3.2.4.2.4.2.3.1.1 "><p id="EN-US_TOPIC_0000001180320217__p9991114316198">Basic</p>
 </td>
 <td class="cellrowborder" valign="top" width="78.78%" headers="mcps1.3.3.2.4.2.4.2.3.1.2 "><p id="EN-US_TOPIC_0000001180320217__p1199118438195">Configure the region, AZ, node flavor, cluster name, database port, VPC, subnet, security group, public access, and enterprise project.</p>
 </td>
 </tr>
 <tr id="EN-US_TOPIC_0000001180320217__row1146920132016"><td class="cellrowborder" valign="top" width="21.22%" headers="mcps1.3.3.2.4.2.4.2.3.1.1 "><p id="EN-US_TOPIC_0000001180320217__p15146162092017">Advanced settings</p>
 </td>
 <td class="cellrowborder" valign="top" width="78.78%" headers="mcps1.3.3.2.4.2.4.2.3.1.2 "><div class="p" id="EN-US_TOPIC_0000001180320217__p18762515200">If <span class="parmvalue" id="EN-US_TOPIC_0000001180320217__parmvalue15266143611489"><b>Custom</b></span> is selected, configure the following parameters:<ul id="EN-US_TOPIC_0000001180320217__ul5840537172013"><li id="EN-US_TOPIC_0000001180320217__li5331957122610">If <strong id="EN-US_TOPIC_0000001180320217__b07371939144816">Automated Snapshot</strong> is enabled, you can configure the following parameters:<ul id="EN-US_TOPIC_0000001180320217__ul1795240112615"><li id="EN-US_TOPIC_0000001180320217__li993718122219"><strong id="EN-US_TOPIC_0000001180320217__b192321843134817">Retention Days</strong></li><li id="EN-US_TOPIC_0000001180320217__li499813151219"><strong id="EN-US_TOPIC_0000001180320217__b156571644154811">Start Time</strong></li><li id="EN-US_TOPIC_0000001180320217__li0791259172519"><strong id="EN-US_TOPIC_0000001180320217__b66583462481">Execution Period</strong></li></ul>
 </li><li id="EN-US_TOPIC_0000001180320217__li1315185782710"><strong id="EN-US_TOPIC_0000001180320217__b5186773499">Parameter Template</strong></li><li id="EN-US_TOPIC_0000001180320217__li38409371207"><strong id="EN-US_TOPIC_0000001180320217__b533869194919">Tag</strong>: If encryption is enabled for the original cluster, you can configure a key name.</li></ul>
 </div>
 </td>
 </tr>
 </tbody>
 </table>
 </div>
 </p></li><li id="EN-US_TOPIC_0000001180320217__li18688111631"><span>Click <strong id="EN-US_TOPIC_0000001180320217__b19849131413497">Restore</strong> to go to the confirmation page.</span></li><li id="EN-US_TOPIC_0000001180320217__li573921115318"><span>Click <span class="uicontrol" id="EN-US_TOPIC_0000001180320217__uicontrol8901220164911"><b>Submit</b></span> to restore the snapshot to the new cluster.</span><p><p id="EN-US_TOPIC_0000001180320217__p1785311388395">When the status of the new cluster changes to <span class="parmvalue" id="EN-US_TOPIC_0000001180320217__parmvalue4417125174916"><b>Available</b></span>, the snapshot is restored.</p>
 <p id="EN-US_TOPIC_0000001180320217__p4853163823912">After the snapshot is restored, the private network address and EIP (if <span class="parmname" id="EN-US_TOPIC_0000001180320217__parmname1196852814911"><b>EIP</b></span> is set to <span class="parmvalue" id="EN-US_TOPIC_0000001180320217__parmvalue43329305175241"><b>Automatically assign</b></span>) are automatically assigned. </p>
 <div class="note" id="EN-US_TOPIC_0000001180320217__note17854133817391"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001180320217__p6854103810396">If the number of requested nodes, vCPU (cores), or memory (GB) exceed the user's remaining quota, a warning dialog box is displayed, indicating that the quota is insufficient and displaying the detailed remaining quota and the current quota application. You can click <strong id="EN-US_TOPIC_0000001180320217__b152955218495">Increase quota</strong> in the warning dialog box to submit a service ticket and apply for higher node quota.</p>
 <p id="EN-US_TOPIC_0000001180320217__p13245117153115">For details about quotas, see <a href="dws_03_0034.html">What Is the User Quota?</a>.</p>
 </div></div>
 </p></li></ol>
 </div>
 </div>
 <div>
 <div class="familylinks">
 <div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_1015.html">Restoration Using a Snapshot</a></div>
 </div>
 </div>
 <script language="JavaScript">
 <!--
 image_size('.imgResize');
 var msg_imageMax = "view original image";
 var msg_imageClose = "close";
 //--></script>
--- a/docs/dws/umn/dws_01_0030.html
+++ b/docs/dws/umn/dws_01_0030.html
@ -0,0 +1,26 @@
 <a name="EN-US_TOPIC_0000001134400748"></a><a name="EN-US_TOPIC_0000001134400748"></a>
 <h1 class="topictitle1">Deleting Manual Snapshots</h1>
 <div id="body1489028034712"><p id="EN-US_TOPIC_0000001134400748__p28661527131316">On the <strong id="EN-US_TOPIC_0000001134400748__b197048491455">Snapshots</strong> page, you can delete a snapshot in the <strong id="EN-US_TOPIC_0000001134400748__b197101491515">Unavailable</strong> state or delete an available snapshot to release the storage space.</p>
 <div class="caution" id="EN-US_TOPIC_0000001134400748__note17133141595519"><span class="cautiontitle"><img src="public_sys-resources/caution_3.0-en-us.png"> </span><div class="cautionbody"><p id="EN-US_TOPIC_0000001134400748__p17133131513551">Deleted snapshots cannot be restored. Exercise caution when performing this operation.</p>
 </div></div>
 <div class="section" id="EN-US_TOPIC_0000001134400748__section12353184964319"><h4 class="sectiontitle">Procedure</h4><ol id="EN-US_TOPIC_0000001134400748__ol57278144410"><li id="EN-US_TOPIC_0000001134400748__li472831104417"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001134400748__li9728131154419"><span>In the navigation pane, choose <strong id="EN-US_TOPIC_0000001134400748__b1295171611619">Snapshots</strong>. All snapshots are displayed by default.</span></li><li id="EN-US_TOPIC_0000001134400748__li1172812118449"><span>In the <span class="uicontrol" id="EN-US_TOPIC_0000001134400748__uicontrol56399261469"><b>Operation</b></span> column of the snapshot that you want to delete, click <span class="uicontrol" id="EN-US_TOPIC_0000001134400748__uicontrol146444261862"><b>Delete</b></span>.</span><p><div class="p" id="EN-US_TOPIC_0000001134400748__p122225818554"><span><img id="EN-US_TOPIC_0000001134400748__image1298699135518" src="figure/en-us_image_0000001232385296.png" width="493.76250000000005" height="62.966057000000006" title="Click to enlarge" class="imgResize"></span><div class="note" id="EN-US_TOPIC_0000001134400748__note172891124419"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001134400748__p47287118445">You can delete snapshots that are manually created only.</p>
 </div></div>
 </div>
 </p></li><li id="EN-US_TOPIC_0000001134400748__li2542115310557"><span>In the dialog box that is displayed, confirm the information and click <span class="uicontrol" id="EN-US_TOPIC_0000001134400748__uicontrol6182953887"><b>Yes</b></span> to delete the snapshot.</span><p><p id="EN-US_TOPIC_0000001134400748__p101381256125512"><span><img id="EN-US_TOPIC_0000001134400748__image882934719557" src="figure/en-us_image_0000001232385392.png" width="482.79" height="136.31037" title="Click to enlarge" class="imgResize"></span></p>
 </p></li></ol>
 </div>
 </div>
 <div>
 <div class="familylinks">
 <div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0092.html">Manual Snapshots</a></div>
 </div>
 </div>
 <script language="JavaScript">
 <!--
 image_size('.imgResize');
 var msg_imageMax = "view original image";
 var msg_imageClose = "close";
 //--></script>
--- a/docs/dws/umn/dws_01_0031.html
+++ b/docs/dws/umn/dws_01_0031.html
@ -0,0 +1,70 @@
 <a name="EN-US_TOPIC_0000001180320153"></a><a name="EN-US_TOPIC_0000001180320153"></a>
 <h1 class="topictitle1">Downloading the Client</h1>
 <div id="body1492143168050"><p id="EN-US_TOPIC_0000001180320153__p084514013113">GaussDB(DWS) provides client tool packages that match the cluster versions. You can download the desired client tool package on the GaussDB(DWS) management console.</p>
 <p id="EN-US_TOPIC_0000001180320153__p181638390132">The client tool package contains the following:</p>
 <ul id="EN-US_TOPIC_0000001180320153__ul19221210171418"><li id="EN-US_TOPIC_0000001180320153__li3935152512013"><strong id="EN-US_TOPIC_0000001180320153__b842352706174250">Database connection tool gsql and the script for testing sample data</strong><p id="EN-US_TOPIC_0000001180320153__p2571434171413">gsql is a command line client running on the Linux operating system. It is used to connect to the database in a data warehouse cluster.</p>
 <p id="EN-US_TOPIC_0000001180320153__p1613923519198">The script for testing sample data is used when you start an example.</p>
 </li><li id="EN-US_TOPIC_0000001180320153__li122341021417"><strong id="EN-US_TOPIC_0000001180320153__b84235270617464">GDS tool package</strong><p id="EN-US_TOPIC_0000001180320153__p1199612611505">Gauss Data Service (GDS) is a data service tool. You can use the GDS tool to import a data file in a common file system to the GaussDB(DWS) database. The GDS tool package must be installed on the server where the data source file is located. The server where the data source file is located is called a data server or GDS server.</p>
 </li></ul>
 <div class="section" id="EN-US_TOPIC_0000001180320153__section22966852154814"><h4 class="sectiontitle">Downloading the Client</h4><ol id="EN-US_TOPIC_0000001180320153__ol60386497154929"><li id="EN-US_TOPIC_0000001180320153__li115408565467"><span>Log in to the GaussDB(DWS) console. For details, see <a href="dws_01_0157.html">Accessing the GaussDB(DWS) Management Console</a>.</span></li><li id="EN-US_TOPIC_0000001180320153__li25411875155123"><span>In the navigation pane on the left, click <span class="uicontrol" id="EN-US_TOPIC_0000001180320153__uicontrol63258372318"><b>Connections</b></span>.</span></li><li id="EN-US_TOPIC_0000001180320153__li50432353163955"><span>Select the GaussDB(DWS) client of the corresponding version from the drop-down list of <strong id="EN-US_TOPIC_0000001180320153__b1123718691314"><span id="EN-US_TOPIC_0000001180320153__text16236466137">gsql CLI</span></strong><strong id="EN-US_TOPIC_0000001180320153__b42373615131"> Client</strong>.</span><p><p id="EN-US_TOPIC_0000001180320153__p53255496174429">Choose a corresponding client version according to the cluster version and operating system to which the client is to be installed.</p>
 <ul id="EN-US_TOPIC_0000001180320153__ul48178451102440"><li id="EN-US_TOPIC_0000001180320153__li40265179102440">The <span class="parmvalue" id="EN-US_TOPIC_0000001180320153__parmvalue185145216941423"><b>Redhat x86_64</b></span> client can be used on the following OSs:<ul id="EN-US_TOPIC_0000001180320153__ul57548944102440"><li id="EN-US_TOPIC_0000001180320153__li19084831102440">RHEL 6.4 to RHEL 7.6</li><li id="EN-US_TOPIC_0000001180320153__li37545756102440">CentOS 6.4 to CentOS 7.4</li><li id="EN-US_TOPIC_0000001180320153__li21307408102440">EulerOS 2.3</li></ul>
 </li><li id="EN-US_TOPIC_0000001180320153__li53666696102443">The <span class="parmvalue" id="EN-US_TOPIC_0000001180320153__parmvalue12536662141423"><b>SUSE x86_64</b></span> client can be used on the following OSs:<ul id="EN-US_TOPIC_0000001180320153__ul276428104814"><li id="EN-US_TOPIC_0000001180320153__li138112612482">SLES 11.1 to SLES 11.4</li><li id="EN-US_TOPIC_0000001180320153__li135376307483">SLES 12.0 to SLES 12.3</li></ul>
 </li></ul>
 <div class="fignone" id="EN-US_TOPIC_0000001180320153__fig1547010371642"><span class="figcap"><b>Figure 1 </b>Downloading a gsql client</span><br><span><img id="EN-US_TOPIC_0000001180320153__image13276105485117" src="figure/en-us_image_0000001180320363.png" width="465.5" height="113.229683" title="Click to enlarge" class="imgResize"></span></div>
 </p></li><li id="EN-US_TOPIC_0000001180320153__li1668501401317"><span>Click <span class="uicontrol" id="EN-US_TOPIC_0000001180320153__uicontrol2520533171315"><b>Download</b></span> to download the gsql tool matching the current cluster version. Click <strong id="EN-US_TOPIC_0000001180320153__b227971010510">Historical Version</strong> to download the gsql tool corresponding to the cluster version.</span><p><p id="EN-US_TOPIC_0000001180320153__p954411872219">If clusters of different versions are available, you will download the gsql tool matching the earliest cluster version after clicking <strong id="EN-US_TOPIC_0000001180320153__b1941819363521">Download</strong>. If there is no cluster, you will download the gsql tool of the earliest version after clicking <strong id="EN-US_TOPIC_0000001180320153__b1875355435220">Download</strong>. GaussDB(DWS) clusters are compatible with earlier versions of gsql tools.</p>
 <div class="note" id="EN-US_TOPIC_0000001180320153__note122577579305"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001180320153__ul337172318265"><li id="EN-US_TOPIC_0000001180320153__li937162392610">In the cluster list on the <span class="wintitle" id="EN-US_TOPIC_0000001180320153__wintitle54952276571"><b>Clusters</b></span> page, click the name of the specified cluster and click the <span class="parmname" id="EN-US_TOPIC_0000001180320153__parmname14971127195713"><b>Basic Information</b></span> tab to view the cluster version.</li></ul>
 </div></div>
 <p id="EN-US_TOPIC_0000001180320153__p8571718143220"><a href="#EN-US_TOPIC_0000001180320153__t8fecf5f1a1ff445ba5451382c11182a8">Table 1</a> lists the files and folders in the downloaded tool package.</p>
 <div class="tablenoborder"><a name="EN-US_TOPIC_0000001180320153__t8fecf5f1a1ff445ba5451382c11182a8"></a><a name="t8fecf5f1a1ff445ba5451382c11182a8"></a><table cellpadding="4" cellspacing="0" summary="" id="EN-US_TOPIC_0000001180320153__t8fecf5f1a1ff445ba5451382c11182a8" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Files and folders in the downloaded tool package</caption><thead align="left"><tr id="EN-US_TOPIC_0000001180320153__rcf6a7cd1410646c3acd6e06c0ccfca93"><th align="left" class="cellrowborder" valign="top" width="16.85%" id="mcps1.3.4.2.4.2.4.2.3.1.1"><p id="EN-US_TOPIC_0000001180320153__a2d989a0f459b4417bba469e9ed198487"><strong id="EN-US_TOPIC_0000001180320153__b69101326152320">File or Folder</strong></p>
 </th>
 <th align="left" class="cellrowborder" valign="top" width="83.15%" id="mcps1.3.4.2.4.2.4.2.3.1.2"><p id="EN-US_TOPIC_0000001180320153__aaeee215110904fd980f4d74fb697efa8"><strong id="EN-US_TOPIC_0000001180320153__b088613306237">Description</strong></p>
 </th>
 </tr>
 </thead>
 <tbody><tr id="EN-US_TOPIC_0000001180320153__r3fe1a64e58d840b68538183c0d634a44"><td class="cellrowborder" valign="top" width="16.85%" headers="mcps1.3.4.2.4.2.4.2.3.1.1 "><p id="EN-US_TOPIC_0000001180320153__a8a16b90d41ac422882ceb1df761fabca">bin</p>
 </td>
 <td class="cellrowborder" valign="top" width="83.15%" headers="mcps1.3.4.2.4.2.4.2.3.1.2 "><p id="EN-US_TOPIC_0000001180320153__p123406261119">This folder contains the executable files of gsql on Linux, including the tools gsql, GDS, gs_dump, gs_dumpall, and gs_restore. For details, see <span id="EN-US_TOPIC_0000001180320153__ph15517122333919">"Server Tool"</span>.</p>
 </td>
 </tr>
 <tr id="EN-US_TOPIC_0000001180320153__r9403c771cae94e57b5c78dcbf033db71"><td class="cellrowborder" valign="top" width="16.85%" headers="mcps1.3.4.2.4.2.4.2.3.1.1 "><p id="EN-US_TOPIC_0000001180320153__en-us_topic_0167984001_p26124344180">gds</p>
 </td>
 <td class="cellrowborder" valign="top" width="83.15%" headers="mcps1.3.4.2.4.2.4.2.3.1.2 "><p id="EN-US_TOPIC_0000001180320153__a6e13c2b0c15a4c4f8c41015ec5674d75">This folder contains the files of the GDS data service tool. The GDS tool is used for parallel data loading and can import the data files stored in a common file system to a GaussDB(DWS) database.</p>
 </td>
 </tr>
 <tr id="EN-US_TOPIC_0000001180320153__r8fa2f8f3ee034fad830ecc96be19d2c7"><td class="cellrowborder" valign="top" width="16.85%" headers="mcps1.3.4.2.4.2.4.2.3.1.1 "><p id="EN-US_TOPIC_0000001180320153__a4daca4a9648d4be28c33e7ca06195cad">lib</p>
 </td>
 <td class="cellrowborder" valign="top" width="83.15%" headers="mcps1.3.4.2.4.2.4.2.3.1.2 "><p id="EN-US_TOPIC_0000001180320153__a112b44845bf84b19a1a16faf8bbf57bf">This folder contains the <strong id="EN-US_TOPIC_0000001180320153__b173701618142811">lib</strong> library required for executing the gsql client.</p>
 </td>
 </tr>
 <tr id="EN-US_TOPIC_0000001180320153__r8f8cba67c64f4653a2ce6c538ad47efa"><td class="cellrowborder" valign="top" width="16.85%" headers="mcps1.3.4.2.4.2.4.2.3.1.1 "><p id="EN-US_TOPIC_0000001180320153__en-us_topic_0167984001_p262033412186">sample</p>
 </td>
 <td class="cellrowborder" valign="top" width="83.15%" headers="mcps1.3.4.2.4.2.4.2.3.1.2 "><p id="EN-US_TOPIC_0000001180320153__p143194163914">This folder contains the following directories and files:</p>
 <ul id="EN-US_TOPIC_0000001180320153__ul5636131718426"><li id="EN-US_TOPIC_0000001180320153__li26368171424"><strong id="EN-US_TOPIC_0000001180320153__b532919672915">setup.sh</strong>: script file for configuring the AK/SK before using gsql to import sample data</li><li id="EN-US_TOPIC_0000001180320153__li363615171420"><strong id="EN-US_TOPIC_0000001180320153__b1883144373019">tpcds_load_data_from_obs.sql</strong>: script file for importing the TPC-DS sample data using the gsql client</li><li id="EN-US_TOPIC_0000001180320153__li1163671754216"><strong id="EN-US_TOPIC_0000001180320153__b172233389324">query_sql</strong> directory: script file for querying the TPC-DS sample data</li></ul>
 </td>
 </tr>
 <tr id="EN-US_TOPIC_0000001180320153__r8751b7a9c87a4e149dbfb35b6744e2f3"><td class="cellrowborder" valign="top" width="16.85%" headers="mcps1.3.4.2.4.2.4.2.3.1.1 "><p id="EN-US_TOPIC_0000001180320153__a2d03bd9607494e44bf9680f3511d999f">gsql_env.sh</p>
 </td>
 <td class="cellrowborder" valign="top" width="83.15%" headers="mcps1.3.4.2.4.2.4.2.3.1.2 "><p id="EN-US_TOPIC_0000001180320153__a484ec47d1b2c4d57b9e5b81a1f4bbdb0">Script file for configuring environment variables before running the gsql client.</p>
 </td>
 </tr>
 </tbody>
 </table>
 </div>
 </p></li></ol>
 </div>
 </div>
 <div>
 <div class="familylinks">
 <div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0093.html">Using the gsql CLI Client to Connect to a Cluster</a></div>
 </div>
 </div>
 <script language="JavaScript">
 <!--
 image_size('.imgResize');
 var msg_imageMax = "view original image";
 var msg_imageClose = "close";
 //--></script>
--- a/docs/dws/umn/dws_01_0032.html
+++ b/docs/dws/umn/dws_01_0032.html
@ -0,0 +1,25 @@
 <a name="EN-US_TOPIC_0000001180320147"></a><a name="EN-US_TOPIC_0000001180320147"></a>
 <h1 class="topictitle1">Downloading the JDBC or ODBC Driver</h1>
 <div id="body1492143168050"><p id="EN-US_TOPIC_0000001180320147__p1339464612462">The JDBC or ODBC driver is used to connect to data warehouse clusters. You can download the JDBC or ODBC driver provided by GaussDB(DWS) from the management console or use the open-source JDBC or ODBC driver.</p>
 <div class="section" id="EN-US_TOPIC_0000001180320147__section583116715476"><h4 class="sectiontitle">Open-Source JDBC or ODBC Driver</h4><p id="EN-US_TOPIC_0000001180320147__p7035726113931">GaussDB(DWS) also supports open-source JDBC and ODBC drivers: PostgreSQL JDBC 9.3-1103 or later; PostgreSQL ODBC 09.01.0200 or later</p>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001180320147__section8483877102527"><h4 class="sectiontitle">Downloading the JDBC or ODBC Driver</h4><ol id="EN-US_TOPIC_0000001180320147__ol60630376102536"><li id="EN-US_TOPIC_0000001180320147__li6029015714233"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001180320147__li14529230102538"><span>In the navigation pane on the left, click <span class="uicontrol"><b>Connections</b></span>.</span></li><li id="EN-US_TOPIC_0000001180320147__li6336035910265"><span>In the <span class="parmname" id="EN-US_TOPIC_0000001180320147__parmname54049730103334"><b>Driver</b></span> area, choose a driver that you want to download.</span><p><ul id="EN-US_TOPIC_0000001180320147__ul14144775102648"><li id="EN-US_TOPIC_0000001180320147__li21256942102648"><strong id="EN-US_TOPIC_0000001180320147__b1417719385355">JDBC Driver</strong><p id="EN-US_TOPIC_0000001180320147__p4385957103243">Select <span class="parmvalue" id="EN-US_TOPIC_0000001180320147__parmvalue3549338810335"><b>DWS JDBC Driver</b></span> and click <span class="uicontrol" id="EN-US_TOPIC_0000001180320147__uicontrol23451325115320"><b>Download</b></span> to download the JDBC driver matching the current cluster version. If clusters of different versions are available, you will download the JDBC driver matching the earliest cluster version after clicking <strong id="EN-US_TOPIC_0000001180320147__b257613484224">Download</strong>. If there is no cluster, you will download the JDBC driver of the earliest version after clicking <strong id="EN-US_TOPIC_0000001180320147__b2576148122217">Download</strong>. GaussDB(DWS) clusters are compatible with earlier versions of JDBC drivers.</p>
 <p id="EN-US_TOPIC_0000001180320147__p11241008371">Click <strong id="EN-US_TOPIC_0000001180320147__b5280113017548">Historical Version</strong> to download the corresponding JDBC driver version. You are advised to download the JDBC driver based on the cluster version.</p>
 <p id="EN-US_TOPIC_0000001180320147__p21797570103353">The JDBC driver can be used on all platforms and depends on JDK 1.6 or later.</p>
 </li><li id="EN-US_TOPIC_0000001180320147__li27972870103241"><strong id="EN-US_TOPIC_0000001180320147__b1351917211544">ODBC Driver</strong><p id="EN-US_TOPIC_0000001180320147__p5529786010357">Select a corresponding version and click <span class="uicontrol" id="EN-US_TOPIC_0000001180320147__uicontrol13517184215412"><b>Download</b></span> to download the ODBC driver matching the current cluster version. If clusters of different versions are available, you will download the ODBC driver matching the earliest cluster version after clicking <strong id="EN-US_TOPIC_0000001180320147__b1397605614221">Download</strong>. If there is no cluster, you will download the ODBC driver of the earliest version after clicking <strong id="EN-US_TOPIC_0000001180320147__b15977125611228">Download</strong>. GaussDB(DWS) clusters are compatible with earlier versions of ODBC drivers.</p>
 <p id="EN-US_TOPIC_0000001180320147__p2975132017371">Click <strong id="EN-US_TOPIC_0000001180320147__b84417316551">Historical Version</strong> to download the corresponding ODBC driver version. You are advised to download the ODBC driver based on the cluster version.</p>
 <p id="EN-US_TOPIC_0000001180320147__p43722611103715">The ODBC driver is applicable to the following operating systems only:</p>
 <ul id="EN-US_TOPIC_0000001180320147__ul65060019103719"><li id="EN-US_TOPIC_0000001180320147__li4609095515468">Windows Server 2008 or Windows 7 or later</li><li id="EN-US_TOPIC_0000001180320147__li4305789194032">x86 servers: RHEL 6.4 to RHEL 7.6</li><li id="EN-US_TOPIC_0000001180320147__li26852918103722">x86 servers: CentOS 6.4 to CentOS 7.4</li><li id="EN-US_TOPIC_0000001180320147__li52896563103746">x86 servers: SUSE 11.1 to SUSE 11.4; SUSE 12.0 to SUSE 12.3</li></ul>
 <div class="note" id="EN-US_TOPIC_0000001180320147__note62479713194112"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001180320147__p25446510194112">Windows drivers can only be 32-bit and can be used in 32-bit or 64-bit operating systems. However, the applications must be 32-bit.</p>
 </div></div>
 </li></ul>
 </p></li></ol>
 </div>
 </div>
 <div>
 <div class="familylinks">
 <div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0081.html">Using the JDBC and ODBC Drivers to Connect to a Cluster</a></div>
 </div>
 </div>
--- a/docs/dws/umn/dws_01_0033.html
+++ b/docs/dws/umn/dws_01_0033.html
@ -0,0 +1,97 @@
 <a name="EN-US_TOPIC_0000001180320209"></a><a name="EN-US_TOPIC_0000001180320209"></a>
 <h1 class="topictitle1">Obtaining the Cluster Connection Address</h1>
 <div id="body1492586202773"><div class="section" id="EN-US_TOPIC_0000001180320209__section26616723151647"><h4 class="sectiontitle">Scenario</h4><p id="EN-US_TOPIC_0000001180320209__p04121558928">You can access GaussDB(DWS) clusters by different methods and the connection address of each connection method varies. This section describes how to view and obtain the private network address on the <span id="EN-US_TOPIC_0000001180320209__text1541015910162">cloud</span> platform, public network address on the Internet, and JDBC connection strings.</p>
 <p id="EN-US_TOPIC_0000001180320209__p19197496151650">To obtain the cluster connection address, use either of the following methods:</p>
 <ul id="EN-US_TOPIC_0000001180320209__ul175171650155913"><li id="EN-US_TOPIC_0000001180320209__li45175505598"><a href="#EN-US_TOPIC_0000001180320209__section5539467151713">Obtaining the Cluster Connection Address on the Connections Page</a></li><li id="EN-US_TOPIC_0000001180320209__li10517175085915"><a href="#EN-US_TOPIC_0000001180320209__section149501253104810">Obtaining the Cluster Access Addresses on the Basic Information Page</a></li></ul>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001180320209__section5539467151713"><a name="EN-US_TOPIC_0000001180320209__section5539467151713"></a><a name="section5539467151713"></a><h4 class="sectiontitle">Obtaining the Cluster Connection Address on the Connections Page</h4><ol id="EN-US_TOPIC_0000001180320209__ol26716197151740"><li id="EN-US_TOPIC_0000001180320209__li6029015714233"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001180320209__li25411875155123"><span>In the navigation pane on the left, click <span class="uicontrol" id="EN-US_TOPIC_0000001180320209__uicontrol1284600310103522"><b>Connections</b></span>.</span></li><li id="EN-US_TOPIC_0000001180320209__li40219600152241"><span>In the <span class="parmname" id="EN-US_TOPIC_0000001180320209__parmname55222884142917"><b>Data Warehouse Connection Information</b></span> area, select an available cluster.</span><p><p id="EN-US_TOPIC_0000001180320209__p1627472815235">You can only select clusters in the <span class="parmvalue" id="EN-US_TOPIC_0000001180320209__parmvalue1158130015145817"><b>Available</b></span> state.</p>
 <p id="EN-US_TOPIC_0000001180320209__p85019188544"></p>
 <div class="fignone" id="EN-US_TOPIC_0000001180320209__fig14123111115591"><span class="figcap"><b>Figure 1 </b>Connection information</span><br><span><img id="EN-US_TOPIC_0000001180320209__image7247154124818" src="figure/en-us_image_0000001134560772.png" width="465.5" height="255.14853000000002" title="Click to enlarge" class="imgResize"></span></div>
 </p></li><li id="EN-US_TOPIC_0000001180320209__li44185516152326"><span>View and obtain the cluster connection information.</span><p><ul id="EN-US_TOPIC_0000001180320209__ul15059897152410"><li id="EN-US_TOPIC_0000001180320209__li63718748152412"><span class="parmname" id="EN-US_TOPIC_0000001180320209__parmname45067886142937"><b>Private Network Address</b></span></li><li id="EN-US_TOPIC_0000001180320209__li39294468152414"><span class="parmname" id="EN-US_TOPIC_0000001180320209__parmname6037662142946"><b>Public Network Address</b></span></li><li id="EN-US_TOPIC_0000001180320209__li41645464152410"><span class="parmname" id="EN-US_TOPIC_0000001180320209__parmname989588142954"><b>JDBC URL (Private Network)</b></span></li><li id="EN-US_TOPIC_0000001180320209__li135445781423"><span class="parmname" id="EN-US_TOPIC_0000001180320209__parmname816064060144917"><b>JDBC URL (Public Network)</b></span></li><li id="EN-US_TOPIC_0000001180320209__li3503184262914"><span class="parmname" id="EN-US_TOPIC_0000001180320209__parmname056896124915"><b>ODBC URL</b></span></li></ul>
 <div class="note" id="EN-US_TOPIC_0000001180320209__note14551036152422"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001180320209__ul16258155912525"><li id="EN-US_TOPIC_0000001180320209__li651204125311">If no EIP is automatically assigned during cluster creation, <span class="parmname" id="EN-US_TOPIC_0000001180320209__parmname1997655969756_1"><b>Public Network Address</b></span> is empty. If you want to use a public network address (consisting of an EIP and the database port) to access the cluster from the Internet, click <span class="parmname" id="EN-US_TOPIC_0000001180320209__parmname10541646538"><b>Bind EIP</b></span> to bind one.</li><li id="EN-US_TOPIC_0000001180320209__li17258105916525">If an EIP is bound during cluster creation but you do not want to use the public network address to access the cluster, click <span class="parmname" id="EN-US_TOPIC_0000001180320209__parmname14257195915520"><b>Unbind EIP</b></span> to unbind the EIP. After the EIP is unbound, <span class="parmname" id="EN-US_TOPIC_0000001180320209__parmname24481718115414"><b>Public Network Address</b></span> is empty.</li></ul>
 </div></div>
 </p></li></ol>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001180320209__section149501253104810"><a name="EN-US_TOPIC_0000001180320209__section149501253104810"></a><a name="section149501253104810"></a><h4 class="sectiontitle">Obtaining the Cluster Access Addresses on the Basic Information Page</h4><ol id="EN-US_TOPIC_0000001180320209__ol15285145694916"><li id="EN-US_TOPIC_0000001180320209__li972954712269"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001180320209__li33798861115225"><span>In the navigation tree on the left, click <span class="uicontrol" id="EN-US_TOPIC_0000001180320209__uicontrol942773654912"><b>Clusters</b></span>.</span></li><li id="EN-US_TOPIC_0000001180320209__li53353217115225"><span>In the cluster list, click the name of the target cluster. The <span class="parmname" id="EN-US_TOPIC_0000001180320209__parmname10416912115225"><b>Basic Information</b></span> page is displayed.</span></li><li id="EN-US_TOPIC_0000001180320209__li1270911918357"><span>In the <strong id="EN-US_TOPIC_0000001180320209__b975316447410">Database Attribute</strong> area, view and obtain the cluster's access address information, including the private network address and public network address.</span><p><div class="p" id="EN-US_TOPIC_0000001180320209__p15509956195319"><span><img id="EN-US_TOPIC_0000001180320209__image1463881091813" src="figure/en-us_image_0000001432175545.png" width="479.7975" height="218.034481" title="Click to enlarge" class="imgResize"></span>
 <div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="EN-US_TOPIC_0000001180320209__table878289143910" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Database attribute parameters</caption><thead align="left"><tr id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_r2b6913f2352a423d92e248eee4ed7ccf"><th align="left" class="cellrowborder" valign="top" width="19%" id="mcps1.3.3.2.4.2.1.2.2.3.1.1"><p id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_en-us_topic_0106894684_p77831797399">Parameter</p>
 </th>
 <th align="left" class="cellrowborder" valign="top" width="81%" id="mcps1.3.3.2.4.2.1.2.2.3.1.2"><p id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_en-us_topic_0106894684_p137830993917">Description</p>
 </th>
 </tr>
 </thead>
 <tbody><tr id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_r882d4694703946ed8c700bf93ff625cf"><td class="cellrowborder" valign="top" width="19%" headers="mcps1.3.3.2.4.2.1.2.2.3.1.1 "><p id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_en-us_topic_0106894684_p830515405276">Default Database</p>
 </td>
 <td class="cellrowborder" valign="top" width="81%" headers="mcps1.3.3.2.4.2.1.2.2.3.1.2 "><p id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_ae9a46454aab74e27ba94bcd2c2ea9484">Database name specified when the cluster is created. When you connect to the cluster for the first time, connect to the default database.</p>
 </td>
 </tr>
 <tr id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_r4ff9b08ec9b64c62bd6bf3272c6eac82"><td class="cellrowborder" valign="top" width="19%" headers="mcps1.3.3.2.4.2.1.2.2.3.1.1 "><p id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_a2be5aa42a2be4708a4c93d9017cf7705">Initial Administrator</p>
 </td>
 <td class="cellrowborder" valign="top" width="81%" headers="mcps1.3.3.2.4.2.1.2.2.3.1.2 "><p id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_a92f034cc83264dceaf7957ee023e4fbe">Database administrator specified during cluster creation. When you connect to the cluster for the first time, you need to use the initial database administrator and password to connect to the default database.</p>
 </td>
 </tr>
 <tr id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_r758c339bb9794651bc85a7d94aea003a"><td class="cellrowborder" valign="top" width="19%" headers="mcps1.3.3.2.4.2.1.2.2.3.1.1 "><p id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_en-us_topic_0106894684_p193208401279">Port</p>
 </td>
 <td class="cellrowborder" valign="top" width="81%" headers="mcps1.3.3.2.4.2.1.2.2.3.1.2 "><p id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_en-us_topic_0106894684_p203223409278">Port for accessing the cluster database over the public network or private network. The host port is specified when a cluster is created and used to listen to client connections.</p>
 </td>
 </tr>
 <tr id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_row139072101512"><td class="cellrowborder" valign="top" width="19%" headers="mcps1.3.3.2.4.2.1.2.2.3.1.1 "><p id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_p1318152024618">Connection String</p>
 </td>
 <td class="cellrowborder" valign="top" width="81%" headers="mcps1.3.3.2.4.2.1.2.2.3.1.2 "><p id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_p21832094618">Connection string. You can click <strong id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_b566575017544">View Details</strong> to check the data warehouse connection information. Its value can be:</p>
 <ul id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_ul71814054911"><li id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_li818174017493"><strong id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_b1751560145610">JDBC URL (Private Network)</strong>. In the private network environment, you can use the JDBC URL (private network) to connect to the cluster when developing applications.</li><li id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_li1018144054918"><strong id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_b141541413575">JDBC URL (Public Network)</strong>. In the public network environment, you can use the JDBC URL (public network) to connect to the cluster when developing applications.</li><li id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_li81914044912"><strong id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_b645841015813">ODBC URL</strong>. In GaussDB(DWS), you can use an ODBC driver to connect to the database. The driver can connect to the database on an ECS or over the Internet.</li></ul>
 </td>
 </tr>
 <tr id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_row133115918620"><td class="cellrowborder" valign="top" width="19%" headers="mcps1.3.3.2.4.2.1.2.2.3.1.1 "><p id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_p0333592612">ELB Address</p>
 </td>
 <td class="cellrowborder" valign="top" width="81%" headers="mcps1.3.3.2.4.2.1.2.2.3.1.2 "><p id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_p193316596610">To achieve high availability and avoid single-CN failures, a new cluster needs to be bound to ELB. You are advised to use the ELB address to connect to the cluster.</p>
 </td>
 </tr>
 <tr id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_re2ccebbab5814999b351e44f82925c80"><td class="cellrowborder" valign="top" width="19%" headers="mcps1.3.3.2.4.2.1.2.2.3.1.1 "><p id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_en-us_topic_0106894684_p17422209466">Private Network Domain Name</p>
 </td>
 <td class="cellrowborder" valign="top" width="81%" headers="mcps1.3.3.2.4.2.1.2.2.3.1.2 "><p id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_en-us_topic_0106894684_p124255014619">Name of the domain for accessing the database in the cluster over the private network. The private network domain address is automatically generated when a cluster is created. The default name format is <em id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_a5ae815650c064d8a8dae03738456943b">ClusterName.</em><strong id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_b21975644819"></strong><strong id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_b919156154817">dws.otc-tsi.de</strong>. When you access a data warehouse cluster using a domain name, the domain name resolver provides the load balancing function.</p>
 <div class="note" id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_nd02d0d2abfe340abb06b2280c3c63ee3"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_en-us_topic_0106894684_p244575418567">If the cluster name does not comply with the domain name standards, the prefix of the default access domain name will be adjusted accordingly.</p>
 </div></div>
 <p id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_en-us_topic_0106894684_p342513044618">You can click <strong id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_b120093217113036">Modify </strong>to change the private network domain name. The access domain name contains 4 to 63 characters, which consists of letters, digits, and hyphens (-), and must start with a letter.</p>
 <p id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_abc230c5c3da74f8dbf403914262594ee">For details, see <a href="dws_01_0140.html">Managing Access Domain Names</a>.</p>
 </td>
 </tr>
 <tr id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_r1b0f000178004534b5997cb450b6f31e"><td class="cellrowborder" valign="top" width="19%" headers="mcps1.3.3.2.4.2.1.2.2.3.1.1 "><p id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_en-us_topic_0106894684_p177837983914">Private Network IP Address</p>
 </td>
 <td class="cellrowborder" valign="top" width="81%" headers="mcps1.3.3.2.4.2.1.2.2.3.1.2 "><p id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_en-us_topic_0106894684_p137832943917">IP address for accessing the database in the cluster over the private network.</p>
 <div class="note" id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_note780356123115"><span class="notetitle"> NOTE: </span><div class="notebody"><ul id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_ul173316457329"><li id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_li1634114510323">A private IP address is automatically generated when you create a cluster. The IP address is fixed.</li><li id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_li1150131812345">The number of private IP addresses equals the number of CNs. You can log in to any node to connect to the cluster.</li><li id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_li146871531113714">If you access a fixed IP address over the internal network, all the workloads will be processed on a single CN.</li></ul>
 </div></div>
 </td>
 </tr>
 <tr id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_rcc1fdae89a1a49b9948cefc71bdf0842"><td class="cellrowborder" valign="top" width="19%" headers="mcps1.3.3.2.4.2.1.2.2.3.1.1 "><p id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_en-us_topic_0106894684_p677962610462">Public Network Domain Name</p>
 </td>
 <td class="cellrowborder" valign="top" width="81%" headers="mcps1.3.3.2.4.2.1.2.2.3.1.2 "><p id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_a56628f8431734c0b985896cc5d37f780">Name of the domain for accessing the database in the cluster over the public network.</p>
 <p id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_a18532f4eec4147bfa5192dc05897f6f1">For details, see <a href="dws_01_0140.html">Managing Access Domain Names</a>.</p>
 </td>
 </tr>
 <tr id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_r8e260b607d194a63b9ac8e44f62bcfc6"><td class="cellrowborder" valign="top" width="19%" headers="mcps1.3.3.2.4.2.1.2.2.3.1.1 "><p id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_a7bd36fd74d10480eb32659d97f72c3d7">Public Network IP Address</p>
 </td>
 <td class="cellrowborder" valign="top" width="81%" headers="mcps1.3.3.2.4.2.1.2.2.3.1.2 "><p id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_a07d4d14f1c094c7db17a95b5a0498bcd">IP address for accessing the database in the cluster over the public network.</p>
 <div class="note" id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_ne289450a5d9a4b95847e71440dcb30ea"><span class="notetitle"> NOTE: </span><div class="notebody"><ul id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_u45bbabcd797b4cfebd9a6e646ae01dd6"><li id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_lcb4fe5f0cdc84469b22c4e444f79322a">If no EIP is assigned during cluster creation and <span class="parmname" id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_parmname941317568113036"><b>Public Network IP Address</b></span> is empty, click <span class="parmname" id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_parmname912963336113036"><b>Bind EIP</b></span> to bind an EIP to the cluster.</li><li id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_le3b1833cf35d4ef1b00417f5adb05021">If an EIP is bound during cluster creation, click <span class="parmname" id="EN-US_TOPIC_0000001180320209__en-us_topic_0000001180440131_p2838a47c4a194c119dec0b81e4a24ceb"><b>Unbind EIP</b></span> to unbind the EIP.</li></ul>
 </div></div>
 </td>
 </tr>
 </tbody>
 </table>
 </div>
 </div>
 </p></li></ol>
 </div>
 </div>
 <div>
 <div class="familylinks">
 <div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0131.html">Cluster Connection</a></div>
 </div>
 </div>
 <script language="JavaScript">
 <!--
 image_size('.imgResize');
 var msg_imageMax = "view original image";
 var msg_imageClose = "close";
 //--></script>
--- a/docs/dws/umn/dws_01_0035.html
+++ b/docs/dws/umn/dws_01_0035.html
@ -0,0 +1,16 @@
 <a name="EN-US_TOPIC_0000001180320251"></a><a name="EN-US_TOPIC_0000001180320251"></a>
 <h1 class="topictitle1">Read-only Status</h1>
 <div id="body1588041015666"><p id="EN-US_TOPIC_0000001180320251__p8060118">No database operation is allowed on a read-only cluster. Cancel the read-only status on the management console.</p>
 <div class="section" id="EN-US_TOPIC_0000001180320251__section1614565113217"><h4 class="sectiontitle">Impact on the System</h4><ul id="EN-US_TOPIC_0000001180320251__ul10651610174112"><li id="EN-US_TOPIC_0000001180320251__li1865141074118">You can cancel the read-only status only when a cluster is read-only.</li><li id="EN-US_TOPIC_0000001180320251__li1690111409429">When a cluster is in read-only status, stop the write tasks to prevent data loss caused by used up disk space.</li><li id="EN-US_TOPIC_0000001180320251__li126438362447">After the read-only status is canceled, clear the data as soon as possible to prevent the cluster from entering the read-only status again after a period of time.</li></ul>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001180320251__section9511922183219"><h4 class="sectiontitle">Canceling Read-only Status</h4><ol id="EN-US_TOPIC_0000001180320251__ol8312165133319"><li id="EN-US_TOPIC_0000001180320251__li931225183319"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001180320251__li11952509114244"><span>Click <span class="uicontrol" id="EN-US_TOPIC_0000001180320251__uicontrol0580122119"><b>Clusters</b></span>.</span><p><p id="EN-US_TOPIC_0000001180320251__p2374663163311">All clusters are displayed by default.</p>
 </p></li><li id="EN-US_TOPIC_0000001180320251__li25916796163327"><span>In the <span class="parmname" id="EN-US_TOPIC_0000001180320251__parmname6666226615"><b>Operation</b></span> column of the target cluster, choose <span class="menucascade" id="EN-US_TOPIC_0000001180320251__menucascade7667326915"><b><span class="uicontrol" id="EN-US_TOPIC_0000001180320251__uicontrol20667162617117">More</span></b> &gt; <b><span class="uicontrol" id="EN-US_TOPIC_0000001180320251__uicontrol566712269110">Cancel Readonly</span></b></span>.</span></li><li id="EN-US_TOPIC_0000001180320251__li02759308915"><span>In the dialog box that is displayed, click <strong id="EN-US_TOPIC_0000001180320251__b0363812171316">OK</strong> to confirm and cancel the read-only status for the cluster.</span></li></ol>
 </div>
 </div>
 <div>
 <div class="familylinks">
 <div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0600.html">Clusters</a></div>
 </div>
 </div>
--- a/docs/dws/umn/dws_01_0037.html
+++ b/docs/dws/umn/dws_01_0037.html
@ -0,0 +1,66 @@
 <a name="EN-US_TOPIC_0000001180320141"></a><a name="EN-US_TOPIC_0000001180320141"></a>
 <h1 class="topictitle1">Using the gsql Client to Connect to a Cluster</h1>
 <div id="body1491553271744"><p id="EN-US_TOPIC_0000001180320141__p1699416016201">This section describes how to connect to a database through an SQL client after you create a data warehouse cluster and before you use the cluster's database. GaussDB(DWS) provides the gsql client that matches the cluster version for you to access the cluster using the cluster's public or private network address.</p>
 <div class="section" id="EN-US_TOPIC_0000001180320141__section2664278815443"><h4 class="sectiontitle">Using the gsql CLI Client to Connect to a Cluster</h4><ol id="EN-US_TOPIC_0000001180320141__ol3845850015443"><li id="EN-US_TOPIC_0000001180320141__li147272252437"><span>Prepare a Linux ECS to install and run the gsql client.</span><p><p id="EN-US_TOPIC_0000001180320141__p103589108451">For details, see <a href="dws_01_0128.html">Preparing an ECS as the gsql Client Host</a>.</p>
 </p></li><li id="EN-US_TOPIC_0000001180320141__li57820116171210"><span>Download the gsql client by referring to <a href="dws_01_0031.html">Downloading the Client</a>, and use an SSH file transfer tool (such as WinSCP) to upload the client to a target Linux host.</span><p><p id="EN-US_TOPIC_0000001180320141__adf760149a35140c48cf09071207cd279">The user who uploads the client must have the full control permission on the target directory on the host to which the client is uploaded.</p>
 <p id="EN-US_TOPIC_0000001180320141__p2754133018133">Alternatively, you can remotely log in to the Linux host where the gsql is to be installed in SSH mode and run the following command in the Linux command window to download the gsql client:</p>
 <pre class="screen" id="EN-US_TOPIC_0000001180320141__screen0169162716481">wget https://obs.otc.t-systems.com/dws/download/dws_client_redhat_x64.zip --no-check-certificate</pre>
 </p></li><li id="EN-US_TOPIC_0000001180320141__li14921556171524"><span>Use the SSH tool to remotely log in to the host where the client is installed.</span><p><p id="EN-US_TOPIC_0000001180320141__en-us_topic_0106888034_p141041143523">For details about how to log in to an ECS, see "ECSs&gt; Logging In to a Linux ECS &gt; Login Using an SSH Password" in the <i><cite id="EN-US_TOPIC_0000001180320141__cd7370d9c4ec64f37aeceb04df55fd347">Elastic Cloud Server User Guide</cite></i>.</p>
 </p></li><li id="EN-US_TOPIC_0000001180320141__li143598191920"><span>(Optional) <span id="EN-US_TOPIC_0000001180320141__text443615881913">To connect to the cluster in SSL mode</span>, configure SSL authentication parameters on the host where the client is installed. For details, see <a href="dws_01_0038.html">Establishing Secure TCP/IP Connections in SSL Mode</a>.</span><p><div class="note" id="EN-US_TOPIC_0000001180320141__note04362085193"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001180320141__p943638171915">The SSL connection mode is more secure than the non-SSL mode. You are advised to connect the client to the cluster in SSL mode.</p>
 </div></div>
 </p></li><li id="EN-US_TOPIC_0000001180320141__li28159407171547"><span>Run the following commands to decompress the client:</span><p><pre class="screen" id="EN-US_TOPIC_0000001180320141__screen173918175523">cd &lt;<em id="EN-US_TOPIC_0000001180320141__i3290164118364">Path for saving the client</em>&gt;
 unzip <em id="EN-US_TOPIC_0000001180320141__i10517201512535">dws_client_8.1.x_redhat_x64.zip</em></pre>
 <p id="EN-US_TOPIC_0000001180320141__p14308192714355">In the preceding commands:</p>
 <ul id="EN-US_TOPIC_0000001180320141__ul18555114323517"><li id="EN-US_TOPIC_0000001180320141__li155410439357">&lt;<em id="EN-US_TOPIC_0000001180320141__i953114942312">Path_for_storing_the_client</em>&gt;: Replace it with the actual path.</li><li id="EN-US_TOPIC_0000001180320141__li9555114313356"><em id="EN-US_TOPIC_0000001180320141__i123762054104815">dws_client_8.1.x_redhat_x64.zip</em>: This is the client tool package name of <span class="parmvalue" id="EN-US_TOPIC_0000001180320141__parmvalue185611912154213"><b>RedHat x86</b></span>. Replace it with the actual name.</li></ul>
 </p></li><li id="EN-US_TOPIC_0000001180320141__li15256751171613"><span>Run the following command to configure the GaussDB(DWS) client:</span><p><pre class="screen" id="EN-US_TOPIC_0000001180320141__screen39549318531">source gsql_env.sh</pre>
 <p id="EN-US_TOPIC_0000001180320141__acba60d877148432faf5ecdf94dd7b73e">If the following information is displayed, the GaussDB(DWS) client is successfully configured:</p>
 <pre class="screen" id="EN-US_TOPIC_0000001180320141__s8fd77cb5c040479baaab9ae3f2ea8fa5">All things done.</pre>
 </p></li><li id="EN-US_TOPIC_0000001180320141__li41463031113158"><span>Connect to the database in the GaussDB(DWS) cluster using the gsql client. Replace the values of each parameter with actual values.</span><p><pre class="screen" id="EN-US_TOPIC_0000001180320141__screen14165156155416"><strong id="EN-US_TOPIC_0000001180320141__b1429125514332">gsql -d &lt;</strong><em id="EN-US_TOPIC_0000001180320141__i1643665510335">Database_name</em><strong id="EN-US_TOPIC_0000001180320141__b12436185533316">&gt; -h &lt;</strong><em id="EN-US_TOPIC_0000001180320141__i5437255163316">Cluster_address</em><strong id="EN-US_TOPIC_0000001180320141__b184371355133320">&gt; -U &lt;</strong><em id="EN-US_TOPIC_0000001180320141__i18438205533314">Database_user</em><strong id="EN-US_TOPIC_0000001180320141__b943825513311">&gt; -p &lt;</strong><em id="EN-US_TOPIC_0000001180320141__i243915503318">Database_port</em>&gt; <strong id="EN-US_TOPIC_0000001180320141__b1844112558334">-r</strong></pre>
 <p id="EN-US_TOPIC_0000001180320141__p6670175610390">The parameters are described as follows:</p>
 <ul id="EN-US_TOPIC_0000001180320141__ul6532192614405"><li id="EN-US_TOPIC_0000001180320141__li135361926194014"><em id="EN-US_TOPIC_0000001180320141__i43181148132517">Database_name</em>: Enter the name of the database to be connected. If you use the client to connect to the cluster for the first time, enter the default database <strong id="EN-US_TOPIC_0000001180320141__b13322154812111"><span id="EN-US_TOPIC_0000001180320141__text6850145215424">gaussdb</span></strong>.</li><li id="EN-US_TOPIC_0000001180320141__li112312661818"><em id="EN-US_TOPIC_0000001180320141__i094617612267">Cluster_address</em>: For details about how to obtain this address, see <a href="dws_01_0033.html">Obtaining the Cluster Connection Address</a>. If a public network address is used for connection, set this parameter to <span class="parmname" id="EN-US_TOPIC_0000001180320141__parmname21231326121819"><b>Public Network Address</b></span> or <span class="parmname" id="EN-US_TOPIC_0000001180320141__parmname587154113195"><b>Public Network Domain Name</b></span>. If a private network address is used for connection, set this parameter to <span class="parmname" id="EN-US_TOPIC_0000001180320141__parmname12124132611189"><b>Private Network Address</b></span> or <span class="parmname" id="EN-US_TOPIC_0000001180320141__parmname89791149141913"><b>Private Network Domain Name</b></span>. </li><li id="EN-US_TOPIC_0000001180320141__li16543122664016"><em id="EN-US_TOPIC_0000001180320141__i87951622192618">Database_user</em>: Enter the username of the cluster's database. If you use the client to connect to the cluster for the first time, set this parameter to the default database administrator configured during cluster creation, for example, <span class="parmvalue" id="EN-US_TOPIC_0000001180320141__parmvalue901316906152829"><b>dbadmin</b></span>.</li><li id="EN-US_TOPIC_0000001180320141__li10550102618400"><em id="EN-US_TOPIC_0000001180320141__i1975219309261">Database_port</em>: Enter the database port set during cluster creation.</li></ul>
 <p id="EN-US_TOPIC_0000001180320141__p4649355413199">For example, run the following command to connect to the default database <strong id="EN-US_TOPIC_0000001180320141__b4518103716511"><span id="EN-US_TOPIC_0000001180320141__text16675135114313">gaussdb</span></strong> in the GaussDB(DWS) cluster:</p>
 <pre class="screen" id="EN-US_TOPIC_0000001180320141__screen157451922201313">gsql -d <span id="EN-US_TOPIC_0000001180320141__text8980103144418">gaussdb</span> -h 10.168.0.74 -U dbadmin -p 8000 -W <em id="EN-US_TOPIC_0000001180320141__i1655214575539">password</em> -r</pre>
 <p id="EN-US_TOPIC_0000001180320141__p14596465113158">If the following information is displayed, the connection succeeded:</p>
 <div class="codecoloring" codetype="Sql" id="EN-US_TOPIC_0000001180320141__screen64259327113158"><div class="highlight"><table class="highlighttable"><tr><td class="linenos"><div class="linenodiv"><pre><span class="normal">1</span></pre></div></td><td class="code"><div><pre><span></span><span class="n">gaussdb</span><span class="o">=&gt;</span><span class="w"></span>
 </pre></div></td></tr></table></div>
 </div>
 </p></li></ol>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001180320141__section41003216539"><h4 class="sectiontitle">gsql Command Reference</h4><p id="EN-US_TOPIC_0000001180320141__p94866279131">For more information about the gsql commands, see the <em id="EN-US_TOPIC_0000001180320141__i1539711813349">Data Warehouse Service (DWS) Tool Guide</em>.</p>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001180320141__section16360114045919"><h4 class="sectiontitle">(Optional) Importing TPC-DS Sample Data Using gsql</h4><p id="EN-US_TOPIC_0000001180320141__p19752111617011">GaussDB(DWS) users can import data from external sources to data warehouse clusters. This section describes how to import sample data from OBS to a data warehouse cluster and perform querying and analysis operations on the sample data. The sample data is generated based on the standard TPC-DS benchmark test.</p>
 <p id="EN-US_TOPIC_0000001180320141__p7938170102720">TPC-DS is the benchmark for testing the performance of decision support. With TPC-DS test data and cases, you can simulate complex scenarios, such as big data set statistics, report generation, online query, and data mining, to better understand functions and performance of database applications.</p>
 <ol id="EN-US_TOPIC_0000001180320141__ol157036501972"><li id="EN-US_TOPIC_0000001180320141__li6937618813"><span>Use the SSH remote connection tool to log in to the host where the gsql client is installed and go to the gsql directory. The <strong id="EN-US_TOPIC_0000001180320141__b137521936738">/opt</strong> directory is used as an example for storing the gsql client.</span><p><pre class="screen" id="EN-US_TOPIC_0000001180320141__screen12234194145713"><strong id="EN-US_TOPIC_0000001180320141__b82451541105710">cd /opt</strong></pre>
 </p></li><li id="EN-US_TOPIC_0000001180320141__li2697125017711"><span>Switch to the specified directory and set the AK and SK for importing sample data and the OBS access address.</span><p><pre class="screen" id="EN-US_TOPIC_0000001180320141__screen9534125810547">cd sample
 /bin/bash setup.sh -ak &lt;<em id="EN-US_TOPIC_0000001180320141__i2311247155617">Access_Key_Id&gt;</em> -sk &lt;<em id="EN-US_TOPIC_0000001180320141__i10311247135620">Secret_Access_Key&gt;</em> -obs_location obs.otc.t-systems.com</pre>
 <p id="EN-US_TOPIC_0000001180320141__p66971501171">If the following information is displayed, the settings are successful:</p>
 <pre class="screen" id="EN-US_TOPIC_0000001180320141__screen569735012718">setup successfully!</pre>
 <div class="note" id="EN-US_TOPIC_0000001180320141__note1369735019715"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001180320141__p204716185300"><em id="EN-US_TOPIC_0000001180320141__i174184215373">&lt;Access_Key_Id&gt;</em> and <em id="EN-US_TOPIC_0000001180320141__i20802426373">&lt;Secret_Access_Key&gt;</em>: indicate the AK and SK, respectively. For details about how to obtain the AK and SK, see "Data Import &gt; Concurrently Importing Data from OBS &gt; Creating Access Keys (AK and SK)" in the <em id="EN-US_TOPIC_0000001180320141__i9466108124912">Data Warehouse Service (DWS) Developer Guide</em>. Then, replace the parameters in the statements with the obtained values.</p>
 </div></div>
 </p></li><li id="EN-US_TOPIC_0000001180320141__li144036111801"><span>Go back to previous directory and run the gsql environment variables.</span><p><pre class="screen" id="EN-US_TOPIC_0000001180320141__screen18599162743510">cd ..
 source gsql_env.sh
 cd bin</pre>
 </p></li><li id="EN-US_TOPIC_0000001180320141__li07034507712"><span>Import the sample data to the data warehouse.</span><p><p id="EN-US_TOPIC_0000001180320141__p14375203571114">Command format:</p>
 <pre class="screen" id="EN-US_TOPIC_0000001180320141__screen1354517342593">gsql -d &lt;<em id="EN-US_TOPIC_0000001180320141__i20811148143716">Database name</em>&gt; -h &lt;<em id="EN-US_TOPIC_0000001180320141__i1581694883714">Public network address of the cluster&gt;</em> -U &lt;<em id="EN-US_TOPIC_0000001180320141__i16817184812371">Administrator&gt;</em> -p &lt;<em id="EN-US_TOPIC_0000001180320141__i19817104843711">Data warehouse port number&gt;</em> -f &lt;<em id="EN-US_TOPIC_0000001180320141__i1781704811379">Path for storing the sample data script&gt; -r</em></pre>
 <p id="EN-US_TOPIC_0000001180320141__p549564951117">Sample command:</p>
 <pre class="screen" id="EN-US_TOPIC_0000001180320141__screen398214551593">gsql -d <span id="EN-US_TOPIC_0000001180320141__text254144216457">gaussdb</span> -h 10.168.0.74 -U dbadmin -p 8000 -f /opt/sample/tpcds_load_data_from_obs.sql -r</pre>
 <div class="note" id="EN-US_TOPIC_0000001180320141__note1870365011711"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001180320141__p117032502710">In the preceding command, sample data script <span class="filepath" id="EN-US_TOPIC_0000001180320141__filepath17375399518"><b>tpcds_load_data_from_obs.sql</b></span> is stored in the sample directory (for example, <strong id="EN-US_TOPIC_0000001180320141__b3388191157">/opt/sample/</strong>) of the GaussDB(DWS) client.</p>
 </div></div>
 <p id="EN-US_TOPIC_0000001180320141__p207031150572">After you enter the database administrator password and successfully connect to the database in the cluster, the system will automatically create a foreign table to associate the sample data outside the cluster. Then, the system creates a target table for saving the sample data and imports the data to the target table using the foreign table.</p>
 <p id="EN-US_TOPIC_0000001180320141__p1270312509710">The time required for importing a large dataset depends on the current GaussDB(DWS) cluster specifications. Generally, the import takes about 10 to 20 minutes. If information similar to the following is displayed, the import is successful.</p>
 <pre class="screen" id="EN-US_TOPIC_0000001180320141__screen15703115012718">Time:1845600.524 ms</pre>
 </p></li></ol><ol start="5" id="EN-US_TOPIC_0000001180320141__ol146958501712"><li id="EN-US_TOPIC_0000001180320141__li969412502719"><span>In the Linux command window, run the following commands to switch to a specific directory and query the sample data:</span><p><pre class="screen" id="EN-US_TOPIC_0000001180320141__screen7422039141412">cd /opt/sample/query_sql/
 /bin/bash tpcds100x.sh</pre>
 </p></li><li id="EN-US_TOPIC_0000001180320141__li116951502710"><span>Enter the cluster's public network IP address, access port, database name, user who accesses the database, and password of the user as prompted.</span><p><ul id="EN-US_TOPIC_0000001180320141__ul11694115016711"><li id="EN-US_TOPIC_0000001180320141__li269445010716">The default database name is <strong id="EN-US_TOPIC_0000001180320141__b378716551568"><span id="EN-US_TOPIC_0000001180320141__text149310555455">gaussdb</span></strong>.</li><li id="EN-US_TOPIC_0000001180320141__li26941502712">Use the database administrator username and password configured during cluster creation as the username and password for accessing the database.</li></ul>
 <p id="EN-US_TOPIC_0000001180320141__p46944501878">After the query is complete, a directory for storing the query result, such as <strong id="EN-US_TOPIC_0000001180320141__b842352706184710">query_output_20170914_072341</strong>, will be generated in the current query directory, for example, <span class="filepath" id="EN-US_TOPIC_0000001180320141__filepath494650861184645"><b>sample/query_sql/</b></span>.</p>
 </p></li></ol>
 </div>
 </div>
 <div>
 <div class="familylinks">
 <div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0093.html">Using the gsql CLI Client to Connect to a Cluster</a></div>
 </div>
 </div>
--- a/docs/dws/umn/dws_01_0038.html
+++ b/docs/dws/umn/dws_01_0038.html
--- a/docs/dws/umn/dws_01_0039.html
+++ b/docs/dws/umn/dws_01_0039.html
--- a/docs/dws/umn/dws_01_0055.html
+++ b/docs/dws/umn/dws_01_0055.html
@ -0,0 +1,19 @@
 <a name="EN-US_TOPIC_0000001180440149"></a><a name="EN-US_TOPIC_0000001180440149"></a>
 <h1 class="topictitle1">Importing Data from MRS to GaussDB(DWS)</h1>
 <div id="body1499656133705"><div class="section" id="EN-US_TOPIC_0000001180440149__section34418118183527"><h4 class="sectiontitle">Importing Data from MRS to a Data Warehouse Cluster</h4><p id="EN-US_TOPIC_0000001180440149__p8060118">MRS is a big data cluster running based on the open-source Hadoop ecosystem. It provides the industry's latest cutting-edge storage and analysis capabilities of massive volumes of data, satisfying your data storage and processing requirements. For details about MRS services, see the <i><cite id="EN-US_TOPIC_0000001180440149__cite1716351711455">MapReduce Service User Guide</cite></i>.</p>
 <p id="EN-US_TOPIC_0000001180440149__p56178650111411">You can use Hive/Spark (analysis cluster of MRS) to store massive volumes of service data. Hive/Spark data files are stored in HDFS. On GaussDB(DWS), you can connect a data warehouse cluster to MRS clusters, read data from HDFS files, and write the data to GaussDB(DWS) when the clusters are on the same network.</p>
 </div>
 <div class="section" id="EN-US_TOPIC_0000001180440149__section4774472184623"><h4 class="sectiontitle">Import Process</h4><p id="EN-US_TOPIC_0000001180440149__p098116386811">Perform the following operations to import data from MRS to a data warehouse cluster:</p>
 <ol id="EN-US_TOPIC_0000001180440149__ol2946194915157"><li id="EN-US_TOPIC_0000001180440149__li139452049181517">In the data warehouse cluster, create an MRS data source connection according to <a href="dws_01_0059.html">Creating an MRS Data Source Connection</a>.<div class="note" id="EN-US_TOPIC_0000001180440149__note4268181341618"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001180440149__ul1618919385454"><li id="EN-US_TOPIC_0000001180440149__li20189203819458">Multiple MRS data sources can exist on the same network, but one GaussDB(DWS) cluster can connect to only one MRS cluster at a time.</li></ul>
 </div></div>
 </li><li id="EN-US_TOPIC_0000001180440149__li125762663515">Create an HDFS foreign table for querying data from the MRS cluster over APIs of a foreign server.<p id="EN-US_TOPIC_0000001180440149__p16734543193517"><a name="EN-US_TOPIC_0000001180440149__li125762663515"></a><a name="li125762663515"></a>For details, see "Data Import &gt; Importing Data from MRS to a Cluster" in the <i><cite id="EN-US_TOPIC_0000001180440149__cite3601147125410">Data Warehouse Service (DWS) Developer Guide</cite></i>.</p>
 </li><li id="EN-US_TOPIC_0000001180440149__li1665122602810">(Optional) When the HDFS configuration of the MRS cluster changes, update the MRS data source configuration on GaussDB(DWS). For details, see <a href="dws_01_0156.html">Updating the MRS Data Source Configuration</a>.</li></ol>
 </div>
 </div>
 <div>
 <div class="familylinks">
 <div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0057.html">MRS Data Sources</a></div>
 </div>
 </div>
--- a/Show More
+++ b/Show More