diff --git a/docs/dws/umn/.placeholder b/docs/dws/umn/.placeholder deleted file mode 100644 index e69de29b..00000000 diff --git a/docs/dws/umn/ALL_META.TXT.json b/docs/dws/umn/ALL_META.TXT.json new file mode 100644 index 00000000..543bf81d --- /dev/null +++ b/docs/dws/umn/ALL_META.TXT.json @@ -0,0 +1,2072 @@ +[ + { + "uri":"dws_01_index.html", + "product_code":"dws", + "code":"1", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Service Overview", + "title":"Service Overview", + "githuburl":"" + }, + { + "uri":"dws_01_0002.html", + "product_code":"dws", + "code":"2", + "des":"GaussDB(DWS) is an online data processing database that runs on the cloud infrastructure to provide scalable, fully-managed, and out-of-the-box analytic database service,", + "doc_type":"usermanual", + "kw":"What Is GaussDB(DWS)?,Service Overview,User Guide", + "title":"What Is GaussDB(DWS)?", + "githuburl":"" + }, + { + "uri":"dws_01_0007.html", + "product_code":"dws", + "code":"3", + "des":"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 d", + "doc_type":"usermanual", + "kw":"Advantages,Service Overview,User Guide", + "title":"Advantages", + "githuburl":"" + }, + { + "uri":"dws_01_00013.html", + "product_code":"dws", + "code":"4", + "des":"Enhanced ETL + Real-time BI analysisETL + BI analysisThe data warehouse is the pillar of the Business Intelligence (BI) system for collecting, storing, and analyzing mass", + "doc_type":"usermanual", + "kw":"Application Scenarios,Service Overview,User Guide", + "title":"Application Scenarios", + "githuburl":"" + }, + { + "uri":"dws_01_0091.html", + "product_code":"dws", + "code":"5", + "des":"GaussDB(DWS) enables you to use this service through various methods, such as the GaussDB(DWS) management console, GaussDB(DWS) client, and REST APIs. This section descri", + "doc_type":"usermanual", + "kw":"Functions,Service Overview,User Guide", + "title":"Functions", + "githuburl":"" + }, + { + "uri":"dws_01_0004.html", + "product_code":"dws", + "code":"6", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Concepts", + "title":"Concepts", + "githuburl":"" + }, + { + "uri":"dws_01_0005.html", + "product_code":"dws", + "code":"7", + "des":"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", + "doc_type":"usermanual", + "kw":"GaussDB(DWS) Management Concepts,Concepts,User Guide", + "title":"GaussDB(DWS) Management Concepts", + "githuburl":"" + }, + { + "uri":"dws_01_0006.html", + "product_code":"dws", + "code":"8", + "des":"A data warehouse cluster is an analysis-oriented relational database platform that supports online analysis.OLAP is a major function of data warehouse clusters. It suppor", + "doc_type":"usermanual", + "kw":"GaussDB(DWS) Database Concepts,Concepts,User Guide", + "title":"GaussDB(DWS) Database Concepts", + "githuburl":"" + }, + { + "uri":"dws_01_0003.html", + "product_code":"dws", + "code":"9", + "des":"GaussDB(DWS) uses Identity and Access Management (IAM) for authentication and authorization.Users who have the DWS Administrator permissions can fully utilize GaussDB(DWS", + "doc_type":"usermanual", + "kw":"Related Services,Service Overview,User Guide", + "title":"Related Services", + "githuburl":"" + }, + { + "uri":"dws_01_0144.html", + "product_code":"dws", + "code":"10", + "des":"If you need to assign different permissions to employees in your enterprise to access your cloud GaussDB(DWS) resources, IAM is a good choice for fine-grained permissions", + "doc_type":"usermanual", + "kw":"GaussDB(DWS) Permissions Management,Service Overview,User Guide", + "title":"GaussDB(DWS) Permissions Management", + "githuburl":"" + }, + { + "uri":"dws_01_0009.html", + "product_code":"dws", + "code":"11", + "des":"The following figure shows how to use GaussDB(DWS).GaussDB(DWS) provides a web-based management console and HTTPS-compliant APIs for you to manage data warehouse clusters", + "doc_type":"usermanual", + "kw":"GaussDB(DWS) Access,Service Overview,User Guide", + "title":"GaussDB(DWS) Access", + "githuburl":"" + }, + { + "uri":"dws_01_0010.html", + "product_code":"dws", + "code":"12", + "des":"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.You cannot c", + "doc_type":"usermanual", + "kw":"Restrictions,Service Overview,User Guide", + "title":"Restrictions", + "githuburl":"" + }, + { + "uri":"dws_01_00113.html", + "product_code":"dws", + "code":"13", + "des":"This section describes the technical specifications of GaussDB(DWS) in different versions.", + "doc_type":"usermanual", + "kw":"Technical Specifications,Service Overview,User Guide", + "title":"Technical Specifications", + "githuburl":"" + }, + { + "uri":"dws_01_0078.html", + "product_code":"dws", + "code":"14", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Getting Started", + "title":"Getting Started", + "githuburl":"" + }, + { + "uri":"dws_01_0088.html", + "product_code":"dws", + "code":"15", + "des":"This guide is an introductory tutorial that demonstrates how to create a sample GaussDB(DWS) cluster, connect to the cluster database, import the sample data from OBS, an", + "doc_type":"usermanual", + "kw":"Step 1: Starting Preparations,Getting Started,User Guide", + "title":"Step 1: Starting Preparations", + "githuburl":"" + }, + { + "uri":"dws_01_0013.html", + "product_code":"dws", + "code":"16", + "des":"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 ", + "doc_type":"usermanual", + "kw":"Step 2: Creating a Cluster,Getting Started,User Guide", + "title":"Step 2: Creating a Cluster", + "githuburl":"" + }, + { + "uri":"dws_01_0107.html", + "product_code":"dws", + "code":"17", + "des":"This section describes how to use a database client to connect to the database in a GaussDB(DWS) cluster. In the following example, the Data Studio client tool is used fo", + "doc_type":"usermanual", + "kw":"Step 3: Connecting to a Cluster,Getting Started,User Guide", + "title":"Step 3: Connecting to a Cluster", + "githuburl":"" + }, + { + "uri":"dws_01_0079.html", + "product_code":"dws", + "code":"18", + "des":"After performing the steps in preceding sections, you can refer to the documentation listed as follows for more information about GaussDB(DWS):Data Warehouse Service (DWS", + "doc_type":"usermanual", + "kw":"Step 4: Viewing Other Documents and Clearing Resources,Getting Started,User Guide", + "title":"Step 4: Viewing Other Documents and Clearing Resources", + "githuburl":"" + }, + { + "uri":"dws_01_0018.html", + "product_code":"dws", + "code":"19", + "des":"GaussDB(DWS) is an online data processing database that uses the cloud infrastructure to provide scalable, fully-managed, and out-of-the-box analytic database service, fr", + "doc_type":"usermanual", + "kw":"Process for Using GaussDB(DWS),User Guide", + "title":"Process for Using GaussDB(DWS)", + "githuburl":"" + }, + { + "uri":"dws_01_0154.html", + "product_code":"dws", + "code":"20", + "des":"Before using GaussDB(DWS), make the following preparations:Registering a Public Cloud Account and Completing Real-Name AuthenticationDetermining the Cluster PortsIf you d", + "doc_type":"usermanual", + "kw":"Preparations,User Guide", + "title":"Preparations", + "githuburl":"" + }, + { + "uri":"dws_01_0160.html", + "product_code":"dws", + "code":"21", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Cluster Configuration", + "title":"Cluster Configuration", + "githuburl":"" + }, + { + "uri":"dws_01_0157.html", + "product_code":"dws", + "code":"22", + "des":"This section describes how to log in to the GaussDB(DWS) management console and use GaussDB(DWS).", + "doc_type":"usermanual", + "kw":"Accessing the GaussDB(DWS) Management Console,Cluster Configuration,User Guide", + "title":"Accessing the GaussDB(DWS) Management Console", + "githuburl":"" + }, + { + "uri":"dws_01_0019.html", + "product_code":"dws", + "code":"23", + "des":"To use cloud GaussDB(DWS), create a cluster first.This section describes how to create a data warehouse cluster on the GaussDB(DWS) management console.You have evaluated ", + "doc_type":"usermanual", + "kw":"Creating a Cluster,Cluster Configuration,User Guide", + "title":"Creating a Cluster", + "githuburl":"" + }, + { + "uri":"dws_01_0131.html", + "product_code":"dws", + "code":"24", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Cluster Connection", + "title":"Cluster Connection", + "githuburl":"" + }, + { + "uri":"dws_01_0137.html", + "product_code":"dws", + "code":"25", + "des":"If you have created a GaussDB(DWS) cluster, you can use the SQL client tool or a third-party driver such as JDBC or ODBC to connect to the cluster and access the database", + "doc_type":"usermanual", + "kw":"Methods of Connecting to a Cluster,Cluster Connection,User Guide", + "title":"Methods of Connecting to a Cluster", + "githuburl":"" + }, + { + "uri":"dws_01_0033.html", + "product_code":"dws", + "code":"26", + "des":"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 p", + "doc_type":"usermanual", + "kw":"Obtaining the Cluster Connection Address,Cluster Connection,User Guide", + "title":"Obtaining the Cluster Connection Address", + "githuburl":"" + }, + { + "uri":"dws_01_0093.html", + "product_code":"dws", + "code":"27", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Using the gsql CLI Client to Connect to a Cluster", + "title":"Using the gsql CLI Client to Connect to a Cluster", + "githuburl":"" + }, + { + "uri":"dws_01_0031.html", + "product_code":"dws", + "code":"28", + "des":"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.The cl", + "doc_type":"usermanual", + "kw":"Downloading the Client,Using the gsql CLI Client to Connect to a Cluster,User Guide", + "title":"Downloading the Client", + "githuburl":"" + }, + { + "uri":"dws_01_0128.html", + "product_code":"dws", + "code":"29", + "des":"The gsql command line client provided by GaussDB(DWS) runs on the Linux OS. Before using it to remotely connect to a GaussDB(DWS) cluster, you need to prepare a Linux hos", + "doc_type":"usermanual", + "kw":"Preparing an ECS as the gsql Client Host,Using the gsql CLI Client to Connect to a Cluster,User Guid", + "title":"Preparing an ECS as the gsql Client Host", + "githuburl":"" + }, + { + "uri":"dws_01_0037.html", + "product_code":"dws", + "code":"30", + "des":"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", + "doc_type":"usermanual", + "kw":"Using the gsql Client to Connect to a Cluster,Using the gsql CLI Client to Connect to a Cluster,User", + "title":"Using the gsql Client to Connect to a Cluster", + "githuburl":"" + }, + { + "uri":"dws_01_0038.html", + "product_code":"dws", + "code":"31", + "des":"If the client or JDBC/ODBC driver needs to use SSL connection, you must configure related SSL connection parameters in the client or application code. The GaussDB(DWS) ma", + "doc_type":"usermanual", + "kw":"Establishing Secure TCP/IP Connections in SSL Mode,Using the gsql CLI Client to Connect to a Cluster", + "title":"Establishing Secure TCP/IP Connections in SSL Mode", + "githuburl":"" + }, + { + "uri":"dws_01_0076.html", + "product_code":"dws", + "code":"32", + "des":"GaussDB(DWS) supports connections in SSL authentication mode so that data transmitted between the GaussDB(DWS) client and the database can be encrypted. The SSL mode deli", + "doc_type":"usermanual", + "kw":"(Optional) Configuring SSL Connection,Using the gsql CLI Client to Connect to a Cluster,User Guide", + "title":"(Optional) Configuring SSL Connection", + "githuburl":"" + }, + { + "uri":"dws_01_0083.html", + "product_code":"dws", + "code":"33", + "des":"GaussDB(DWS) supports the standard SSL (TLS 1.2). As a highly secure protocol, SSL authenticates bidirectional identification between the server and client using digital ", + "doc_type":"usermanual", + "kw":"(Optional) Downloading the SSL Certificate,Using the gsql CLI Client to Connect to a Cluster,User Gu", + "title":"(Optional) Downloading the SSL Certificate", + "githuburl":"" + }, + { + "uri":"dws_01_0094.html", + "product_code":"dws", + "code":"34", + "des":"Data Studio is a SQL client tool running on the Windows operating system. It provides various GUIs for you to manage databases and database objects, as well as edit, run,", + "doc_type":"usermanual", + "kw":"Using the Data Studio GUI Client to Connect to a Cluster,Cluster Connection,User Guide", + "title":"Using the Data Studio GUI Client to Connect to a Cluster", + "githuburl":"" + }, + { + "uri":"dws_01_0081.html", + "product_code":"dws", + "code":"35", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Using the JDBC and ODBC Drivers to Connect to a Cluster", + "title":"Using the JDBC and ODBC Drivers to Connect to a Cluster", + "githuburl":"" + }, + { + "uri":"dws_01_0106.html", + "product_code":"dws", + "code":"36", + "des":"If the connection pool mechanism is used during application development, the following specifications must be met. Otherwise, connections in the connection pool have stat", + "doc_type":"usermanual", + "kw":"Development Specifications,Using the JDBC and ODBC Drivers to Connect to a Cluster,User Guide", + "title":"Development Specifications", + "githuburl":"" + }, + { + "uri":"dws_01_0032.html", + "product_code":"dws", + "code":"37", + "des":"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 us", + "doc_type":"usermanual", + "kw":"Downloading the JDBC or ODBC Driver,Using the JDBC and ODBC Drivers to Connect to a Cluster,User Gui", + "title":"Downloading the JDBC or ODBC Driver", + "githuburl":"" + }, + { + "uri":"dws_01_0077.html", + "product_code":"dws", + "code":"38", + "des":"In GaussDB(DWS), you can use a JDBC driver to connect to a database on Linux or Windows. The driver can connect to the database through an ECS on the cloud platform or ov", + "doc_type":"usermanual", + "kw":"Using a JDBC Driver to Connect to a Database,Using the JDBC and ODBC Drivers to Connect to a Cluster", + "title":"Using a JDBC Driver to Connect to a Database", + "githuburl":"" + }, + { + "uri":"dws_01_0086.html", + "product_code":"dws", + "code":"39", + "des":"GaussDB(DWS) allows you to use an ODBC driver to connect to the database through an ECS on the cloud platform or over the Internet.For details about how to use the ODBC A", + "doc_type":"usermanual", + "kw":"Using an ODBC Driver to Connect to a Database,Using the JDBC and ODBC Drivers to Connect to a Cluste", + "title":"Using an ODBC Driver to Connect to a Database", + "githuburl":"" + }, + { + "uri":"dws_01_0133.html", + "product_code":"dws", + "code":"40", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Connecting to a Cluster Using IAM Authentication", + "title":"Connecting to a Cluster Using IAM Authentication", + "githuburl":"" + }, + { + "uri":"dws_01_0134.html", + "product_code":"dws", + "code":"41", + "des":"GaussDB(DWS) allows you to access databases using IAM authentication. When you use the JDBC application program to connect to a cluster, set the IAM username, credential,", + "doc_type":"usermanual", + "kw":"Overview,Connecting to a Cluster Using IAM Authentication,User Guide", + "title":"Overview", + "githuburl":"" + }, + { + "uri":"dws_01_0135.html", + "product_code":"dws", + "code":"42", + "des":"The IAM account you use to access a database must be granted with the DWS Database Access permission. Only users with both the DWS Administrator and DWS Database Access p", + "doc_type":"usermanual", + "kw":"Granting an IAM Account the DWS Database Access Permission,Connecting to a Cluster Using IAM Authent", + "title":"Granting an IAM Account the DWS Database Access Permission", + "githuburl":"" + }, + { + "uri":"dws_01_0136.html", + "product_code":"dws", + "code":"43", + "des":"You can log in to the management console to create an AK/SK pair or use an existing one.Log in to the management console, move your cursor over your account in the upper ", + "doc_type":"usermanual", + "kw":"Creating an IAM User Credential,Connecting to a Cluster Using IAM Authentication,User Guide", + "title":"Creating an IAM User Credential", + "githuburl":"" + }, + { + "uri":"dws_01_0132.html", + "product_code":"dws", + "code":"44", + "des":"When you use the JDBC application program to connect to a cluster, set the IAM username, credential, and other information as you configure the JDBC URL. After doing this", + "doc_type":"usermanual", + "kw":"Configuring the JDBC Connection to Connect to a Cluster Using IAM Authentication,Connecting to a Clu", + "title":"Configuring the JDBC Connection to Connect to a Cluster Using IAM Authentication", + "githuburl":"" + }, + { + "uri":"dws_01_0039.html", + "product_code":"dws", + "code":"45", + "des":"By default, a database supports a certain number of connections. Administrators can manage database connections to learn about the connection performance of the current d", + "doc_type":"usermanual", + "kw":"Managing Database Connections,Cluster Connection,User Guide", + "title":"Managing Database Connections", + "githuburl":"" + }, + { + "uri":"dws_01_0600.html", + "product_code":"dws", + "code":"46", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Clusters", + "title":"Clusters", + "githuburl":"" + }, + { + "uri":"dws_01_0020.html", + "product_code":"dws", + "code":"47", + "des":"On the Clusters page of the GaussDB(DWS) management console, you can view the general information about a cluster in the cluster list, such as the cluster status, task in", + "doc_type":"usermanual", + "kw":"Checking the Cluster Status,Clusters,User Guide", + "title":"Checking the Cluster Status", + "githuburl":"" + }, + { + "uri":"dws_01_0112.html", + "product_code":"dws", + "code":"48", + "des":"Log in to the GaussDB(DWS) management console. In the navigation tree on the left, choose Clusters. In the cluster list, locate the required cluster and click its name. T", + "doc_type":"usermanual", + "kw":"Viewing Basic Cluster Information,Clusters,User Guide", + "title":"Viewing Basic Cluster Information", + "githuburl":"" + }, + { + "uri":"dws_01_0140.html", + "product_code":"dws", + "code":"49", + "des":"A domain name is a string of characters separated by dots to identify the location of a computer or a computer group on the Internet, for example, www.example.com. You ca", + "doc_type":"usermanual", + "kw":"Managing Access Domain Names,Clusters,User Guide", + "title":"Managing Access Domain Names", + "githuburl":"" + }, + { + "uri":"dws_01_0818.html", + "product_code":"dws", + "code":"50", + "des":"On the Nodes tab page, you can view the node list of the current cluster, add new nodes to or remove nodes from it, and view the node usage, status, and flavors.This feat", + "doc_type":"usermanual", + "kw":"Nodes,Clusters,User Guide", + "title":"Nodes", + "githuburl":"" + }, + { + "uri":"dws_01_0023.html", + "product_code":"dws", + "code":"51", + "des":"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 storag", + "doc_type":"usermanual", + "kw":"Cluster Scale-out,Clusters,User Guide", + "title":"Cluster Scale-out", + "githuburl":"" + }, + { + "uri":"dws_01_0820.html", + "product_code":"dws", + "code":"52", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Cluster Redistribution", + "title":"Cluster Redistribution", + "githuburl":"" + }, + { + "uri":"dws_01_8201.html", + "product_code":"dws", + "code":"53", + "des":"Data redistribution, where data in existing nodes is evenly allocated to the new nodes after you scale out a cluster, is a time-consuming yet crucial task that accelerate", + "doc_type":"usermanual", + "kw":"Redistributing Data,Cluster Redistribution,User Guide", + "title":"Redistributing Data", + "githuburl":"" + }, + { + "uri":"dws_01_8202.html", + "product_code":"dws", + "code":"54", + "des":"On the View Redistribution Details page, you can view the redistribution mode and progress of the current cluster. In offline scheduling mode, you can pause, resume, and ", + "doc_type":"usermanual", + "kw":"Viewing Redistribution Details,Cluster Redistribution,User Guide", + "title":"Viewing Redistribution Details", + "githuburl":"" + }, + { + "uri":"dws_01_8115.html", + "product_code":"dws", + "code":"55", + "des":"In the Unbalanced state, the number of primary instances on some nodes increases. As a result, the load pressure is high. In this case, the cluster is normal, but the ove", + "doc_type":"usermanual", + "kw":"Performing a Primary/Standby Switchback,Clusters,User Guide", + "title":"Performing a Primary/Standby Switchback", + "githuburl":"" + }, + { + "uri":"dws_01_0008.html", + "product_code":"dws", + "code":"56", + "des":"After you create a data warehouse cluster, the system automatically configures a random maintenance window for the cluster. Alternatively, you can customize a maintenance", + "doc_type":"usermanual", + "kw":"Cluster Upgrade,Clusters,User Guide", + "title":"Cluster Upgrade", + "githuburl":"" + }, + { + "uri":"dws_01_0026.html", + "product_code":"dws", + "code":"57", + "des":"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 numbe", + "doc_type":"usermanual", + "kw":"Password Reset,Clusters,User Guide", + "title":"Password Reset", + "githuburl":"" + }, + { + "uri":"dws_01_0024.html", + "product_code":"dws", + "code":"58", + "des":"If a cluster is in the Unbalanced state or cannot work properly, you may need to restart it for restoration. After modifying a cluster's configurations, such as security ", + "doc_type":"usermanual", + "kw":"Cluster Restart,Clusters,User Guide", + "title":"Cluster Restart", + "githuburl":"" + }, + { + "uri":"dws_01_0152.html", + "product_code":"dws", + "code":"59", + "des":"After a cluster is created, you can modify the cluster's database parameters as required. On the GaussDB(DWS) management console, you can view or set common database para", + "doc_type":"usermanual", + "kw":"Modifying Database Parameters,Clusters,User Guide", + "title":"Modifying Database Parameters", + "githuburl":"" + }, + { + "uri":"dws_01_0057.html", + "product_code":"dws", + "code":"60", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"MRS Data Sources", + "title":"MRS Data Sources", + "githuburl":"" + }, + { + "uri":"dws_01_0055.html", + "product_code":"dws", + "code":"61", + "des":"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 v", + "doc_type":"usermanual", + "kw":"Importing Data from MRS to GaussDB(DWS),MRS Data Sources,User Guide", + "title":"Importing Data from MRS to GaussDB(DWS)", + "githuburl":"" + }, + { + "uri":"dws_01_0059.html", + "product_code":"dws", + "code":"62", + "des":"Before GaussDB(DWS) reads data from MRS HDFS, you need to create an MRS data source connection that functions as a channel of transporting data warehouse cluster data and", + "doc_type":"usermanual", + "kw":"Creating an MRS Data Source Connection,MRS Data Sources,User Guide", + "title":"Creating an MRS Data Source Connection", + "githuburl":"" + }, + { + "uri":"dws_01_0156.html", + "product_code":"dws", + "code":"63", + "des":"For MRS, if the following parameter configurations of the HDFS cluster change, data may fail to be imported to the data warehouse cluster from the HDFS cluster. Before im", + "doc_type":"usermanual", + "kw":"Updating the MRS Data Source Configuration,MRS Data Sources,User Guide", + "title":"Updating the MRS Data Source Configuration", + "githuburl":"" + }, + { + "uri":"dws_01_0723.html", + "product_code":"dws", + "code":"64", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Managing Cluster Workloads", + "title":"Managing Cluster Workloads", + "githuburl":"" + }, + { + "uri":"dws_01_07231.html", + "product_code":"dws", + "code":"65", + "des":"When multiple database users query jobs at the same time, some complex queries may occupy cluster resources for a long time, affecting the performance of other queries. F", + "doc_type":"usermanual", + "kw":"Workload Management Overview,Managing Cluster Workloads,User Guide", + "title":"Workload Management Overview", + "githuburl":"" + }, + { + "uri":"dws_01_07233.html", + "product_code":"dws", + "code":"66", + "des":"You can create a maximum of 63 workload queues.", + "doc_type":"usermanual", + "kw":"Adding Workload Queues,Managing Cluster Workloads,User Guide", + "title":"Adding Workload Queues", + "githuburl":"" + }, + { + "uri":"dws_01_07234.html", + "product_code":"dws", + "code":"67", + "des":"You can modify the parameters of a workload queue.Click Edit on the right and modify the parameters according to Table 1.Workload queue parametersParameterDescriptionValu", + "doc_type":"usermanual", + "kw":"Modifying Workload Queues,Managing Cluster Workloads,User Guide", + "title":"Modifying Workload Queues", + "githuburl":"" + }, + { + "uri":"dws_01_07238.html", + "product_code":"dws", + "code":"68", + "des":"In the Query Overview area, you can view the number of long and short queries that are running in the current queue at the current time. The chart information is refreshe", + "doc_type":"usermanual", + "kw":"Workload Queue Query,Managing Cluster Workloads,User Guide", + "title":"Workload Queue Query", + "githuburl":"" + }, + { + "uri":"dws_01_07239.html", + "product_code":"dws", + "code":"69", + "des":"If the queue to be deleted has associated database users, these users will be associated with the default queue after the queue is deleted.", + "doc_type":"usermanual", + "kw":"Deleting Workload Queues,Managing Cluster Workloads,User Guide", + "title":"Deleting Workload Queues", + "githuburl":"" + }, + { + "uri":"dws_01_72362.html", + "product_code":"dws", + "code":"70", + "des":"Workload plan is an advanced workload management feature provided by GaussDB(DWS). You can create a workload plan, add multiple stages to the plan, and configure differen", + "doc_type":"usermanual", + "kw":"Workload Plans,Managing Cluster Workloads,User Guide", + "title":"Workload Plans", + "githuburl":"" + }, + { + "uri":"dws_01_72363.html", + "product_code":"dws", + "code":"71", + "des":"You must stop the workload plan when adding a stage. Otherwise, the stage cannot be added.You can add a maximum of 48 stages for each plan.The switchover time of all phas", + "doc_type":"usermanual", + "kw":"Stages of Workload Plans,Managing Cluster Workloads,User Guide", + "title":"Stages of Workload Plans", + "githuburl":"" + }, + { + "uri":"dws_01_72365.html", + "product_code":"dws", + "code":"72", + "des":"You can commission a workload plan in the test environment and export the plan configurations to the production environment.An ongoing workload plan cannot be imported.Be", + "doc_type":"usermanual", + "kw":"Importing and Exporting Workload Plans,Managing Cluster Workloads,User Guide", + "title":"Importing and Exporting Workload Plans", + "githuburl":"" + }, + { + "uri":"dws_01_0724.html", + "product_code":"dws", + "code":"73", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Managing Logical Clusters", + "title":"Managing Logical Clusters", + "githuburl":"" + }, + { + "uri":"dws_01_7241.html", + "product_code":"dws", + "code":"74", + "des":"A physical cluster can be divided into logical clusters that use the node-group mechanism. Tables in a database can be allocated to different physical nodes by logical cl", + "doc_type":"usermanual", + "kw":"Overview,Managing Logical Clusters,User Guide", + "title":"Overview", + "githuburl":"" + }, + { + "uri":"dws_01_7242.html", + "product_code":"dws", + "code":"75", + "des":"If you access the Logical Clusters page for the first time, the metadata of the logical cluster created at the backend is synchronized to the frontend. After the synchron", + "doc_type":"usermanual", + "kw":"Adding Logical Clusters,Managing Logical Clusters,User Guide", + "title":"Adding Logical Clusters", + "githuburl":"" + }, + { + "uri":"dws_01_7243.html", + "product_code":"dws", + "code":"76", + "des":"Nodes are added to or removed from a logical cluster by ring.At least one ring must be reserved in a logical cluster.The ring removed from the logical cluster will be add", + "doc_type":"usermanual", + "kw":"Editing Logical Clusters,Managing Logical Clusters,User Guide", + "title":"Editing Logical Clusters", + "githuburl":"" + }, + { + "uri":"dws_01_7244.html", + "product_code":"dws", + "code":"77", + "des":"The first added logical cluster cannot be deleted.Nodes of the deleted logical cluster are added to the elastic cluster.", + "doc_type":"usermanual", + "kw":"Deleting Logical Clusters,Managing Logical Clusters,User Guide", + "title":"Deleting Logical Clusters", + "githuburl":"" + }, + { + "uri":"dws_01_7245.html", + "product_code":"dws", + "code":"78", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Restarting Logical Clusters,Managing Logical Clusters,User Guide", + "title":"Restarting Logical Clusters", + "githuburl":"" + }, + { + "uri":"dws_01_7246.html", + "product_code":"dws", + "code":"79", + "des":"Logical clusters and elastic clusters cannot be scaled out online.", + "doc_type":"usermanual", + "kw":"Scaling Out Logical Clusters,Managing Logical Clusters,User Guide", + "title":"Scaling Out Logical Clusters", + "githuburl":"" + }, + { + "uri":"dws_01_0103.html", + "product_code":"dws", + "code":"80", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Managing Tags", + "title":"Managing Tags", + "githuburl":"" + }, + { + "uri":"dws_01_0104.html", + "product_code":"dws", + "code":"81", + "des":"A tag is a key-value pair customized by users and used to identify cloud resources. It helps users to classify and search for cloud resources.Tags are composed of key-val", + "doc_type":"usermanual", + "kw":"Overview,Managing Tags,User Guide", + "title":"Overview", + "githuburl":"" + }, + { + "uri":"dws_01_0105.html", + "product_code":"dws", + "code":"82", + "des":"This section describes how to search for clusters based on tags and how to add, modify, and delete tags for clusters.You can quickly locate a tagged cluster using tags.Yo", + "doc_type":"usermanual", + "kw":"Tag Management,Managing Tags,User Guide", + "title":"Tag Management", + "githuburl":"" + }, + { + "uri":"dws_01_0113.html", + "product_code":"dws", + "code":"83", + "des":"An enterprise project is a cloud resource management mode. Enterprise Management provides users with comprehensive management in cloud-based resources, personnel, and per", + "doc_type":"usermanual", + "kw":"Managing Enterprise Projects,Clusters,User Guide", + "title":"Managing Enterprise Projects", + "githuburl":"" + }, + { + "uri":"dws_01_0025.html", + "product_code":"dws", + "code":"84", + "des":"If you do not need to use a cluster, perform the operations in this section to delete it.Deleted clusters cannot be recovered. Additionally, you cannot access user data a", + "doc_type":"usermanual", + "kw":"Deleting Clusters,Clusters,User Guide", + "title":"Deleting Clusters", + "githuburl":"" + }, + { + "uri":"dws_01_0126.html", + "product_code":"dws", + "code":"85", + "des":"To facilitate database parameter configuration, GaussDB(DWS) provides the parameter template function. A parameter template contains some common database parameters. You ", + "doc_type":"usermanual", + "kw":"Managing Parameter Templates,Clusters,User Guide", + "title":"Managing Parameter Templates", + "githuburl":"" + }, + { + "uri":"dws_01_0073.html", + "product_code":"dws", + "code":"86", + "des":"If a cluster fails to be created, you can go to the Clusters page of the GaussDB(DWS) management console to view the cluster status and the cause of failure.For details a", + "doc_type":"usermanual", + "kw":"Managing Clusters That Fail to Be Created,Clusters,User Guide", + "title":"Managing Clusters That Fail to Be Created", + "githuburl":"" + }, + { + "uri":"dws_01_0035.html", + "product_code":"dws", + "code":"87", + "des":"No database operation is allowed on a read-only cluster. Cancel the read-only status on the management console.You can cancel the read-only status only when a cluster is ", + "doc_type":"usermanual", + "kw":"Read-only Status,Clusters,User Guide", + "title":"Read-only Status", + "githuburl":"" + }, + { + "uri":"dws_01_0161.html", + "product_code":"dws", + "code":"88", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Cluster HA", + "title":"Cluster HA", + "githuburl":"" + }, + { + "uri":"dws_01_0800.html", + "product_code":"dws", + "code":"89", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Snapshots", + "title":"Snapshots", + "githuburl":"" + }, + { + "uri":"dws_01_0151.html", + "product_code":"dws", + "code":"90", + "des":"A snapshot is a full or incremental backup of a GaussDB(DWS) cluster at a specific point in time. It records the current database data and cluster information, including ", + "doc_type":"usermanual", + "kw":"Overview,Snapshots,User Guide", + "title":"Overview", + "githuburl":"" + }, + { + "uri":"dws_01_0092.html", + "product_code":"dws", + "code":"91", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Manual Snapshots", + "title":"Manual Snapshots", + "githuburl":"" + }, + { + "uri":"dws_01_0028.html", + "product_code":"dws", + "code":"92", + "des":"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 ", + "doc_type":"usermanual", + "kw":"Manually Creating a Snapshot,Manual Snapshots,User Guide", + "title":"Manually Creating a Snapshot", + "githuburl":"" + }, + { + "uri":"dws_01_0030.html", + "product_code":"dws", + "code":"93", + "des":"On the Snapshots page, you can delete a snapshot in the Unavailable state or delete an available snapshot to release the storage space.Deleted snapshots cannot be restore", + "doc_type":"usermanual", + "kw":"Deleting Manual Snapshots,Manual Snapshots,User Guide", + "title":"Deleting Manual Snapshots", + "githuburl":"" + }, + { + "uri":"dws_01_1013.html", + "product_code":"dws", + "code":"94", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Automated Snapshots", + "title":"Automated Snapshots", + "githuburl":"" + }, + { + "uri":"dws_01_10131.html", + "product_code":"dws", + "code":"95", + "des":"Automated snapshots adopt differential incremental backups. The automated snapshot created for the first time is a full backup (base version), and then the system creates", + "doc_type":"usermanual", + "kw":"Automated Snapshot Overview,Automated Snapshots,User Guide", + "title":"Automated Snapshot Overview", + "githuburl":"" + }, + { + "uri":"dws_01_0089.html", + "product_code":"dws", + "code":"96", + "des":"You can select a snapshot type and set one or more automated snapshot policies for a cluster. After an automated snapshot policy is enabled, the system automatically crea", + "doc_type":"usermanual", + "kw":"Configuring an Automated Snapshot Policy,Automated Snapshots,User Guide", + "title":"Configuring an Automated Snapshot Policy", + "githuburl":"" + }, + { + "uri":"dws_01_0085.html", + "product_code":"dws", + "code":"97", + "des":"This section describes how to copy snapshots that are automatically created for long-term retention.All snapshots are displayed by default. You can copy the snapshots tha", + "doc_type":"usermanual", + "kw":"Copying Automated Snapshots,Automated Snapshots,User Guide", + "title":"Copying Automated Snapshots", + "githuburl":"" + }, + { + "uri":"dws_01_10134.html", + "product_code":"dws", + "code":"98", + "des":"Only GaussDB(DWS) can delete automated snapshots. You cannot delete them manually.GaussDB(DWS) deletes an automated snapshot if:The retention period of the snapshot ends.", + "doc_type":"usermanual", + "kw":"Deleting an Automated Snapshot,Automated Snapshots,User Guide", + "title":"Deleting an Automated Snapshot", + "githuburl":"" + }, + { + "uri":"dws_01_0021.html", + "product_code":"dws", + "code":"99", + "des":"This section describes how to view snapshot information on the Snapshots page.In the snapshot list, all snapshots are displayed by default. Click next to the snapshot na", + "doc_type":"usermanual", + "kw":"Viewing Snapshot Information,Snapshots,User Guide", + "title":"Viewing Snapshot Information", + "githuburl":"" + }, + { + "uri":"dws_01_1015.html", + "product_code":"dws", + "code":"100", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Restoration Using a Snapshot", + "title":"Restoration Using a Snapshot", + "githuburl":"" + }, + { + "uri":"dws_01_0029.html", + "product_code":"dws", + "code":"101", + "des":"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.When a snapshot is restored to a new c", + "doc_type":"usermanual", + "kw":"Restoring a Snapshot to a New Cluster,Restoration Using a Snapshot,User Guide", + "title":"Restoring a Snapshot to a New Cluster", + "githuburl":"" + }, + { + "uri":"dws_01_0080.html", + "product_code":"dws", + "code":"102", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Cluster DR", + "title":"Cluster DR", + "githuburl":"" + }, + { + "uri":"dws_01_00081.html", + "product_code":"dws", + "code":"103", + "des":"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 specif", + "doc_type":"usermanual", + "kw":"DR Overview,Cluster DR,User Guide", + "title":"DR Overview", + "githuburl":"" + }, + { + "uri":"dws_01_00082.html", + "product_code":"dws", + "code":"104", + "des":"You can create a DR task only when the cluster is in the Available or Unbalanced state.Type: Cross-AZ DRName: Enter 4 to 64 case-insensitive characters, starting with a l", + "doc_type":"usermanual", + "kw":"Creating a DR Task,Cluster DR,User Guide", + "title":"Creating a DR Task", + "githuburl":"" + }, + { + "uri":"dws_01_00083.html", + "product_code":"dws", + "code":"105", + "des":"On the page that is displayed, view the following information:DR Information: You can view the DR ID, DR name, DR creation time, and DR status.Production Cluster Informat", + "doc_type":"usermanual", + "kw":"Viewing DR Information,Cluster DR,User Guide", + "title":"Viewing DR Information", + "githuburl":"" + }, + { + "uri":"dws_01_00084.html", + "product_code":"dws", + "code":"106", + "des":"The DR status will change to Starting. The process will take some time. After the task is started, the DR status will change to Running.You can start a DR task that is in", + "doc_type":"usermanual", + "kw":"DR Management,Cluster DR,User Guide", + "title":"DR Management", + "githuburl":"" + }, + { + "uri":"dws_01_00085.html", + "product_code":"dws", + "code":"107", + "des":"After scale-out, the number of DNs in the production cluster must be the same as that in the DR cluster.", + "doc_type":"usermanual", + "kw":"Mutually Exclusive DR Cases,Cluster DR,User Guide", + "title":"Mutually Exclusive DR Cases", + "githuburl":"" + }, + { + "uri":"dws_01_0822.html", + "product_code":"dws", + "code":"108", + "des":"If the internal IP address or EIP of a CN is used to connect to a cluster, the failure of this CN will lead to cluster connection failure. If a private domain name is use", + "doc_type":"usermanual", + "kw":"Associating and Disassociating ELB,Cluster HA,User Guide", + "title":"Associating and Disassociating ELB", + "githuburl":"" + }, + { + "uri":"dws_01_7115.html", + "product_code":"dws", + "code":"109", + "des":"After a cluster is created, the number of required CNs varies with service requirements. The CN management function enables you to adjust the number of CNs in the cluster", + "doc_type":"usermanual", + "kw":"CNs,Cluster HA,User Guide", + "title":"CNs", + "githuburl":"" + }, + { + "uri":"dws_01_0162.html", + "product_code":"dws", + "code":"110", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Monitoring and Alarms", + "title":"Monitoring and Alarms", + "githuburl":"" + }, + { + "uri":"dws_01_0022.html", + "product_code":"dws", + "code":"111", + "des":"This section describes how to check cluster metrics on Cloud Eye. By monitoring cluster running metrics, you can identify the time when the database cluster is abnormal a", + "doc_type":"usermanual", + "kw":"Monitoring Clusters Using Cloud Eye,Monitoring and Alarms,User Guide", + "title":"Monitoring Clusters Using Cloud Eye", + "githuburl":"" + }, + { + "uri":"dws_01_00014.html", + "product_code":"dws", + "code":"112", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Databases Monitoring", + "title":"Databases Monitoring", + "githuburl":"" + }, + { + "uri":"dws_01_00131.html", + "product_code":"dws", + "code":"113", + "des":"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 ", + "doc_type":"usermanual", + "kw":"Database Monitoring Overview,Databases Monitoring,User Guide", + "title":"Database Monitoring Overview", + "githuburl":"" + }, + { + "uri":"dws_01_00136.html", + "product_code":"dws", + "code":"114", + "des":"You can check the status and available resources of a cluster and learn about its real-time resource consumption through the GaussDB(DWS) monitoring items.Table 1 describ", + "doc_type":"usermanual", + "kw":"Monitoring Metrics,Databases Monitoring,User Guide", + "title":"Monitoring Metrics", + "githuburl":"" + }, + { + "uri":"dws_01_00132.html", + "product_code":"dws", + "code":"115", + "des":"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", + "doc_type":"usermanual", + "kw":"Cluster Overview,Databases Monitoring,User Guide", + "title":"Cluster Overview", + "githuburl":"" + }, + { + "uri":"dws_01_00133.html", + "product_code":"dws", + "code":"116", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Monitoring", + "title":"Monitoring", + "githuburl":"" + }, + { + "uri":"dws_01_1331.html", + "product_code":"dws", + "code":"117", + "des":"On the page that is displayed, view the real-time consumption of nodes, memory, disks, disk I/O, and network I/O.On the Overview tab page, you can view the key resources ", + "doc_type":"usermanual", + "kw":"Node Monitoring,Monitoring,User Guide", + "title":"Node Monitoring", + "githuburl":"" + }, + { + "uri":"dws_01_1337.html", + "product_code":"dws", + "code":"118", + "des":"The Performance Monitoring page displays the resource consumption trends of clusters and databases.You can configure monitoring views by customizing monitoring panels. Mo", + "doc_type":"usermanual", + "kw":"Performance Monitoring,Monitoring,User Guide", + "title":"Performance Monitoring", + "githuburl":"" + }, + { + "uri":"dws_01_1332.html", + "product_code":"dws", + "code":"119", + "des":"The Database Monitoring page displays the real-time and historical resource consumption a database.You can select a database and check its resource usage. For details, se", + "doc_type":"usermanual", + "kw":"Database Monitoring,Monitoring,User Guide", + "title":"Database Monitoring", + "githuburl":"" + }, + { + "uri":"dws_01_1333.html", + "product_code":"dws", + "code":"120", + "des":"The Session Monitoring page displays the session-level real-time database query statistics. You can also select and terminate a session.You can browse the query statistic", + "doc_type":"usermanual", + "kw":"Session Monitoring,Monitoring,User Guide", + "title":"Session Monitoring", + "githuburl":"" + }, + { + "uri":"dws_01_1334.html", + "product_code":"dws", + "code":"121", + "des":"The Query Monitoring page displays the real-time information about all queries that are running in a cluster and the historical information about the queries that have be", + "doc_type":"usermanual", + "kw":"Query Monitoring,Monitoring,User Guide", + "title":"Query Monitoring", + "githuburl":"" + }, + { + "uri":"dws_01_1338.html", + "product_code":"dws", + "code":"122", + "des":"On the Instance Monitoring page, you can view the real-time and historical information about detected slow instances.DMS can automatically configure and start the slow in", + "doc_type":"usermanual", + "kw":"Instance Monitoring,Monitoring,User Guide", + "title":"Instance Monitoring", + "githuburl":"" + }, + { + "uri":"dws_01_1339.html", + "product_code":"dws", + "code":"123", + "des":"On the Load Monitoring page, you can view the real-time and historical resource consumption of workload queues.The DMS displays the user-defined workload queue name, real", + "doc_type":"usermanual", + "kw":"Load Monitoring,Monitoring,User Guide", + "title":"Load Monitoring", + "githuburl":"" + }, + { + "uri":"dws_01_00175.html", + "product_code":"dws", + "code":"124", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Utilities", + "title":"Utilities", + "githuburl":"" + }, + { + "uri":"dws_01_00134.html", + "product_code":"dws", + "code":"125", + "des":"To enable SQL diagnosis, enable monitoring on real-time and historical queries on the Queries and History tabs, respectively. For details, see .Query IDDatabaseSchema Nam", + "doc_type":"usermanual", + "kw":"SQL Diagnosis,Utilities,User Guide", + "title":"SQL Diagnosis", + "githuburl":"" + }, + { + "uri":"dws_01_01752.html", + "product_code":"dws", + "code":"126", + "des":"You can audit DDL to check DDL metadata, identify inappropriate table definitions, and locate performance problems.This feature is supported only in cluster version 8.1.2", + "doc_type":"usermanual", + "kw":"DDL Audit,Utilities,User Guide", + "title":"DDL Audit", + "githuburl":"" + }, + { + "uri":"dws_01_00135.html", + "product_code":"dws", + "code":"127", + "des":"The Monitoring page displays the collection period and data aging period of monitoring metrics.The cluster monitoring function is enabled by default.Disable the function ", + "doc_type":"usermanual", + "kw":"Settings,Databases Monitoring,User Guide", + "title":"Settings", + "githuburl":"" + }, + { + "uri":"dws_01_00137.html", + "product_code":"dws", + "code":"128", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Typical Scenarios", + "title":"Typical Scenarios", + "githuburl":"" + }, + { + "uri":"dws_01_01372.html", + "product_code":"dws", + "code":"129", + "des":"The execution of SQL statements takes a long time, resulting in great resource consumption.If the execution efficiency of SQL statements is low, optimization suggestions ", + "doc_type":"usermanual", + "kw":"SQL Diagnosis,Typical Scenarios,User Guide", + "title":"SQL Diagnosis", + "githuburl":"" + }, + { + "uri":"dws_01_01373.html", + "product_code":"dws", + "code":"130", + "des":"Time-consuming SQL statements exist.On the Top 5 Time-Consuming Queries page directed from the Cluster Overview page, record the change of top 5 time-consuming queries.An", + "doc_type":"usermanual", + "kw":"Top Time-Consuming SQL Statements Viewing,Typical Scenarios,User Guide", + "title":"Top Time-Consuming SQL Statements Viewing", + "githuburl":"" + }, + { + "uri":"dws_01_1240.html", + "product_code":"dws", + "code":"131", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Alarms", + "title":"Alarms", + "githuburl":"" + }, + { + "uri":"dws_01_1241.html", + "product_code":"dws", + "code":"132", + "des":"Alarm management includes viewing and configuring alarm rules and subscribing to alarm information. Alarm rules display alarm statistics and details of the past week for ", + "doc_type":"usermanual", + "kw":"Alarm Management,Alarms,User Guide", + "title":"Alarm Management", + "githuburl":"" + }, + { + "uri":"dws_01_1242.html", + "product_code":"dws", + "code":"133", + "des":"Concepts related to threshold alarmsAlarm rule: consists of the alarm rule name, rule description, clusters associated with the rule, alarm policy triggering relationship", + "doc_type":"usermanual", + "kw":"Alarm Rules,Alarms,User Guide", + "title":"Alarm Rules", + "githuburl":"" + }, + { + "uri":"dws_01_1243.html", + "product_code":"dws", + "code":"134", + "des":"You can subscribe to GaussDB(DWS) alarm notifications to receive notifications by SMS message, email, or application when an alarm of a specified severity is generated.To", + "doc_type":"usermanual", + "kw":"Alarm Subscriptions,Alarms,User Guide", + "title":"Alarm Subscriptions", + "githuburl":"" + }, + { + "uri":"dws_01_0700.html", + "product_code":"dws", + "code":"135", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Cluster Security Management", + "title":"Cluster Security Management", + "githuburl":"" + }, + { + "uri":"dws_01_0074.html", + "product_code":"dws", + "code":"136", + "des":"By default, the administrator specified when you create a GaussDB(DWS) cluster is the database system administrator. The administrator can create other users and view the", + "doc_type":"usermanual", + "kw":"Configuring Separation of Permissions,Cluster Security Management,User Guide", + "title":"Configuring Separation of Permissions", + "githuburl":"" + }, + { + "uri":"dws_01_0145.html", + "product_code":"dws", + "code":"137", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Permissions", + "title":"Permissions", + "githuburl":"" + }, + { + "uri":"dws_01_0150.html", + "product_code":"dws", + "code":"138", + "des":"An RBAC policy consists of a Version, a Statement, and Depends.When selecting a policy for a user group, click below the policy to view the details of the policy. The DW", + "doc_type":"usermanual", + "kw":"RBAC Syntax of RBAC Policies,Permissions,User Guide", + "title":"RBAC Syntax of RBAC Policies", + "githuburl":"" + }, + { + "uri":"dws_01_0701.html", + "product_code":"dws", + "code":"139", + "des":"GaussDB(DWS) protects mission-critical operations. If you want to perform a mission-critical operation on the management console, you must enter a credential for identity", + "doc_type":"usermanual", + "kw":"Protection for Mission-Critical Operations,Cluster Security Management,User Guide", + "title":"Protection for Mission-Critical Operations", + "githuburl":"" + }, + { + "uri":"dws_01_0119.html", + "product_code":"dws", + "code":"140", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Audit Logs", + "title":"Audit Logs", + "githuburl":"" + }, + { + "uri":"dws_01_1911.html", + "product_code":"dws", + "code":"141", + "des":"Tenant database audit logs:GaussDB(DWS) allows you to record the audit logs of specific operations, involving audit log retention policies, unauthorized access, as well a", + "doc_type":"usermanual", + "kw":"Overview,Audit Logs,User Guide", + "title":"Overview", + "githuburl":"" + }, + { + "uri":"dws_01_0118.html", + "product_code":"dws", + "code":"142", + "des":"This section is organized as follows:Enabling CTSDisabling the Audit Log FunctionKey OperationsViewing TracesA tracker will be automatically created after CTS is enabled.", + "doc_type":"usermanual", + "kw":"Viewing Audit Logs of Key Operations on the Management Console,Audit Logs,User Guide", + "title":"Viewing Audit Logs of Key Operations on the Management Console", + "githuburl":"" + }, + { + "uri":"dws_01_0075.html", + "product_code":"dws", + "code":"143", + "des":"Database audit logs are configured on the Security Settings page. You can change security settings only when the cluster status is Available and Unbalanced, and Task Info", + "doc_type":"usermanual", + "kw":"Configuring the Database Audit Logs,Audit Logs,User Guide", + "title":"Configuring the Database Audit Logs", + "githuburl":"" + }, + { + "uri":"dws_01_0142.html", + "product_code":"dws", + "code":"144", + "des":"GaussDB(DWS) records information (audit logs) about connections and user activities in your database. With the information, you can monitor the database to ensure securit", + "doc_type":"usermanual", + "kw":"Dumping the Database Audit Logs,Audit Logs,User Guide", + "title":"Dumping the Database Audit Logs", + "githuburl":"" + }, + { + "uri":"dws_03_0061.html", + "product_code":"dws", + "code":"145", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"FAQs", + "title":"FAQs", + "githuburl":"" + }, + { + "uri":"dws_03_0001.html", + "product_code":"dws", + "code":"146", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"General Problems", + "title":"General Problems", + "githuburl":"" + }, + { + "uri":"dws_03_0003.html", + "product_code":"dws", + "code":"147", + "des":"Much data (orders, stocks, materials, and payments) is generated in the business operation systems and background (transactional) database of enterprises.Decision makers ", + "doc_type":"usermanual", + "kw":"Why Are Data Warehouses Necessary?,General Problems,User Guide", + "title":"Why Are Data Warehouses Necessary?", + "githuburl":"" + }, + { + "uri":"dws_03_0005.html", + "product_code":"dws", + "code":"148", + "des":"The Hadoop big data platform can be regarded as a next-generation data warehousing system. It has the characteristics of modern data warehouses and is widely used by ente", + "doc_type":"usermanual", + "kw":"What Are the Differences Between a Data Warehouse and the Hadoop Big Data Platform?,General Problems", + "title":"What Are the Differences Between a Data Warehouse and the Hadoop Big Data Platform?", + "githuburl":"" + }, + { + "uri":"dws_03_0006.html", + "product_code":"dws", + "code":"149", + "des":"Conventional data warehouses are not practical for smaller enterprises due to high cost, time-consuming device and system selection and procurement, and complex scale-out", + "doc_type":"usermanual", + "kw":"Why Should I Use Public Cloud GaussDB(DWS)?,General Problems,User Guide", + "title":"Why Should I Use Public Cloud GaussDB(DWS)?", + "githuburl":"" + }, + { + "uri":"dws_03_0009.html", + "product_code":"dws", + "code":"150", + "des":"Both allow you to run conventional relational databases on the cloud and transfer database management loads. RDS databases are useful for OLTP, reporting, and analysis, b", + "doc_type":"usermanual", + "kw":"Should I Choose Public Cloud GaussDB(DWS) or RDS?,General Problems,User Guide", + "title":"Should I Choose Public Cloud GaussDB(DWS) or RDS?", + "githuburl":"" + }, + { + "uri":"dws_03_0010.html", + "product_code":"dws", + "code":"151", + "des":"MRS works better with big data processing frameworks such as Apache Spark, Hadoop, and HBase, to process and analyze ultra-large data sets through custom code. It allows ", + "doc_type":"usermanual", + "kw":"When Should I Use GaussDB(DWS) and MRS?,General Problems,User Guide", + "title":"When Should I Use GaussDB(DWS) and MRS?", + "githuburl":"" + }, + { + "uri":"dws_03_0011.html", + "product_code":"dws", + "code":"152", + "des":"No. Although SQL on OBS of GaussDB(DWS) can be used for GaussDB(DWS) and OBS data query, it cannot replace the processing frameworks of MRS.Apart from SQL query, MRS also", + "doc_type":"usermanual", + "kw":"Can GaussDB(DWS) SQL on OBS Replace MRS?,General Problems,User Guide", + "title":"Can GaussDB(DWS) SQL on OBS Replace MRS?", + "githuburl":"" + }, + { + "uri":"dws_03_0037.html", + "product_code":"dws", + "code":"153", + "des":"GaussDB(DWS) and Hive have different functions in the following aspects:Hive is a data warehouse based on Hadoop MapReduce. GaussDB(DWS) is a data warehouse based on Post", + "doc_type":"usermanual", + "kw":"What Are the Differences Between GaussDB(DWS) and Hive in Functions?,General Problems,User Guide", + "title":"What Are the Differences Between GaussDB(DWS) and Hive in Functions?", + "githuburl":"" + }, + { + "uri":"dws_03_0034.html", + "product_code":"dws", + "code":"154", + "des":"For cloud services, quotas limit the number of resources available to users. If you need more, submit a service ticket to increase your quotas. Once approved, we will upd", + "doc_type":"usermanual", + "kw":"What Is the User Quota?,General Problems,User Guide", + "title":"What Is the User Quota?", + "githuburl":"" + }, + { + "uri":"dws_03_0067.html", + "product_code":"dws", + "code":"155", + "des":"Users and roles are shared within the entire cluster, but their data is not shared. That is, a user can connect to any database, but after the connection is successful, a", + "doc_type":"usermanual", + "kw":"What Are the Differences Between Users and Roles?,General Problems,User Guide", + "title":"What Are the Differences Between Users and Roles?", + "githuburl":"" + }, + { + "uri":"dws_03_0052.html", + "product_code":"dws", + "code":"156", + "des":"A region and availability zone (AZ) identify the location of a data center. You can create resources in regions and AZs.A region is a physical data center. Each region is", + "doc_type":"usermanual", + "kw":"Regions and AZs,General Problems,User Guide", + "title":"Regions and AZs", + "githuburl":"" + }, + { + "uri":"dws_03_0022.html", + "product_code":"dws", + "code":"157", + "des":"Yes. In the big data era, data has become a core asset. The public cloud will adhere to the commitment made over the years that we do not touch your applications or data,", + "doc_type":"usermanual", + "kw":"Is My Data Secure in GaussDB(DWS)?,General Problems,User Guide", + "title":"Is My Data Secure in GaussDB(DWS)?", + "githuburl":"" + }, + { + "uri":"dws_03_0023.html", + "product_code":"dws", + "code":"158", + "des":"GaussDB(DWS) uses IAM and VPC to control user access and isolate cluster network. Cluster access is over SSL and cipher suite. Additionally, GaussDB(DWS) supports two-way", + "doc_type":"usermanual", + "kw":"How Is GaussDB(DWS) Secured?,General Problems,User Guide", + "title":"How Is GaussDB(DWS) Secured?", + "githuburl":"" + }, + { + "uri":"dws_03_0053.html", + "product_code":"dws", + "code":"159", + "des":"Yes. When a data warehouse cluster is created, its security group cannot be changed. However, you can add, delete, or modify rules of the current security group.To edit t", + "doc_type":"usermanual", + "kw":"Can I Modify the Security Group of a GaussDB(DWS) Cluster?,General Problems,User Guide", + "title":"Can I Modify the Security Group of a GaussDB(DWS) Cluster?", + "githuburl":"" + }, + { + "uri":"dws_03_2121.html", + "product_code":"dws", + "code":"160", + "des":"The evolving Internet and IoT produce massive volumes of data. This data needs to be managed, using concepts like database, data warehouse, data lake, and lakehouse. Here", + "doc_type":"usermanual", + "kw":"What Is a Database/Data Warehouse/Data Lake/Lakehouse?,General Problems,User Guide", + "title":"What Is a Database/Data Warehouse/Data Lake/Lakehouse?", + "githuburl":"" + }, + { + "uri":"dws_03_0029.html", + "product_code":"dws", + "code":"161", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Cluster Management", + "title":"Cluster Management", + "githuburl":"" + }, + { + "uri":"dws_03_0016.html", + "product_code":"dws", + "code":"162", + "des":"Check that you have enough quota for creating the cluster.Call the Customer Hotline for support.Telephone:Germany: 0800 330 44 44International: +800 44556600", + "doc_type":"usermanual", + "kw":"What Do I Do If Creating a GaussDB(DWS) Cluster Failed?,Cluster Management,User Guide", + "title":"What Do I Do If Creating a GaussDB(DWS) Cluster Failed?", + "githuburl":"" + }, + { + "uri":"dws_03_0031.html", + "product_code":"dws", + "code":"163", + "des":"Cluster patching or upgrading is automatic because GaussDB(DWS) upgrades its own version.For service patch:Duration: less than 10 minutesImpact on services: 1 to 3 minute", + "doc_type":"usermanual", + "kw":"How Can I Upgrade or Downgrade GaussDB(DWS)?,Cluster Management,User Guide", + "title":"How Can I Upgrade or Downgrade GaussDB(DWS)?", + "githuburl":"" + }, + { + "uri":"dws_03_0033.html", + "product_code":"dws", + "code":"164", + "des":"After you delete data stored in GaussDB(DWS) data warehouses, dirty data may be generated from the unreleased disk space. This results in space waste and deteriorates sna", + "doc_type":"usermanual", + "kw":"How Can I Clear and Reclaim Storage?,Cluster Management,User Guide", + "title":"How Can I Clear and Reclaim Storage?", + "githuburl":"" + }, + { + "uri":"dws_03_0054.html", + "product_code":"dws", + "code":"165", + "des":"If you do not run VACUUM to clear and reclaim the storage space before the scale-out, the data deleted from GaussDB(DWS) may not free up the occupied disk space.During th", + "doc_type":"usermanual", + "kw":"Why Did the Used Storage Reduce After Scale-out?,Cluster Management,User Guide", + "title":"Why Did the Used Storage Reduce After Scale-out?", + "githuburl":"" + }, + { + "uri":"dws_03_0104.html", + "product_code":"dws", + "code":"166", + "des":"You can view the used capacity of a cluster CPU, memory, and disks on the Cloud Eye management console. Perform the following steps to view the information:", + "doc_type":"usermanual", + "kw":"How Do I View Node Metrics (CPU, Memory, and Disk Usage)?,Cluster Management,User Guide", + "title":"How Do I View Node Metrics (CPU, Memory, and Disk Usage)?", + "githuburl":"" + }, + { + "uri":"dws_03_0090.html", + "product_code":"dws", + "code":"167", + "des":"A cluster with three data nodes of 320 GB each has a total capacity of 960 GB. When 1 GB data is stored, GaussDB(DWS) stores 1 GB data on two nodes due to duplication, a ", + "doc_type":"usermanual", + "kw":"How Is the Disk Space or Capacity of GaussDB(DWS) Calculated?,Cluster Management,User Guide", + "title":"How Is the Disk Space or Capacity of GaussDB(DWS) Calculated?", + "githuburl":"" + }, + { + "uri":"dws_03_0024.html", + "product_code":"dws", + "code":"168", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Database Connections", + "title":"Database Connections", + "githuburl":"" + }, + { + "uri":"dws_03_0017.html", + "product_code":"dws", + "code":"169", + "des":"Yes, but GaussDB(DWS) clients and drivers are recommended. Unlike open-source PostgreSQL clients and drivers, GaussDB(DWS) clients and drivers have two key advantages:Sec", + "doc_type":"usermanual", + "kw":"Does GaussDB(DWS) Support Third-Party Clients and JDBC and ODBC Drivers?,Database Connections,User G", + "title":"Does GaussDB(DWS) Support Third-Party Clients and JDBC and ODBC Drivers?", + "githuburl":"" + }, + { + "uri":"dws_03_0040.html", + "product_code":"dws", + "code":"170", + "des":"No, direct access is not supported. VMs at the bottom layer of GaussDB(DWS) serve as the compute nodes for data analysis. Access cluster databases using the private or pu", + "doc_type":"usermanual", + "kw":"Can I Connect to GaussDB(DWS) Cluster Nodes Using SSH?,Database Connections,User Guide", + "title":"Can I Connect to GaussDB(DWS) Cluster Nodes Using SSH?", + "githuburl":"" + }, + { + "uri":"dws_03_0014.html", + "product_code":"dws", + "code":"171", + "des":"Check:Whether the cluster status is normal.Whether the connection command, username, password, IP address, and port are correct.Whether the operating system type and vers", + "doc_type":"usermanual", + "kw":"What Should I Do If I Cannot Connect to a Data Warehouse Cluster?,Database Connections,User Guide", + "title":"What Should I Do If I Cannot Connect to a Data Warehouse Cluster?", + "githuburl":"" + }, + { + "uri":"dws_03_0025.html", + "product_code":"dws", + "code":"172", + "des":"After the EIP is unbound, the network may be disconnected. However, the TCP layer does not detect a faulty physical connection in time due to keepalive settings. As a res", + "doc_type":"usermanual", + "kw":"Why Was I Not Notified of Failure Unbinding the EIP When GaussDB(DWS) Is Connected Over the Internet", + "title":"Why Was I Not Notified of Failure Unbinding the EIP When GaussDB(DWS) Is Connected Over the Internet?", + "githuburl":"" + }, + { + "uri":"dws_03_0169.html", + "product_code":"dws", + "code":"173", + "des":"Resources in different AZs of the same region can communicate with each other directly if they belong to the same VPC.For resources in different AZs of the same region bu", + "doc_type":"usermanual", + "kw":"How Can a Data Warehouse and a Database in Different AZs of the Same Region Communicate?,Database Co", + "title":"How Can a Data Warehouse and a Database in Different AZs of the Same Region Communicate?", + "githuburl":"" + }, + { + "uri":"dws_03_2125.html", + "product_code":"dws", + "code":"174", + "des":"If BI applications, client ECS, and DGC need to communicate with GaussDB(DWS), they must be in the same region and VPC as the GaussDB(DWS) cluster (different subnets are ", + "doc_type":"usermanual", + "kw":"Do I Need the Same VPC and Subnet to Connect to a GaussDB(DWS) Cluster?,Database Connections,User Gu", + "title":"Do I Need the Same VPC and Subnet to Connect to a GaussDB(DWS) Cluster?", + "githuburl":"" + }, + { + "uri":"dws_03_2130.html", + "product_code":"dws", + "code":"175", + "des":"You can also log in to the VPC management console to manually create a security group. Then, go back to the page for creating data warehouse clusters, click the button n", + "doc_type":"usermanual", + "kw":"How Do I Configure a Whitelist to Protect Clusters Available Through a Public IP Address?,Database C", + "title":"How Do I Configure a Whitelist to Protect Clusters Available Through a Public IP Address?", + "githuburl":"" + }, + { + "uri":"dws_03_0026.html", + "product_code":"dws", + "code":"176", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Data Import and Export", + "title":"Data Import and Export", + "githuburl":"" + }, + { + "uri":"dws_03_0018.html", + "product_code":"dws", + "code":"177", + "des":"The file formats supported by OBS and GDS foreign tables are as follows:OBS file formats: CSV, TEXT, ORC, and CARBONDATA. The default format is TEXT.GDS file formats: CSV", + "doc_type":"usermanual", + "kw":"What Are the Differences Between Data Formats Supported by OBS and GDS Foreign Tables?,Data Import a", + "title":"What Are the Differences Between Data Formats Supported by OBS and GDS Foreign Tables?", + "githuburl":"" + }, + { + "uri":"dws_03_0027.html", + "product_code":"dws", + "code":"178", + "des":"GaussDB(DWS) supports efficient data import from multiple data sources. The following lists typical data import modes. For details, see \"Import Modes\" in the Data Warehou", + "doc_type":"usermanual", + "kw":"How Can I Import Data to GaussDB(DWS)?,Data Import and Export,User Guide", + "title":"How Can I Import Data to GaussDB(DWS)?", + "githuburl":"" + }, + { + "uri":"dws_03_0028.html", + "product_code":"dws", + "code":"179", + "des":"Each node in a data warehouse cluster has a default storage capacity of 160 GB, 256 GB, 1.6 TB, 1.8 TB, or 13 TB. A cluster can house 3 to 32 nodes and the total storage ", + "doc_type":"usermanual", + "kw":"How Much Service Data Can a Data Warehouse Store?,Data Import and Export,User Guide", + "title":"How Much Service Data Can a Data Warehouse Store?", + "githuburl":"" + }, + { + "uri":"dws_03_0073.html", + "product_code":"dws", + "code":"180", + "des":"GaussDB(DWS) is a fully managed service on the cloud. Users cannot log in to the background to import or export data by using COPY, so the COPY syntax is disabled. You ar", + "doc_type":"usermanual", + "kw":"How Do I Use \\Copy to Import and Export Data?,Data Import and Export,User Guide", + "title":"How Do I Use \\Copy to Import and Export Data?", + "githuburl":"" + }, + { + "uri":"dws_03_0102.html", + "product_code":"dws", + "code":"181", + "des":"No, GaussDB(DWS) does not support OBS data import or export across regions. The GaussDB(DWS) cluster and OBS must be in the same region.", + "doc_type":"usermanual", + "kw":"Can I Export GaussDB(DWS) Data from/to OBS Across Regions?,Data Import and Export,User Guide", + "title":"Can I Export GaussDB(DWS) Data from/to OBS Across Regions?", + "githuburl":"" + }, + { + "uri":"dws_03_0074.html", + "product_code":"dws", + "code":"182", + "des":"To import heterogeneous data to GaussDB(DWS), use CDM to migrate the entire MySQL or SQL Server database. Or migrate the entire GaussDB(DWS) database to another GaussDB(D", + "doc_type":"usermanual", + "kw":"How Do I Import GaussDB(DWS)/Oracle/MySQL/SQL Server Data to GaussDB(DWS) (Whole Database Migration)", + "title":"How Do I Import GaussDB(DWS)/Oracle/MySQL/SQL Server Data to GaussDB(DWS) (Whole Database Migration)?", + "githuburl":"" + }, + { + "uri":"dws_03_0105.html", + "product_code":"dws", + "code":"183", + "des":"No. The GDS server and GaussDB(DWS) can only communicate with each other on the intranet. Each DN in the GaussDB(DWS) cluster is used to connect to the GDS server in para", + "doc_type":"usermanual", + "kw":"Can I Import Data over the Public/External Network Using GDS?,Data Import and Export,User Guide", + "title":"Can I Import Data over the Public/External Network Using GDS?", + "githuburl":"" + }, + { + "uri":"dws_03_0110.html", + "product_code":"dws", + "code":"184", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Account, Password, and Permissions", + "title":"Account, Password, and Permissions", + "githuburl":"" + }, + { + "uri":"dws_03_0092.html", + "product_code":"dws", + "code":"185", + "des":"To change the password of the database administrator dbadmin, log in to the console and choose More > Reset Password in cluster row.For security, the following two parame", + "doc_type":"usermanual", + "kw":"How Do I Change My Expired Database Password?,Account, Password, and Permissions,User Guide", + "title":"How Do I Change My Expired Database Password?", + "githuburl":"" + }, + { + "uri":"dws_03_0095.html", + "product_code":"dws", + "code":"186", + "des":"To view the user list, query the PG_USER view.SELECT * FROM pg_user;To view user attributes, query the PG_AUTHID system catalog.SELECT * FROM pg_authid;Query the permissi", + "doc_type":"usermanual", + "kw":"How Do I View All Database Users and Their Permissions?,Account, Password, and Permissions,User Guid", + "title":"How Do I View All Database Users and Their Permissions?", + "githuburl":"" + }, + { + "uri":"dws_03_0197.html", + "product_code":"dws", + "code":"187", + "des":"This section describes how to grant users the SELECT, INSERT, UPDATE, or full permissions for tables.Assume there are users u1, u2, u3, u4, and u5 and five schemas named ", + "doc_type":"usermanual", + "kw":"How Do I Grant Table Permissions to a User?,Account, Password, and Permissions,User Guide", + "title":"How Do I Grant Table Permissions to a User?", + "githuburl":"" + }, + { + "uri":"dws_03_0196.html", + "product_code":"dws", + "code":"188", + "des":"This section describes how to grant the query permission for a schema as an example. For more information, see \"How Do I Grant Table Permissions to a User?\" in FAQ. You ", + "doc_type":"usermanual", + "kw":"How Do I Grant Schema Permissions to a User?,Account, Password, and Permissions,User Guide", + "title":"How Do I Grant Schema Permissions to a User?", + "githuburl":"" + }, + { + "uri":"dws_03_0195.html", + "product_code":"dws", + "code":"189", + "des":"GaussDB(DWS) provides an implicitly defined group public that contains all roles. By default, all new users and roles have the permissions of public. To revoke permission", + "doc_type":"usermanual", + "kw":"How Do I Revoke the CONNECT ON DATABASE Permission from a User?,Account, Password, and Permissions,U", + "title":"How Do I Revoke the CONNECT ON DATABASE Permission from a User?", + "githuburl":"" + }, + { + "uri":"dws_03_0065.html", + "product_code":"dws", + "code":"190", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Database Usage", + "title":"Database Usage", + "githuburl":"" + }, + { + "uri":"dws_03_0075.html", + "product_code":"dws", + "code":"191", + "des":"No, you only need to set the primary key. By default, the first column of the primary key is selected as the distribution key. If both are set, the primary key must conta", + "doc_type":"usermanual", + "kw":"Do I Need to Set a Distribution Key After Setting a Primary Key?,Database Usage,User Guide", + "title":"Do I Need to Set a Distribution Key After Setting a Primary Key?", + "githuburl":"" + }, + { + "uri":"dws_03_0076.html", + "product_code":"dws", + "code":"192", + "des":"Yes.GaussDB(DWS) is compatible with PostgreSQL stored procedures. For details, see \"Stored Procedures\" in the Developer Guide.", + "doc_type":"usermanual", + "kw":"Is GaussDB(DWS) Compatible with PostgreSQL Stored Procedures?,Database Usage,User Guide", + "title":"Is GaussDB(DWS) Compatible with PostgreSQL Stored Procedures?", + "githuburl":"" + }, + { + "uri":"dws_03_0064.html", + "product_code":"dws", + "code":"193", + "des":"Partitioned table: Partitioning refers to splitting what is logically one large table into smaller physical pieces based on specific schemes. The table based on the logic", + "doc_type":"usermanual", + "kw":"What Are Partitioned Tables, Partitions, and Partition Keys?,Database Usage,User Guide", + "title":"What Are Partitioned Tables, Partitions, and Partition Keys?", + "githuburl":"" + }, + { + "uri":"dws_03_0078.html", + "product_code":"dws", + "code":"194", + "des":"You are advised to use the Data Studio graphical client to export table data. You can export data from:A specific tableAll tables in a schemaAll tables in a databaseFor d", + "doc_type":"usermanual", + "kw":"How Can I Export the Table Structure?,Database Usage,User Guide", + "title":"How Can I Export the Table Structure?", + "githuburl":"" + }, + { + "uri":"dws_03_0079.html", + "product_code":"dws", + "code":"195", + "des":"You can use pg_tables and pg_views to query all table information and views in a database. Example:For details about the returned columns, see \"PG_TABLES\" and \"PG_VIEWS\" ", + "doc_type":"usermanual", + "kw":"How Can I Export All Tables and Views from a Database?,Database Usage,User Guide", + "title":"How Can I Export All Tables and Views from a Database?", + "githuburl":"" + }, + { + "uri":"dws_03_0085.html", + "product_code":"dws", + "code":"196", + "des":"In GaussDB(DWS), the encoding format of a database cannot be changed. You need to create another database in the required format. For globalization purposes, set the enco", + "doc_type":"usermanual", + "kw":"How Can I Change the Character Encoding Format of a Database?,Database Usage,User Guide", + "title":"How Can I Change the Character Encoding Format of a Database?", + "githuburl":"" + }, + { + "uri":"dws_03_0088.html", + "product_code":"dws", + "code":"197", + "des":"Yes. TRUNCATE is more efficient than DELETE for deleting massive data.For details, see \"TRUNCATE\" in the Data Warehouse Service (DWS) Developer Guide.TRUNCATE quickly rem", + "doc_type":"usermanual", + "kw":"How Can I Delete Table Data Efficiently?,Database Usage,User Guide", + "title":"How Can I Delete Table Data Efficiently?", + "githuburl":"" + }, + { + "uri":"dws_03_0089.html", + "product_code":"dws", + "code":"198", + "des":"Yes. For tables that involve frequent add, delete, or modify operations, perform VACUUM FULL and ANALYZE to reclaim the disk space occupied by updated or deleted data, pr", + "doc_type":"usermanual", + "kw":"Do I Need to Run VACUUM FULL and ANALYZE on Common Tables Periodically?,Database Usage,User Guide", + "title":"Do I Need to Run VACUUM FULL and ANALYZE on Common Tables Periodically?", + "githuburl":"" + }, + { + "uri":"dws_03_2124.html", + "product_code":"dws", + "code":"199", + "des":"To query information about OBS/GDS foreign tables such as OBS paths, run the following statement:The following uses table traffic_data.GCJL_OBS as an example:", + "doc_type":"usermanual", + "kw":"How Do I View Foreign Table Information?,Database Usage,User Guide", + "title":"How Do I View Foreign Table Information?", + "githuburl":"" + }, + { + "uri":"dws_03_2126.html", + "product_code":"dws", + "code":"200", + "des":"In a data warehouse database, you need to carefully choose distribution columns for large tables, because they can affect your database and query performance. If an impro", + "doc_type":"usermanual", + "kw":"How Do I Change Distribution Columns?,Database Usage,User Guide", + "title":"How Do I Change Distribution Columns?", + "githuburl":"" + }, + { + "uri":"dws_03_0035.html", + "product_code":"dws", + "code":"201", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Database Performance", + "title":"Database Performance", + "githuburl":"" + }, + { + "uri":"dws_03_0071.html", + "product_code":"dws", + "code":"202", + "des":"When a database is used for a period of time, the table data increases as services grow, or the table data is frequently added, deleted, or modified. This results in bloa", + "doc_type":"usermanual", + "kw":"Why Is SQL Execution Slow After Long GaussDB(DWS) Usage?,Database Performance,User Guide", + "title":"Why Is SQL Execution Slow After Long GaussDB(DWS) Usage?", + "githuburl":"" + }, + { + "uri":"dws_03_0036.html", + "product_code":"dws", + "code":"203", + "des":"Due to the MPP architecture limitation of GaussDB(DWS), a few PostgreSQL methods and functions cannot be pushed to DNs for execution. As a result, performance bottlenecks", + "doc_type":"usermanual", + "kw":"Why Does GaussDB(DWS) Perform Worse Than a Single-Server Database in Extreme Scenarios?,Database Per", + "title":"Why Does GaussDB(DWS) Perform Worse Than a Single-Server Database in Extreme Scenarios?", + "githuburl":"" + }, + { + "uri":"dws_03_0100.html", + "product_code":"dws", + "code":"204", + "des":"The top SQL feature lets you view SQL statements executed in a specified period (in real time and historical). SQL statements of the current CN or all CNs are available f", + "doc_type":"usermanual", + "kw":"How Can I View SQL Execution Records of A Certain Period When Service Read and Write Are Blocked?,Da", + "title":"How Can I View SQL Execution Records of A Certain Period When Service Read and Write Are Blocked?", + "githuburl":"" + }, + { + "uri":"dws_03_0068.html", + "product_code":"dws", + "code":"205", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Logs", + "title":"Logs", + "githuburl":"" + }, + { + "uri":"dws_03_0082.html", + "product_code":"dws", + "code":"206", + "des":"GaussDB(DWS) allows you to record the audit logs of specific operations, involving audit log retention policies, unauthorized access, as well as DML, DDL, SELECT and COPY", + "doc_type":"usermanual", + "kw":"How Can I View Database Operation Logs?,Logs,User Guide", + "title":"How Can I View Database Operation Logs?", + "githuburl":"" + }, + { + "uri":"dws_01_0070.html", + "product_code":"dws", + "code":"207", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Change History,User Guide", + "title":"Change History", + "githuburl":"" + } +] \ No newline at end of file diff --git a/docs/dws/umn/CLASS.TXT.json b/docs/dws/umn/CLASS.TXT.json new file mode 100644 index 00000000..b099ceb6 --- /dev/null +++ b/docs/dws/umn/CLASS.TXT.json @@ -0,0 +1,1865 @@ +[ + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Service Overview", + "uri":"dws_01_index.html", + "doc_type":"usermanual", + "p_code":"", + "code":"1" + }, + { + "desc":"GaussDB(DWS) is an online data processing database that runs on the cloud infrastructure to provide scalable, fully-managed, and out-of-the-box analytic database service,", + "product_code":"dws", + "title":"What Is GaussDB(DWS)?", + "uri":"dws_01_0002.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"2" + }, + { + "desc":"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 d", + "product_code":"dws", + "title":"Advantages", + "uri":"dws_01_0007.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"3" + }, + { + "desc":"Enhanced ETL + Real-time BI analysisETL + BI analysisThe data warehouse is the pillar of the Business Intelligence (BI) system for collecting, storing, and analyzing mass", + "product_code":"dws", + "title":"Application Scenarios", + "uri":"dws_01_00013.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"4" + }, + { + "desc":"GaussDB(DWS) enables you to use this service through various methods, such as the GaussDB(DWS) management console, GaussDB(DWS) client, and REST APIs. This section descri", + "product_code":"dws", + "title":"Functions", + "uri":"dws_01_0091.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"5" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Concepts", + "uri":"dws_01_0004.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"6" + }, + { + "desc":"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", + "product_code":"dws", + "title":"GaussDB(DWS) Management Concepts", + "uri":"dws_01_0005.html", + "doc_type":"usermanual", + "p_code":"6", + "code":"7" + }, + { + "desc":"A data warehouse cluster is an analysis-oriented relational database platform that supports online analysis.OLAP is a major function of data warehouse clusters. It suppor", + "product_code":"dws", + "title":"GaussDB(DWS) Database Concepts", + "uri":"dws_01_0006.html", + "doc_type":"usermanual", + "p_code":"6", + "code":"8" + }, + { + "desc":"GaussDB(DWS) uses Identity and Access Management (IAM) for authentication and authorization.Users who have the DWS Administrator permissions can fully utilize GaussDB(DWS", + "product_code":"dws", + "title":"Related Services", + "uri":"dws_01_0003.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"9" + }, + { + "desc":"If you need to assign different permissions to employees in your enterprise to access your cloud GaussDB(DWS) resources, IAM is a good choice for fine-grained permissions", + "product_code":"dws", + "title":"GaussDB(DWS) Permissions Management", + "uri":"dws_01_0144.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"10" + }, + { + "desc":"The following figure shows how to use GaussDB(DWS).GaussDB(DWS) provides a web-based management console and HTTPS-compliant APIs for you to manage data warehouse clusters", + "product_code":"dws", + "title":"GaussDB(DWS) Access", + "uri":"dws_01_0009.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"11" + }, + { + "desc":"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.You cannot c", + "product_code":"dws", + "title":"Restrictions", + "uri":"dws_01_0010.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"12" + }, + { + "desc":"This section describes the technical specifications of GaussDB(DWS) in different versions.", + "product_code":"dws", + "title":"Technical Specifications", + "uri":"dws_01_00113.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"13" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Getting Started", + "uri":"dws_01_0078.html", + "doc_type":"usermanual", + "p_code":"", + "code":"14" + }, + { + "desc":"This guide is an introductory tutorial that demonstrates how to create a sample GaussDB(DWS) cluster, connect to the cluster database, import the sample data from OBS, an", + "product_code":"dws", + "title":"Step 1: Starting Preparations", + "uri":"dws_01_0088.html", + "doc_type":"usermanual", + "p_code":"14", + "code":"15" + }, + { + "desc":"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 ", + "product_code":"dws", + "title":"Step 2: Creating a Cluster", + "uri":"dws_01_0013.html", + "doc_type":"usermanual", + "p_code":"14", + "code":"16" + }, + { + "desc":"This section describes how to use a database client to connect to the database in a GaussDB(DWS) cluster. In the following example, the Data Studio client tool is used fo", + "product_code":"dws", + "title":"Step 3: Connecting to a Cluster", + "uri":"dws_01_0107.html", + "doc_type":"usermanual", + "p_code":"14", + "code":"17" + }, + { + "desc":"After performing the steps in preceding sections, you can refer to the documentation listed as follows for more information about GaussDB(DWS):Data Warehouse Service (DWS", + "product_code":"dws", + "title":"Step 4: Viewing Other Documents and Clearing Resources", + "uri":"dws_01_0079.html", + "doc_type":"usermanual", + "p_code":"14", + "code":"18" + }, + { + "desc":"GaussDB(DWS) is an online data processing database that uses the cloud infrastructure to provide scalable, fully-managed, and out-of-the-box analytic database service, fr", + "product_code":"dws", + "title":"Process for Using GaussDB(DWS)", + "uri":"dws_01_0018.html", + "doc_type":"usermanual", + "p_code":"", + "code":"19" + }, + { + "desc":"Before using GaussDB(DWS), make the following preparations:Registering a Public Cloud Account and Completing Real-Name AuthenticationDetermining the Cluster PortsIf you d", + "product_code":"dws", + "title":"Preparations", + "uri":"dws_01_0154.html", + "doc_type":"usermanual", + "p_code":"", + "code":"20" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Cluster Configuration", + "uri":"dws_01_0160.html", + "doc_type":"usermanual", + "p_code":"", + "code":"21" + }, + { + "desc":"This section describes how to log in to the GaussDB(DWS) management console and use GaussDB(DWS).", + "product_code":"dws", + "title":"Accessing the GaussDB(DWS) Management Console", + "uri":"dws_01_0157.html", + "doc_type":"usermanual", + "p_code":"21", + "code":"22" + }, + { + "desc":"To use cloud GaussDB(DWS), create a cluster first.This section describes how to create a data warehouse cluster on the GaussDB(DWS) management console.You have evaluated ", + "product_code":"dws", + "title":"Creating a Cluster", + "uri":"dws_01_0019.html", + "doc_type":"usermanual", + "p_code":"21", + "code":"23" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Cluster Connection", + "uri":"dws_01_0131.html", + "doc_type":"usermanual", + "p_code":"", + "code":"24" + }, + { + "desc":"If you have created a GaussDB(DWS) cluster, you can use the SQL client tool or a third-party driver such as JDBC or ODBC to connect to the cluster and access the database", + "product_code":"dws", + "title":"Methods of Connecting to a Cluster", + "uri":"dws_01_0137.html", + "doc_type":"usermanual", + "p_code":"24", + "code":"25" + }, + { + "desc":"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 p", + "product_code":"dws", + "title":"Obtaining the Cluster Connection Address", + "uri":"dws_01_0033.html", + "doc_type":"usermanual", + "p_code":"24", + "code":"26" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Using the gsql CLI Client to Connect to a Cluster", + "uri":"dws_01_0093.html", + "doc_type":"usermanual", + "p_code":"24", + "code":"27" + }, + { + "desc":"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.The cl", + "product_code":"dws", + "title":"Downloading the Client", + "uri":"dws_01_0031.html", + "doc_type":"usermanual", + "p_code":"27", + "code":"28" + }, + { + "desc":"The gsql command line client provided by GaussDB(DWS) runs on the Linux OS. Before using it to remotely connect to a GaussDB(DWS) cluster, you need to prepare a Linux hos", + "product_code":"dws", + "title":"Preparing an ECS as the gsql Client Host", + "uri":"dws_01_0128.html", + "doc_type":"usermanual", + "p_code":"27", + "code":"29" + }, + { + "desc":"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", + "product_code":"dws", + "title":"Using the gsql Client to Connect to a Cluster", + "uri":"dws_01_0037.html", + "doc_type":"usermanual", + "p_code":"27", + "code":"30" + }, + { + "desc":"If the client or JDBC/ODBC driver needs to use SSL connection, you must configure related SSL connection parameters in the client or application code. The GaussDB(DWS) ma", + "product_code":"dws", + "title":"Establishing Secure TCP/IP Connections in SSL Mode", + "uri":"dws_01_0038.html", + "doc_type":"usermanual", + "p_code":"27", + "code":"31" + }, + { + "desc":"GaussDB(DWS) supports connections in SSL authentication mode so that data transmitted between the GaussDB(DWS) client and the database can be encrypted. The SSL mode deli", + "product_code":"dws", + "title":"(Optional) Configuring SSL Connection", + "uri":"dws_01_0076.html", + "doc_type":"usermanual", + "p_code":"27", + "code":"32" + }, + { + "desc":"GaussDB(DWS) supports the standard SSL (TLS 1.2). As a highly secure protocol, SSL authenticates bidirectional identification between the server and client using digital ", + "product_code":"dws", + "title":"(Optional) Downloading the SSL Certificate", + "uri":"dws_01_0083.html", + "doc_type":"usermanual", + "p_code":"27", + "code":"33" + }, + { + "desc":"Data Studio is a SQL client tool running on the Windows operating system. It provides various GUIs for you to manage databases and database objects, as well as edit, run,", + "product_code":"dws", + "title":"Using the Data Studio GUI Client to Connect to a Cluster", + "uri":"dws_01_0094.html", + "doc_type":"usermanual", + "p_code":"24", + "code":"34" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Using the JDBC and ODBC Drivers to Connect to a Cluster", + "uri":"dws_01_0081.html", + "doc_type":"usermanual", + "p_code":"24", + "code":"35" + }, + { + "desc":"If the connection pool mechanism is used during application development, the following specifications must be met. Otherwise, connections in the connection pool have stat", + "product_code":"dws", + "title":"Development Specifications", + "uri":"dws_01_0106.html", + "doc_type":"usermanual", + "p_code":"35", + "code":"36" + }, + { + "desc":"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 us", + "product_code":"dws", + "title":"Downloading the JDBC or ODBC Driver", + "uri":"dws_01_0032.html", + "doc_type":"usermanual", + "p_code":"35", + "code":"37" + }, + { + "desc":"In GaussDB(DWS), you can use a JDBC driver to connect to a database on Linux or Windows. The driver can connect to the database through an ECS on the cloud platform or ov", + "product_code":"dws", + "title":"Using a JDBC Driver to Connect to a Database", + "uri":"dws_01_0077.html", + "doc_type":"usermanual", + "p_code":"35", + "code":"38" + }, + { + "desc":"GaussDB(DWS) allows you to use an ODBC driver to connect to the database through an ECS on the cloud platform or over the Internet.For details about how to use the ODBC A", + "product_code":"dws", + "title":"Using an ODBC Driver to Connect to a Database", + "uri":"dws_01_0086.html", + "doc_type":"usermanual", + "p_code":"35", + "code":"39" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Connecting to a Cluster Using IAM Authentication", + "uri":"dws_01_0133.html", + "doc_type":"usermanual", + "p_code":"35", + "code":"40" + }, + { + "desc":"GaussDB(DWS) allows you to access databases using IAM authentication. When you use the JDBC application program to connect to a cluster, set the IAM username, credential,", + "product_code":"dws", + "title":"Overview", + "uri":"dws_01_0134.html", + "doc_type":"usermanual", + "p_code":"40", + "code":"41" + }, + { + "desc":"The IAM account you use to access a database must be granted with the DWS Database Access permission. Only users with both the DWS Administrator and DWS Database Access p", + "product_code":"dws", + "title":"Granting an IAM Account the DWS Database Access Permission", + "uri":"dws_01_0135.html", + "doc_type":"usermanual", + "p_code":"40", + "code":"42" + }, + { + "desc":"You can log in to the management console to create an AK/SK pair or use an existing one.Log in to the management console, move your cursor over your account in the upper ", + "product_code":"dws", + "title":"Creating an IAM User Credential", + "uri":"dws_01_0136.html", + "doc_type":"usermanual", + "p_code":"40", + "code":"43" + }, + { + "desc":"When you use the JDBC application program to connect to a cluster, set the IAM username, credential, and other information as you configure the JDBC URL. After doing this", + "product_code":"dws", + "title":"Configuring the JDBC Connection to Connect to a Cluster Using IAM Authentication", + "uri":"dws_01_0132.html", + "doc_type":"usermanual", + "p_code":"40", + "code":"44" + }, + { + "desc":"By default, a database supports a certain number of connections. Administrators can manage database connections to learn about the connection performance of the current d", + "product_code":"dws", + "title":"Managing Database Connections", + "uri":"dws_01_0039.html", + "doc_type":"usermanual", + "p_code":"24", + "code":"45" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Clusters", + "uri":"dws_01_0600.html", + "doc_type":"usermanual", + "p_code":"", + "code":"46" + }, + { + "desc":"On the Clusters page of the GaussDB(DWS) management console, you can view the general information about a cluster in the cluster list, such as the cluster status, task in", + "product_code":"dws", + "title":"Checking the Cluster Status", + "uri":"dws_01_0020.html", + "doc_type":"usermanual", + "p_code":"46", + "code":"47" + }, + { + "desc":"Log in to the GaussDB(DWS) management console. In the navigation tree on the left, choose Clusters. In the cluster list, locate the required cluster and click its name. T", + "product_code":"dws", + "title":"Viewing Basic Cluster Information", + "uri":"dws_01_0112.html", + "doc_type":"usermanual", + "p_code":"46", + "code":"48" + }, + { + "desc":"A domain name is a string of characters separated by dots to identify the location of a computer or a computer group on the Internet, for example, www.example.com. You ca", + "product_code":"dws", + "title":"Managing Access Domain Names", + "uri":"dws_01_0140.html", + "doc_type":"usermanual", + "p_code":"46", + "code":"49" + }, + { + "desc":"On the Nodes tab page, you can view the node list of the current cluster, add new nodes to or remove nodes from it, and view the node usage, status, and flavors.This feat", + "product_code":"dws", + "title":"Nodes", + "uri":"dws_01_0818.html", + "doc_type":"usermanual", + "p_code":"46", + "code":"50" + }, + { + "desc":"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 storag", + "product_code":"dws", + "title":"Cluster Scale-out", + "uri":"dws_01_0023.html", + "doc_type":"usermanual", + "p_code":"46", + "code":"51" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Cluster Redistribution", + "uri":"dws_01_0820.html", + "doc_type":"usermanual", + "p_code":"46", + "code":"52" + }, + { + "desc":"Data redistribution, where data in existing nodes is evenly allocated to the new nodes after you scale out a cluster, is a time-consuming yet crucial task that accelerate", + "product_code":"dws", + "title":"Redistributing Data", + "uri":"dws_01_8201.html", + "doc_type":"usermanual", + "p_code":"52", + "code":"53" + }, + { + "desc":"On the View Redistribution Details page, you can view the redistribution mode and progress of the current cluster. In offline scheduling mode, you can pause, resume, and ", + "product_code":"dws", + "title":"Viewing Redistribution Details", + "uri":"dws_01_8202.html", + "doc_type":"usermanual", + "p_code":"52", + "code":"54" + }, + { + "desc":"In the Unbalanced state, the number of primary instances on some nodes increases. As a result, the load pressure is high. In this case, the cluster is normal, but the ove", + "product_code":"dws", + "title":"Performing a Primary/Standby Switchback", + "uri":"dws_01_8115.html", + "doc_type":"usermanual", + "p_code":"46", + "code":"55" + }, + { + "desc":"After you create a data warehouse cluster, the system automatically configures a random maintenance window for the cluster. Alternatively, you can customize a maintenance", + "product_code":"dws", + "title":"Cluster Upgrade", + "uri":"dws_01_0008.html", + "doc_type":"usermanual", + "p_code":"46", + "code":"56" + }, + { + "desc":"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 numbe", + "product_code":"dws", + "title":"Password Reset", + "uri":"dws_01_0026.html", + "doc_type":"usermanual", + "p_code":"46", + "code":"57" + }, + { + "desc":"If a cluster is in the Unbalanced state or cannot work properly, you may need to restart it for restoration. After modifying a cluster's configurations, such as security ", + "product_code":"dws", + "title":"Cluster Restart", + "uri":"dws_01_0024.html", + "doc_type":"usermanual", + "p_code":"46", + "code":"58" + }, + { + "desc":"After a cluster is created, you can modify the cluster's database parameters as required. On the GaussDB(DWS) management console, you can view or set common database para", + "product_code":"dws", + "title":"Modifying Database Parameters", + "uri":"dws_01_0152.html", + "doc_type":"usermanual", + "p_code":"46", + "code":"59" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"MRS Data Sources", + "uri":"dws_01_0057.html", + "doc_type":"usermanual", + "p_code":"46", + "code":"60" + }, + { + "desc":"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 v", + "product_code":"dws", + "title":"Importing Data from MRS to GaussDB(DWS)", + "uri":"dws_01_0055.html", + "doc_type":"usermanual", + "p_code":"60", + "code":"61" + }, + { + "desc":"Before GaussDB(DWS) reads data from MRS HDFS, you need to create an MRS data source connection that functions as a channel of transporting data warehouse cluster data and", + "product_code":"dws", + "title":"Creating an MRS Data Source Connection", + "uri":"dws_01_0059.html", + "doc_type":"usermanual", + "p_code":"60", + "code":"62" + }, + { + "desc":"For MRS, if the following parameter configurations of the HDFS cluster change, data may fail to be imported to the data warehouse cluster from the HDFS cluster. Before im", + "product_code":"dws", + "title":"Updating the MRS Data Source Configuration", + "uri":"dws_01_0156.html", + "doc_type":"usermanual", + "p_code":"60", + "code":"63" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Managing Cluster Workloads", + "uri":"dws_01_0723.html", + "doc_type":"usermanual", + "p_code":"46", + "code":"64" + }, + { + "desc":"When multiple database users query jobs at the same time, some complex queries may occupy cluster resources for a long time, affecting the performance of other queries. F", + "product_code":"dws", + "title":"Workload Management Overview", + "uri":"dws_01_07231.html", + "doc_type":"usermanual", + "p_code":"64", + "code":"65" + }, + { + "desc":"You can create a maximum of 63 workload queues.", + "product_code":"dws", + "title":"Adding Workload Queues", + "uri":"dws_01_07233.html", + "doc_type":"usermanual", + "p_code":"64", + "code":"66" + }, + { + "desc":"You can modify the parameters of a workload queue.Click Edit on the right and modify the parameters according to Table 1.Workload queue parametersParameterDescriptionValu", + "product_code":"dws", + "title":"Modifying Workload Queues", + "uri":"dws_01_07234.html", + "doc_type":"usermanual", + "p_code":"64", + "code":"67" + }, + { + "desc":"In the Query Overview area, you can view the number of long and short queries that are running in the current queue at the current time. The chart information is refreshe", + "product_code":"dws", + "title":"Workload Queue Query", + "uri":"dws_01_07238.html", + "doc_type":"usermanual", + "p_code":"64", + "code":"68" + }, + { + "desc":"If the queue to be deleted has associated database users, these users will be associated with the default queue after the queue is deleted.", + "product_code":"dws", + "title":"Deleting Workload Queues", + "uri":"dws_01_07239.html", + "doc_type":"usermanual", + "p_code":"64", + "code":"69" + }, + { + "desc":"Workload plan is an advanced workload management feature provided by GaussDB(DWS). You can create a workload plan, add multiple stages to the plan, and configure differen", + "product_code":"dws", + "title":"Workload Plans", + "uri":"dws_01_72362.html", + "doc_type":"usermanual", + "p_code":"64", + "code":"70" + }, + { + "desc":"You must stop the workload plan when adding a stage. Otherwise, the stage cannot be added.You can add a maximum of 48 stages for each plan.The switchover time of all phas", + "product_code":"dws", + "title":"Stages of Workload Plans", + "uri":"dws_01_72363.html", + "doc_type":"usermanual", + "p_code":"64", + "code":"71" + }, + { + "desc":"You can commission a workload plan in the test environment and export the plan configurations to the production environment.An ongoing workload plan cannot be imported.Be", + "product_code":"dws", + "title":"Importing and Exporting Workload Plans", + "uri":"dws_01_72365.html", + "doc_type":"usermanual", + "p_code":"64", + "code":"72" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Managing Logical Clusters", + "uri":"dws_01_0724.html", + "doc_type":"usermanual", + "p_code":"46", + "code":"73" + }, + { + "desc":"A physical cluster can be divided into logical clusters that use the node-group mechanism. Tables in a database can be allocated to different physical nodes by logical cl", + "product_code":"dws", + "title":"Overview", + "uri":"dws_01_7241.html", + "doc_type":"usermanual", + "p_code":"73", + "code":"74" + }, + { + "desc":"If you access the Logical Clusters page for the first time, the metadata of the logical cluster created at the backend is synchronized to the frontend. After the synchron", + "product_code":"dws", + "title":"Adding Logical Clusters", + "uri":"dws_01_7242.html", + "doc_type":"usermanual", + "p_code":"73", + "code":"75" + }, + { + "desc":"Nodes are added to or removed from a logical cluster by ring.At least one ring must be reserved in a logical cluster.The ring removed from the logical cluster will be add", + "product_code":"dws", + "title":"Editing Logical Clusters", + "uri":"dws_01_7243.html", + "doc_type":"usermanual", + "p_code":"73", + "code":"76" + }, + { + "desc":"The first added logical cluster cannot be deleted.Nodes of the deleted logical cluster are added to the elastic cluster.", + "product_code":"dws", + "title":"Deleting Logical Clusters", + "uri":"dws_01_7244.html", + "doc_type":"usermanual", + "p_code":"73", + "code":"77" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Restarting Logical Clusters", + "uri":"dws_01_7245.html", + "doc_type":"usermanual", + "p_code":"73", + "code":"78" + }, + { + "desc":"Logical clusters and elastic clusters cannot be scaled out online.", + "product_code":"dws", + "title":"Scaling Out Logical Clusters", + "uri":"dws_01_7246.html", + "doc_type":"usermanual", + "p_code":"73", + "code":"79" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Managing Tags", + "uri":"dws_01_0103.html", + "doc_type":"usermanual", + "p_code":"46", + "code":"80" + }, + { + "desc":"A tag is a key-value pair customized by users and used to identify cloud resources. It helps users to classify and search for cloud resources.Tags are composed of key-val", + "product_code":"dws", + "title":"Overview", + "uri":"dws_01_0104.html", + "doc_type":"usermanual", + "p_code":"80", + "code":"81" + }, + { + "desc":"This section describes how to search for clusters based on tags and how to add, modify, and delete tags for clusters.You can quickly locate a tagged cluster using tags.Yo", + "product_code":"dws", + "title":"Tag Management", + "uri":"dws_01_0105.html", + "doc_type":"usermanual", + "p_code":"80", + "code":"82" + }, + { + "desc":"An enterprise project is a cloud resource management mode. Enterprise Management provides users with comprehensive management in cloud-based resources, personnel, and per", + "product_code":"dws", + "title":"Managing Enterprise Projects", + "uri":"dws_01_0113.html", + "doc_type":"usermanual", + "p_code":"46", + "code":"83" + }, + { + "desc":"If you do not need to use a cluster, perform the operations in this section to delete it.Deleted clusters cannot be recovered. Additionally, you cannot access user data a", + "product_code":"dws", + "title":"Deleting Clusters", + "uri":"dws_01_0025.html", + "doc_type":"usermanual", + "p_code":"46", + "code":"84" + }, + { + "desc":"To facilitate database parameter configuration, GaussDB(DWS) provides the parameter template function. A parameter template contains some common database parameters. You ", + "product_code":"dws", + "title":"Managing Parameter Templates", + "uri":"dws_01_0126.html", + "doc_type":"usermanual", + "p_code":"46", + "code":"85" + }, + { + "desc":"If a cluster fails to be created, you can go to the Clusters page of the GaussDB(DWS) management console to view the cluster status and the cause of failure.For details a", + "product_code":"dws", + "title":"Managing Clusters That Fail to Be Created", + "uri":"dws_01_0073.html", + "doc_type":"usermanual", + "p_code":"46", + "code":"86" + }, + { + "desc":"No database operation is allowed on a read-only cluster. Cancel the read-only status on the management console.You can cancel the read-only status only when a cluster is ", + "product_code":"dws", + "title":"Read-only Status", + "uri":"dws_01_0035.html", + "doc_type":"usermanual", + "p_code":"46", + "code":"87" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Cluster HA", + "uri":"dws_01_0161.html", + "doc_type":"usermanual", + "p_code":"", + "code":"88" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Snapshots", + "uri":"dws_01_0800.html", + "doc_type":"usermanual", + "p_code":"88", + "code":"89" + }, + { + "desc":"A snapshot is a full or incremental backup of a GaussDB(DWS) cluster at a specific point in time. It records the current database data and cluster information, including ", + "product_code":"dws", + "title":"Overview", + "uri":"dws_01_0151.html", + "doc_type":"usermanual", + "p_code":"89", + "code":"90" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Manual Snapshots", + "uri":"dws_01_0092.html", + "doc_type":"usermanual", + "p_code":"89", + "code":"91" + }, + { + "desc":"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 ", + "product_code":"dws", + "title":"Manually Creating a Snapshot", + "uri":"dws_01_0028.html", + "doc_type":"usermanual", + "p_code":"91", + "code":"92" + }, + { + "desc":"On the Snapshots page, you can delete a snapshot in the Unavailable state or delete an available snapshot to release the storage space.Deleted snapshots cannot be restore", + "product_code":"dws", + "title":"Deleting Manual Snapshots", + "uri":"dws_01_0030.html", + "doc_type":"usermanual", + "p_code":"91", + "code":"93" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Automated Snapshots", + "uri":"dws_01_1013.html", + "doc_type":"usermanual", + "p_code":"89", + "code":"94" + }, + { + "desc":"Automated snapshots adopt differential incremental backups. The automated snapshot created for the first time is a full backup (base version), and then the system creates", + "product_code":"dws", + "title":"Automated Snapshot Overview", + "uri":"dws_01_10131.html", + "doc_type":"usermanual", + "p_code":"94", + "code":"95" + }, + { + "desc":"You can select a snapshot type and set one or more automated snapshot policies for a cluster. After an automated snapshot policy is enabled, the system automatically crea", + "product_code":"dws", + "title":"Configuring an Automated Snapshot Policy", + "uri":"dws_01_0089.html", + "doc_type":"usermanual", + "p_code":"94", + "code":"96" + }, + { + "desc":"This section describes how to copy snapshots that are automatically created for long-term retention.All snapshots are displayed by default. You can copy the snapshots tha", + "product_code":"dws", + "title":"Copying Automated Snapshots", + "uri":"dws_01_0085.html", + "doc_type":"usermanual", + "p_code":"94", + "code":"97" + }, + { + "desc":"Only GaussDB(DWS) can delete automated snapshots. You cannot delete them manually.GaussDB(DWS) deletes an automated snapshot if:The retention period of the snapshot ends.", + "product_code":"dws", + "title":"Deleting an Automated Snapshot", + "uri":"dws_01_10134.html", + "doc_type":"usermanual", + "p_code":"94", + "code":"98" + }, + { + "desc":"This section describes how to view snapshot information on the Snapshots page.In the snapshot list, all snapshots are displayed by default. Click next to the snapshot na", + "product_code":"dws", + "title":"Viewing Snapshot Information", + "uri":"dws_01_0021.html", + "doc_type":"usermanual", + "p_code":"89", + "code":"99" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Restoration Using a Snapshot", + "uri":"dws_01_1015.html", + "doc_type":"usermanual", + "p_code":"89", + "code":"100" + }, + { + "desc":"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.When a snapshot is restored to a new c", + "product_code":"dws", + "title":"Restoring a Snapshot to a New Cluster", + "uri":"dws_01_0029.html", + "doc_type":"usermanual", + "p_code":"100", + "code":"101" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Cluster DR", + "uri":"dws_01_0080.html", + "doc_type":"usermanual", + "p_code":"88", + "code":"102" + }, + { + "desc":"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 specif", + "product_code":"dws", + "title":"DR Overview", + "uri":"dws_01_00081.html", + "doc_type":"usermanual", + "p_code":"102", + "code":"103" + }, + { + "desc":"You can create a DR task only when the cluster is in the Available or Unbalanced state.Type: Cross-AZ DRName: Enter 4 to 64 case-insensitive characters, starting with a l", + "product_code":"dws", + "title":"Creating a DR Task", + "uri":"dws_01_00082.html", + "doc_type":"usermanual", + "p_code":"102", + "code":"104" + }, + { + "desc":"On the page that is displayed, view the following information:DR Information: You can view the DR ID, DR name, DR creation time, and DR status.Production Cluster Informat", + "product_code":"dws", + "title":"Viewing DR Information", + "uri":"dws_01_00083.html", + "doc_type":"usermanual", + "p_code":"102", + "code":"105" + }, + { + "desc":"The DR status will change to Starting. The process will take some time. After the task is started, the DR status will change to Running.You can start a DR task that is in", + "product_code":"dws", + "title":"DR Management", + "uri":"dws_01_00084.html", + "doc_type":"usermanual", + "p_code":"102", + "code":"106" + }, + { + "desc":"After scale-out, the number of DNs in the production cluster must be the same as that in the DR cluster.", + "product_code":"dws", + "title":"Mutually Exclusive DR Cases", + "uri":"dws_01_00085.html", + "doc_type":"usermanual", + "p_code":"102", + "code":"107" + }, + { + "desc":"If the internal IP address or EIP of a CN is used to connect to a cluster, the failure of this CN will lead to cluster connection failure. If a private domain name is use", + "product_code":"dws", + "title":"Associating and Disassociating ELB", + "uri":"dws_01_0822.html", + "doc_type":"usermanual", + "p_code":"88", + "code":"108" + }, + { + "desc":"After a cluster is created, the number of required CNs varies with service requirements. The CN management function enables you to adjust the number of CNs in the cluster", + "product_code":"dws", + "title":"CNs", + "uri":"dws_01_7115.html", + "doc_type":"usermanual", + "p_code":"88", + "code":"109" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Monitoring and Alarms", + "uri":"dws_01_0162.html", + "doc_type":"usermanual", + "p_code":"", + "code":"110" + }, + { + "desc":"This section describes how to check cluster metrics on Cloud Eye. By monitoring cluster running metrics, you can identify the time when the database cluster is abnormal a", + "product_code":"dws", + "title":"Monitoring Clusters Using Cloud Eye", + "uri":"dws_01_0022.html", + "doc_type":"usermanual", + "p_code":"110", + "code":"111" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Databases Monitoring", + "uri":"dws_01_00014.html", + "doc_type":"usermanual", + "p_code":"110", + "code":"112" + }, + { + "desc":"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 ", + "product_code":"dws", + "title":"Database Monitoring Overview", + "uri":"dws_01_00131.html", + "doc_type":"usermanual", + "p_code":"112", + "code":"113" + }, + { + "desc":"You can check the status and available resources of a cluster and learn about its real-time resource consumption through the GaussDB(DWS) monitoring items.Table 1 describ", + "product_code":"dws", + "title":"Monitoring Metrics", + "uri":"dws_01_00136.html", + "doc_type":"usermanual", + "p_code":"112", + "code":"114" + }, + { + "desc":"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", + "product_code":"dws", + "title":"Cluster Overview", + "uri":"dws_01_00132.html", + "doc_type":"usermanual", + "p_code":"112", + "code":"115" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Monitoring", + "uri":"dws_01_00133.html", + "doc_type":"usermanual", + "p_code":"112", + "code":"116" + }, + { + "desc":"On the page that is displayed, view the real-time consumption of nodes, memory, disks, disk I/O, and network I/O.On the Overview tab page, you can view the key resources ", + "product_code":"dws", + "title":"Node Monitoring", + "uri":"dws_01_1331.html", + "doc_type":"usermanual", + "p_code":"116", + "code":"117" + }, + { + "desc":"The Performance Monitoring page displays the resource consumption trends of clusters and databases.You can configure monitoring views by customizing monitoring panels. Mo", + "product_code":"dws", + "title":"Performance Monitoring", + "uri":"dws_01_1337.html", + "doc_type":"usermanual", + "p_code":"116", + "code":"118" + }, + { + "desc":"The Database Monitoring page displays the real-time and historical resource consumption a database.You can select a database and check its resource usage. For details, se", + "product_code":"dws", + "title":"Database Monitoring", + "uri":"dws_01_1332.html", + "doc_type":"usermanual", + "p_code":"116", + "code":"119" + }, + { + "desc":"The Session Monitoring page displays the session-level real-time database query statistics. You can also select and terminate a session.You can browse the query statistic", + "product_code":"dws", + "title":"Session Monitoring", + "uri":"dws_01_1333.html", + "doc_type":"usermanual", + "p_code":"116", + "code":"120" + }, + { + "desc":"The Query Monitoring page displays the real-time information about all queries that are running in a cluster and the historical information about the queries that have be", + "product_code":"dws", + "title":"Query Monitoring", + "uri":"dws_01_1334.html", + "doc_type":"usermanual", + "p_code":"116", + "code":"121" + }, + { + "desc":"On the Instance Monitoring page, you can view the real-time and historical information about detected slow instances.DMS can automatically configure and start the slow in", + "product_code":"dws", + "title":"Instance Monitoring", + "uri":"dws_01_1338.html", + "doc_type":"usermanual", + "p_code":"116", + "code":"122" + }, + { + "desc":"On the Load Monitoring page, you can view the real-time and historical resource consumption of workload queues.The DMS displays the user-defined workload queue name, real", + "product_code":"dws", + "title":"Load Monitoring", + "uri":"dws_01_1339.html", + "doc_type":"usermanual", + "p_code":"116", + "code":"123" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Utilities", + "uri":"dws_01_00175.html", + "doc_type":"usermanual", + "p_code":"112", + "code":"124" + }, + { + "desc":"To enable SQL diagnosis, enable monitoring on real-time and historical queries on the Queries and History tabs, respectively. For details, see .Query IDDatabaseSchema Nam", + "product_code":"dws", + "title":"SQL Diagnosis", + "uri":"dws_01_00134.html", + "doc_type":"usermanual", + "p_code":"124", + "code":"125" + }, + { + "desc":"You can audit DDL to check DDL metadata, identify inappropriate table definitions, and locate performance problems.This feature is supported only in cluster version 8.1.2", + "product_code":"dws", + "title":"DDL Audit", + "uri":"dws_01_01752.html", + "doc_type":"usermanual", + "p_code":"124", + "code":"126" + }, + { + "desc":"The Monitoring page displays the collection period and data aging period of monitoring metrics.The cluster monitoring function is enabled by default.Disable the function ", + "product_code":"dws", + "title":"Settings", + "uri":"dws_01_00135.html", + "doc_type":"usermanual", + "p_code":"112", + "code":"127" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Typical Scenarios", + "uri":"dws_01_00137.html", + "doc_type":"usermanual", + "p_code":"112", + "code":"128" + }, + { + "desc":"The execution of SQL statements takes a long time, resulting in great resource consumption.If the execution efficiency of SQL statements is low, optimization suggestions ", + "product_code":"dws", + "title":"SQL Diagnosis", + "uri":"dws_01_01372.html", + "doc_type":"usermanual", + "p_code":"128", + "code":"129" + }, + { + "desc":"Time-consuming SQL statements exist.On the Top 5 Time-Consuming Queries page directed from the Cluster Overview page, record the change of top 5 time-consuming queries.An", + "product_code":"dws", + "title":"Top Time-Consuming SQL Statements Viewing", + "uri":"dws_01_01373.html", + "doc_type":"usermanual", + "p_code":"128", + "code":"130" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Alarms", + "uri":"dws_01_1240.html", + "doc_type":"usermanual", + "p_code":"110", + "code":"131" + }, + { + "desc":"Alarm management includes viewing and configuring alarm rules and subscribing to alarm information. Alarm rules display alarm statistics and details of the past week for ", + "product_code":"dws", + "title":"Alarm Management", + "uri":"dws_01_1241.html", + "doc_type":"usermanual", + "p_code":"131", + "code":"132" + }, + { + "desc":"Concepts related to threshold alarmsAlarm rule: consists of the alarm rule name, rule description, clusters associated with the rule, alarm policy triggering relationship", + "product_code":"dws", + "title":"Alarm Rules", + "uri":"dws_01_1242.html", + "doc_type":"usermanual", + "p_code":"131", + "code":"133" + }, + { + "desc":"You can subscribe to GaussDB(DWS) alarm notifications to receive notifications by SMS message, email, or application when an alarm of a specified severity is generated.To", + "product_code":"dws", + "title":"Alarm Subscriptions", + "uri":"dws_01_1243.html", + "doc_type":"usermanual", + "p_code":"131", + "code":"134" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Cluster Security Management", + "uri":"dws_01_0700.html", + "doc_type":"usermanual", + "p_code":"", + "code":"135" + }, + { + "desc":"By default, the administrator specified when you create a GaussDB(DWS) cluster is the database system administrator. The administrator can create other users and view the", + "product_code":"dws", + "title":"Configuring Separation of Permissions", + "uri":"dws_01_0074.html", + "doc_type":"usermanual", + "p_code":"135", + "code":"136" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Permissions", + "uri":"dws_01_0145.html", + "doc_type":"usermanual", + "p_code":"135", + "code":"137" + }, + { + "desc":"An RBAC policy consists of a Version, a Statement, and Depends.When selecting a policy for a user group, click below the policy to view the details of the policy. The DW", + "product_code":"dws", + "title":"RBAC Syntax of RBAC Policies", + "uri":"dws_01_0150.html", + "doc_type":"usermanual", + "p_code":"137", + "code":"138" + }, + { + "desc":"GaussDB(DWS) protects mission-critical operations. If you want to perform a mission-critical operation on the management console, you must enter a credential for identity", + "product_code":"dws", + "title":"Protection for Mission-Critical Operations", + "uri":"dws_01_0701.html", + "doc_type":"usermanual", + "p_code":"135", + "code":"139" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Audit Logs", + "uri":"dws_01_0119.html", + "doc_type":"usermanual", + "p_code":"", + "code":"140" + }, + { + "desc":"Tenant database audit logs:GaussDB(DWS) allows you to record the audit logs of specific operations, involving audit log retention policies, unauthorized access, as well a", + "product_code":"dws", + "title":"Overview", + "uri":"dws_01_1911.html", + "doc_type":"usermanual", + "p_code":"140", + "code":"141" + }, + { + "desc":"This section is organized as follows:Enabling CTSDisabling the Audit Log FunctionKey OperationsViewing TracesA tracker will be automatically created after CTS is enabled.", + "product_code":"dws", + "title":"Viewing Audit Logs of Key Operations on the Management Console", + "uri":"dws_01_0118.html", + "doc_type":"usermanual", + "p_code":"140", + "code":"142" + }, + { + "desc":"Database audit logs are configured on the Security Settings page. You can change security settings only when the cluster status is Available and Unbalanced, and Task Info", + "product_code":"dws", + "title":"Configuring the Database Audit Logs", + "uri":"dws_01_0075.html", + "doc_type":"usermanual", + "p_code":"140", + "code":"143" + }, + { + "desc":"GaussDB(DWS) records information (audit logs) about connections and user activities in your database. With the information, you can monitor the database to ensure securit", + "product_code":"dws", + "title":"Dumping the Database Audit Logs", + "uri":"dws_01_0142.html", + "doc_type":"usermanual", + "p_code":"140", + "code":"144" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"FAQs", + "uri":"dws_03_0061.html", + "doc_type":"usermanual", + "p_code":"", + "code":"145" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"General Problems", + "uri":"dws_03_0001.html", + "doc_type":"usermanual", + "p_code":"145", + "code":"146" + }, + { + "desc":"Much data (orders, stocks, materials, and payments) is generated in the business operation systems and background (transactional) database of enterprises.Decision makers ", + "product_code":"dws", + "title":"Why Are Data Warehouses Necessary?", + "uri":"dws_03_0003.html", + "doc_type":"usermanual", + "p_code":"146", + "code":"147" + }, + { + "desc":"The Hadoop big data platform can be regarded as a next-generation data warehousing system. It has the characteristics of modern data warehouses and is widely used by ente", + "product_code":"dws", + "title":"What Are the Differences Between a Data Warehouse and the Hadoop Big Data Platform?", + "uri":"dws_03_0005.html", + "doc_type":"usermanual", + "p_code":"146", + "code":"148" + }, + { + "desc":"Conventional data warehouses are not practical for smaller enterprises due to high cost, time-consuming device and system selection and procurement, and complex scale-out", + "product_code":"dws", + "title":"Why Should I Use Public Cloud GaussDB(DWS)?", + "uri":"dws_03_0006.html", + "doc_type":"usermanual", + "p_code":"146", + "code":"149" + }, + { + "desc":"Both allow you to run conventional relational databases on the cloud and transfer database management loads. RDS databases are useful for OLTP, reporting, and analysis, b", + "product_code":"dws", + "title":"Should I Choose Public Cloud GaussDB(DWS) or RDS?", + "uri":"dws_03_0009.html", + "doc_type":"usermanual", + "p_code":"146", + "code":"150" + }, + { + "desc":"MRS works better with big data processing frameworks such as Apache Spark, Hadoop, and HBase, to process and analyze ultra-large data sets through custom code. It allows ", + "product_code":"dws", + "title":"When Should I Use GaussDB(DWS) and MRS?", + "uri":"dws_03_0010.html", + "doc_type":"usermanual", + "p_code":"146", + "code":"151" + }, + { + "desc":"No. Although SQL on OBS of GaussDB(DWS) can be used for GaussDB(DWS) and OBS data query, it cannot replace the processing frameworks of MRS.Apart from SQL query, MRS also", + "product_code":"dws", + "title":"Can GaussDB(DWS) SQL on OBS Replace MRS?", + "uri":"dws_03_0011.html", + "doc_type":"usermanual", + "p_code":"146", + "code":"152" + }, + { + "desc":"GaussDB(DWS) and Hive have different functions in the following aspects:Hive is a data warehouse based on Hadoop MapReduce. GaussDB(DWS) is a data warehouse based on Post", + "product_code":"dws", + "title":"What Are the Differences Between GaussDB(DWS) and Hive in Functions?", + "uri":"dws_03_0037.html", + "doc_type":"usermanual", + "p_code":"146", + "code":"153" + }, + { + "desc":"For cloud services, quotas limit the number of resources available to users. If you need more, submit a service ticket to increase your quotas. Once approved, we will upd", + "product_code":"dws", + "title":"What Is the User Quota?", + "uri":"dws_03_0034.html", + "doc_type":"usermanual", + "p_code":"146", + "code":"154" + }, + { + "desc":"Users and roles are shared within the entire cluster, but their data is not shared. That is, a user can connect to any database, but after the connection is successful, a", + "product_code":"dws", + "title":"What Are the Differences Between Users and Roles?", + "uri":"dws_03_0067.html", + "doc_type":"usermanual", + "p_code":"146", + "code":"155" + }, + { + "desc":"A region and availability zone (AZ) identify the location of a data center. You can create resources in regions and AZs.A region is a physical data center. Each region is", + "product_code":"dws", + "title":"Regions and AZs", + "uri":"dws_03_0052.html", + "doc_type":"usermanual", + "p_code":"146", + "code":"156" + }, + { + "desc":"Yes. In the big data era, data has become a core asset. The public cloud will adhere to the commitment made over the years that we do not touch your applications or data,", + "product_code":"dws", + "title":"Is My Data Secure in GaussDB(DWS)?", + "uri":"dws_03_0022.html", + "doc_type":"usermanual", + "p_code":"146", + "code":"157" + }, + { + "desc":"GaussDB(DWS) uses IAM and VPC to control user access and isolate cluster network. Cluster access is over SSL and cipher suite. Additionally, GaussDB(DWS) supports two-way", + "product_code":"dws", + "title":"How Is GaussDB(DWS) Secured?", + "uri":"dws_03_0023.html", + "doc_type":"usermanual", + "p_code":"146", + "code":"158" + }, + { + "desc":"Yes. When a data warehouse cluster is created, its security group cannot be changed. However, you can add, delete, or modify rules of the current security group.To edit t", + "product_code":"dws", + "title":"Can I Modify the Security Group of a GaussDB(DWS) Cluster?", + "uri":"dws_03_0053.html", + "doc_type":"usermanual", + "p_code":"146", + "code":"159" + }, + { + "desc":"The evolving Internet and IoT produce massive volumes of data. This data needs to be managed, using concepts like database, data warehouse, data lake, and lakehouse. Here", + "product_code":"dws", + "title":"What Is a Database/Data Warehouse/Data Lake/Lakehouse?", + "uri":"dws_03_2121.html", + "doc_type":"usermanual", + "p_code":"146", + "code":"160" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Cluster Management", + "uri":"dws_03_0029.html", + "doc_type":"usermanual", + "p_code":"145", + "code":"161" + }, + { + "desc":"Check that you have enough quota for creating the cluster.Call the Customer Hotline for support.Telephone:Germany: 0800 330 44 44International: +800 44556600", + "product_code":"dws", + "title":"What Do I Do If Creating a GaussDB(DWS) Cluster Failed?", + "uri":"dws_03_0016.html", + "doc_type":"usermanual", + "p_code":"161", + "code":"162" + }, + { + "desc":"Cluster patching or upgrading is automatic because GaussDB(DWS) upgrades its own version.For service patch:Duration: less than 10 minutesImpact on services: 1 to 3 minute", + "product_code":"dws", + "title":"How Can I Upgrade or Downgrade GaussDB(DWS)?", + "uri":"dws_03_0031.html", + "doc_type":"usermanual", + "p_code":"161", + "code":"163" + }, + { + "desc":"After you delete data stored in GaussDB(DWS) data warehouses, dirty data may be generated from the unreleased disk space. This results in space waste and deteriorates sna", + "product_code":"dws", + "title":"How Can I Clear and Reclaim Storage?", + "uri":"dws_03_0033.html", + "doc_type":"usermanual", + "p_code":"161", + "code":"164" + }, + { + "desc":"If you do not run VACUUM to clear and reclaim the storage space before the scale-out, the data deleted from GaussDB(DWS) may not free up the occupied disk space.During th", + "product_code":"dws", + "title":"Why Did the Used Storage Reduce After Scale-out?", + "uri":"dws_03_0054.html", + "doc_type":"usermanual", + "p_code":"161", + "code":"165" + }, + { + "desc":"You can view the used capacity of a cluster CPU, memory, and disks on the Cloud Eye management console. Perform the following steps to view the information:", + "product_code":"dws", + "title":"How Do I View Node Metrics (CPU, Memory, and Disk Usage)?", + "uri":"dws_03_0104.html", + "doc_type":"usermanual", + "p_code":"161", + "code":"166" + }, + { + "desc":"A cluster with three data nodes of 320 GB each has a total capacity of 960 GB. When 1 GB data is stored, GaussDB(DWS) stores 1 GB data on two nodes due to duplication, a ", + "product_code":"dws", + "title":"How Is the Disk Space or Capacity of GaussDB(DWS) Calculated?", + "uri":"dws_03_0090.html", + "doc_type":"usermanual", + "p_code":"161", + "code":"167" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Database Connections", + "uri":"dws_03_0024.html", + "doc_type":"usermanual", + "p_code":"145", + "code":"168" + }, + { + "desc":"Yes, but GaussDB(DWS) clients and drivers are recommended. Unlike open-source PostgreSQL clients and drivers, GaussDB(DWS) clients and drivers have two key advantages:Sec", + "product_code":"dws", + "title":"Does GaussDB(DWS) Support Third-Party Clients and JDBC and ODBC Drivers?", + "uri":"dws_03_0017.html", + "doc_type":"usermanual", + "p_code":"168", + "code":"169" + }, + { + "desc":"No, direct access is not supported. VMs at the bottom layer of GaussDB(DWS) serve as the compute nodes for data analysis. Access cluster databases using the private or pu", + "product_code":"dws", + "title":"Can I Connect to GaussDB(DWS) Cluster Nodes Using SSH?", + "uri":"dws_03_0040.html", + "doc_type":"usermanual", + "p_code":"168", + "code":"170" + }, + { + "desc":"Check:Whether the cluster status is normal.Whether the connection command, username, password, IP address, and port are correct.Whether the operating system type and vers", + "product_code":"dws", + "title":"What Should I Do If I Cannot Connect to a Data Warehouse Cluster?", + "uri":"dws_03_0014.html", + "doc_type":"usermanual", + "p_code":"168", + "code":"171" + }, + { + "desc":"After the EIP is unbound, the network may be disconnected. However, the TCP layer does not detect a faulty physical connection in time due to keepalive settings. As a res", + "product_code":"dws", + "title":"Why Was I Not Notified of Failure Unbinding the EIP When GaussDB(DWS) Is Connected Over the Internet?", + "uri":"dws_03_0025.html", + "doc_type":"usermanual", + "p_code":"168", + "code":"172" + }, + { + "desc":"Resources in different AZs of the same region can communicate with each other directly if they belong to the same VPC.For resources in different AZs of the same region bu", + "product_code":"dws", + "title":"How Can a Data Warehouse and a Database in Different AZs of the Same Region Communicate?", + "uri":"dws_03_0169.html", + "doc_type":"usermanual", + "p_code":"168", + "code":"173" + }, + { + "desc":"If BI applications, client ECS, and DGC need to communicate with GaussDB(DWS), they must be in the same region and VPC as the GaussDB(DWS) cluster (different subnets are ", + "product_code":"dws", + "title":"Do I Need the Same VPC and Subnet to Connect to a GaussDB(DWS) Cluster?", + "uri":"dws_03_2125.html", + "doc_type":"usermanual", + "p_code":"168", + "code":"174" + }, + { + "desc":"You can also log in to the VPC management console to manually create a security group. Then, go back to the page for creating data warehouse clusters, click the button n", + "product_code":"dws", + "title":"How Do I Configure a Whitelist to Protect Clusters Available Through a Public IP Address?", + "uri":"dws_03_2130.html", + "doc_type":"usermanual", + "p_code":"168", + "code":"175" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Data Import and Export", + "uri":"dws_03_0026.html", + "doc_type":"usermanual", + "p_code":"145", + "code":"176" + }, + { + "desc":"The file formats supported by OBS and GDS foreign tables are as follows:OBS file formats: CSV, TEXT, ORC, and CARBONDATA. The default format is TEXT.GDS file formats: CSV", + "product_code":"dws", + "title":"What Are the Differences Between Data Formats Supported by OBS and GDS Foreign Tables?", + "uri":"dws_03_0018.html", + "doc_type":"usermanual", + "p_code":"176", + "code":"177" + }, + { + "desc":"GaussDB(DWS) supports efficient data import from multiple data sources. The following lists typical data import modes. For details, see \"Import Modes\" in the Data Warehou", + "product_code":"dws", + "title":"How Can I Import Data to GaussDB(DWS)?", + "uri":"dws_03_0027.html", + "doc_type":"usermanual", + "p_code":"176", + "code":"178" + }, + { + "desc":"Each node in a data warehouse cluster has a default storage capacity of 160 GB, 256 GB, 1.6 TB, 1.8 TB, or 13 TB. A cluster can house 3 to 32 nodes and the total storage ", + "product_code":"dws", + "title":"How Much Service Data Can a Data Warehouse Store?", + "uri":"dws_03_0028.html", + "doc_type":"usermanual", + "p_code":"176", + "code":"179" + }, + { + "desc":"GaussDB(DWS) is a fully managed service on the cloud. Users cannot log in to the background to import or export data by using COPY, so the COPY syntax is disabled. You ar", + "product_code":"dws", + "title":"How Do I Use \\Copy to Import and Export Data?", + "uri":"dws_03_0073.html", + "doc_type":"usermanual", + "p_code":"176", + "code":"180" + }, + { + "desc":"No, GaussDB(DWS) does not support OBS data import or export across regions. The GaussDB(DWS) cluster and OBS must be in the same region.", + "product_code":"dws", + "title":"Can I Export GaussDB(DWS) Data from/to OBS Across Regions?", + "uri":"dws_03_0102.html", + "doc_type":"usermanual", + "p_code":"176", + "code":"181" + }, + { + "desc":"To import heterogeneous data to GaussDB(DWS), use CDM to migrate the entire MySQL or SQL Server database. Or migrate the entire GaussDB(DWS) database to another GaussDB(D", + "product_code":"dws", + "title":"How Do I Import GaussDB(DWS)/Oracle/MySQL/SQL Server Data to GaussDB(DWS) (Whole Database Migration)?", + "uri":"dws_03_0074.html", + "doc_type":"usermanual", + "p_code":"176", + "code":"182" + }, + { + "desc":"No. The GDS server and GaussDB(DWS) can only communicate with each other on the intranet. Each DN in the GaussDB(DWS) cluster is used to connect to the GDS server in para", + "product_code":"dws", + "title":"Can I Import Data over the Public/External Network Using GDS?", + "uri":"dws_03_0105.html", + "doc_type":"usermanual", + "p_code":"176", + "code":"183" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Account, Password, and Permissions", + "uri":"dws_03_0110.html", + "doc_type":"usermanual", + "p_code":"145", + "code":"184" + }, + { + "desc":"To change the password of the database administrator dbadmin, log in to the console and choose More > Reset Password in cluster row.For security, the following two parame", + "product_code":"dws", + "title":"How Do I Change My Expired Database Password?", + "uri":"dws_03_0092.html", + "doc_type":"usermanual", + "p_code":"184", + "code":"185" + }, + { + "desc":"To view the user list, query the PG_USER view.SELECT * FROM pg_user;To view user attributes, query the PG_AUTHID system catalog.SELECT * FROM pg_authid;Query the permissi", + "product_code":"dws", + "title":"How Do I View All Database Users and Their Permissions?", + "uri":"dws_03_0095.html", + "doc_type":"usermanual", + "p_code":"184", + "code":"186" + }, + { + "desc":"This section describes how to grant users the SELECT, INSERT, UPDATE, or full permissions for tables.Assume there are users u1, u2, u3, u4, and u5 and five schemas named ", + "product_code":"dws", + "title":"How Do I Grant Table Permissions to a User?", + "uri":"dws_03_0197.html", + "doc_type":"usermanual", + "p_code":"184", + "code":"187" + }, + { + "desc":"This section describes how to grant the query permission for a schema as an example. For more information, see \"How Do I Grant Table Permissions to a User?\" in FAQ. You ", + "product_code":"dws", + "title":"How Do I Grant Schema Permissions to a User?", + "uri":"dws_03_0196.html", + "doc_type":"usermanual", + "p_code":"184", + "code":"188" + }, + { + "desc":"GaussDB(DWS) provides an implicitly defined group public that contains all roles. By default, all new users and roles have the permissions of public. To revoke permission", + "product_code":"dws", + "title":"How Do I Revoke the CONNECT ON DATABASE Permission from a User?", + "uri":"dws_03_0195.html", + "doc_type":"usermanual", + "p_code":"184", + "code":"189" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Database Usage", + "uri":"dws_03_0065.html", + "doc_type":"usermanual", + "p_code":"145", + "code":"190" + }, + { + "desc":"No, you only need to set the primary key. By default, the first column of the primary key is selected as the distribution key. If both are set, the primary key must conta", + "product_code":"dws", + "title":"Do I Need to Set a Distribution Key After Setting a Primary Key?", + "uri":"dws_03_0075.html", + "doc_type":"usermanual", + "p_code":"190", + "code":"191" + }, + { + "desc":"Yes.GaussDB(DWS) is compatible with PostgreSQL stored procedures. For details, see \"Stored Procedures\" in the Developer Guide.", + "product_code":"dws", + "title":"Is GaussDB(DWS) Compatible with PostgreSQL Stored Procedures?", + "uri":"dws_03_0076.html", + "doc_type":"usermanual", + "p_code":"190", + "code":"192" + }, + { + "desc":"Partitioned table: Partitioning refers to splitting what is logically one large table into smaller physical pieces based on specific schemes. The table based on the logic", + "product_code":"dws", + "title":"What Are Partitioned Tables, Partitions, and Partition Keys?", + "uri":"dws_03_0064.html", + "doc_type":"usermanual", + "p_code":"190", + "code":"193" + }, + { + "desc":"You are advised to use the Data Studio graphical client to export table data. You can export data from:A specific tableAll tables in a schemaAll tables in a databaseFor d", + "product_code":"dws", + "title":"How Can I Export the Table Structure?", + "uri":"dws_03_0078.html", + "doc_type":"usermanual", + "p_code":"190", + "code":"194" + }, + { + "desc":"You can use pg_tables and pg_views to query all table information and views in a database. Example:For details about the returned columns, see \"PG_TABLES\" and \"PG_VIEWS\" ", + "product_code":"dws", + "title":"How Can I Export All Tables and Views from a Database?", + "uri":"dws_03_0079.html", + "doc_type":"usermanual", + "p_code":"190", + "code":"195" + }, + { + "desc":"In GaussDB(DWS), the encoding format of a database cannot be changed. You need to create another database in the required format. For globalization purposes, set the enco", + "product_code":"dws", + "title":"How Can I Change the Character Encoding Format of a Database?", + "uri":"dws_03_0085.html", + "doc_type":"usermanual", + "p_code":"190", + "code":"196" + }, + { + "desc":"Yes. TRUNCATE is more efficient than DELETE for deleting massive data.For details, see \"TRUNCATE\" in the Data Warehouse Service (DWS) Developer Guide.TRUNCATE quickly rem", + "product_code":"dws", + "title":"How Can I Delete Table Data Efficiently?", + "uri":"dws_03_0088.html", + "doc_type":"usermanual", + "p_code":"190", + "code":"197" + }, + { + "desc":"Yes. For tables that involve frequent add, delete, or modify operations, perform VACUUM FULL and ANALYZE to reclaim the disk space occupied by updated or deleted data, pr", + "product_code":"dws", + "title":"Do I Need to Run VACUUM FULL and ANALYZE on Common Tables Periodically?", + "uri":"dws_03_0089.html", + "doc_type":"usermanual", + "p_code":"190", + "code":"198" + }, + { + "desc":"To query information about OBS/GDS foreign tables such as OBS paths, run the following statement:The following uses table traffic_data.GCJL_OBS as an example:", + "product_code":"dws", + "title":"How Do I View Foreign Table Information?", + "uri":"dws_03_2124.html", + "doc_type":"usermanual", + "p_code":"190", + "code":"199" + }, + { + "desc":"In a data warehouse database, you need to carefully choose distribution columns for large tables, because they can affect your database and query performance. If an impro", + "product_code":"dws", + "title":"How Do I Change Distribution Columns?", + "uri":"dws_03_2126.html", + "doc_type":"usermanual", + "p_code":"190", + "code":"200" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Database Performance", + "uri":"dws_03_0035.html", + "doc_type":"usermanual", + "p_code":"145", + "code":"201" + }, + { + "desc":"When a database is used for a period of time, the table data increases as services grow, or the table data is frequently added, deleted, or modified. This results in bloa", + "product_code":"dws", + "title":"Why Is SQL Execution Slow After Long GaussDB(DWS) Usage?", + "uri":"dws_03_0071.html", + "doc_type":"usermanual", + "p_code":"201", + "code":"202" + }, + { + "desc":"Due to the MPP architecture limitation of GaussDB(DWS), a few PostgreSQL methods and functions cannot be pushed to DNs for execution. As a result, performance bottlenecks", + "product_code":"dws", + "title":"Why Does GaussDB(DWS) Perform Worse Than a Single-Server Database in Extreme Scenarios?", + "uri":"dws_03_0036.html", + "doc_type":"usermanual", + "p_code":"201", + "code":"203" + }, + { + "desc":"The top SQL feature lets you view SQL statements executed in a specified period (in real time and historical). SQL statements of the current CN or all CNs are available f", + "product_code":"dws", + "title":"How Can I View SQL Execution Records of A Certain Period When Service Read and Write Are Blocked?", + "uri":"dws_03_0100.html", + "doc_type":"usermanual", + "p_code":"201", + "code":"204" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Logs", + "uri":"dws_03_0068.html", + "doc_type":"usermanual", + "p_code":"145", + "code":"205" + }, + { + "desc":"GaussDB(DWS) allows you to record the audit logs of specific operations, involving audit log retention policies, unauthorized access, as well as DML, DDL, SELECT and COPY", + "product_code":"dws", + "title":"How Can I View Database Operation Logs?", + "uri":"dws_03_0082.html", + "doc_type":"usermanual", + "p_code":"205", + "code":"206" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Change History", + "uri":"dws_01_0070.html", + "doc_type":"usermanual", + "p_code":"", + "code":"207" + } +] \ No newline at end of file diff --git a/docs/dws/umn/PARAMETERS.txt b/docs/dws/umn/PARAMETERS.txt new file mode 100644 index 00000000..6da8d5f0 --- /dev/null +++ b/docs/dws/umn/PARAMETERS.txt @@ -0,0 +1,3 @@ +version="" +language="en-us" +type="" \ No newline at end of file diff --git a/docs/dws/umn/dws_01_00013.html b/docs/dws/umn/dws_01_00013.html new file mode 100644 index 00000000..340f000c --- /dev/null +++ b/docs/dws/umn/dws_01_00013.html @@ -0,0 +1,30 @@ + + +

Application Scenarios

+
+
+
+
+
Parent topic: Service Overview
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_00014.html b/docs/dws/umn/dws_01_00014.html new file mode 100644 index 00000000..01a6cdeb --- /dev/null +++ b/docs/dws/umn/dws_01_00014.html @@ -0,0 +1,27 @@ + + +

Databases Monitoring

+
+
+ + +
+
Parent topic: Monitoring and Alarms
+
+
+ diff --git a/docs/dws/umn/dws_01_0002.html b/docs/dws/umn/dws_01_0002.html new file mode 100644 index 00000000..42348252 --- /dev/null +++ b/docs/dws/umn/dws_01_0002.html @@ -0,0 +1,85 @@ + + +

What Is GaussDB(DWS)?

+

GaussDB(DWS) is an online data processing database that runs on the cloud 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.

+

Architecture

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.

+
Figure 1 Architecture
+ +
+

Logical Cluster Architecture

Figure 2 shows the logical architecture of a GaussDB(DWS) cluster. For details about instances, see Table 1.

+
Figure 2 Logical cluster architecture
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 Cluster architecture description

Name

+

Description

+

Remarks

+

Global Transaction Manager (GTM)

+

Generates and maintains the globally unique information, such as the transaction ID, transaction snapshot, and timestamp.

+

The cluster includes only one pair of GTMs: one primary GTM and one standby GTM.

+

Workload Manager (WLM)

+

WLM controls allocation of system resources to prevent service congestion and system crash resulting from excessive workload.

+

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.

+

Coordinator (CN)

+

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.

+

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.

+

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.

+

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.

+

Datanode (DN)

+

A DN stores service data by column or row or in the hybrid mode, executes data query tasks, and returns execution results to CNs.

+

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.

+

+

Storage

+

Functions as the server's local storage resources to store data permanently.

+

-

+
+
+

DNs in a cluster store data on disks. Figure 3 describes the objects on each DN and the relationships among them logically.

+ +

Data can be distributed in replication, round-robin, or hash mode. You can specify the distribution mode during table creation.

+
Figure 3 Logical database architecture
+
+
+
+
+
Parent topic: Service Overview
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_0003.html b/docs/dws/umn/dws_01_0003.html new file mode 100644 index 00000000..9cb33837 --- /dev/null +++ b/docs/dws/umn/dws_01_0003.html @@ -0,0 +1,30 @@ + + +

Related Services

+

+

IAM

GaussDB(DWS) uses Identity and Access Management (IAM) for authentication and authorization.

+

Users who have the DWS Administrator permissions can fully utilize GaussDB(DWS). To obtain the permissions, contact a user with the Security Administrator permissions or directly create a user with the DWS Administrator permissions. Users granted the DWS Database Access permissions can generate temporary database user credentials based on IAM users to connect to databases in the data warehouse clusters.

+
+

ECS

GaussDB(DWS) uses an ECS as a cluster node.

+
+

VPC

GaussDB(DWS) uses the Virtual Private Cloud (VPC) service to provide a network topology for clusters to isolate clusters and control access.

+
+

OBS

GaussDB(DWS) uses OBS to convert cluster data and external data, satisfying the requirements for secure, reliable, and cost-effective storage.

+
+

MRS

Data can be migrated from MRS to GaussDB(DWS) clusters for analysis after the data is processed by Hadoop.

+
+

Cloud Eye

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.

+
+

CTS

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.

+
+

TMS

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.

+
+

DNS

GaussDB(DWS) uses Domain Name Service (DNS) to provide the cluster IP addresses mapped from domain names.

+
+
+
+
+
Parent topic: Service Overview
+
+
+ diff --git a/docs/dws/umn/dws_01_0004.html b/docs/dws/umn/dws_01_0004.html new file mode 100644 index 00000000..da4018c7 --- /dev/null +++ b/docs/dws/umn/dws_01_0004.html @@ -0,0 +1,17 @@ + + +

Concepts

+
+
+ + +
+
Parent topic: Service Overview
+
+
+ diff --git a/docs/dws/umn/dws_01_0005.html b/docs/dws/umn/dws_01_0005.html new file mode 100644 index 00000000..b12af046 --- /dev/null +++ b/docs/dws/umn/dws_01_0005.html @@ -0,0 +1,20 @@ + + +

GaussDB(DWS) Management Concepts

+

Cluster

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.

+
+

Node

Each data warehouse cluster contains at least three nodes, all of which support data storage and analysis.

+
+

Flavor

You need to specify the node flavors when you create a data warehouse cluster. CPU, memory, and storage resources vary depending on node flavors.

+
+

Snapshot

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.

+
+

Project

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.

+
+
+
+
+
Parent topic: Concepts
+
+
+ diff --git a/docs/dws/umn/dws_01_0006.html b/docs/dws/umn/dws_01_0006.html new file mode 100644 index 00000000..c94224b1 --- /dev/null +++ b/docs/dws/umn/dws_01_0006.html @@ -0,0 +1,24 @@ + + +

GaussDB(DWS) Database Concepts

+

Database

A data warehouse cluster is an analysis-oriented relational database platform that supports online analysis.

+
+

OLAP

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.

+
+

MPP

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.

+
+

Shared-Nothing Architecture

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.

+
+

Database Version

Each data warehouse cluster has a specific database version. You can check the version when creating a data warehouse cluster.

+
+

Database Connection

You can use a client to connect to a GaussDB(DWS) cluster in the cloud and over the Internet.

+
+

Database User

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.

+
+
+
+
+
Parent topic: Concepts
+
+
+ diff --git a/docs/dws/umn/dws_01_0007.html b/docs/dws/umn/dws_01_0007.html new file mode 100644 index 00000000..23b81a21 --- /dev/null +++ b/docs/dws/umn/dws_01_0007.html @@ -0,0 +1,31 @@ + + +

Advantages

+

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.

+

Unlike conventional data warehouses, GaussDB(DWS) excels in massive data processing and general platform management with the following benefits:

+

Ease of use

+ +

High performance

+ +

High scalability

+ +

Robust reliability

+ +
+
+
+
Parent topic: Service Overview
+
+
+ diff --git a/docs/dws/umn/dws_01_0008.html b/docs/dws/umn/dws_01_0008.html new file mode 100644 index 00000000..31563c7e --- /dev/null +++ b/docs/dws/umn/dws_01_0008.html @@ -0,0 +1,34 @@ + + +

Cluster Upgrade

+

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 Configuring the Maintenance Window.

+

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&M operation by sending SMS messages. Exercise caution when performing operations on the cluster during the O&M period.

+

If the upgrade affects the current query requests or service running, contact technical support for emergency handling.

+

A cluster is charged by hour as long as it is in the Available 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.

+

Upgrading a Cluster

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.

+

After the cluster is upgraded, it cannot be rolled back.

+
+

The following figure shows the cluster version.

+
Figure 1 Version description
+ +
+

Configuring the Maintenance Window

  1. Log in to the GaussDB(DWS) management console.
  2. Click Clusters.
  3. In the cluster list, click the name of the target cluster. The Basic Information page is displayed.

    In the Cluster Information area, you can view the maintenance window.

    +

  4. Click Configure next to Maintenance Window.
  5. In the dialog box that is displayed, configure the maintenance window.

    Figure 2 Configuring the maintenance window
    +

  6. Click OK.
+
+
+
+
+
Parent topic: Clusters
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_00081.html b/docs/dws/umn/dws_01_00081.html new file mode 100644 index 00000000..7444c39e --- /dev/null +++ b/docs/dws/umn/dws_01_00081.html @@ -0,0 +1,29 @@ + + +

DR Overview

+

Overview

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.

+

+
  • This feature is supported only in cluster version 8.1.1 or later.
+
+
+

DR Features

+
+

Constraints and Limitations

+
+
+
+
+
Parent topic: Cluster DR
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_00082.html b/docs/dws/umn/dws_01_00082.html new file mode 100644 index 00000000..e73e9a9d --- /dev/null +++ b/docs/dws/umn/dws_01_00082.html @@ -0,0 +1,34 @@ + + +

Creating a DR Task

+

Prerequisites

You can create a DR task only when the cluster is in the Available or Unbalanced state.

+
+

Procedure

  1. Log in to the GaussDB(DWS) management console.
  2. In the navigation pane on the left, click DR Tasks.
  3. On the displayed page, click Create.
  4. Select the type and enter the name of the DR task to be created.

    • Type: Cross-AZ DR
    • Name: Enter 4 to 64 case-insensitive characters, starting with a letter. Only letters, digits, hyphens (-), and underscores (_) are allowed.

      +
    +

  5. Configure the production cluster.

    • Select a created production cluster from the drop-down list.
    • After a production cluster is selected, the system automatically displays its AZ.

      +
    +

  6. Configure the DR cluster.

    • Select the AZ associated with the region where the DR cluster resides.

      The production cluster AZ will be filtered out from the available DR cluster AZs.

      +
      +
    • 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.

      +
    +

  7. Configure advanced parameters. Select Default to keep the default values of the advanced parameters. You can also select Custom to modify the values.

    • 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.

      +

      The default DR synchronization period is 30 minutes.

      +
      +
    +

  8. Click OK.

    The DR status will then change to Creating. Wait until the creation is complete, and the DR status will change to Not Started.

    +

+
+
+
+
+
Parent topic: Cluster DR
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_00083.html b/docs/dws/umn/dws_01_00083.html new file mode 100644 index 00000000..2ee4f168 --- /dev/null +++ b/docs/dws/umn/dws_01_00083.html @@ -0,0 +1,21 @@ + + +

Viewing DR Information

+
  1. Log in to the GaussDB(DWS) management console.
  2. In the navigation pane on the left, click DR Tasks.
  3. In the DR list, click the name of a DR task.

    On the page that is displayed, view the following information:

    +
    • DR Information: You can view the DR ID, DR name, DR creation time, and DR status.
    • Production Cluster Information: 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.
    • DR Cluster Information: 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.
    • DR Configurations: You can view and modify the DR synchronization period.
    +

    +

+
+
+
+
Parent topic: Cluster DR
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_00084.html b/docs/dws/umn/dws_01_00084.html new file mode 100644 index 00000000..2e2f6833 --- /dev/null +++ b/docs/dws/umn/dws_01_00084.html @@ -0,0 +1,44 @@ + + +

DR Management

+

Starting a DR Task

  1. Log in to the GaussDB(DWS) management console.
  2. In the navigation pane on the left, click DR Tasks.
  3. Click Start in the Operation column of the target DR task.
  4. In the dialog box that is displayed, click OK.

    The DR status will change to Starting. The process will take some time. After the task is started, the DR status will change to Running.

    +
    • You can start a DR task that is in the Not started/Startup failed/Stopped state.
    • 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.
    +
    +

+
+

Stopping the DR Task

  1. Log in to the GaussDB(DWS) management console.
  2. In the navigation pane on the left, click DR Tasks.
  3. Click Stop in the Operation column of the target DR task.
  4. In the dialog box that is displayed, click OK.

    The DR status will change to Stopping. The process will take some time. After the DR task is stopped, the status will change to Stopped.

    +
    • Only DR tasks in the Running or Stop failed state can be stopped.
    • Data cannot be synchronized after a DR task is stopped.
    +
    +

+
+

Switching to the DR Cluster

  1. Log in to the GaussDB(DWS) management console.
  2. In the navigation pane on the left, click DR Tasks.
  3. Click Switch to DR Cluster in the Operation column of the target DR task.
  4. In the dialog box that is displayed, click OK.

    The DR status will change to DR switching.

    +

    After the switchover is successful, the DR status will change to the original status.

    +
    • You can perform a DR switchover when the DR task is in the Running or Abnormal state.
    • During a switchover, the original production cluster is not available.
    • RPO of DR switchover:
      • Production cluster in the Available state: RPO = 0
      • Production cluster in the Unavailable state: A zero RPO may not be achieved, but data can at least be restored to that of the latest successful DR synchronization (Last DR Succeeded). For details, see Viewing DR Information.
      +
    +
    +

+
+

Updating DR Configurations

  1. Log in to the GaussDB(DWS) management console.
  2. In the navigation pane on the left, click DR Tasks.
  3. In the DR list, click the DR name to go to the DR information page.
  4. In the DR Configurations area, click Modify.

    +
    • Only DR tasks in the Not started or Stopped state can be modified.
    • The new configuration takes effect after DR is restarted.
    +
    +

+
+

Deleting DR Tasks

  1. Log in to the GaussDB(DWS) management console.
  2. In the navigation pane on the left, click DR Tasks.
  3. Click Delete in the Operation column of the target DR task.
  4. In the dialog box that is displayed, click OK.

    The DR status will change to Deleting.
    • You can delete a DR task when DR Status is Creation failed, Not started, Startup failed, Stopped, Stop failed, or Abnormal.
    • Data cannot be synchronized after a DR task is deleted, and the deleted task cannot be restored.
    +
    +
    +

+
+
+
+
+
Parent topic: Cluster DR
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_00085.html b/docs/dws/umn/dws_01_00085.html new file mode 100644 index 00000000..af6eca3d --- /dev/null +++ b/docs/dws/umn/dws_01_00085.html @@ -0,0 +1,23 @@ + + +

Mutually Exclusive DR Cases

+

Case 1: How Do I Scale out a Cluster in the DR State?

  1. Log in to the GaussDB(DWS) management console.
  2. In the navigation pane on the left, click Clusters.
  3. In the cluster list, if Task Information of the cluster you want to scale out is DR not started, perform 5 and 7.
  4. If the Task Information is other than DR not started, delete the DR task. For details, see Deleting DR Tasks.
  5. In the Operation column of the production and DR clusters, choose More > Scale Out.

    +

    +

  6. Create a DR task. For details, see Creating a DR Task.
  7. Start the DR task. For details, see Starting a DR Task.

    After scale-out, the number of DNs in the production cluster must be the same as that in the DR cluster.

    +
    +

+
+
+
+
+
Parent topic: Cluster DR
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_0009.html b/docs/dws/umn/dws_01_0009.html new file mode 100644 index 00000000..7523caa3 --- /dev/null +++ b/docs/dws/umn/dws_01_0009.html @@ -0,0 +1,36 @@ + + +

GaussDB(DWS) Access

+

The following figure shows how to use GaussDB(DWS).

+
Figure 1 Process for using GaussDB(DWS)
+

Accessing a Cluster

GaussDB(DWS) provides a web-based management console and HTTPS-compliant APIs for you to manage data warehouse clusters.

+
+

Accessing the Database in a Cluster

GaussDB(DWS) supports database access using the following methods:
  • GaussDB(DWS) clients

    Access the cluster database using GaussDB(DWS) clients. For details, see Connecting to Clusters" in the Data Warehouse Service (DWS) User Guide.

    +
  • Open-source PostgreSQL clients
    The following lists compatible open-source clients: +
    +
  • JDBC and ODBC API calling

    You can call standard APIs, such as JDBC and ODBC, to access databases in clusters.

    +

    For details, see "Using the JDBC and ODBC Drivers to Connect to a Cluster" in the Data Warehouse Service (DWS) User Guide.

    +
+
+
+

End-to-End Data Analysis Process

GaussDB(DWS) has been seamlessly integrated with other services on the cloud, helping you rapidly deploy end-to-end data analysis solutions.

+

The following figure shows the end-to-end data analysis process. Services in use during each process are also displayed.

+
Figure 2 End-to-end data analysis process
+
+
+
+
+
Parent topic: Service Overview
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_0010.html b/docs/dws/umn/dws_01_0010.html new file mode 100644 index 00000000..7f751b5c --- /dev/null +++ b/docs/dws/umn/dws_01_0010.html @@ -0,0 +1,11 @@ + + +

Restrictions

+
+
+
+
+
Parent topic: Service Overview
+
+
+ diff --git a/docs/dws/umn/dws_01_00113.html b/docs/dws/umn/dws_01_00113.html new file mode 100644 index 00000000..19a54de1 --- /dev/null +++ b/docs/dws/umn/dws_01_00113.html @@ -0,0 +1,151 @@ + + +

Technical Specifications

+

This section describes the technical specifications of GaussDB(DWS) in different versions.

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 GaussDB(DWS) technical specifications

Technical Specifications

+

Maximum Value of 8.0.x

+

Maximum Value of 8.1.0

+

Maximum Value of 8.1.1

+

Data capacity

+

10 PB

+

10 PB

+

20 PB

+

Number of cluster nodes

+

256

+

256

+

2048

+

Size of a single table

+

1 PB

+

1 PB

+

1 PB

+

Size of data in each row

+

1 GB

+

1 GB

+

1 GB

+

Size of a single column in each record

+

1 GB

+

1 GB

+

1 GB

+

Number of records in each table

+

255

+

255

+

255

+

Number of columns in each table

+

1600

+

1600

+

1600

+

Number of indexes in each table

+

Unlimited

+

Unlimited

+

Unlimited

+

Number of columns in the index of each table

+

32

+

32

+

32

+

Number of constraints in each table

+

Unlimited

+

Unlimited

+

Unlimited

+

Number of concurrent connections

+

60 for analytical long transactions; 5,000 for short transactions

+

60 for analytical long transactions; 5,000 for short transactions

+

80 for analytical long transactions; 5,000 for short transactions

+

Number of partitions in a partitioned table

+

32,768

+

32768

+

32768

+

Size of each partition in a partitioned table

+

1 PB

+

1 PB

+

1 PB

+

Number of records in each partition in a partitioned table

+

255

+

255

+

255

+
+
+
+
+
+
Parent topic: Service Overview
+
+
+ diff --git a/docs/dws/umn/dws_01_0013.html b/docs/dws/umn/dws_01_0013.html new file mode 100644 index 00000000..daf79483 --- /dev/null +++ b/docs/dws/umn/dws_01_0013.html @@ -0,0 +1,61 @@ + + +

Step 2: Creating a Cluster

+

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.

+

Creating a Cluster

  1. Log in to the GaussDB(DWS) management console.
  2. Choose Clusters in the navigation pane on the left.
  3. On the Clusters page, click Create Cluster in the upper right corner.
  4. Select the region to which the cluster to be created belongs.

    • Region: Select the current working area of the cluster.
    • AZ: Retain the default value.
    +

  5. Configure node parameters.

    • Cluster Type: For example, Standard.
    • CPU Architecture: Select a CPU architecture based on your requirements, for example, x86.
    • Node Flavor: Retain the default value.
    • Nodes: Retain the default value. At least 3 nodes are required.
    +
    Figure 1 Configuring node parameters
    +

  6. Configure cluster parameters.

    • Cluster Name: Enter dws-demo.
    • Cluster Version: The current cluster version is displayed and cannot be changed.
    • Default Database: The value is gaussdb, which cannot be changed.
    • Administrator Account: The default value is dbadmin. Use the default value. After a cluster is created, the client uses this account and its password to connect to the cluster's database.
    • Administrator Password: Enter the password.
    • Confirm Password: Enter the password again.
    • Database Port: Use the default port number. This port is used by the client or application to connect to the cluster's database.
    +
    Figure 2 Configuring the cluster
    +

  7. Configure network parameters.

    • VPC: You can select an existing VPC from the drop-down list. If no VPC has been configured, click View VPC to enter the VPC management console to create one, for example, vpc-dws. Then, go back to the page for creating a cluster on the GaussDB(DWS) management console, click next to the VPC drop-down list, and select the new VPC.
    • Subnet: When you create a VPC, a subnet is created by default. You can select the corresponding subnet.
    • Security Group: Select Automatic creation.

      The automatically created security group is named GaussDB(DWS)-<Cluster name>-<GaussDB(DWS) cluster database port>. The outbound allows all access requests, while the inbound enables only Database Port for access requests from clients or applications.

      +

      If you select a custom security group, add an inbound rule to it to enable Database Port for client hosts to access GaussDB(DWS). Table 1 shows an example. For details about how to add an inbound rule, see "Security > Security Group > Adding a Security Group Rule" in the Virtual Private Cloud User Guide.

      + +
      + + + + + + + + + + + + + +
      Table 1 Inbound rule example

      Parameter

      +

      Example Value

      +

      Protocol/Application

      +

      TCP

      +

      Port

      +

      8000

      +
      NOTE:

      Enter the value of Database Port set when creating the GaussDB(DWS) cluster. This port is used for receiving client connections to GaussDB(DWS). The default port number is 8000.

      +
      +

      Source

      +

      Select IP address, and enter the IP address and subnet mask of the client host that accesses GaussDB(DWS), for example, 192.168.0.10/16.

      +
      +
      +
    • EIP: Select Automatically assign to apply for a cluster EIP as the public network IP address of the cluster. In addition, set the EIP bandwidth.
    +
    Figure 3 Configuring the network
    +

  8. 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 default.

    An enterprise project facilitates project-level management and grouping of cloud resources and users.

    +

    You can select the default enterprise project (default) or other existing enterprise projects. To create an enterprise project, log in to the Enterprise Management console. For details, see the Enterprise Management User Guide.

    +

  9. Select Default for Advanced Settings in this example.

    • Default: indicates that the following advanced settings use the default configurations.
      • Automated Snapshot: By default, the policy for automatically creating cluster snapshots is enabled.
      • CNs: Three CNs are deployed by default.
      • Parameter Template: The default database parameter template is associated with the cluster.
      • Tag: By default, no tag is added to the cluster.
      +
    • Custom: Select this option to configure the following advanced parameters: Automated Snapshot, CNs, Parameter Template, Tag
    +

  10. Click Create Now. The Confirm page is displayed.
  11. Click Submit.

    After the submission is successful, the creation starts. Click Back to Cluster List. The Clusters page is displayed. The initial status of the cluster is Creating. Cluster creation takes some time. Wait for a while. Clusters in the Available state are ready for use.

    +

+
+
+
+
+
Parent topic: Getting Started
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_00131.html b/docs/dws/umn/dws_01_00131.html new file mode 100644 index 00000000..a6e82d7e --- /dev/null +++ b/docs/dws/umn/dws_01_00131.html @@ -0,0 +1,16 @@ + + +

Database Monitoring Overview

+

Overview

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.

+

The database monitoring function is supported by 8.1.1.200 and later versions.

+
+
+

Entering the Database Monitoring Page

  1. Log in to the GaussDB(DWS) management console.
  2. On the Clusters page, locate the target cluster.
  3. In the Operation column of the target cluster, choose Monitoring Panel. The database monitoring page is displayed.
+
+
+
+
+
Parent topic: Databases Monitoring
+
+
+ diff --git a/docs/dws/umn/dws_01_00132.html b/docs/dws/umn/dws_01_00132.html new file mode 100644 index 00000000..36986d30 --- /dev/null +++ b/docs/dws/umn/dws_01_00132.html @@ -0,0 +1,36 @@ + + +

Cluster Overview

+

Cluster Overview

  1. Log in to the GaussDB(DWS) management console.
  2. On the Clusters page, locate the target cluster.
  3. In the Operation column of the target cluster, click Monitoring Panel. The database monitoring page is displayed.
  4. In the navigation pane on the left, click Cluster Overview.

    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.

    +

+
+

Cluster Status

In the Cluster Status area, you can view the status of the current cluster and the number of available resources, including the numbers of nodes, CNs, and databases.

+

+
+

Resource Consumption

In Resource Consumption, you can view the real-time resource consumption of the current cluster, including Memory Usage, Disk Usage, CPU Usage, Disk I/O (KB/s), and Network I/O (KB/s).

+

+
+

TOP SQL

In the TOP SQL 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.

+

+

+

Top 5 SQL statement query is implemented by max_ctime, 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.

+
+
+

Key Metrics

On the Cluster Overview page, you can also view the database metrics of the current cluster, including Sessions and Queries.

+

+

+
+
+
+
+
Parent topic: Databases Monitoring
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_00133.html b/docs/dws/umn/dws_01_00133.html new file mode 100644 index 00000000..c4f33155 --- /dev/null +++ b/docs/dws/umn/dws_01_00133.html @@ -0,0 +1,27 @@ + + +

Monitoring

+
+
+ + +
+
Parent topic: Databases Monitoring
+
+
+ diff --git a/docs/dws/umn/dws_01_00134.html b/docs/dws/umn/dws_01_00134.html new file mode 100644 index 00000000..ce4f1d53 --- /dev/null +++ b/docs/dws/umn/dws_01_00134.html @@ -0,0 +1,45 @@ + + +

SQL Diagnosis

+

Prerequisites

To enable SQL diagnosis, enable monitoring on real-time and historical queries on the Queries and History tabs, respectively. For details, see .

+
+

Viewing SQL Diagnosis

  1. Log in to the GaussDB(DWS) management console.
  2. On the Clusters page, locate the target cluster.
  3. In the Operation column of the target cluster, click Monitoring Panel.
  4. In the navigation pane on the left, choose Utilities > SQL Diagnosis. The metrics include:

    • Query ID
    • Database
    • Schema Name
    • User Name
    • Client
    • Client IP Address
    • Running Time (ms)
    • CPU Time (ms)
    • Scale-Out Started
    • Completed
    • Details
    +

  5. On the SQL Diagnosis page, you can view the SQL diagnosis information. In the Details column of a specified query ID, click View to view the detailed SQL diagnosis result, including:

    • Diagnosis Type
    • Alarm Information
    • SQL Statement
    • Execution Plan
    +

    +

+
+

Setting GUC Parameters

GUC parameters related to SQL diagnosis are as follows. For details, see "GUC Parameters" in the Data Warehouse Service (DWS) Developer Guide.

+ +
+
+
+
+
Parent topic: Utilities
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_00135.html b/docs/dws/umn/dws_01_00135.html new file mode 100644 index 00000000..58d15894 --- /dev/null +++ b/docs/dws/umn/dws_01_00135.html @@ -0,0 +1,29 @@ + + +

Settings

+

The Monitoring page displays the collection period and data aging period of monitoring metrics.

+
  • The cluster monitoring function is enabled by default.
  • Disable the function if the cluster is being recovered. Enable the function when the fault is rectified.
  • 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.
+
+

Monitoring Collection

  1. Log in to the GaussDB(DWS) management console.
  2. On the Clusters page, locate the target cluster.
  3. In the Operation column of the target cluster, choose Monitoring Panel. The database monitoring page is displayed.
  4. In the navigation pane on the left, choose Settings > Monitoring. You can reconfigure the collection frequency or disable the collection of the monitoring item.

    +

    Click Update of DDL Audit to reset the automatic audit frequency or audit items.

    +

    +
    +

+
+

Collection Storage

  1. Log in to the GaussDB(DWS) management console.
  2. On the Clusters page, locate the target cluster.
  3. In the Operation column of the target cluster, choose Monitoring Panel. The database monitoring page is displayed.
  4. In the navigation pane on the left, choose Settings > Monitoring and switch to the Collection Storage tab page. Update the retention days.

    +

+
+
+
+
+
Parent topic: Databases Monitoring
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_00136.html b/docs/dws/umn/dws_01_00136.html new file mode 100644 index 00000000..f590578b --- /dev/null +++ b/docs/dws/umn/dws_01_00136.html @@ -0,0 +1,1845 @@ + + +

Monitoring Metrics

+

You can check the status and available resources of a cluster and learn about its real-time resource consumption through the GaussDB(DWS) monitoring items.

+

Table 1 describes GaussDB(DWS) monitoring metrics.

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 GaussDB(DWS) monitoring metrics

Monitored Object

+

Metric

+

Description

+

Value Range

+

Monitoring Period (Raw Data)

+

Cluster Overview

+

+

+

+

Cluster Status

+

Status of a cluster.

+

Normal/Abnormal/Degraded

+

30s

+

Nodes

+

Number of available nodes and total number of nodes (Available/Total) in a cluster.

+

≥ 0

+

60s

+

CNs

+

Number of CNs in a cluster.

+

≥ 0

+

60s

+

Databases

+

Number of created databases in a cluster.

+

≥ 0

+

90s

+

Resource Consumption

+

+

+

+

+

CPU Usage

+

Average real-time CPU usage of all nodes in a cluster.

+

0% to 100%

+

30s

+

Memory Usage

+

Average real-time memory usage of all nodes in a cluster.

+

0% to 100%

+

30s

+

Disk Usage

+

Average real-time disk usage of all nodes in a cluster.

+

0% to 100%

+

30s

+

Disk I/O

+

Average real-time disk I/O of all nodes in a cluster.

+

≥ 0 KB/s

+

30s

+

Network I/O

+

Average real-time network I/O of all NICs in a cluster.

+

≥ 0 KB/s

+

30s

+

Top 5 Time-Consuming Queries

+

+

+

Query ID

+

ID of a query, which is automatically generated by the database.

+

≥ 0

+

180s

+

SQL Statement

+

Query statement executed by a user.

+

Character string

+

180s

+

Execution Time

+

Execution time of a query statement (unit: ms).

+

≥ 0 ms

+

180s

+

Top 5 Queries with Most Data Written to Disk

+

+

+

Query ID

+

ID of a query, which is automatically generated by the database.

+

≥ 0

+

180s

+

SQL Statement

+

Query statement executed by a user.

+

Character string

+

180s

+

Data Written to Disk

+

Data to be written to disks after a user runs a statement (unit: MB).

+

≥ 0 MB

+

180s

+

Cluster Resource Metrics

+

+

+

+

+

+

+

+

+

+

+

CPU Usage

+

Average CPU usage and skew ratio of all nodes in the cluster. The formula for calculating the skew is (max-avg)/max.

+

0% to 100%

+

30s

+

Memory Usage

+

Average memory usage and skew ratio of all nodes in the cluster. The formula for calculating the skew is (max-avg)/max.

+

0% to 100%

+

30s

+

Disk Usage

+

Average usage and skew ratio of all disks in the cluster. The formula for calculating the skew is (max-avg)/max.

+

0% to 100%

+

30s

+

Disk I/O Usage

+

Average I/O usage and skew rate of all disks in the cluster. The formula for calculating the skew is (max-avg)/max.

+

0% to 100%

+

30s

+

Network I/O Usage

+

Average I/O usage and skew rate of all NICs in the cluster. The formula for calculating the skew is (max-avg)/max.

+

0% to 100%

+

30s

+

Key Database Metrics

+

Cluster Status

+

Cluster running status.

+

Normal/Degraded/Abnormal

+

30s

+

Cluster Abnormal CNs

+

Number of abnormal CNs in the cluster

+

≥ 0

+

60s

+

Cluster Read-only

+

Whether the cluster is in the read-only state

+

Yes/No

+

30s

+

Concurrent Sessions

+

Number of concurrent sessions in a cluster within a specified period.

+

≥ 0

+

30s

+

Concurrent Queries

+

Number of concurrent queries in a cluster within a specified period.

+

≥ 0

+

30s

+

Node Monitoring-Overview

+

+

+

+

+

+

+

Node Name

+

Name of a node in a cluster.

+

Character string

+

30s

+

CPU Usage

+

CPU usage of a host.

+

0% to 100%

+

30s

+

Memory Usage

+

Memory usage of a host.

+

0% to 100%

+

30s

+

Average Disk Usage (%)

+

Disk usage of a host.

+

0% to 100%

+

30s

+

IP Address

+

Service IP address of a host.

+

Character string

+

30s

+

Disk I/O

+

Disk I/O of a host (unit: KB/s)

+

≥ 0 KB/s

+

30s

+

TCP Protocol Stack Retransmission Rate

+

Retransmission rate of TCP packets per unit time.

+

0% to 100%

+

30s

+

Status

+

Running status of a host

+

Online/Offline

+

30s

+

Node Monitoring-Disks

+

+

+

+

+

+

+

+

+

Node Name

+

Name of a node in a cluster.

+

Character string

+

30s

+

Disk Name

+

Name of a disk on a host.

+

Character string

+

30s

+

Disk Capacity

+

Disk capacity of the host (unit: GB)

+

≥ 0 GB

+

30s

+

Disk Usage

+

Disk usage of a host.

+

0% to 100%

+

30s

+

Disk Read Rate

+

Disk read rate of the host (unit: KB/s)

+

≥ 0 KB/s

+

30s

+

Disk Write Rate

+

Disk write rate of the host (unit: KB/s)

+

≥ 0 KB/s

+

30s

+

I/O Wait Time (await, ms)

+

Average waiting time for each I/O request (unit: ms)

+

≥ 0 ms

+

30s

+

I/O Service Time (svctm, ms)

+

Average processing time for each I/O request (unit: ms)

+

≥ 0 ms

+

30s

+

I/O Utility (util, %)

+

Disk I/O usage of a host.

+

0% to 100%

+

30s

+

Node Monitoring-Network

+

+

+

+

+

+

+

+

+

Node Name

+

Name of a node in a cluster.

+

Character string

+

30s

+

NIC Name

+

Name of the NIC on a host.

+

Character string

+

30s

+

NIC Status

+

NIC status.

+

up/down

+

30s

+

NIC Speed

+

Working rate of a NIC, in Mbit/s.

+

≥ 0

+

30s

+

Received Packets

+

Number of received packets of a NIC.

+

≥ 0

+

30s

+

Sent Packets

+

Number of sent packets of a NIC.

+

≥ 0

+

30s

+

Lost Packets Received

+

Number of received lost packets of a NIC.

+

≥ 0

+

30s

+

Receive Rate

+

Number of bytes received by a NIC per unit of time (KB/s).

+

≥ 0 KB/s

+

30s

+

Transmit Rate

+

Number of bytes sent by a NIC per unit of time (unit: KB/s)

+

≥ 0 KB/s

+

30s

+

Database Monitoring

+

+

+

+

+

+

+

+

+

+

+

+

+

+

+

+

+

+

Database Name

+

Name of the database created by a user in a cluster.

+

Character string

+

60s

+

Usage

+

Used capacity of the current database (unit: GB).

+

≥ 0 GB

+

86400s

+

Users

+

Number of users in the current database.

+

≥ 0

+

30s

+

Sessions

+

Number of sessions in the current database.

+

≥ 0

+

30s

+

Applications

+

Number of applications in the current database.

+

≥ 0

+

30s

+

Queries

+

Number of active queries in the current database.

+

≥ 0

+

30s

+

Scanning Rows

+

Number of rows returned by the full table scan query in the current database.

+

≥ 0

+

60s

+

Index Query Rows

+

Number of rows returned by the index query in the current database.

+

≥ 0

+

60s

+

Inserted Rows

+

Number of rows inserted in the current database.

+

≥ 0

+

60s

+

Updated Rows

+

Number of rows updated in the current database.

+

≥ 0

+

60s

+

Deleted Rows

+

Number of rows deleted from the current database.

+

≥ 0

+

60s

+

Executed Transactions

+

Number of transaction executions on the current database.

+

≥ 0

+

60s

+

Transaction Rollbacks

+

Number of transactions in the current database that have been rolled back.

+

≥ 0

+

60s

+

Deadlocks

+

Number of deadlocks detected in the current database.

+

≥ 0

+

60s

+

Physical Read Times

+

Number of disk blocks read in the current database.

+

≥ 0

+

60s

+

Logical Read Times

+

Number of times that disk blocks are found in the cache.

+

≥ 0

+

60s

+

Temporary Files

+

Number of temporary files created in the current database.

+

≥ 0

+

60s

+

Temporary File Capacity

+

Size of temporary files written by the current database, in GB.

+

≥ 0

+

60s

+

Performance Monitoring

+

+

+

+

+

+

+

+

+

+

+

+

+

+

+

+

+

+

+

+

+

+

+

+

+

Cluster CPU Usage

+

Historical trend of the average CPU usage and skew of all nodes in the cluster. The formula for calculating the skew is (max-avg)/max.

+

0% to 100%

+

30s

+

Cluster Memory Usage

+

Historical trend of the average memory usage and skew of all nodes in the cluster. The formula for calculating the skew is (max-avg)/max.

+

0% to 100%

+

30s

+

Cluster Disk Usage

+

Historical trend of the average disk usage and skew of all nodes in the cluster. The formula for calculating the skew is (max-avg)/max.

+

0% to 100%

+

30s

+

Cluster Disk I/O

+

Historical trend of the average disk I/O and skew of all disks in the cluster. The formula for calculating the skew is (max-avg)/max.

+

0% to 100%

+

30s

+

Cluster Network I/O

+

Historical trend of the average network I/O value and skew of all NICs in the cluster. The formula for calculating the skew is (max-avg)/max.

+

0% to 100%

+

30s

+

Cluster Status

+

Historical trend of the cluster status.

+

Normal/Abnormal/Degraded

+

30s

+

Cluster Read-only

+

Historical trend of the cluster read-only status change trend.

+

Yes/No

+

30s

+

Cluster Abnormal CNs

+

Historical trend of the number of abnormal CNs in the cluster.

+

≥ 0

+

60s

+

Cluster Abnormal DNs

+

Historical trend of the number of abnormal DNs in the cluster.

+

≥ 0

+

60s

+

Cluster CPU Usage of DNs

+

Historical trends of the average CPU usage and skew ratio changes of all DNs in the cluster. The formula for calculating the skew ratio is (max – avg)/max.

+

0% to 100%

+

60s

+

Cluster Sessions

+

Historical trend of the number of sessions in a cluster.

+

≥ 0

+

30s

+

Cluster Queries

+

Historical change trend of the number of queries in the cluster.

+

≥ 0

+

30s

+

Cluster Deadlocks

+

Historical trend of the number of deadlocks in a cluster.

+

≥ 0

+

60s

+

Cluster TPS

+

Average number of transactions per second of all databases in a cluster. Formula: (delta_xact_commit + delta_xact_rollback)/current_collect_rate

+

≥0

+

60s

+

Cluster QPS

+

Average number of concurrent requests per second of all databases in a cluster. Formula: delta_query_count/current_collect_rate

+

≥ 0

+

60s

+

Database Sessions

+

Historical trend of the number of sessions on a single database in a cluster.

+

≥ 0

+

30s

+

Database Queries

+

Historical trend of the number of queries on a single database in a cluster.

+

≥ 0

+

30s

+

Database Submitted Transactions

+

Historical trend of the number of transactions submitted on a single database in a cluster.

+

≥ 0

+

60s

+

Database Rollback Transactions

+

Historical trend of the number of rollback transactions on a single database in a cluster.

+

≥ 0

+

60s

+

Cluster Scanning Rows

+

Historical trend of the number of rows returned by a full table scan on a single database in a cluster.

+

≥ 0

+

60s

+

Database Index Query Rows

+

Historical trend of the number of rows returned by an index query in a single database of a cluster.

+

≥ 0

+

60s

+

Database Inserted Rows

+

Historical trend of the number of rows inserted into a single database in a cluster.

+

≥ 0

+

60s

+

Database Updated Rows

+

Historical trend of the number of updated rows in a single database in a cluster.

+

≥ 0

+

60s

+

Database Deleted Rows

+

Historical trend of the number of deleted rows in a single database in a cluster.

+

≥ 0

+

60s

+

Database Capacity

+

Historical trend of the capacity in a single database in a cluster.

+

≥ 0

+

86400s

+

Database Length of the Request Waiting Queue

+

Historical trend of the waiting queue length on a single database in a cluster.

+

≥ 0

+

30s

+

Database TPS

+

Number of transactions per second of each database in a cluster. Formula: (delta_xact_commit + delta_xact_rollback)/current_collect_rate.

+

≥0

+

60s

+

Session Monitoring

+

+

+

+

+

+

+

+

+

Session ID

+

ID of the current session (query thread ID).

+

Character string

+

30s

+

User Name

+

Name of the user who executes the current session.

+

Character string

+

30s

+

Database Name

+

Name of the database connected to the current session.

+

Character string

+

30s

+

Session Duration

+

Duration of the current session (unit: ms).

+

≥ 0 ms

+

30s

+

Application Name

+

Name of the application that creates the current session.

+

Character string

+

30s

+

Queries

+

Number of SQL statements executed in the current session.

+

≥ 0

+

30s

+

Latest Query Duration

+

Duration for executing the previous SQL statement in the current session.

+

≥ 0 ms

+

30s

+

Client IP Address

+

IP address of the client that initiates the current session.

+

Character string

+

30s

+

Connected CN

+

Connected CN of the current session.

+

Character string

+

30s

+

Session Status

+

Execution status of the current session.

+

Running/Idle/Retry

+

30s

+

Query Monitoring-Real-Time

+

+

+

+

+

+

+

+

+

+

+

+

+

+

+

+

+

+

Query ID

+

Query ID of a current query statement, which is a unique identifier allocated by the kernel to each query statement.

+

Character string

+

30s

+

User Name

+

Name of the user who submits the current query statement.

+

Character string

+

30s

+

Database Name

+

Name of the database corresponding to the current query statement.

+

Character string

+

30s

+

Application Name

+

Name of the application corresponding to the current query statement.

+

Character string

+

30s

+

Workload Queue

+

Name of the workload queue that carries the current query statement.

+

Character string

+

30s

+

Submitted

+

Timestamp when the current query statement is submitted.

+

Character string

+

30s

+

Blocking Time

+

Waiting time before the current query statement is executed, in ms.

+

≥ 0

+

30s

+

Execution Time

+

Execution time of the current query statement, in ms.

+

≥ 0

+

30s

+

CPU Time

+

Total CPU time spent by the current query statement on all DNs, in ms.

+

≥ 0

+

30s

+

CPU Time Skew

+

CPU time skew of the current query statement among all DNs.

+

0% to 100%

+

30s

+

Average Written Data

+

Average data size of the current query statement flushed to disks on all DNs, in MB.

+

≥ 0

+

30s

+

Statement

+

Query statement that is being executed.

+

Character string

+

30s

+

Connected CN

+

Name of the CN that submits the current query statement.

+

Character string

+

30s

+

Client IP Address

+

IP address of the client that submits the current query statement.

+

Character string

+

30s

+

Lane

+

Lane where the current query statement is located.

+

Fast Lane/Slow Lane

+

30s

+

Query Status

+

Query status of the statement that is being executed.

+

Character string

+

30s

+

Session ID

+

Session ID of the current query statement, which is a unique identifier allocated by the kernel to each client connection.

+

Character string

+

30s

+

Queuing Status

+

Status of the current query execution in the database, indicating whether the query is queued in the workload queue.

+

Yes/No

+

30s

+

Query Monitoring-History

+

+

+

+

+

+

+

+

+

+

+

+

Query ID

+

Query ID of a query statement, which is a unique identifier allocated by the kernel to each query statement.

+

Character string

+

180s

+

User Name

+

Name of the user who submits a query statement.

+

Character string

+

180s

+

Application Name

+

Application name corresponding to a query statement.

+

Character string

+

180s

+

Database Name

+

Name of the database corresponding to a query statement.

+

Character string

+

180s

+

Workload Queue

+

Name of the workload queue that carries the current query statement.

+

Character string

+

180s

+

Submitted

+

Timestamp when a query statement is submitted.

+

Character string

+

180s

+

Blocking Time

+

Waiting time before the query statement is executed, in ms.

+

≥ 0

+

180s

+

Execution Time

+

Execution time of the query statement, in ms.

+

≥ 0

+

180s

+

CPU Time

+

Total CPU time spent by the query statement on all DNs, in ms.

+

≥ 0

+

180s

+

CPU Time Skew

+

CPU time skew of a query statement executed on all DNs.

+

0% to 100%

+

180s

+

Average Written Data

+

Average data size of the query statement flushed to disks on all DNs, in MB.

+

≥ 0

+

180s

+

Statement

+

Query statements to be parsed

+

Character string

+

180s

+

Slow Instance Monitoring

+

+

+

+

+

Slow Instance

+

Number of slow instances detected at the current time point.

+

≥ 0

+

240s

+

Detected

+

Time when a slow instance is detected for the first time.

+

Character string

+

240s

+

Node Name

+

Name of the node where the slow instance is deployed.

+

Character string

+

240s

+

Instance

+

Name of an instance.

+

Character string

+

240s

+

Slow Node Detections (within 24 hours)

+

Number of times that a slow instance is detected within 24 hours.

+

≥ 0

+

240s

+

Workload Queue Monitoring

+

+

+

+

+

+

+

+

+

+

+

+

+

Workload Queue

+

Name of the workload queue in the cluster.

+

Character string

+

120s

+

CPU Usage

+

Real-time CPU usage of the workload queue.

+

0% to 100%

+

120s

+

CPU Resource

+

CPU usage quotas of the workload queue.

+

0% to 100%

+

120s

+

Real-Time Concurrent Short Queries

+

Number of real-time concurrent simple queries in a workload queue.

+

≥ 0

+

120s

+

Concurrent Short Queries

+

Concurrent simple query quotas of a workload queue.

+

≥ 0

+

120s

+

Real-Time Concurrent Queries

+

Number of real-time concurrent complex queries in a workload queue.

+

≥ 0

+

120s

+

Query Concurrency

+

Concurrent complex query quotas of a workload queue.

+

≥ 0

+

120s

+

Waiting Queries

+

+

+

+

+

+

+

User

+

Name of the user of waiting queries

+

Character string

+

120s

+

Application

+

Name of the application to be queried.

+

Character string

+

120s

+

Database

+

Name of the database to be queried.

+

Character string

+

120s

+

Queuing Status

+

Execution status of a query in the database (CCN/CN/DN).

+

Character string

+

120s

+

Wait Time

+

Waiting time for a waiting query (unit: ms).

+

≥ 0 ms

+

120s

+

Workload Queue

+

Workload queue to which the waiting query belongs.

+

Character string

+

120s

+

Statement

+

Query statement for the waiting status.

+

Character string

+

120s

+

Circuit Breaking Queries

+

+

+

+

+

+

+

+

Query ID

+

Query ID of the circuit breaking query statement.

+

Character string

+

120s

+

Query Statement

+

Query statement for the circuit breaking status.

+

Character string

+

120s

+

Blocking Time

+

Blocking time before the query statement triggers circuit breaking, in ms.

+

≥ 0

+

120s

+

Execution Time

+

Execution time before the query statement triggers circuit breaking, in ms.

+

≥ 0

+

120s

+

CPU Time

+

Average CPU time consumed by each DN before the query statement triggers circuit breaking, in ms.

+

≥ 0

+

120s

+

CPU Skew

+

Skew rate of CPU time consumed by each DN before the query statement triggers circuit breaking.

+

0% to 100%

+

120s

+

Exception Handling

+

Handling method after the query statement triggers circuit breaking.

+

Abort/Degrade

+

120s

+

Status

+

Circuit breaking handling status of a query statement.

+

Executing/Completed

+

120s

+

SQL Tuning

+

+

+

+

+

+

+

+

+

+

+

+

Query ID

+

IP address of the current query (query logic ID).

+

Character string

+

180s

+

Database

+

Name of the database where the current query is executed.

+

Character string

+

180s

+

Schema Name

+

Name of the current query schema.

+

Character string

+

180s

+

User Name

+

Name of the user who performs the query.

+

Character string

+

180s

+

Client

+

Name of the client that initiates the current query.

+

Character string

+

180s

+

Client IP Address

+

IP address of the client that initiates the current query.

+

Character string

+

180s

+

Running Time

+

Execution time of the current query, in ms.

+

≥ 0

+

180s

+

CPU Time

+

CPU time of the current query, in ms.

+

≥ 0

+

180s

+

Scale-Out Started

+

Start time of the current query.

+

Timestamp

+

180s

+

Completed

+

End time of the current query.

+

Timestamp

+

180s

+

Details

+

Details about the current query.

+

Character string

+

180s

+

INODE

+

Inode Usage

+

Disk inode usage.

+

0% to 100%

+

30s

+

SCHEMA

+

Schema Usage

+

Database schema usage.

+

0% to 100%

+

3600s

+
+
+ +
+ + + + + + + + + + + + + + + +
Table 2 Restrictions on monitoring metrics

Type

+

Metric

+

ECS Cluster

+

BMS Cluster

+

Network

+

+

NIC nominal speed

+

None

+

100/1000/10000/50000M

+

NIC working mode (duplex)

+

None

+

full/half

+
+
+
+
+
+
Parent topic: Databases Monitoring
+
+
+ diff --git a/docs/dws/umn/dws_01_00137.html b/docs/dws/umn/dws_01_00137.html new file mode 100644 index 00000000..2dfb0638 --- /dev/null +++ b/docs/dws/umn/dws_01_00137.html @@ -0,0 +1,17 @@ + + +

Typical Scenarios

+
+
+ + +
+
Parent topic: Databases Monitoring
+
+
+ diff --git a/docs/dws/umn/dws_01_00175.html b/docs/dws/umn/dws_01_00175.html new file mode 100644 index 00000000..8cbb273e --- /dev/null +++ b/docs/dws/umn/dws_01_00175.html @@ -0,0 +1,18 @@ + + +

Utilities

+

+
+
+ + +
+
Parent topic: Databases Monitoring
+
+
+ diff --git a/docs/dws/umn/dws_01_0018.html b/docs/dws/umn/dws_01_0018.html new file mode 100644 index 00000000..4450dbd1 --- /dev/null +++ b/docs/dws/umn/dws_01_0018.html @@ -0,0 +1,85 @@ + + +

Process for Using GaussDB(DWS)

+

GaussDB(DWS) is an online data processing database that uses the cloud 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.

+

GaussDB(DWS) provides an easy-to-use management console, allowing you to quickly create clusters and easily manage data warehouses.

+

Process Description

Figure 1 Process for using GaussDB(DWS)
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 Process description

Process

+

Task

+

Description

+

Operation Instruction

+

Make preparations.

+

-

+

Before using GaussDB(DWS), select an open port on your firewall as the database port of your data warehouse cluster.

+

Preparations

+

Create a cluster.

+

-

+

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.

+

Creating a Cluster

+

Connect to the cluster.

+

-

+

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 Connection Management page of the GaussDB(DWS) management console.

+

Methods of Connecting to a Cluster

+

Access the database.

+

-

+

After connecting to the cluster, you can create and manage databases, manage users and permissions, import and export data, and query and analyze data.

+

Data Warehouse Service (DWS) Developer Guide

+

Manage and monitor the cluster.

+

+

+

Manage the cluster.

+

View the cluster status, modify cluster configurations, add cluster tags, and scale out, restart, and delete the cluster.

+

Managing clusters

+

Manage the snapshot.

+

Create snapshots to back up and restore the cluster.

+

Managing snapshots

+

Perform O&M and monitoring.

+

View the running status and performance of the cluster through monitoring, log auditing, event notification, and resource load management.

+		 +
+
+
+
+ diff --git a/docs/dws/umn/dws_01_0019.html b/docs/dws/umn/dws_01_0019.html new file mode 100644 index 00000000..b4ccf626 --- /dev/null +++ b/docs/dws/umn/dws_01_0019.html @@ -0,0 +1,379 @@ + + +

Creating a Cluster

+

To use cloud GaussDB(DWS), create a cluster first.

+

This section describes how to create a data warehouse cluster on the GaussDB(DWS) management console.

+

Preparations Before Creating a Cluster

+
+

Creating a Cluster

  1. Log in to the GaussDB(DWS) management console.
  2. Choose Clusters in the navigation pane on the left.
  3. On the Clusters page, click Create Cluster.
  4. Select Region.

    +

    + + + + + + + + + + + + + +
    Table 1 Region parameters

    Parameter

    +

    Description

    +

    Example Value

    +

    Region

    +

    Select the actual region where the cluster nodes run.

    +

    eu-de

    +

    AZ

    +

    Select an AZ associated with the cluster region.

    +

    -

    +
    +
    +

  5. Configure Resource, CPU Architecture, and Node Flavor.

    The number of nodes in a new cluster cannot exceed the quota that can be used by a user or 32. If the node quota is insufficient, click Increase quota to submit a service ticket and apply for higher node quota.

    +
    +
    Figure 1 Configuring node parameters
    +
    +
    + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 2 Node configuration parameters

    Parameter

    +

    Description

    +

    Example Value

    +

    Cluster Type

    +

    GaussDB(DWS) cluster types include:

    +
    • Standard: The OLAP database engine is used, supporting online query and offline analysis of 10 PB data. A Standard cluster can be scaled out to 1024 nodes.
    +

    Standard

    +

    CPU Architecture

    +

    The CPU architecture includes:

    +
    • x86
    +
    NOTE:

    The only difference between the x86 and Kunpeng architectures lies in the underlying architecture, of which the application layer is unaware. The same SQL syntax is used. If x86 servers are sold out when you create a cluster, select the Kunpeng architecture.

    +
    +

    x86

    +

    Node Flavor

    +

    Select the desired node flavor based on service requirements. Each node flavor displays the vCPU, memory, and recommended application scenario.

    +

    +

    Table 3 describes the node flavors supported by GaussDB(DWS).

    +

    dws.m3.xlarge

    +

    Nodes

    +

    Specify the number of nodes in the cluster.

    +

    The number of nodes ranges from 3 to 256.

    +

    3

    +

    Total Capacity (GB)

    +

    Displays the total capacity of a cluster.

    +

    The storage capacity of each flavor is the actual database space used for storing data. The displayed storage capacity has deducted the disk space consumed by backups and RAIDs.

    +

    -

    +
    +
    +
    + +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 3 Flavor description

    Type

    +

    vCPU Cores

    +

    Memory

    +

    Disk Size

    +

    Disk Type

    +

    dws.m1.xlarge.ultrahigh

    +

    4

    +

    32 GB

    +

    256 GB

    +

    General-purpose generation I, SSD

    +

    dws.d1.xlarge

    +

    4

    +

    32 GB

    +

    1.68 TB

    +

    Local disk (HDD)

    +

    dws.d2.15xlarge

    +

    60

    +

    540 GB

    +

    13.41 TB

    +

    Disk-intensive generation II (KVM), local disk (HDD)

    +

    dws.d2.xlarge

    +

    4

    +

    32 GB

    +

    1.68 TB

    +

    Disk-intensive generation II (KVM), local disk (HDD)

    +

    dws.m3.xlarge

    +

    4

    +

    32 GB

    +

    160 GB

    +

    General-purpose generation III (KVM), SSD

    +
    +
    +

  6. Configure cluster parameters.

    Figure 2 Cluster parameters
    +
    +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 4 Cluster parameters

    Parameter

    +

    Description

    +

    Example Value

    +

    Cluster Name

    +

    Set the name of the data warehouse cluster.

    +

    Enter 4 to 64 characters. Only case-insensitive letters, digits, hyphens (-), and underscores (_) are allowed. The value must start with a letter.

    +
    NOTE:

    After a cluster is created, its name cannot be changed.

    +
    +

    dws-demo

    +

    Cluster Version

    +

    Displays the version of the database instance installed in the cluster. The figure is for reference only.

    +

    -

    +

    Default Database

    +

    The default database name of the cluster is gaussdb.

    +
    NOTE:

    This name cannot be changed.

    +
    +

    gaussdb

    +

    Administrator Account

    +

    Set the database administrator name.

    +

    The administrator username must:

    +
    • Consist of lowercase letters, digits, or underscores.
    • Start with a lowercase letter or an underscore.
    • Contain 6 to 64 characters.
    • Cannot be a keyword of the GaussDB(DWS) database. For details about the keywords of the GaussDB(DWS) database, see "SQL Reference > Keyword" in the Data Warehouse Service (DWS) Developer Guide.
    +

    dbadmin

    +

    Administrator Password

    +

    Set the password of the database administrator account.

    +
    The password complexity requirements are as follows:
    • Consists of 8 to 32 characters.
    • Cannot be the username or the username spelled backwards.
    • Must contain at least three of the following character types: uppercase letters, lowercase letters, digits, and special characters (~!`?,.:;-_'"(){}[]/<>@#%^&*+|\=)
    • Passes the weak password check.
    +
    +
    NOTE:

    Change the password regularly and keep it secure.

    +
    +

    -

    +

    Confirm Password

    +

    Enter the database administrator password again.

    +

    -

    +

    Database Port

    +

    Specify the port used when the client or application connects to the database in the cluster.

    +

    The port number ranges from 8000 to 30000.

    +

    8000

    +
    +
    +
    +

  7. Configure network parameters.

    Figure 3 Configuring the network
    +
    +
    + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 5 Network parameters

    Parameter

    +

    Description

    +

    Example Value

    +

    VPC

    +

    Specify a virtual private network for nodes in a cluster to isolate networks of different services.

    +

    If you create a data warehouse cluster for the first time and have not configured the VPC, click View VPC. On the VPC management console that is displayed, create a VPC that satisfies your needs.

    +

    For details about how to create a VPC, see "VPC and Subnet > Creating a VPC" in the Virtual Private Cloud User Guide.

    +

    After selecting a VPC from the drop-down list, click View VPC to enter the VPC management console and view the detailed information about the VPC.

    +

    You can click to refresh the options in the VPC drop-down list.

    +

    vpc-dws

    +

    Subnet

    +

    Specify a VPC subnet.

    +

    A subnet provides dedicated network resources that are isolated from other networks, improving network security.

    +

    subnet-dws

    +

    Security Group

    +

    Specify a VPC security group.

    +

    A security group restricts access rules to enhance security when GaussDB(DWS) and other services access each other.

    +
    • Automatic creation

      If Automatic creation is selected, the system automatically creates a default security group. This option is selected by default.

      +

      The rule of the default security group is as follows: The outbound allows all access requests, while the inbound is open only to the database port that you set to connect to the GaussDB(DWS) cluster.

      +

      The format of the default security group name is dws-<Cluster_name>-<Cluster_database_port>, for example, dws-dws-demo-8000.

      +
      NOTE:

      If the quotas of the security group and the security group rule are insufficient, an error message will be displayed after you submit the cluster creation application. Select an existing group and retry.

      +
      +
    • Manual creation

      You can also log in to the VPC management console to manually create a security group. Then, go back to the page for creating data warehouse clusters, click the button next to the Security Group drop-down list to refresh the page, and select the new security group.

      +

      To enable the GaussDB(DWS) client to connect to the cluster, you need to add an inbound rule to the new security group to grant the access permission to the database port of the data warehouse cluster. The following is an example of an inbound rule..

      +
      • Protocol: TCP
      • Port: 8000. Use the database port number when you create the cluster for receiving GaussDB(DWS) client connections.
      • Source: Select IP address and use the host IP address of the client host, for example, 192.168.0.10/32.
      +

      The security group of a cluster cannot be changed but can be modified. For details, see Modifying a Security Group.

      +
    +

    Automatic creation

    +

    Public Network Access

    +

    Specify whether users can use a client to connect to a cluster's database over the Internet. The following methods are supported:

    +
    • Do not use: The EIP is not required.
    • Automatically assign: Specify the EIP bandwidth, and an EIP with dedicated bandwidth will be bound to the cluster. The EIP can be used to access the cluster over the Internet. The name of an automatically assigned EIP starts with the cluster name.
    • Specify: A specified EIP is bound to the cluster. If no available EIPs are displayed in the drop-down list, click Create EIP to go to the Elastic IP page and create an EIP that satisfies your needs. You can set the bandwidth as needed.
    +
    NOTE:
    • If you use the EIP binding function for the first time in each project of each region, the system prompts you to create the DWSAccessVPC agency to authorize GaussDB(DWS) to access VPC. After the authorization is successful, GaussDB(DWS) can switch to a healthy VM when the VM bound with the EIP becomes faulty.
    • Only cloud accounts or users with Security Administrator permissions can create agencies by default. IAM users under an account do not have the permission for creating agencies by default. Contact a user with the permission and complete the authorization on the current page.
    • Do not use indicates disabling access to the cluster over the public network. After a cluster is created, if you want to access it over the public network, bind an EIP to the cluster and create a public network domain name. For details, see Creating a Public Network Domain Name.
    +
    +

    Automatically assign

    +

    Bandwidth

    +

    When EIP is set to Automatically assign, you need to specify the bandwidth of the EIP, which ranges from 1 Mbit/s to 100 Mbit/s.

    +

    50 Mbit/s

    +
    +
    +
    +

  8. 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 default.

    An enterprise project facilitates project-level management and grouping of cloud resources and users.

    +

    You can select the default enterprise project (default) or other existing enterprise projects. To create an enterprise project, log in to the Enterprise Management console. For details, see the Enterprise Management User Guide.

    +

    The enterprise project of the discount package must be the same as that of the cluster. All projects applies to any cluster.

    +
    +

  9. Configure advanced settings. Select Default to keep the default values of the advanced parameters. You can also select Custom to modify the values.

    Figure 4 Custom advanced parameters
    +
    • CNs

      CNs receive access requests from the clients and return the execution results. In addition, a CN splits and distributes tasks to the DNs for parallel execution.

      +

      The value ranges from 2 to the number of cluster nodes minus 1. The maximum value is 5 and the default value is 2. In a large-scale cluster, you are advised to deploy multiple CNs.

      +
    • Parameter Template

      A parameter template is a set of parameters for data warehouses. You need to select a parameter template from the drop-down list of Parameter Template and associate it with the cluster during cluster creation. You can select the default parameter template or a customized parameter template. By default, the cluster is associated with the default database parameter template.

      +

      For details about parameter templates, see Managing Parameter Templates.

      +
    • Tag

      A tag is a key-value pair used to identify a cluster. For details about the keys and values, see Table 6. By default, no tag is added to the cluster.

      +

      For more information about tags, see Overview.

      + +
      + + + + + + + + + + + + + +
      Table 6 Tag parameters

      Parameter

      +

      Description

      +

      Example Value

      +

      Tag key

      +

      You can perform the following operations:

      +
      • Select a predefined tag key or an existing resource tag key from the drop-down list of the text box.
        NOTE:

        To add a predefined tag, you need to create one on TMS and select it from the drop-down list of Tag key. You can click View predefined tags to enter the Predefined Tags page of TMS. Then, click Create Tag to create a predefined tag. For more information, see Management > Predefined Tags > Creating Predefined Tags in the Tag Management Service User Guide.

        +
        +
      +
      • Enter a tag key in the text box. The tag key can contain a maximum of 36 characters and cannot be an empty string.

        Only digits, letters, underscores (_), and hyphens (-) are allowed.

        +
        NOTE:

        A key must be unique in a given cluster.

        +
        +
        +
      +

      key01

      +

      Tag value

      +

      You can perform the following operations:

      +
      • Select a predefined tag value or resource tag value from the drop-down list of the text box.
      • Enter a tag value in the text box. The tag key can contain a maximum of 43 characters and cannot be an empty string.

        Only digits, letters, underscores (_), periods (.), and hyphens (-) are allowed.

        +

        +
      +

      value01

      +
      +
      +
    +

  10. Click Create Now. The Confirm page is displayed.

    If the number of requested nodes, vCPU (cores), or memory (GB) exceeds the user's remaining quota, a warning dialog box is displayed, indicating that the quota is insufficient and displaying the details of the remaining quota and the current quota application. You can click Increase quota in the warning dialog box to submit a service ticket and apply for higher node quota.

    +

    For details about quotas, see What Is the User Quota?.

    +
    +

  11. Click Submit.

    After the submission is successful, the creation starts. Click Back to Cluster List to go back to the Clusters page. The initial status of the cluster is Creating. Cluster creation takes some time. Clusters in the Available state are ready for use.

    +

+
+
+
+
+
Parent topic: Cluster Configuration
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_0020.html b/docs/dws/umn/dws_01_0020.html new file mode 100644 index 00000000..955ee1d5 --- /dev/null +++ b/docs/dws/umn/dws_01_0020.html @@ -0,0 +1,175 @@ + + +

Checking the Cluster Status

+

On the Clusters page of the GaussDB(DWS) management console, you can view the general information about a cluster in the cluster list, such as the cluster status, task information, and node flavor.

+

Querying General Information of a Cluster

Log in to the GaussDB(DWS) management console. In the navigation pane, choose Clusters. The cluster list displays all clusters. If there are a large number of clusters, you can turn pages to view the clusters in any status.

+

Enter the cluster name in the search box, and click to search for a cluster. Alternatively, in the All projects drop-down list above the cluster list, select the target project. Click to refresh the cluster list. You can also click Search by Tag to search for clusters based on the criteria. For details, see Searching for Clusters Based on Tags.

+

Clusters are listed in chronological order by default, with the most recent clusters displayed at the top. Table 1 lists the cluster list parameters.

+
Figure 1 Cluster list
+ +
+ + + + + + + + + + + + + + + + + + + + + + +
Table 1 Cluster list parameters

Parameter

+

Description

+

Cluster Name

+

Cluster name specified when a cluster is created.

+

Cluster Status

+

Cluster running status. For details, see Cluster Status.

+

Task Information

+

Cluster task status. For details, see Cluster Task Information.

+

Node Flavor

+

Node flavors of clusters. For details about the node flavors, see Table 3.

+

Enterprise Project

+

Enterprise project to which a cluster belongs.

+

Operation

+		 +
+
+
+

Cluster Status

+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 2 Cluster status description

Status

+

Description

+

Available

+

Indicates that the cluster runs properly.

+

Read-only

+

A cluster goes into this state when the disk usage of the cluster or a single node in the cluster is greater than 90%. The cluster can still work in this state but supports only query operations. Write operations are not supported. When the cluster status becomes read-only, contact technical support engineers.

+

After the read-only status is canceled for the cluster, you are advised to perform the following operations:

+
  • Use the SQL client tool to connect to the database as the database administrator and run the following command to periodically clear and reclaim the storage space:
    VACUUM FULL;
    +

    After you delete data stored in GaussDB(DWS) data warehouses, dirty data may be generated possibly because the disk space is not released. This results in disk space waste. It is recommended that the storage space be cleared periodically.

    +
  • You are advised to check the disk capacity and analyze whether the existing cluster specifications meet service requirements. If not, expand the cluster capacity. For details, see Cluster Scale-out.
+

Unbalanced

+

If the role of a GTM or DN in the cluster is different from the initial role, the cluster is in the Unbalanced state. In the Unbalanced state, the number of primary instances on some nodes increases. As a result, the load pressure is high. In this case, the cluster is normal, but the overall performance is not as good as that in a balanced state. You are advised to switch a cluster to the Available state during off-peak hours.

+

Redistributing

+

A cluster goes into this state when it detects that the service data on the original nodes is significantly larger than that on the new node after a new node is added to the cluster. In this case, the system automatically redistributes data on all nodes. The cluster can still work in this state.

+

Redistribution failed

+

A cluster goes into this state when data redistribution fails, but no data loss occurs. The cluster can still work in this state. You are advised to contact technical support.

+

Degraded

+

A cluster goes into this state when some nodes in the cluster are faulty, but the whole cluster runs properly. You are advised to contact technical support.

+

Unavailable

+

A cluster goes into this state when it cannot provide database services. You are advised to contact technical support.

+

Creating

+

A cluster goes into this state when it is being created.

+

Creation failed

+

A cluster goes into this state when it fails to be created.

+

Creating, restoring

+

A cluster goes into this state when it is being restored from a snapshot.

+
+
+
+

Cluster Task Information

+
+ + + + + + + + + + + + + + + + + + + + + + + + + +
Table 3 Task information description

Status

+

Description

+

Creating snapshot

+

Indicates that a snapshot is being created in the cluster.

+

Snapshot creation failed

+

Indicates that a snapshot fails to be created.

+

Configuring

+

Indicates that the system is storing modifications of cluster parameters.

+

Restarting

+

Indicates that a cluster is being restarted.

+

Restart failed

+

Indicates that a cluster fails to be restarted.

+

Resizing

+

Indicates that a cluster is being resized.

+

Resize failed

+

Indicates that a cluster fails to be resized.

+
+
+
+
+
+
+
Parent topic: Clusters
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_0021.html b/docs/dws/umn/dws_01_0021.html new file mode 100644 index 00000000..63434efb --- /dev/null +++ b/docs/dws/umn/dws_01_0021.html @@ -0,0 +1,70 @@ + + +

Viewing Snapshot Information

+

This section describes how to view snapshot information on the Snapshots page.

+

Viewing Snapshot Information

  1. Log in to the GaussDB(DWS) management console.
  2. In the navigation pane on the left, choose Snapshots.

    In the snapshot list, all snapshots are displayed by default. Click next to the snapshot name to display the snapshot details.

    +

    +

  3. You can view Snapshot Name, Snapshot Status, Cluster Name, Snapshot Type, and Snapshot Created of snapshots.

    You can also enter a snapshot name or cluster name in the upper right corner of the snapshot list and click to search for the specified snapshot. GaussDB(DWS) supports fuzzy search.

    +

    Table 1 describes snapshot status.

    + +
    + + + + + + + + + + + + + +
    Table 1 Snapshot status

    Status

    +

    Description

    +

    Available

    +

    Indicates that the existing snapshot works properly.

    +

    Creating

    +

    Indicates that a snapshot is being created.

    +

    Unavailable

    +

    Indicates that the existing snapshot cannot provide services.

    +
    +
    +

    Table 2 describes the snapshot types.

    + +
    + + + + + + + + + + +
    Table 2 Snapshot types

    Type

    +

    Description

    +

    Manual

    +

    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.

    +

    Automated

    +

    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.

    +
    +
    +

+
+
+
+
+
Parent topic: Snapshots
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_0022.html b/docs/dws/umn/dws_01_0022.html new file mode 100644 index 00000000..cbbfd79e --- /dev/null +++ b/docs/dws/umn/dws_01_0022.html @@ -0,0 +1,516 @@ + + +

Monitoring Clusters Using Cloud Eye

+

Function

This section describes how to check cluster metrics on Cloud Eye. By monitoring cluster running metrics, you can identify the time when the database cluster is abnormal and analyze potential activity problems based on the database logs, improving database performance. This section describes the metrics that can be monitored by Cloud Eye as well as their namespaces and dimensions. You can use the management console or APIs provided by Cloud Eye to query the monitoring metrics and alarms generated by GaussDB(DWS). For details, see the User Guide and API Reference of Cloud Eye.

+

This section is organized as follows:

+ +
+

Namespace

SYS.DWS

+
+

Cluster Monitoring Metrics

With the GaussDB(DWS) monitoring metrics provided by Cloud Eye, you can obtain information about the cluster running status and performance. This information will provide a better understanding of the node-level information.

+

Table 1 describes GaussDB(DWS) monitoring metrics.

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 GaussDB(DWS) monitoring metrics

Metric ID

+

Name

+

Description

+

Value Range

+

Monitored Object

+

Monitoring Period (Raw Data)

+

dws001_shared_buffer_hit_ratio

+

Cache Hit Ratio

+

Percentage of data volume obtained from memory, expressed in percentage

+

0% to 100%

+

Data warehouse cluster

+

4 minutes

+

dws002_in_memory_sort_ratio

+

In-memory Sort Ratio

+

Percentage of data volume that is sorted in memory, expressed in percentage

+

0% to 100%

+

Data warehouse cluster

+

4 minutes

+

dws003_physical_reads

+

File Reads

+

Total number of database file reads

+

> 0

+

Data warehouse cluster

+

4 minutes

+

dws004_physical_writes

+

File Writes

+

Total number of database file writes

+

> 0

+

Data warehouse cluster

+

4 minutes

+

dws005_physical_reads_per_second

+

File Reads per Second

+

Number of database file reads per second

+

≥ 0

+

Data warehouse cluster

+

4 minutes

+

dws006_physical_writes_per_second

+

File Writes per Second

+

Number of database file writes per second

+

≥ 0

+

Data warehouse cluster

+

4 minutes

+

dws007_db_size

+

Data Volume

+

Total size of data in the database, in MB

+

≥ 0 MB

+

Data warehouse cluster

+

4 minutes

+

dws008_active_sql_count

+

Active SQL Count

+

Number of active SQLs in the database

+

≥ 0

+

Data warehouse cluster

+

4 minutes

+

dws009_session_count

+

Session Count

+

Number of sessions that access the database

+

≥ 0

+

Data warehouse cluster

+

4 minutes

+

dws010_cpu_usage

+

CPU Usage

+

CPU usage of each node in a cluster, in percentage

+

0% to 100%

+

Data warehouse node

+

1 minute

+

dws011_mem_usage

+

Memory Usage

+

Memory usage of each node in a cluster, in percentage

+

0% to 100%

+

Data warehouse node

+

1 minute

+

dws012_iops

+

IOPS

+

Number of I/O requests processed by each node in the cluster per second

+

≥ 0

+

Data warehouse node

+

1 minute

+

dws013_bytes_in

+

Network Input Throughput

+

Data input to each node in the cluster per second over the network

+

Unit: byte/s

+

≥ 0 bytes/s

+

Data warehouse node

+

1 minute

+

dws014_bytes_out

+

Network Output Throughput

+

Data sent to the network per second from each node in the cluster

+

Unit: byte/s

+

≥ 0 bytes/s

+

Data warehouse node

+

+

1 minute

+

dws015_disk_usage

+

Disk Usage

+

Disk usage of each node in a cluster, in percentage

+

0% to 100%

+

Data warehouse node

+

1 minute

+

dws016_disk_total_size

+

Total Disk Size

+

Total disk space of each node in the cluster

+

Unit: GB

+

100 to 2000 GB

+

Data warehouse node

+

1 minute

+

dws017_disk_used_size

+

Used Disk Space

+

Used disk space of each node in the cluster

+

Unit: GB

+

0 to 3600 GB

+

Data warehouse node

+

1 minute

+

dws018_disk_read_throughput

+

Disk Read Throughput

+

Data volume read from each disk in the cluster per second

+

Unit: byte/s

+

≥ 0 bytes/s

+

Data warehouse node

+

1 minute

+

dws019_disk_write_throughput

+

Disk Write Throughput

+

Data volume written to each disk in the cluster per second

+

Unit: byte/s

+

≥ 0 bytes/s

+

Data warehouse node

+

1 minute

+

dws020_avg_disk_sec_per_read

+

Average Time per Disk Read

+

Average time used each time when a disk reads data

+

Unit: second

+

> 0s

+

Data warehouse node

+

1 minute

+

dws021_avg_disk_sec_per_write

+

Average Time per Disk Write

+

Average time used each time when data is written to a disk

+

Unit: second

+

> 0s

+

Data warehouse node

+

1 minute

+

dws022_avg_disk_queue_length

+

Average Disk Queue Length

+

Average I/O queue length of a disk

+

≥ 0

+

Data warehouse node

+

1 minute

+
+
+
+

Dimensions

+
+ + + + + + + + + + +

Key

+

Value

+

datastore_id

+

Data warehouse cluster ID

+

dws_instance_id

+

Data warehouse node ID

+
+
+
+

Cluster and Node Monitoring Information

  1. Log in to the GaussDB(DWS) management console.
  2. View the cluster information. In the cluster list, click View Metric in the Operation column where a specific cluster resides. The Cloud Eye management console is displayed. By default, the cluster monitoring information on the Cloud Eye management console is displayed.

    Additionally, you can specify a specific monitoring metric and the time range to view the performance curve.

    +

  3. View the node information. Click to return to the Cloud Eye management console. On the Data Warehouse Nodes tab page, you can view metrics of each node in the cluster.

    Additionally, you can specify a specific monitoring metric and the time range to view the performance curve.

    +

    Cloud Eye also supports the ability to compare the monitoring metrics of multiple nodes. For details, see Comparing the Monitoring Metrics of Multiple Nodes.

    +

+
+

Comparing the Monitoring Metrics of Multiple Nodes

  1. In the left navigation pane of the Cloud Eye management console, choose Dashboard > Panels.
  2. On the page that is displayed, click Create Panel. In the displayed dialog box, enter the name and click OK.
  3. Click Add Graph in the upper right corner.
  4. In the displayed dialog box, configure the title and monitoring metrics.

    You can add multiple monitoring metrics by clicking Add Metric.

    +
    +

    The following describes how to set parameters if you want to compare CPU usage of two nodes.

    + +
    + + + + + + + + + + + + + + + + +
    Table 2 Configuration example

    Parameter

    +

    Example Value

    +

    Resource Type

    +

    DWS

    +

    Dimension

    +

    Data Warehouse Node

    +

    Monitored Object

    +

    dws-demo-dws-cn-cn-2-1

    +

    dws-demo-dws-cn-cn-1-1

    +

    dws-demo-dws-dn-1-1

    +

    Metric

    +

    CPU Usage

    +
    +
    +

  5. Click OK.

    Then you can view the corresponding monitoring graph on the Panels page. Move the cursor to the graph and click in the upper right corner to zoom in the graph and view detailed metric comparison data.

    +

+
+

Creating Alarm Rules

Setting GaussDB(DWS) alarm rules allows you to customize the monitored objects and notification policies and determine the running status of your GaussDB(DWS) at any time.

+

A GaussDB(DWS) alarm rule includes the alarm rule name, monitored object, metric, threshold, monitoring interval, and whether to send a notification. This section describes how to set GaussDB(DWS) alarm rules.

+
  1. Log in to the GaussDB(DWS) management console.
  2. In the navigation pane on the left, choose Clusters.
  3. Locate the row containing the target cluster, click More > View Metric in the Operation column to enter the Cloud Eye management console and view the GaussDB(DWS) monitoring information.

    The status of the target cluster must be Available. Otherwise, you cannot create alarm rules.

    +

    +

  4. In the left navigation pane of the Cloud Eye management console, choose Alarm Management > Alarm Rules.
  5. On the Alarm Rules page, click Create Alarm Rule in the upper right corner.

    +

  6. On the Create Alarm Rule page, set parameters as prompted.

    1. Configure the rule name and description.

      +
    2. Configure the alarm parameters as prompted.

      +

      + +
      + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
      Table 3 Configuring alarm parameters

      Parameter

      +

      Description

      +

      Example Value

      +

      Resource Type

      +

      Name of the cloud service resource for which the alarm rule is configured.

      +

      Data Warehouse Service

      +

      Dimension

      +

      Metric dimension of the alarm rule. You can select Data Warehouse Nodes or Data Warehouses.

      +

      Data Warehouse Node

      +

      Monitoring Scope

      +

      Resource scope to which an alarm rule applies. Select Specific resources and select one or more monitoring objects. Select the ID of the cluster instance or node you have created. Click to synchronize the monitoring objects to the right pane.

      +

      Specific resources

      +

      Method

      +

      Select Use template or Create manually as required.

      +
      • If no alarm template is available, set Method to Create manually and configure related parameters to create an alarm rule.
      • If you have available alarm rule templates, set Method to Use template, so that you can use a template to quickly create alarm rules.
      +

      Create manually

      +

      Template

      +

      This parameter is valid only when Use template is selected.

      +

      Select the template to be imported. If no alarm template is available, click Create Custom Template to create one that meets your requirements.

      +

      -

      +

      Alarm Policy

      +

      This parameter is valid only when Create manually is selected.

      +

      Set the policy that triggers an alarm. For example, trigger an alarm if the CPU usage equals to or is greater than 80% for 3 consecutive periods.

      +

      Table 1 describes the GaussDB(DWS) monitoring metrics.

      +

      -

      +

      Alarm Severity

      +

      Severity of an alarm. Valid values are Critical, Major, Minor, and Informational.

      +

      Major

      +
      +
      +
    3. Configure the alarm notification parameters as prompted.
      +
      + + + + + + + + + + + + + + + + + +
      Table 4 Configuring alarm notifications

      Parameter

      +

      Description

      +

      Example Value

      +

      Alarm Notification

      +

      Whether to notify users when alarms are triggered. Notifications can be sent as emails or text messages, or HTTP/HTTPS requests sent to the servers.

      +

      You can enable (recommended) or disable Alarm Notification.

      +

      Enable

      +

      Notification Object

      +

      Name of the topic to which the alarm notification is sent.

      +

      If you enable Alarm Notification, you need to select a topic. If no desired topics are available, create one first, whereupon the SMN service is invoked. For details about how to create a topic, see the Simple Message Notification User Guide.

      +

      -

      +

      Trigger Condition

      +

      Condition for triggering the alarm. You can select Generated alarm, Cleared alarm, or both.

      +

      -

      +
      +
      +
      +
    4. After the configuration is complete, click Next.

      After the alarm rule is created, if the metric data reaches the specified threshold, Cloud Eye will immediately inform you that an exception has occurred.

      +
    +

+
+
+
+
+
Parent topic: Monitoring and Alarms
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_0023.html b/docs/dws/umn/dws_01_0023.html new file mode 100644 index 00000000..4fcde45f --- /dev/null +++ b/docs/dws/umn/dws_01_0023.html @@ -0,0 +1,30 @@ + + +

Cluster Scale-out

+

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).

+

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 VACUUM command to reclaim the storage space first. If the used storage capacity is still high after you run the VACUUM command, you can scale out your cluster. For details about VACUUM, see "SQL Reference > SQL Syntax > VACUUM" in the Data Warehouse Service (DWS) Developer Guide.

+

Impact on the System

+
+

Prerequisites

+
+

Scaling Out a Cluster

  • A cluster becomes read-only during scale-out. Exercise caution when performing this operation.
  • To ensure data security, create a manual snapshot before scaling. For details about how to create a snapshot, see Manually Creating a Snapshot.
+
+
  1. Log in to the GaussDB(DWS) management console.
  2. Choose Clusters.

    All clusters are displayed by default.

    +

  3. In the Operation column of the target cluster, choose More > Scale Out.

    On the page that is displayed, the Automated Backup button is enabled by default.

    +

    +

  4. Specify the number of nodes to be added.

    • 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.

      If the node quota is insufficient, click Increase quota to submit a service ticket and apply for higher node quota.

      +
    • Flavor of the new nodes must be the same as that of existing nodes in the cluster.
    • The VPC, subnet, and security group of the cluster with new nodes added are the same as those of the original cluster.
    +

  5. Configure advanced parameters. If you choose Custom, you can enable Online Scale-out and Auto Redistribution, and set Redistribution Mode to Online. Click OK if a message is prompted.

    If you choose Default, Online Scale-out will be disabled, Auto Redistribution will be enabled, and Redistribution Mode will be Offline by default.

    +

  6. Click Next: Confirm.
  7. Click Scale Out Now.

    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 Increase quota in the warning dialog box to submit a service ticket and apply for higher node quota.

    +

    For details about quotas, see What Is the User Quota?.

    +
    +

  8. Click Submit.

    • After you submit the scale-out application, task information of the cluster changes to Scaling out and the process will take several minutes. During the scale-out, the cluster automatically restarts. Therefore, the cluster status will stay Unavailable for a while. After the cluster is restarted, the status will change to Available. In the last phase of scale-out, the system dynamically redistributes user data in the cluster, during which the cluster is in the Read-only state.
    • A cluster is successfully scaled out only when the cluster is in the Available state and task information Scaling out is not displayed. Then you can use the cluster.
    • If Scale-out failed is displayed, the cluster fails to be scaled out.
    +

+
+
+
+
+
Parent topic: Clusters
+
+
+ diff --git a/docs/dws/umn/dws_01_0024.html b/docs/dws/umn/dws_01_0024.html new file mode 100644 index 00000000..16218be9 --- /dev/null +++ b/docs/dws/umn/dws_01_0024.html @@ -0,0 +1,18 @@ + + +

Cluster Restart

+

If a cluster is in the Unbalanced 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.

+

Impact on the System

+
+

Procedure

  1. Log in to the GaussDB(DWS) management console.
  2. Click Clusters.
  3. In the Operation column of the cluster to be restarted, click Restart.
  4. In the dialog box that is displayed, click Yes.

    Task Information changes to Restarting. When Cluster Status changes to Available again, the cluster is successfully restarted.

    +

+
+
+
+
+
Parent topic: Clusters
+
+
+ diff --git a/docs/dws/umn/dws_01_0025.html b/docs/dws/umn/dws_01_0025.html new file mode 100644 index 00000000..caae6f42 --- /dev/null +++ b/docs/dws/umn/dws_01_0025.html @@ -0,0 +1,28 @@ + + +

Deleting Clusters

+

If you do not need to use a cluster, perform the operations in this section to delete it.

+

Impact on the System

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.

+
+

Deleting a Cluster

  1. Log in to the GaussDB(DWS) management console.
  2. Click in the upper left corner of the management console to select a region.
  3. On the Clusters page, locate the cluster to be deleted.
  4. Locate the row that contains the target cluster, and choose More > Delete.

    +

  5. In the displayed dialog box, confirm the deletion. You can determine whether to perform the following operations:

    • Create a snapshot for the cluster.

      If the cluster status is normal, you can click Create Snapshot. In the dialog box that is displayed, enter the snapshot name and click OK to create a snapshot for the cluster to be deleted. After the snapshot is created, go back to the Clusters page and delete the cluster.

      +
    • Release the EIP bound to the cluster.

      If the cluster is bound with an EIP, you can click Release the EIP bound to the cluster to release the EIP of the cluster to be deleted.

      +
    +

    +

  6. Click Yes.

    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.

    +

+
+
+
+
+
Parent topic: Clusters
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_0026.html b/docs/dws/umn/dws_01_0026.html new file mode 100644 index 00000000..355deaa8 --- /dev/null +++ b/docs/dws/umn/dws_01_0026.html @@ -0,0 +1,26 @@ + + +

Password Reset

+

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 Clusters 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 failed_login_attempts parameter on the Parameter Modifications tab of the cluster. For details, see Modifying Database Parameters.

+

Resetting a Password

  1. Log in to the GaussDB(DWS) management console.
  2. Choose Clusters.
  3. In the Operation column of the target cluster, choose More > Reset Password.

    Figure 1 Password resetting
    +

  4. On the displayed Reset Password page, set a new password, confirm the password, and then click OK.

    The password complexity requirements are as follows:
    • Contains 8 to 32 characters.
    • Cannot be the username or the username spelled backwards.
    • Must contain at least three of the following character types: uppercase letters, lowercase letters, digits, and special characters (~!`?,.:;-_'"(){}[]/<>@#%^&*+|\=)
    • Passes the weak password check.
    +
    +
    • Cannot be the same as the old password and cannot be the reverse of the old password.
    • Cannot use a historical password.
    +

    If the default cluster administrator account is deleted or renamed, password resetting fails.

    +
    +

+
+
+
+
+
Parent topic: Clusters
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_0028.html b/docs/dws/umn/dws_01_0028.html new file mode 100644 index 00000000..e30b1e12 --- /dev/null +++ b/docs/dws/umn/dws_01_0028.html @@ -0,0 +1,26 @@ + + +

Manually Creating a Snapshot

+

Prerequisites

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 Snapshots page to back up cluster data.

+

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.

+
  • Manual snapshots can be backed up to OBS.
  • Snapshots can be created only for clusters in Available, Read-only, or Unbalanced state.
+
+
+

Impact on the System

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.

+

To ensure the integrity of snapshot data, do not write data during snapshot creation.

+
+
+

Procedure

  1. Log in to the GaussDB(DWS) management console.
  2. In the navigation pane, choose Snapshots.
  3. Click Create Snapshot and enter snapshot information.

    • Cluster Name: Select a GaussDB(DWS) cluster from the drop-down list. The drop-down list only displays clusters that are in the Available state.
    • Snapshot Name: 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 (_).
    • Snapshot Description: Enter the snapshot information. This parameter is optional. Snapshot information contains 0 to 256 characters and does not support the following special characters: !<>'=&"
    +
    Figure 1 Creating a snapshot
    +

  4. Click OK.

    The task status of the cluster for which you are creating a snapshot is Creating snapshot. The status of the snapshot that is being created is Creating. After the snapshot is created, its status becomes Available.

    +

    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 How Can I Clear and Reclaim Storage?

    +
    +

+
+
+
+
+
Parent topic: Manual Snapshots
+
+
+ diff --git a/docs/dws/umn/dws_01_0029.html b/docs/dws/umn/dws_01_0029.html new file mode 100644 index 00000000..bfa3f550 --- /dev/null +++ b/docs/dws/umn/dws_01_0029.html @@ -0,0 +1,58 @@ + + +

Restoring a Snapshot to a New Cluster

+

Scenario

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.

+

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.

+

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.

+
  • Currently, you can only use the snapshots stored in OBS to restore data to a new cluster.
  • By default, the new cluster created during restoration has the same specifications and node quantity as the original cluster.
  • Restoring data to a new cluster does not affect the services running in the original cluster.
  • If cold and hot tables are used, snapshots cannot be used to restore cold data to a new cluster.
+
+
+

Prerequisites

+
+

Procedure

  1. Log in to the GaussDB(DWS) management console.
  2. In the navigation pane, choose Snapshots. All snapshots are displayed by default.
  3. In the Operation column of a snapshot, click Restore.

    +

  4. Configure the parameters of the new cluster, as shown in the following figure.

    +

    +

    You can modify cluster parameters. For details, see Table 1. By default, other parameters are the same as those in the snapshot. For details, see Table 2.

    + +
    + + + + + + + + + + +
    Table 1 Parameters for the new cluster

    Category

    +

    Operation

    +

    Basic

    +

    Configure the region, AZ, node flavor, cluster name, database port, VPC, subnet, security group, public access, and enterprise project.

    +

    Advanced settings

    +
    If Custom is selected, configure the following parameters:
    • If Automated Snapshot is enabled, you can configure the following parameters:
      • Retention Days
      • Start Time
      • Execution Period
      +
    • Parameter Template
    • Tag: If encryption is enabled for the original cluster, you can configure a key name.
    +
    +
    +
    +

  5. Click Restore to go to the confirmation page.
  6. Click Submit to restore the snapshot to the new cluster.

    When the status of the new cluster changes to Available, the snapshot is restored.

    +

    After the snapshot is restored, the private network address and EIP (if EIP is set to Automatically assign) are automatically assigned.

    +

    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 Increase quota in the warning dialog box to submit a service ticket and apply for higher node quota.

    +

    For details about quotas, see What Is the User Quota?.

    +
    +

+
+
+
+
+
Parent topic: Restoration Using a Snapshot
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_0030.html b/docs/dws/umn/dws_01_0030.html new file mode 100644 index 00000000..e7ce35b8 --- /dev/null +++ b/docs/dws/umn/dws_01_0030.html @@ -0,0 +1,26 @@ + + +

Deleting Manual Snapshots

+

On the Snapshots page, you can delete a snapshot in the Unavailable state or delete an available snapshot to release the storage space.

+

Deleted snapshots cannot be restored. Exercise caution when performing this operation.

+
+

Procedure

  1. Log in to the GaussDB(DWS) management console.
  2. In the navigation pane, choose Snapshots. All snapshots are displayed by default.
  3. In the Operation column of the snapshot that you want to delete, click Delete.

    You can delete snapshots that are manually created only.

    +
    +
    +

  4. In the dialog box that is displayed, confirm the information and click Yes to delete the snapshot.

    +

+
+
+
+
+
Parent topic: Manual Snapshots
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_0031.html b/docs/dws/umn/dws_01_0031.html new file mode 100644 index 00000000..049456d0 --- /dev/null +++ b/docs/dws/umn/dws_01_0031.html @@ -0,0 +1,70 @@ + + +

Downloading the Client

+

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.

+

The client tool package contains the following:

+ +

Downloading the Client

  1. Log in to the GaussDB(DWS) console. For details, see Accessing the GaussDB(DWS) Management Console.
  2. In the navigation pane on the left, click Connections.
  3. Select the GaussDB(DWS) client of the corresponding version from the drop-down list of gsql CLI Client.

    Choose a corresponding client version according to the cluster version and operating system to which the client is to be installed.

    +
    • The Redhat x86_64 client can be used on the following OSs:
      • RHEL 6.4 to RHEL 7.6
      • CentOS 6.4 to CentOS 7.4
      • EulerOS 2.3
      +
    • The SUSE x86_64 client can be used on the following OSs:
      • SLES 11.1 to SLES 11.4
      • SLES 12.0 to SLES 12.3
      +
    +
    Figure 1 Downloading a gsql client
    +

  4. Click Download to download the gsql tool matching the current cluster version. Click Historical Version to download the gsql tool corresponding to the cluster version.

    If clusters of different versions are available, you will download the gsql tool matching the earliest cluster version after clicking Download. If there is no cluster, you will download the gsql tool of the earliest version after clicking Download. GaussDB(DWS) clusters are compatible with earlier versions of gsql tools.

    +
    • In the cluster list on the Clusters page, click the name of the specified cluster and click the Basic Information tab to view the cluster version.
    +
    +

    Table 1 lists the files and folders in the downloaded tool package.

    + +
    + + + + + + + + + + + + + + + + + + + +
    Table 1 Files and folders in the downloaded tool package

    File or Folder

    +

    Description

    +

    bin

    +

    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 "Server Tool".

    +

    gds

    +

    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.

    +

    lib

    +

    This folder contains the lib library required for executing the gsql client.

    +

    sample

    +

    This folder contains the following directories and files:

    +
    • setup.sh: script file for configuring the AK/SK before using gsql to import sample data
    • tpcds_load_data_from_obs.sql: script file for importing the TPC-DS sample data using the gsql client
    • query_sql directory: script file for querying the TPC-DS sample data
    +

    gsql_env.sh

    +

    Script file for configuring environment variables before running the gsql client.

    +
    +
    +

+
+
+
+
+
Parent topic: Using the gsql CLI Client to Connect to a Cluster
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_0032.html b/docs/dws/umn/dws_01_0032.html new file mode 100644 index 00000000..1c6ff132 --- /dev/null +++ b/docs/dws/umn/dws_01_0032.html @@ -0,0 +1,25 @@ + + +

Downloading the JDBC or ODBC Driver

+

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.

+

Open-Source JDBC or ODBC Driver

GaussDB(DWS) also supports open-source JDBC and ODBC drivers: PostgreSQL JDBC 9.3-1103 or later; PostgreSQL ODBC 09.01.0200 or later

+
+

Downloading the JDBC or ODBC Driver

  1. Log in to the GaussDB(DWS) management console.
  2. In the navigation pane on the left, click Connections.
  3. In the Driver area, choose a driver that you want to download.

    • JDBC Driver

      Select DWS JDBC Driver and click Download 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 Download. If there is no cluster, you will download the JDBC driver of the earliest version after clicking Download. GaussDB(DWS) clusters are compatible with earlier versions of JDBC drivers.

      +

      Click Historical Version to download the corresponding JDBC driver version. You are advised to download the JDBC driver based on the cluster version.

      +

      The JDBC driver can be used on all platforms and depends on JDK 1.6 or later.

      +
    • ODBC Driver

      Select a corresponding version and click Download 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 Download. If there is no cluster, you will download the ODBC driver of the earliest version after clicking Download. GaussDB(DWS) clusters are compatible with earlier versions of ODBC drivers.

      +

      Click Historical Version to download the corresponding ODBC driver version. You are advised to download the ODBC driver based on the cluster version.

      +

      The ODBC driver is applicable to the following operating systems only:

      +
      • Windows Server 2008 or Windows 7 or later
      • x86 servers: RHEL 6.4 to RHEL 7.6
      • x86 servers: CentOS 6.4 to CentOS 7.4
      • x86 servers: SUSE 11.1 to SUSE 11.4; SUSE 12.0 to SUSE 12.3
      +

      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.

      +
      +
    +

+
+
+
+
+
Parent topic: Using the JDBC and ODBC Drivers to Connect to a Cluster
+
+
+ diff --git a/docs/dws/umn/dws_01_0033.html b/docs/dws/umn/dws_01_0033.html new file mode 100644 index 00000000..9c95834c --- /dev/null +++ b/docs/dws/umn/dws_01_0033.html @@ -0,0 +1,97 @@ + + +

Obtaining the Cluster Connection Address

+

Scenario

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 cloud platform, public network address on the Internet, and JDBC connection strings.

+

To obtain the cluster connection address, use either of the following methods:

+ +
+

Obtaining the Cluster Connection Address on the Connections Page

  1. Log in to the GaussDB(DWS) management console.
  2. In the navigation pane on the left, click Connections.
  3. In the Data Warehouse Connection Information area, select an available cluster.

    You can only select clusters in the Available state.

    +

    +
    Figure 1 Connection information
    +

  4. View and obtain the cluster connection information.

    • Private Network Address
    • Public Network Address
    • JDBC URL (Private Network)
    • JDBC URL (Public Network)
    • ODBC URL
    +
    • If no EIP is automatically assigned during cluster creation, Public Network Address 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 Bind EIP to bind one.
    • If an EIP is bound during cluster creation but you do not want to use the public network address to access the cluster, click Unbind EIP to unbind the EIP. After the EIP is unbound, Public Network Address is empty.
    +
    +

+
+

Obtaining the Cluster Access Addresses on the Basic Information Page

  1. Log in to the GaussDB(DWS) management console.
  2. In the navigation tree on the left, click Clusters.
  3. In the cluster list, click the name of the target cluster. The Basic Information page is displayed.
  4. In the Database Attribute area, view and obtain the cluster's access address information, including the private network address and public network address.

    +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Database attribute parameters

    Parameter

    +

    Description

    +

    Default Database

    +

    Database name specified when the cluster is created. When you connect to the cluster for the first time, connect to the default database.

    +

    Initial Administrator

    +

    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.

    +

    Port

    +

    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.

    +

    Connection String

    +

    Connection string. You can click View Details to check the data warehouse connection information. Its value can be:

    +
    • JDBC URL (Private Network). In the private network environment, you can use the JDBC URL (private network) to connect to the cluster when developing applications.
    • JDBC URL (Public Network). In the public network environment, you can use the JDBC URL (public network) to connect to the cluster when developing applications.
    • ODBC URL. 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.
    +

    ELB Address

    +

    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.

    +

    Private Network Domain Name

    +

    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 ClusterName.dws.otc-tsi.de. When you access a data warehouse cluster using a domain name, the domain name resolver provides the load balancing function.

    +
    NOTE:

    If the cluster name does not comply with the domain name standards, the prefix of the default access domain name will be adjusted accordingly.

    +
    +

    You can click Modify 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.

    +

    For details, see Managing Access Domain Names.

    +

    Private Network IP Address

    +

    IP address for accessing the database in the cluster over the private network.

    +
    NOTE:
    • A private IP address is automatically generated when you create a cluster. The IP address is fixed.
    • The number of private IP addresses equals the number of CNs. You can log in to any node to connect to the cluster.
    • If you access a fixed IP address over the internal network, all the workloads will be processed on a single CN.
    +
    +

    Public Network Domain Name

    +

    Name of the domain for accessing the database in the cluster over the public network.

    +

    For details, see Managing Access Domain Names.

    +

    Public Network IP Address

    +

    IP address for accessing the database in the cluster over the public network.

    +
    NOTE:
    • If no EIP is assigned during cluster creation and Public Network IP Address is empty, click Bind EIP to bind an EIP to the cluster.
    • If an EIP is bound during cluster creation, click Unbind EIP to unbind the EIP.
    +
    +
    +
    +
    +

+
+
+
+
+
Parent topic: Cluster Connection
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_0035.html b/docs/dws/umn/dws_01_0035.html new file mode 100644 index 00000000..3a065b1b --- /dev/null +++ b/docs/dws/umn/dws_01_0035.html @@ -0,0 +1,16 @@ + + +

Read-only Status

+

No database operation is allowed on a read-only cluster. Cancel the read-only status on the management console.

+

Impact on the System

+
+

Canceling Read-only Status

  1. Log in to the GaussDB(DWS) management console.
  2. Click Clusters.

    All clusters are displayed by default.

    +

  3. In the Operation column of the target cluster, choose More > Cancel Readonly.
  4. In the dialog box that is displayed, click OK to confirm and cancel the read-only status for the cluster.
+
+
+
+
+
Parent topic: Clusters
+
+
+ diff --git a/docs/dws/umn/dws_01_0037.html b/docs/dws/umn/dws_01_0037.html new file mode 100644 index 00000000..eea281b8 --- /dev/null +++ b/docs/dws/umn/dws_01_0037.html @@ -0,0 +1,66 @@ + + +

Using the gsql Client to Connect to a Cluster

+

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.

+

Using the gsql CLI Client to Connect to a Cluster

  1. Prepare a Linux ECS to install and run the gsql client.

    For details, see Preparing an ECS as the gsql Client Host.

    +

  2. Download the gsql client by referring to Downloading the Client, and use an SSH file transfer tool (such as WinSCP) to upload the client to a target Linux host.

    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.

    +

    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:

    +
    wget https://obs.otc.t-systems.com/dws/download/dws_client_redhat_x64.zip --no-check-certificate
    +

  3. Use the SSH tool to remotely log in to the host where the client is installed.

    For details about how to log in to an ECS, see "ECSs> Logging In to a Linux ECS > Login Using an SSH Password" in the Elastic Cloud Server User Guide.

    +

  4. (Optional) To connect to the cluster in SSL mode, configure SSL authentication parameters on the host where the client is installed. For details, see Establishing Secure TCP/IP Connections in SSL Mode.

    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.

    +
    +

  5. Run the following commands to decompress the client:

    cd <Path for saving the client>
+unzip dws_client_8.1.x_redhat_x64.zip
    +

    In the preceding commands:

    +
    • <Path_for_storing_the_client>: Replace it with the actual path.
    • dws_client_8.1.x_redhat_x64.zip: This is the client tool package name of RedHat x86. Replace it with the actual name.
    +

  6. Run the following command to configure the GaussDB(DWS) client:

    source gsql_env.sh
    +

    If the following information is displayed, the GaussDB(DWS) client is successfully configured:

    +
    All things done.
    +

  7. Connect to the database in the GaussDB(DWS) cluster using the gsql client. Replace the values of each parameter with actual values.

    gsql -d <Database_name> -h <Cluster_address> -U <Database_user> -p <Database_port> -r
    +

    The parameters are described as follows:

    +
    • Database_name: 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 gaussdb.
    • Cluster_address: For details about how to obtain this address, see Obtaining the Cluster Connection Address. If a public network address is used for connection, set this parameter to Public Network Address or Public Network Domain Name. If a private network address is used for connection, set this parameter to Private Network Address or Private Network Domain Name.
    • Database_user: 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, dbadmin.
    • Database_port: Enter the database port set during cluster creation.
    +

    For example, run the following command to connect to the default database gaussdb in the GaussDB(DWS) cluster:

    +
    gsql -d gaussdb -h 10.168.0.74 -U dbadmin -p 8000 -W password -r
    +

    If the following information is displayed, the connection succeeded:

    +
    1
    gaussdb=>
+
    + +
    +

+
+

gsql Command Reference

For more information about the gsql commands, see the Data Warehouse Service (DWS) Tool Guide.

+
+

(Optional) Importing TPC-DS Sample Data Using gsql

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.

+

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.

+
  1. 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 /opt directory is used as an example for storing the gsql client.

    cd /opt
    +

  2. Switch to the specified directory and set the AK and SK for importing sample data and the OBS access address.

    cd sample
+/bin/bash setup.sh -ak <Access_Key_Id> -sk <Secret_Access_Key> -obs_location obs.otc.t-systems.com
    +

    If the following information is displayed, the settings are successful:

    +
    setup successfully!
    +

    <Access_Key_Id> and <Secret_Access_Key>: indicate the AK and SK, respectively. For details about how to obtain the AK and SK, see "Data Import > Concurrently Importing Data from OBS > Creating Access Keys (AK and SK)" in the Data Warehouse Service (DWS) Developer Guide. Then, replace the parameters in the statements with the obtained values.

    +
    +

  3. Go back to previous directory and run the gsql environment variables.

    cd ..
+source gsql_env.sh
+cd bin
    +

  4. Import the sample data to the data warehouse.

    Command format:

    +
    gsql -d <Database name> -h <Public network address of the cluster> -U <Administrator> -p <Data warehouse port number> -f <Path for storing the sample data script> -r
    +

    Sample command:

    +
    gsql -d gaussdb -h 10.168.0.74 -U dbadmin -p 8000 -f /opt/sample/tpcds_load_data_from_obs.sql -r
    +

    In the preceding command, sample data script tpcds_load_data_from_obs.sql is stored in the sample directory (for example, /opt/sample/) of the GaussDB(DWS) client.

    +
    +

    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.

    +

    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.

    +
    Time:1845600.524 ms
    +

  1. In the Linux command window, run the following commands to switch to a specific directory and query the sample data:

    cd /opt/sample/query_sql/
+/bin/bash tpcds100x.sh
    +

  2. Enter the cluster's public network IP address, access port, database name, user who accesses the database, and password of the user as prompted.

    • The default database name is gaussdb.
    • Use the database administrator username and password configured during cluster creation as the username and password for accessing the database.
    +

    After the query is complete, a directory for storing the query result, such as query_output_20170914_072341, will be generated in the current query directory, for example, sample/query_sql/.

    +

+
+
+
+
+
Parent topic: Using the gsql CLI Client to Connect to a Cluster
+
+
+ diff --git a/docs/dws/umn/dws_01_0038.html b/docs/dws/umn/dws_01_0038.html new file mode 100644 index 00000000..7094db1a --- /dev/null +++ b/docs/dws/umn/dws_01_0038.html @@ -0,0 +1,143 @@ + + +

Establishing Secure TCP/IP Connections in SSL Mode

+
If the client or JDBC/ODBC driver needs to use SSL connection, you must configure related SSL connection parameters in the client or application code. The GaussDB(DWS) management console provides the SSL certificate required by the client. The SSL certificate contains the default certificate, private key, root certificate, and private key password encryption file required by the client. Download the SSL certificate to the host where the client resides and specify the path of the certificate on the client.

Using the default certificate may pose security risks. To improve system security, you are advised to periodically change the certificate to prevent password cracking. If you need to replace the certificate, contact the database customer service.

+
+
+

For more information about SSL certificates, see (Optional) Downloading the SSL Certificate. The following parts are included in this section:

+ +

Configuring Digital Certificate Parameters Related to SSL Authentication on the gsql Client

After a data warehouse cluster is deployed, the SSL authentication mode is enabled by default. The server certificate, private key, and root certificate have been configured by default. You need to configure the client parameters.

+
  1. Log in to the GaussDB(DWS) management console and click Connections to download the SSL certificate.

    For more information about SSL certificates, see (Optional) Downloading the SSL Certificate.

    +
    Figure 1 Downloading the SSL certificate file
    +

  2. Use a file transfer tool (such as WinSCP) to upload the SSL certificate to the host where the client is installed.

    For example, save the downloaded certificate dws_ssl_cert.zip to the /home/dbadmin/dws_ssl/ directory.

    +

  3. Use an SSH remote connection tool (such as PuTTY) to log in to the host where the gsql client is installed and run the following commands to go to the directory where the SSL certificate is stored and decompress the SSL certificate:

    cd /home/dbadmin/dws_ssl/
+unzip dws_ssl_cert.zip
    +

  4. Run the export command and configure digital certificate parameters related to SSL authentication on the host where the gsql client is installed.

    There are two SSL authentication modes: bidirectional authentication and unidirectional authentication. Different authentication modes require different client environment variables. For details, see SSL Authentication Modes and Client Parameters.

    +

    The following parameters must be configured for bidirectional authentication:

    +
    export PGSSLCERT="/home/dbadmin/dws_ssl/sslcert/client.crt"
+export PGSSLKEY="/home/dbadmin/dws_ssl/sslcert/client.key"
+export PGSSLMODE="verify-ca"
+export PGSSLROOTCERT="/home/dbadmin/dws_ssl/sslcert/cacert.pem"
    +

    The following parameters must be configured for unidirectional authentication:

    +
    export PGSSLMODE="verify-ca"
+export PGSSLROOTCERT="/home/dbadmin/dws_ssl/sslcert/cacert.pem"
    +
    • You are advised to use bidirectional authentication for security purposes.
    • The environment variables configured for a client must contain the absolute file paths.
    +
    +

  5. Change the client private key permissions.

    The permissions on the client's root certificate, private key, certificate, and encrypted private key file must be 600. If the permissions do not meet the requirement, the client cannot connect to the cluster in SSL mode.

    +
    chmod 600 client.key
+chmod 600 client.crt
+chmod 600 client.key.cipher
+chmod 600 client.key.rand
+chmod 600 cacert.pem
    +

+
+

SSL Authentication Modes and Client Parameters

There are two SSL authentication modes: bidirectional authentication and unidirectional authentication. Table Table 1 shows the differences between these two modes. You are advised to use bidirectional authentication for security purposes.

+ +
+ + + + + + + + + + + + + + + + +
Table 1 Authentication modes

Authentication Mode

+

Description

+

Environment Variables Configured on a Client

+

Maintenance

+

Bidirectional authentication (recommended)

+

The client verifies the server's certificate and the server verifies the client's certificate. The connection can be set up only after the verifications are successful.

+

Set the following environment variables:

+
  • PGSSLCERT
  • PGSSLKEY
  • PGSSLROOTCERT
  • PGSSLMODE
+

This authentication mode is applicable to scenarios that require high data security. When using this mode, you are advised to set the PGSSLMODE client variable to verify-ca for network data security purposes.

+

Unidirectional authentication

+

The client verifies the server's certificate, whereas the server does not verify the client's certificate. The server loads the certificate information and sends it to the client. The client verifies the server's certificate according to the root certificate.

+

Set the following environment variables:

+
  • PGSSLROOTCERT
  • PGSSLMODE
+

To prevent TCP-based link spoofing, you are advised to use the SSL certificate authentication. In addition to configuring the client root certificate, you are advised to set the PGSSLMODE variable to verify-ca on the client.

+
+
+

Configure environment variables related to SSL authentication on the client. For details, see Table 2.

+

The path of environment variables is set to /home/dbadmin/dws_ssl/ as an example. Replace it with the actual path.

+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + +
Table 2 Client parameters

Environment Variable

+

Description

+

Value Range

+

PGSSLCERT

+

Specifies the certificate files for a client, including the public key. Certificates prove the legal identity of the client and the public key is sent to the remote end for data encryption.

+
The absolute path of the files must be specified, for example:
export PGSSLCERT='/home/dbadmin/dws_ssl/sslcert/client.crt'
+
+

(No default value)

+

PGSSLKEY

+

Specifies the client private key file used to decrypt the digital signatures and the data encrypted using the public key.

+
The absolute path of the files must be specified, for example:
export PGSSLKEY='/home/dbadmin/dws_ssl/sslcert/client.key'
+
+

(No default value)

+

PGSSLMODE

+

Specifies whether to negotiate with the server about SSL connection and specifies the priority of the SSL connection.

+

Values and meanings:

+
  • disable: only tries to establish a non-SSL connection.
  • allow: tries to establish a non-SSL connection first, and then an SSL connection if the first attempt fails.
  • prefer: tries to establish an SSL connection first, and then a non-SSL connection if the first attempt fails.
  • require: only tries to establish an SSL connection. If there is a CA file, perform the verification according to the scenario in which the parameter is set to verify-ca.
  • verify-ca: tries to establish an SSL connection and check whether the server certificate is issued by a trusted CA.
  • verify-full: GaussDB(DWS) does not support this mode.
+

Default value: prefer

+

PGSSLROOTCERT

+

Specifies the root certificate file for issuing client certificates. The root certificate is used to verify the server certificate.

+
The absolute path of the files must be specified, for example:
export PGSSLROOTCERT='/home/dbadmin/dws_ssl/sslcert/certca.pem'
+
+

Default value: null

+

PGSSLCRL

+

Specifies the certificate revocation list file, which is used to check whether a server certificate is in the list. If the certificate is in the list, it is invalid.

+
The absolute path of the files must be specified, for example:
export PGSSLCRL='/home/dbadmin/dws_ssl/sslcert/sslcrl-file.crl'
+
+

Default value: null

+
+
+
+
+
+
+
Parent topic: Using the gsql CLI Client to Connect to a Cluster
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_0039.html b/docs/dws/umn/dws_01_0039.html new file mode 100644 index 00000000..f13f59ae --- /dev/null +++ b/docs/dws/umn/dws_01_0039.html @@ -0,0 +1,148 @@ + + +

Managing Database Connections

+

Scenario

By default, a database supports a certain number of connections. Administrators can manage database connections to learn about the connection performance of the current database or increase the connection limit so that more users or applications can connect to the database at the same time.

+
+

Maximum Number of Connections

The number of connections supported by a cluster depends on its node flavor.

+ +
+ + + + + + + + + + + + + + + + + + + +
Table 1 Number of supported connections

Parameter

+

Node Flavor

+

Number of CN Connections

+

Number of DN Connections

+

max_connections

+

+

+

vCPUs < 16

+

512

+

Number of CN connections x 2

+

vCPUs > 16 && <= 32

+

1024

+

Number of CN connections x 2

+

other

+

2048

+

Number of CN connections x 2

+
+
+

The policies of comm_max_stream, poolsize, and max_prepared_transactions are the same as those of max_connections.

+
+
+

Viewing the Maximum Number of Connections

  1. Use the SQL client tool to connect to the database in a cluster.
  2. Run the following command:

    1
    SHOW max_connections;
+
    + +
    +

    Information similar to the following is displayed, showing that the maximum number of database connections is 200 by default.

    +
    max_connections
+----------------- 
+200
+(1 row)
    +

+
+

Viewing the Number of Used Connections

  1. Use the SQL client tool to connect to the database in a cluster.
  2. View the number of connections in scenarios described in Table 2.

    +

    + + + + + + + + + + + + + + + + + + + +
    Table 2 Viewing the number of connections

    Description

    +

    Command

    +

    View the maximum number of sessions connected to a specific user.

    +

    Run the following command to view the maximum number of sessions connected to user dbadmin.

    +
    1
    SELECT ROLNAME,ROLCONNLIMIT FROM PG_ROLES WHERE ROLNAME='dbadmin';
+
    + +
    +

    Information similar to the following is displayed. -1 indicates that the number of sessions connected to user dbadmin is not limited.

    +
     rolname  | rolconnlimit
+----------+--------------
+ dwsadmin |           -1
+(1 row)
    +

    View the number of session connections that have been used by a user.

    +

    Run the following command to view the number of session connections that have been used by dbadmin.

    +
    1
    SELECT COUNT(*) FROM V$SESSION WHERE USERNAME='dbadmin';
+
    + +
    +

    Information similar to the following is displayed. 1 indicates the number of session connections used by user dbadmin.

    +
     count
+-------
+     1
+(1 row)
    +

    View the maximum number of sessions connected to a specific database.

    +

    Run the following command to view the upper limit of connections used by gaussdb.

    +
    1
    SELECT DATNAME,DATCONNLIMIT FROM PG_DATABASE WHERE DATNAME='gaussdb';
+
    + +
    +

    Information similar to the following is displayed. -1 indicates that the number of sessions connected to database gaussdb is not limited.

    +
     datname  | datconnlimit
+----------+--------------
+ gaussdb |           -1
+(1 row)
    +

    View the number of session connections that have been used by a database.

    +

    Run the following command to view the number of session connections that have been used by gaussdb.

    +
    1
    SELECT COUNT(*) FROM PG_STAT_ACTIVITY WHERE DATNAME='gaussdb';
+
    + +
    +

    Information similar to the following is displayed. 1 indicates the number of session connections used by database gaussdb.

    +
     count 
+-------
+     1
+(1 row)
    +

    View the number of session connections that have been used by all users.

    +

    Run the following command to view the number of session connections that have been used by all users:

    +
    1
    SELECT COUNT(*) FROM V$SESSION;
+
    + +
    +

    Information similar to the following is displayed.

    +
     count
+-------
+     10
+(1 row)
    +
    +
    +

+
+
+
+
+
Parent topic: Cluster Connection
+
+
+ diff --git a/docs/dws/umn/dws_01_0055.html b/docs/dws/umn/dws_01_0055.html new file mode 100644 index 00000000..1e0fa763 --- /dev/null +++ b/docs/dws/umn/dws_01_0055.html @@ -0,0 +1,19 @@ + + +

Importing Data from MRS to GaussDB(DWS)

+

Importing Data from MRS to a Data Warehouse Cluster

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 MapReduce Service User Guide.

+

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.

+
+

Import Process

Perform the following operations to import data from MRS to a data warehouse cluster:

+
  1. In the data warehouse cluster, create an MRS data source connection according to Creating an MRS Data Source Connection.
    • 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.
    +
    +
  2. Create an HDFS foreign table for querying data from the MRS cluster over APIs of a foreign server.

    For details, see "Data Import > Importing Data from MRS to a Cluster" in the Data Warehouse Service (DWS) Developer Guide.

    +
  3. (Optional) When the HDFS configuration of the MRS cluster changes, update the MRS data source configuration on GaussDB(DWS). For details, see Updating the MRS Data Source Configuration.
+
+
+
+
+
Parent topic: MRS Data Sources
+
+
+ diff --git a/docs/dws/umn/dws_01_0057.html b/docs/dws/umn/dws_01_0057.html new file mode 100644 index 00000000..fd9df6eb --- /dev/null +++ b/docs/dws/umn/dws_01_0057.html @@ -0,0 +1,19 @@ + + +

MRS Data Sources

+
+
+ + +
+
Parent topic: Clusters
+
+
+ diff --git a/docs/dws/umn/dws_01_0059.html b/docs/dws/umn/dws_01_0059.html new file mode 100644 index 00000000..ed04f73a --- /dev/null +++ b/docs/dws/umn/dws_01_0059.html @@ -0,0 +1,68 @@ + + +

Creating an MRS Data Source Connection

+

Scenario

Before GaussDB(DWS) reads data from MRS HDFS, you need to create an MRS data source connection that functions as a channel of transporting data warehouse cluster data and MRS cluster data.

+
+

Impact on the System

+
+

Prerequisites

+
+

Procedure

  1. Log in to the public cloud management console.
  2. Choose Service List > EI Enterprise Intelligence > MapReduce Service to enter the MRS management console and create a cluster.

    Configure parameters as required. For details, see "Cluster Operation Guide > Custom Creation of a Cluster" in the MapReduce Service User Guide.

    +
    • The AZ, VPC, and subnet of the MRS cluster must be the same as those of the data warehouse cluster.
    • Cluster Type must be Analysis Cluster.
    • Cluster Version supports MRS 1.9.2 (recommended).

      Cluster Version can also be set to 1.6.x, 1.7.x, 1.8.x, or 2.0.x.

      +
      +
    • In the Analysis Components area, select Hive, Tez, and Spark2x.
    +

    If you enable Kerberos authentication for an MRS cluster, use MRS Manager to create a user for interconnecting GaussDB(DWS) with the system after the MRS cluster is created. The user type must be Human-Machine and the user, user group hadoop, and role Manager_administrator must be bound together. The user password must be changed on the MRS Manager page after the user is created.

    +
    +

    If you already have a qualified MRS cluster, skip this step.

    +

  3. Choose Service List > EI Enterprise Intelligence > GaussDB(DWS).
  4. On the GaussDB(DWS) management console, click Clusters.
  5. In the cluster list, click the name of a cluster. On the page that is displayed, click the MRS Data Sources tab.
  6. Click Create MRS Cluster Connection and configure parameters.

    Figure 1 Creating an MRS data source
    + +
    + + + + + + + + + + + + + + + + +
    Table 1 MRS cluster connection parameters

    Parameter

    +

    Description

    +

    MRS Data Source

    +

    Specifies the MRS cluster to which GaussDB(DWS) can connect. By default, all available analytic MRS clusters that are in the same VPC and subnet as the current data warehouse cluster and in the Available state are displayed.

    +

    After you select an MRS cluster, the system automatically displays whether Kerberos authentication is enabled for the selected cluster. Click View MRS Cluster to view its detailed information.

    +

    If the MRS Data Source drop-down list is empty, click Create MRS Cluster to create an MRS cluster.

    +

    MRS Account

    +

    Specifies the account used when a data warehouse cluster connects to an MRS cluster. This parameter is available only when Kerberos authentication is selected for the MRS cluster.

    +

    Password

    +

    Specifies the password of the connection user. If you change the password, you need to create a connection again. This parameter is valid only for clusters with MRS Kerberos authentication enabled.

    +

    Description

    +

    Describes the connection.

    +
    +
    +

  7. Click OK to save the connection.

    Configuration Status turns to Creating. You can view the connection that is successfully created in the MRS data source list and the connection status is Available.

    +
    • In the Operation column, you can click Update Configurations to update MRS Cluster Status and Configuration Status. During configuration update, you cannot create a connection. The system checks whether the security group rule is correct. If the rule is incorrect, the system rectifies the fault. For details, see Updating the MRS Data Source Configuration.
    • In the Operation column, you can click Delete to delete the unnecessary connection. When deleting a connection, you need to manually delete the security group rule.
    +
    +

+
+
+
+
+
Parent topic: MRS Data Sources
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_0070.html b/docs/dws/umn/dws_01_0070.html new file mode 100644 index 00000000..d14aeaac --- /dev/null +++ b/docs/dws/umn/dws_01_0070.html @@ -0,0 +1,216 @@ + + +

Change History

+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Release Date

+

Description

+

2022-11-17

+

This issue is the twenty-sixth official release.

+

Added the following sections:

+

Performing a Primary/Standby Switchback

+

Associating and Disassociating ELB

+

Managing Cluster Workloads

+

CNs

+

Associating and Disassociating ELB

+

2021-12-30

+

This issue is the twenty-fifth official release.

+

Added the following sections:

+

Databases Monitoring

+

Alarms

+

2021-07-30

+

This issue is the twenty-fourth official release.

+

Added the following sections:

+ +

2020-11-03

+

This issue is the twenty-third official release.

+

Modified the following sections:

+ +

2019-09-30

+

This issue is the twenty-second official release.

+

Added the following sections:

+ +

Modified the following sections:

+ +

2019-03-30

+

This is the twenty-first official release.

+

Modified the following sections:

+ +

2019-03-29

+

This issue is the twentieth official release.

+

2019-03-11

+

This issue is the nineteenth official release.

+

Added the following section:

+ +

2019-01-29

+

This issue is the eighteenth official release.

+

Modified the following sections:

+ +

Deleted the following section. For related information, see "Data Import" in the Data Warehouse Service (DWS) Developer Guide.

+
  • Importing and Exporting Data
+

2018-12-24

+

This issue is the seventeenth official release.

+

Added the following sections:

+ +

Modified the following sections:

+ +

2018-11-12

+

This issue is the sixteenth official release.

+

Modified the following section:

+
  • Cluster Scale-out: Optimized the description of cluster status changes during scale-out.
+

2018-09-26

+

This issue is the fifteenth official release.

+

2018-09-15

+

This issue is the fourteenth official release.

+

Modified the following sections:

+ +

2018-09-05

+

This issue is the thirteenth official release.

+

Modified the following sections:

+ +

2018-08-29

+

This issue is the twelfth official release.

+

Modified the following sections:

+ +

Deleted the following section:

+
  • "gsql Client User Guide" has been released in the Data Warehouse Service (DWS) Tool Guide.
+

2018-08-22

+

This issue is the eleventh official release.

+

Modified the following sections:

+ +

2018-08-07

+

This issue is the tenth official release.

+

Modified the following sections:

+
  • Creating a Cluster: Added three KVM node flavors dws.d2.15xlarge, dws.d2.xlarge, and dws.m3.xlarge.
+

Added the following sections:

+ +

2018-06-21

+

This issue is the ninth official release.

+

2018-06-13

+

This is the eighth official release.

+

Modified the following sections:

+ +

Added the following sections:

+
  • Tag Management: Added the functions of adding tags to a cluster and searching for a cluster by tag.
  • 7.3.5-Using the gsql Client to Connect to a Cluster (SSL): Added the procedure for connecting the gsql to the cluster in SSL mode.
  • Using GDS to Import and Export Data: Described how to use GDS to import data from a remote server to GaussDB(DWS) and export data from GaussDB(DWS) to a remote server.
+

2018-02-12

+

This issue is the seventh official release.

+

Modified the following sections:

+
  • What Is GaussDB(DWS)?: Added basic functions and reference document links.
  • Related Services: Added the relationship description between MRS and GaussDB(DWS).
  • Cluster Scale-out: Optimized the description of prerequisites.
  • Cluster Restart: Optimized the impact of cluster restart on the system.
  • Step 3: Connecting to a Cluster: Deleted the procedure of configuring a security group for a cluster.
  • Creating a Cluster: Added the procedure of creating a default security group for a cluster.
  • Downloading the Client: Added the third-party open source PostgreSQL client.
+

Deleted the following content from this document. If you want to know more about the following content, see the Data Warehouse Service Database Developer Guide.

+
  • Managing Database Users
  • Managing Database Audit
  • Importing Data from OBS to a Data Warehouse Cluster
  • Exporting Data from a Data Warehouse Cluster to OBS
  • SQL on OBS
  • Clearing and Reclaiming the Storage Space
+

2017-12-29

+

This is the sixth official release.

+

The following topics are added:

+ +

Modified the following sections:

+ +

2017-11-01

+

This issue is the fifth official release.

+ +

2017-10-16

+

This issue is the fourth official release.

+ +

2017-09-30

+

This issue is the third official release.

+ +

2017-08-30

+

This issue is the second official release.

+ +

2017-08-07

+

This issue is the first official release.

+
+
+
+ diff --git a/docs/dws/umn/dws_01_0073.html b/docs/dws/umn/dws_01_0073.html new file mode 100644 index 00000000..87d90c2a --- /dev/null +++ b/docs/dws/umn/dws_01_0073.html @@ -0,0 +1,26 @@ + + +

Managing Clusters That Fail to Be Created

+

If a cluster fails to be created, you can go to the Clusters page of the GaussDB(DWS) management console to view the cluster status and the cause of failure.

+

Checking the Cause of a Creation Failure

  1. Log in to the GaussDB(DWS) management console and click Clusters in the left navigation pane on the left.
  2. In the cluster list, locate the cluster whose Cluster Status is Creation failed.

    Figure 1 Viewing clusters that fail to be created
    +

  3. Click in the Cluster Status column to view the cause of the creation failure.

    For details about the error codes, see "Error Code Reference". If the fault persists, contact technical support.

    +

+
+

Deleting a Cluster That Fails to Be Created

You can delete a cluster that fails to be created if you do not need it. Before deletion, check the cause of creation failure.

+
  1. Log in to the GaussDB(DWS) management console and click Clusters in the left navigation pane on the left.
  2. In the cluster list, locate the row containing the failed cluster to be deleted, and choose More > Delete.
  3. (Optional) If the cluster is bound with an EIP during creation, click Release the EIP bound with the cluster to release the EIP.
  4. In the dialog box that is displayed, click Yes to delete the cluster.

    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 when the cluster is deleted.

    +

+
+
+
+
+
Parent topic: Clusters
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_0074.html b/docs/dws/umn/dws_01_0074.html new file mode 100644 index 00000000..aae81dee --- /dev/null +++ b/docs/dws/umn/dws_01_0074.html @@ -0,0 +1,94 @@ + + +

Configuring Separation of Permissions

+

Scenario

By default, the administrator specified when you create a GaussDB(DWS) cluster is the database system administrator. The administrator can create other users and view the audit logs of the database. That is, separation of permissions is disabled.

+

GaussDB(DWS) supports role-based separation of permissions. In this way, different roles have different permissions and cluster data can be better protected.

+

For details about the default permissions mode and the separation of permissions mode, see "Database Security Management > Managing Users and Their Permissions > Separation of Permissions" in the Data Warehouse Service (DWS) Developer Guide.

+
+

Impact on the System

After you have modified the security parameters and the modifications take effect, the cluster may be restarted, which makes the cluster unavailable temporarily.

+
+

Prerequisites

To modify the cluster's security configuration, ensure that the following conditions are met:

+ +
+

Procedure

  1. Log in to the GaussDB(DWS) management console.
  2. In the navigation pane on the left, click Clusters.
  3. In the cluster list, click the name of a cluster. On the page that is displayed, click Security Settings.

    By default, Configuration Status is Synchronized, which indicates that the latest database result is displayed.

    +

  4. On the Security Settings page, configure separation of permissions.

    indicates that the function is enabled. When separation of permissions is enabled, configure the username and password for Security Administrator and Audit Administrator. Then the system automatically creates these two users. You can use these two users to connect to the database and perform database-related operations.

    +

    indicates that Rights Separation is disabled. Rights Separation is disabled by default.

    +
    Figure 1 Security configuration
    +
    +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Security parameters

    Parameter

    +

    Description

    +

    Example Value

    +

    Security Administrator

    +

    The username must meet the following requirements:

    +
    • Consists of lowercase letters, digits, or underscores.
    • Starts with a lowercase letter or an underscore.
    • Contains 6 to 64 characters.
    • Cannot be a keyword of the GaussDB(DWS) database. For details about the keywords of the GaussDB(DWS) database, see "SQL Syntax Reference > Keyword" in the Data Warehouse Service (DWS) Developer Guide.
    +

    security_admin

    +

    Password

    +
    The password complexity requirements are as follows:
    • Contains 8 to 32 characters.
    • Cannot be the username or the username spelled backwards.
    • Must contain at least three of the following character types: uppercase letters, lowercase letters, digits, and special characters (~!`?,.:;-_'"(){}[]/<>@#%^&*+|\=)
    • Passes the weak password check.
    +
    +

    -

    +

    Confirm Password

    +

    Enter the password of the security administrator again.

    +

    -

    +

    Audit Administrator

    +

    The username must meet the following requirements:

    +
    • Consists of lowercase letters, digits, or underscores.
    • Starts with a lowercase letter or an underscore.
    • Contains 6 to 64 characters.
    • Cannot be a keyword of the GaussDB(DWS) database. For details about the keywords of the GaussDB(DWS) database, see "SQL Syntax Reference > Keyword" in the Data Warehouse Service (DWS) Developer Guide.
    +

    audit_admin

    +

    Password

    +
    The password complexity requirements are as follows:
    • Contains 8 to 32 characters.
    • Cannot be the username or the username spelled backwards.
    • Must contain at least 3 of the following character types: uppercase letters, lowercase letters, digits, and special characters ~!@#%^&*()-_=+|[{}];:,<.>/?
    • Passes the weak password check.
    +
    +

    -

    +

    Confirm Password

    +

    Enter the password of the audit administrator again.

    +

    -

    +
    +
    +
    +

  5. Click Apply.
  6. In the displayed Save Configuration dialog box, select or deselect Restart the cluster and click Yes.

    • If you select Restart the cluster, the system saves the settings on the Security Settings page and restarts the cluster immediately. After the cluster is restarted, the security settings take effect immediately.
    • If you do not select Restart the cluster, the system only saves the settings on the Security Settings page. Later, you need to manually restart the cluster for the security settings to take effect.
    +

    After the security settings are complete, Configuration Status can be one of the following on the Security Settings page:

    +
    • Applying: The system is saving the settings.
    • Synchronized: The settings have been saved and taken effect.
    • Take effect after restart: The settings have been saved but have not taken effect. Restart the cluster for the settings to take effect.
    +

+
+
+
+
+
Parent topic: Cluster Security Management
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_0075.html b/docs/dws/umn/dws_01_0075.html new file mode 100644 index 00000000..2632b6a0 --- /dev/null +++ b/docs/dws/umn/dws_01_0075.html @@ -0,0 +1,122 @@ + + +

Configuring the Database Audit Logs

+

Prerequisites

Database audit logs are configured on the Security Settings page. You can change security settings only when the cluster status is Available and Unbalanced, and Task Information cannot be Creating snapshot, Resizing, Configuring, or Restarting.

+
+

Procedure

  1. Log in to the GaussDB(DWS) management console.
  2. Click Clusters.
  3. In the cluster list, click the name of a cluster. On the page that is displayed, click Security Settings.

    By default, Configuration Status is Synchronized, which indicates that the latest database results are displayed.

    +

  4. In the Audit Settings area, configure the audit log retention policy.

    Table 1 describes the detailed information.

    + +
    + + + + + + + + + + +
    Table 1 Audit log retention policy

    Parameter

    +

    Description

    +

    Audit Log Retention Policy

    +

    Specifies the audit log retention policy. Possible values are:

    +
    • Space priority: Audit logs will be automatically deleted if the size of audit logs on a single node exceeds 1 GB.
    • Time priority: Audit logs will be retained within the minimum retention period. After this period expires, audit logs will be automatically deleted if the size of audit logs on a single node exceeds 1 GB.
    +

    Space priority is preferred.

    +
    CAUTION:
    • Clusters 1.0.0 and 1.1.0 do not support audit log retention.
    • If the planned storage space of the database is limited, select Space priority to prevent faulty nodes or low performance caused by insufficient disk space.
    +
    +

    Minimum Retention Period (day)

    +

    This parameter is valid when Audit Log Retention Policy is set to Time priority.

    +

    The value ranges from 0 to 730 days. The default value is 90 days.

    +
    +
    +

  5. Enable the audit function for the following operations if necessary.

    Figure 1 Audit items
    +

    Table 2 describes the detailed information about the audit items.

    + +
    + + + + + + + + + + + + + + + + + + + + + + +
    Table 2 Audit items

    Parameter

    +

    Description

    +

    Audit Unauthorized Access

    +

    Specifies whether to record unauthorized operations. This parameter is disabled by default.

    +

    Audit DML Execution

    +

    Specifies whether to record INSERT, UPDATE, and DELETE operations on tables. This parameter is disabled by default.

    +

    Audit SELECT Execution

    +

    Specifies whether to record the SELECT operation. This parameter is disabled by default.

    +

    Audit Stored Procedure Execution

    +

    Specifies whether to record operations when executing the stored procedure or user-defined functions. This parameter is disabled by default.

    +

    Audit COPY Execution

    +

    Specifies whether to record the COPY operation. This parameter is disabled by default.

    +

    Audit DDL Execution

    +

    Specifies whether to record the CREATE, DROP, and ALTER operations of specified database objects. DATABASE, SCHEMA, and USER are selected by default.

    +

    +
    +
    +

    Except the audit items listed in Table 2, key audit items in Table 3 are enabled by default on GaussDB(DWS).

    + +
    + + + + + + + + + + + + + + + +
    Table 3 Key audit items

    Parameter

    +

    Description

    +

    Key audit items

    +

    Records successful and failed logins and logout.

    +

    Records database startup, stop, recovery, and switchover.

    +

    Records user locking and unlocking.

    +

    Records the grants and reclaims of user permissions.

    +

    Records the audit function of the SET operation.

    +
    +
    +

  6. Enable or disable audit log dumps.

    For more information, see Enabling Audit Log Dumps.

    +

  7. Click Apply.

    Click . The configuration status Applying indicates that the configurations are being saved.

    +

    When the status changes to Synchronized, the configurations are saved and take effect.

    +

+
+
+
+
+
Parent topic: Audit Logs
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_0076.html b/docs/dws/umn/dws_01_0076.html new file mode 100644 index 00000000..d9b8c9b3 --- /dev/null +++ b/docs/dws/umn/dws_01_0076.html @@ -0,0 +1,194 @@ + + +

(Optional) Configuring SSL Connection

+

GaussDB(DWS) supports connections in SSL authentication mode so that data transmitted between the GaussDB(DWS) client and the database can be encrypted. The SSL mode delivers higher security than the common mode. By default, the SSL function is enabled in a cluster to allow SSL or non-SSL connections from the client. For security purposes, you are advised to enable SSL connection. If you want to use SSL connection, enable Require SSL Connection for the cluster.

+

On the Security Settings page of the cluster, you can enable or disable Require SSL Connection.

+
  • After you have changed the security setting parameters and the settings take effect, the cluster may be restarted, which makes the cluster unavailable temporarily.
  • To modify the cluster's security configuration, ensure that the following conditions are met:
    • The cluster status is Available or Unbalanced.
    • The value of Task Information cannot be Creating snapshot, Resizing, Configuring, or Restarting.
    +
+
+

The following parts are included in this section:

+ +

Configuring SSL Connection

  1. Log in to the GaussDB(DWS) management console.
  2. In the navigation pane on the left, click Clusters.
  3. In the cluster list, click the name of a cluster. On the page that is displayed, click Security Settings.

    By default, Configuration Status is set to Synchronized, which indicates that the latest database result is displayed.

    +

  4. In the SSL Connection area, enable Require SSL Connection (recommended).

    indicates that the server requires SSL connection.

    +

    indicates that no SSL connection is required (default).

    +
    Figure 1 SSL connection
    +
    • If the gsql client or ODBC driver provided by GaussDB(DWS) is used, GaussDB(DWS) supports the TLSv1.2 SSL protocol.
    • If the JDBC driver provided by GaussDB(DWS) is used, GaussDB(DWS) supports SSL protocols, such as SSLv3, TLSv1, TLSv1.1, and TLSv1.2. The SSL protocol used between the client and the database depends on the Java Development Kit (JDK) version used by the client. Generally, JDK supports multiple SSL protocols.
    +
    +

  5. Click Apply.

    The system automatically saves the SSL connection settings. On the Security Settings page, Configuration Status is Applying. After Configuration Status changes to Synchronized, the settings have been saved and taken effect.

    +

+
+

Combinations of SSL Connection Parameters on the Client and Server

Whether the client uses the SSL encryption connection mode and whether to verify the server certificate depend on client parameter sslmode and server (cluster) parameters ssl and require_ssl. The parameters are described as follows:

+ +

The combinations of client parameter sslmode and server parameters ssl and require_ssl are as follows.

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 Combinations of SSL connection parameters on the client and server

ssl (Server)

+

sslmode (Client)

+

require_ssl (Server)

+

Result

+

on

+

disable

+

on

+

The server requires SSL, but the client disables SSL for the connection. As a result, the connection cannot be set up.

+

disable

+

off

+

The connection is not encrypted.

+

allow

+

on

+

The connection is encrypted.

+

allow

+

off

+

The connection is not encrypted.

+

prefer

+

on

+

The connection is encrypted.

+

prefer

+

off

+

The connection is encrypted.

+

require

+

on

+

The connection is encrypted.

+

require

+

off

+

The connection is encrypted.

+

verify-ca

+

on

+

The connection is encrypted and the server certificate is verified.

+

verify-ca

+

off

+

The connection is encrypted and the server certificate is verified.

+

off

+

disable

+

on

+

The connection is not encrypted.

+

disable

+

off

+

The connection is not encrypted.

+

allow

+

on

+

The connection is not encrypted.

+

allow

+

off

+

The connection is not encrypted.

+

prefer

+

on

+

The connection is not encrypted.

+

prefer

+

off

+

The connection is not encrypted.

+

require

+

on

+

The client requires SSL, but SSL is disabled on the server. Therefore, the connection cannot be set up.

+

require

+

off

+

The client requires SSL, but SSL is disabled on the server. Therefore, the connection cannot be set up.

+

verify-ca

+

on

+

The client requires SSL, but SSL is disabled on the server. Therefore, the connection cannot be set up.

+

verify-ca

+

off

+

The client requires SSL, but SSL is disabled on the server. Therefore, the connection cannot be set up.

+
+
+
+
+
+
+
Parent topic: Using the gsql CLI Client to Connect to a Cluster
+
+
+ diff --git a/docs/dws/umn/dws_01_0077.html b/docs/dws/umn/dws_01_0077.html new file mode 100644 index 00000000..d687de70 --- /dev/null +++ b/docs/dws/umn/dws_01_0077.html @@ -0,0 +1,572 @@ + + +

Using a JDBC Driver to Connect to a Database

+

In GaussDB(DWS), you can use a JDBC driver to connect to a database on Linux or Windows. The driver can connect to the database through an ECS on the cloud platform or over the Internet.

+

When using the JDBC driver to connect to the data warehouse cluster, determine whether to enable SSL authentication. SSL authentication is used to encrypt communication data between the client and the server. It safeguards sensitive data transmitted over the Internet. You can download a self-signed certificate file on the GaussDB(DWS) management console. To make the certificate take effect, you must configure the client program using the OpenSSL tool and the Java keytool.

+

The SSL mode delivers higher security than the common mode. You are advised to enable SSL connection when using JDBC to connect to a GaussDB(DWS) cluster.

+
+

For details about how to use the JDBC API, see the official documentation.

+

Prerequisites

+
+

Using a JDBC Driver to Connect to a Database

The procedure for connecting to the database using a JDBC driver in a Linux environment is similar to that in a Windows environment. The following describes the connection procedure in a Windows environment.

+
  1. Determine whether you want to use the SSL mode to connect to the GaussDB(DWS) cluster.

    +

  2. (Optional) On Linux, use WinSCP to upload the downloaded SSL certificate file to the Linux environment.
  3. Configure the certificate to enable SSL connection.

    1. Download the OpenSSL toolkit for Windows at https://slproweb.com/products/Win32OpenSSL.html. OpenSSL 3.0.0 is currently not supported. Download Win64 OpenSSL v1.1.1L Light instead.
    2. Double-click the installation package Win64OpenSSL_Light-1_1_1L.exe and install it to the default path on drive C. Copy the DLLs to the OpenSSL directory, as shown in the following figure. Retain the default settings in the remaining steps until the installation is successful.

      +
    3. Install an environment variable. Click Start in the lower left corner of the local PC, right-click This PC, choose More > Properties > View advanced system settings. Switch to the Advanced tab and click Environment Variables.

      +
    4. In the System variables area, double-click Path and click New in the window displayed. Add the OpenSSL bin path to the last line, for example, C:\Program Files\OpenSSL-Win64\bin, and click OK. Click OK again and the variable is configured successfully.

      +
    5. Decompress the package to obtain the certificate file. Decompression path C:\ is used as an example.

      You are advised to store the certificate file in a path of the English version and can specify the actual path when configuring the certificate. If the path is incorrect, a message stating that the file does not exist will be prompted.

      +
    6. Open Command Prompt and switch to the C:\dws_ssl_cert\sslcert path. Run the following commands to import the root license to the truststore:
      openssl x509 -in cacert.pem -out cacert.crt.der -outform der
+keytool -keystore mytruststore -alias cacert -import -file cacert.crt.der
      +
      • cacert.pem indicates the root certificate obtained after decompression.
      • cacert.crt.der indicates the generated intermediate file. You can store the file to another path and change the file name to your desired one.
      • mytruststore indicates the generated truststore name and cacert indicates the alias name. Both parameters can be modified.
      +

      Enter the truststore password as prompted and answer y.

      +

      +
    7. Convert the format of the client private key.
      openssl pkcs12 -export -out client.pkcs12 -in client.crt -inkey client.key
      +

      Enter the client private key password Gauss@MppDB. Then enter and confirm the self-defined private key password.

      +
    8. Import the private key to the keystore.
      keytool -importkeystore -deststorepass Gauss@MppDB -destkeystore client.jks -srckeystore client.pkcs12 -srcstorepass Password -srcstoretype PKCS12 -alias 1
      +
      • In the preceding command, Password is an example. Replace it with the actual password.
      • If information similar to the following is displayed and no error is reported, the import is successful. The target key file client.jks will be generated in C:\dws_ssl_cert\sslcert.

        +

        +

        +
      +
      +
    +

  4. Decompress the downloaded JDBC driver to obtain gsjdbc4.jar.
  5. Add the JAR file to the application project so that applications can reference the JAR file.

    Take the Eclipse project as an example. Store the JAR file to the project directory, for example, the lib directory in the project directory. In the Eclipse project, right-click the JAR file in the lib directory and choose Build Path to reference the JAR file.

    +
    Figure 1 Referencing a JAR file
    +

  6. Load the driver.

    The following methods are available:

    +
    • Using a code: Class.forName("org.postgresql.Driver");
    • Using a parameter during the JVM startup: java -Djdbc.drivers=org.postgresql.Driver jdbctest
    +

    The JDBC driver package downloaded on GaussDB(DWS)contains gsjdbc.jar.

    +
    • gsjdbc4.jar: The gsjdbc4.jar driver package is compatible with PostgreSQL. Its class names and class structures are the same as those of the PostgreSQL driver. Applications that run in PostgreSQL can be directly migrated to the current system.
    +
    +

  7. Call the DriverManager.getConnection() method of JDBC to connect to GaussDB(DWS) databases.

    The JDBC API does not provide the connection retry capability. You need to implement the retry processing in the service code.

    +

    DriverManager.getConnection() methods:

    +
    • DriverManager.getConnection(String url);
    • DriverManager.getConnection(String url, Properties info);
    • DriverManager.getConnection(String url, String user, String password);
    + +
    + + + + + + + + + + + + + + + + +
    Table 1 Database connection parameters

    Parameter

    +

    Description

    +

    url

    +

    Specifies the database connection descriptor, which can be viewed on the management console. For details, see Obtaining the Cluster Connection Address.

    +

    The URL format is as follows:

    +
    • jdbc:postgresql:database
    • jdbc:postgresql://host/database
    • jdbc:postgresql://host:port/database
    • jdbc:postgresql://host:port[,host:port][...]/database
    +
    NOTE:
    • If gsjdbc200.jar is used, change jdbc:postgresql to jdbc:gaussdb.
      • database indicates the name of the database to be connected.
      • host indicates the name or IP address of the database server.

        If the connected GaussDB(DWS) server and cluster are on the same network, use a private IP address. Otherwise, use a public IP address.

        +
      • port indicates the port number of the database server. By default, the database running on port 8000 of the local host is connected.
      • Multiple IP addresses and ports can be configured. JDBC balances load by random access and failover, and will automatically ignore unreachable IP addresses.

        Separate multiple pairs of IP addresses and ports by commas (,). Example: jdbc:postgresql://10.10.0.13:8000,10.10.0.14:8000/database

        +
      +
    • If JDBC is used to connect to a cluster, only JDBC connection parameters can be configured in a cluster address. Variables cannot be added.
    +
    +

    info

    +

    Specifies database connection properties. Common properties include the following:

    +
    • user: a string type. It indicates the database user who creates the connection task.
    • password: a string type. It indicates the password of the database user.
    • ssl: a boolean type. It indicates whether to use the SSL connection.
    • loggerLevel: string type. It indicates the volume of log data sent to the LogStream or LogWriter specified in the DriverManager. Currently, OFF, DEBUG, and TRACE are supported. DEBUG indicates that only logs of DEBUG or a higher level are printed, generating little log information. TRACE indicates that logs of the DEBUG and TRACE levels are displayed, generating detailed log information. The default value is OFF, indicating that no logs will be displayed.
    • prepareThreshold: integer type. It indicates the number of PreparedStatement executions required before requests are converted to prepared statements in servers. The default value is 5.
    • batchMode: boolean type. It indicates whether to connect the database in batch mode.
    • fetchsize: integer type. It indicates the default fetch size for statements in the created connection.
    • ApplicationName: string type. It indicates an application name. The default value is PostgreSQL JDBC Driver.
    • allowReadOnly: boolean type. It indicates whether to enable the read-only mode for connection. The default value is false. If the value is not changed to true, the execution of connection.setReadOnly does not take effect.
    • blobMode: string type. It is used to set the setBinaryStream method to assign values to different data types. The value on indicates that values are assigned to the BLOB data type and off indicates that values are assigned to the BYTEA data type. The default value is on.
    • connectionExtraInfo: boolean type. This parameter indicates whether the JDBC driver reports the driver deployment path and process owner to the database.
      NOTE:

      The value can be true or false. The default value is true. If connectionExtraInfo is set to true, the JDBC driver reports the driver deployment path and process owner to the database and displays the information in the connection_info parameter. In this case, you can query the information from PG_STAT_ACTIVITY or PGXC_STAT_ACTIVITY.

      +
      +
    +

    user

    +

    Specifies the database user.

    +

    password

    +

    Specifies the password of the database user.

    +
    +
    +

    The following describes the sample code used to encrypt the connection using the SSL certificate:

    +
     1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+19
+20
+21
+22
+23
+24
+25
+26
+27
+28
+29
+30
+31
+32
+33
+34
+35
+36
+37
+38
+39
+40
+41
+42
+43
+44
+45
+46
    // The following code obtains the database SSL connection operation and encapsulates the operation as an API.
+public static Connection GetConnection(String username, String passwd)
+    {
+        //Define the driver class.
+        String driver = "org.postgresql.Driver";
+         //Set keyStore.
+        System.setProperty("javax.net.ssl.trustStore", "mytruststore");
+        System.setProperty("javax.net.ssl.keyStore", "client.jks");
+        System.setProperty("javax.net.ssl.trustStorePassword", "password");
+        System.setProperty("javax.net.ssl.keyStorePassword", "password");
+
+        Properties props = new Properties();
+        props.setProperty("user", username);
+        props.setProperty("password", passwd);
+        props.setProperty("ssl", "true");
+
+        String  url = "jdbc:postgresql://" + "10.10.0.13" + ':'
+                    + "8000" + '/'
+                    + "gaussdb";
+        Connection conn = null;
+        
+        try
+        {
+            //Load the driver.
+            Class.forName(driver);
+        }
+        catch( Exception e )
+        {
+            e.printStackTrace();
+            return null;
+        }
+        
+        try
+        {
+             //Create a connection.
+            conn = DriverManager.getConnection(url, props );
+            System.out.println("Connection succeed!");
+        }
+        catch(Exception e)
+        {
+            e.printStackTrace();
+            return null;
+        }
+        
+        return conn;
+    }
+
    + +
    +

    +

  8. Run SQL statements.

    1. Run the following command to create a statement object:
      1
      Statement stmt = con.createStatement();
+
      + +
      +
    2. Run the following command to execute the statement object:
      1
      int rc = stmt.executeUpdate("CREATE TABLE tab1(id INTEGER, name VARCHAR(32));");
+
      + +
      +
    3. Run the following command to release the statement object:
      1
      stmt.close();
+
      + +
      +
    +

  9. Call close() to close the connection.
+
+

Sample Code

This code sample illustrates how to develop applications based on the JDBC API provided by GaussDB(DWS).

+

Before completing the following example, you need to create a stored procedure. For details, see "Tutorial: Development Using JDBC or ODBC" in the Data Warehouse Service (DWS) Developer Guide.

+
 1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
create or replace procedure testproc 
+(
+    psv_in1 in integer,
+    psv_in2 in integer,
+    psv_inout in out integer
+)
+as
+begin
+    psv_inout := psv_in1 + psv_in2 + psv_inout;
+end;
+/
+
+ +
+
+
  1
+  2
+  3
+  4
+  5
+  6
+  7
+  8
+  9
+ 10
+ 11
+ 12
+ 13
+ 14
+ 15
+ 16
+ 17
+ 18
+ 19
+ 20
+ 21
+ 22
+ 23
+ 24
+ 25
+ 26
+ 27
+ 28
+ 29
+ 30
+ 31
+ 32
+ 33
+ 34
+ 35
+ 36
+ 37
+ 38
+ 39
+ 40
+ 41
+ 42
+ 43
+ 44
+ 45
+ 46
+ 47
+ 48
+ 49
+ 50
+ 51
+ 52
+ 53
+ 54
+ 55
+ 56
+ 57
+ 58
+ 59
+ 60
+ 61
+ 62
+ 63
+ 64
+ 65
+ 66
+ 67
+ 68
+ 69
+ 70
+ 71
+ 72
+ 73
+ 74
+ 75
+ 76
+ 77
+ 78
+ 79
+ 80
+ 81
+ 82
+ 83
+ 84
+ 85
+ 86
+ 87
+ 88
+ 89
+ 90
+ 91
+ 92
+ 93
+ 94
+ 95
+ 96
+ 97
+ 98
+ 99
+100
+101
+102
+103
+104
+105
+106
+107
+108
+109
+110
+111
+112
+113
+114
+115
+116
+117
+118
+119
+120
+121
+122
+123
+124
+125
+126
+127
+128
+129
+130
+131
+132
+133
+134
+135
+136
+137
+138
+139
+140
+141
+142
+143
+144
+145
+146
+147
+148
+149
+150
+151
+152
+153
+154
+155
+156
+157
+158
+159
+160
+161
+162
+163
+164
+165
+166
+167
+168
//DBtest.java
+//gsjdbc4.jar is used as an example.
+//Demonstrate the main steps for JDBC development, including creating databases, creating tables, and inserting data.
+
+import java.sql.Connection;
+import java.sql.DriverManager;
+import java.sql.PreparedStatement;
+import java.sql.SQLException;
+import java.sql.Statement;
+import java.sql.CallableStatement;
+import java.sql.Types;
+
+public class DBTest {
+//Create a database connection. Replace the following IP address and database with the actual database connection address and database name.
+  public static Connection GetConnection(String username, String passwd) {
+    String driver = "org.postgresql.Driver";
+    String sourceURL = "jdbc:postgresql://10.10.0.13:8000/database";
+    Connection conn = null;
+    try {
+      // Load the database driver.
+      Class.forName(driver).newInstance();
+    } catch (Exception e) {
+      e.printStackTrace();
+      return null;
+    }
+
+    try {
+      //Create a database connection.
+      conn = DriverManager.getConnection(sourceURL, username, passwd);
+      System.out.println("Connection succeed!");
+    } catch (Exception e) {
+      e.printStackTrace();
+      return null;
+    }
+
+    return conn;
+  };
+
+  //Run the common SQL statements to create table customer_t1.
+  public static void CreateTable(Connection conn) {
+    Statement stmt = null;
+    try {
+      stmt = conn.createStatement();
+
+      //Run the common SQL statements.
+      int rc = stmt
+          .executeUpdate("CREATE TABLE customer_t1(c_customer_sk INTEGER, c_customer_name VARCHAR(32));");
+
+      stmt.close();
+    } catch (SQLException e) {
+      if (stmt != null) {
+        try {
+          stmt.close();
+        } catch (SQLException e1) {
+          e1.printStackTrace();
+        }
+      }
+      e.printStackTrace();
+    }
+  }
+
+  //Run the prepared statements and insert data in batches.
+  public static void BatchInsertData(Connection conn) {
+    PreparedStatement pst = null;
+
+    try {
+      //Generate the prepared statements.
+      pst = conn.prepareStatement("INSERT INTO customer_t1 VALUES (?,?)");
+      for (int i = 0; i < 3; i++) {
+        //Add parameters.
+        pst.setInt(1, i);
+        pst.setString(2, "data " + i);
+        pst.addBatch();
+      }
+      //Execute batch processing.
+      pst.executeBatch();
+      pst.close();
+    } catch (SQLException e) {
+      if (pst != null) {
+        try {
+          pst.close();
+        } catch (SQLException e1) {
+        e1.printStackTrace();
+        }
+      }
+      e.printStackTrace();
+    }
+  }
+
+  //Run the precompiled statement to update the data.
+  public static void ExecPreparedSQL(Connection conn) {
+    PreparedStatement pstmt = null;
+    try {
+      pstmt = conn
+          .prepareStatement("UPDATE customer_t1 SET c_customer_name = ? WHERE c_customer_sk = 1");
+      pstmt.setString(1, "new Data");
+      int rowcount = pstmt.executeUpdate();
+      pstmt.close();
+    } catch (SQLException e) {
+      if (pstmt != null) {
+        try {
+          pstmt.close();
+        } catch (SQLException e1) {
+          e1.printStackTrace();
+        }
+      }
+      e.printStackTrace();
+    }
+  }
+
+
+//Execute the storage procedure. 
+  public static void ExecCallableSQL(Connection conn) {
+    CallableStatement cstmt = null;
+    try {
+      
+      cstmt=conn.prepareCall("{? = CALL TESTPROC(?,?,?)}");
+      cstmt.setInt(2, 50); 
+      cstmt.setInt(1, 20);
+      cstmt.setInt(3, 90);
+      cstmt.registerOutParameter(4, Types.INTEGER);  //Register a parameter of the out type. Its value is an integer.
+      cstmt.execute();
+      int out = cstmt.getInt(4);  //Obtain the out parameter.
+      System.out.println("The CallableStatment TESTPROC returns:"+out);
+      cstmt.close();
+    } catch (SQLException e) {
+      if (cstmt != null) {
+        try {
+          cstmt.close();
+        } catch (SQLException e1) {
+          e1.printStackTrace();
+        }
+      }
+      e.printStackTrace();
+    }
+  }
+  
+
+  /**
+   * Main program, which gradually invokes each static method.
+   * @param args
+  */
+  public static void main(String[] args) {
+    //Create a database connection. Replace User and Password with the actual database user name and password.
+    Connection conn = GetConnection("User", "Password");
+
+    //Create a table.
+    CreateTable(conn);
+
+    //Insert data in batches.
+    BatchInsertData(conn);
+
+    //Run the precompiled statement to update the data.
+    ExecPreparedSQL(conn);
+
+    //Execute the storage procedure. 
+    ExecCallableSQL(conn);
+
+    //Close the database connection.
+    try {
+      conn.close();
+    } catch (SQLException e) {
+      e.printStackTrace();
+    }
+
+  }
+
+}
+
+ +
+
+
+
+
+
Parent topic: Using the JDBC and ODBC Drivers to Connect to a Cluster
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_0078.html b/docs/dws/umn/dws_01_0078.html new file mode 100644 index 00000000..af571609 --- /dev/null +++ b/docs/dws/umn/dws_01_0078.html @@ -0,0 +1,17 @@ + + +

Getting Started

+
+
+ +
+ diff --git a/docs/dws/umn/dws_01_0079.html b/docs/dws/umn/dws_01_0079.html new file mode 100644 index 00000000..c388f29d --- /dev/null +++ b/docs/dws/umn/dws_01_0079.html @@ -0,0 +1,21 @@ + + +

Step 4: Viewing Other Documents and Clearing Resources

+

Viewing Other Relevant Documents

After performing the steps in preceding sections, you can refer to the documentation listed as follows for more information about GaussDB(DWS):

+ +
+

Deleting Resources

After performing the steps in "Getting Started," if you do not need to use the sample data, clusters, ECSs, or VPCs, delete the resources so that your service quotas will not be wasted or occupied.

+
+
  1. Delete a GaussDB(DWS) cluster.

    On the GaussDB(DWS) management console, click Clusters, locate the row that contains dws-demo in the cluster list, and choose More > Delete. In the dialog box that is displayed, select Release the EIP bound with the cluster and click OK.

    +

    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 when the cluster is deleted.

    +

  2. Delete a subnet. Before deleting the subnet, ensure that it is not bound to other resources.

    Log in to the VPC management console. In the navigation tree on the left, click Virtual Private Cloud. In the VPC list, click vpc-dws. In the subnet list, locate the row that contains subnet-dws and click Delete.

    +

  3. Delete a VPC. Before deleting the VPC, ensure that it is not bound to other resources.

    Log in to the VPC management console, locate the row that contains vpc-dws in the VPC list, and click Delete.

    +

    For details, see "VPC and Subnet > Deleting a VPC" in the Virtual Private Cloud User Guide.

    +

+
+
+
+
Parent topic: Getting Started
+
+
+ diff --git a/docs/dws/umn/dws_01_0080.html b/docs/dws/umn/dws_01_0080.html new file mode 100644 index 00000000..cd69c5b5 --- /dev/null +++ b/docs/dws/umn/dws_01_0080.html @@ -0,0 +1,23 @@ + + +

Cluster DR

+
+
+ + +
+
Parent topic: Cluster HA
+
+
+ diff --git a/docs/dws/umn/dws_01_0081.html b/docs/dws/umn/dws_01_0081.html new file mode 100644 index 00000000..f9b81f9b --- /dev/null +++ b/docs/dws/umn/dws_01_0081.html @@ -0,0 +1,23 @@ + + +

Using the JDBC and ODBC Drivers to Connect to a Cluster

+
+
+ + +
+
Parent topic: Cluster Connection
+
+
+ diff --git a/docs/dws/umn/dws_01_0083.html b/docs/dws/umn/dws_01_0083.html new file mode 100644 index 00000000..fbacef1e --- /dev/null +++ b/docs/dws/umn/dws_01_0083.html @@ -0,0 +1,18 @@ + + +

(Optional) Downloading the SSL Certificate

+

GaussDB(DWS) supports the standard SSL (TLS 1.2). As a highly secure protocol, SSL authenticates bidirectional identification between the server and client using digital signatures and digital certificates to ensure secure data transmission. To support SSL connection, GaussDB(DWS) has obtained the formal certificates and keys for the server and client from the CA certification center. It is assumed that the key and certificate for the server are server.key and server.crt respectively; the key and certificate for the client are client.key and client.crt respectively, and the name of the CA root certificate is cacert.pem.

+

By default, the SSL function is enabled for a data warehouse cluster (the server) to allow SSL and non-SSL connections from the client. In addition, the certificate, private key, and root certificate of the server have been configured by default.

+
If the client or JDBC/ODBC driver needs to use SSL connection, you must configure related SSL connection parameters in the client or application code. The GaussDB(DWS) management console provides the SSL certificate required by the client. The SSL certificate contains the default certificate, private key, root certificate, and private key password encryption file required by the client. Download the SSL certificate to the host where the client resides and specify the path of the certificate on the client.

Using the default certificate may pose security risks. To improve system security, you are advised to periodically change the certificate to prevent password cracking. If you need to replace the certificate, contact the database customer service.

+
+
+

This section describes how to download an SSL certificate.

+

Downloading the SSL Certificate File

  1. Log in to the GaussDB(DWS) management console.
  2. In the navigation pane on the left, click Connections.
  3. In the Driver area, click download an SSL certificate.
+
+
+
+
+
Parent topic: Using the gsql CLI Client to Connect to a Cluster
+
+
+ diff --git a/docs/dws/umn/dws_01_0085.html b/docs/dws/umn/dws_01_0085.html new file mode 100644 index 00000000..186b6dbc --- /dev/null +++ b/docs/dws/umn/dws_01_0085.html @@ -0,0 +1,28 @@ + + +

Copying Automated Snapshots

+

This section describes how to copy snapshots that are automatically created for long-term retention.

+

Copying an Automated Snapshot

  1. Log in to the GaussDB(DWS) management console.
  2. In the navigation pane on the left, choose Snapshots.

    All snapshots are displayed by default. You can copy the snapshots that are automatically created.

    +

  3. In the Operation column of the snapshot that you want to copy, click Copy.

    • New Snapshot Name: Enter a new 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 (_).

      +
    • Snapshot Description: Enter the snapshot information.

      This parameter is optional. Snapshot information contains 0 to 256 characters and does not support the following special characters: !<>'=&"

      +
    +
    Figure 1 Copying a snapshot
    +

  4. Click OK. The system starts to copy the snapshot for the cluster.

    The system displays a message indicating that the snapshot is successfully copied and delivered. After the snapshot is copied, the status of the copied snapshot is Available.

    +

    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 How Can I Clear and Reclaim Storage?

    +
    +

+
+
+
+
+
Parent topic: Automated Snapshots
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_0086.html b/docs/dws/umn/dws_01_0086.html new file mode 100644 index 00000000..6b75ad19 --- /dev/null +++ b/docs/dws/umn/dws_01_0086.html @@ -0,0 +1,334 @@ + + +

Using an ODBC Driver to Connect to a Database

+

GaussDB(DWS) allows you to use an ODBC driver to connect to the database through an ECS on the cloud platform or over the Internet.

+

For details about how to use the ODBC API, see the official document.

+

Prerequisites

+
+

Using an ODBC Driver to Connect to a Database (Linux)

  1. Upload the ODBC package and code file to the Linux environment and decompress them to the specified directory.
  2. Log in to the Linux environment as user root.
  3. Prepare unixODBC.

    1. Decompress the unixODBC code file.
      tar -xvf unixODBC-2.3.0.tar.gz
      +
    2. Modify the configuration.
      cd unixODBC-2.3.0
+vi configure
      +

      Change the value of LIB_VERSION to the following. Save the change and exit.

      +
      LIB_VERSION="1:0:0"
      +
    3. Compile the code file and install the driver.
      ./configure --enable-gui=no
+make
+make install
      +
    +

  4. Replace the driver file.

    1. Decompress dws_odbc_driver_for_linux.zip.
      unzip dws_odbc_driver_for_linux.zip
      +
    2. Copy all files in the lib directory to /usr/local/lib. If there are files with the same name, overwrite them.
    3. Copy psqlodbcw.la and psqlodbcw.so in the odbc/lib directory to /usr/local/lib.
    +

  5. Run the following command to modify the configuration of the driver file:

    vi /usr/local/etc/odbcinst.ini
    +

    Copy the following content to the file:

    +
    [DWS] 
+Driver64=/usr/local/lib/psqlodbcw.so
    +

    The parameters are as follows:

    +
    • [DWS]: indicates the driver name. You can customize the name.
    • Driver64 or Driver: indicates the path where the dynamic library of the driver resides. For a 64-bit operating system, search for Driver64 first. If Driver64 is not configured, search for Driver.
    +

  6. Run the following command to modify the data source file:

    vi /usr/local/etc/odbc.ini
    +

    Copy the following content to the configuration file, save the modification, and exit.

    +
    [DWSODBC]
+Driver=DWS
+Servername=10.10.0.13
+Database=gaussdb
+Username=dbadmin
+Password=password
+Port=8000
+Sslmode=allow
    + +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

    Parameter

    +

    Description

    +

    Example Value

    +

    [DSN]

    +

    Data source name.

    +

    [DWSODBC]

    +

    Driver

    +

    Driver name, corresponding to DriverName in odbcinst.ini.

    +

    Driver=DWS

    +

    Servername

    +

    Server IP address.

    +

    Servername=10.10.0.13

    +

    Database

    +

    Name of the database to be connected to.

    +

    Database=gaussdb

    +

    Username

    +

    Database username.

    +

    Username=dbadmin

    +

    Password

    +

    Database user password.

    +

    Password=password

    +

    Port

    +

    Port number of the server.

    +

    Port=8000

    +

    Sslmode

    +

    SSL certification mode. This parameter is enabled for the cluster by default.

    +

    Values and meanings:

    +
    • disable: only tries to establish a non-SSL connection.
    • allow: tries establishing a non-SSL connection first, and then an SSL connection if the attempt fails.
    • prefer: tries establishing an SSL connection first, and then a non-SSL connection if the attempt fails.
    • require: only tries establishing an SSL connection. If there is a CA file, perform the verification according to the scenario in which the parameter is set to verify-ca.
    • verify-ca: tries establishing an SSL connection and checks whether the server certificate is issued by a trusted CA.
    • verify-full: not supported by GaussDB(DWS)
    +
    NOTE:

    The SSL mode delivers higher security than the common mode. By default, the SSL function is enabled in a cluster to allow SSL or non-SSL connections from the client. You are advised to use the SSL mode when using ODBC to connect to a GaussDB (DWS) cluster.

    +
    +

    Sslmode=allow

    +
    +
    +

    You can view the values of Servername and Port on the GaussDB(DWS) management console. Log in to the GaussDB(DWS) management console and click Connection Management. In the Data Warehouse Connection String area, select the target cluster and obtain Private Network Address or Public Network Address. For details, see Obtaining the Cluster Connection Address.

    +
    +

  7. Configure environment variables.

    vi ~/.bashrc
    +

    Add the following information to the configuration file:

    +
    export LD_LIBRARY_PATH=/usr/local/lib/:$LD_LIBRARY_PATH 
+export ODBCSYSINI=/usr/local/etc 
+export ODBCINI=/usr/local/etc/odbc.ini
    +

  8. Import environment variables.

    source ~/.bashrc
    +

  9. Run the following commands to connect to the database:

    /usr/local/bin/isql -v DWSODBC
    +

    If the following information is displayed, the connection is successful:

    +
    1
+2
+3
+4
+5
+6
+7
+8
+9
    +---------------------------------------+ 
+| Connected!                            | 
+|                                       | 
+| sql-statement                         | 
+| help [tablename]                      | 
+| quit                                  | 
+|                                       | 
++---------------------------------------+  
+SQL> 
+
    + +
    +

+
+

Using an ODBC Driver to Connect to a Database (Windows)

  1. Decompress ODBC driver package dws_odbc_driver_for_windows.zip (for Windows) and install psqlodbc.msi.
  2. Decompress the SSL certificate package to obtain the certificate file.

    You can choose to automatically or manually deploy the certificate based on your needs.

    +

    Automatic deployment:

    +

    Double-click the sslcert_env.bat file. The certificate is automatically deployed to a default location.

    +

    The sslcert_env.bat file ensures the purity of the certificate environment. When the %APPDATA%\postgresql directory exists, a message will be prompted asking you whether you want to remove related directories. If you want to remove related directories, back up files in the directory.

    +
    +
    Manual deployment:
    1. Create a new folder named postgresql in the %APPDATA%\ directory.
    2. Copy files client.crt, client.key, client.key.cipher, and client.key.rand to the %APPDATA%\postgresql directory and change client in the file name to postgres. For example, change the name of client.key to postgres.key.
    3. Copy cacert.pem to %APPDATA%\postgresql and change the name of cacert.pem to root.crt.
    +
    +

  3. Open Driver Manager.

    Currently, because GaussDB(DWS) only provides a 32-bit ODBC driver, it only supports 32-bit application development. Use the 32-bit Driver Manager when you configure the data source. (Assume the Windows system drive is drive C. If another disk drive is used, modify the path accordingly.)

    +
    • In a 64-bit Windows operating system, open C:\Windows\SysWOW64\odbcad32.exe.

      Do not choose Control Panel > System and Security > Administrative Tools > Data Sources (ODBC) directly.

      +

      WOW64 is the acronym for Windows 32-bit on Windows 64-bit. C:\Windows\SysWOW64\ stores the 32-bit environment on a 64-bit system. C:\Windows\System32\ stores the environment consistent with the current operating system. For technical details, see the Windows technical documents.

      +
      +
    • In a 32-bit Windows operating system, open C:\Windows\System32\odbcad32.exe.

      You can also open Driver Manager by choosing Control Panel > System and Security > Administrative Tools > Data Sources (ODBC).

      +
    +

  4. Configure a data source to be connected to.

    1. On the User DSN tab, click Add and choose PostgreSQL Unicode for setup.
      Figure 1 Configuring a data source to be connected to
      +

      You can view the values of Server and Port on the GaussDB(DWS) management console. Log in to the GaussDB(DWS) management console and click Connections. In the Data Warehouse Connection String area, select the target cluster and obtain Private Network Address or Public Network Address. For details, see Obtaining the Cluster Connection Address.

      +
    2. Click Test to verify that the connection is correct. If Connection successful is displayed, the connection is correct.
    +

  5. Compile an ODBC sample program to connect to the data source.

    The ODBC API does not provide the database connection retry capability. You need to implement the connection retry processing in the service code.

    +

    The sample code is as follows:

    +
     1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+19
+20
+21
+22
+23
+24
+25
+26
+27
+28
+29
+30
+31
+32
+33
+34
+35
+36
+37
+38
+39
+40
+41
+42
+43
+44
+45
+46
+47
+48
+49
+50
+51
+52
+53
+54
+55
+56
+57
+58
+59
+60
+61
+62
+63
+64
+65
+66
+67
+68
+69
+70
+71
+72
+73
+74
+75
+76
+77
+78
+79
+80
+81
+82
+83
    // This example shows how to obtain GaussDB(DWS) data through the ODBC driver.
+// DBtest.c (compile with: libodbc.so)  
+#include <stdlib.h> 
+#include <stdio.h> 
+#include <sqlext.h>
+#ifdef WIN32
+#include <windows.h>
+#endif 
+SQLHENV       V_OD_Env;        // Handle ODBC environment 
+SQLHSTMT      V_OD_hstmt;      // Handle statement 
+SQLHDBC       V_OD_hdbc;       // Handle connection     
+char          typename[100];
+SQLINTEGER    value = 100;
+SQLINTEGER    V_OD_erg,V_OD_buffer,V_OD_err,V_OD_id;
+int main(int argc,char *argv[]) 
+{         
+      // 1. Apply for an environment handle.       
+      V_OD_erg = SQLAllocHandle(SQL_HANDLE_ENV,SQL_NULL_HANDLE,&V_OD_Env);     
+      if ((V_OD_erg != SQL_SUCCESS) && (V_OD_erg != SQL_SUCCESS_WITH_INFO))        
+      {           
+           printf("Error AllocHandle\n");           
+           exit(0);        
+      } 
+      // 2. Set environment attributes (version information).         
+      SQLSetEnvAttr(V_OD_Env, SQL_ATTR_ODBC_VERSION, (void*)SQL_OV_ODBC3, 0);      
+      // 3. Apply for a connection handle.        
+      V_OD_erg = SQLAllocHandle(SQL_HANDLE_DBC, V_OD_Env, &V_OD_hdbc);     
+      if ((V_OD_erg != SQL_SUCCESS) && (V_OD_erg != SQL_SUCCESS_WITH_INFO))      
+      {                     
+           SQLFreeHandle(SQL_HANDLE_ENV, V_OD_Env);          
+           exit(0);       
+      }
+      // 4. Set connection attributes.
+      SQLSetConnectAttr(V_OD_hdbc, SQL_ATTR_AUTOCOMMIT, SQL_AUTOCOMMIT_ON, 0);          
+      // 5. Connect to a data source. You do not need to enter the username and password if you have configured them in the odbc.ini file. If you have not configured them, specify the name and password of the user who wants to connect to the database in the SQLConnect function.
+      V_OD_erg = SQLConnect(V_OD_hdbc, (SQLCHAR*) "gaussdb", SQL_NTS,  
+                           (SQLCHAR*) "", SQL_NTS,  (SQLCHAR*) "", SQL_NTS);        
+      if ((V_OD_erg != SQL_SUCCESS) && (V_OD_erg != SQL_SUCCESS_WITH_INFO))      
+      {           
+          printf("Error SQLConnect %d\n",V_OD_erg);            
+          SQLFreeHandle(SQL_HANDLE_ENV, V_OD_Env);       
+          exit(0);        
+      }     
+      printf("Connected !\n"); 
+      // 6. Set statement attributes.
+      SQLSetStmtAttr(V_OD_hstmt,SQL_ATTR_QUERY_TIMEOUT,(SQLPOINTER *)3,0);
+      // 7. Apply for a statement handle.
+      SQLAllocHandle(SQL_HANDLE_STMT, V_OD_hdbc, &V_OD_hstmt);       
+      // 8. Executes an SQL statement directly.
+      SQLExecDirect(V_OD_hstmt,"drop table IF EXISTS testtable",SQL_NTS);
+      SQLExecDirect(V_OD_hstmt,"create table testtable(id int)",SQL_NTS);
+      SQLExecDirect(V_OD_hstmt,"insert into testtable values(25)",SQL_NTS);
+      // 9. Prepare for execution.
+      SQLPrepare(V_OD_hstmt,"insert into testtable values(?)",SQL_NTS); 
+      // 10. Bind parameters.
+      SQLBindParameter(V_OD_hstmt,1,SQL_PARAM_INPUT,SQL_C_SLONG,SQL_INTEGER,0,0,
+                       &value,0,NULL);
+      // 11. Execute the ready statement.
+      SQLExecute(V_OD_hstmt);
+      SQLExecDirect(V_OD_hstmt,"select id from testtable",SQL_NTS);
+      // 12. Obtain the attributes of a certain column in the result set.
+      SQLColAttribute(V_OD_hstmt,1,SQL_DESC_TYPE,typename,100,NULL,NULL);                 
+      printf("SQLColAtrribute %s\n",typename);
+      // 13. Bind the result set.
+      SQLBindCol(V_OD_hstmt,1,SQL_C_SLONG, (SQLPOINTER)&V_OD_buffer,150,
+                (SQLLEN *)&V_OD_err);
+      // 14. Collect data using SQLFetch.
+      V_OD_erg=SQLFetch(V_OD_hstmt);
+      // 15. Obtain and return data using SQLGetData.
+      while(V_OD_erg != SQL_NO_DATA)
+      {
+          SQLGetData(V_OD_hstmt,1,SQL_C_SLONG,(SQLPOINTER)&V_OD_id,0,NULL);
+          printf("SQLGetData ----ID = %d\n",V_OD_id);
+          V_OD_erg=SQLFetch(V_OD_hstmt);
+      };
+      printf("Done !\n");pgadmin
+      // 16. Disconnect from the data source and release handles.
+      SQLFreeHandle(SQL_HANDLE_STMT,V_OD_hstmt);    
+      SQLDisconnect(V_OD_hdbc);         
+      SQLFreeHandle(SQL_HANDLE_DBC,V_OD_hdbc);       
+      SQLFreeHandle(SQL_HANDLE_ENV, V_OD_Env);  
+      return(0);
+ }
+
    + +
    +

+
+
+
+
+
Parent topic: Using the JDBC and ODBC Drivers to Connect to a Cluster
+
+
+ diff --git a/docs/dws/umn/dws_01_0088.html b/docs/dws/umn/dws_01_0088.html new file mode 100644 index 00000000..a91c6074 --- /dev/null +++ b/docs/dws/umn/dws_01_0088.html @@ -0,0 +1,20 @@ + + +

Step 1: Starting Preparations

+

This guide is an introductory tutorial that demonstrates how to create a sample GaussDB(DWS) cluster, connect to the cluster database, import the sample data from OBS, and analyze the sample data. You can use this tutorial to evaluate GaussDB(DWS).

+

Before creating a GaussDB(DWS) cluster, ensure that the following prerequisites are met:

+ +

Registering a Public Cloud Account and Completing Real-Name Authentication

If you do not have a public cloud account, register one. If you already have an account with real-name authentication, skip this step and use the account.

+
  1. Open the official public cloud website and click Register in the upper right corner. The registration page is displayed.
  2. Fill in user information as instructed to complete the registration.
  3. Click the username in the upper right corner to enter the Account Info page. Then click Real-Name Authentication in the left navigation pane.
  4. Perform real-name authentication as prompted.

    You must perform real-name authentication before enabling cloud services.

    +
    +
+
+

Determining the Cluster Ports

+
+
+
+
+
Parent topic: Getting Started
+
+
+ diff --git a/docs/dws/umn/dws_01_0089.html b/docs/dws/umn/dws_01_0089.html new file mode 100644 index 00000000..958edef2 --- /dev/null +++ b/docs/dws/umn/dws_01_0089.html @@ -0,0 +1,100 @@ + + +

Configuring an Automated Snapshot Policy

+

You can select a snapshot type and set one or more automated snapshot policies for a cluster. After an automated snapshot policy is enabled, the system automatically creates snapshots based on the preset time, period, and snapshot type according to the policy.

+

Perform the following steps to configure an automated snapshot policy.

+

Procedure

  1. Log in to the GaussDB(DWS) management console.
  2. In the navigation pane on the left, choose Clusters.
  3. Click the name of a cluster.
  4. Click the Snapshots tab page and click Policy List. All the policies of the current cluster are displayed on the Policy List page. Toggle on Snapshot Policy.

    • indicates that the policy is enabled (default). The default retention period is three days.
    • indicates that the policy is disabled. If this policy is disabled, historical automated snapshots will be automatically deleted.
    +
    Figure 1 Policy list
    +

  5. After this function is enabled, you can set the retention mode for automated snapshots. For more information, see Table 1.

    +
    +
    + + + + + + + +
    Table 1 Automated snapshot parameters

    Parameter

    +

    Description

    +

    Retention Days

    +

    Retention days of the snapshots that are automatically created. The value ranges from 1 to 31 days.

    +
    NOTE:

    Snapshots that are automatically created cannot be deleted manually. The system automatically deletes these snapshots when their retention duration exceeds the threshold.

    +
    +
    +
    +
    +

  6. After automated snapshot is enabled, you can configure its parameters. For more information, see Table 2.

    The snapshot creation time is UTC, which may be different from your local time.

    +
    +
    • If the snapshot type is set to Full, you can choose either Periodic or One-time, as shown in the following figures.
      • Periodic: Specify the days for every week/month and the exact time on the days.

        +
      • One-time: Specify a day and the exact time on the day.
      +

      +
    • Incremental snapshots can be set only to Periodic, as shown in the first figure below.
      • When configuring a periodic incremental snapshot policy, you can specify the days for every week/month and the exact time on the days. You can also specify the start time and interval for the snapshots.
      +

      +

      +

      Choosing the days in red (29/30/31) may skip some monthly backups.

      +
      +
    + +
    + + + + + + + + + + + + + + + + + + + +
    Table 2 Parameter description

    Parameter

    +

    Description

    +

    Name

    +

    The policy name must be unique, consist of 4 to 92 characters, and start with a letter. It is case-insensitive and can contain only letters, digits, hyphens (-), and underscores (_).

    +

    Type

    +

    You can choose either full or incremental snapshots.

    +

    Policy

    +

    You can choose either periodic or one-time snapshots.

    +
    NOTE:

    You can select One-off Snapshot only when Snapshot Type is set to Full.

    +
    +

    One-time

    +

    You can create a full snapshot at a specified time in the future. The UTC time is used.

    +

    Periodic Policy Configurations

    +

    You can create automated snapshots on a daily, weekly, or monthly basis:

    +
    • Days: Specify days for every week or every month. Weekly and Monthly cannot be selected at the same time. For Monthly, the specified days are applicable only to months that contain the dates. For example, if you select 29, no automated snapshot will be created on February, 2022.
    • Time: Specify the exact time on the selected days. For incremental snapshots, you can specify the start time and interval. The interval can be 4 to 24 hours, indicating that a snapshot is created at an interval of 4 to 24 hours.
    +
    NOTICE:

    If the incremental data is large and the execution period is long, the backup will be slow. In this case, increase the backup frequency.

    +
    +
    +
    +

  7. Click OK.

    A maximum of three snapshot policies can be set for a cluster.

    +
    +

  8. (Optional) To modify an automated snapshot policy, click Modify in the Operation column.

    +

  9. (Optional) To preview a policy, click Preview Policy. The next seven snapshots of the cluster will be displayed. If no full snapshot policy is configured for the cluster, the default policy is used, that is, a full snapshot is taken after every 14 incremental snapshots.

    Implementation of the same policy varies according to operations in the cluster. For example:

    +
    • The policy preview time is for your reference only. The cluster triggers a snapshot within one hour before or after the preset time.
    • The next automated snapshots after cluster scale-out, upgrade, resize, and media modification are full snapshots by default.
    • If a periodic policy is used for a cluster, no automated backup is allowed within 4 hours after the last automated snapshot is complete.
    • If the snapshot start time of multiple policies conflicts, the priorities of the policies are as follows: one-time > periodic > full > incremental.
    • You can use any backup, full or incremental, to restore the full data of a resource.
    +
    +
    +

+
+
+
+
+
Parent topic: Automated Snapshots
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_0091.html b/docs/dws/umn/dws_01_0091.html new file mode 100644 index 00000000..e3a92354 --- /dev/null +++ b/docs/dws/umn/dws_01_0091.html @@ -0,0 +1,67 @@ + + +

Functions

+

GaussDB(DWS) enables you to use this service through various methods, such as the GaussDB(DWS) management console, GaussDB(DWS) client, and REST APIs. This section describes the main functions of GaussDB(DWS).

+

Cluster Management

A data warehouse cluster contains nodes with the same flavor in the same subnet. These nodes jointly provide services. GaussDB(DWS) provides a professional, efficient, and centralized management console, allowing you to quickly apply for clusters, easily manage data warehouses, and focus on data and services.

+

Main functions of cluster management are described as follows:

+ +

GaussDB(DWS) allows you to manage clusters and snapshots in either of the following ways:

+ +
+

Enterprise-Level Data Warehouses and Compatibility with Standard SQL

After a data warehouse cluster is created, you can use the SQL client to connect to the cluster and perform operations such as creating a database, managing the database, importing and exporting data, and querying data.

+

GaussDB(DWS) provides petabyte-level (PB-level) high-performance databases with the following features:

+ + +

GaussDB(DWS) has comprehensive SQL capabilities:

+ +

For details about the SQL syntax and database operation guidance, see the Data Warehouse Service Database Development Guide.

+
+

Diverse Data Import Modes

GaussDB(DWS) supports efficient data import from multiple data sources. The following lists typical data import modes. For details, see "Data Import" in the Data Warehouse Service (DWS) Developer Guide.

+ +

In addition, GaussDB(DWS)supports data import using mainstream third-party ETL tools.

+
+

APIs

You can call standard APIs, such as JDBC and ODBC, to access databases in GaussDB(DWS) clusters.

+

For details, see "Using the JDBC and ODBC Drivers to Connect to a Cluster" in the Data Warehouse Service (DWS) User Guide.

+
+

High Reliability

+
+

Security Management

+
+

Monitoring and Auditing

+
+

Multiple Database Tools

GaussDB(DWS) provides the following self-developed tools. You can download the tool packages on the GaussDB(DWS) management console. For details about the tools, see the Data Warehouse Service (DWS) Tool Guide.

+ +
+
+
+
+
Parent topic: Service Overview
+
+
+ diff --git a/docs/dws/umn/dws_01_0092.html b/docs/dws/umn/dws_01_0092.html new file mode 100644 index 00000000..a4c64f48 --- /dev/null +++ b/docs/dws/umn/dws_01_0092.html @@ -0,0 +1,21 @@ + + + +

Manual Snapshots

+ +

+
+ +
+ + +
+
Parent topic: Snapshots
+
+
+ diff --git a/docs/dws/umn/dws_01_0093.html b/docs/dws/umn/dws_01_0093.html new file mode 100644 index 00000000..ac05a481 --- /dev/null +++ b/docs/dws/umn/dws_01_0093.html @@ -0,0 +1,25 @@ + + +

Using the gsql CLI Client to Connect to a Cluster

+
+
+ + +
+
Parent topic: Cluster Connection
+
+
+ diff --git a/docs/dws/umn/dws_01_0094.html b/docs/dws/umn/dws_01_0094.html new file mode 100644 index 00000000..33f250b1 --- /dev/null +++ b/docs/dws/umn/dws_01_0094.html @@ -0,0 +1,153 @@ + + +

Using the Data Studio GUI Client to Connect to a Cluster

+

Data Studio is a SQL client tool running on the Windows operating system. It provides various GUIs for you to manage databases and database objects, as well as edit, run, and debug SQL scripts, and view execution plans. Download the Data Studio software package from the GaussDB(DWS) management console. The package can be used without installation after being decompressed.

+

Data Studio versions include Windows x86 (32-bit Windows system) and Windows x64 (64-bit Windows system).

+

Preparations Before Connecting to a Cluster

+
+

Connecting to the Cluster Database Using Data Studio

  1. GaussDB(DWS) provides a Windows-based Data Studio client and the tool depends on the JDK. You need to install the JDK on the client host first.

    Only JDK 1.8 is supported.

    +
    +

    In the Windows operating system, you can download the required JDK version from the official website of SDK, and install it by following the installation guidance.

    +

  2. Log in to the GaussDB(DWS) management console.
  3. Click Connections.
  4. On the Download Client and Driver page, download Data Studio GUI Client.

    • Select Windows x86 or Windows x64 based on the OS type and click Download to download a Data Studio version that matches the current cluster.

      If clusters of different versions are available, you will download the Data Studio matching the earliest cluster version after clicking Download. If there is no cluster, you will download the Data Studio tool of the earliest version after clicking Download. GaussDB(DWS) clusters are compatible with earlier versions of Data Studio.

      +
    • Click Historical Version to download the corresponding Data Studio version. You are advised to download Data Studio based on the cluster version.
    +

  5. Decompress the downloaded client software package (32-bit or 64-bit) to the installation directory.
  6. Open the installation directory and double-click Data Studio.exe to start the Data Studio client. See Figure 1.

    Figure 1 Starting the client
    +

    If your computer blocks the running of the application, you can unlock the Data Studio.exe file to start the application.

    +
    +

  7. Choose File > New Connection from the main menu. See Figure 2.

    Figure 2 New connection
    +
    Figure 3 New connection
    +

  8. In the displayed New Database Connection window, enter the connection parameters.

    +

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Connection parameters

    Field

    +

    Description

    +

    Example Value

    +

    Database Type

    +

    Select GaussDB A

    +

    GaussDB A

    +

    Connection Name

    +

    Name of the connection

    +

    dws-demo

    +

    Host

    +

    IP address (IPv4) or domain name of the cluster to be connected

    +

    -

    +

    Port Number

    +

    Database port

    +

    8000

    +

    Database Name

    +

    Database name

    +

    gaussdb

    +

    Username

    +

    Username for connecting to the database

    +

    -

    +

    Password

    +

    Password for logging in to the database to be connected

    +

    -

    +

    Save Password

    +

    Select an option from the drop-down list:

    +
    • Current Session Only: The password is saved only in the current session.
    • Do Not Save: The password is not saved.
    +

    -

    +

    Enable SSL

    +

    If Enable SSL is selected, the client can use SSL to encrypt connections. The SSL connection mode is more secure than common modes, so you are advised to enable SSL connection.

    +

    -

    +
    +
    +

    When Enable SSL is selected, download the SSL certificate and decompress it by referring to (Optional) Downloading the SSL Certificate. Click the SSL tab and configure the following parameters:

    + +
    + + + + + + + + + + + + + + + + + + + +
    Table 2 Configuring SSL parameters

    Field

    +

    Description

    +

    Client SSL Certificate

    +

    Select the sslcert\client.crt file in the decompressed SSL certificate directory.

    +

    Client SSL Key

    +

    Only the PK8 format is supported. Select the sslcert\client.key.pk8 file in the directory where the SSL certificate is decompressed.

    +

    Root Certificate

    +

    When SSL Mode is set to verify-ca, the root certificate must be configured. Select the sslcert\cacert.pem file in the decompressed SSL certificate directory.

    +

    SSL Cipher

    +

    Set the password for the client SSL key in PK8 format.

    +

    SSL Mode

    +

    GaussDB(DWS) supports the following SSL modes:

    +
    • require
    • verify-ca
    +

    GaussDB(DWS) does not support the verify-full mode.

    +
    +
    +
    Figure 4 Configuring SSL parameters
    +

  9. Click OK to establish the database connection.

    If SSL is enabled, click Continue in the displayed Connection Security Alert dialog box.

    +

    After the login is successful, the RECENT LOGIN ACTIVITY dialog box is displayed, indicating that Data Studio is connected to the database. You can run the SQL statement in the SQL Terminal window on the Data Studio page.

    +
    Figure 5 Successful login
    +

    For details about how to use other functions of Data Studio, press F1 to view the Data Studio user manual.

    +

+
+
+
+
+
Parent topic: Cluster Connection
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_0103.html b/docs/dws/umn/dws_01_0103.html new file mode 100644 index 00000000..b7ee3287 --- /dev/null +++ b/docs/dws/umn/dws_01_0103.html @@ -0,0 +1,17 @@ + + +

Managing Tags

+
+
+ + +
+
Parent topic: Clusters
+
+
+ diff --git a/docs/dws/umn/dws_01_0104.html b/docs/dws/umn/dws_01_0104.html new file mode 100644 index 00000000..88342acd --- /dev/null +++ b/docs/dws/umn/dws_01_0104.html @@ -0,0 +1,26 @@ + + +

Overview

+

A tag is a key-value pair customized by users and used to identify cloud resources. It helps users to classify and search for cloud resources.

+

Tags are composed of key-value pairs.

+ +

On GaussDB(DWS), after creating a cluster, you can add identifiers to items such as the project name, service type, and background information using tags. If you use tags in other cloud services, you are advised to create the same tag key-value pairs for cloud resources used by the same business to keep consistency.

+

GaussDB(DWS) supports the following two types of tags:

+ + +

On GaussDB(DWS), tags can be added to the following resources:

+ +
+
+
+
Parent topic: Managing Tags
+
+
+ diff --git a/docs/dws/umn/dws_01_0105.html b/docs/dws/umn/dws_01_0105.html new file mode 100644 index 00000000..c4d6f7bd --- /dev/null +++ b/docs/dws/umn/dws_01_0105.html @@ -0,0 +1,70 @@ + + +

Tag Management

+

This section describes how to search for clusters based on tags and how to add, modify, and delete tags for clusters.

+

Adding a Tag to a Cluster

  1. On the Clusters page, click the name of the cluster to which a tag is to be added, and click the Tags tab.

    Figure 1 Tags page
    +

  2. Click Add Tag.
  3. Configure the tag parameters in the displayed dialog box.

    Figure 2 Adding a tag to a cluster
    + +
    + + + + + + + + + + + + + +
    Table 1 Tag parameters

    Parameter

    +

    Description

    +

    Example Value

    +

    Tag key

    +

    You can:

    +
    • Select a predefined tag key or an existing resource tag key from the drop-down list of the text box.
      NOTE:

      To add a predefined tag, you need to create one on TMS and select it from the drop-down list of Tag key. You can click View predefined tags to enter the Predefined Tags page of TMS. Then, click Create Tag to create a predefined tag. For more information, see "Management > Predefined Tags > Creating Predefined Tags" in the Tag Management Service User Guide.

      +
      +
    +
    • Enter a tag key in the text box. The tag key can contain a maximum of 36 characters and cannot be an empty string.
      Only digits, letters, underscores (_), and hyphens (-) are allowed.
      NOTE:

      A key must be unique in a given cluster.

      +
      +
      +
    +

    key01

    +

    Tag value

    +

    You can:

    +
    • Select a predefined tag value or resource tag value from the drop-down list of the text box.
    • Enter a tag value in the text box. The tag key can contain a maximum of 43 characters and cannot be an empty string.

      Only digits, letters, underscores (_), periods (.), and hyphens (-) are allowed.

      +
    +

    value01

    +
    +
    +

  4. Click OK.
+
+

Searching for Clusters Based on Tags

You can quickly locate a tagged cluster using tags.

+
  1. Log in to the GaussDB(DWS) management console.
  2. Click Clusters.
  3. Click Search by Tag on the upper right of the cluster list to expand the tab page.

    Figure 3 Search by Tag
    +

  4. In the Search by Tag area, click the Tag Key text box to select a tag key from the drop-down list and then click the Tag Value text box to select the corresponding tag value.

    You can only enter a tag key or value that exists in the drop-down list. If no tag key or value is available, create a tag for the cluster. For details, see Adding a Tag to a Cluster.

    +

  5. Click to add the selected tag to the area under the text boxes.

    • Select another tag in the text boxes and click to generate a tag combination for cluster search. You can add a maximum of 10 tags to search for data warehouse clusters. If you specify more than one tag, clusters containing all the specified tags will be displayed.
    • To delete an existing tag, click next to the tag.
    • You can click Reset to clear all added tags.
      Figure 4 Adding the tag key and value
      +
    +

  6. Click Search. The target cluster will be displayed in the cluster list.
+
+

Modifying a Tag

  1. On the Clusters page, click the name of the cluster for which a tag is to be modified, and click the Tags tab.
  2. Locate the row that contains the tag to be modified, and click Edit in the Operation column. The Edit Tag dialog box is displayed.

    Figure 5 Editing a tag
    +

  3. Enter the new key value in the Value text box.
  4. Click OK.
+
+

Deleting a Tag

  1. On the Clusters page, click the name of the cluster from which a tag is to be deleted, and click the Tags tab.
  2. Locate the row that contains the tag to be deleted, click Delete in the Operation column. The Delete Tag dialog box is displayed.

    Figure 6 Deleting a tag
    +

  3. Click Yes to delete the tag.
+
+
+
+
+
Parent topic: Managing Tags
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_0106.html b/docs/dws/umn/dws_01_0106.html new file mode 100644 index 00000000..a8348ccc --- /dev/null +++ b/docs/dws/umn/dws_01_0106.html @@ -0,0 +1,12 @@ + + +

Development Specifications

+

If the connection pool mechanism is used during application development, the following specifications must be met. Otherwise, connections in the connection pool have statuses, which will affect the correctness of subsequent operations on the connection pool.

+ +
+
+
+
Parent topic: Using the JDBC and ODBC Drivers to Connect to a Cluster
+
+
+ diff --git a/docs/dws/umn/dws_01_0107.html b/docs/dws/umn/dws_01_0107.html new file mode 100644 index 00000000..594d8909 --- /dev/null +++ b/docs/dws/umn/dws_01_0107.html @@ -0,0 +1,153 @@ + + +

Step 3: Connecting to a Cluster

+

Scenario

This section describes how to use a database client to connect to the database in a GaussDB(DWS) cluster. In the following example, the Data Studio client tool is used for connection through the public network address. You can also use other SQL clients to connect to the cluster. For more connection methods, see Methods of Connecting to a Cluster.

+
  1. Obtain the name, username, and password of the database to be connected.

    If you use the client to connect to the cluster for the first time, use the database administrator username and password set in Step 2: Creating a Cluster to connect to the default database gaussdb.

    +
  2. Obtaining the Public Network Address of the Cluster: Connect to the cluster database using the public network address.
  3. Connecting to the Cluster Database Using Data Studio: Download and configure the Data Studio client and connect to the cluster database.
+
+

Obtaining the Public Network Address of the Cluster

  1. Log in to the GaussDB(DWS) management console.
  2. In the navigation tree on the left, click Clusters.
  3. In the cluster list, select a created cluster (for example, dws-demo) and click next to the cluster name to obtain the public network address.

    The public network address will be used in Connecting to the Cluster Database Using Data Studio.

    +
    Figure 1 Cluster management
    +

+
+

Connecting to the Cluster Database Using Data Studio

  1. GaussDB(DWS) provides a Windows-based Data Studio GUI client. The tool depends on JDK, so you must install Java 1.8.0_141 or later on the client host.

    In the Windows operating system, you can download the required JDK version from the official website of JDK, and install it by following the installation guide.

    +

  2. Log in to the GaussDB(DWS) management console.
  3. Click Connections.
  4. On the Download Client and Driver page, download Data Studio GUI Client.

    • Select Windows x86 or Windows x64 based on the operating system type and click Download to download the Data Studio tool matching the current cluster version.

      If clusters of different versions are available, you will download the Data Studio tool matching the earliest cluster version after clicking Download. If there is no cluster, you will download the Data Studio tool of the earliest version after clicking Download. GaussDB(DWS) clusters are compatible with earlier versions of Data Studio tools.

      +
    • Click Historical Version to download the corresponding Data Studio version. You are advised to download the Data Studio based on the cluster version.
    +
    Figure 2 Downloading clients
    +

  5. Decompress the downloaded client software package (32-bit or 64-bit) to the installation directory.
  6. Open the installation directory and double-click Data Studio.exe to start the Data Studio client. See Figure 3.

    Figure 3 Starting the client
    +

  7. Choose File > New Connection from the main menu. See Figure 4.

    Figure 4 Creating a connection
    +

  8. In the displayed New Database Connection window, enter the connection parameters.

    +

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Connection parameters

    Parameter

    +

    Description

    +

    Example

    +

    Database Type

    +

    Select GaussDB A.

    +

    GaussDB A

    +

    Connection Name

    +

    Name of a connection

    +

    dws-demo

    +

    Host

    +

    IP address (IPv4) or domain name of the cluster to be connected

    +

    -

    +

    Host Port

    +

    Database port

    +

    8000

    +

    Database Name

    +

    Database name

    +

    gaussdb

    +

    User Name

    +

    Username for connecting to the database

    +

    -

    +

    Password

    +

    Password for logging in to the database to be connected

    +

    -

    +

    Save Password

    +

    Select an option from the drop-down list:

    +
    • Current Session Only: The password is saved only in the current session.
    • Do Not Save: The password is not saved.
    +

    -

    +

    Enable SSL

    +

    If Enable SSL is selected, the client can use SSL to encrypt connections. The SSL mode is more secure than common modes, so you are advised to enable SSL connection.

    +

    -

    +
    +
    +

    When Enable SSL is selected, download and decompress the SSL certificate. For details, see (Optional) Downloading the SSL Certificate. Click the SSL tab and configure the following parameters:

    + +
    + + + + + + + + + + + + + + + + + + + +
    Table 2 Configuring SSL parameters

    Parameter

    +

    Description

    +

    Client SSL Certificate

    +

    Select the sslcert\client.crt file in the decompressed SSL certificate directory.

    +

    Client SSL Key

    +

    Only the PK8 format is supported. Select the sslcert\client.key.pk8 file in the directory where the SSL certificate is decompressed.

    +

    +

    Root Certificate

    +

    When SSL Mode is set to verify-ca, the root certificate must be configured. Select the sslcert\cacert.pem file in the decompressed SSL certificate directory.

    +

    SSL Password

    +

    Set the password for the client SSL key in PK8 format.

    +

    SSL Mode

    +

    Supported SSL modes include:

    +
    • require
    • verify-ca
    +

    GaussDB(DWS) does not support the verify-full mode.

    +
    +
    +
    Figure 5 Configuring SSL parameters
    +

  9. Click OK to establish the database connection.

    If SSL is enabled, click Continue in the displayed Connection Security Alert dialog box.

    +

    After the login is successful, the RECENT LOGIN ACTIVITY dialog box is displayed, indicating that Data Studio is connected to the database. You can run the SQL statement in the SQL Terminal window on the Data Studio page.

    +
    Figure 6 Successful login
    +

    For details about how to use other functions of Data Studio, press F1 to view the Data Studio user manual.

    +

+
+
+
+
+
Parent topic: Getting Started
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_0112.html b/docs/dws/umn/dws_01_0112.html new file mode 100644 index 00000000..5996d89e --- /dev/null +++ b/docs/dws/umn/dws_01_0112.html @@ -0,0 +1,239 @@ + + +

Viewing Basic Cluster Information

+

Log in to the GaussDB(DWS) management console. In the navigation tree on the left, choose Clusters. In the cluster list, locate the required cluster and click its name. The Basic Information page is displayed.

+

+
Figure 1 Basic cluster information
+

On a cluster's Basic Information page, you can view the following information:

+ + +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 Cluster information

Parameter

+

Description

+

Cluster Name

+

Cluster name specified when a cluster is created.

+

Cluster Status

+

Cluster running status. For details, see Cluster Status.

+

Parameter Configuration Status

+

Parameter configuration status of a cluster.

+

Task Information

+

Cluster task status. For details, see Cluster Task Information.

+

Cluster ID

+

ID of the cluster.

+

Nodes

+

Number of nodes in the cluster.

+

Cluster Version

+

Cluster version information.

+

Used Storage Capacity

+

Used storage capacity of the cluster.

+

Created

+

Time when the cluster was created.

+

Last Snapshot Created

+

Time when the last snapshot was created.

+

Maintenance Window

+

Maintenance window of the cluster.

+

You can click Configure on the right of Maintenance Window to configure the maintenance window. For more information, see Configuring the Maintenance Window.

+

Enterprise Project

+

Enterprise project to which a cluster belongs. You can click the enterprise project name to view and edit it on the console of the Enterprise Project service.

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 2 Database attribute parameters

Parameter

+

Description

+

Default Database

+

Database name specified when the cluster is created. When you connect to the cluster for the first time, connect to the default database.

+

Initial Administrator

+

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.

+

Port

+

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.

+

Connection String

+

Connection string. You can click View Details to check the data warehouse connection information. Its value can be:

+
  • JDBC URL (Private Network). In the private network environment, you can use the JDBC URL (private network) to connect to the cluster when developing applications.
  • JDBC URL (Public Network). In the public network environment, you can use the JDBC URL (public network) to connect to the cluster when developing applications.
  • ODBC URL. 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.
+

ELB Address

+

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.

+

Private Network Domain Name

+

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 ClusterName.dws.otc-tsi.de. When you access a data warehouse cluster using a domain name, the domain name resolver provides the load balancing function.

+
NOTE:

If the cluster name does not comply with the domain name standards, the prefix of the default access domain name will be adjusted accordingly.

+
+

You can click Modify 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.

+

For details, see Managing Access Domain Names.

+

Private Network IP Address

+

IP address for accessing the database in the cluster over the private network.

+
NOTE:
  • A private IP address is automatically generated when you create a cluster. The IP address is fixed.
  • The number of private IP addresses equals the number of CNs. You can log in to any node to connect to the cluster.
  • If you access a fixed IP address over the internal network, all the workloads will be processed on a single CN.
+
+

Public Network Domain Name

+

Name of the domain for accessing the database in the cluster over the public network.

+

For details, see Managing Access Domain Names.

+

Public Network IP Address

+

IP address for accessing the database in the cluster over the public network.

+
NOTE:
  • If no EIP is assigned during cluster creation and Public Network IP Address is empty, click Bind EIP to bind an EIP to the cluster.
  • If an EIP is bound during cluster creation, click Unbind EIP to unbind the EIP.
+
+
+
+ +
+ + + + + + + + + + +
Table 3 Node configuration

Parameter

+

Description

+

Node Flavor

+

Node flavor of the cluster.

+

Node Specifications

+

Specifications of the node flavor.

+
+
+ +
+ + + + + + + + + + + + + + + + + + + +
Table 4 Network

Parameter

+

Description

+

Region

+

Current working zone of the cluster.

+

AZ

+

AZ selected during cluster creation.

+

VPC

+

VPC selected during cluster creation.

+

A VPC is a secure, isolated, and logical network environment.

+

After a data warehouse cluster is created, its VPC cannot be changed. However, you can edit and modify the current VPC. You can click the VPC name to go to the VPC details page to configure it. For details about VPC operations, see VPC and Subnet in the Virtual Private Cloud User Guide.

+

Subnet

+

Subnet selected during cluster creation.

+

A subnet provides dedicated network resources that are isolated from other networks, improving network security.

+

After a data warehouse cluster is created, its subnet cannot be changed. However, you can edit and modify the current subnet. You can click the subnet name to go to the subnet details page to configure it. For details about subnet operations, see VPC and Subnet > Modifying a Subnet in the Virtual Private Cloud User Guide.

+

Security Group

+

Security group selected during cluster creation.

+

After a data warehouse cluster is created, its security group cannot be changed. However, you can edit and modify the current security group, and add, delete, or modify rules in it.

+

You can click the security group name to go to the security group details page to configure it. For details about security group operations, see Security > Security Group in the Virtual Private Cloud User Guide.

+
+
+ +
+ + + + + + + + + + +
Table 5 Data encryption information

Parameter

+

Description

+

Key Name

+

Indicates the database encryption key of the cluster when Encrypt DataStore is enabled.

+

Last Key Rotation Time

+

Indicates the time when the last encryption key is rotated when Encrypt DataStore is enabled.

+
+
+
+
+
+
Parent topic: Clusters
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_0113.html b/docs/dws/umn/dws_01_0113.html new file mode 100644 index 00000000..44b8358b --- /dev/null +++ b/docs/dws/umn/dws_01_0113.html @@ -0,0 +1,35 @@ + + +

Managing Enterprise Projects

+

An enterprise project is a cloud resource management mode. Enterprise Management provides users with comprehensive management in cloud-based resources, personnel, and permissions. Unlike common management consoles that feature independent control and configuration of cloud products, the Enterprise Management console is oriented to resource management. It helps enterprises with cloud-based management in resources, personnel, and permissions in the hierarchy of companies, departments, and projects.

+

Binding an Enterprise Project

You can select an enterprise project during cluster creation to associate it with the cluster. For details, see Creating a Cluster. The Enterprise Project drop-down list displays the projects you created. In addition, the system has a built-in enterprise project (default). If you do not select an enterprise project for the cluster, the default project is used.

+

During cluster creation, if the cluster is successfully bound to an enterprise project, the cluster will be successfully created. If the binding fails, the system sends an alarm and the cluster fails to be created.

+

Snapshots of a cluster retain the association between the cluster and its enterprise project. When the cluster is restored, the association is also restored.

+

When you delete a cluster, the association between the cluster and its enterprise project is automatically deleted.

+
+

Viewing Enterprise Projects

After a cluster is created, you can view the associated enterprise project in the cluster list and Basic Information page. You can query only the cluster resources of the project on which you have the access permission.

+

In the cluster list on the Clusters page, view the enterprise project to which the cluster belongs.

+
Figure 1 Viewing the enterprise project
+

In the cluster list, find the target cluster and click the cluster name. The Basic Information page is displayed, on which you can view the enterprise project associated with the cluster. Click the enterprise project name to view and edit it on the Enterprise Management console.

+
Figure 2 Viewing the enterprise project
+

When querying the resource list of a specified project on the Enterprise Management console, you can also query the GaussDB(DWS) resources.

+
+

Searching for Clusters by Enterprise Project

Log in to the GaussDB(DWS) management console, choose Clusters, click All projects above the cluster list, and select the required project name from the drop-down list to view all clusters associated with the project.

+
Figure 3 Search by enterprise projects
+
+

Migrating a Cluster to or Out of an Enterprise Project

A GaussDB(DWS) cluster can be associated with only one enterprise project. After a cluster is created, you can migrate it from its current enterprise project to another one on the Enterprise Management console, or migrate the cluster from another enterprise project to a specified enterprise project. After the migration, the cluster is associated with the new enterprise project. The association between the cluster and the original enterprise project is automatically released. For details, see "Resource Management > Managing Enterprise Project Resources" in the Enterprise Management User Guide.

+
+
+
+
+
Parent topic: Clusters
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_0118.html b/docs/dws/umn/dws_01_0118.html new file mode 100644 index 00000000..cadabc85 --- /dev/null +++ b/docs/dws/umn/dws_01_0118.html @@ -0,0 +1,122 @@ + + +

Viewing Audit Logs of Key Operations on the Management Console

+

This section is organized as follows:

+ +

Enabling CTS

A tracker will be automatically created after CTS is enabled. All traces recorded by CTS are associated with a tracker. Currently, only one tracker can be created for each account.

+
  1. Log in to the management console, choose Service List > Management & Governance > Cloud Trace Service. The CTS management console is displayed.
  2. In the navigation tree on the left, choose Cloud Trace Service > Tracker.
  3. Enable CTS.

    If you are a first-time CTS user and do not have any trackers in the tracker list, enable CTS first. For details, see "Getting Started > Enabling CTS" in the Cloud Trace Service User Guide.

    +

    If you have enabled CTS, the system has automatically created a management tracker. Only one management tracker can be created and it cannot be deleted. You can also manually create a data tracker. For details, see "Tracker Management > Creating a Tracker" in the Cloud Trace Service User Guide.

    +

+
+

Disabling the Audit Log Function

If you want to disable the audit log function, disable the tracker in CTS.

+
  1. Log in to the management console, choose Service List > Management & Governance > Cloud Trace Service. The CTS management console is displayed.
  2. Disable the audit log function by disabling the tracker. To enable the audit log function again, you only need to enable the tracker.

    For details about how to enable or disable a tracker, see "Tracker Management > Disabling or Enabling a Tracker" in the Cloud Trace Service User Guide.

    +

+
+

Key Operations

With CTS, you can record operations associated with GaussDB(DWS) for later query, audit, and backtrack operations.

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 GaussDB(DWS) operations that can be recorded by CTS

Operation

+

Resource

+

Event Name

+

Creating/Restoring a cluster

+

cluster

+

createCluster

+

Deleting a cluster

+

cluster

+

deleteCluster

+

Scaling out a cluster

+

cluster

+

growCluster

+

Restarting a cluster

+

cluster

+

rebootCluster

+

Creating a snapshot

+

backup

+

createBackup

+

Deleting a snapshot

+

backup

+

deleteBackup

+

Setting security parameters

+

configurations

+

updateConfigurations

+

Creating an MRS data source

+

dataSource

+

createExtDataSource

+

Deleting an MRS data source

+

dataSource

+

deleteExtDataSource

+

Updating an MRS data source

+

dataSource

+

updateExtDataSource

+
+
+
+

Viewing Traces

  1. Log in to the management console, choose Service List > Management & Governance > Cloud Trace Service. The CTS management console is displayed.
  2. In the navigation pane on the left, choose Trace List.
  3. In the upper right corner of the trace list, click Filter to set the search criteria.

    The following filters are available:

    +
    • Trace Source, Resource Type, and Search By
      • Trace Source: Select GaussDB(DWS).
      • Resource Type: Select All resource types or specify a resource type.
      • Search By: Select All filters or any of the following options:
        • Trace name: If you select this option, you also need to select a specific trace name.
        • Resource ID: If you select this option, you also need to select or enter a specific resource ID.
        • Resource name: If you select this option, you also need to select or enter a specific resource name.
        +
      +
    • Operator: Select a specific operator (at user level rather than tenant level).
    • Trace Status: Available options include All trace statuses, normal, warning, and incident. You can only select one of them.
    • Start Date and End Date: You can specify the time period to query traces.
      Figure 1 Querying traces
      +
    +

  4. Click Query.
  5. Click on the left of the trace to be queried to extend its details.

    Figure 2 Traces
    +

  6. Locate the row containing the target trace and click View Trace in the Operation column.

    Figure 3 Viewing a trace
    +

    For details about the key fields in the CTS trace structure, see "Trace References > Trace Structure" and "Trace References > Example Traces" in the Cloud Trace Service User Guide.

    +

+
+
+
+
+
Parent topic: Audit Logs
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_0119.html b/docs/dws/umn/dws_01_0119.html new file mode 100644 index 00000000..0c764b58 --- /dev/null +++ b/docs/dws/umn/dws_01_0119.html @@ -0,0 +1,17 @@ + + +

Audit Logs

+
+
+ +
+ diff --git a/docs/dws/umn/dws_01_0126.html b/docs/dws/umn/dws_01_0126.html new file mode 100644 index 00000000..db757709 --- /dev/null +++ b/docs/dws/umn/dws_01_0126.html @@ -0,0 +1,85 @@ + + +

Managing Parameter Templates

+

To facilitate database parameter configuration, GaussDB(DWS) provides the parameter template function. A parameter template contains some common database parameters. You can manage parameter templates on the GaussDB(DWS) management console. After applying a parameter template to a cluster, you can modify parameters on the parameter modification page of the cluster.

+

The following parts are included in this section:

+ +

Overview

A parameter template is a set of parameters applicable to data warehouses. All parameters in the template have default values. The parameters include the session timeout interval, date, and time format. For details, see Parameters. You can adjust parameter values to better adapt the database to actual services. When creating a cluster, you can specify a parameter template for it. Parameters in the template will be applied to all databases in the cluster. If you do not specify a parameter template, the system applies the default parameter template to the cluster. After a cluster is created, you can modify the parameters on the Parameter Modifications page. Alternatively, select an existing parameter template or create a parameter template on the Parameter Template Management page and apply it to the cluster.

+

GaussDB(DWS) presets a default parameter template to data warehouses of each version. The default parameter template cannot be deleted and modified. If you want to modify parameter values in the template, create a customized parameter template. The parameters in the customized template can be modified. After a customized parameter template is applied to a cluster, it is not associated with the cluster. If you modify the parameter values in the template, the modifications will not be synchronized to the cluster. You need to apply the template to the cluster again, and then the modified parameter values can be applied to the cluster. Similarly, if you modify parameters on the cluster details page, the modifications will not be synchronized to the parameter template.

+

The default values of the following parameters are for reference only. For more information, see "Setting GUC Parameters".

+
+
+

Parameters

The parameter template only contains three parameters. These parameters will take effect on a cluster during cluster installation. You can check more parameters on the cluster parameter modification page of the console. For details, see Modifying Database Parameters.

+ +
+ + + + + + + + + + + + + + + + + +
Table 1 Parameters

Parameter

+

Description

+

Default Value

+

timezone

+

Sets the time zone displayed in the time stamps.

+

UTC

+

log_timezone

+

Sets the time zone for timestamps in the server log.

+

UTC

+

password_encryption_type

+

Specifies the encryption type of user passwords.

+
  • 0 indicates that passwords are encrypted with MD5.
  • 1 indicates that passwords are encrypted with SHA-256, which is compatible with the MD5 user authentication method of the PostgreSQL client.
  • 2 indicates that passwords are encrypted with SHA-256. MD5 is not recommended because it is not a secure encryption algorithm.
+

1

+
+
+
+

Creating a Parameter Template

If parameters in the default parameter template cannot meet service requirements, you can customize a parameter template and change the parameter values to better adapt to services.

+

To create a parameter template, perform the following steps:

+
  1. Log in to the GaussDB(DWS) management console.
  2. In the navigation tree on the left, click Parameter Templates.
  3. Click Create Parameter Template and set the following parameters:

    • Database Engine: Select a database engine.
    • Database Version: Select a database version.
    • Name: Enter the name of the new parameter template.

      Enter 4 to 64 characters. Only letters, digits, hyphens (-), underscores (_), and periods (.) are allowed. The value must start with a letter. Letters are case-insensitive.

      +
    • Description: Enter the description of the new parameter template. This parameter is optional.

      The parameter template description contains 0 to 256 characters and does not support special characters !<>'=&".

      +
    +

    The Database Engine and Database Version selected during parameter template creation must be the same as the cluster type and version of the parameter template to be applied.

    +
    +
    Figure 1 Creating a parameter template
    +

  4. Click OK.
+
+

Modifying a Parameter Template

You can modify the parameter values in a customized parameter template but cannot modify the parameter values in the default parameter template.

+
  1. Log in to the GaussDB(DWS) management console.
  2. In the navigation tree on the left, click Parameter Templates.
  3. In the Name column, click the name of the target parameter template. Its parameter table is displayed.
  4. Enter a new value in the Value column of the parameter to be modified. After the modification, click Save.

    Figure 2 Modifying parameters
    +

  5. In the Modification Preview dialog box, confirm the settings and modifications and click Save.
+
+

Applying a Parameter Template to the Cluster

After a cluster is created, you can apply a new parameter template to the cluster so that the values of all parameters in the parameter template can take effect in the cluster.

+

To apply a parameter template, perform the following steps:

+
  1. Log in to the GaussDB(DWS) management console.
  2. In the navigation tree on the left, click Parameter Templates.
  3. Select the target parameter template and click Apply in the Operation column.
  4. In the Parameter Template Application dialog box that is displayed, select the target cluster.

    You can apply the selected parameter template to the cluster corresponding to the parameter template version.

    +
    Figure 3 Parameter template application
    +

  5. Click OK.

    If some parameter values in the new parameter template are different from the original parameter values in the cluster, a window comparing the differences will be displayed.

    +

+
+

Deleting a Parameter Template

You can delete an unnecessary parameter template or a parameter template that is no longer used. The default parameter template cannot be deleted. Deleted parameter templates cannot be restored. Exercise caution when performing this operation.

+
  1. Log in to the GaussDB(DWS) management console.
  2. In the navigation tree on the left, click Parameter Templates.
  3. In the Operation column of the parameter template to be deleted, click Delete.
  4. In the displayed dialog box, click Yes.
+
+
+
+
+
Parent topic: Clusters
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_0128.html b/docs/dws/umn/dws_01_0128.html new file mode 100644 index 00000000..21868d7c --- /dev/null +++ b/docs/dws/umn/dws_01_0128.html @@ -0,0 +1,27 @@ + + +

Preparing an ECS as the gsql Client Host

+

The gsql command line client provided by GaussDB(DWS) runs on the Linux OS. Before using it to remotely connect to a GaussDB(DWS) cluster, you need to prepare a Linux host for installing and running the gsql client. If you use a public network address to access the cluster, you can install the gsql client on your own Linux host. Ensure that the Linux host has a public network address. For your convenience, you are advised to create a Linux ECS. This section describes how to prepare an ECS. If you already have a qualified ECS, skip this section.

+

Preparing an ECS

For details about how to create an ECS, see "Getting Started > Creating an ECS" in the Elastic Cloud Server User Guide.

+

The created ECS must meet the following requirements:

+ +
+
+
+
+
Parent topic: Using the gsql CLI Client to Connect to a Cluster
+
+
+ diff --git a/docs/dws/umn/dws_01_0131.html b/docs/dws/umn/dws_01_0131.html new file mode 100644 index 00000000..802f1be5 --- /dev/null +++ b/docs/dws/umn/dws_01_0131.html @@ -0,0 +1,21 @@ + + +

Cluster Connection

+
+
+ +
+ diff --git a/docs/dws/umn/dws_01_0132.html b/docs/dws/umn/dws_01_0132.html new file mode 100644 index 00000000..3d02965f --- /dev/null +++ b/docs/dws/umn/dws_01_0132.html @@ -0,0 +1,112 @@ + + +

Configuring the JDBC Connection to Connect to a Cluster Using IAM Authentication

+

When you use the JDBC application program to connect to a cluster, set the IAM username, credential, and other information as you configure the JDBC URL. After doing this, when you try to access a database, the system will automatically generate a temporary credential and a connection will be set up.

+

Currently, only clusters whose version is 1.3.1 or later and their corresponding JDBC driver provided by GaussDB(DWS) can access the databases in IAM authentication mode. Download the JDBC driver. For details, see Downloading the JDBC or ODBC Driver.

+
+

Configuring JDBC Connection Parameters

+
+ + + + + + + + + + +
Table 1 Database connection parameters

Parameter

+

Description

+

url

+

gsjdbc4.jar/gsjdbc200.jar database connection descriptor. The JDBC API does not provide the connection retry capability. You need to implement the retry processing in the service code. The URL example is as follows:

+
jdbc:dws:iam://dws-IAM-demo:eu-de/gaussdb?AccessKeyID=XXXXXXXXXXXXXXXXXXXX&SecretAccessKey=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX&DbUser=user_test&AutoCreate=true
+

JDBC URL parameters:

+
  • jdbc:dws:iam is a prefix in the URL format.
  • dws-IAM-demo indicates the name of the cluster containing the database.
  • eu-de indicates the region where the cluster resides.
  • gaussdb indicates the name of the database to which you want to connect.
  • AccessKeyID and SecretAccessKey are the access key ID and secret access key corresponding to the IAM user specified by DbUser.
  • Set DbUser to the IAM username. Note that the current version does not support hyphens (-) in the IAM username.
    • If the user specified by DbUser exists in the database, the temporary user credential has the same permissions as the existing user.
    • If the user specified by DbUser does not exist in the database and the value of AutoCreate is true, a new user named by the value of DbUser is automatically created. The created user is a common database user by default.
    +
  • Parameter AutoCreate is optional. The default value is false. This parameter indicates whether to automatically create a database user named by the value of DbUser in the database.
    • The value true indicates that a user is automatically created. If the user already exists, the user will not be created again.
    • The value false indicates that a user is not created. If the username specified by DbUser does not exist in the database, an error is returned.
    +
+

info

+

Database connection properties. Common properties include the following:

+
  • ssl: a boolean type. It indicates whether the SSL connection is used.
  • loglevel: an integer type. It sets the log amount recorded in DriverManager for LogStream or LogWriter.

    Currently, org.postgresql.Driver.DEBUG and org.postgresql.Driver.INFO logs are supported. If the value is 1, only org.postgresql.Driver.INFO (little information) is recorded. If the value is greater than or equal to 2, org.postgresql.Driver.DEBUG and org.postgresql.Driver.INFO logs are printed, and detailed log information is generated. Its default value is 0, which indicates that no logs are printed.

    +
  • charSet: a string type. It indicates character sets used when data is sent from the database or the database receives data.
  • prepareThreshold: an integer type. It is used to determine the execution times of PreparedStatement before the information is converted into prepared statements on the server. The default value is 5.
+
+
+
+

Example

 1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+19
+20
+21
+22
+23
+24
+25
+26
+27
+28
+29
+30
+31
+32
+33
+34
//The following uses gsjdbc4.jar as an example. 
+//The following encapsulates the database connection obtaining operations into an API. You can connect to the database by specifying the region where the cluster is located, cluster name, access key ID, secret access key, and the corresponding IAM username.
+public static Connection GetConnection(String clustername, String regionname, String AK, String SK, String username) 
+    {
+        //Driver class
+        String driver = "org.postgresql.Driver";
+        // Database connection descriptor.
+        String sourceURL = "jdbc:dws:iam://" + clustername + ":" + regionname + "/gaussdb?" + "AccessKeyID=" + AK + "&SecretAccessKey=" + SK + "&DbUser=" + username + "&autoCreate=true";
+        
+        Connection conn = null;
+        
+        try
+        {
+            //Load the driver.
+            Class.forName(driver);
+        }
+        catch( Exception e )
+        {
+             return null;
+        }
+        
+        try
+        {
+             //Create a connection.
+            conn = DriverManager.getConnection(sourceURL);
+            System.out.println("Connection succeed!");
+         }
+        catch(Exception e)
+        {
+             return null;
+        }
+        
+        return conn;
+    };
+
+ +
+
+
+
+
+
Parent topic: Connecting to a Cluster Using IAM Authentication
+
+
+ diff --git a/docs/dws/umn/dws_01_0133.html b/docs/dws/umn/dws_01_0133.html new file mode 100644 index 00000000..d102c6b5 --- /dev/null +++ b/docs/dws/umn/dws_01_0133.html @@ -0,0 +1,22 @@ + + +

Connecting to a Cluster Using IAM Authentication

+

+
+
+ + +
+
Parent topic: Using the JDBC and ODBC Drivers to Connect to a Cluster
+
+
+ diff --git a/docs/dws/umn/dws_01_0134.html b/docs/dws/umn/dws_01_0134.html new file mode 100644 index 00000000..99ef83bf --- /dev/null +++ b/docs/dws/umn/dws_01_0134.html @@ -0,0 +1,17 @@ + + +

Overview

+

GaussDB(DWS) allows you to access databases using IAM authentication. When you use the JDBC application program to connect to a cluster, set the IAM username, credential, and other information as you configure the JDBC URL. After doing this, when you try to access a database, the system will automatically generate a temporary credential and a connection will be set up.

+
  • Currently, only clusters 1.3.1 and later versions and their corresponding JDBC drivers can access the databases in IAM authentication mode.
+
+

IAM supports two types of user credential: password and Access Key ID/Secret Access Key (AK/SK). JDBC connection requires the latter.

+

The IAM account you use to access a database must be granted with the DWS Database Access permission. Only users with both the DWS Administrator and DWS Database Access permissions can connect to GaussDB(DWS) databases using the temporary database user credentials generated based on IAM users.

+

The process of accessing a database is as follows:

+
  1. Granting an IAM Account the DWS Database Access Permission
  2. Creating an IAM User Credential
  3. Configuring the JDBC Connection to Connect to a Cluster Using IAM Authentication
+
+
+
+
Parent topic: Connecting to a Cluster Using IAM Authentication
+
+
+ diff --git a/docs/dws/umn/dws_01_0135.html b/docs/dws/umn/dws_01_0135.html new file mode 100644 index 00000000..f789b0ed --- /dev/null +++ b/docs/dws/umn/dws_01_0135.html @@ -0,0 +1,18 @@ + + +

Granting an IAM Account the DWS Database Access Permission

+

The IAM account you use to access a database must be granted with the DWS Database Access permission. Only users with both the DWS Administrator and DWS Database Access permissions can connect to GaussDB(DWS) databases using the temporary database user credentials generated based on IAM users. Using the DWS Database Access permission helps to control access to databases.

+

The DWS Database Access permission can only be granted to user groups. Ensure that your IAM account is in a user group with this permission.

+

On IAM, only users in the admin group have the permissions to manage users. This requires that your IAM account be in the admin user group. Otherwise, contact the IAM account administrator to grant your IAM account this permission.

+

Procedure

  1. Log in to the cloud management console and choose Service List > Management & Governance > Identity and Access Management to enter the IAM management console.
  2. Modify the user group to which your IAM user belongs. Set a policy for, grant the DWS Database Access permission to, and add your IAM user to it.

    Only users in the admin user group of IAM can perform this step. In IAM, only users in the admin user group can manage users, including creating user groups and users and setting user group rights.

    +

    For details, see "User and User Group Management > Viewing or Modifying User Group Information" in the Identity and Access Management User Guide.

    +

    You can also create an IAM user group, and set a policy for, grant the DWS Administrator and DWS Database Access permissions to, and add your IAM user to it. For details, see "User and User Group Management > Creating a User Group" in the Identity and Access Management User Guide.

    +

+
+
+
+
+
Parent topic: Connecting to a Cluster Using IAM Authentication
+
+
+ diff --git a/docs/dws/umn/dws_01_0136.html b/docs/dws/umn/dws_01_0136.html new file mode 100644 index 00000000..217fd06b --- /dev/null +++ b/docs/dws/umn/dws_01_0136.html @@ -0,0 +1,16 @@ + + +

Creating an IAM User Credential

+

You can log in to the management console to create an AK/SK pair or use an existing one.

+

Creating an AK/SK Pair

Log in to the management console, move your cursor over your account in the upper right corner, and choose My Credential. Click the Access Keys tab. On the Access Keys tab page, you can view the existing AKs or click Add Access Key to create an AK/SK pair.

+

The AK/SK pair is so important that you can download the private key file containing the AK/SK information only when you create the pair. On the management console, you can only view the AKs. If you have not downloaded the file, create an AK/SK pair again.

+

Each user can create a maximum of two AK/SK pairs, which are valid permanently. To ensure account security, change your AK/SK pairs periodically and keep them safe.

+
+
+
+
+
+
Parent topic: Connecting to a Cluster Using IAM Authentication
+
+
+ diff --git a/docs/dws/umn/dws_01_0137.html b/docs/dws/umn/dws_01_0137.html new file mode 100644 index 00000000..ee8e28e2 --- /dev/null +++ b/docs/dws/umn/dws_01_0137.html @@ -0,0 +1,18 @@ + + +

Methods of Connecting to a Cluster

+

If you have created a GaussDB(DWS) cluster, you can use the SQL client tool or a third-party driver such as JDBC or ODBC to connect to the cluster and access the database in the cluster.

+

The procedure for connecting to a cluster is as follows:

+
  1. Obtaining the Cluster Connection Address
  2. If SSL encryption is used, perform the following steps:
    1. (Optional) Configuring SSL Connection
    2. (Optional) Downloading the SSL Certificate
    +
  3. Connect to the cluster and access the database in the cluster. You can choose any of the following methods to connect to a cluster: +
+
+
+
+
Parent topic: Cluster Connection
+
+
+ diff --git a/docs/dws/umn/dws_01_01372.html b/docs/dws/umn/dws_01_01372.html new file mode 100644 index 00000000..0fd80457 --- /dev/null +++ b/docs/dws/umn/dws_01_01372.html @@ -0,0 +1,16 @@ + + +

SQL Diagnosis

+

Symptom

The execution of SQL statements takes a long time, resulting in great resource consumption.

+
+

Troubleshooting Process

If the execution efficiency of SQL statements is low, optimization suggestions are provided after the kernel executes the SQL statements. You can query the execution history to retrieve optimization suggestions and further optimize SQL statements to improve query efficiency.

+
+

Troubleshooting Procedure

  1. On the SQL Diagnosing page, select a time period that does not seem right.
  2. Search for SQL statements based on indicators such as the start time, end time, and running duration of the statement.
  3. Click Details to view SQL optimization suggestions.
  4. Optimize the SQL statement based on suggestions.
+
+
+
+
+
Parent topic: Typical Scenarios
+
+
+ diff --git a/docs/dws/umn/dws_01_01373.html b/docs/dws/umn/dws_01_01373.html new file mode 100644 index 00000000..0eef15b8 --- /dev/null +++ b/docs/dws/umn/dws_01_01373.html @@ -0,0 +1,18 @@ + + +

Top Time-Consuming SQL Statements Viewing

+

Symptom

Time-consuming SQL statements exist.

+
+

Troubleshooting Process

On the Top 5 Time-Consuming Queries page directed from the Cluster Overview page, record the change of top 5 time-consuming queries.

+

Analyze the frequency of top 5 queries to locate slow queries.

+
+

Troubleshooting Procedure

  1. On the Cluster Overview page, click and view the Top5 Time-Consuming Queries page.
  2. Find the IDs of time-consuming queries and query the pid field (session_id) in the database view PGXC_WLM_SESSION_STATISTICS.
  3. On the Session Monitoring page, locate the session_id and kill the time-consuming SQL statement.
+
+

+
+
+
+
Parent topic: Typical Scenarios
+
+
+ diff --git a/docs/dws/umn/dws_01_0140.html b/docs/dws/umn/dws_01_0140.html new file mode 100644 index 00000000..2cf9b7ef --- /dev/null +++ b/docs/dws/umn/dws_01_0140.html @@ -0,0 +1,40 @@ + + +

Managing Access Domain Names

+

Overview

A domain name is a string of characters separated by dots to identify the location of a computer or a computer group on the Internet, for example, www.example.com. You can enter a domain name in the address box of the web browser to access a website or web application.

+
+

On GaussDB(DWS), you can access clusters using the private network domain name or the public network domain name.

+

Private network domain name: Name of the domain for accessing the database in the cluster through the private network. The private network domain name is automatically generated when you create a cluster. The default naming rule is cluster name.dws.otc-tsi.de. If the cluster name does not comply with the domain name standards, the prefix of the default access domain name will be adjusted accordingly.

+

Public network domain name: Name of the domain for accessing the database in the cluster through the public network. If a cluster is not bound to an EIP, it cannot be accessed using the public network domain name. If you bind an EIP during cluster creation, the public network domain name is automatically generated. The default naming rule is cluster name.dws.t-systems.com.

+

After a cluster is created, you can set private and public domain names for accessing the cluster as required. The operations are as follows:

+ +

Modifying a Private Network Domain Name

The private network domain name is automatically generated during cluster creation. After the cluster is created, you can modify the default domain name based on site requirements.

+

To modify the private network domain name, perform the following steps:

+
  1. Log in to the GaussDB(DWS) management console.
  2. In the navigation tree on the left, choose Clusters.
  3. In the cluster list, find the target cluster and click the cluster name. The Basic Information page is displayed.
  4. In the Database Attribute area, click Modify next to the automatically generated Private Network Domain Name.
  5. In the Modify Private Network Domain Name dialog box, enter the target domain name and click OK.

    The private network domain name contains 4 to 63 characters, which consists of letters, digits, and hyphens (-) and must start with a letter.

    +

    After the domain name is modified, click copy button next to the private network domain name to copy it.

    +

+
+

Creating a Public Network Domain Name

A cluster is not bound to an EIP by default during cluster creation. That is, cluster access using the public network is disabled. After a cluster is created, if you want to access it over the public network, bind an EIP to the cluster and create a public network domain name.

+

To create a public network domain name, perform the following steps:

+
  1. Log in to the GaussDB(DWS) management console.
  2. In the navigation tree on the left, choose Clusters.
  3. In the cluster list, find the target cluster and click the cluster name. The Basic Information page is displayed.
  4. In the Database Attribute area, Public Network Domain Name and Public Network IP Address are empty. Click Bind EIP to bind the cluster with an EIP.

    +

  5. Select an EIP from the drop-down list in the Bind EIP dialog box.

    If no available EIPs are displayed, click View EIP to go to the Elastic IP page and create an EIP that satisfies your needs. After the new EIP is created, click the refresh icon next to the drop-down list. The newly created EIP will be displayed in the EIP drop-down list.

    +

    After the EIP is bound successfully, the specific public network IP address is displayed in the Database Attribute area.

    +

  6. In the Database Attribute area, click Create next to Public Network Domain Name to create a public network domain name for the cluster.
  7. In the Apply for Public Network Domain Name dialog box, enter the target domain name and click OK.

    The public network domain name contains 4 to 63 characters, which consists of letters, digits, and hyphens (-) and must start with a letter.

    +

    The specific public network domain name is displayed in the Database Attribute area after being created. Click copy button to copy the public network domain name.

    +

+
+

Modifying a Public Network Domain Name

If you bind an EIP during cluster creation, the public network domain name is automatically generated. After a cluster is created, you can modify the public network domain name as required.

+

To modify the public network domain name, perform the following steps:

+
  1. Log in to the GaussDB(DWS) management console.
  2. In the navigation tree on the left, choose Clusters.
  3. In the cluster list, find the target cluster and click the cluster name. The Basic Information page is displayed.
  4. Click Modify next to the Public Network Domain Name in the Database Attribute area.
  5. In the Modify Public Network Domain Name dialog box, enter the target domain name and click OK.
+
+

Releasing a Public Network Domain Name

After a cluster is created, you can release unnecessary public network domain names.

+

To do so, perform the following steps:

+
  1. Log in to the GaussDB(DWS) management console.
  2. In the navigation pane on the left, choose Clusters.
  3. In the cluster list, find the target cluster and click the cluster name. The Basic Information page is displayed.
  4. Click Release next to the Public Network Domain Name in the Database Attribute area.
  5. In the Release Domain Name dialog box, click Yes.
+
+
+
+
+
Parent topic: Clusters
+
+
+ diff --git a/docs/dws/umn/dws_01_0142.html b/docs/dws/umn/dws_01_0142.html new file mode 100644 index 00000000..556b5dff --- /dev/null +++ b/docs/dws/umn/dws_01_0142.html @@ -0,0 +1,112 @@ + + +

Dumping the Database Audit Logs

+

GaussDB(DWS) records information (audit logs) about connections and user activities in your database. With the information, you can monitor the database to ensure security and facilitate fault troubleshooting and historical operation record locating. These audit logs are stored in the database by default. You can also dump them to OBS so that users who are responsible for monitoring the database can view the logs more conveniently.

+

You can perform the following operations on the GaussDB(DWS) console:

+ +

Enabling Audit Log Dumps

After a data warehouse cluster is created, you can enable audit log dump for it to dump audit logs to OBS.

+

Before enabling audit log dump, ensure that the following conditions are met:

+ +

The procedure is as follows:

+
  1. Log in to the GaussDB(DWS) management console.
  2. In the navigation tree on the left, click Clusters.
  3. In the cluster list, click the name of the cluster for which you want to enable audit log dump. On the page that is displayed, click Security Settings.
  4. In the Audit Settings area, enable Audit Log Dump.

    indicates that the function is enabled. indicates that the function is disabled.

    +

    When you enable audit log dump for a project in a region for the first time, the system prompts you to create an agency named DWSAccessOBS. After the agency is created, GaussDB(DWS) can dump audit logs to OBS. By default, only cloud accounts or users with Security Administrator permissions can create agencies. IAM users under an account do not have the permission for creating agencies by default. Contact a user with the permission and complete the authorization on the current page.

    +
    • OBS Bucket: Name of the OBS bucket used to store the audit data. If no OBS bucket is available, click View OBS Bucket to access the OBS console and create one. For details, see Console Operation Guide > Managing Buckets > Creating a Bucket in the Object Storage Service User Guide.
    • OBS Path: User-defined directory on OBS for storing audit files. Different directory levels are separated by forward slashes (/). The value is a string containing 1 to 50 characters, which cannot start with a forward slash (/). If the entered OBS path does not exist, the system creates one and dumps data to it.
    • Dump Interval (Minute): Interval based on which GaussDB(DWS) periodically dumps data to OBS. The value ranges from 5 to 43200. The unit is minute.
    +

  5. Click Apply.

    If Configuration Status is Applying, the system is saving the settings.

    +

    Wait for a moment and then refresh Configuration Status. When Configuration Status is Synchronized, the configuration is saved and takes effect.

    +

+
+

Modifying Audit Log Dump Configurations

After audit log dump is enabled, you can modify the dump configurations, for example, modifying the OBS bucket, path, and dump interval.

+

The procedure is as follows:

+
  1. Log in to the GaussDB(DWS) management console.
  2. In the navigation tree on the left, click Clusters.
  3. In the cluster list, click the name of the cluster for which you want to modify the audit log dump configurations. On the page that is displayed, click Security Settings.
  4. In the Audit Settings area, modify the Audit Log Dump configurations.
  5. Click Apply.

    If Configuration Status is Applying, the system is saving the settings.

    +

    Wait for a moment and then refresh Configuration Status. When Configuration Status is Synchronized, the configuration is saved and takes effect.

    +

+
+

Viewing Audit Log Dumps

After audit log dump is enabled, you can view the dumped audit logs on OBS.

+

The procedure is as follows:

+
+
  1. Log in to the GaussDB(DWS) management console.
  2. In the navigation tree on the left, click Clusters.
  3. In the cluster list, click the name of the target cluster. On the page that is displayed, click Security Settings.
  4. In the Audit Settings area, click View Dump Record.
  5. In the Audit Log Dump Records dialog box, click View OBS Bucket. The OBS console page is displayed.
  6. Select the OBS bucket and folder where the logs are stored to view the log files.

    You can download and decompress the files to view. The fields of audit log files are described as follows:

    + +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Log file fields

    Name

    +

    Description

    +

    time

    +

    Indicates the operation time.

    +

    type

    +

    Indicates the operation type.

    +

    result

    +

    Indicates the operation result.

    +

    username

    +

    Indicates the name of the user who initiates the operation.

    +

    database

    +

    Indicates the database name.

    +

    client_conninfo

    +

    Indicates the client connection information.

    +

    object_name

    +

    Indicates the operation object name.

    +

    detail_info

    +

    Indicates the detailed information about the operation.

    +

    node_name

    +

    Indicates the node name.

    +

    thread_id

    +

    Indicates the thread ID.

    +

    local_port

    +

    Indicates the local port.

    +

    remote_port

    +

    Indicates the remote port.

    +
    +
    +

+

Disabling Audit Log Dumps

You can disable audit log dumps if you do not want to dump audit logs to OBS.

+

The procedure is as follows:

+
+
  1. Log in to the GaussDB(DWS) management console.
  2. In the navigation tree on the left, click Clusters.
  3. In the cluster list, click the name of the cluster for which you want to disable audit log dump. On the page that is displayed, click Security Settings.
  4. In the Audit Settings area, disable audit log dump.

    indicates that the function is disabled.

    +

  5. Click Apply.

    If Configuration Status is Applying, the system is saving the settings.

    +

    Wait for a moment and then refresh Configuration Status. When Configuration Status is Synchronized, the configuration is saved and takes effect.

    +

+
+
+
+
Parent topic: Audit Logs
+
+
+ diff --git a/docs/dws/umn/dws_01_0144.html b/docs/dws/umn/dws_01_0144.html new file mode 100644 index 00000000..bbf839c2 --- /dev/null +++ b/docs/dws/umn/dws_01_0144.html @@ -0,0 +1,397 @@ + + +

GaussDB(DWS) Permissions Management

+

If you need to assign different permissions to employees in your enterprise to access your cloud GaussDB(DWS) resources, IAM is a good choice for fine-grained permissions management. IAM provides identity authentication, permissions management, and access control, helping you secure access to your cloud resources.

+

With IAM, you can use your cloud account to create IAM users for your employees, and assign permissions to the users to control their access to specific resource types. For example, some software developers in your enterprise need to use GaussDB(DWS) resources but must not delete them or perform any high-risk operations. To this end, you can create IAM users for the software developers and grant them only the permissions required for using GaussDB(DWS) resources.

+

If your cloud account does not need individual IAM users for permissions management, you may skip this section.

+

IAM can be used free of charge. You pay only for the resources in your account. For more information about IAM, see "Service Overview" in the Identity and Access Management User Guide.

+

Supported System Policies

By default, new IAM users do not have permissions assigned. You need to add a user to one or more groups, and attach permissions policies or roles to these groups. Users inherit permissions from the groups to which they are added and can perform specified operations on cloud services.

+

GaussDB(DWS) is a project-level service deployed and accessed in specific physical regions. To assign GaussDB(DWS) permissions to a user group, specify the scope as region-specific projects and select projects for the permissions to take effect. If All projects is selected, the permissions will take effect for the user group in all region-specific projects. When accessing GaussDB(DWS), the users need to switch to a region where they have been authorized to use GaussDB(DWS).

+ +
Table 1 lists all the system-defined roles and policies supported by GaussDB(DWS). +
+ + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 GaussDB(DWS) system permissions

Role/Policy Name

+

Description

+

Category

+

Dependencies

+

DWS ReadOnlyAccess

+

Read-only permissions for GaussDB(DWS). Users granted these permissions can only view GaussDB(DWS) data.

+

System-defined policy

+

N/A

+

DWS FullAccess

+

Administrator permissions for GaussDB(DWS). Users granted these permissions can perform all operations on GaussDB(DWS).

+

System-defined policy

+

N/A

+

DWS Administrator

+

Administrator permissions for GaussDB(DWS). Users granted these permissions can perform operations on all GaussDB(DWS) resources.

+
  • Users granted permissions of the VPC Administrator policy can create VPCs and subnets.
  • Users granted permissions of the Cloud Eye Administrator policy can view monitoring information of data warehouse clusters.
+

System-defined role

+

Dependent on the Tenant Guest and Server Administrator policies, which must be assigned in the same project as the DWS Administrator policy.

+

DWS Database Access

+

GaussDB(DWS) database access permission. Users with this permission can generate the temporary database user credentials based on IAM users to connect to the database in the data warehouse cluster.

+

System-defined role

+

Dependent on the DWS Administrator policy, which must be assigned in the same project as the DWS Database Access policy.

+
+
+
+

Table 2 lists the common operations supported by each system-defined policy or role of GaussDB(DWS). Choose appropriate policies or roles as required.

+
  • If you use the EIP for the first time for a project in a region, the system prompts you to create the DWSAccessVPC agency to authorize GaussDB(DWS) to access VPC. After the authorization is successful, GaussDB(DWS) can switch to a healthy VM when the VM bound with the EIP is faulty.
  • By default, only cloud accounts or the users with Security Administrator permissions can create agencies. By default, the IAM users in those accounts cannot create agencies. When the users use the EIP, the system displays a message indicating insufficient permissions. Contact a user with the DWS FullAccess permissions to authorize the agency on the current page.
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 2 Common operations supported by each system-defined policy or role of GaussDB(DWS)

Operation

+

DWS FullAccess

+

DWS ReadOnlyAccess

+

DWS Administrator

+

DWS Database Access

+

Creating/Restoring clusters

+

√

+

x

+

√

+

x

+

Obtaining the cluster list

+

√

+

√

+

√

+

√

+

Obtaining the details of a cluster

+

√

+

√

+

√

+

√

+

Setting automated snapshot policy

+

√

+

x

+

√

+

x

+

Setting security parameters/parameter groups

+

√

+

x

+

√

+

x

+

Restarting clusters

+

√

+

x

+

√

+

x

+

Scaling out clusters

+

√

+

x

+

√

+

x

+

Resetting passwords

+

√

+

x

+

√

+

x

+

Applying parameter templates to clusters

+

√

+

x

+

√

+

x

+

Deleting clusters

+

√

+

x

+

√

+

x

+

Configuring maintenance windows

+

√

+

x

+

√

+

x

+

Binding EIPs

+

√

+

x

+

√

+

x

+

Unbinding EIPs

+

√

+

x

+

√

+

x

+

Creating DNS domain names

+

√

+

x

+

√

+

x

+

Releasing DNS domain names

+

√

+

x

+

√

+

x

+

Modifying DNS domain names

+

√

+

x

+

√

+

x

+

Creating MRS connections

+

√

+

x

+

√

+

x

+

Updating MRS connections

+

√

+

x

+

√

+

x

+

Deleting MRS connections

+

√

+

x

+

√

+

x

+

Adding/Deleting tags

+

√

+

x

+

√

+

x

+

Editing tags

+

√

+

x

+

√

+

x

+

Creating snapshots

+

√

+

x

+

√

+

x

+

Obtaining the snapshot list

+

√

+

√

+

√

+

√

+

Deleting snapshots

+

√

+

x

+

√

+

x

+

Copying snapshots

+

√

+

x

+

√

+

x

+

Creating parameter templates

+

√

+

x

+

√

+

x

+

Deleting parameter templates

+

√

+

x

+

√

+

x

+

Modifying parameter templates

+

√

+

x

+

√

+

x

+
+
+
+
+
+
+
Parent topic: Service Overview
+
+
+ diff --git a/docs/dws/umn/dws_01_0145.html b/docs/dws/umn/dws_01_0145.html new file mode 100644 index 00000000..1ebd38a0 --- /dev/null +++ b/docs/dws/umn/dws_01_0145.html @@ -0,0 +1,16 @@ + + +

Permissions

+

+
+
+ + +
+
Parent topic: Cluster Security Management
+
+
+ diff --git a/docs/dws/umn/dws_01_0150.html b/docs/dws/umn/dws_01_0150.html new file mode 100644 index 00000000..18f06d41 --- /dev/null +++ b/docs/dws/umn/dws_01_0150.html @@ -0,0 +1,101 @@ + + +

RBAC Syntax of RBAC Policies

+

Policy Structure

An RBAC policy consists of a Version, a Statement, and Depends.

+
Figure 1 RBAC policy structure
+
+

Policy Syntax

When selecting a policy for a user group, click below the policy to view the details of the policy. The DWS Administrator policy is used as an example to describe the syntax of RBAC policies.

+
Figure 2 Syntax of RBAC Policies
+
{
+        "Version": "1.0",
+        "Statement": [
+                {
+                        "Effect": "Allow",
+                        "Action": [
+                                "dws:dws:*"
+                        ]
+                }
+        ],
+        "Depends": [
+                {
+                        "catalog": "BASE",
+                        "display_name": "Server Administrator"
+                },
+                {
+                        "catalog": "BASE",
+                        "display_name": "Tenant Guest"
+                }
+        ]
+}
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + +

Parameter

+

Meaning

+

Value

+

Version

+

Policy version

+

The value is fixed to 1.0.

+

Statement

+

Action

+

Operations to be performed on GaussDB(DWS)

+

Format: Service name:Resource type:Operation.

+

dws:dws:*: Permissions for performing all operations on all resource types in GaussDB(DWS).

+

Effect

+

Whether the operation defined in an action is allowed

+
  • Allow
  • Deny
+

Depends

+

catalog

+

Name of the service to which dependencies of a policy belong

+

Service name

+

Example: BASE

+

display_name

+

Name of a dependent policy

+

Policy name

+

Example: Server Administrator

+
+
+

When using RBAC for authentication, pay attention to the Depends parameter and grant other dependent permissions at the same time.

+

For example, the DWS Administrator permission depends on the Server Administrator and Tenant Guest permissions. When granting the DWS Administrator permission to users, you also need to grant the two dependent permissions to the users.

+
+
+
+
+
+
Parent topic: Permissions
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_0151.html b/docs/dws/umn/dws_01_0151.html new file mode 100644 index 00000000..afe9172b --- /dev/null +++ b/docs/dws/umn/dws_01_0151.html @@ -0,0 +1,16 @@ + + +

Overview

+

A snapshot is a full or incremental backup of a GaussDB(DWS) cluster at a specific point in time. It records the current database data and cluster information, including the number of nodes, node specifications, and database administrator name. Snapshots can be created manually or automatically. For details, see Manual Snapshots and Automated Snapshots.

+

When a snapshot is used for restoration, GaussDB(DWS) creates a new cluster based on the cluster information recorded in the snapshot and restores data from the snapshot. For details about how to restore a cluster from a snapshot, see Restoring a Snapshot to a New Cluster.

+
  • Snapshot storage space
    • The cluster storage is provided by GaussDB(DWS) free of charge. Cluster storage = Storage space per node x Number of nodes
    +
  • The dependencies of the snapshot service are as follows:
    • Only the snapshots stored in OBS can be used to restore data to a new cluster.
    +
  • A new cluster created from the snapshot has the same configurations (including the number and flavor of nodes) as those of the original cluster.
  • If you create a new cluster based on a snapshot without modifying parameters, the parameters of the new cluster will be the same as those of the snapshot.
+
+
+
+
+
Parent topic: Snapshots
+
+
+ diff --git a/docs/dws/umn/dws_01_0152.html b/docs/dws/umn/dws_01_0152.html new file mode 100644 index 00000000..66e670c9 --- /dev/null +++ b/docs/dws/umn/dws_01_0152.html @@ -0,0 +1,558 @@ + + +

Modifying Database Parameters

+

After a cluster is created, you can modify the cluster's database parameters as required. On the GaussDB(DWS) management console, you can view or set common database parameters. For details, see Managing Parameter Templates. You can run SQL commands to view or set other database parameters. For details, see Setting Configuration Parameters in the Data Warehouse Service Database Development Guide.

+

Prerequisites

You can modify parameters only when no task is running in the cluster.

+
+

Procedure

  1. Log in to the GaussDB(DWS) management console.
  2. In the navigation pane on the left, choose Clusters.
  3. In the cluster list, find the target cluster and click the cluster name. The Basic Information page is displayed.
  4. Click the Parameters tab and modify the parameter values. Then click Save.

    +

    +

  5. In the Modification Preview dialog box, confirm the modifications and click Save.
+
+

Parameter Description

The following table describes part of the database parameters. You can search for and check more parameters by following the instructions in Procedure.

+
  • The default values of the following parameters are for reference only. For more information, see "Setting GUC Parameters".
  • After you modify parameters, restart the cluster to make the new settings take effect. Before the restart, the old parameter settings are still displayed.
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 Parameters

Parameter

+

Description

+

Default Value

+

session_timeout

+

Specifies the timeout interval of an idle session, in seconds. The value 0 indicates that the timeout limit is disabled. The value ranges from 0 to 86400.

+

600

+

datestyle

+

Sets the display format for date and time.

+

ISO,MDY

+

failed_login_attempts

+

Sets the number of consecutive incorrect password attempts after which the account is locked. The value 0 indicates that the number of incorrect password attempts is not limited. The value ranges from 0 to 1000.

+

10

+

timezone

+

Sets the time zone displayed in the time stamps.

+

UTC

+

log_timezone

+

Sets the time zone for timestamps in the server log.

+

UTC

+

enable_resource_record

+

Specifies whether to enable resource recording.

+

If the actual execution time of an SQL statement is greater than the value of resource_track_duration (the default value is 60s; customizable), the monitoring information will be archived.

+

This function will cause storage space expansion and slightly affect system performance. Disable it when it is not required.

+
NOTE:
  • Archiving: The monitoring information is stored in the history view and archived in the info table. The archiving time is 3 minutes. After the archiving, records in the history view are cleared.
  • History view GS_WLM_SESSION_HISTORY, which corresponds to info table GS_WLM_SESSION_INFO
  • History view GS_WLM_OPERATOR_HISTORY, which corresponds to info table GS_WLM_OPERATOR_INFO
+
+

off

+

query_dop

+

Sets the Symmetric Multi-Processing (SMP) degree.

+
  • Value 0 indicates that the SMP is adaptive.
  • Value 1 indicates that the SMP is disabled.
  • Value 2 indicates that the SMP degree is 2.
+

0

+

resource_track_cost

+

Sets the minimum execution cost for resource monitoring on statements. The value -1 indicates that resource monitoring is disabled (execution cost less than 10). If the value is greater than or equal to 0, and the cost of executing statements exceeds the value and is greater than or equal to 10, resource monitoring is performed.

+

You can run the SQL command Explain to query the estimated execution cost of an SQL statement.

+

100000

+

resource_track_duration

+

Sets the minimum time for archiving executed statements recorded during real-time monitoring, in seconds.

+
  • The value 0 indicates that all the statements are archived.
  • If the value is greater than 0, historical statements are archived when the execution time of the statements exceeds this value.
+

60

+

password_effect_time

+

Sets the validity period of the account password. When the password is about to expire or has expired, the system prompts the user to change the password.

+

The value ranges from 0 to 999, in days. If this parameter is set to 0, the function is disabled.

+

90

+

update_lockwait_timeout

+

Sets the maximum duration that a lock waits for concurrent updates on a row to complete. If the lock wait time exceeds the value, the system will report an error. If this parameter is set to 0, an error is reported immediately when a lock appears. The unit is milliseconds.

+

120000

+

enable_resource_track

+

Specifies whether to enable resource monitoring. After you enable this function, SQL statements can be monitored.

+

on

+

password_policy

+

Specifies whether to check the password complexity when you create a GaussDB(DWS) account using CREATE ROLE/CREATE USER, or modify the account using ALTER ROLE/ALTER USER.

+
  • 0 indicates that no password complexity policy is used.
  • 1 indicates that the default password complexity policy is used.
+

1

+

password_reuse_time

+

Specifies whether to check the password reuse interval when you modify the account password using ALTER USER/ALTER ROLE. The value ranges from 0 to 3650, in days.

+
  • 0 indicates that the password reuse interval is not restricted.
  • A positive number indicates that the new password cannot be chosen from passwords in history that are newer than the specified number of days.
+
NOTE:

The password_reuse_time and password_reuse_max parameters are checked during password change.

+
  • If the value of either password_reuse_time or password_reuse_max is positive, the password can be reused.
  • If the value of password_reuse_time is 0, password reuse is restricted based on the number of password changes, but not on the time elapsed.
  • If the values of both parameters are 0, password reuse is not restricted.
+
+

60

+

password_reuse_max

+

Specifies whether to check the number of password changes when you modify the account password using ALTER USER/ALTER ROLE.

+
  • 0 indicates that the password is not restricted by the number of password changes.
  • A positive number indicates that the new password cannot be chosen from the specified number of the most recent passwords.
+
NOTE:

The password_reuse_time and password_reuse_max parameters are checked during password change.

+
  • If the value of either password_reuse_time or password_reuse_max is positive, the password can be reused.
  • If the value of password_reuse_max is 0, the password is not restricted based on the time elapsed, but not on the number of password changes.
  • If the values of both parameters are 0, password reuse is not restricted.
+
+

0

+

password_lock_time

+

Specifies the duration before a locked account is automatically unlocked.

+
  • 0 indicates that the account is not automatically locked if the password verification fails.
  • A positive number indicates the duration after which a locked account is automatically unlocked.
+

1

+

password_encryption_type

+

Specifies the encryption type of user passwords.

+
  • 0 indicates that passwords are encrypted with MD5.
  • 1 indicates that passwords are encrypted with SHA-256, which is compatible with the MD5 user authentication method of the PostgreSQL client.
  • 2 indicates that passwords are encrypted with SHA-256. MD5 is not recommended because it is not a secure encryption algorithm.
+

2

+

password_notify_time

+

Specifies how many days in advance a user is notified before a password expires.

+
  • 0 indicates that the notification is disabled.
  • A value ranging from 1 to 999 indicates the number of days prior to password expiration that a user will receive a notification.
+

7

+

enable_stateless_pooler_reuse

+

Specifies whether to enable the pooler reuse mode. The setting takes effect after the cluster is restarted.

+
  • on indicates that the pooler reuse mode is enabled.
  • off indicates that the pooler reuse mode is disabled.
+
NOTE:

Set this parameter to the same value for CNs and DNs. If this parameter is set to off for CNs and on for DNs, the cluster communication fails. Restart the cluster for the setting to take effect.

+
+

off

+

work_mem

+

Specifies the amount of memory to be used by internal sort operations and hash tables before they write data into temporary disk files, in KB.

+

Sort operations are required for ORDER BY, DISTINCT, and merge joins.

+

Hash tables are used in hash joins, hash-based aggregation, and hash-based processing of IN subqueries.

+

In a complex query, several sort or hash operations may run in parallel; each operation will be allowed to use as much memory as this parameter specifies. If the memory is insufficient, data will be written into temporary files. In addition, several running sessions could be performing such operations concurrently. Therefore, the total memory used may be many times the value of work_mem.

+

64MB

+

maintenance_work_mem

+

Specifies the maximum amount of memory to be used by maintenance operations, such as VACUUM, CREATE INDEX, and ALTER TABLE ADD FOREIGN KEY, in KB.

+
NOTE:

This parameter may affect the execution efficiency of VACUUM, VACUUM FULL, CLUSTER, and CREATE INDEX.

+
+

128MB

+

enable_orc_cache

+

Specifies whether to reserve 1/4 of cstore_buffers for storing ORC metadata when cstore_buffers is initialized.

+
  • on indicates that the ORC metadata is cached, which improves the query performance of HDFS tables but occupies column-store caches. As a result, the column-store performance is compromised.
  • off indicates that the ORC metadata is not cached.
+

on

+

sql_use_spacelimit

+

Specifies the space size for files to be flushed to disks when a single SQL statement is executed on a single DN, in KB. The managed space includes the space occupied by ordinary tables, temporary tables, and intermediate result sets to be flushed to disks. -1 indicates no limit.

+

-1

+

enable_bitmapscan

+

Specifies whether to enable the optimizer's use of bitmap-scan plan types.

+
  • on
  • off
+

on

+

enable_hashagg

+

Specifies whether to enable the optimizer's use of hash aggregation plan types.

+
  • on
  • off
+

on

+

enable_hashjoin

+

Specifies whether enable the optimizer's use of hash join plan types.

+
  • on
  • off
+

on

+

enable_indexscan

+

Specifies whether to enable the optimizer's use of index-scan plan types.

+
  • on
  • off
+

on

+

enable_indexonlyscan

+

Specifies whether to enable the optimizer's use of index-only-scan plan types.

+
  • on
  • off
+

on

+

enable_mergejoin

+

Specifies whether the optimizer's use of merge-join plan types.

+
  • on
  • off
+

off

+

enable_nestloop

+

Specifies whether the optimizer's use of nested-loop-join plan types. It is impossible to suppress nested-loop joins entirely, but disabling this parameter encourages the optimizer to choose other methods if available.

+
  • on
  • off
+

off

+

enable_seqscan

+

Specifies whether enable the optimizer's use of sequential-scan plan types. It is impossible to suppress sequential scans entirely, but disabling this parameter encourages the optimizer to choose other methods if available.

+
  • on
  • off
+

on

+

enable_tidscan

+

Specifies whether enable the optimizer's use of TID scan plan types.

+
  • on
  • off
+

on

+

enable_kill_query

+

In CASCADE mode, when a user is deleted, all the objects belonging to the user are deleted. This parameter specifies whether the queries of the objects belonging to the user can be unlocked when the user is deleted.

+
  • on indicates that the unlocking is allowed.
  • off indicates that the unlocking is not allowed.
+

off

+

enable_vector_engine

+

Specifies whether to enable the optimizer's use of vectorized execution engines.

+
  • on
  • off
+

on

+

enable_broadcast

+

Specifies whether to enable the optimizer's use of broadcast distribution when it evaluates the cost of stream.

+
  • on
  • off
+

on

+

skew_option

+

Specifies whether to enable an optimization policy.

+
  • off indicates that the policy is disabled.
  • normal indicates that a radical policy is used. All possible skews are optimized.
  • lazy indicates that a conservative policy is used. Uncertain skews are ignored.
+

normal

+

default_statistics_target

+

Specifies the default statistics target for table columns without a column-specific target set via ALTER TABLE SET STATISTICS. If this parameter is set to a positive number, it indicates the number of samples of statistics information. If this parameter is set to a negative number, percentage is used to set the statistic target. The negative number converts to its corresponding percentage, for example, -5 means 5%.

+

100

+

enable_codegen

+

Specifies whether to enable code optimization. Currently, LLVM optimization is used.

+
  • on
  • off
+

on

+

autoanalyze

+

Specifies whether to automatically collect statistics on tables that have no statistics when a plan is generated.

+
  • on indicates that the table statistics are automatically collected.
  • off indicates that the table statistics are not automatically collected.
+
NOTE:
  • This parameter is now not available to foreign tables. If you need the statistics, manually perform the analyze operation.
  • This parameter is not available to temporary tables with the ON COMMIT [DELETE ROWS|DROP] option. If you need the statistics, manually perform the analyze operation.
  • If an exception occurs in the database during the execution of autoanalyze on a table, after the database is recovered, the system may still prompt you to collect the statistics of the table when you run the statement again. In this case, manually perform ANALYZE on the table to synchronize statistics.
+
+

off

+

enable_sonic_hashagg

+

Specifies whether to enable the hash aggregation operator designed for column-oriented hash tables when certain constraints are met.

+
  • on
  • off
+

on

+

log_hostname

+

By default, connection log messages only show the IP address of the connecting host. The host name can be recorded when this parameter is set to on. It may take some time to parse the host name. Therefore, the database performance may be affected.

+
  • on
  • off
+

off

+

max_active_statements

+

Specifies the maximum number of concurrent jobs. This parameter applies to all the jobs on one CN. The values -1 and 0 indicate that the number of concurrent jobs is not limited.

+

60

+

enable_resource_track

+

Specifies whether to enable resource monitoring.

+

on

+

resource_track_level

+

Sets the resource monitoring level of the current session. This parameter is valid only when enable_resource_track is set to on.

+
  • none indicates that resources are not monitored.
  • query enables the query-level resource monitoring. If this function is enabled, the plan information (similar to the output information of explain) of SQL statements will be recorded in top SQL statements.
  • perf enables the perf-level resource monitoring. If this function is enabled, the plan information (similar to the output information of EXPLAIN ANALYZE) that contains the actual execution time and the number of execution rows will be recorded in top SQL statements.
  • operator enables the operator-level resource monitoring. If this function is enabled, not only the information including the actual execution time and number of execution rows is recorded in the top SQL statements, but also the operator-level execution information is updated to the top SQL statements.
+

query

+

enable_dynamic_workload

+

Specifies whether to enable dynamic load management.

+
  • on
  • off
+

on

+

topsql_retention_time

+

Specifies the data storage retention period of the gs_wlm_session_info and gs_wlm_operator_info catalogs in historical top SQL statements. The unit is day.

+
  • If it is set to 0, the data is stored permanently.
  • If the value is greater than 0, the data is stored for the specified number of days.
+

0

+

track_counts

+

Specifies whether to enable collection of statistics on database activities.

+
  • on
  • off
+

off

+

autovacuum

+

Specifies whether to enable the autovacuum process. track_counts must be set to on for autovacuum to work.

+
  • on
  • off
+

off

+

autovacuum_mode

+

Specifies the autovacuum mode. autovacuum must be set to on.

+
  • analyze indicates that only autoanalyze is performed.
  • vacuum indicates that only autovacuum is performed.
  • mix indicates that both are performed.
  • none indicates that neither is performed.
+

mix

+

autoanalyze_timeout

+

Specifies the autoanalyze timeout period, in seconds. If the duration of autoanalyze on a table exceeds the value of autoanalyze_timeout, the autoanalyze operation is automatically canceled.

+

5min

+

autovacuum_io_limits

+

Specifies the maximum number of I/Os triggered by the autovacuum process per second. –1 indicates that the default cgroup is used.

+

-1

+

autovacuum_max_workers

+

Specifies the maximum number of concurrent autovacuum threads. 0 indicates that autovacuum is disabled.

+

3

+

autovacuum_naptime

+

Specifies the interval between two autovacuum operations, in seconds.

+

10min

+

autovacuum_vacuum_threshold

+

Specifies the threshold for triggering VACUUM. When the number of deleted or updated records in a table exceeds the specified threshold, the VACUUM operation is executed on this table.

+

50

+

autovacuum_analyze_threshold

+

Specifies the threshold for triggering ANALYZE. When the number of deleted, inserted, or updated records in a table exceeds the specified threshold, the ANALYZE operation is executed on this table.

+

50

+

autovacuum_analyze_scale_factor

+

Specifies a fraction of the table size added to the autovacuum_analyze_threshold parameter when deciding whether to analyze a table.

+

0.1

+

statement_timeout

+

Specifies the statement timeout interval, in milliseconds. When the execution time of a statement exceeds the value (starting from the time when the server receives the command), the statement reports an error and exits.

+

0

+

deadlock_timeout

+

Specifies the deadlock timeout interval, in milliseconds. When the applied lock exceeds the value, the system will check whether a deadlock occurs.

+

1s

+

lockwait_timeout

+

Specifies the maximum wait time for a single lock, in milliseconds. If the lock wait time exceeds the value, the system will report an error.

+

20min

+

max_query_retry_times

+

Specifies the maximum number of automatic retry times when an SQL statement error occurs. Currently, a statement can start retrying if the following errors occur: Connection reset by peer, Lock wait timeout, and Connection timed out. If this parameter is set to 0, the retry function is disabled.

+

6

+

max_pool_size

+

Specifies the maximum number of connections between the connection pool of a CN and another CN or DN.

+

800

+

enable_gtm_free

+

Specifies whether the GTM-FREE mode is enabled. In large concurrency scenarios, the snapshots delivered by the GTM increase in number and size. The network between the GTM and the CN becomes the performance bottleneck. The GTM-FREE mode is used to eliminate the bottleneck. In this mode, the CN communicates with DNs instead of the GTM. The CN sends queries to each DN, which locally generates snapshots and XIDs, ensuring external write consistency but not external read consistency.

+

off

+

enable_fast_query_shipping

+

Specifies whether to enable the optimizer's use of a distributed framework.

+

on

+

enable_crc_check

+

Specifies whether to enable data checks. Check information is generated when table data is written and is checked when the data is read. You are not advised to modify the settings.

+

on

+

explain_perf_mode

+

Specifies the display format of explain.

+
  • normal indicates that the default printing format is used.
  • pretty indicates that the optimized display format of GaussDB(DWS) is used. The new format contains a plan node ID, directly and effectively analyzing performance.
  • summary indicates that analysis of the pretty printed information is added.
  • run indicates that the system exports the printed information specified by summary as a CSV file for further analysis.
+

pretty

+

udf_memory_limit

+

Specifies the maximum physical memory that can be used when UDFs are executed on each CN and DN, in KB.

+

200MB

+

default_transaction_read_only

+

Specifies whether each newly created transaction is read only.

+
  • on indicates the transaction is read only.
  • off indicates the transaction is not read only.
+

off

+
+
+
+
+
+
+
Parent topic: Clusters
+
+
+ diff --git a/docs/dws/umn/dws_01_0154.html b/docs/dws/umn/dws_01_0154.html new file mode 100644 index 00000000..0ff49131 --- /dev/null +++ b/docs/dws/umn/dws_01_0154.html @@ -0,0 +1,15 @@ + + +

Preparations

+

Before using GaussDB(DWS), make the following preparations:

+ +

Registering a Public Cloud Account and Completing Real-Name Authentication

If you do not have a public cloud account, register one. If you already have an account with real-name authentication, skip this step and use the account.

+
  1. Open the official public cloud website and click Register in the upper right corner. The registration page is displayed.
  2. Fill in user information as instructed to complete the registration.
  3. Click the username in the upper right corner to enter the Account Info page. Then click Real-Name Authentication in the left navigation pane.
  4. Perform real-name authentication as prompted.

    You must perform real-name authentication before enabling cloud services.

    +
    +
+
+

Determining the Cluster Ports

+
+
+
+ diff --git a/docs/dws/umn/dws_01_0156.html b/docs/dws/umn/dws_01_0156.html new file mode 100644 index 00000000..d8f25136 --- /dev/null +++ b/docs/dws/umn/dws_01_0156.html @@ -0,0 +1,86 @@ + + +

Updating the MRS Data Source Configuration

+

Scenario

For MRS, if the following parameter configurations of the HDFS cluster change, data may fail to be imported to the data warehouse cluster from the HDFS cluster. Before importing data using the HDFS cluster, you must update the MRS data source configuration.

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Parameter

+

Description

+

dfs.client.read.shortcircuit

+

Specifies whether to enable the local read function.

+

dfs.client.read.shortcircuit.skip.checksum

+

Specifies whether to skip data verification during the local read.

+

dfs.client.block.write.replace-datanode-on-failure.enable

+

Specifies whether to replace the location storing copies with the new node when data blocks fail to be written to HDFS.

+

dfs.encrypt.data.transfer

+

Specifies whether to enable data encryption.

+
NOTE:

This parameter is available only for clusters with Kerberos authentication enabled.

+
+

dfs.encrypt.data.transfer.algorithm

+

Specifies the encryption and decryption algorithm for key transmission.

+

dfs.encrypt.data.transfer.cipher.suites

+

Specifies the encryption and decryption algorithm for the transmission of actually stored data.

+

dfs.replication

+

Specifies the default number of data copies.

+

dfs.blocksiz

+

Specifies the default size of a data block.

+

hadoop.security.authentication

+

Specifies the security authentication mode.

+

hadoop.rpc.protection

+

Specifies the RPC communication protection mode.

+

dfs.domain.socket.path

+

Specifies the locally used Domain socket path.

+
+
+
+

Prerequisites

You have created an MRS data source connection for the data warehouse cluster.

+
+

Impact on the System

When you are updating an MRS data source connection, the data warehouse cluster will automatically restart and cannot provide services.

+
+

Procedure

  1. On the GaussDB(DWS) management console, click Clusters.
  2. In the cluster list, click the name of a cluster. On the page that is displayed, click MRS Data Sources.
  3. In the MRS data source list, select the MRS data source that you want to update. In the Operation column, click Update Configurations.

    MRS Cluster Status and Configuration Status of the current connection will be updated. During configuration update, you cannot create a connection. The system checks whether the security group rule is correct. If the rule is incorrect, the system rectifies the fault.

    +

+
+
+
+
+
Parent topic: MRS Data Sources
+
+
+ diff --git a/docs/dws/umn/dws_01_0157.html b/docs/dws/umn/dws_01_0157.html new file mode 100644 index 00000000..f620ac2d --- /dev/null +++ b/docs/dws/umn/dws_01_0157.html @@ -0,0 +1,14 @@ + + +

Accessing the GaussDB(DWS) Management Console

+

Scenario

This section describes how to log in to the GaussDB(DWS) management console and use GaussDB(DWS).

+
+

Procedure

  1. Log in to the public cloud management console.
  2. From the menu on top of the management console, choose Service List.
  3. Choose EI Enterprise Intelligence > GaussDB(DWS) to enter the GaussDB(DWS) management console.
+
+
+
+
+
Parent topic: Cluster Configuration
+
+
+ diff --git a/docs/dws/umn/dws_01_0160.html b/docs/dws/umn/dws_01_0160.html new file mode 100644 index 00000000..5ef9db1f --- /dev/null +++ b/docs/dws/umn/dws_01_0160.html @@ -0,0 +1,14 @@ + + +

Cluster Configuration

+

+
+
+ +
+ diff --git a/docs/dws/umn/dws_01_0161.html b/docs/dws/umn/dws_01_0161.html new file mode 100644 index 00000000..1f7ef37a --- /dev/null +++ b/docs/dws/umn/dws_01_0161.html @@ -0,0 +1,21 @@ + + + +

Cluster HA

+ +

+
+ +
+ +
+ diff --git a/docs/dws/umn/dws_01_0162.html b/docs/dws/umn/dws_01_0162.html new file mode 100644 index 00000000..35e22918 --- /dev/null +++ b/docs/dws/umn/dws_01_0162.html @@ -0,0 +1,15 @@ + + +

Monitoring and Alarms

+
+
+ +
+ diff --git a/docs/dws/umn/dws_01_01752.html b/docs/dws/umn/dws_01_01752.html new file mode 100644 index 00000000..e3ad0cd8 --- /dev/null +++ b/docs/dws/umn/dws_01_01752.html @@ -0,0 +1,104 @@ + + +

DDL Audit

+

You can audit DDL to check DDL metadata, identify inappropriate table definitions, and locate performance problems.

+
  • This feature is supported only in cluster version 8.1.2 or later.
  • The selected audit items are displayed on the DDL Audit page by default. You can configure the audit items on the Monitoring Collection page (see Monitoring Collection). Table 1 shows the audit item details.
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 Audit items

Item

+

Description

+

Number of Distribution Keys (disKeyCount)

+

If there is no data skew, use no more than four distribution keys.

+

Generally, if you use many distribution keys, data can be evenly distributed in a cluster and thus avoid data skew. However, if too many distribution keys are used, the storage performance and joint query performance may deteriorate. You are advised to configure no more than four distribution keys.

+
  • Storage performance issue:

    When data is added, the hash function calculates the result of each distribution column, aggregates the results, and then determines where to distribute data. A large number of distribution keys require time-consuming, complex calculation.

    +
  • Union query performance issue:

    During multi-table join query, if all the columns of the distribution key are involved in the join condition, data does not need to be redistributed in the execution plan. If a large number of distribution keys are used, some of them may not be the columns involved in the join condition, and data redistribution may occur, which consumes many resources and takes long.

    +
+

Number of Index Columns/PCKs (indexKeyOrPckCount)

+

It is recommended that the number of partial cluster keys (PCKs)/columns of an index be less than or equal to 4.

+
  • A large number of index columns require many resources to maintain index data, and are likely to contain duplicate indexes.
  • While column-store data is imported, PCK columns are compared and calculated to determine CU division. A large number of PCKs will consume many resources and much time, affecting performance. To efficiently filter CUs in a query, the prefixes of the columns involved in the query conditions must be PCK columns. (For example, if the PCK columns are a, b, and c, the query criteria must be a>? and b>? and c>?.) Otherwise, all the CUs must be traversed, and data clustering does not contribute to query acceleration.
+

+

Invalid PCKs (invalidPck)

+

Do not create invalid PCK columns.

+

In 8.1.1 and later versions, the cluster can filter and compare data of the char, int8, int2, int4, text, bpchar, varchar, date, time, timestamp and timestamptz types. If a column of an unsupported data type is used as a PCK, the column is an invalid PCK column. It does not take effect during CU filtering and will consume resources for its maintenance.

+

+

numeric Data Usage (validityOfNumeric)

+

+

To facilitate calculation, integers are recommended if you need to use numeric types. If a value does not need to be highly precise, use a fixed-length floating data type for it.

+

If you have to use variable-length numeric types, you are advised to set their maximum length to 38 bits. The system will try to convert the calculation of such values to the calculation between int and bigint values to improve efficiency.

+

In 8.1.1 and later versions, if no precision is specified, up to 131,072 digits can be placed before the decimal point and up to 16,383 digits can be placed after the decimal point. That is, the maximum scale and precision are used. In this case, the calculation performance will deteriorate.

+

Index Column Width (widthOfIndexKey)

+

Generally, wide index columns are character string columns, which do not involve compare operations and will lead to large indexes that consume unnecessary space. Specify a value smaller than 64 bytes.

+

Replication Table Size (sizeOfCopyTable)

+

Tables whose storage space of a single DN is greater than the threshold (100 MB) are identified. Use common associated columns as distribution keys (generally with one primary key).

+

The cluster supports replication tables. A replication table maintains a full copy of data on each node and is mainly used to store data of enumerated types. A large replication table occupies much space and may slow down union queries, because the full table data on each node is traversed, which is time consuming. A union query on distribution tables may take less time, because the data traversed on each node is less than that of a replication table.

+

Skew Detection for Single-Distribution-Key Tables (recognitionOfDataSkew)

+

Data skew of single-distribution-key tables is detected by statistics. This audit applies only to tables with one distribution key.

+

Distribution Key Usage (validityOfDiskey)

+

+

In a cluster, you are not advised to use a column of the Boolean or date type as a distribution column, because it may cause data skew.

+

Number of Cached Sequence Values (cacheSizeOfSequence)

+

Specify a number greater than 100.

+

If a table column uses sequences, its next_value is obtained from the cached value in the local node. If cached sequence values are used up, a request will be sent asking GTM to obtain the value again. If a large amount of data is added but only a few values are cached, GTM will receive many requests, and may get overloaded and even break down. To avoid this problem, you are advised to set the cache value to a value greater than 100 when creating a sequence.

+

Optimizable Indexes (optimizableIndexKey)

+

Scenarios where indexes can be optimized:

+
  • The index column of an index is the first N columns of another index.
  • The index columns of two indexes are the same, but the orders are different.
+
+
+

Viewing and Exporting DDL Audit Results

  1. Log in to the GaussDB(DWS) management console.
  2. On the Clusters page, locate the target cluster.
  3. In the Operation column of the target cluster, click Monitoring Panel.
  4. In the navigation tree on the left, choose Utilities > DDL Audit. The result of each audit item is displayed.

    +

  5. If the review result of an item is Failed, click View to go to the details page.

    +

  6. Click Export in the upper left corner to export the audit result.

    +

+
+

Manually Auditing DDL Items

  1. Log in to the GaussDB(DWS) management console.
  2. On the Clusters page, locate the target cluster.
  3. In the Operation column of the target cluster, choose Monitoring Panel. The database monitoring page is displayed.
  4. In the navigation tree on the left, choose Utilities > DDL Audit. On the page that is displayed, select the items to be audited and click One-Click Audit.

    +

+
+

+
+
+
+
Parent topic: Utilities
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_0600.html b/docs/dws/umn/dws_01_0600.html new file mode 100644 index 00000000..b72fcca9 --- /dev/null +++ b/docs/dws/umn/dws_01_0600.html @@ -0,0 +1,49 @@ + + +

Clusters

+
+
+ +
+ diff --git a/docs/dws/umn/dws_01_0700.html b/docs/dws/umn/dws_01_0700.html new file mode 100644 index 00000000..5e036a16 --- /dev/null +++ b/docs/dws/umn/dws_01_0700.html @@ -0,0 +1,19 @@ + + + +

Cluster Security Management

+ +

+
+ +
+ +
+ diff --git a/docs/dws/umn/dws_01_0701.html b/docs/dws/umn/dws_01_0701.html new file mode 100644 index 00000000..714c723f --- /dev/null +++ b/docs/dws/umn/dws_01_0701.html @@ -0,0 +1,35 @@ + + +

Protection for Mission-Critical Operations

+

Scenario

GaussDB(DWS) protects mission-critical operations. If you want to perform a mission-critical operation on the management console, you must enter a credential for identity verification. You can perform the operation only after your identity is verified. For account security, you are advised to enable operation protection. The setting will take effect for both the account and its users.

+

Currently, the following operations are supported: scaling out a cluster, deleting a cluster, restarting a cluster, adding a CN, and deleting a CN.

+
+

Enabling Operation Protection

Operation protection is disabled by default. To enable it, perform the following steps:

+
  1. Log in to the GaussDB(DWS) console.
  2. Move the cursor to the username in the upper right corner of the page and click Security Settings from the drop-down list.

    Figure 1 Security Settings
    +

  3. On the Security Settings page, click the Critical Operations tab. Click Enable in the Operation Protection area.

    Figure 2 Critical Operations
    +

  4. On the Operation Protection page, select Enable to enable operation protection.

    • When IAM users created using your account perform a critical operation, they will be prompted to choose a verification method from email, SMS, and virtual MFA device.
      • If a user is only associated with a mobile number, only SMS verification will be available.
      • If a user is only associated with an email address, only email verification will be available.
      • If a user is not associated with an email address, mobile number, or virtual MFA device, the user will need to associate an email address, mobile number, or virtual MFA device with their account before the user can perform any critical operations.
      +
    • Change your phone number or email address for verification in My Account on the management console.
    +
    +

  5. After operation protection is enabled, when you perform a mission-critical operation, the system will protect the operation.

    For example, when you delete a cluster, a verification dialog box for mission-critical operation protection is displayed. You need to select a mode to perform verification. This helps avoid risks and losses caused by misoperations.
    Figure 3 Identity Verification
    +
    +

+
+

Disabling Operation Protection

To disable operation protection, perform the following steps:

+
  1. Log in to the GaussDB(DWS) console.
  2. Move the cursor to the username in the upper right corner of the page and click Security Settings from the drop-down list.

    Figure 4 Security Settings
    +

  3. On the Security Settings page, click the Critical Operations tab. Click Change in the Operation Protection area.

    Figure 5 Modifying operation protection settings
    +

  4. On the Operation Protection page, select Disable and click OK.
+
+
+
+
+
Parent topic: Cluster Security Management
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_0723.html b/docs/dws/umn/dws_01_0723.html new file mode 100644 index 00000000..d8f10706 --- /dev/null +++ b/docs/dws/umn/dws_01_0723.html @@ -0,0 +1,29 @@ + + +

Managing Cluster Workloads

+
+
+ + +
+
Parent topic: Clusters
+
+
+ diff --git a/docs/dws/umn/dws_01_07231.html b/docs/dws/umn/dws_01_07231.html new file mode 100644 index 00000000..a547af2b --- /dev/null +++ b/docs/dws/umn/dws_01_07231.html @@ -0,0 +1,43 @@ + + +

Workload Management Overview

+

Overview

When multiple database users query jobs at the same time, some complex queries may occupy cluster resources for a long time, affecting the performance of other queries. For example, a group of database users continuously submit complex and time-consuming queries, while another group of users frequently submit short queries. In this case, short queries may have to wait in the queue for the time-consuming queries to complete.

+
+

To improve efficiency, you can use the GaussDB(DWS) workload management function to handle such problems. GaussDB(DWS) workload management uses workload queues as resource bearers. You can create different workload queues for different service types and configure different resource ratios for these queues. Then, add database users to the corresponding queues to restrict their resource usages. For example, classify database users who frequently submit complex query jobs into one type, create a workload queue for these users, allocate more resources to the queue, and then add these users to the queue. In this case, the complex jobs submitted by these users can use only the resources of the created queue. Also, create a queue that occupies fewer resources and allocate it to users who submit short queries. In this way, the two types of jobs can be executed at the same time without affecting each other.

+
  • If a resource pool has been created on the backend in the database of the earlier version, delete it and create a new one on the frontend. For details, contact technical support.
+
+

Page Overview

On the Workload Management page, you can modify the global configurations of workload management, add, create, and modify workload queues, add database users to queues, and remove database users from queues.

+

+

+
+

Short Query Configuration

In the Short Query Configuration area, you can enable or disable the short query acceleration function. To change the number of concurrent short queries (-1 by default. 0 or -1 indicates that the concurrent short queries are not controlled), you can enable short query acceleration.

+

+
+

Resource Configuration

In the Resource Configuration area, you can view the resource configuration of the current workload queue, including the CPU resource (%), memory resource (%), storage resource (MB), and query concurrency.

+
+

+

Exception Rule

In the Exception Rule area, you can view the exception rule settings of the current workload queue. Exception rules allow you to control exceptions of jobs executed by associated users in the queue.

+

+
+

Associated User

In the Associated User list, you can view the associated users of the current workload queue, and the memory and disk usage of each user at the current time, as shown in the following figure.

+

+
+

Entering Workload Management Page

  1. Log in to the GaussDB(DWS) management console.
  2. On the displayed Clusters page, click the name of the target cluster.
  3. Switch to the Workload Management tab page.
+
+

Enabling/Disabling Workload Management

The Workload Management Configuration area includes the Workload Switch and Maximum Concurrency parameters. Maximum Concurrency refers to the maximum concurrent queries on a single CN. If you disable Workload Switch, all workload management functions will be unavailable.

+

+
+
+
+
+
Parent topic: Managing Cluster Workloads
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_07233.html b/docs/dws/umn/dws_01_07233.html new file mode 100644 index 00000000..ee8c934d --- /dev/null +++ b/docs/dws/umn/dws_01_07233.html @@ -0,0 +1,69 @@ + + +

Adding Workload Queues

+
  1. Log in to the GaussDB(DWS) management console.
  2. On the displayed Clusters page, click the name of the target cluster.
  3. Switch to the Workload Management tab page.
  4. Click the plus sign (+) next to Workload Queue.

    +

    You can create a maximum of 63 workload queues.

    +
    +

  5. Enter the name and configure related resources for a new workload queue by referring to Table 1.

    +

    + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Configuring workload queue parameters

    Parameter

    +

    Description

    +

    Value

    +

    Name

    +

    Name of a workload queue.

    +

    queue_test

    +

    CPU Usage (%)

    +

    Percentage of the CPU time slice that can be used by database users in a queue for job execution.

    +

    20

    +

    Memory Resource (%)

    +

    Percentage of the memory usage by a queue.

    +
    CAUTION:

    You can manage memory and query concurrency separately or jointly. Under joint management, jobs can be delivered only when both the memory and concurrency conditions are met.

    +
    +

    20

    +

    Storage Resource (MB)

    +

    Size of the available space for permanent tables.

    +
    CAUTION:

    This parameter indicates the total tablespace of all DNs in a queue. Available space of a single DN = Configured value/Number of DNs.

    +
    +

    1024

    +

    Query Concurrency

    +

    Maximum number of concurrent queries in a queue.

    +
    CAUTION:

    You can manage memory and query concurrency separately or jointly. Under joint management, jobs can be delivered only when both the memory and concurrency conditions are met.

    +
    +

    10

    +
    +
    +

    +

  6. Confirm the information and click OK.

    +

+
+
+
+
Parent topic: Managing Cluster Workloads
+
+
+ diff --git a/docs/dws/umn/dws_01_07234.html b/docs/dws/umn/dws_01_07234.html new file mode 100644 index 00000000..942c48c9 --- /dev/null +++ b/docs/dws/umn/dws_01_07234.html @@ -0,0 +1,158 @@ + + +

Modifying Workload Queues

+

You can modify the parameters of a workload queue.

+
  1. Log in to the GaussDB(DWS) management console.
  2. On the displayed Clusters page, click the name of the target cluster.
  3. Switch to the Workload Management tab page.
  4. In the Workload Queue area on the left, click the name of the queue to be modified. The following configuration areas are displayed, including Short Query Configuration, Resource Configuration, Exception Rule, and Associated User.

    +

  5. Modify the short query configuration. Set the parameters as required and click Save on the right.

    +

    + + + + + + + + + + + + + +

    Parameter

    +

    Description

    +

    Value

    +

    Short Query Acceleration

    +

    Whether to enable short query acceleration. This function is enabled by default.

    +

    Enable

    +

    Concurrent Short Queries

    +

    A short query is a job whose estimated memory used for execution is less than 32 MB. The default value -1 indicates that the job is not controlled.

    +

    10

    +
    +
    +

  6. Modify the resource configuration.

    1. Click Edit on the right and modify the parameters according to Table 1. +
      + + + + + + + + + + + + + + + + + + + + + + + + + +
      Table 1 Workload queue parameters

      Parameter

      +

      Description

      +

      Value

      +

      Name

      +

      Name of a workload queue.

      +

      queue_test

      +

      CPU Resource (%)

      +

      Percentage of the CPU time slice that can be used by database users in a queue for job execution.

      +

      20

      +

      Memory Resource (%)

      +

      Percentage of the memory usage by a queue.

      +
      CAUTION:

      You can manage memory and query concurrency separately or jointly. Under joint management, jobs can be delivered only when both the memory and concurrency conditions are met.

      +
      +

      20

      +

      Storage Resource (MB)

      +

      Size of the available space for permanent tables.

      +
      CAUTION:

      This parameter indicates the total tablespace of all DNs in a queue. Available space of a single DN = Configured value/Number of DNs.

      +
      +

      1024

      +

      Query Concurrency

      +

      Maximum number of concurrent queries in a queue.

      +
      CAUTION:

      You can manage memory and query concurrency separately or jointly. Under joint management, jobs can be delivered only when both the memory and concurrency conditions are met.

      +
      +

      10

      +
      +
      +
    2. Click OK.
    +

  7. Modify the exception rules.

    1. Modify the parameters according to Table 2.

      Exception rules allow you to control exceptions of jobs executed by users in a queue. Currently, you can configure the parameters listed in Table 2.

      +
      • If you select Terminate, you need to set the corresponding time or percentage.
      • If you select No restriction, the corresponding execution rule does not take effect.
      +
      + +
      + + + + + + + + + + + + + + + + + + + + + + + + + +
      Table 2 Exception rule parameters

      Parameter

      +

      Description

      +

      Value

      +

      Blocking Time

      +

      Job blocking duration, in seconds. The duration includes the total time spent in global and local concurrent queuing.

      +

      For example, if the blocking time is set to 300s, a job executed by a user in the queue will be terminated after being blocked for 300 seconds.

      +

      1200

      +

      Execution Time

      +

      Execution duration of a job, in seconds. The time indicates the duration from the start point of execution to the current time point.

      +

      For example, if Time required for execution is set to 100s, a job executed by a user in the queue will be terminated after being executed for more than 100 seconds.

      +

      2400

      +

      Total CPU time on all DNs

      +

      Total CPU time spent in executing a job on all DNs, in seconds.

      +

      100

      +

      Interval for Checking CPU Skew Rate

      +

      Interval for checking the CPU skew, in seconds. This parameter must be set together with Total CPU Time on All DNs.

      +

      2400

      +

      Total CPU Time Skew Rate on All DNs

      +

      CPU time skew rate of a job executed on DNs. The value depends on the setting of Interval for Checking CPU Skew Rate.

      +

      90

      +
      +
      +
    2. Click Save.
    +

  8. Associate users.

    • The resources used by a user to run jobs can be controlled only after the user is added to a queue.
    • A database user can be added to only one queue. Users removed from a queue can be added to another queue.
    • The administrator cannot be associated.
    +
    +
    1. Click Add on the right.
    2. Select the users to be added from the current user list. You can select multiple users at a time.

      +
    3. Click OK.
    4. To delete a user, click Delete in the Operation column of the user.
    +

+

+
+
+
+
Parent topic: Managing Cluster Workloads
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_07238.html b/docs/dws/umn/dws_01_07238.html new file mode 100644 index 00000000..42d79d61 --- /dev/null +++ b/docs/dws/umn/dws_01_07238.html @@ -0,0 +1,21 @@ + + +

Workload Queue Query

+
  1. Log in to the GaussDB(DWS) management console.
  2. On the displayed Clusters page, click the name of the target cluster.
  3. Switch to the Workload Management tab page.
  4. In the Workload Queue area on the left, click the name of the queue to be viewed.

    In the Query Overview area, you can view the number of long and short queries that are running in the current queue at the current time. The chart information is refreshed every 15 seconds.

    +

    +

+

+
+
+
+
Parent topic: Managing Cluster Workloads
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_07239.html b/docs/dws/umn/dws_01_07239.html new file mode 100644 index 00000000..f90804bd --- /dev/null +++ b/docs/dws/umn/dws_01_07239.html @@ -0,0 +1,21 @@ + + +

Deleting Workload Queues

+
  1. Log in to the GaussDB(DWS) management console.
  2. On the displayed Clusters page, click the name of the target cluster.
  3. Switch to the Workload Management tab page.
  4. In the Workload Queue area on the left, click the name of the queue to be deleted.
  5. Click Delete on the right.

    If the queue to be deleted has associated database users, these users will be associated with the default queue after the queue is deleted.

    +
    +

    +

+
+
+
+
Parent topic: Managing Cluster Workloads
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_0724.html b/docs/dws/umn/dws_01_0724.html new file mode 100644 index 00000000..ed945e98 --- /dev/null +++ b/docs/dws/umn/dws_01_0724.html @@ -0,0 +1,25 @@ + + +

Managing Logical Clusters

+
+
+ + +
+
Parent topic: Clusters
+
+
+ diff --git a/docs/dws/umn/dws_01_0800.html b/docs/dws/umn/dws_01_0800.html new file mode 100644 index 00000000..980e37df --- /dev/null +++ b/docs/dws/umn/dws_01_0800.html @@ -0,0 +1,23 @@ + + +

Snapshots

+
+
+ + +
+
Parent topic: Cluster HA
+
+
+ diff --git a/docs/dws/umn/dws_01_0818.html b/docs/dws/umn/dws_01_0818.html new file mode 100644 index 00000000..cab15d14 --- /dev/null +++ b/docs/dws/umn/dws_01_0818.html @@ -0,0 +1,41 @@ + + +

Nodes

+

Overview

On the Nodes tab page, you can view the node list of the current cluster, add new nodes to or remove nodes from it, and view the node usage, status, and flavors.

+

+
  • This feature is supported only in 8.1.1.200 or later.
+
+
+

Adding Nodes

This function is more suited for large-scale scale-out. Nodes can be added in batches in advance. For example, if 180 more BMS nodes are needed, add them in three batches (60 for each batch). If some nodes fail to be added, add them again. After all the 180 nodes are successfully added, use the nodes for cluster scale-out. Adding nodes does not affect cluster services.

+

Precautions

+ +

Procedure

+
  1. Log in to the GaussDB(DWS) management console.
  2. Choose Clusters. All clusters are displayed by default.
  3. Click the name of the target cluster. On the Basic Information page that is displayed, click Nodes.
  4. Click Add Node, enter the number of nodes to be added, and click Next: Confirm.

    +

  5. Click Submit. The nodes will start to be added, as shown in the following figure.

    +

    +

+

The nodes that fail to be added will be automatically rolled back and recorded in the displayed list, as shown in the following figure.

+

+
+
+

Removing Nodes

Precautions

+ +

Procedure

+
  1. Log in to the GaussDB(DWS) management console.
  2. Choose Clusters. All clusters are displayed by default.
  3. Click the name of the target cluster. On the Basic Information page that is displayed, click Nodes.
  4. On the Nodes page, select the nodes to be removed, click Remove, and click Yes to submit the task. The nodes that are successfully removed will not be displayed on the Nodes page.

    +

    +

+
+
+
+
+
Parent topic: Clusters
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_0820.html b/docs/dws/umn/dws_01_0820.html new file mode 100644 index 00000000..b115feb7 --- /dev/null +++ b/docs/dws/umn/dws_01_0820.html @@ -0,0 +1,17 @@ + + +

Cluster Redistribution

+
+
+ + +
+
Parent topic: Clusters
+
+
+ diff --git a/docs/dws/umn/dws_01_0822.html b/docs/dws/umn/dws_01_0822.html new file mode 100644 index 00000000..e7a6f185 --- /dev/null +++ b/docs/dws/umn/dws_01_0822.html @@ -0,0 +1,38 @@ + + +

Associating and Disassociating ELB

+

Overview

If the internal IP address or EIP of a CN is used to connect to a cluster, the failure of this CN will lead to cluster connection failure. If a private domain name is used for connection, connection failures can be avoided by polling. However, private domain names cannot be used for public network access, and requests cannot be forwarded in the case of a CN failure. Therefore, ELB is used to avoid single CN failures.

+

An ELB distributes access traffic to multiple ECSs for traffic control based on forwarding policies. It improves the fault tolerance capability of application programs. For details, see Elastic Load Balance User Guide.

+

With ELB health checks, CN requests of a cluster can be quickly forwarded to normal CNs. If a CN is faulty, the workload can be immediately shifted to a healthy node, minimizing cluster access faults.

+

The following ELB operations are supported:

+ +
  • This feature is supported only in cluster version 8.1.1 and later.
  • For load balancing and high availability purposes, and to prevent single CN failures, a cluster must be bound to ELB.
+
+
+

Constraints and Limitations

+
+

Associating ELB

  1. Log in to the GaussDB(DWS) management console.
  2. Click Clusters. All clusters are displayed by default.
  3. Click the name of the target cluster.
  4. On the Basic Information page that is displayed, click Associate ELB and select the ELB name. If no load balancer exists, create one on the ELB management console. Then refresh the GaussDB(DWS) page and associate ELB with the cluster.
  5. After the request is delivered, go back to the Clusters page. Task information Associating ELB of the cluster is displayed. The process takes some time.

    +

  6. Log in to the ELB management console, click the name of the associated ELB, switch to the Backend Server Groups tab, and check whether the cluster CNs are associated with the load balancer.

    +

  1. Open the Basic Information tab of the cluster. The ELB Address will be used for connecting to the cluster.

    +

    +

+
+

Disassociating ELB

  1. Log in to the GaussDB(DWS) management console.
  2. Click Clusters. All clusters are displayed by default.
  3. Click the name of the target cluster.
  4. On the Basic Information page that is displayed, click Disassociate ELB.

    +

  5. After the request is delivered, go back to the Clusters page. Task information Dissociating ELB of the cluster is displayed. The process takes some time.

    +

  6. Log in to the ELB management console, click the name of the dissociated ELB, switch to the Backend Server Groups tab, and check whether the cluster CNs are deleted.

    +

+
+
+
+
+
Parent topic: Cluster HA
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_1013.html b/docs/dws/umn/dws_01_1013.html new file mode 100644 index 00000000..f1d9fd91 --- /dev/null +++ b/docs/dws/umn/dws_01_1013.html @@ -0,0 +1,21 @@ + + +

Automated Snapshots

+
+
+ + +
+
Parent topic: Snapshots
+
+
+ diff --git a/docs/dws/umn/dws_01_10131.html b/docs/dws/umn/dws_01_10131.html new file mode 100644 index 00000000..6e3b8cc0 --- /dev/null +++ b/docs/dws/umn/dws_01_10131.html @@ -0,0 +1,18 @@ + + +

Automated Snapshot Overview

+

Automated snapshots adopt differential incremental backups. The automated snapshot created for the first time is a full backup (base version), and then the system creates full backups at a specified interval. Incremental backups are generated between two full backups. The incremental backup records change based on the previous backup.

+

During snapshot restoration, GaussDB(DWS) uses all backups between the latest full backup and the current incremental backup to restore the cluster. This can prevent data loss.

+

If the retention period of an incremental snapshot exceeds the maximum retention period, GaussDB(DWS) does not delete the snapshot immediately. Instead, GaussDB(DWS) retains it until the next full backup, when the deletion of the snapshot will not hinder incremental data backup and restoration.

+
Figure 1 Snapshot backup process
+

Automated snapshots are enabled by default when you create a cluster. If automated snapshots are enabled for a cluster, GaussDB(DWS) periodically takes snapshots of that cluster based on the time and interval you set, usually every eight hours. You can configure one or more automated snapshot policies for the cluster as required. For details, see Configuring an Automated Snapshot Policy.

+

The retention period of an automated snapshot can be set to 1 to 31 days. The default retention period is 3 days. The system deletes the snapshot at the end of the retention period. If you want to keep an automated snapshot for a longer period, you can create a copy of it as a manual snapshot. The automated snapshot is retained until the end of the retention period, whrereas the corresponding manual snapshot is retained until you manually delete it. For details about how to replicate an automated snapshot, see Copying Automated Snapshots.

+

If you disable the automated snapshot function for an existing cluster, all its automated snapshots will be deleted. However, manual snapshots will not be deleted.

+
+
+
+
+
Parent topic: Automated Snapshots
+
+
+ diff --git a/docs/dws/umn/dws_01_10134.html b/docs/dws/umn/dws_01_10134.html new file mode 100644 index 00000000..a9670f4a --- /dev/null +++ b/docs/dws/umn/dws_01_10134.html @@ -0,0 +1,15 @@ + + +

Deleting an Automated Snapshot

+

Only GaussDB(DWS) can delete automated snapshots. You cannot delete them manually.

+

GaussDB(DWS) deletes an automated snapshot if:

+ +

If you disable automated snapshot, GaussDB(DWS) will stop taking snapshots and delete the existing automated snapshots of the corresponding cluster. Exercise caution when performing this operation.

+
+
+
+
+
Parent topic: Automated Snapshots
+
+
+ diff --git a/docs/dws/umn/dws_01_1015.html b/docs/dws/umn/dws_01_1015.html new file mode 100644 index 00000000..39e22bb2 --- /dev/null +++ b/docs/dws/umn/dws_01_1015.html @@ -0,0 +1,19 @@ + + + +

Restoration Using a Snapshot

+ +

+
+ +
+ + +
+
Parent topic: Snapshots
+
+
+ diff --git a/docs/dws/umn/dws_01_1240.html b/docs/dws/umn/dws_01_1240.html new file mode 100644 index 00000000..807263ba --- /dev/null +++ b/docs/dws/umn/dws_01_1240.html @@ -0,0 +1,19 @@ + + +

Alarms

+
+
+ + +
+
Parent topic: Monitoring and Alarms
+
+
+ diff --git a/docs/dws/umn/dws_01_1241.html b/docs/dws/umn/dws_01_1241.html new file mode 100644 index 00000000..046d712c --- /dev/null +++ b/docs/dws/umn/dws_01_1241.html @@ -0,0 +1,207 @@ + + +

Alarm Management

+

Overview

Alarm management includes viewing and configuring alarm rules and subscribing to alarm information. Alarm rules display alarm statistics and details of the past week for users to view tenant alarms. In addition to providing a set of default GaussDB(DWS) alarm rules, this feature allows you to modify alarm thresholds based on your own services. GaussDB(DWS) alarm notifications are sent using the SMN service.

+

This feature supports only the database kernel of 8.1.1.200 and later.

+
+
+

Visiting the Alarms Page

  1. Log in to the GaussDB(DWS) management console.
  2. In the navigation pane on the left, click Alarms.
  3. On the page that is displayed:

    • Existing Alarm Statistics

      Statistics of the existing alarms in the past seven days are displayed by alarm severity in a bar chart. In this way, you can see clearly the number and category of the alarms generated in the past week.

      +
    • Today's Alarms

      Statistics of the existing alarms on the current day are displayed by alarm severity in a list. In this way, you can see clearly the number and category of the unhandled alarms generated on the day.

      +
    • Alarm details

      Details about all alarms, handled and unhandled, in the past seven days are displayed in a table for you to quickly locate faults, including the alarm name, alarm severity, cluster name, location, description, generation date, and status.

      +
    +

    +

    The alarm data displayed (a maximum of 30 days) is supported by the Event Service microservice.

    +
    +

+
+

Alarm Types and Alarms

+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 Threshold alarms of DMS alarm sources

Type

+

Name

+

Severity

+

Description

+

Default

+

Node CPU Usage Exceeds the Threshold

+

Urgent

+

This alarm is generated if the threshold of CPU usage (system + user) of any node in the cluster is exceeded within the specified period and the constraint is not met. The alarm will be cleared when the CPU usage (system + user) is lower than the threshold and the constraint is not met.

+

Default

+

Node System CPU Usage Exceeds the Threshold

+

Urgent

+

This alarm is generated if the threshold of system CPU usage of any node in the cluster is exceeded within the specified period and the constraint is not met. The alarm will be cleared when the system CPU usage is lower than the threshold and the constraint is not met.

+

Default

+

Node Swap Usage Exceeds the Threshold

+

Urgent

+

This alarm is generated if the threshold of swap usage of any node in the cluster is exceeded within the specified period and the constraint is not met. The alarm will be cleared when the swap usage is lower than the threshold and the constraint is not met.

+

Default

+

Node System Disk Usage Exceeds the Threshold

+

Urgent: > 85%; Important: >75%

+

This alarm is generated if the threshold of system disk (/) usage of any node in the cluster is exceeded within the specified period and the constraint is not met. The alarm will be cleared when the system disk (/) usage is lower than the threshold and the constraint is not met.

+

Default

+

Node Log Disk Usage Exceeds the Threshold

+

Urgent: > 85%; Important: >75%

+

This alarm is generated if the threshold of log disk (/var/chroot/DWS/manager) usage of any node in the cluster is exceeded within the specified period and the constraint is not met. The alarm will be cleared when the log disk (/var/chroot/DWS/manager) usage is lower than the threshold and the constraint is not met.

+

Default

+

Node Data Disk Usage Exceeds the Threshold

+

Urgent: > 85%; Important: >75%

+

This alarm is generated if the threshold of data disk (/var/chroot/DWS/data[n]) usage of any node in the cluster is exceeded within the specified period and the constraint is not met. The alarm will be cleared when the data disk (/var/chroot/DWS/data[n]) usage is lower than the threshold and the constraint is not met.

+

Default

+

Node System Disk I/O Usage Exceeds the Threshold

+

Urgent

+

This alarm is generated if the threshold of system disk (/) I/O usage (util) of any node in the cluster is exceeded within the specified period and the constraint is not met. The alarm will be cleared when the system disk (/) I/O usage (util) is lower than the threshold and the constraint is not met.

+

Default

+

Node Log Disk I/O Usage Exceeds the Threshold

+

Urgent

+

This alarm is generated if the threshold of log disk (/var/chroot/DWS/manager) I/O usage (util) of any node in the cluster is exceeded within the specified period and the constraint is not met. The alarm will be cleared when the log disk (/var/chroot/DWS/manager) I/O usage (util) is lower than the threshold and the constraint is not met.

+

Default

+

Node Data Disk I/O Usage Exceeds the Threshold

+

Urgent

+

This alarm is generated if the threshold of data disk (/var/chroot/DWS/data[n]) I/O usage (util) of any node in the cluster is exceeded within the specified period and the constraint is not met. The alarm will be cleared when the data disk (/var/chroot/DWS/data[n]) I/O usage (util) is lower than the threshold and the constraint is not met.

+

Default

+

Node System Disk Latency Exceeds the Threshold

+

Important

+

This alarm is generated if the threshold of system disk (/) I/O latency (await) of any node in the cluster is exceeded within the specified period and the constraint is not met. The alarm will be cleared when the system disk (/) I/O latency (await) is lower than the threshold and the constraint is not met.

+

Default

+

Node Log Disk Latency Exceeds the Threshold

+

Important

+

This alarm is generated if the threshold of log disk (/var/chroot/DWS/manager) I/O latency (await) of any node in the cluster is exceeded within the specified period and the constraint is not met. The alarm will be cleared when the log disk (/var/chroot/DWS/manager) I/O latency (await) is lower than the threshold and the constraint is not met.

+

Default

+

Node Data Disk Latency Exceeds the Threshold

+

Important

+

This alarm is generated if the threshold of data disk (/var/chroot/DWS/data[n]) I/O latency (await) of any node in the cluster is exceeded within the specified period and the constraint is not met. The alarm will be cleared when the data disk (/var/chroot/DWS/data[n]) I/O latency (await) is lower than the threshold and the constraint is not met.

+

Default

+

Node System Disk Inode Usage Exceeds the Threshold

+

Urgent: > 85%; Important: >75%

+

This alarm is generated if the threshold of system disk (/) inode usage of any node in the cluster is exceeded within the specified period and the constraint is not met. The alarm will be cleared when the system disk (/) inode usage is lower than the threshold and the constraint is not met.

+

Default

+

Node Log Disk Inode Usage Exceeds the Threshold

+

Urgent: > 85%; Important: >75%

+

This alarm is generated if the threshold of log disk (/var/chroot/DWS/manager) inode usage of any node in the cluster is exceeded within the specified period and the constraint is not met. The alarm will be cleared when the log disk (/var/chroot/DWS/manager) inode usage is lower than the threshold and the constraint is not met.

+

Default

+

Node Data Disk Inode Usage Exceeds the Threshold

+

Urgent: > 85%; Important: >75%

+

This alarm is generated if the threshold of data disk (/var/chroot/DWS/data[n]) inode usage of any node in the cluster is exceeded within the specified period and the constraint is not met. The alarm will be cleared when the data disk (/var/chroot/DWS/data[n]) inode usage is lower than the threshold and the constraint is not met.

+

Default

+

Data Flushed to Disks of the Query Statement Exceeds the Threshold

+

Urgent

+

This alarm is generated if the threshold of data flushed to disks of the SQL statement in the cluster is exceeded within the specified period and the constraint is not met. The alarm can be cleared only after you handle the SQL statement.

+

Default

+

Number of Queuing Query Statements Exceeds the Threshold

+

Urgent

+

This alarm is generated if the threshold of the number of queuing SQL statements is exceeded within the specified period. The alarm will be cleared when the number of queuing SQL statements is less than the threshold.

+

Custom

+

Name of the user-defined threshold alarm

+

User-defined alarm severity

+

Alarm description

+
+
+
+
+
+
+
Parent topic: Alarms
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_1242.html b/docs/dws/umn/dws_01_1242.html new file mode 100644 index 00000000..453e3302 --- /dev/null +++ b/docs/dws/umn/dws_01_1242.html @@ -0,0 +1,40 @@ + + +

Alarm Rules

+

Overview

+
+

Viewing Alarm Rules

  1. Log in to the GaussDB(DWS) management console.
  2. In the navigation pane on the left, choose Alarms.
  3. Click View Alarm Rule in the upper left corner. On the page that is displayed, you can see the threshold alarm rules of database cluster monitoring metrics, as shown in the following figure.
+
+

Modifying an Alarm Rule

  1. Log in to the GaussDB(DWS) management console.
  2. In the navigation pane on the left, click Alarms.
  3. Click View Alarm Rule in the upper left corner.
  4. On the Alarm Rules page that is displayed, click Modify in the Operation column of the target alarm rule.

    • Alarm Rule
    • Description
    • Associated Cluster: From the drop-down list, select the current tenant's clusters to which the alarm rule applies.
    • Triggered Policies
      • Independent: Alarm policies are triggered independently of each other.
      • Priority: Alarm policies are triggered by priority. Policies of a lower priority will be automatically triggered after those of a higher priority.
      +
    • Alarm Policy
      • Metric: GaussDB(DWS) monitoring metric, which is the data source used by the alarm engine for threshold determination.
      • Trigger: calculation rule for threshold determination of a monitoring metric. Select the average value within a period of time of a metric to reduce the probability of alarm oscillation.
      • Constraint: suppresses the repeated triggering and clearance of alarms of the same type within the specified period.
      • Alarm Severity: includes Urgent, Important, Minor, and Prompt.
      +
    +

    +

    You can modify only some items of the default rules (associated cluster, alarm policy threshold, time period, and alarm constraint). User-defined rules support modification of all items.

    +
    +

  5. Confirm the information and click OK.
+
+

Creating an Alarm Rule

  1. Log in to the GaussDB(DWS) management console.
  2. In the navigation pane on the left, click Alarms.
  3. Click View Alarm Rule in the upper left corner.
  4. Click Create Alarm Rule in the upper right corner. You can configure items, such as the alarm rule name, rule description, clusters associated with the rule, and alarm policy.

    • Alarm Rule
    • Description
    • Associated Cluster: From the drop-down list, select the current tenant's clusters to which the alarm rule applies.
    • Triggered Policies
      • Independent: Alarm policies are triggered independently of each other.
      • Priority: Alarm policies are triggered by priority. Policies of a lower priority will be automatically triggered after those of a higher priority.
      +
    • Alarm Policy
      • Metric: GaussDB(DWS) monitoring metric, which is the data source used by the alarm engine for threshold determination.
      • Alarm Object: databases in the selected cluster and schemas in the selected databases.
      • Trigger: calculation rule for threshold determination of a monitoring metric. Select the average value within a period of time of a metric to reduce the probability of alarm oscillation.
      • Constraint: suppresses the repeated triggering and clearance of alarms of the same type within the specified period.
      • Alarm Severity: includes Urgent, Important, Minor, and Prompt.
        Figure 1 Creating an alarm rule
        +

        Currently, only alarm rules of schema usage metrics can be created on GaussDB(DWS).

        +
        +
      +
    +

+
+
+
+
+
Parent topic: Alarms
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_1243.html b/docs/dws/umn/dws_01_1243.html new file mode 100644 index 00000000..dd0fbb33 --- /dev/null +++ b/docs/dws/umn/dws_01_1243.html @@ -0,0 +1,60 @@ + + +

Alarm Subscriptions

+

You can subscribe to GaussDB(DWS) alarm notifications to receive notifications by SMS message, email, or application when an alarm of a specified severity is generated.

+

Creating a Subscription

  1. Log in to the GaussDB(DWS) management console.
  2. In the navigation pane on the left, choose Alarms > Subscriptions.
  3. Click Create Subscription in the upper left corner of the page.
  4. In the Subscription Settings area, configure the basic information and alarm severity of the subscription.

    + +
    + + + + + + + + + + + + + +
    Table 1 Subscription parameters

    Parameter

    +

    Description

    +

    Status

    +

    Whether to enable the alarm subscription.

    +

    indicates that the alarm subscription is enabled. indicates that the alarm subscription is disabled. When you disable a subscription, you will not receive the corresponding alarm notifications, but the subscription will not be deleted.

    +

    Subscription Name

    +

    Name of the alarm subscription:

    +
    • Contains only letters, digits, hyphens (-), and underscores (_), and must start with a letter or digit.
    • Contains 1 to 256 characters.
    +

    Alarm Severity

    +

    Severity of the alarm you want to subscribe to: Urgent, Important, Minor, or Prompt

    +
    +
    +

  5. The Subscribed Alarms area displays the subscribed alarms by subscription settings. Select an SMN topic from the drop-down list.

    To create a topic, click Create Topic to switch to the SMN console page. For details, .

    +

    +

    +

    The selected topic must have granted GaussDB(DWS) the permission for publishing messages to the topic. To grant permissions, configure topic policies on the SMN management console. When configuring the topic policy, select DWS as the service that can publish messages to this topic.

    +
    +

  6. Confirm the information and click OK.
+
+

Modifying a Subscription

  1. Log in to the GaussDB(DWS) management console.
  2. In the navigation pane on the left, choose Alarms and click the Subscriptions tab.
  3. In the Operation column of the target subscription, click Edit.

    +

  4. On the Edit Subscription page displayed, modify the parameters. For details, see 4 to 5.

    +

  5. Click OK.
+
+

Deleting a Subscription

  1. Log in to the GaussDB(DWS) management console.
  2. In the navigation pane on the left, choose Alarms > Subscriptions.
  3. In the Operation column of the target subscription, click Delete. A confirmation dialog box is displayed.

    +

  4. Click Yes to delete the subscription.
+
+
+
+
+
Parent topic: Alarms
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_1331.html b/docs/dws/umn/dws_01_1331.html new file mode 100644 index 00000000..261cf2c0 --- /dev/null +++ b/docs/dws/umn/dws_01_1331.html @@ -0,0 +1,41 @@ + + +

Node Monitoring

+

Node Monitoring

  1. Log in to the GaussDB(DWS) management console.
  2. On the Clusters page, locate the target cluster.
  3. In the Operation column of the target cluster, click Monitoring Panel. The database monitoring page is displayed.
  4. In the navigation pane on the left, choose Monitoring > Node Monitoring.

    On the page that is displayed, view the real-time consumption of nodes, memory, disks, disk I/O, and network I/O.

    +

+
+

Overview

On the Overview tab page, you can view the key resources of a specified node based on the node name, including:

+ +

+

+
+

Disks

On the Disks tab page, view the real-time disk resource consumption of a node by node name and disk name, including:

+ +

+

+

The sum of the used disk space and available disk space is not equal to the total disk space. This is because a small amount of space is reserved in each default partition for system administrators to use. Even if common users have run out of space, system administrators can log in to the system and use their space required for solving problems.

+

Run the Linux df command to collect the disk capacity information, as shown in the following figure.

+

+

/dev/sda4: Used(5757444) + Available(540228616) != Total(569616888)

+
  • Filesystem: path name of the device file corresponding to the file system. Generally, it is a hard disk partition.
  • IK-blocks: number of data blocks (1024 bytes) in a partition.
  • Used: number of data blocks used by the disk.
  • Available: number of available data blocks on the disk.
  • Use%: percentage of the space used by common users. Even if the space is used up, the partition still reserves the space for system administrators.
  • Mounted on: mount point of the file system.
+
+
+

Network

On the Network tab page, view the real-time network resource consumption of a node by node name and NIC name, including:

+ +

+

+
+
+
+
+
Parent topic: Monitoring
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_1332.html b/docs/dws/umn/dws_01_1332.html new file mode 100644 index 00000000..93529322 --- /dev/null +++ b/docs/dws/umn/dws_01_1332.html @@ -0,0 +1,28 @@ + + +

Database Monitoring

+

Database Monitoring

  1. Log in to the GaussDB(DWS) management console.
  2. On the Clusters page, locate the target cluster.
  3. In the Operation column of the target cluster, click Monitoring Panel. The database monitoring page is displayed.
  4. In the navigation pane on the left, choose Monitoring > Database Monitoring.

    The Database Monitoring page displays the real-time and historical resource consumption a database.

    +

+
+

Database Resource Consumption

You can select a database and check its resource usage. For details, see Monitoring Metrics. including:

+ +

+
+

Database Trend Monitoring

In the Monitoring column of a database, click to view the performance indicators of the database, including:

+ +

+
+
+
+
+
Parent topic: Monitoring
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_1333.html b/docs/dws/umn/dws_01_1333.html new file mode 100644 index 00000000..463a4ace --- /dev/null +++ b/docs/dws/umn/dws_01_1333.html @@ -0,0 +1,28 @@ + + +

Session Monitoring

+

Session Monitoring

  1. Log in to the GaussDB(DWS) management console.
  2. On the Clusters page, locate the target cluster.
  3. In the Operation column of the target cluster, click Monitoring Panel.
  4. In the navigation pane on the left, choose Monitoring > Session Monitoring.

    The Session Monitoring page displays the session-level real-time database query statistics. You can also select and terminate a session.

    +

+
+

Query Statistics

You can browse the query statistics of a specified session based on the session ID, including:

+ +

+
+

Terminating a Session

Select a session to be terminated, click Terminate a Session, and confirm your operation.

+

The fine-grained permission control function is added. Only users with the operate permission are able to terminate sessions. For users with the read-only permission, the Terminate a Session button is grayed out.

+
+
+
+
+
+
Parent topic: Monitoring
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_1334.html b/docs/dws/umn/dws_01_1334.html new file mode 100644 index 00000000..c4ff644b --- /dev/null +++ b/docs/dws/umn/dws_01_1334.html @@ -0,0 +1,103 @@ + + +

Query Monitoring

+

Query Monitoring

  1. Log in to the GaussDB(DWS) management console.
  2. On the Clusters page, locate the target cluster.
  3. In the Operation column of the target cluster, click Monitoring Panel.
  4. In the navigation pane on the left, choose Monitoring > Query Monitoring.

    The Query Monitoring page displays the real-time information about all queries that are running in a cluster and the historical information about the queries that have been run.

    +

+
+

Prerequisites

You need to set GUC parameters before viewing data on the monitoring page. If GUC parameters are not set, real-time or historical query may be unavailable. However, if this parameter is set, the cluster performance may deteriorate. Therefore, you need to balance the settings of related parameters. The following table describes recommended settings. For details about how to modify parameters, see "Modifying Database Parameters". Setting GUC Parameters provides parameter details.

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 Recommended GUC parameter settings

GUC Parameter

+

CN Configuration

+

DN Configuration

+

max_active_statements

+

10

+

10

+

enable_resource_track

+

on

+

on

+

resource_track_level

+

query

+

query

+

resource_track_cost

+

0

+

0

+

resource_track_duration

+

0

+

0

+

enable_resource_record

+

on

+

on

+

session_statistics_memory

+

1000MB

+

1000MB

+
+
+
+

Querying Information

In this area, you can browse the number of queries in different status, including Running, Blocked, Delayed, Canceled, Fast Lane, and Slow Lane.

+

+
+

Real-Time Query

In the Real-Time Query area, you can browse the real-time information about all running queries, including:

+ +
+

Terminating a Query

Select a query to be terminated, click Terminate Query, and confirm your operation.

+

The fine-grained permission control function is added. Only users with the operate permission are able to terminate queries. For users with the read-only permission, the Terminate Query button is grayed out.

+
+
+

Historical Query

In the History area, you can browse all historical query information based on the specified time period, including:

+ +
+

Viewing Query Monitoring Details

You can click a query ID to view the query details, including the basic information of query statements, real-time and historical resource consumption, SQL description, and query plan.

+

+
+
+
+
+
Parent topic: Monitoring
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_1337.html b/docs/dws/umn/dws_01_1337.html new file mode 100644 index 00000000..f3e387ba --- /dev/null +++ b/docs/dws/umn/dws_01_1337.html @@ -0,0 +1,39 @@ + + +

Performance Monitoring

+

Performance Monitoring

  1. Log in to the GaussDB(DWS) management console.
  2. On the Clusters page, locate the target cluster.
  3. In the Operation column of the target cluster, click Monitoring Panel.
  4. In the navigation pane on the left, choose Monitoring > Performance Monitoring.

    The Performance Monitoring page displays the resource consumption trends of clusters and databases.

    +

+
+

Monitoring Panel

You can configure monitoring views by customizing monitoring panels. Monitoring views are bound to users. After logging in to the system, you can view the user-defined monitoring panels.

+ +

+
+

Adding a Monitoring View

Currently, DMS provides two types of monitoring views: cluster and database. You can click Add View to add a monitoring view as required The monitoring indicators are as follows:

+ +
+

Exporting Monitoring Data

Performance Monitoring supports data export. You can click Export Data to further process data. By default, data in all monitoring views on the current page is exported. The export time range is subject to the selected time range.

+

+

Performance Monitoring allows data aggregation of different periods. You can aggregate raw data based on the corresponding sampling period to display indicator trends of a longer period.

+

+
+

+
+
+
+
+
Parent topic: Monitoring
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_1338.html b/docs/dws/umn/dws_01_1338.html new file mode 100644 index 00000000..b60d90ac --- /dev/null +++ b/docs/dws/umn/dws_01_1338.html @@ -0,0 +1,24 @@ + + +

Instance Monitoring

+

Instance Monitoring

  1. Log in to the GaussDB(DWS) management console.
  2. On the Clusters page, locate the target cluster.
  3. In the Operation column of the target cluster, click Monitoring Panel.
  4. In the navigation pane on the left, choose Monitoring > Instance Monitoring.

    On the Instance Monitoring page, you can view the real-time and historical information about detected slow instances.

    +

+
+

Slow Instance Detection

DMS can automatically configure and start the slow instance detection script on cluster CNs, periodically collect the cache table of the script, and report the detected slow instance data. You can view the number of slow instances detected within 24 hours and the distribution status in the time dimension on the GUI to quickly locate the slow nodes in the cluster and analyze the root causes.

+

The Instance Monitoring page consists of two parts. The upper part displays the time distribution chart of detected slow instances, that is, the number of slow instances detected in different detection periods. The lower part displays slow instance details. When you select any bar in the time distribution chart, details about the detection time, node name, instance name, and number of detections (within 24 hours) of slow instances are displayed.

+

+
+
+
+
+
Parent topic: Monitoring
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_1339.html b/docs/dws/umn/dws_01_1339.html new file mode 100644 index 00000000..6c3b12de --- /dev/null +++ b/docs/dws/umn/dws_01_1339.html @@ -0,0 +1,37 @@ + + +

Load Monitoring

+

Load Monitoring

  1. Log in to the GaussDB(DWS) management console.
  2. On the Clusters page, locate the target cluster.
  3. In the Operation column of the target cluster, click Monitoring Panel.
  4. In the navigation pane on the left, choose Monitoring > Load Monitoring.

    On the Load Monitoring page, you can view the real-time and historical resource consumption of workload queues.

    +

+
+

Workload Queues

The DMS displays the user-defined workload queue name, real-time and historical resource consumption, and workload queue resource quotas.

+ +

+
+

Exception Handling Rules

You can click the drop-down list of any workload queue to view the exception handling rule configured for the workload queue.

+ +

+
+

Waiting Queries

You can view the waiting queries in a workload queue in real time to identify the service pressure.

+ +

+
+

Circuit Breaking Queries

You can view the status of a triggered circuit breaking query in a workload queue.

+ +

+
+
+
+
+
Parent topic: Monitoring
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_1911.html b/docs/dws/umn/dws_01_1911.html new file mode 100644 index 00000000..b5c5b30e --- /dev/null +++ b/docs/dws/umn/dws_01_1911.html @@ -0,0 +1,18 @@ + + +

Overview

+
+
+
+
+
Parent topic: Audit Logs
+
+
+ diff --git a/docs/dws/umn/dws_01_7115.html b/docs/dws/umn/dws_01_7115.html new file mode 100644 index 00000000..7820df55 --- /dev/null +++ b/docs/dws/umn/dws_01_7115.html @@ -0,0 +1,39 @@ + + +

CNs

+

Purpose

After a cluster is created, the number of required CNs varies with service requirements. The CN management function enables you to adjust the number of CNs in the cluster. The operations are as follows:

+ +
+

Constraints and Limitations

+
+

Adding CNs

  1. Log in to the GaussDB(DWS) management console.
  2. On the Clusters page, locate the cluster to which you want to add CNs.
  3. In the Operation column of the specified cluster, choose More > Manage CN > Add CN Node.

    +

    +

  4. On the displayed page, set the number of CNs as required and click OK.

    +
    • Before adding a CN, ensure that the cluster is in the Available, Unbalanced, or Redistributing state.
    • The number of CNs after adjustment must be greater than the number of deployed CNs, less than or equal to the number of nodes, and less than or equal to 20.
    +
    +

+
+

Deleting CNs

  1. Log in to the GaussDB(DWS) management console.
  2. On the Clusters page, locate the cluster from which you want to delete CNs.
  3. In the Operation column of the specified cluster, choose More > Manage CN > Delete CN Node.

    +

    +

  4. On the displayed page, select the CN to be deleted and click OK.

    +
    • At least one CN must be reserved when you delete a CN.
    • When you delete a CN, the cluster must be in the Available, Degraded, or Unbalanced state.
    • If an elastic IP address has been bound to a CN, the CN cannot be deleted.
    • If abnormal nodes exist, only the abnormal CNs can be deleted.
      • If one CN is faulty, only this CN can be deleted.
      • If two or more CNs are faulty, no CN can be deleted.
      +
    +
    +

+
+
+
+
+
Parent topic: Cluster HA
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_72362.html b/docs/dws/umn/dws_01_72362.html new file mode 100644 index 00000000..25e98fb7 --- /dev/null +++ b/docs/dws/umn/dws_01_72362.html @@ -0,0 +1,43 @@ + + +

Workload Plans

+

Overview

Workload plan is an advanced workload management feature provided by GaussDB(DWS). You can create a workload plan, add multiple stages to the plan, and configure different queue resource ratios for the stages. When a plan is started, it automatically switches the queue resource configurations in different stages. If a customer runs different services in different stages and these services occupy different proportions of resources, the workload plan function can help the customer implement automatic switchover of queue resource configurations in different stages.

+

+
+

Adding Workload Plans

  1. Log in to the GaussDB(DWS) management console.
  2. On the displayed Clusters page, click the name of the target cluster.
  3. Switch to the Workload Management tab page.
  4. Click the plus sign (+) next to Workload Plan to add a workload plan.
  5. Enter a plan name and click OK.

    1. Before creating a workload plan, you must plan and create workload queues. For details, see Adding Workload Queues.

    +

    2. You can create a maximum of 10 workload plans.

    +
    +

    +

+
+

Starting Workload Plans

  1. Log in to the GaussDB(DWS) management console.
  2. On the displayed Clusters page, click the name of the target cluster.
  3. Switch to the Workload Management tab page.
  4. Enter the plan details page and click Start to start a workload plan.

    • Only one plan can be started for each cluster.
    • A plan must have at least two stages before it can be started.
    +
    +

    +

+
+

Checking Execution Logs of Workload Plans

  1. Log in to the GaussDB(DWS) management console.
  2. On the displayed Clusters page, click the name of the target cluster.
  3. Switch to the Workload Management tab page.
  4. Go to the plan details page and view the switchover logs in the Plan Execution Log area.

    +

    +

+
+

Stopping Workload Plans

  1. Log in to the GaussDB(DWS) management console.
  2. On the displayed Clusters page, click the name of the target cluster.
  3. Switch to the Workload Management tab page.
  4. Enter the plan details page and click Stop to stop a workload plan.

    +

+
+

Deleting Workload Plans

  1. Log in to the GaussDB(DWS) management console.
  2. On the displayed Clusters page, click the name of the target cluster.
  3. Switch to the Workload Management tab page.
  4. Enter the plan details page and click Delete to delete a workload plan.

    You cannot delete a running workload plan.

    +
    +

    +

+
+
+
+
+
Parent topic: Managing Cluster Workloads
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_72363.html b/docs/dws/umn/dws_01_72363.html new file mode 100644 index 00000000..a9e2391f --- /dev/null +++ b/docs/dws/umn/dws_01_72363.html @@ -0,0 +1,36 @@ + + +

Stages of Workload Plans

+

Adding Stages for a Workload Plan

  1. Log in to the GaussDB(DWS) management console.
  2. On the displayed Clusters page, click the name of the target cluster.
  3. Switch to the Workload Management tab page.
  4. Go to the plan details page and click Add in the Plan stage area. On the Add Stage page, enter the stage name and configure the queue information. Confirm the configuration and click OK.

    • You must stop the workload plan when adding a stage. Otherwise, the stage cannot be added.
    • You can add a maximum of 48 stages for each plan.
    • The switchover time of all phases in a plan cannot be the same.
    +
    +

    +

+

+
+

Modifying Stages for a Workload Plan

  1. Log in to the GaussDB(DWS) management console.
  2. On the displayed Clusters page, click the name of the target cluster.
  3. Switch to the Workload Management tab page.
  4. Go to the plan details page and click Modify in the Operation column of the target plan stage.

    +

  5. On the Modify Stage page, you can modify information such as the switchover time and queue configurations.

    +

+
+

Manually Switching Stages for a Workload Plan

If a running plan needs to be switched to a stage in advance, you can manually do it.

+
  1. Log in to the GaussDB(DWS) management console.
  2. On the displayed Clusters page, click the name of the target cluster.
  3. Switch to the Workload Management tab page.
  4. Go to the plan details page, click the Handover button in the plan overview area, and select the target stage.

    +

+
+

Deleting Stages for a Workload Plan

  1. Log in to the GaussDB(DWS) management console.
  2. On the displayed Clusters page, click the name of the target cluster.
  3. Switch to the Workload Management tab page.
  4. Go to the plan details page and click Delete in the Operation column of the target plan stage.

    +

+

You must stop the workload plan when deleting a stage. Otherwise, the stage cannot be deleted.

+
+
+
+
+
+
Parent topic: Managing Cluster Workloads
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_72365.html b/docs/dws/umn/dws_01_72365.html new file mode 100644 index 00000000..aa9aa569 --- /dev/null +++ b/docs/dws/umn/dws_01_72365.html @@ -0,0 +1,26 @@ + + +

Importing and Exporting Workload Plans

+

You can commission a workload plan in the test environment and export the plan configurations to the production environment.

+

Exporting a Workload Plan

  1. Log in to the GaussDB(DWS) management console.
  2. On the displayed Clusters page, click the name of the target cluster.
  3. Switch to the Workload Management tab page.
  4. Enter the plan details page and click Export to export a workload plan.

    +

+
+

Importing a Workload Plan

  1. Log in to the GaussDB(DWS) management console.
  2. On the displayed Clusters page, click the name of the target cluster.
  3. Switch to the Workload Management tab page.
  4. Enter the plan details page, click Import, and select and import the target configuration file to the workload plan.

    • An ongoing workload plan cannot be imported.
    • Before importing a workload plan, you need to create workload queues.
    +
    +

    +

+
+
+
+
+
Parent topic: Managing Cluster Workloads
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_7241.html b/docs/dws/umn/dws_01_7241.html new file mode 100644 index 00000000..11942c9f --- /dev/null +++ b/docs/dws/umn/dws_01_7241.html @@ -0,0 +1,39 @@ + + +

Overview

+

A physical cluster can be divided into logical clusters that use the node-group mechanism. Tables in a database can be allocated to different physical nodes by logical cluster. A logical cluster can contain tables from multiple databases. Figure 1 shows the relationships between logical clusters, databases, and tables.

+
Figure 1 Relationships between logical clusters, databases, and tables
+
  • Logical clusters are supported in 8.1.0.100 or later.
  • You are advised to allocate tables in a database to the same logical cluster.
+
+

Permissions (Logical Clusters)

+ +
+

Elastic Cluster

An elastic cluster consists of non-logical cluster nodes in a physical cluster in logical cluster mode. The elastic cluster is named elastic_group, which is a special node group that can contain multiple or no DNs.

+

An elastic cluster cannot be manually created. When the first logical cluster is created in a physical cluster, an elastic cluster is also automatically created and all physical nodes not belonging to the logical cluster are automatically added to the elastic cluster. DNs in the elastic cluster will be used for logical clusters created later. To create a logical cluster, ensure that your logical cluster has DNs. (DNs are not required only when you create the first logical cluster in physical cluster mode.) You can add new physical nodes to the elastic cluster through scale-out.

+
+

Replication Table Node Group

A replication table node group is a special node group in logical cluster mode. It can contain one or more logical clusters, but can only create replication tables. One typical scenario is to create public dimension tables. If multiple logical clusters require some common dimension tables, create a replication table node group and add the common dimension tables to it. The logical clusters contained in the replication table node group can access these dimension tables on the local DNs, with no need to access the tables on other DNs. If a logical cluster is scaled in, the replication table node group will be scaled accordingly. If the logical cluster is deleted, the replication table node group will be scaled in. However, if the replication table node group contains only one logical cluster and the logical cluster is deleted, the replication table node group will also be deleted. In this case, create tables in a logical cluster instead.

+

Create a replication table node group using the CREATE NODE GROUP SQL statement and delete one using DROP NODE GROUP. Before deleting a replication table node group, delete all table objects in the node group.

+

Creation of replication table node groups is supported in 8.1.2 or later.

+
+
+

Constraints and Limitations

+
+
+
+
+
Parent topic: Managing Logical Clusters
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_7242.html b/docs/dws/umn/dws_01_7242.html new file mode 100644 index 00000000..d184ea93 --- /dev/null +++ b/docs/dws/umn/dws_01_7242.html @@ -0,0 +1,27 @@ + + +

Adding Logical Clusters

+
  1. Log in to the GaussDB(DWS) management console.
  2. In the cluster list, click the name of a cluster.
  3. On the Basic Information page, enable Logical Cluster.

    +

    +

    +

    +

  4. Go to the Logical Clusters tab and click Add Logical Cluster.

    +

    +

  5. Move the ring you want to add from the right to the left panel, enter the logical cluster name, and click OK.

    +

+
  • If you access the Logical Clusters page for the first time, the metadata of the logical cluster created at the backend is synchronized to the frontend. After the synchronization is complete, you can view information about the logical clusters at the frontend. The logical cluster name is case sensitive. For example, metadata of lc1 and LC1 cannot be synchronized.
+
+
+
+
+
Parent topic: Managing Logical Clusters
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_7243.html b/docs/dws/umn/dws_01_7243.html new file mode 100644 index 00000000..651ad63b --- /dev/null +++ b/docs/dws/umn/dws_01_7243.html @@ -0,0 +1,23 @@ + + +

Editing Logical Clusters

+
  1. Log in to the GaussDB(DWS) management console.
  2. In the cluster list, click the name of a cluster.
  3. Switch to the Logical Clusters tab and click Edit in the Operation column of the target cluster.

    +

    +

  4. Add a node to the logical cluster by moving the selected ring from the right to the left, or remove a node from the logical cluster by moving the selected ring from the left to the right, and click OK.

    +

+
  • Nodes are added to or removed from a logical cluster by ring.
  • At least one ring must be reserved in a logical cluster.
  • The ring removed from the logical cluster will be added to the elastic cluster.
+
+
+
+
+
Parent topic: Managing Logical Clusters
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_7244.html b/docs/dws/umn/dws_01_7244.html new file mode 100644 index 00000000..45ebe306 --- /dev/null +++ b/docs/dws/umn/dws_01_7244.html @@ -0,0 +1,21 @@ + + +

Deleting Logical Clusters

+
  1. Log in to the GaussDB(DWS) management console.
  2. In the cluster list, click the name of a cluster.
  3. Switch to the Logical Clusters page. Click Delete in the Operation column of the target cluster, and click OK in the displayed dialog box.

    +

+
  • The first added logical cluster cannot be deleted.
  • Nodes of the deleted logical cluster are added to the elastic cluster.
+
+
+
+
+
Parent topic: Managing Logical Clusters
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_7245.html b/docs/dws/umn/dws_01_7245.html new file mode 100644 index 00000000..f0957556 --- /dev/null +++ b/docs/dws/umn/dws_01_7245.html @@ -0,0 +1,19 @@ + + +

Restarting Logical Clusters

+
  1. Log in to the GaussDB(DWS) management console.
  2. In the cluster list, click the name of a cluster.
  3. Switch to the Logical Clusters page. Click Restart in the Operation column of the target cluster, and click OK in the displayed dialog box.

    +

+
+
+
+
Parent topic: Managing Logical Clusters
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_7246.html b/docs/dws/umn/dws_01_7246.html new file mode 100644 index 00000000..797bcb88 --- /dev/null +++ b/docs/dws/umn/dws_01_7246.html @@ -0,0 +1,22 @@ + + +

Scaling Out Logical Clusters

+
  1. Log in to the GaussDB(DWS) management console.
  2. On the displayed Clusters page, click More in the Operation column of the target cluster, and select Scale Out.

    +

  3. On the Scale Out page, select the logical cluster or elastic cluster to be scaled out and click Next to confirm specifications.

    +

+
  • Logical clusters and elastic clusters cannot be scaled out online.
+
+
+
+
+
Parent topic: Managing Logical Clusters
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_8115.html b/docs/dws/umn/dws_01_8115.html new file mode 100644 index 00000000..810cc171 --- /dev/null +++ b/docs/dws/umn/dws_01_8115.html @@ -0,0 +1,27 @@ + + +

Performing a Primary/Standby Switchback

+

Context

In the Unbalanced state, the number of primary instances on some nodes increases. As a result, the load pressure is high. In this case, the cluster is normal, but the overall performance is lower than that in the balanced state. During off-peak hours, you are advised to perform a switchback to restore the primary/standby relationship of your cluster.

+
  • Only 8.1.1.202 and later versions support primary/standby switchback.
  • You are advised to perform a switchback during off-peak hours. Switchback interrupts services for a short period of time. The actual interruption duration depends on your service volume.
+
+
+

Procedure

  1. Log in to the GaussDB(DWS) management console.
  2. On the Clusters page, find a cluster in Unbalanced state.
  3. In the Operation column of the cluster, choose More > Switchback.

    +

  4. In the dialog box that is displayed, confirm that the service is in off-peak hours, and click Yes. A message will be displayed in the upper right corner, indicating that the switchback request is being processed.

    +

  5. Check the cluster status. During the switchback, the cluster status is Switching back. After the switchback, the cluster status will change to Available.

    +

+
+

+
+
+
+
Parent topic: Clusters
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_8201.html b/docs/dws/umn/dws_01_8201.html new file mode 100644 index 00000000..70c02ab0 --- /dev/null +++ b/docs/dws/umn/dws_01_8201.html @@ -0,0 +1,46 @@ + + +

Redistributing Data

+

Data redistribution, where data in existing nodes is evenly allocated to the new nodes after you scale out a cluster, is a time-consuming yet crucial task that accelerates service response.

+

By default, redistribution is automatically started after cluster scale-out. For enhanced reliability, disable the automatic redistribution function and manually start a redistribution task after the scale-out is successful. In this way, both scale-out and redistribution can be retried upon failures.

+

Currently, offline redistribution and online redistribution are supported. The default mode is offline redistribution.

+
  • The cluster redistribution function is supported in 8.1.1.200 or later.
  • This function can be manually enabled only when the cluster task information displays To be redistributed after scale-out.
  • You can also select the redistribution mode when you configure cluster scale-out (see Configure advanced parameters).
+
+

Offline Redistribution

Precautions

+ +

Procedure

+
+
  1. Log in to the GaussDB(DWS) management console.
  2. Choose Clusters. All clusters are displayed by default.
  3. In the Operation column of the target cluster, choose More > Redistribute, as shown in the following figure.

    +

    +

  4. On the Redistribute page that is displayed, keep the default offline redistribution mode and click Next: Confirm to submit the task.

    +

    +

    +

+

Online Redistribution

Precautions

+

In online redistribution mode, the database supports partial DDL and DCL operations.

+ + +

Procedure

+
+
  1. Log in to the GaussDB(DWS) management console.
  2. Choose Clusters. All clusters are displayed by default.
  3. In the Operation column of the target cluster, choose More > Redistribute, as shown in the following figure.

    +

    +

  4. On the Redistribute page that is displayed, set Advanced to Custom, set the redistribution mode to Online, and click Next: Confirm to submit the task.

    +

    +

    +

+
+
+
+
Parent topic: Cluster Redistribution
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_8202.html b/docs/dws/umn/dws_01_8202.html new file mode 100644 index 00000000..23851264 --- /dev/null +++ b/docs/dws/umn/dws_01_8202.html @@ -0,0 +1,31 @@ + + +

Viewing Redistribution Details

+

On the View Redistribution Details page, you can view the redistribution mode and progress of the current cluster. In offline scheduling mode, you can pause, resume, and modify redistribution, and perform retries upon failures.

+
  • This function is supported in 8.1.1.200 or later.
+
+

Precautions

+ +

Procedure

+
  1. Log in to the GaussDB(DWS) management console.
  2. Choose Clusters. All clusters are displayed by default.
  3. In the Operation column of the target cluster, choose More > View Redistribution Details, as shown in the following figure.

    +
    • In offline redistribution or online redistribution mode, only data progress and table progress are displayed.

      +
    +

    If redistribution fails, click Retry, as shown in the following figure.

    +

    +

    +
    +

+
+
+
+
Parent topic: Cluster Redistribution
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_01_index.html b/docs/dws/umn/dws_01_index.html new file mode 100644 index 00000000..9a891675 --- /dev/null +++ b/docs/dws/umn/dws_01_index.html @@ -0,0 +1,29 @@ + + +

Service Overview

+
+
+ +
+ diff --git a/docs/dws/umn/dws_03_0001.html b/docs/dws/umn/dws_03_0001.html new file mode 100644 index 00000000..ea96018c --- /dev/null +++ b/docs/dws/umn/dws_03_0001.html @@ -0,0 +1,41 @@ + + +

General Problems

+
+
+ + +
+
Parent topic: FAQs
+
+
+ diff --git a/docs/dws/umn/dws_03_0003.html b/docs/dws/umn/dws_03_0003.html new file mode 100644 index 00000000..f9d30212 --- /dev/null +++ b/docs/dws/umn/dws_03_0003.html @@ -0,0 +1,20 @@ + + +

Why Are Data Warehouses Necessary?

+

Status Quo and Requirements

Much data (orders, stocks, materials, and payments) is generated in the business operation systems and background (transactional) database of enterprises.

+
+

Decision makers categorize and analyze the data for business decision-making.

+

Difficulties

Data categorization and analysis involve the concurrent access to the data in multiple database tables. That is, multiple tables being updated by different transactions may be locked at the same time, which may cause complications to the database systems during peak hours.

+
+ +

Solution

Data warehouses excel in data aggregation and association, so users mine more data, get more information, and make better decisions. The mining requires complex queries that involve data on multiple tables.

+

The ETL process copies data in business operation databases to data warehouses for analysis and computing. Data can be aggregated from multiple business operation systems into one data warehouse for better association, analysis, and actionable insights.

+
+

Data warehouses and standard transaction-oriented databases such as Oracle, Microsoft SQL Server, and MySQL use different design modes. Data warehouses are optimized in terms of data aggregation and association but the transaction or data adding and deleting functions or performance may not be guaranteed. Therefore, data warehouses and databases apply to different scenarios. Transactional databases are dedicated to transaction processing (business operation of enterprises) whereas data warehouses excel at complex data analysis. In conclusion, databases apply to data updates whereas data warehouses apply to data analysis.

+
+
+
+
Parent topic: General Problems
+
+
+ diff --git a/docs/dws/umn/dws_03_0005.html b/docs/dws/umn/dws_03_0005.html new file mode 100644 index 00000000..4626943e --- /dev/null +++ b/docs/dws/umn/dws_03_0005.html @@ -0,0 +1,81 @@ + + +

What Are the Differences Between a Data Warehouse and the Hadoop Big Data Platform?

+

The Hadoop big data platform can be regarded as a next-generation data warehousing system. It has the characteristics of modern data warehouses and is widely used by enterprises. Because of the scalability of MPP, the MPP-based data warehousing system is sometimes classified as a big data platform.

+

However, data warehouses greatly differ from the Hadoop platform in function and user experience in different scenarios. For details, see the following table.

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 Feature comparison between data warehouses and the Hadoop big data platform

Feature

+

Hadoop

+

Data Warehouse

+

Number of compute nodes

+

1000s

+

Max 256

+

Data volume

+

Over 10 PB

+

Max 10 PB

+

Data type

+

Relational, semi-relational, unstructured (voice, images, and video)

+

Relational only

+

Latency

+

Medium to high

+

Low

+

Application ecosystem

+

Innovative/AI

+

Traditional/BI

+

Application development API

+

SQL and other programming language APIs, such as MapReduce

+

Standard database SQL

+

Scalability

+

Unlimited, with comprehensive programming APIs

+

Limited, supported by UDFs

+

Transaction support

+

Limited

+

Comprehensive

+
+
+

Data warehouses and the Hadoop platform work together in different scenarios. GaussDB(DWS) on the public cloud can seamlessly integrate with Hadoop-based MRS on the public cloud to provide the SQL-over-Hadoop data sharing across platforms and services. GaussDB(DWS) serves as a data warehouse for managing massive data while relishing the openness, convenience, and innovation of the Hadoop platform. You can also enjoy the upper-layer applications of conventional data warehouses, especially BI applications, using GaussDB(DWS).

+
+
+
+
Parent topic: General Problems
+
+
+ diff --git a/docs/dws/umn/dws_03_0006.html b/docs/dws/umn/dws_03_0006.html new file mode 100644 index 00000000..3cc66163 --- /dev/null +++ b/docs/dws/umn/dws_03_0006.html @@ -0,0 +1,14 @@ + + +

Why Should I Use Public Cloud GaussDB(DWS)?

+

Conventional data warehouses are not practical for smaller enterprises due to high cost, time-consuming device and system selection and procurement, and complex scale-out.

+

GaussDB(DWS) on the public cloud is the better choice:

+ +
+
+
+
Parent topic: General Problems
+
+
+ diff --git a/docs/dws/umn/dws_03_0009.html b/docs/dws/umn/dws_03_0009.html new file mode 100644 index 00000000..ea3029f6 --- /dev/null +++ b/docs/dws/umn/dws_03_0009.html @@ -0,0 +1,74 @@ + + +

Should I Choose Public Cloud GaussDB(DWS) or RDS?

+

Both allow you to run conventional relational databases on the cloud and transfer database management loads. RDS databases are useful for OLTP, reporting, and analysis, but are less capable of handling read operations of a large amount of data (complex read-only queries). GaussDB(DWS) is useful for OLAP by reducing analysis and report workloads of large data sets by an order of magnitude, thanks to its multi-node scale and resources and optimized algorithms (column storage, vectorized executors, and distributed frameworks).

+

You can scale out a GaussDB(DWS) cluster to address complex data and queries, or to handle overwhelming analysis and report workloads that affect OLTP performance.

+

The following table shows the comparison between OLTP and OLAP.

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 Feature comparison between OLTP and OLAP

Feature

+

RDS for OLTP

+

GaussDB(DWS) for OLAP

+

User

+

Operations and low-level management

+

Decision-makers and senior management

+

Function

+

Daily operation processing

+

Analysis and decision-making

+

Design

+

By application

+

By theme

+

Data

+

Latest, detailed, two-dimensional, discrete

+

Historical, integrated, multidimensional, unified

+

Access

+

Dozens of read and write records

+

Millions of read records

+

Coverage

+

Simple read/write operations

+

Complex queries

+

Database size

+

Hundreds of GB

+

TB or PB

+
+
+
+
+
+
Parent topic: General Problems
+
+
+ diff --git a/docs/dws/umn/dws_03_0010.html b/docs/dws/umn/dws_03_0010.html new file mode 100644 index 00000000..89af1ae2 --- /dev/null +++ b/docs/dws/umn/dws_03_0010.html @@ -0,0 +1,13 @@ + + +

When Should I Use GaussDB(DWS) and MRS?

+

MRS works better with big data processing frameworks such as Apache Spark, Hadoop, and HBase, to process and analyze ultra-large data sets through custom code. It allows you to control cluster configurations and software installed in the cluster.

+

GaussDB(DWS) works better with complex queries of a large amount of structured data. It aims to pool data from different sources together, such as inventory, finance, and retail system. To ensure consistency and accuracy of enterprise reports, GaussDB(DWS) stores data in a highly structured manner. This structure can directly build the data consistency rule to the database table. Additionally, GaussDB(DWS) is highly compatible with standard SQL statements and the syntax of conventional transaction-supported databases.

+

GaussDB(DWS) is preferred when you want to perform complex query of a large amount of structured data with high performance.

+
+
+
+
Parent topic: General Problems
+
+
+ diff --git a/docs/dws/umn/dws_03_0011.html b/docs/dws/umn/dws_03_0011.html new file mode 100644 index 00000000..1c00f108 --- /dev/null +++ b/docs/dws/umn/dws_03_0011.html @@ -0,0 +1,14 @@ + + +

Can GaussDB(DWS) SQL on OBS Replace MRS?

+

No. Although SQL on OBS of GaussDB(DWS) can be used for GaussDB(DWS) and OBS data query, it cannot replace the processing frameworks of MRS.

+

Apart from SQL query, MRS also provides other functions. Public cloud MRS is a hosting service. It helps you use the latest common big data processing frameworks, such as Spark, Hadoop, and HBase, to process and analyze big data sets on a customizable cluster. With public cloud MRS, you can run a wide variety of scale-out data processing tasks for applications such as machine learning, graph analytics, data transformation, and stream data. GaussDB(DWS) SQL on OBS works with MRS. If you have already use MRS to process large-size data storage, GaussDB(DWS) SQL on OBS can be used to query these data without affecting MRS tasks.

+

In this case, the query service, data warehouses, and complex data processing frameworks play their own roles – simply select the appropriate tool for the task.

+

+
+
+
+
Parent topic: General Problems
+
+
+ diff --git a/docs/dws/umn/dws_03_0014.html b/docs/dws/umn/dws_03_0014.html new file mode 100644 index 00000000..5132876a --- /dev/null +++ b/docs/dws/umn/dws_03_0014.html @@ -0,0 +1,22 @@ + + +

What Should I Do If I Cannot Connect to a Data Warehouse Cluster?

+

Troubleshooting

Check:

+ +

If cluster connection failed on the public cloud, check the following items:

+ +

If cluster connection failed through the Internet, confirm the following items:

+ +
+

Technical Support

Call the Customer Hotline for support.

+

Telephone:

+

Germany: 0800 330 44 44

+

International: +800 44556600

+
+
+
+
+
Parent topic: Database Connections
+
+
+ diff --git a/docs/dws/umn/dws_03_0016.html b/docs/dws/umn/dws_03_0016.html new file mode 100644 index 00000000..d29b9bb4 --- /dev/null +++ b/docs/dws/umn/dws_03_0016.html @@ -0,0 +1,17 @@ + + +

What Do I Do If Creating a GaussDB(DWS) Cluster Failed?

+

Troubleshooting

Check that you have enough quota for creating the cluster.

+
+

Technical Support

Call the Customer Hotline for support.

+

Telephone:

+

Germany: 0800 330 44 44

+

International: +800 44556600

+
+
+
+
+
Parent topic: Cluster Management
+
+
+ diff --git a/docs/dws/umn/dws_03_0017.html b/docs/dws/umn/dws_03_0017.html new file mode 100644 index 00000000..90b04a2e --- /dev/null +++ b/docs/dws/umn/dws_03_0017.html @@ -0,0 +1,16 @@ + + +

Does GaussDB(DWS) Support Third-Party Clients and JDBC and ODBC Drivers?

+

Yes, but GaussDB(DWS) clients and drivers are recommended. Unlike open-source PostgreSQL clients and drivers, GaussDB(DWS) clients and drivers have two key advantages:

+ +

GaussDB(DWS) supports open-source PostgreSQL clients and JDBC and ODBC drivers.

+

The compatible client and driver versions are:

+ +

For details about how to use JDBC/ODBC to connect to GaussDB(DWS), see Tutorial: Development Using JDBC or ODBC.

+
+
+
+
Parent topic: Database Connections
+
+
+ diff --git a/docs/dws/umn/dws_03_0018.html b/docs/dws/umn/dws_03_0018.html new file mode 100644 index 00000000..139d0eb3 --- /dev/null +++ b/docs/dws/umn/dws_03_0018.html @@ -0,0 +1,13 @@ + + +

What Are the Differences Between Data Formats Supported by OBS and GDS Foreign Tables?

+

The file formats supported by OBS and GDS foreign tables are as follows:

+

OBS file formats: CSV, TEXT, ORC, and CARBONDATA. The default format is TEXT.

+

GDS file formats: CSV and TEXT. The default format is TEXT.

+
+
+
+
Parent topic: Data Import and Export
+
+
+ diff --git a/docs/dws/umn/dws_03_0022.html b/docs/dws/umn/dws_03_0022.html new file mode 100644 index 00000000..8f57507b --- /dev/null +++ b/docs/dws/umn/dws_03_0022.html @@ -0,0 +1,24 @@ + + +

Is My Data Secure in GaussDB(DWS)?

+

Yes. In the big data era, data has become a core asset. The public cloud will adhere to the commitment made over the years that we do not touch your applications or data, helping you protect your core assets. This is our commitment to users and the society, laying the foundation for the business success of the public cloud and their partners.

+

GaussDB(DWS) is a data warehousing system with telecom-class security to safeguard your data and privacy. Moreover, the public cloud GaussDB(DWS) delivers carrier-class quality, which can satisfy data security and privacy requirements of governments, financial organizations, and carriers. Therefore, it is widely used by various industries. GaussDB(DWS) of the public cloud won the following security authentication:

+ +

Service Data Security

GaussDB(DWS) is built on public cloud software infrastructure, including ECS and OBS.

+
+

Service data of GaussDB(DWS) users is stored in the ECSs in the cluster. Neither users nor public cloud O&M administrators can log in to the ECSs.

+

The operating system of ECSs is hardened for security, including kernel hardening, installation of the latest patch, permission control, port management, and protocol and port anti-attack.

+

GaussDB(DWS) provides complete security measures, such as password policies, authentication, session management, user permissions management, and database audit.

+

Snapshot Data Security

GaussDB(DWS) backups are snapshots stored in OBS. OBS supports access permission control, key access, and data encryption features. GaussDB(DWS) snapshot data can be used for data backup and restoration only and cannot be accessed by any user. GaussDB(DWS) administrators can view the OBS space occupied by snapshot data on the GaussDB(DWS) console and public cloud bills.

+
+

Network Access Security

GaussDB(DWS) is fully isolated between the layer-2 and layer-3 networks to fulfill security requirements of government and financial users.

+ +
+ +
+
+
+
Parent topic: General Problems
+
+
+ diff --git a/docs/dws/umn/dws_03_0023.html b/docs/dws/umn/dws_03_0023.html new file mode 100644 index 00000000..32da1b35 --- /dev/null +++ b/docs/dws/umn/dws_03_0023.html @@ -0,0 +1,12 @@ + + +

How Is GaussDB(DWS) Secured?

+

GaussDB(DWS) uses IAM and VPC to control user access and isolate cluster network. Cluster access is over SSL and cipher suite. Additionally, GaussDB(DWS) supports two-way digital certificate authentication.

+

Node OSs in each cluster are hardened to allow valid access to only OS files.

+
+
+
+
Parent topic: General Problems
+
+
+ diff --git a/docs/dws/umn/dws_03_0024.html b/docs/dws/umn/dws_03_0024.html new file mode 100644 index 00000000..9d5cdf3b --- /dev/null +++ b/docs/dws/umn/dws_03_0024.html @@ -0,0 +1,28 @@ + + +

Database Connections

+

+
+
+ + +
+
Parent topic: FAQs
+
+
+ diff --git a/docs/dws/umn/dws_03_0025.html b/docs/dws/umn/dws_03_0025.html new file mode 100644 index 00000000..e887d5bd --- /dev/null +++ b/docs/dws/umn/dws_03_0025.html @@ -0,0 +1,22 @@ + + +

Why Was I Not Notified of Failure Unbinding the EIP When GaussDB(DWS) Is Connected Over the Internet?

+

After the EIP is unbound, the network may be disconnected. However, the TCP layer does not detect a faulty physical connection in time due to keepalive settings. As a result, the gsql, ODBC, and JDBC clients also cannot identify the network fault in time.

+

The duration when the database sends the disconnection message to the client depends on the keepalive settings. The specific algorithm for calculating the duration is:

+

keepalive_time + keepalive_probes x keepalive_intvl

+

Keepalive values affect network communication stability. Adjust them to service pressure and network conditions.

+

On Linux, run the sysctl command to modify the following parameters:

+ +

For example, if you want to change the value of net.ipv4.tcp_keepalive_time, run the following command to change it to 120.

+

sysctl net.ipv4.tcp_keepalive_time=120

+

On Windows, modify the following configuration information in registry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters:

+ +

If you cannot find the preceding parameters in registry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters, add these parameters. Open Registry Editor, right-click the blank area on the right, and choose Create > DWORD (32-bit) Value to add these parameters.

+
+
+
+
+
Parent topic: Database Connections
+
+
+ diff --git a/docs/dws/umn/dws_03_0026.html b/docs/dws/umn/dws_03_0026.html new file mode 100644 index 00000000..1f8ac5ae --- /dev/null +++ b/docs/dws/umn/dws_03_0026.html @@ -0,0 +1,27 @@ + + +

Data Import and Export

+
+
+ + +
+
Parent topic: FAQs
+
+
+ diff --git a/docs/dws/umn/dws_03_0027.html b/docs/dws/umn/dws_03_0027.html new file mode 100644 index 00000000..9407e81b --- /dev/null +++ b/docs/dws/umn/dws_03_0027.html @@ -0,0 +1,19 @@ + + +

How Can I Import Data to GaussDB(DWS)?

+

GaussDB(DWS) supports efficient data import from multiple data sources. The following lists typical data import modes. For details, see "Import Modes" in the Data Warehouse Service (DWS) Developer Guide.

+ + + + +
+
+
+
Parent topic: Data Import and Export
+
+
+ diff --git a/docs/dws/umn/dws_03_0028.html b/docs/dws/umn/dws_03_0028.html new file mode 100644 index 00000000..c83b1a08 --- /dev/null +++ b/docs/dws/umn/dws_03_0028.html @@ -0,0 +1,13 @@ + + +

How Much Service Data Can a Data Warehouse Store?

+

Each node in a data warehouse cluster has a default storage capacity of 160 GB, 256 GB, 1.6 TB, 1.8 TB, or 13 TB. A cluster can house 3 to 32 nodes and the total storage capacity of the cluster expands proportionally as the cluster scale grows.

+

To enhance reliability, each node has a copy, which occupies half of the storage space.

+

The GaussDB(DWS) system backs up data and generates indexes, temporary cache files, and run logs, which occupy storage space. Therefore, the actual storage space of each node is about half of the total storage capacity.

+
+
+
+
Parent topic: Data Import and Export
+
+
+ diff --git a/docs/dws/umn/dws_03_0029.html b/docs/dws/umn/dws_03_0029.html new file mode 100644 index 00000000..53d71bf2 --- /dev/null +++ b/docs/dws/umn/dws_03_0029.html @@ -0,0 +1,25 @@ + + +

Cluster Management

+
+
+ + +
+
Parent topic: FAQs
+
+
+ diff --git a/docs/dws/umn/dws_03_0031.html b/docs/dws/umn/dws_03_0031.html new file mode 100644 index 00000000..46281b57 --- /dev/null +++ b/docs/dws/umn/dws_03_0031.html @@ -0,0 +1,27 @@ + + +

How Can I Upgrade or Downgrade GaussDB(DWS)?

+

Cluster patching or upgrading is automatic because GaussDB(DWS) upgrades its own version.

+

For service patch:

+ +

For service upgrade:

+ +

Downgrade is not supported.

+

The following figure describes the database version.

+

+
  • During service patch, the last digit of database version X.X.X is changed, for example, the database is upgraded from 1.1.0 to 1.1.1.
  • During service upgrade, the first two digits of database version X.X.X are changed, for example, the database is upgraded from 1.1.0 to 1.2.0.
+
+
+
+
+
Parent topic: Cluster Management
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_03_0033.html b/docs/dws/umn/dws_03_0033.html new file mode 100644 index 00000000..202d722e --- /dev/null +++ b/docs/dws/umn/dws_03_0033.html @@ -0,0 +1,23 @@ + + +

How Can I Clear and Reclaim Storage?

+

After you delete data stored in GaussDB(DWS) data warehouses, dirty data may be generated from the unreleased disk space. This results in space waste and deteriorates snapshot creation and restoration performance. The following describes the impact on the system:

+ +

Perform the following steps to clear and reclaim the storage space:

+
  1. Connect to the database. For details, see Cluster Connection.
  2. Run the following command to clear and reclaim the storage space:

    VACUUM FULL;

    +

    By default, tables the current user has the permission on are deleted. Other tables are skipped.

    +

    The following information is displayed once the space is cleared:

    +
    1
    VACUUM
+
    + +
    +
    • VACUUM FULL reclaims all expired row space, however it requires an exclusive lock on each table being processed, and might take a long time to complete on large, distributed database tables. You are advised to do VACUUM FULL to specified tables. If you want to do VACUUM FULL to the entire database, you are advised to do it during database maintenance.
    • The statistical information will be lost if you use the FULL parameter. To collect the statistics, add keyword ANALYZE, for example, VACUUM FULL ANALYZE;. For more information about VACUUM, see "SQL Reference > SQL Syntax > VACUUM" in the Data Warehouse Service (DWS) Developer Guide.
    +
    +
+
+
+
+
Parent topic: Cluster Management
+
+
+ diff --git a/docs/dws/umn/dws_03_0034.html b/docs/dws/umn/dws_03_0034.html new file mode 100644 index 00000000..7ae38ab0 --- /dev/null +++ b/docs/dws/umn/dws_03_0034.html @@ -0,0 +1,11 @@ + + +

What Is the User Quota?

+

For cloud services, quotas limit the number of resources available to users. If you need more, submit a service ticket to increase your quotas. Once approved, we will update your resource quota accordingly and send you a notification.

+
+
+
+
Parent topic: General Problems
+
+
+ diff --git a/docs/dws/umn/dws_03_0035.html b/docs/dws/umn/dws_03_0035.html new file mode 100644 index 00000000..b849422e --- /dev/null +++ b/docs/dws/umn/dws_03_0035.html @@ -0,0 +1,19 @@ + + +

Database Performance

+
+
+ + +
+
Parent topic: FAQs
+
+
+ diff --git a/docs/dws/umn/dws_03_0036.html b/docs/dws/umn/dws_03_0036.html new file mode 100644 index 00000000..c766617b --- /dev/null +++ b/docs/dws/umn/dws_03_0036.html @@ -0,0 +1,15 @@ + + +

Why Does GaussDB(DWS) Perform Worse Than a Single-Server Database in Extreme Scenarios?

+

Due to the MPP architecture limitation of GaussDB(DWS), a few PostgreSQL methods and functions cannot be pushed to DNs for execution. As a result, performance bottlenecks occur on CNs.

+

Explanation:

+ +

Solutions:

+ +
+
+
+
Parent topic: Database Performance
+
+
+ diff --git a/docs/dws/umn/dws_03_0037.html b/docs/dws/umn/dws_03_0037.html new file mode 100644 index 00000000..c30ab9da --- /dev/null +++ b/docs/dws/umn/dws_03_0037.html @@ -0,0 +1,13 @@ + + +

What Are the Differences Between GaussDB(DWS) and Hive in Functions?

+

GaussDB(DWS) and Hive have different functions in the following aspects:

+
  1. Hive is a data warehouse based on Hadoop MapReduce. GaussDB(DWS) is a data warehouse based on Postgres MPP.
  2. Hive data is stored on HDFS. GaussDB(DWS) data can be stored locally or on OBS in foreign table form.
  3. Hive does not support indexes. GaussDB(DWS) supports indexes, so querying is faster.
  4. Hive does not support stored procedures. GaussDB(DWS) does, so it has more extensive application scenarios.
  5. Hive supports fewer SQL statements than GaussDB(DWS), including functions, customized functions, and stored procedures.
  6. Hive does not support transactions. GaussDB(DWS) supports complete transactions.
  7. Both Hive and GaussDB(DWS) support backups, so the reliability is the same.
  8. GaussDB(DWS) delivers much better performance than Hive.
+

Based on their respective functions, Hive is useful for offline analysis while GaussDB(DWS) is useful for both online analysis and ad-hoc query.

+
+
+
+
Parent topic: General Problems
+
+
+ diff --git a/docs/dws/umn/dws_03_0040.html b/docs/dws/umn/dws_03_0040.html new file mode 100644 index 00000000..f952982d --- /dev/null +++ b/docs/dws/umn/dws_03_0040.html @@ -0,0 +1,11 @@ + + +

Can I Connect to GaussDB(DWS) Cluster Nodes Using SSH?

+

No, direct access is not supported. VMs at the bottom layer of GaussDB(DWS) serve as the compute nodes for data analysis. Access cluster databases using the private or public network access address instead.

+
+
+
+
Parent topic: Database Connections
+
+
+ diff --git a/docs/dws/umn/dws_03_0052.html b/docs/dws/umn/dws_03_0052.html new file mode 100644 index 00000000..625a79ff --- /dev/null +++ b/docs/dws/umn/dws_03_0052.html @@ -0,0 +1,23 @@ + + +

Regions and AZs

+

Concepts

A region and availability zone (AZ) identify the location of a data center. You can create resources in regions and AZs.

+ +

Figure 1 shows the relationship between regions and AZs.

+
Figure 1 Regions and AZs
+
+

How Do I Select a Region?

You are advised to select a region close to you or your target users. This reduces network latency and improves access rate.

+
+

How Do I Select an AZ?

Consider your requirements for DR and network latency when selecting an AZ:

+ +
+

Regions and Endpoints

When you use resources with API calls, you must specify the regional endpoint. For details about public cloud regions and endpoints, see "Regions and Endpoints".

+
+

+
+
+
+
Parent topic: General Problems
+
+
+ diff --git a/docs/dws/umn/dws_03_0053.html b/docs/dws/umn/dws_03_0053.html new file mode 100644 index 00000000..586a0c7c --- /dev/null +++ b/docs/dws/umn/dws_03_0053.html @@ -0,0 +1,13 @@ + + +

Can I Modify the Security Group of a GaussDB(DWS) Cluster?

+

Yes. When a data warehouse cluster is created, its security group cannot be changed. However, you can add, delete, or modify rules of the current security group.

+

To edit the cluster security group:

+
  1. Log in to the GaussDB(DWS) management console.
  2. In the navigation pane on the left, click Clusters.
  3. In the cluster list, find the target cluster and click the cluster name. The Basic Information page is displayed.
  4. Locate the Security Group parameter and click the security group name to switch to the Security Groups page on the VPC console, on which you can set the security group.
+
+
+
+
Parent topic: General Problems
+
+
+ diff --git a/docs/dws/umn/dws_03_0054.html b/docs/dws/umn/dws_03_0054.html new file mode 100644 index 00000000..85af7d48 --- /dev/null +++ b/docs/dws/umn/dws_03_0054.html @@ -0,0 +1,16 @@ + + +

Why Did the Used Storage Reduce After Scale-out?

+

Possible Causes

If you do not run VACUUM to clear and reclaim the storage space before the scale-out, the data deleted from GaussDB(DWS) may not free up the occupied disk space.

+

During the scale-out, the system redistributes the data because the service data volume on the original nodes is significantly larger than that on the newly added nodes. When the redistribution starts, the system automatically performs VACUUM to free up the storage space. In this way, the used storage is reduced.

+
+

Handling Procedure

You are advised to periodically clear and reclaim the storage space by running VACUUM FULL to prevent data expansion.

+

If the used storage space is still large after you run VACUUM FULL, analyze whether the existing cluster flavor meets service requirements. If no, scale out the cluster.

+
+
+
+
+
Parent topic: Cluster Management
+
+
+ diff --git a/docs/dws/umn/dws_03_0061.html b/docs/dws/umn/dws_03_0061.html new file mode 100644 index 00000000..04da92b4 --- /dev/null +++ b/docs/dws/umn/dws_03_0061.html @@ -0,0 +1,25 @@ + + +

FAQs

+
+
+ +
+ diff --git a/docs/dws/umn/dws_03_0064.html b/docs/dws/umn/dws_03_0064.html new file mode 100644 index 00000000..90c491c7 --- /dev/null +++ b/docs/dws/umn/dws_03_0064.html @@ -0,0 +1,14 @@ + + +

What Are Partitioned Tables, Partitions, and Partition Keys?

+

Partitioned table: Partitioning refers to splitting what is logically one large table into smaller physical pieces based on specific schemes. The table based on the logic is called a partitioned table, and a physical piece is called a partition. Data is stored on these smaller physical pieces, namely, partitions, instead of the larger logical partitioned table.

+

Partition: In the GaussDB(DWS) distributed system, data partitioning is to horizontally partition table data within a node based on a specified policy. The table is divided into partitions that do not overlap within a specific range.

+

Partition key: A partition key is an ordered set of one or more table columns. The values in the table partition keys are used to determine the data partition that a row belongs to.

+

+
+
+
+
Parent topic: Database Usage
+
+
+ diff --git a/docs/dws/umn/dws_03_0065.html b/docs/dws/umn/dws_03_0065.html new file mode 100644 index 00000000..8fc3ab39 --- /dev/null +++ b/docs/dws/umn/dws_03_0065.html @@ -0,0 +1,33 @@ + + +

Database Usage

+
+
+ + +
+
Parent topic: FAQs
+
+
+ diff --git a/docs/dws/umn/dws_03_0067.html b/docs/dws/umn/dws_03_0067.html new file mode 100644 index 00000000..e0d936f7 --- /dev/null +++ b/docs/dws/umn/dws_03_0067.html @@ -0,0 +1,26 @@ + + +

What Are the Differences Between Users and Roles?

+
Users and roles are shared within the entire cluster, but their data is not shared. That is, a user can connect to any database, but after the connection is successful, any user can access only the database declared in the connection request. +
+

The permissions provided by Gauss(DWS) include the O&M permissions for components on the management plane. You can assign different permissions to users as needed. The management plane uses roles for better permissions management. You can select specified permissions and assign them to roles in a unified manner. In this way, permissions can be viewed and managed in a centralized manner.

+

The following figure shows the relationships between permissions, roles, and users in unified permissions management.

+

+

GaussDB(DWS) provides various permissions. Select and assign permissions to different users based on service scenarios. A role can be assigned one or more permissions.

+

After a role is granted to a user through GRANT, the user will have all the permissions of the role. It is recommended that roles be used to efficiently grant permissions. A user has permissions only for their own tables, but does not have permissions for other users' tables in their schemas.

+ +
+
+
+
Parent topic: General Problems
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_03_0068.html b/docs/dws/umn/dws_03_0068.html new file mode 100644 index 00000000..09aa9be0 --- /dev/null +++ b/docs/dws/umn/dws_03_0068.html @@ -0,0 +1,15 @@ + + +

Logs

+
+
+ + +
+
Parent topic: FAQs
+
+
+ diff --git a/docs/dws/umn/dws_03_0071.html b/docs/dws/umn/dws_03_0071.html new file mode 100644 index 00000000..d1f4f992 --- /dev/null +++ b/docs/dws/umn/dws_03_0071.html @@ -0,0 +1,18 @@ + + +

Why Is SQL Execution Slow After Long GaussDB(DWS) Usage?

+

When a database is used for a period of time, the table data increases as services grow, or the table data is frequently added, deleted, or modified. This results in bloating tables and inaccurate statistics, deteriorating database performance.

+

You are advised to periodically perform VACUUM FULL and ANALYZE on tables that are frequently added, deleted, or modified.

+
  1. By default, 100 out of 30,000 records of statistics are collected. When a large amount of data is involved, the SQL execution is unstable, which may be caused by a changed execution plan. In this case, the sampling rate needs to be adjusted for statistics. You can run set default_statistics_target to increase the sampling rate, which helps the optimizer generate the optimal plan.

    +

  2. Perform ANALYZE again. For details, see "ANALYZE | ANALYSE" in the Developer Guide.

    +

+

To test whether disk fragments affect database performance, use the following function:

+
select * from pgxc_get_stat_dirty_tables(30,100000);
+
+
+
+
+
Parent topic: Database Performance
+
+
+ diff --git a/docs/dws/umn/dws_03_0073.html b/docs/dws/umn/dws_03_0073.html new file mode 100644 index 00000000..4857a588 --- /dev/null +++ b/docs/dws/umn/dws_03_0073.html @@ -0,0 +1,16 @@ + + +

How Do I Use \Copy to Import and Export Data?

+

GaussDB(DWS) is a fully managed service on the cloud. Users cannot log in to the background to import or export data by using COPY, so the COPY syntax is disabled. You are advised to store data files on OBS and use OBS foreign tables to import data. If you want to use COPY to import and export data, perform the following operations:

+
  1. Place the data file on the client.
  2. Use gsql to connect to the target cluster.
  3. Run the following command to import data. Enter the directory name and file name of the data file on the client and specify the import option in with. The command is almost the same as the common COPY command. You only need to add a backslash (\) before the command. When the data is successfully imported, no notification will be displayed.
    \copy table_name from '/directory_name/file_name' with(...);
    +
  4. Run the following command to export data to a local file. Retain the default settings of parameters.
    \copy table_name to '/directory_name/file_name';
    +
  5. Specify the copy_option parameter to export data to a CSV file.
    \copy table_name to '/directory_name/file_name' CSV;
    +
  6. Use with to specify parameters, exporting data as CSV files that use vertical bars (|) as delimiters.
    \copy table_name to '/directory_name/file_name' with(format 'csv',delimiter '|') ;
    +
+
+
+
+
Parent topic: Data Import and Export
+
+
+ diff --git a/docs/dws/umn/dws_03_0074.html b/docs/dws/umn/dws_03_0074.html new file mode 100644 index 00000000..cbeb0835 --- /dev/null +++ b/docs/dws/umn/dws_03_0074.html @@ -0,0 +1,12 @@ + + +

How Do I Import GaussDB(DWS)/Oracle/MySQL/SQL Server Data to GaussDB(DWS) (Whole Database Migration)?

+

To import heterogeneous data to GaussDB(DWS), use CDM to migrate the entire MySQL or SQL Server database. Or migrate the entire GaussDB(DWS) database to another GaussDB(DWS) database. For details, see "Entire DB Migration" in the Cloud Data Migration User Guide.

+

Alternatively, you can store data in OBS and then dump the data to GaussDB(DWS). For details, see "About Parallel Data Import from OBS" in the Data Warehouse Service (DWS) Developer Guide.

+
+
+
+
Parent topic: Data Import and Export
+
+
+ diff --git a/docs/dws/umn/dws_03_0075.html b/docs/dws/umn/dws_03_0075.html new file mode 100644 index 00000000..9ae3b7f9 --- /dev/null +++ b/docs/dws/umn/dws_03_0075.html @@ -0,0 +1,11 @@ + + +

Do I Need to Set a Distribution Key After Setting a Primary Key?

+

No, you only need to set the primary key. By default, the first column of the primary key is selected as the distribution key. If both are set, the primary key must contain the distribution key.

+
+
+
+
Parent topic: Database Usage
+
+
+ diff --git a/docs/dws/umn/dws_03_0076.html b/docs/dws/umn/dws_03_0076.html new file mode 100644 index 00000000..3662bd7f --- /dev/null +++ b/docs/dws/umn/dws_03_0076.html @@ -0,0 +1,12 @@ + + +

Is GaussDB(DWS) Compatible with PostgreSQL Stored Procedures?

+

Yes.

+

GaussDB(DWS) is compatible with PostgreSQL stored procedures. For details, see "Stored Procedures" in the Developer Guide.

+
+
+
+
Parent topic: Database Usage
+
+
+ diff --git a/docs/dws/umn/dws_03_0078.html b/docs/dws/umn/dws_03_0078.html new file mode 100644 index 00000000..7dc5a5c1 --- /dev/null +++ b/docs/dws/umn/dws_03_0078.html @@ -0,0 +1,16 @@ + + +

How Can I Export the Table Structure?

+

You are advised to use the Data Studio graphical client to export table data. You can export data from:

+ +

For details, see "Exporting Table Data" in the Tool Guide.

+

+

+

+
+
+
+
Parent topic: Database Usage
+
+
+ diff --git a/docs/dws/umn/dws_03_0079.html b/docs/dws/umn/dws_03_0079.html new file mode 100644 index 00000000..cb743fd0 --- /dev/null +++ b/docs/dws/umn/dws_03_0079.html @@ -0,0 +1,15 @@ + + +

How Can I Export All Tables and Views from a Database?

+

You can use pg_tables and pg_views to query all table information and views in a database. Example:

+
SELECT * FROM pg_tables;
+SELECT * FROM pg_views;
+

+

For details about the returned columns, see "PG_TABLES" and "PG_VIEWS" in the Developer Guide.

+
+
+
+
Parent topic: Database Usage
+
+
+ diff --git a/docs/dws/umn/dws_03_0082.html b/docs/dws/umn/dws_03_0082.html new file mode 100644 index 00000000..c9ca5bc1 --- /dev/null +++ b/docs/dws/umn/dws_03_0082.html @@ -0,0 +1,14 @@ + + +

How Can I View Database Operation Logs?

+

GaussDB(DWS) allows you to record the audit logs of specific operations, involving audit log retention policies, unauthorized access, as well as DML, DDL, SELECT and COPY operations performed on stored procedures and database objects.

+

After configuring audit logs, you can query audit information to troubleshoot, or historical operation records for a malfunctioning GaussDB(DWS) cluster.

+

The audit logs are stored in the database by default. Dump them to OBS to give users who are responsible for monitoring the database easier access.

+

For details, see "Audit Logs" in the Management Guide.

+
+
+
+
Parent topic: Logs
+
+
+ diff --git a/docs/dws/umn/dws_03_0085.html b/docs/dws/umn/dws_03_0085.html new file mode 100644 index 00000000..e9db0d6b --- /dev/null +++ b/docs/dws/umn/dws_03_0085.html @@ -0,0 +1,43 @@ + + +

How Can I Change the Character Encoding Format of a Database?

+

In GaussDB(DWS), the encoding format of a database cannot be changed. You need to create another database in the required format. For globalization purposes, set the encoding to UTF8 when creating a database.

+

Syntax

1
+2
+3
+4
+5
+6
+7
+8
CREATE DATABASE database_name
+    [ [ WITH ] { [ OWNER [=] user_name ] |
+               [ TEMPLATE [=] template ] |
+               [ ENCODING [=] encoding ] |
+               [ LC_COLLATE [=] lc_collate ] |
+               [ LC_CTYPE [=] lc_ctype ] |
+               [ DBCOMPATIBILITY [=] compatibility_type ] |
+               [ CONNECTION LIMIT [=] connlimit ]}[...] ];
+
+ +
+
+ +

Example

To create a UTF8 database music that can be modified later. (The encoding of the local environment must also be UTF8.)

+
CREATE DATABASE music ENCODING 'UTF8' template = template0;
+
+
+
+
+
Parent topic: Database Usage
+
+
+ diff --git a/docs/dws/umn/dws_03_0088.html b/docs/dws/umn/dws_03_0088.html new file mode 100644 index 00000000..f8dbf334 --- /dev/null +++ b/docs/dws/umn/dws_03_0088.html @@ -0,0 +1,93 @@ + + +

How Can I Delete Table Data Efficiently?

+

Yes. TRUNCATE is more efficient than DELETE for deleting massive data.

+

For details, see "TRUNCATE" in the Data Warehouse Service (DWS) Developer Guide.

+

Function

TRUNCATE quickly removes all rows from a database table.

+

It has the same effect as the unconditional DELETE, but TRUNCATE is faster, especially for large tables, because it does not scan tables.

+
+

Features

+
+

Example

1
+2
+3
+4
+5
--Create a table.CREATE TABLE tpcds.reason_t1 AS TABLE tpcds.reason;
+
+--Truncate the table.TRUNCATE TABLE tpcds.reason_t1;
+
+--Drop the table.DROP TABLE tpcds.reason_t1;
+
+ +
+
 1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+19
+20
+21
+22
+23
+24
+25
+26
+27
+28
+29
--Create a partitioned table.
+CREATE TABLE tpcds.reason_p
+(
+  r_reason_sk integer,
+  r_reason_id character(16),
+  r_reason_desc character(100)
+)PARTITION BY RANGE (r_reason_sk)
+(
+  partition p_05_before values less than (05),
+  partition p_15 values less than (15),
+  partition p_25 values less than (25),
+  partition p_35 values less than (35),
+  partition p_45_after values less than (MAXVALUE)
+);
+
+--Insert data.
+INSERT INTO tpcds.reason_p SELECT * FROM tpcds.reason;
+
+--Truncate the p_05_before partition.
+ALTER TABLE tpcds.reason_p TRUNCATE PARTITION p_05_before;
+
+--Truncate the p_15 partition.
+ALTER TABLE tpcds.reason_p TRUNCATE PARTITION for (13);
+
+--Truncate the partitioned table.
+TRUNCATE TABLE tpcds.reason_p;
+
+--Drop the table.
+DROP TABLE tpcds.reason_p;
+
+ +
+

+
+
+
+
+
Parent topic: Database Usage
+
+
+ diff --git a/docs/dws/umn/dws_03_0089.html b/docs/dws/umn/dws_03_0089.html new file mode 100644 index 00000000..8eb2d62f --- /dev/null +++ b/docs/dws/umn/dws_03_0089.html @@ -0,0 +1,24 @@ + + +

Do I Need to Run VACUUM FULL and ANALYZE on Common Tables Periodically?

+

Yes. For tables that involve frequent add, delete, or modify operations, perform VACUUM FULL and ANALYZE to reclaim the disk space occupied by updated or deleted data, preventing performance deterioration caused by data expansion and inaccurate statistics.

+

Generally, you are advised to use ANALYZE after multiple add and modify operations are performed on a table, and use VACUUM FULL after delete operations are performed. VACUUM FULL can be used only on special occasions, such as when you want to physically narrow a table to decrease the occupied disk space after deleting most rows of the table. VACUUM FULL usually shrinks a table more than VACUUM does.

+

Syntax

-- Perform ANALYZE on a table.
+ANALYZE Table name;
+-- Perform ANALYZE on all tables (non-foreign tables) in the database.
+ANALYZE;
+-- Perform VACUUM on a table.
+VACUUM Table name;
+-- -- Perform VACUUM FULL on a table.
+VACUUM FULL Table_name;
+

For details, see in "VACUUM" and "ANALYZE | ANALYSE" in the Developer Guide.

+

If the physical space usage does not decrease after you run the VACUUM FULL command, check whether there were other active transactions (started before you delete data transactions and not ended before you run VACUUM FULL). If yes, run this command again when the transactions have finished.

+
+
+
+
+
+
Parent topic: Database Usage
+
+
+ diff --git a/docs/dws/umn/dws_03_0090.html b/docs/dws/umn/dws_03_0090.html new file mode 100644 index 00000000..d02bfa5c --- /dev/null +++ b/docs/dws/umn/dws_03_0090.html @@ -0,0 +1,12 @@ + + +

How Is the Disk Space or Capacity of GaussDB(DWS) Calculated?

+

A cluster with three data nodes of 320 GB each has a total capacity of 960 GB. When 1 GB data is stored, GaussDB(DWS) stores 1 GB data on two nodes due to duplication, a security mechanism, thereby occupying a total of 2 GB space. As a result, more than 2 GB space is occupied if metadata and indexes are calculated. Therefore, a three-node cluster with a total capacity of 960 GB can store 480 GB data. This mechanism ensures data security.

+

When you create nodes on the console, you are billed by the available capacity of a node. For example, the actual space of dws.m3.xlarge is 320 GB and the available space displayed is 160 GB, the space you will be billed for.

+
+
+
+
Parent topic: Cluster Management
+
+
+ diff --git a/docs/dws/umn/dws_03_0092.html b/docs/dws/umn/dws_03_0092.html new file mode 100644 index 00000000..d37a985f --- /dev/null +++ b/docs/dws/umn/dws_03_0092.html @@ -0,0 +1,14 @@ + + +

How Do I Change My Expired Database Password?

+

To change the password of the database administrator dbadmin, log in to the console and choose More > Reset Password in cluster row.

+

For security, the following two parameters manage account passwords. Log in to the console, click the cluster name and switch to the parameter modification page to modify the parameters.

+ +
+
+
+
Parent topic: Account, Password, and Permissions
+
+
+ diff --git a/docs/dws/umn/dws_03_0095.html b/docs/dws/umn/dws_03_0095.html new file mode 100644 index 00000000..f984f538 --- /dev/null +++ b/docs/dws/umn/dws_03_0095.html @@ -0,0 +1,27 @@ + + +

How Do I View All Database Users and Their Permissions?

+
+
+
+
+
Parent topic: Account, Password, and Permissions
+
+
+ diff --git a/docs/dws/umn/dws_03_0100.html b/docs/dws/umn/dws_03_0100.html new file mode 100644 index 00000000..339dc8f8 --- /dev/null +++ b/docs/dws/umn/dws_03_0100.html @@ -0,0 +1,12 @@ + + +

How Can I View SQL Execution Records of A Certain Period When Service Read and Write Are Blocked?

+

The top SQL feature lets you view SQL statements executed in a specified period (in real time and historical). SQL statements of the current CN or all CNs are available for viewing.

+ +
+
+
+
Parent topic: Database Performance
+
+
+ diff --git a/docs/dws/umn/dws_03_0102.html b/docs/dws/umn/dws_03_0102.html new file mode 100644 index 00000000..a37dac1e --- /dev/null +++ b/docs/dws/umn/dws_03_0102.html @@ -0,0 +1,11 @@ + + +

Can I Export GaussDB(DWS) Data from/to OBS Across Regions?

+

No, GaussDB(DWS) does not support OBS data import or export across regions. The GaussDB(DWS) cluster and OBS must be in the same region.

+
+
+
+
Parent topic: Data Import and Export
+
+
+ diff --git a/docs/dws/umn/dws_03_0104.html b/docs/dws/umn/dws_03_0104.html new file mode 100644 index 00000000..43457f56 --- /dev/null +++ b/docs/dws/umn/dws_03_0104.html @@ -0,0 +1,12 @@ + + +

How Do I View Node Metrics (CPU, Memory, and Disk Usage)?

+

You can view the used capacity of a cluster CPU, memory, and disks on the Cloud Eye management console. Perform the following steps to view the information:

+
  1. Log in to the GaussDB(DWS) console and click Viewing Metric next to a cluster.
  2. Click to return to the Cloud Service Monitoring page. On the Data Warehouse Node page, and click View Metric on the right of the corresponding node to view its disk usage.
+
+
+
+
Parent topic: Cluster Management
+
+
+ diff --git a/docs/dws/umn/dws_03_0105.html b/docs/dws/umn/dws_03_0105.html new file mode 100644 index 00000000..dcff1c94 --- /dev/null +++ b/docs/dws/umn/dws_03_0105.html @@ -0,0 +1,11 @@ + + +

Can I Import Data over the Public/External Network Using GDS?

+

No. The GDS server and GaussDB(DWS) can only communicate with each other on the intranet. Each DN in the GaussDB(DWS) cluster is used to connect to the GDS server in parallel to import a large amount of data. The GDS server and the cluster must be in the same network. If GDS is deployed on an offline server, the firewall needs to be enabled and the cluster needs an EIP. However, one cluster can be bound only to one EIP, and data import with multiple DNs cannot be implemented.

+
+
+
+
Parent topic: Data Import and Export
+
+
+ diff --git a/docs/dws/umn/dws_03_0110.html b/docs/dws/umn/dws_03_0110.html new file mode 100644 index 00000000..19e9be21 --- /dev/null +++ b/docs/dws/umn/dws_03_0110.html @@ -0,0 +1,27 @@ + + + +

Account, Password, and Permissions

+ +

+
+ +
+ + +
+
Parent topic: FAQs
+
+
+ diff --git a/docs/dws/umn/dws_03_0169.html b/docs/dws/umn/dws_03_0169.html new file mode 100644 index 00000000..629c6f23 --- /dev/null +++ b/docs/dws/umn/dws_03_0169.html @@ -0,0 +1,12 @@ + + +

How Can a Data Warehouse and a Database in Different AZs of the Same Region Communicate?

+

Resources in different AZs of the same region can communicate with each other directly if they belong to the same VPC.

+

For resources in different AZs of the same region but not in the same VPC, create a VPC peering connection. .

+
+
+
+
Parent topic: Database Connections
+
+
+ diff --git a/docs/dws/umn/dws_03_0195.html b/docs/dws/umn/dws_03_0195.html new file mode 100644 index 00000000..febb5722 --- /dev/null +++ b/docs/dws/umn/dws_03_0195.html @@ -0,0 +1,36 @@ + + +

How Do I Revoke the CONNECT ON DATABASE Permission from a User?

+

GaussDB(DWS) provides an implicitly defined group public that contains all roles. By default, all new users and roles have the permissions of public. To revoke permissions of public from a user or role, or re-grant these permissions to them, add the public keyword in the REVOKE or GRANT statement.

+

GaussDB(DWS) grants the permissions for objects of certain types to public. By default, permissions on tables, columns, sequences, foreign data sources, foreign servers, schemas, and tablespaces are not granted to PUBLIC, but the following permissions are granted to PUBLIC: CONNECT and CREATE TEMP TABLE permissions on databases, EXECUTE permission on functions, and USAGE permission on languages and data types (including domains). An object owner can revoke the default permissions granted to public and grant permissions to other users. For security purposes, create an object and set its permissions in the same transaction so that other users do not have time windows to use the object. In addition, you can run the ALTER DEFAULT PRIVILEGES statement to modify the default permissions.

+

The following shows an example of revoking the CONNECT ON DATABASE permission from a user.

+
  1. Connect to the default database gaussdb of a GaussDB(DWS) cluster.

    gsql -d gaussdb -h 192.168.0.89 -U dbadmin -p 8000 -r
    +

    If the following information is displayed after you enter the password as prompted, the connection is successful.

    +
    1
    gaussdb=>
+
    + +
    +

  2. Create user u1.

    CREATE USER u1 IDENTIFIED BY 'password';
+CREATE USER
    +

  3. Check whether access of u1 is normal.

    gsql -d gaussdb -h 192.168.0.89 -U u1 -p 8000 -W password -r
+gsql ((GaussDB 8.1.0 build be03b9a0) compiled at 2021-03-12 14:18:02 commit 1237 last mr 2001 release)
+SSL connection (protocol: TLSv1.3, cipher: TLS_AES_128_GCM_SHA256, bits: 128)
+Type "help" for help.
    +

  4. Revoke the CONNECT ON DATABASE permission from public.

    gsql -d gaussdb -h 192.168.0.89 -U dbadmin -p 8000 -r
+gaussdb=>
+
+REVOKE CONNECT ON database gaussdb FROM public;
+REVOKE
    +

    revoke connect on database postgres from u1 cannot be used directly because the CONNECT permission is granted to public.

    +
    +

  5. Verify the result. If the following information is displayed, the CONNECT ON DATABASE permission has been revoked from user u1.

    gsql -d gaussdb -h 192.168.0.89 -U u1 -p 8000
+gsql: FATAL:  permission denied for database "gaussdb"
+DETAIL:  User does not have CONNECT privilege.
    +

+
+
+
+
Parent topic: Account, Password, and Permissions
+
+
+ diff --git a/docs/dws/umn/dws_03_0196.html b/docs/dws/umn/dws_03_0196.html new file mode 100644 index 00000000..b8b9695b --- /dev/null +++ b/docs/dws/umn/dws_03_0196.html @@ -0,0 +1,81 @@ + + +

How Do I Grant Schema Permissions to a User?

+

This section describes how to grant the query permission for a schema as an example. For more information, see "How Do I Grant Table Permissions to a User?" in FAQ. You can grant:

+ +

Assume that there are users u1 and u2, and two schemas named after them. User u2 needs to access tables in schema u1.

+

+

+
  1. Connect to your database as dbadmin. Run the following statements to create users u1 and u2. Two schemas will be created and named after the users by default.

    1
+2
    CREATE USER u1 PASSWORD '{password}';
+CREATE USER u2 PASSWORD '{password}';
+
    + +
    +

  2. Create tables u1.t1 and u1.t2 in schema u1.

    1
+2
    CREATE TABLE u1.t1 (c1 int, c2 int);
+CREATE TABLE u1.t2 (c1 int, c2 int);
+
    + +
    +

  3. Grant the access permission of schema u1 to user u2.

    1
    GRANT USAGE ON SCHEMA u1 TO u2;
+
    + +
    +

  4. Grant user u2 the permission to query table u1.t1 in schema u1.

    1
    GRANT SELECT ON u1.t1 TO u2;
+
    + +
    +

  5. Start a new session and connect to the database as user u2 Verify that user u2 can query the u1.t1 table but not the u1.t2 table.

    1
+2
    SELECT * FROM u1.t1;
+SELECT * FROM u1.t2;
+
    + +
    +

    +

  6. In the session started by user dbadmin, grant user u2 the permission to query all the tables in schema u1.

    1
    GRANT SELECT ON ALL TABLES IN SCHEMA u1 TO u2;
+
    + +
    +

  7. In the session started by user u2, verify that u2 can query all tables.

    1
+2
    SELECT * FROM u1.t1;
+SELECT * FROM u1.t2;
+
    + +
    +

    +

  8. In the session started by user dbadmin, create table u1.t3.

    1
    CREATE TABLE u1.t3 (c1 int, c2 int);
+
    + +
    +

  9. In the session started by user u2, verify that user u2 does not have the query permission for u1.t3. It indicates that user u2 has the permission to access all the existing tables in schema u1, but not the tables to be created in the future.

    1
    SELECT * FROM u1.t3;
+
    + +
    +

    +

  10. In the session started by user dbadmin, grant user u2 the permission to query the tables to be created in schema u1. Create table u1.t4.

    1
+2
    ALTER DEFAULT PRIVILEGES FOR ROLE u1 IN SCHEMA u1 GRANT SELECT ON TABLES TO u2;
+CREATE TABLE u1.t4 (c1 int, c2 int);
+
    + +
    +

  11. In the session started by user u2, verify that user u2 can access table u1.t4, but does not have the permission to access u1.t3. To let the user access table u1.t3, you can grant permissions by performing 4.

    1
    SELECT * FROM u1.t4;
+
    + +
    +

    +

+
+
+
+
Parent topic: Account, Password, and Permissions
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_03_0197.html b/docs/dws/umn/dws_03_0197.html new file mode 100644 index 00000000..6767db1c --- /dev/null +++ b/docs/dws/umn/dws_03_0197.html @@ -0,0 +1,234 @@ + + +

How Do I Grant Table Permissions to a User?

+

This section describes how to grant users the SELECT, INSERT, UPDATE, or full permissions for tables.

+

Syntax

1
+2
+3
+4
+5
+6
GRANT { { SELECT | INSERT | UPDATE | DELETE | TRUNCATE | REFERENCES | TRIGGER | ANALYZE | ANALYSE } [, ...] 
+      | ALL [ PRIVILEGES ] }
+    ON { [ TABLE ] table_name [, ...]
+       | ALL TABLES IN SCHEMA schema_name [, ...] }
+    TO { [ GROUP ] role_name | PUBLIC } [, ...] 
+    [ WITH GRANT OPTION ];
+
+ +
+
+

Scenario

Assume there are users u1, u2, u3, u4, and u5 and five schemas named after these users. Their permission requirements are as follows:

+ +

+

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 Permissions of the u1.t1 table

User

+

Type

+

GRANT Statement

+

Query

+

Insert

+

Update

+

Delete

+

u1

+

Owner

+

-

+

√

+

√

+

√

+

√

+

u2

+

Read-only user

+
1
GRANT SELECT ON u1.t1 TO u2;
+
+ +
+

√

+

x

+

x

+

x

+

u3

+

INSERT user

+
1
GRANT INSERT ON u1.t1 TO u3;
+
+ +
+

x

+

√

+

x

+

x

+

u4

+

UPDATE user

+
1
GRANT SELECT,UPDATE ON u1.t1 TO u4;  
+
+ +
+
NOTICE:

The UPDATE permission must be granted together with the SELECT permission, or information leakage may occur.

+
+

√

+

x

+

√

+

x

+

u5

+

Super user

+
1
GRANT ALL PRIVILEGES ON u1.t1 TO u5;
+
+ +
+

√

+

√

+

√

+

√

+
+
+
+

Procedure

Perform the following steps to grant and verify permissions:

+
  1. Connect to your database as dbadmin. Run the following statements to create users u1 to u5. Five schemas will be created and named after the users by default.

    1
+2
+3
+4
+5
    CREATE USER u1 PASSWORD '{password}';
+CREATE USER u2 PASSWORD '{password}';
+CREATE USER u3 PASSWORD '{password}';
+CREATE USER u4 PASSWORD '{password}';
+CREATE USER u5 PASSWORD '{password}';
+
    + +
    +

  1. Create table u1.t1 in schema u1.

    1
    CREATE TABLE u1.t1 (c1 int, c2 int);
+
    + +
    +

  2. Insert two records to the table.

    1
+2
    INSERT INTO u1.t1 VALUES (1,2);
+INSERT INTO u1.t1 VALUES (1,2);
+
    + +
    +

  3. Grant schema permissions to users.

    1
    GRANT USAGE ON SCHEMA u1 TO u2,u3,u4,u5;
+
    + +
    +

  4. Grant user u2 the permission to query the u1.t1 table.

    1
    GRANT SELECT ON u1.t1 TO u2;
+
    + +
    +

  5. Start a new session and connect to the database as user u2. Verify that user u2 can query the u1.t1 table but cannot write to or modify the table.

    1
+2
+3
    SELECT * FROM u1.t1;
+INSERT INTO u1.t1 VALUES (1,20);
+UPDATE u1.t1 SET c2 = 3 WHERE c1 =1;
+
    + +
    +

    +

  6. In the session started by user dbadmin, grant permissions to users u3, u4, and u5.

    1
+2
+3
    GRANT INSERT ON u1.t1 TO u3; -- Allow u3 to insert data.
+GRANT SELECT,UPDATE ON u1.t1 TO u4; -- Allow u4 to modify the table.
+GRANT ALL PRIVILEGES ON u1.t1 TO u5; -- Allow u5 to query, insert, modify, and delete table data.
+
    + +
    +

  7. Start a new session and connect to the database as user u3. Verify that user u3 can query the u1.t1 table but cannot query or modify the table.

    1
+2
+3
    SELECT * FROM u1.t1;
+INSERT INTO u1.t1 VALUES (1,20);
+UPDATE u1.t1 SET c2 = 3 WHERE c1 =1;
+
    + +
    +

    +

  8. Start a new session and connect to the database as user u4. Verify that user u4 can modify and query the u1.t1 table, but cannot insert data to the table.

    1
+2
+3
    SELECT * FROM u1.t1;
+INSERT INTO u1.t1 VALUES (1,20);
+UPDATE u1.t1 SET c2 = 3 WHERE c1 =1;
+
    + +
    +

    +

  9. Start a new session and connect to the database as user u5. Verify that user u4 can query, insert, modify, and delete data in the u1.t1 table.

    1
+2
+3
+4
    SELECT * FROM u1.t1;
+INSERT INTO u1.t1 VALUES (1,20);
+UPDATE u1.t1 SET c2 = 3 WHERE c1 =1;
+DELETE FROM u1.t1;
+
    + +
    +

    +

  10. In the session started by user dbadmin, execute the has_table_privilege function to query user permissions.

    1
    SELECT * FROM pg_class WHERE relname = 't1';
+
    + +
    +

    Check the relacl column in the command output. rolename=xxxx/yyyy indicates that rolename has the xxxx permission on the table and the permission is obtained from yyyy.

    +

    The following figure shows the command output.

    +

    +
    • u1=arwdDxtA/u1 indicates that u1 is the owner and has full permissions.
    • u2=r/u1 indicates that u2 has the read permission.
    • u3=a/u1 indicates that u3 has the insert permission.
    • u4=rw/u1 indicates that u4 has the read and update permissions.
    • u5=arwdDxtA/u1 indicates that u5 has full permissions.
    +

+
+
+
+
+
Parent topic: Account, Password, and Permissions
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_03_2121.html b/docs/dws/umn/dws_03_2121.html new file mode 100644 index 00000000..469338fe --- /dev/null +++ b/docs/dws/umn/dws_03_2121.html @@ -0,0 +1,118 @@ + + +

What Is a Database/Data Warehouse/Data Lake/Lakehouse?

+

The evolving Internet and IoT produce massive volumes of data. This data needs to be managed, using concepts like database, data warehouse, data lake, and lakehouse. Here is an overview of how they map with our products and solutions.

+

Database

A database is where data is organized, stored, and managed by data structure.

+

Databases have been used in computers since the 1960s, with the two prevailing data models (hierarchical and network), and data and applications were very interdependent. This limited database applications.

+

A database usually refers to a relational database. A relational database organizes data with a relational model, that is, data is stored in rows and columns. Therefore, database data is well-structured and independent with low redundancy. In 1970, relational databases were born to completely separate data from applications for software and have become an indispensable part of mainstream computer systems. Relational databases are the foundation of database products from all vendors, with relational API support even if a database is non-relational.

+

Relational databases process basic and routine transactions using OLTP, such as bank transactions.

+
+

Data Warehouse

Database growth has facilitated data growth. OLAP explores the relationship between data and mines more data value. However, it is difficult to share data between different databases, and data integration and analysis also face great challenges.

+

To overcome these challenges for enterprises, Bill Inmon, proposed the idea of data warehousing in 1990. The data warehouse runs on a unique storage architecture to perform OLAP on a large amount of the OLTP data accumulated over the years. In this way, enterprises can obtain valuable information from massive data quickly and effectively to make informed decisions. Thanks to data warehouses, the information industry has evolved from operational systems based on relational databases to decision support systems.

+

Unlike a database, a data warehouse has the following features:

+ + +
+ + + + + + + + + + + + + + + + + + + + + +
Table 1 Comparison between data warehouses and databases

Dimension

+

Data Warehouse

+

Database

+

Application scenario

+

OLAP

+

OLTP

+

Data source

+

Multiple

+

Single

+

Data normalization

+

Denormalized schemas

+

Highly normalized static schemas

+

Data access

+

Optimized read operations

+

Optimized write operations

+
+
+
+

Data Lake

Data is an important asset for enterprises. Production and operations data are saved and distilled into effective management policies.

+

The data lake does that. It is a large data warehouse that centrally stores structured and unstructured data. It can store raw data of multiple data sources and types, meaning that data can be accessed, processed, analyzed, and transmitted without being structured first. The data lake helps enterprises quickly complete federated analysis of heterogeneous data sources and explore data value.

+
A data lake is in essence a solution that consists of a data storage architecture and data processing tools.
  • The storage architecture must be scalable and reliable enough to store massive data of any type (structured, semi-structured, unstructured data).
  • The two types of processing tools have separate functions:
    • The first type: migrates data into the lake, including defining sources, formulating synchronization policies, moving data, and compiling catalogs.
    • The second type then uses that data, including analyzing, mining, and using it. The data lake must be equipped with wide-ranging capabilities, such as comprehensive data and data lifecycle management, diversified data analytics, and secure data acquisition and release. These data governance tools help guarantee data quality, which can be compromised by a lack of metadata and turn the data lake into a data swamp.
    +
+
+

Now with big data and AI, lake data is even more valuable and plays new roles. It represents more enterprise capabilities. For example, the data lake can centralize data management, helping enterprises build more optimized operation models. It also provides other enterprise capabilities such as prediction analysis and recommendation models. These models can stimulate further growth.

+

Just like any other warehouse and lake, one stores goods, or data, from one source while the other stores water, or data, from many sources.

+ +
+ + + + + + + + + + + + + + + + + + + + + +
Table 2 Comparison between data lakes and data warehouses

Dimension

+

Data Lake

+

Data Warehouse

+

Application scenario

+

Exploratory analytics (machine learning, data discovery, profiling, prediction)

+

Data analytics (based on historical structured data)

+

Cost

+

Low initial cost, high subsequent cost

+

High initial cost, low subsequent cost

+

Data quality

+

Massive raw data to be cleaned and normalized before use

+

High quality data that can be used as the basis of facts

+

Target user

+

Data scientists and data developers

+

Business analysts

+
+
+
+

Lakehouse

Although the application scenarios and architectures of a data warehouse and a data lake are different, they can cooperate to resolve problems. A data warehouse stores structured data and is ideal for quick BI and decision-making support, while a data lake stores data in any format and can generate larger value by mining data. Therefore, their convergence can bring more benefits to enterprises in some scenarios.

+

A lakehouse, the convergence of a data warehouse and a data lake, aims to enable data mobility and streamline construction. The key of the lakehouse architecture is to enable the free flow of data/metadata between the data warehouse and the data lake. The explicit-value data in the lake can flow to or even be directly used by the warehouse. The implicit-value data in the warehouse can also flow to the lake for long-term storage at a low cost and for future data mining.

+
+

Data Enablement Solution

Data Lake Governance Center (DGC) is a data enablement platform that helps large government agencies and companies customize intelligent data resource management solutions. This solution can import all-domain data into the data lake, eliminating data silos, unleashing the value of data, and empowering data-driven digital transformation.

+

DGC features the FusionInsight intelligent data lake as its core. Around it are computing engines such as the database, data warehouse, data lake, and data platform. DGC provides comprehensive data enablement, covering data collection, aggregation, computing, asset management, and data openness.

+

Lake, warehouse, and database engines enable agile data lake construction, fast migration of GaussDB databases, and real-time analysis of the data warehouse. For more information, go to:

+ +
+
+
+
+
Parent topic: General Problems
+
+
+ diff --git a/docs/dws/umn/dws_03_2124.html b/docs/dws/umn/dws_03_2124.html new file mode 100644 index 00000000..337f0288 --- /dev/null +++ b/docs/dws/umn/dws_03_2124.html @@ -0,0 +1,28 @@ + + +

How Do I View Foreign Table Information?

+

To query information about OBS/GDS foreign tables such as OBS paths, run the following statement:

+
1
select * from pg_get_tabledef('Foreign_table_name')
+
+ +
+

The following uses table traffic_data.GCJL_OBS as an example:

+
1
select * from pg_get_tabledef('traffic_data.GCJL_OBS');
+
+ +
+

+
+
+
+
Parent topic: Database Usage
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_03_2125.html b/docs/dws/umn/dws_03_2125.html new file mode 100644 index 00000000..3407dc2b --- /dev/null +++ b/docs/dws/umn/dws_03_2125.html @@ -0,0 +1,12 @@ + + +

Do I Need the Same VPC and Subnet to Connect to a GaussDB(DWS) Cluster?

+

If BI applications, client ECS, and DGC need to communicate with GaussDB(DWS), they must be in the same region and VPC as the GaussDB(DWS) cluster (different subnets are allowed).

+

In the same region, communication is allowed between different AZs in the same VPC. In the case of different VPCs, create a VPC peering connection to enable communication. For details, see .

+
+
+
+
Parent topic: Database Connections
+
+
+ diff --git a/docs/dws/umn/dws_03_2126.html b/docs/dws/umn/dws_03_2126.html new file mode 100644 index 00000000..e249faef --- /dev/null +++ b/docs/dws/umn/dws_03_2126.html @@ -0,0 +1,85 @@ + + +

How Do I Change Distribution Columns?

+

In a data warehouse database, you need to carefully choose distribution columns for large tables, because they can affect your database and query performance. If an improper distribution key is used, data skew may occur after data is imported. As a result, the usage of some disks will be much higher than that of other disks, and the cluster may even become read-only. If the hash distribution policy is used and data skew occurs, the I/O performance of some DNs will be poor, affecting the overall query performance. You also need to consider how to adjust the distribution column of existing tables to improve performance.

+

If the hash distribution policy is used, you need to check tables to ensure their data is evenly distributed on each DN. Generally, over 5% difference between the amount of data on different DNs is regarded as data skew. If the difference is over 10%, you have to choose another distribution column.

+

For tables that are not evenly distributed, adjust their distribution columns to reduce data skew and avoid database performance problems.

+

Choosing an Appropriate Distribution Column

The distribution column in a hash table must meet the following requirements, which are ranked by priority in descending order:

+ +
+

Procedure

Run the select version(); statement to query the current database version. Required performance varies according to the version.

+

+ +
  1. Use Data Studio or gsql in Linux to access the database.
  2. Create a table.

    In the following statements, table1 is the original table name and table1_new is the new table name. column1 and column2 are distribution column names.

    +
    +
    1
+2
+3
+4
    CREATE TABLE IF NOT EXISTS table1_new 
+( LIKE table1 INCLUDING ALL EXCLUDING DISTRIBUTION) 
+DISTRIBUTE BY 
+HASH (column1, column2);
+
    + +
    +
    +

  3. Migrate data to the new table.

    1
+2
+3
+4
    START TRANSACTION;
+LOCK TABLE table1 IN ACCESS EXCLUSIVE MODE;
+INSERT INTO table1_new SELECT * FROM table1;
+COMMIT;
+
    + +
    +

  4. Verify that the table data has been migrated. Delete the original table.

    1
+2
    SELECT COUNT(*) FROM table1_new;
+DROP TABLE table1;
+
    + +
    +

  5. Replace the original table.

    1
    ALTER TABLE table1_new RENAME TO table1;
+
    + +
    +

+

+ +
  1. Query the table definition. The command output shows that the distribution column of the table is c_last_name.

    1
    select pg_get_tabledef('customer_t1');
+
    + +
    +

    +

  2. Try updating data in the distribution column. An error message will be displayed.

    1
    update customer_t1 set c_last_name = 'Jimy' where c_customer_sk = 6885;
+
    + +
    +

    +

  3. Change the distribution column of the table to a column that cannot be updated, for example, c_customer_sk.

    1
    alter table customer_t1 DISTRIBUTE BY hash (c_customer_sk); 
+
    + +
    +

    +

  4. Update the data in the old distribution column.

    1
    update customer_t1 set c_last_name = 'Jimy' where c_customer_sk = 6885;
+
    + +
    +

    +

+

+
+
+
+
+
Parent topic: Database Usage
+
+
+ + + \ No newline at end of file diff --git a/docs/dws/umn/dws_03_2130.html b/docs/dws/umn/dws_03_2130.html new file mode 100644 index 00000000..e2c382d3 --- /dev/null +++ b/docs/dws/umn/dws_03_2130.html @@ -0,0 +1,14 @@ + + +

How Do I Configure a Whitelist to Protect Clusters Available Through a Public IP Address?

+

You can also log in to the VPC management console to manually create a security group. Then, go back to the page for creating data warehouse clusters, click the button next to the Security Group drop-down list to refresh the page, and select the new security group.

+

To enable the GaussDB(DWS) client to connect to the cluster, you need to add an inbound rule to the new security group to grant the access permission to the database port of the GaussDB(DWS) cluster.

+ +
+
+
+
Parent topic: Database Connections
+
+
+ diff --git a/docs/dws/umn/figure/en-us_image_0000001134400838.png b/docs/dws/umn/figure/en-us_image_0000001134400838.png new file mode 100644 index 00000000..19772623 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134400838.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134400850.png b/docs/dws/umn/figure/en-us_image_0000001134400850.png new file mode 100644 index 00000000..68ec1cab Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134400850.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134400854.png b/docs/dws/umn/figure/en-us_image_0000001134400854.png new file mode 100644 index 00000000..6428bc90 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134400854.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134400858.png b/docs/dws/umn/figure/en-us_image_0000001134400858.png new file mode 100644 index 00000000..7aab163a Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134400858.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134400860.png b/docs/dws/umn/figure/en-us_image_0000001134400860.png new file mode 100644 index 00000000..c409b8f0 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134400860.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134400862.png b/docs/dws/umn/figure/en-us_image_0000001134400862.png new file mode 100644 index 00000000..26e510b5 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134400862.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134400866.png b/docs/dws/umn/figure/en-us_image_0000001134400866.png new file mode 100644 index 00000000..30418561 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134400866.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134400890.png b/docs/dws/umn/figure/en-us_image_0000001134400890.png new file mode 100644 index 00000000..c51d0bdf Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134400890.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134400894.png b/docs/dws/umn/figure/en-us_image_0000001134400894.png new file mode 100644 index 00000000..1c6877ee Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134400894.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134400896.png b/docs/dws/umn/figure/en-us_image_0000001134400896.png new file mode 100644 index 00000000..fd4050c3 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134400896.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134400908.png b/docs/dws/umn/figure/en-us_image_0000001134400908.png new file mode 100644 index 00000000..2067ddaa Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134400908.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134400914.png b/docs/dws/umn/figure/en-us_image_0000001134400914.png new file mode 100644 index 00000000..ddeaef5e Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134400914.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134400944.png b/docs/dws/umn/figure/en-us_image_0000001134400944.png new file mode 100644 index 00000000..0c68b2ed Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134400944.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134400946.png b/docs/dws/umn/figure/en-us_image_0000001134400946.png new file mode 100644 index 00000000..a60b628e Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134400946.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134400948.png b/docs/dws/umn/figure/en-us_image_0000001134400948.png new file mode 100644 index 00000000..d6cb9501 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134400948.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134400952.png b/docs/dws/umn/figure/en-us_image_0000001134400952.png new file mode 100644 index 00000000..5080f5f1 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134400952.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134400956.png b/docs/dws/umn/figure/en-us_image_0000001134400956.png new file mode 100644 index 00000000..edc345fb Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134400956.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134400958.png b/docs/dws/umn/figure/en-us_image_0000001134400958.png new file mode 100644 index 00000000..c1a1e0e1 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134400958.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134400960.png b/docs/dws/umn/figure/en-us_image_0000001134400960.png new file mode 100644 index 00000000..e637770d Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134400960.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134400964.png b/docs/dws/umn/figure/en-us_image_0000001134400964.png new file mode 100644 index 00000000..705805d8 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134400964.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134400970.png b/docs/dws/umn/figure/en-us_image_0000001134400970.png new file mode 100644 index 00000000..1e6a3cce Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134400970.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134400974.png b/docs/dws/umn/figure/en-us_image_0000001134400974.png new file mode 100644 index 00000000..674253cf Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134400974.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134400976.png b/docs/dws/umn/figure/en-us_image_0000001134400976.png new file mode 100644 index 00000000..2b971aa7 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134400976.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134400982.png b/docs/dws/umn/figure/en-us_image_0000001134400982.png new file mode 100644 index 00000000..a3206320 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134400982.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134400986.png b/docs/dws/umn/figure/en-us_image_0000001134400986.png new file mode 100644 index 00000000..04cd407b Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134400986.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134401018.png b/docs/dws/umn/figure/en-us_image_0000001134401018.png new file mode 100644 index 00000000..47fc53c2 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134401018.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134401020.png b/docs/dws/umn/figure/en-us_image_0000001134401020.png new file mode 100644 index 00000000..fe768db6 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134401020.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134401044.png b/docs/dws/umn/figure/en-us_image_0000001134401044.png new file mode 100644 index 00000000..44d73e28 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134401044.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134401050.png b/docs/dws/umn/figure/en-us_image_0000001134401050.png new file mode 100644 index 00000000..4268e69a Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134401050.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134401052.png b/docs/dws/umn/figure/en-us_image_0000001134401052.png new file mode 100644 index 00000000..9207564c Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134401052.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134401054.png b/docs/dws/umn/figure/en-us_image_0000001134401054.png new file mode 100644 index 00000000..d1fbb55d Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134401054.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134401058.png b/docs/dws/umn/figure/en-us_image_0000001134401058.png new file mode 100644 index 00000000..576b463d Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134401058.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134401064.png b/docs/dws/umn/figure/en-us_image_0000001134401064.png new file mode 100644 index 00000000..dd1f4f14 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134401064.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134401066.png b/docs/dws/umn/figure/en-us_image_0000001134401066.png new file mode 100644 index 00000000..05b2d5f2 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134401066.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134401068.png b/docs/dws/umn/figure/en-us_image_0000001134401068.png new file mode 100644 index 00000000..576b463d Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134401068.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134401070.png b/docs/dws/umn/figure/en-us_image_0000001134401070.png new file mode 100644 index 00000000..6804261a Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134401070.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134401072.png b/docs/dws/umn/figure/en-us_image_0000001134401072.png new file mode 100644 index 00000000..c250d797 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134401072.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134401104.png b/docs/dws/umn/figure/en-us_image_0000001134401104.png new file mode 100644 index 00000000..5112fc97 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134401104.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134560618.png b/docs/dws/umn/figure/en-us_image_0000001134560618.png new file mode 100644 index 00000000..9dc8c016 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134560618.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134560646.png b/docs/dws/umn/figure/en-us_image_0000001134560646.png new file mode 100644 index 00000000..86e62c0f Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134560646.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134560650.png b/docs/dws/umn/figure/en-us_image_0000001134560650.png new file mode 100644 index 00000000..388294a9 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134560650.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134560668.png b/docs/dws/umn/figure/en-us_image_0000001134560668.png new file mode 100644 index 00000000..797ff2aa Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134560668.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134560676.png b/docs/dws/umn/figure/en-us_image_0000001134560676.png new file mode 100644 index 00000000..97ee9653 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134560676.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134560688.png b/docs/dws/umn/figure/en-us_image_0000001134560688.png new file mode 100644 index 00000000..cbce7843 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134560688.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134560694.png b/docs/dws/umn/figure/en-us_image_0000001134560694.png new file mode 100644 index 00000000..54b90243 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134560694.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134560708.png b/docs/dws/umn/figure/en-us_image_0000001134560708.png new file mode 100644 index 00000000..63809b6f Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134560708.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134560712.png b/docs/dws/umn/figure/en-us_image_0000001134560712.png new file mode 100644 index 00000000..4d14d4bb Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134560712.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134560726.png b/docs/dws/umn/figure/en-us_image_0000001134560726.png new file mode 100644 index 00000000..abc975e5 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134560726.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134560730.png b/docs/dws/umn/figure/en-us_image_0000001134560730.png new file mode 100644 index 00000000..c7ef9e09 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134560730.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134560732.png b/docs/dws/umn/figure/en-us_image_0000001134560732.png new file mode 100644 index 00000000..0359776c Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134560732.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134560752.png b/docs/dws/umn/figure/en-us_image_0000001134560752.png new file mode 100644 index 00000000..b835d7d0 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134560752.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134560756.jpg b/docs/dws/umn/figure/en-us_image_0000001134560756.jpg new file mode 100644 index 00000000..e8093cd9 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134560756.jpg differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134560768.png b/docs/dws/umn/figure/en-us_image_0000001134560768.png new file mode 100644 index 00000000..d47c9e5c Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134560768.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134560772.png b/docs/dws/umn/figure/en-us_image_0000001134560772.png new file mode 100644 index 00000000..42b300b9 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134560772.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134560774.png b/docs/dws/umn/figure/en-us_image_0000001134560774.png new file mode 100644 index 00000000..3baaeff5 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134560774.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134560782.png b/docs/dws/umn/figure/en-us_image_0000001134560782.png new file mode 100644 index 00000000..b28f0af2 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134560782.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134560786.png b/docs/dws/umn/figure/en-us_image_0000001134560786.png new file mode 100644 index 00000000..22fbfd45 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134560786.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134560798.png b/docs/dws/umn/figure/en-us_image_0000001134560798.png new file mode 100644 index 00000000..cf89baca Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134560798.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134560814.png b/docs/dws/umn/figure/en-us_image_0000001134560814.png new file mode 100644 index 00000000..9300f9ab Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134560814.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134560822.png b/docs/dws/umn/figure/en-us_image_0000001134560822.png new file mode 100644 index 00000000..f7a199ec Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134560822.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134560824.png b/docs/dws/umn/figure/en-us_image_0000001134560824.png new file mode 100644 index 00000000..bb1b050d Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134560824.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134560832.png b/docs/dws/umn/figure/en-us_image_0000001134560832.png new file mode 100644 index 00000000..77b64622 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134560832.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134560836.png b/docs/dws/umn/figure/en-us_image_0000001134560836.png new file mode 100644 index 00000000..9a2591ab Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134560836.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134560856.png b/docs/dws/umn/figure/en-us_image_0000001134560856.png new file mode 100644 index 00000000..9a2591ab Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134560856.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134560862.png b/docs/dws/umn/figure/en-us_image_0000001134560862.png new file mode 100644 index 00000000..aabf6851 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134560862.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134560868.png b/docs/dws/umn/figure/en-us_image_0000001134560868.png new file mode 100644 index 00000000..903e6c61 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134560868.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134560878.png b/docs/dws/umn/figure/en-us_image_0000001134560878.png new file mode 100644 index 00000000..67d257ad Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134560878.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001134560886.png b/docs/dws/umn/figure/en-us_image_0000001134560886.png new file mode 100644 index 00000000..929dfc64 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001134560886.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001135053258.png b/docs/dws/umn/figure/en-us_image_0000001135053258.png new file mode 100644 index 00000000..f8bc62ad Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001135053258.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001135053260.png b/docs/dws/umn/figure/en-us_image_0000001135053260.png new file mode 100644 index 00000000..e0dc7172 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001135053260.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001135053262.png b/docs/dws/umn/figure/en-us_image_0000001135053262.png new file mode 100644 index 00000000..1e53f279 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001135053262.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001135213036.png b/docs/dws/umn/figure/en-us_image_0000001135213036.png new file mode 100644 index 00000000..da04e091 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001135213036.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001142155952.png b/docs/dws/umn/figure/en-us_image_0000001142155952.png new file mode 100644 index 00000000..be144192 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001142155952.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001144332046.png b/docs/dws/umn/figure/en-us_image_0000001144332046.png new file mode 100644 index 00000000..aae07a1a Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001144332046.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001144332116.png b/docs/dws/umn/figure/en-us_image_0000001144332116.png new file mode 100644 index 00000000..b77bcbf9 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001144332116.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001144491744.png b/docs/dws/umn/figure/en-us_image_0000001144491744.png new file mode 100644 index 00000000..7aad4a8e Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001144491744.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001146626882.png b/docs/dws/umn/figure/en-us_image_0000001146626882.png new file mode 100644 index 00000000..eded3138 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001146626882.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001146786676.png b/docs/dws/umn/figure/en-us_image_0000001146786676.png new file mode 100644 index 00000000..91d93e2c Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001146786676.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001148353740.png b/docs/dws/umn/figure/en-us_image_0000001148353740.png new file mode 100644 index 00000000..ef070046 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001148353740.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001152588340.png b/docs/dws/umn/figure/en-us_image_0000001152588340.png new file mode 100644 index 00000000..7facb26e Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001152588340.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001152679414.png b/docs/dws/umn/figure/en-us_image_0000001152679414.png new file mode 100644 index 00000000..311ccf82 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001152679414.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001152680406.png b/docs/dws/umn/figure/en-us_image_0000001152680406.png new file mode 100644 index 00000000..57f45417 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001152680406.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001152687116.png b/docs/dws/umn/figure/en-us_image_0000001152687116.png new file mode 100644 index 00000000..90841e5f Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001152687116.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001152748072.png b/docs/dws/umn/figure/en-us_image_0000001152748072.png new file mode 100644 index 00000000..234a8f20 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001152748072.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001152771466.png b/docs/dws/umn/figure/en-us_image_0000001152771466.png new file mode 100644 index 00000000..5b233448 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001152771466.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001152832004.png b/docs/dws/umn/figure/en-us_image_0000001152832004.png new file mode 100644 index 00000000..34ca8afa Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001152832004.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001154106106.jpg b/docs/dws/umn/figure/en-us_image_0000001154106106.jpg new file mode 100644 index 00000000..fecff9f4 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001154106106.jpg differ diff --git a/docs/dws/umn/figure/en-us_image_0000001154420256.png b/docs/dws/umn/figure/en-us_image_0000001154420256.png new file mode 100644 index 00000000..ba296bb8 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001154420256.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001158679868.png b/docs/dws/umn/figure/en-us_image_0000001158679868.png new file mode 100644 index 00000000..a2ad27e5 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001158679868.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001158839852.png b/docs/dws/umn/figure/en-us_image_0000001158839852.png new file mode 100644 index 00000000..5dd1719f Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001158839852.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001158998406.png b/docs/dws/umn/figure/en-us_image_0000001158998406.png new file mode 100644 index 00000000..a6298779 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001158998406.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001159158350.png b/docs/dws/umn/figure/en-us_image_0000001159158350.png new file mode 100644 index 00000000..04c8c619 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001159158350.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001159474436.png b/docs/dws/umn/figure/en-us_image_0000001159474436.png new file mode 100644 index 00000000..8b6617a0 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001159474436.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001159800492.png b/docs/dws/umn/figure/en-us_image_0000001159800492.png new file mode 100644 index 00000000..e0158c36 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001159800492.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001161313142.png b/docs/dws/umn/figure/en-us_image_0000001161313142.png new file mode 100644 index 00000000..487a06e0 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001161313142.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001161314776.png b/docs/dws/umn/figure/en-us_image_0000001161314776.png new file mode 100644 index 00000000..94c3f163 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001161314776.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001161787646.png b/docs/dws/umn/figure/en-us_image_0000001161787646.png new file mode 100644 index 00000000..e0158c36 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001161787646.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001161788458.png b/docs/dws/umn/figure/en-us_image_0000001161788458.png new file mode 100644 index 00000000..621b8700 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001161788458.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001163636428.png b/docs/dws/umn/figure/en-us_image_0000001163636428.png new file mode 100644 index 00000000..4786d36d Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001163636428.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001165989868.png b/docs/dws/umn/figure/en-us_image_0000001165989868.png new file mode 100644 index 00000000..98d604f3 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001165989868.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001172481700.png b/docs/dws/umn/figure/en-us_image_0000001172481700.png new file mode 100644 index 00000000..0f2eae2f Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001172481700.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180320263.png b/docs/dws/umn/figure/en-us_image_0000001180320263.png new file mode 100644 index 00000000..1d440e5d Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180320263.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180320269.png b/docs/dws/umn/figure/en-us_image_0000001180320269.png new file mode 100644 index 00000000..9bd2b7a1 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180320269.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180320279.png b/docs/dws/umn/figure/en-us_image_0000001180320279.png new file mode 100644 index 00000000..021753a7 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180320279.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180320283.png b/docs/dws/umn/figure/en-us_image_0000001180320283.png new file mode 100644 index 00000000..6428bc90 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180320283.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180320287.png b/docs/dws/umn/figure/en-us_image_0000001180320287.png new file mode 100644 index 00000000..cf89baca Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180320287.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180320289.png b/docs/dws/umn/figure/en-us_image_0000001180320289.png new file mode 100644 index 00000000..b594b09b Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180320289.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180320293.png b/docs/dws/umn/figure/en-us_image_0000001180320293.png new file mode 100644 index 00000000..90e05ec2 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180320293.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180320297.png b/docs/dws/umn/figure/en-us_image_0000001180320297.png new file mode 100644 index 00000000..54b556a2 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180320297.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180320299.png b/docs/dws/umn/figure/en-us_image_0000001180320299.png new file mode 100644 index 00000000..31244496 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180320299.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180320321.png b/docs/dws/umn/figure/en-us_image_0000001180320321.png new file mode 100644 index 00000000..5a027d5b Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180320321.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180320323.png b/docs/dws/umn/figure/en-us_image_0000001180320323.png new file mode 100644 index 00000000..c7d8ec46 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180320323.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180320325.png b/docs/dws/umn/figure/en-us_image_0000001180320325.png new file mode 100644 index 00000000..503722e2 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180320325.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180320351.png b/docs/dws/umn/figure/en-us_image_0000001180320351.png new file mode 100644 index 00000000..e7af7e14 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180320351.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180320363.png b/docs/dws/umn/figure/en-us_image_0000001180320363.png new file mode 100644 index 00000000..a056c693 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180320363.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180320367.png b/docs/dws/umn/figure/en-us_image_0000001180320367.png new file mode 100644 index 00000000..cd0b130a Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180320367.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180320375.png b/docs/dws/umn/figure/en-us_image_0000001180320375.png new file mode 100644 index 00000000..16fd8a67 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180320375.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180320387.png b/docs/dws/umn/figure/en-us_image_0000001180320387.png new file mode 100644 index 00000000..80cddf3a Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180320387.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180320401.png b/docs/dws/umn/figure/en-us_image_0000001180320401.png new file mode 100644 index 00000000..fd34ff9b Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180320401.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180320405.png b/docs/dws/umn/figure/en-us_image_0000001180320405.png new file mode 100644 index 00000000..7360070a Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180320405.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180320417.png b/docs/dws/umn/figure/en-us_image_0000001180320417.png new file mode 100644 index 00000000..04ffbfd5 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180320417.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180320419.png b/docs/dws/umn/figure/en-us_image_0000001180320419.png new file mode 100644 index 00000000..86e8bfc2 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180320419.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180320421.png b/docs/dws/umn/figure/en-us_image_0000001180320421.png new file mode 100644 index 00000000..dd1f4f14 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180320421.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180320431.png b/docs/dws/umn/figure/en-us_image_0000001180320431.png new file mode 100644 index 00000000..d5a30502 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180320431.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180320461.png b/docs/dws/umn/figure/en-us_image_0000001180320461.png new file mode 100644 index 00000000..d4a04386 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180320461.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180320467.png b/docs/dws/umn/figure/en-us_image_0000001180320467.png new file mode 100644 index 00000000..c2cf7e68 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180320467.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180320473.png b/docs/dws/umn/figure/en-us_image_0000001180320473.png new file mode 100644 index 00000000..f9b04f1f Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180320473.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180320487.png b/docs/dws/umn/figure/en-us_image_0000001180320487.png new file mode 100644 index 00000000..9921fee6 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180320487.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180320497.png b/docs/dws/umn/figure/en-us_image_0000001180320497.png new file mode 100644 index 00000000..e82a32eb Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180320497.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180320503.png b/docs/dws/umn/figure/en-us_image_0000001180320503.png new file mode 100644 index 00000000..e82a32eb Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180320503.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180320505.png b/docs/dws/umn/figure/en-us_image_0000001180320505.png new file mode 100644 index 00000000..1cf17c2e Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180320505.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180320535.png b/docs/dws/umn/figure/en-us_image_0000001180320535.png new file mode 100644 index 00000000..713c118e Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180320535.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180440211.png b/docs/dws/umn/figure/en-us_image_0000001180440211.png new file mode 100644 index 00000000..1533e916 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180440211.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180440215.png b/docs/dws/umn/figure/en-us_image_0000001180440215.png new file mode 100644 index 00000000..3dde1f65 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180440215.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180440217.png b/docs/dws/umn/figure/en-us_image_0000001180440217.png new file mode 100644 index 00000000..ec1178a1 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180440217.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180440219.png b/docs/dws/umn/figure/en-us_image_0000001180440219.png new file mode 100644 index 00000000..a70756ff Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180440219.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180440221.png b/docs/dws/umn/figure/en-us_image_0000001180440221.png new file mode 100644 index 00000000..7a1053d3 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180440221.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180440227.jpg b/docs/dws/umn/figure/en-us_image_0000001180440227.jpg new file mode 100644 index 00000000..954a5253 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180440227.jpg differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180440229.png b/docs/dws/umn/figure/en-us_image_0000001180440229.png new file mode 100644 index 00000000..0c026641 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180440229.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180440233.png b/docs/dws/umn/figure/en-us_image_0000001180440233.png new file mode 100644 index 00000000..e5bd3bf2 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180440233.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180440255.png b/docs/dws/umn/figure/en-us_image_0000001180440255.png new file mode 100644 index 00000000..dc00327b Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180440255.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180440259.png b/docs/dws/umn/figure/en-us_image_0000001180440259.png new file mode 100644 index 00000000..a0166108 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180440259.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180440267.png b/docs/dws/umn/figure/en-us_image_0000001180440267.png new file mode 100644 index 00000000..72acf31d Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180440267.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180440271.png b/docs/dws/umn/figure/en-us_image_0000001180440271.png new file mode 100644 index 00000000..61d4b98f Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180440271.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180440273.png b/docs/dws/umn/figure/en-us_image_0000001180440273.png new file mode 100644 index 00000000..e7ac3ec3 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180440273.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180440275.png b/docs/dws/umn/figure/en-us_image_0000001180440275.png new file mode 100644 index 00000000..16e21062 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180440275.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180440277.png b/docs/dws/umn/figure/en-us_image_0000001180440277.png new file mode 100644 index 00000000..89b0296d Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180440277.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180440309.png b/docs/dws/umn/figure/en-us_image_0000001180440309.png new file mode 100644 index 00000000..fb6e0491 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180440309.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180440311.png b/docs/dws/umn/figure/en-us_image_0000001180440311.png new file mode 100644 index 00000000..e084c67f Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180440311.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180440313.png b/docs/dws/umn/figure/en-us_image_0000001180440313.png new file mode 100644 index 00000000..563163b5 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180440313.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180440315.png b/docs/dws/umn/figure/en-us_image_0000001180440315.png new file mode 100644 index 00000000..9297f878 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180440315.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180440323.png b/docs/dws/umn/figure/en-us_image_0000001180440323.png new file mode 100644 index 00000000..3722b824 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180440323.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180440325.jpg b/docs/dws/umn/figure/en-us_image_0000001180440325.jpg new file mode 100644 index 00000000..3441fd43 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180440325.jpg differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180440335.png b/docs/dws/umn/figure/en-us_image_0000001180440335.png new file mode 100644 index 00000000..6c39dbff Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180440335.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180440339.png b/docs/dws/umn/figure/en-us_image_0000001180440339.png new file mode 100644 index 00000000..0c4a0baf Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180440339.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180440341.png b/docs/dws/umn/figure/en-us_image_0000001180440341.png new file mode 100644 index 00000000..82de3473 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180440341.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180440353.png b/docs/dws/umn/figure/en-us_image_0000001180440353.png new file mode 100644 index 00000000..0acfb607 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180440353.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180440371.png b/docs/dws/umn/figure/en-us_image_0000001180440371.png new file mode 100644 index 00000000..016224c4 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180440371.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180440401.png b/docs/dws/umn/figure/en-us_image_0000001180440401.png new file mode 100644 index 00000000..ed8d5d4d Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180440401.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180440403.png b/docs/dws/umn/figure/en-us_image_0000001180440403.png new file mode 100644 index 00000000..4b964541 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180440403.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180440405.png b/docs/dws/umn/figure/en-us_image_0000001180440405.png new file mode 100644 index 00000000..5c5c71d8 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180440405.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180440407.png b/docs/dws/umn/figure/en-us_image_0000001180440407.png new file mode 100644 index 00000000..9921fee6 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180440407.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180440421.png b/docs/dws/umn/figure/en-us_image_0000001180440421.png new file mode 100644 index 00000000..08f2db81 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180440421.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180440423.png b/docs/dws/umn/figure/en-us_image_0000001180440423.png new file mode 100644 index 00000000..32bf2026 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180440423.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180440435.png b/docs/dws/umn/figure/en-us_image_0000001180440435.png new file mode 100644 index 00000000..d4acbfd5 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180440435.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180440437.png b/docs/dws/umn/figure/en-us_image_0000001180440437.png new file mode 100644 index 00000000..ec3ea9b3 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180440437.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180440439.png b/docs/dws/umn/figure/en-us_image_0000001180440439.png new file mode 100644 index 00000000..11c99ae3 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180440439.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180440441.jpg b/docs/dws/umn/figure/en-us_image_0000001180440441.jpg new file mode 100644 index 00000000..6f3d3394 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180440441.jpg differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180440467.png b/docs/dws/umn/figure/en-us_image_0000001180440467.png new file mode 100644 index 00000000..f835ae7f Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180440467.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001180440471.png b/docs/dws/umn/figure/en-us_image_0000001180440471.png new file mode 100644 index 00000000..1cbd8a19 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001180440471.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001181012661.png b/docs/dws/umn/figure/en-us_image_0000001181012661.png new file mode 100644 index 00000000..619398b0 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001181012661.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001181012665.jpg b/docs/dws/umn/figure/en-us_image_0000001181012665.jpg new file mode 100644 index 00000000..954a5253 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001181012665.jpg differ diff --git a/docs/dws/umn/figure/en-us_image_0000001181172585.png b/docs/dws/umn/figure/en-us_image_0000001181172585.png new file mode 100644 index 00000000..cf89baca Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001181172585.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001181172589.jpg b/docs/dws/umn/figure/en-us_image_0000001181172589.jpg new file mode 100644 index 00000000..954a5253 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001181172589.jpg differ diff --git a/docs/dws/umn/figure/en-us_image_0000001181172591.png b/docs/dws/umn/figure/en-us_image_0000001181172591.png new file mode 100644 index 00000000..62beb31c Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001181172591.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001188355709.png b/docs/dws/umn/figure/en-us_image_0000001188355709.png new file mode 100644 index 00000000..0b6df73e Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001188355709.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001188917631.png b/docs/dws/umn/figure/en-us_image_0000001188917631.png new file mode 100644 index 00000000..5b2df6bc Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001188917631.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001190291829.png b/docs/dws/umn/figure/en-us_image_0000001190291829.png new file mode 100644 index 00000000..a04992e3 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001190291829.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001192706523.png b/docs/dws/umn/figure/en-us_image_0000001192706523.png new file mode 100644 index 00000000..2b971aa7 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001192706523.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001192746635.png b/docs/dws/umn/figure/en-us_image_0000001192746635.png new file mode 100644 index 00000000..1303a51c Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001192746635.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001192746637.png b/docs/dws/umn/figure/en-us_image_0000001192746637.png new file mode 100644 index 00000000..db9e0208 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001192746637.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001196492200.png b/docs/dws/umn/figure/en-us_image_0000001196492200.png new file mode 100644 index 00000000..1cf17c2e Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001196492200.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001198531105.png b/docs/dws/umn/figure/en-us_image_0000001198531105.png new file mode 100644 index 00000000..774b198d Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001198531105.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001198531291.png b/docs/dws/umn/figure/en-us_image_0000001198531291.png new file mode 100644 index 00000000..0b8028a1 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001198531291.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001198667977.png b/docs/dws/umn/figure/en-us_image_0000001198667977.png new file mode 100644 index 00000000..fbf7bc4a Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001198667977.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001198668023.png b/docs/dws/umn/figure/en-us_image_0000001198668023.png new file mode 100644 index 00000000..91b19b39 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001198668023.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001198668101.png b/docs/dws/umn/figure/en-us_image_0000001198668101.png new file mode 100644 index 00000000..70ac9a9e Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001198668101.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001198758917.png b/docs/dws/umn/figure/en-us_image_0000001198758917.png new file mode 100644 index 00000000..129535d5 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001198758917.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001198763919.png b/docs/dws/umn/figure/en-us_image_0000001198763919.png new file mode 100644 index 00000000..6d8a5a14 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001198763919.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001199655548.png b/docs/dws/umn/figure/en-us_image_0000001199655548.png new file mode 100644 index 00000000..bdcc6526 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001199655548.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001200065787.png b/docs/dws/umn/figure/en-us_image_0000001200065787.png new file mode 100644 index 00000000..a76c319e Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001200065787.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001200300871.png b/docs/dws/umn/figure/en-us_image_0000001200300871.png new file mode 100644 index 00000000..530f7c8b Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001200300871.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001200379029.png b/docs/dws/umn/figure/en-us_image_0000001200379029.png new file mode 100644 index 00000000..f4ca4804 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001200379029.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001200379617.png b/docs/dws/umn/figure/en-us_image_0000001200379617.png new file mode 100644 index 00000000..dd1bd90b Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001200379617.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001204079851.png b/docs/dws/umn/figure/en-us_image_0000001204079851.png new file mode 100644 index 00000000..f1cdbed8 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001204079851.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001204558821.png b/docs/dws/umn/figure/en-us_image_0000001204558821.png new file mode 100644 index 00000000..4931e9c0 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001204558821.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001204596316.png b/docs/dws/umn/figure/en-us_image_0000001204596316.png new file mode 100644 index 00000000..315aec65 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001204596316.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001204609361.png b/docs/dws/umn/figure/en-us_image_0000001204609361.png new file mode 100644 index 00000000..7bf8b42e Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001204609361.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001204609685.png b/docs/dws/umn/figure/en-us_image_0000001204609685.png new file mode 100644 index 00000000..d3755cb1 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001204609685.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001204632331.png b/docs/dws/umn/figure/en-us_image_0000001204632331.png new file mode 100644 index 00000000..3630aa95 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001204632331.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001204760551.png b/docs/dws/umn/figure/en-us_image_0000001204760551.png new file mode 100644 index 00000000..e0158c36 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001204760551.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001204848125.png b/docs/dws/umn/figure/en-us_image_0000001204848125.png new file mode 100644 index 00000000..20c677d9 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001204848125.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001204872339.png b/docs/dws/umn/figure/en-us_image_0000001204872339.png new file mode 100644 index 00000000..1cd64ef7 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001204872339.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001204878747.png b/docs/dws/umn/figure/en-us_image_0000001204878747.png new file mode 100644 index 00000000..10563147 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001204878747.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001204891199.png b/docs/dws/umn/figure/en-us_image_0000001204891199.png new file mode 100644 index 00000000..be5a8081 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001204891199.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001207033065.png b/docs/dws/umn/figure/en-us_image_0000001207033065.png new file mode 100644 index 00000000..1fac0af5 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001207033065.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001207147903.png b/docs/dws/umn/figure/en-us_image_0000001207147903.png new file mode 100644 index 00000000..e093bbea Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001207147903.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001214965259.png b/docs/dws/umn/figure/en-us_image_0000001214965259.png new file mode 100644 index 00000000..33015740 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001214965259.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001216015456.png b/docs/dws/umn/figure/en-us_image_0000001216015456.png new file mode 100644 index 00000000..7e8a63a8 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001216015456.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001216175352.png b/docs/dws/umn/figure/en-us_image_0000001216175352.png new file mode 100644 index 00000000..b35e4cc1 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001216175352.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001217284196.png b/docs/dws/umn/figure/en-us_image_0000001217284196.png new file mode 100644 index 00000000..622cc72b Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001217284196.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001231733612.png b/docs/dws/umn/figure/en-us_image_0000001231733612.png new file mode 100644 index 00000000..e8e059d8 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001231733612.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001232285254.png b/docs/dws/umn/figure/en-us_image_0000001232285254.png new file mode 100644 index 00000000..008239b1 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001232285254.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001232385296.png b/docs/dws/umn/figure/en-us_image_0000001232385296.png new file mode 100644 index 00000000..32219812 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001232385296.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001232385392.png b/docs/dws/umn/figure/en-us_image_0000001232385392.png new file mode 100644 index 00000000..c012d50e Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001232385392.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001232389880.png b/docs/dws/umn/figure/en-us_image_0000001232389880.png new file mode 100644 index 00000000..c9e15482 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001232389880.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001232399264.png b/docs/dws/umn/figure/en-us_image_0000001232399264.png new file mode 100644 index 00000000..6866e5c0 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001232399264.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001232559208.png b/docs/dws/umn/figure/en-us_image_0000001232559208.png new file mode 100644 index 00000000..91473a63 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001232559208.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001232719136.png b/docs/dws/umn/figure/en-us_image_0000001232719136.png new file mode 100644 index 00000000..b67f2277 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001232719136.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001238779265.png b/docs/dws/umn/figure/en-us_image_0000001238779265.png new file mode 100644 index 00000000..21d75548 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001238779265.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001248712703.png b/docs/dws/umn/figure/en-us_image_0000001248712703.png new file mode 100644 index 00000000..f80a7170 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001248712703.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001248717121.png b/docs/dws/umn/figure/en-us_image_0000001248717121.png new file mode 100644 index 00000000..778e0907 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001248717121.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001248996617.png b/docs/dws/umn/figure/en-us_image_0000001248996617.png new file mode 100644 index 00000000..61b4d947 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001248996617.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001260615077.png b/docs/dws/umn/figure/en-us_image_0000001260615077.png new file mode 100644 index 00000000..f09241a7 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001260615077.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001268125113.png b/docs/dws/umn/figure/en-us_image_0000001268125113.png new file mode 100644 index 00000000..9b5f2dc2 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001268125113.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001268864780.png b/docs/dws/umn/figure/en-us_image_0000001268864780.png new file mode 100644 index 00000000..68a8bdfa Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001268864780.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001269536006.png b/docs/dws/umn/figure/en-us_image_0000001269536006.png new file mode 100644 index 00000000..1aa6e9a8 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001269536006.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001269695730.png b/docs/dws/umn/figure/en-us_image_0000001269695730.png new file mode 100644 index 00000000..e4ba6fb2 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001269695730.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001276984957.png b/docs/dws/umn/figure/en-us_image_0000001276984957.png new file mode 100644 index 00000000..cd270b1f Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001276984957.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001276994681.png b/docs/dws/umn/figure/en-us_image_0000001276994681.png new file mode 100644 index 00000000..4df4eefc Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001276994681.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001276999057.png b/docs/dws/umn/figure/en-us_image_0000001276999057.png new file mode 100644 index 00000000..0b8028a1 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001276999057.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001277158833.png b/docs/dws/umn/figure/en-us_image_0000001277158833.png new file mode 100644 index 00000000..19564bb8 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001277158833.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001277270017.png b/docs/dws/umn/figure/en-us_image_0000001277270017.png new file mode 100644 index 00000000..3c558eaf Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001277270017.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001277273485.png b/docs/dws/umn/figure/en-us_image_0000001277273485.png new file mode 100644 index 00000000..8ff3fd3f Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001277273485.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001277279565.png b/docs/dws/umn/figure/en-us_image_0000001277279565.png new file mode 100644 index 00000000..5b233448 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001277279565.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001318103277.png b/docs/dws/umn/figure/en-us_image_0000001318103277.png new file mode 100644 index 00000000..0fbe8992 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001318103277.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001318263369.png b/docs/dws/umn/figure/en-us_image_0000001318263369.png new file mode 100644 index 00000000..183ced53 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001318263369.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001318295749.png b/docs/dws/umn/figure/en-us_image_0000001318295749.png new file mode 100644 index 00000000..318ef5b6 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001318295749.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001318300585.png b/docs/dws/umn/figure/en-us_image_0000001318300585.png new file mode 100644 index 00000000..d7779999 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001318300585.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001318423893.png b/docs/dws/umn/figure/en-us_image_0000001318423893.png new file mode 100644 index 00000000..d40c154c Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001318423893.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001318546125.png b/docs/dws/umn/figure/en-us_image_0000001318546125.png new file mode 100644 index 00000000..853b6045 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001318546125.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001318571169.png b/docs/dws/umn/figure/en-us_image_0000001318571169.png new file mode 100644 index 00000000..033cdd1c Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001318571169.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001364353761.png b/docs/dws/umn/figure/en-us_image_0000001364353761.png new file mode 100644 index 00000000..bcc22c24 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001364353761.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001381824320.png b/docs/dws/umn/figure/en-us_image_0000001381824320.png new file mode 100644 index 00000000..166b0297 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001381824320.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001382420930.png b/docs/dws/umn/figure/en-us_image_0000001382420930.png new file mode 100644 index 00000000..a4000a3b Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001382420930.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001400066532.png b/docs/dws/umn/figure/en-us_image_0000001400066532.png new file mode 100644 index 00000000..60bc4a98 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001400066532.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001400224888.png b/docs/dws/umn/figure/en-us_image_0000001400224888.png new file mode 100644 index 00000000..9f81abb9 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001400224888.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001400244856.png b/docs/dws/umn/figure/en-us_image_0000001400244856.png new file mode 100644 index 00000000..c02e2117 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001400244856.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001400246588.png b/docs/dws/umn/figure/en-us_image_0000001400246588.png new file mode 100644 index 00000000..69207d93 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001400246588.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001432175545.png b/docs/dws/umn/figure/en-us_image_0000001432175545.png new file mode 100644 index 00000000..c3aa18a1 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001432175545.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001432193733.png b/docs/dws/umn/figure/en-us_image_0000001432193733.png new file mode 100644 index 00000000..f48103bd Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001432193733.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001432579569.png b/docs/dws/umn/figure/en-us_image_0000001432579569.png new file mode 100644 index 00000000..5db6b350 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001432579569.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001432860233.png b/docs/dws/umn/figure/en-us_image_0000001432860233.png new file mode 100644 index 00000000..0d0d8771 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001432860233.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001450666877.png b/docs/dws/umn/figure/en-us_image_0000001450666877.png new file mode 100644 index 00000000..50507447 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001450666877.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001450747689.png b/docs/dws/umn/figure/en-us_image_0000001450747689.png new file mode 100644 index 00000000..64f17661 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001450747689.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001450766717.png b/docs/dws/umn/figure/en-us_image_0000001450766717.png new file mode 100644 index 00000000..4abaf6d5 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001450766717.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001450883809.png b/docs/dws/umn/figure/en-us_image_0000001450883809.png new file mode 100644 index 00000000..063ed91d Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001450883809.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001450885665.png b/docs/dws/umn/figure/en-us_image_0000001450885665.png new file mode 100644 index 00000000..a9e0901e Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001450885665.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001450965281.png b/docs/dws/umn/figure/en-us_image_0000001450965281.png new file mode 100644 index 00000000..24b962fd Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001450965281.png differ diff --git a/docs/dws/umn/figure/en-us_image_0000001450967281.png b/docs/dws/umn/figure/en-us_image_0000001450967281.png new file mode 100644 index 00000000..0e0f4b00 Binary files /dev/null and b/docs/dws/umn/figure/en-us_image_0000001450967281.png differ diff --git a/docs/dws/umn/public_sys-resources/ExpandCollapse.js b/docs/dws/umn/public_sys-resources/ExpandCollapse.js new file mode 100644 index 00000000..116ddaab --- /dev/null +++ b/docs/dws/umn/public_sys-resources/ExpandCollapse.js @@ -0,0 +1 @@ +var expandClassName="dropdownexpand";var collapseClassName="dropdowncollapse";var collapseTableClassName="dropdowncollapsetable";function ExpandorCollapseNode(a){a=a.parentNode;if(a.className==expandClassName){a.className=collapseClassName}else{a.className=expandClassName}}function ExpandorCollapseTableNode(a){a=a.parentNode;if(a.className==expandClassName){a.className=collapseTableClassName}else{a.className=expandClassName}}function ExpandorCollapseAllNodes(g,h,c){var a=g.getAttribute("title");var b=g.parentNode;if(a=="collapse"){g.setAttribute("title","expand");g.className="dropdownAllButtonexpand";g.innerHTML=h}else{g.setAttribute("title","collapse");g.className="dropdownAllButtoncollapse";g.innerHTML=c}var f=b.getElementsByTagName("*");for(var d=0;d-1){ExpandForHref(a.substring(a.lastIndexOf("#")+1))}}catch(c){}}; \ No newline at end of file diff --git a/docs/dws/umn/public_sys-resources/caution_3.0-en-us.png b/docs/dws/umn/public_sys-resources/caution_3.0-en-us.png new file mode 100644 index 00000000..60f60762 Binary files /dev/null and b/docs/dws/umn/public_sys-resources/caution_3.0-en-us.png differ diff --git a/docs/dws/umn/public_sys-resources/commonltr.css b/docs/dws/umn/public_sys-resources/commonltr.css new file mode 100644 index 00000000..c5480b0a --- /dev/null +++ b/docs/dws/umn/public_sys-resources/commonltr.css @@ -0,0 +1 @@ +body{font-size:10pt;font-family:Arial;margin:1.5em;border-top:2pt;padding-top:1em;padding-bottom:2em}.msgph{font-family:Courier New}.rowlinecopyright{color:red;margin-top:10pt}.unresolved{background-color:skyblue}.noTemplate{background-color:yellow}.base{background-color:#fff}.nested0{margin-top:1em}.p{margin-top:.6em;margin-bottom:.6em}p{margin-top:.5em;margin-bottom:.5em}.note p{margin-top:.5em;margin-bottom:.5em}.tip p{margin-top:.5em;margin-bottom:.5em}.danger p{margin-top:.5em;margin-bottom:.5em}.notice p{margin-top:.5em;margin-bottom:.5em}.warning p{margin-top:.5em;margin-bottom:.5em}.caution p{margin-top:.5em;margin-bottom:.5em}.attention p{margin-top:.5em;margin-bottom:.5em}table p{margin-top:.2em;margin-bottom:.2em}table .p{margin-top:.4em;margin-bottom:.2em}.figcap{font-size:10pt}img{margin-top:.3em}.figdesc{font-style:normal}.figborder{border-style:solid;padding-left:3px;border-width:2px;padding-right:3px;margin-top:1em;border-color:Silver}.figsides{border-left:2px solid;padding-left:3px;border-right:2px solid;padding-right:3px;margin-top:1em;border-color:Silver}.figtop{border-top:2px solid;margin-top:1em;border-color:Silver}.figbottom{border-bottom:2px solid;border-color:Silver}.figtopbot{border-top:2px solid;border-bottom:2px solid;margin-top:1em;border-color:Silver}.fignone{font-size:10pt;margin-top:8pt;margin-bottom:8pt}.familylinks{margin-top:1.5em;margin-bottom:1em}.ullinks{list-style-type:none}.linklist{margin-bottom:1em}.linklistwithchild{margin-left:1.5em;margin-bottom:1em}.sublinklist{margin-left:1.5em;margin-bottom:1em}.relconcepts{margin-top:.6em;margin-bottom:.6em}.reltasks{margin-top:.6em;margin-bottom:.6em}.relref{margin-top:.6em;margin-bottom:.6em}.relinfo{margin-top:.6em;margin-bottom:.6em}.breadcrumb{font-size:smaller;margin-bottom:.6em}.prereq{margin-left:20px}.parentlink{margin-top:.6em;margin-bottom:.6em}.nextlink{margin-top:.6em;margin-bottom:.6em}.previouslink{margin-top:.6em;margin-bottom:.6em}.topictitle1{margin-top:0;margin-bottom:1em;font-size:14pt;color:#007af4}.topictitle2{margin-top:1pc;margin-bottom:.45em;font-size:1.17em;color:#007af4}.topictitle3{margin-top:1pc;margin-bottom:.17em;font-size:1.17em;font-weight:bold;color:#007af4}.topictitle4{margin-top:.83em;font-size:1.17em;font-weight:bold}.topictitle5{font-size:1.17em;font-weight:bold}.topictitle6{font-size:1.17em;font-style:italic}.sectiontitle{margin-top:1em;margin-bottom:1em;color:black;font-size:10.5pt;font-weight:bold;color:#007af4;overflow:auto}.section{margin-top:1em;margin-bottom:1em}.example{margin-top:1em;margin-bottom:1em}.sectiontitle2contents:link{color:#007af4}.sectiontitle2contents:visited{color:#800080}.note{margin-top:1em;margin-bottom:1em;background-color:#ffc}.notetitle{font-weight:bold}.notelisttitle{font-weight:bold}.tip{margin-top:1em;margin-bottom:1em;background-color:#ffc}.tiptitle{font-weight:bold}.fastpath{margin-top:1em;margin-bottom:1em;background-color:#ffc}.fastpathtitle{font-weight:bold}.important{margin-top:1em;margin-bottom:1em;background-color:#ffc}.importanttitle{font-weight:bold}.remember{margin-top:1em;margin-bottom:1em;background-color:#ffc}.remembertitle{font-weight:bold}.restriction{margin-top:1em;margin-bottom:1em;background-color:#ffc}.restrictiontitle{font-weight:bold}.attention{margin-top:1em;margin-bottom:1em;background-color:#ffc}.attentiontitle{font-weight:bold}.dangertitle{font-weight:bold}.danger{margin-top:1em;margin-bottom:1em;background-color:#ffc}.noticetitle{font-weight:bold}.notice{margin-top:1em;margin-bottom:1em;background-color:#ffc}.warningtitle{font-weight:bold}.warning{margin-top:1em;margin-bottom:1em;background-color:#ffc}.cautiontitle{font-weight:bold}.caution{margin-top:1em;margin-bottom:1em;background-color:#ffc}ul.simple{list-style-type:none}li ul{margin-top:.6em}li{margin-top:.6em;margin-bottom:.6em}.note li{margin-top:.2em;margin-bottom:.2em}.tip li{margin-top:.2em;margin-bottom:.2em}.danger li{margin-top:.2em;margin-bottom:.2em}.warning li{margin-top:.2em;margin-bottom:.2em}.notice li{margin-top:.2em;margin-bottom:.2em}.caution li{margin-top:.2em;margin-bottom:.2em}.attention li{margin-top:.2em;margin-bottom:.2em}table li{margin-top:.2em;margin-bottom:.2em}ol{margin-top:1em;margin-bottom:1em;margin-left:2.4em;padding-left:0}ul{margin-top:1em;margin-bottom:1em;margin-left:2.0em;padding-left:0}ol ul{list-style:disc}ul ul{list-style:square}ol ul ul{list-style:square}ol ul{list-style-type:disc}table ol{margin-top:.4em;margin-bottom:.4em;list-style:decimal}table ul{margin-top:.4em;margin-bottom:.4em;list-style:disc}table ul ul{margin-top:.4em;margin-bottom:.4em;list-style:square}table ol ol{margin-top:.4em;margin-bottom:.4em;list-style:lower-alpha}table ol ul{margin-top:.4em;margin-bottom:.4em;list-style:disc}table ul ol{margin-top:.4em;margin-bottom:.4em;list-style:decimal}.substepthirdol{list-style-type:lower-roman}.firstcol{font-weight:bold}th{background-color:#cfcfcf}table{margin-top:8pt;margin-bottom:12pt;width:100%}table caption{margin-top:8pt;text-align:left}.bold{font-weight:bold}.boldItalic{font-weight:bold;font-style:italic}.italic{font-style:italic}.underlined{text-decoration:underline}.var{font-style:italic}.shortcut{text-decoration:underline}.dlterm{font-weight:bold}dd{margin-top:.5em;margin-bottom:.5em}.dltermexpand{font-weight:bold;margin-top:1em}*[compact="yes"]>li{margin-top:0}*[compact="no"]>li{margin-top:.53em}.liexpand{margin-top:1em;margin-bottom:1em}.sliexpand{margin-top:1em;margin-bottom:1em}.dlexpand{margin-top:1em;margin-bottom:1em}.ddexpand{margin-top:1em;margin-bottom:1em}.stepexpand{margin-top:.3em;margin-bottom:.3em}.substepexpand{margin-top:.3em;margin-bottom:.3em}div.imageleft{text-align:left}div.imagecenter{text-align:center}div.imageright{text-align:right}div.imagejustify{text-align:justify}div.noblankline{text-align:center}div.noblankline img{margin-top:0}pre.screen{margin-top:2px;margin-bottom:2px;padding:1.5px 1.5px 0 1.5px;border:0;background-color:#ddd;white-space:pre}pre.codeblock{margin-top:2px;margin-bottom:2px;padding:1.5px 1.5px 0 1.5px;border:0;background-color:#ddd;white-space:pre}.hrcopyright{color:#3f4e5d;margin-top:18pt}.hwcopyright{text-align:center}.comment{margin:2px 2px 2px 2px;font-family:Arial;font-size:10pt;background-color:#bfb;color:#000}.dropdownAllButtonexpand{cursor:pointer;background-repeat:no-repeat;background-position:0 4px;padding-left:15px;background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4}.dropdownAllButtoncollapse{cursor:pointer;background-repeat:no-repeat;background-position:0 4px;padding-left:15px;background-image:url(icon-arrowdn.gif);text-decoration:underline;color:#007af4;text-decoration:underline;color:#007af4}.dropdowntitle{background-repeat:no-repeat;background-position:0 4px;padding-left:15px;cursor:pointer;text-decoration:underline;color:#007af4}.dropdownexpand .dropdowntitle{background-image:url(icon-arrowdn.gif);text-decoration:underline;color:#007af4;margin:0 0 8px 0}.dropdowncollapse .dropdowncontext{display:none}.dropdowncollapse .dropdowntitle{background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4}.dropdowncollapsetable{border:0}.dropdowncollapsetable .dropdowncontext{display:none}.dropdowncollapsetable .dropdowntitle{background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4}pre{font-size:10pt;font-weight:normal;margin-left:9;margin-top:2;margin-bottom:2}.termcolor{color:blue;cursor:pointer}#dhtmlgoodies_tooltip{background-color:#f0f0d2;border:1px solid #000;position:absolute;display:none;z-index:20000;padding:2px;font-size:.9em;-moz-border-radius:6px;font-family:"Trebuchet MS","Lucida Sans Unicode",Arial,sans-serif}#dhtmlgoodies_tooltipShadow{position:absolute;background-color:#555;display:none;z-index:10000;opacity:.7;filter:alpha(opacity=70);-khtml-opacity:.7;-moz-opacity:.7;-moz-border-radius:6px}.freeze{position:fixed;_position:absolute;_top:expression(eval(document.documentElement.scrollTop));left:10;top:0} \ No newline at end of file diff --git a/docs/dws/umn/public_sys-resources/commonltr_print.css b/docs/dws/umn/public_sys-resources/commonltr_print.css new file mode 100644 index 00000000..a5982314 --- /dev/null +++ b/docs/dws/umn/public_sys-resources/commonltr_print.css @@ -0,0 +1 @@ +body{font-size:12.0pt;margin:1.5em;margin-left:1.6cm}.msgph{font-family:Courier New}.rowlinecopyright{color:red;margin-top:10pt}.unresolved{background-color:skyblue}.noTemplate{background-color:yellow}.base{background-color:#fff}.nested0{margin-top:1em}.p{margin-top:1em}p{margin-top:.5em;margin-bottom:.5em}.note p{margin-top:.5em;margin-bottom:.5em}.tip p{margin-top:.5em;margin-bottom:.5em}.danger p{margin-top:.5em;margin-bottom:.5em}.warning p{margin-top:.5em;margin-bottom:.5em}.notice p{margin-top:.5em;margin-bottom:.5em}.caution p{margin-top:.5em;margin-bottom:.5em}.attention p{margin-top:.5em;margin-bottom:.5em}table p{margin-top:.2em;margin-bottom:.2em}table .p{margin-top:.4em;margin-bottom:.2em}.covertable{border:0;width:100% cellpadding:8pt;cellspacing:8pt}.cover_productname{font-size:15.0pt;font-family:"Arial"}.cover_manualtitle{font-size:24.0pt;font-weight:bold;font-family:"Arial"}.cover_manualsubtitle{font-size:18.0pt;font-weight:bold;font-family:"Arial"}.cover_heading{font-size:12.0pt;font-weight:bold;font-family:"Arial"}.cover_text{font-size:9.0pt;font-family:"Arial"}.tocheading,.heading1,.topictitle1{margin-top:40.0pt;margin-right:0;margin-bottom:20.0pt;margin-left:-1cm;text-align:left;border:0;border-bottom:solid windowtext .5pt;font-size:22.0pt;font-family:"Arial";font-weight:bold}.topictitlenumber1{font-size:72.0pt;font-family:"Book Antiqua";font-weight:bold}.topictitle2{margin-top:10.0pt;margin-right:0;margin-bottom:8.0pt;margin-left:-1cm;text-indent:0;font-size:18.0pt;font-family:"Arial";font-weight:bold}.topictitle3{margin-top:10.0pt;margin-right:0;margin-bottom:8.0pt;margin-left:0;text-indent:0;font-size:16.0pt;font-family:"Book Antiqua";font-weight:bold}.topictitle4{margin-top:10.0pt;margin-right:0;margin-bottom:8.0pt;margin-left:0;text-indent:0;font-size:14.0pt;font-family:"Book Antiqua";font-weight:bold}.topictitle5{margin-top:10.0pt;margin-right:0;margin-bottom:8.0pt;margin-left:0;text-indent:0;font-size:13.0pt;font-family:"Book Antiqua";font-weight:bold}.blocklabel,.topictitle6{margin-top:15.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;text-indent:0;font-size:13.0pt;font-family:"Book Antiqua";font-weight:bold}.sectiontitle{margin-top:15.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:-1cm;text-indent:0;font-size:13.0pt;font-family:"Arial";font-weight:bold}.tocentry1{margin-top:8.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:12.0pt;font-family:"Book Antiqua";font-weight:bold}.tocentry2{margin-top:4.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman"}.tocentry3{margin-top:4.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman"}.tocentry4{margin-top:4.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman"}.tocentry5{margin-top:4.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman"}.tofentry1{margin-top:8.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman";font-weight:normal}.totentry1{margin-top:8.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman";font-weight:normal}.indexheading{margin-top:15.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;text-indent:0;font-size:13.0pt;font-family:"Book Antiqua";font-weight:bold}.indexentry1{margin-top:4pt;margin-right:0;margin-bottom:0;margin-left:0;line-height:12.0pt;font-size:12.0pt;font-family:"Times New Roman"}.indexentry2{margin-top:0;margin-right:0;margin-bottom:0;margin-left:24.0pt;line-height:12.0pt;font-size:12.0pt}.indexentry3{margin-top:0;margin-right:0;margin-bottom:0;margin-left:48pt;line-height:12.0pt;font-size:12.0pt}.figurenumber{font-weight:bold}.tablenumber{font-weight:bold}.familylinks{margin-top:1.5em;margin-bottom:1em}.figcap{font-size:11.0pt}.tablecap{font-size:11.0pt}.figdesc{font-style:normal}.fignone{margin-top:8.0pt}.figborder{border-style:solid;padding-left:3px;border-width:2px;padding-right:3px;margin-top:1em;border-color:Silver}.figsides{border-left:2px solid;padding-left:3px;border-right:2px solid;padding-right:3px;margin-top:1em;border-color:Silver}.figtop{border-top:2px solid;margin-top:1em;border-color:Silver}.figbottom{border-bottom:2px solid;border-color:Silver}.figtopbot{border-top:2px solid;border-bottom:2px solid;margin-top:1em;border-color:Silver}.ullinks{margin-left:0;list-style-type:none}.ulchildlink{margin-top:1em;margin-bottom:1em}.olchildlink{margin-top:1em;margin-bottom:1em;margin-left:1em}.linklist{margin-bottom:1em}.linklistwithchild{margin-left:1.5em;margin-bottom:1em}.sublinklist{margin-left:1.5em;margin-bottom:1em}.relconcepts{margin-left:1cm;margin-top:1em;margin-bottom:1em}.reltasks{margin-left:1cm;margin-top:1em;margin-bottom:1em}.relref{margin-left:1cm;margin-top:1em;margin-bottom:1em}.relinfo{margin-top:1em;margin-bottom:1em}.breadcrumb{font-size:smaller;margin-bottom:1em}.prereq{margin-left:0}.parentlink{margin-top:.6em;margin-bottom:.6em}.nextlink{margin-top:.6em;margin-bottom:.6em}.previouslink{margin-top:.6em;margin-bottom:.6em}.section{margin-top:1em;margin-bottom:1em}.example{margin-top:1em;margin-bottom:1em}table .note{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.note{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.notetitle{font-weight:bold;font-size:11.0pt}.notelisttitle{font-weight:bold}table .tip{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.tip{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.tiptitle{font-weight:bold;font-size:11.0pt}table .fastpath{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.fastpath{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.fastpathtitle{font-weight:bold;font-size:11.0pt}table .important{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman";font-style:italic}.important{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.importanttitle{font-weight:bold;font-size:11.0pt}table .remember{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman";font-style:italic}.remember{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.remembertitle{font-weight:bold;font-size:11.0pt}table .restriction{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman";font-style:italic}.restriction{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.restrictiontitle{font-weight:bold;font-size:11.0pt}table .attention{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.attention{margin-top:1em;margin-bottom:1em;border:0;border-top:solid .5pt;border-bottom:solid .5pt}.attentiontitle{font-weight:bold}table .danger{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.dangertitle{font-weight:bold}.danger{margin-top:1em;margin-bottom:1em;border:0;border-top:solid .5pt;border-bottom:solid .5pt}table .notice{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.noticetitle{font-weight:bold}.notice{margin-top:1em;margin-bottom:1em;border:0;border-top:solid .5pt;border-bottom:solid .5pt}table .warning{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.warningtitle{font-weight:bold}.warning{margin-top:1em;margin-bottom:1em;border:0;border-top:solid .5pt;border-bottom:solid .5pt}table .caution{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}table caption{margin-top:8pt;text-align:left;font-weight:bold}.tablenoborder{margin-top:8pt}.cautiontitle{font-weight:bold}.caution{margin-top:1em;margin-bottom:1em;border:0;border-top:solid .5pt;border-bottom:solid .5pt}ul.simple{list-style-type:none}li ul{margin-top:.6em}li{margin-top:.6em;margin-bottom:.6em}.note li{margin-top:.2em;margin-bottom:.2em}.tip li{margin-top:.2em;margin-bottom:.2em}.danger li{margin-top:.2em;margin-bottom:.2em}.warning li{margin-top:.2em;margin-bottom:.2em}.notice li{margin-top:.2em;margin-bottom:.2em}.caution li{margin-top:.2em;margin-bottom:.2em}.attention li{margin-top:.2em;margin-bottom:.2em}table li{margin-top:.2em;margin-bottom:.2em}.firstcol{font-weight:bold}th{background-color:#cfcfcf}.bold{font-weight:bold}.boldItalic{font-weight:bold;font-style:italic}.italic{font-style:italic}.underlined{text-decoration:underline}.var{font-style:italic}.shortcut{text-decoration:underline}.dlterm{font-weight:bold}dd{margin-top:.5em;margin-bottom:.5em}.dltermexpand{font-weight:bold;margin-top:1em}*[compact="yes"]>li{margin-top:0}*[compact="no"]>li{margin-top:.53em}.liexpand{margin-top:1em;margin-bottom:1em}.sliexpand{margin-top:1em;margin-bottom:1em}.dlexpand{margin-top:1em;margin-bottom:1em}.ddexpand{margin-top:1em;margin-bottom:1em}.stepexpand{margin-top:1em;margin-bottom:1em}.substepexpand{margin-top:1em;margin-bottom:1em}table{margin-top:8pt;margin-bottom:10.0pt;width:100%}thead{font-size:10.0pt;font-family:"Book Antiqua";font-weight:bold}tbody{font-size:11.0pt}ol{margin-top:1em;margin-bottom:1em;margin-left:1.7em;-webkit-padding-start:0}ul{margin-top:1em;margin-bottom:1em;margin-left:1.2em;-webkit-padding-start:0}ol ul{list-style:disc}ul ul{list-style:square}ol ol{list-style-type:lower-alpha}table ol{margin-top:.4em;margin-bottom:.4em;list-style:decimal}table ul{margin-top:.4em;margin-bottom:.4em;list-style:disc}table ul ul{margin-top:.4em;margin-bottom:.4em;list-style:square}table ol ol{margin-top:.4em;margin-bottom:.4em;list-style:lower-alpha}table ol ul{margin-top:.4em;margin-bottom:.4em;list-style:disc}table ul ol{margin-top:.4em;margin-bottom:.4em;list-style:decimal}.substepthirdol{list-style-type:lower-roman}div.imageleft{text-align:left}div.imagecenter{text-align:center}div.imageright{text-align:right}div.imagejustify{text-align:justify}div.noblankline{text-align:center}div.noblankline img{margin-top:0}pre{font-size:10.0pt;border-width:2px;padding:2px;margin-top:5px;margin-bottom:5px;white-space:pre-wrap;white-space:-moz-pre-wrap;white-space:-pre-wrap;white-space:-o-pre-wrap;word-wrap:break-word}pre.screen{margin-top:2px;margin-bottom:2px;padding:1.5px 1.5px 0 1.5px;border:0;white-space:pre}pre.codeblock{margin-top:2px;margin-bottom:2px;padding:1.5px 1.5px 0 1.5px;border:0;white-space:pre}.dropdownAllButtonexpand{cursor:pointer;background-repeat:no-repeat;background-position:0 4px;padding-left:15px;background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4}.dropdownAllButtoncollapse{cursor:pointer;background-repeat:no-repeat;background-position:0 4px;padding-left:15px;background-image:url(icon-arrowdn.gif);text-decoration:underline;color:#007af4;text-decoration:underline;color:#007af4}.dropdowntitle{background-repeat:no-repeat;background-position:0 4px;padding-left:15px;cursor:pointer;text-decoration:underline;color:#007af4}.dropdownexpand .dropdowntitle{background-image:url(icon-arrowdn.gif);text-decoration:underline;color:#007af4;margin:0 0 8px 0}.dropdowncollapse .dropdowntitle{background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4;margin:0 0 8px 0}.dropdowncollapsetable .dropdowntitle{background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4;margin:0 0 8px 0}.prefacesectiontitle1{margin-top:10.0pt;margin-right:0;margin-bottom:8.0pt;margin-left:-1cm;text-indent:0;font-size:18.0pt;font-family:"Book Antiqua";font-weight:bold;overflow:auto}.termcolor{color:blue;cursor:pointer}#dhtmlgoodies_tooltip{background-color:#f0f0d2;border:1px solid #000;position:absolute;display:none;z-index:20000;padding:2px;font-size:.9em;-moz-border-radius:6px;font-family:"Trebuchet MS","Lucida Sans Unicode",Arial,sans-serif}#dhtmlgoodies_tooltipShadow{position:absolute;background-color:#555;display:none;z-index:10000;opacity:.7;filter:alpha(opacity=70);-khtml-opacity:.7;-moz-opacity:.7;-moz-border-radius:6px}.freeze{position:fixed;_position:absolute;_top:expression(eval(document.documentElement.scrollTop));left:10;top:0}.hrcopyright{color:#3f4e5d;margin-top:18pt;margin-left:-1cm}.hwcopyright{text-align:center;font-family:Arial;margin-left:-1cm} \ No newline at end of file diff --git a/docs/dws/umn/public_sys-resources/commonrtl.css b/docs/dws/umn/public_sys-resources/commonrtl.css new file mode 100644 index 00000000..f261da75 --- /dev/null +++ b/docs/dws/umn/public_sys-resources/commonrtl.css @@ -0,0 +1,2 @@ +/*! Copyright (c) Huawei Technologies Co., Ltd. 2020-2022. All rights reserved. */.msgph{font-family:Courier New}.unresolved{background-color:#87ceeb}.noTemplate{background-color:#ff0}.base{background-color:#fff}/*! Add space for top level topics */.nested0,.p{margin-top:1em}/*! div with class=p is used for paragraphs that contain blocks, to keep the XHTML valid *//*! Default of italics to set apart figure captions */.figcap,.italic,.var{font-style:italic}.figdesc{font-style:normal}/*! Use @frame to create frames on figures */.figborder{padding-left:3px;padding-right:3px;margin-top:1em;border:2px solid Silver}.figsides{margin-top:1em;padding-left:3px;padding-right:3px;border-left:2px solid Silver;border-right:2px solid Silver}.figtop{border-top:2px solid Silver;margin-top:1em}.figbottom{border-bottom:2px solid Silver}.figtopbot{border-top:2px solid Silver;border-bottom:2px solid Silver;margin-top:1em}/*! Most link groups are created with
. Ensure they have space before and after. */.ullinks,ul.simple{list-style-type:none}.attention,.danger,.ddexpand,.dlexpand,.example,.fastpath,.important,.liexpand,.linklist,.note,.notice,.olchildlink,.relconcepts,.relinfo,.relref,.reltasks,.remember,.restriction,.section,.sliexpand,.stepexpand,.substepexpand,.tip,.ulchildlink,.warning{margin-top:1em;margin-bottom:1em}.linklistwithchild,.sublinklist{margin-top:1em;margin-right:1.5em;margin-bottom:1em}.breadcrumb{font-size:smaller;margin-bottom:1em}.prereq{margin-right:20px}/*! Set heading sizes, getting smaller for deeper nesting */.topictitle1{font-size:1.34em;margin-top:0;margin-bottom:.1em}.topictitle2,.topictitle3,.topictitle4,.topictitle5,.topictitle6,.sectiontitle{font-size:1.17em}.topictitle2{margin-top:1pc;margin-bottom:.45em}.topictitle3{margin-top:1pc;margin-bottom:.17em;font-weight:700}.topictitle4{margin-top:.83em;font-weight:700}.topictitle5{font-weight:700}.topictitle6{font-style:italic}.sectiontitle{margin-top:1em;margin-bottom:0;color:#000;font-weight:700}/*! All note formats have the same default presentation */.attentiontitle,.bold,.cautiontitle,.dangertitle,.dlterm,.fastpathtitle,.firstcol,.importanttitle,.notelisttitle,.notetitle,.noticetitle,.parmname,.remembertitle,.restrictiontitle,.tiptitle,.uicontrol,.warningtitle{font-weight:700}.caution{font-weight:700;margin-bottom:1em}/*! Simple lists do not get a bullet *//*! Used on the first column of a table, when rowheader="firstcol" is used *//*! Various basic phrase styles */.boldItalic{font-weight:700;font-style:italic}.shortcut,.underlined{text-decoration:underline}/*! 2008-10-27 keyword采用跟随上下文的样式 +*//*! Default of bold for definition list terms *//*! Use CSS to expand lists with @compact="no" */.dltermexpand{font-weight:700;margin-top:1em}[compact="yes"]>li{margin-top:0}[compact="no"]>li{margin-top:.53em}/*! Align images based on @align on topic/image */div.imageleft,.text-align-left{text-align:left}div.imagecenter,.text-align-center{text-align:center}div.imageright,.text-align-right{text-align:right}div.imagejustify,.text-align-justify{text-align:justify}.cellrowborder{border-right:0;border-top:0;border-left:1px solid;border-bottom:1px solid}.row-nocellborder{border-left:hidden;border-right:0;border-top:0;border-bottom:1px solid}.cell-norowborder{border-top:0;border-bottom:hidden;border-right:0;border-left:1px solid}.nocellnorowborder{border:0;border-left:hidden;border-bottom:hidden}pre.codeblock,pre.screen{padding:5px;border:outset;background-color:#ccc;margin-top:2px;margin-bottom:2px;white-space:pre} \ No newline at end of file diff --git a/docs/dws/umn/public_sys-resources/danger_3.0-en-us.png b/docs/dws/umn/public_sys-resources/danger_3.0-en-us.png new file mode 100644 index 00000000..47a9c723 Binary files /dev/null and b/docs/dws/umn/public_sys-resources/danger_3.0-en-us.png differ diff --git a/docs/dws/umn/public_sys-resources/delta.gif b/docs/dws/umn/public_sys-resources/delta.gif new file mode 100644 index 00000000..0d1b1f67 Binary files /dev/null and b/docs/dws/umn/public_sys-resources/delta.gif differ diff --git a/docs/dws/umn/public_sys-resources/deltaend.gif b/docs/dws/umn/public_sys-resources/deltaend.gif new file mode 100644 index 00000000..cc7da0fc Binary files /dev/null and b/docs/dws/umn/public_sys-resources/deltaend.gif differ diff --git a/docs/dws/umn/public_sys-resources/icon-arrowdn.gif b/docs/dws/umn/public_sys-resources/icon-arrowdn.gif new file mode 100644 index 00000000..37942803 Binary files /dev/null and b/docs/dws/umn/public_sys-resources/icon-arrowdn.gif differ diff --git a/docs/dws/umn/public_sys-resources/icon-arrowrt.gif b/docs/dws/umn/public_sys-resources/icon-arrowrt.gif new file mode 100644 index 00000000..6aaaa11c Binary files /dev/null and b/docs/dws/umn/public_sys-resources/icon-arrowrt.gif differ diff --git a/docs/dws/umn/public_sys-resources/icon-caution.gif b/docs/dws/umn/public_sys-resources/icon-caution.gif new file mode 100644 index 00000000..079c79b2 Binary files /dev/null and b/docs/dws/umn/public_sys-resources/icon-caution.gif differ diff --git a/docs/dws/umn/public_sys-resources/icon-danger.gif b/docs/dws/umn/public_sys-resources/icon-danger.gif new file mode 100644 index 00000000..079c79b2 Binary files /dev/null and b/docs/dws/umn/public_sys-resources/icon-danger.gif differ diff --git a/docs/dws/umn/public_sys-resources/icon-huawei.gif b/docs/dws/umn/public_sys-resources/icon-huawei.gif new file mode 100644 index 00000000..a31d60f8 Binary files /dev/null and b/docs/dws/umn/public_sys-resources/icon-huawei.gif differ diff --git a/docs/dws/umn/public_sys-resources/icon-note.gif b/docs/dws/umn/public_sys-resources/icon-note.gif new file mode 100644 index 00000000..31be2b03 Binary files /dev/null and b/docs/dws/umn/public_sys-resources/icon-note.gif differ diff --git a/docs/dws/umn/public_sys-resources/icon-notice.gif b/docs/dws/umn/public_sys-resources/icon-notice.gif new file mode 100644 index 00000000..40907065 Binary files /dev/null and b/docs/dws/umn/public_sys-resources/icon-notice.gif differ diff --git a/docs/dws/umn/public_sys-resources/icon-tip.gif b/docs/dws/umn/public_sys-resources/icon-tip.gif new file mode 100644 index 00000000..c47bae05 Binary files /dev/null and b/docs/dws/umn/public_sys-resources/icon-tip.gif differ diff --git a/docs/dws/umn/public_sys-resources/icon-warning.gif b/docs/dws/umn/public_sys-resources/icon-warning.gif new file mode 100644 index 00000000..079c79b2 Binary files /dev/null and b/docs/dws/umn/public_sys-resources/icon-warning.gif differ diff --git a/docs/dws/umn/public_sys-resources/imageResize.js b/docs/dws/umn/public_sys-resources/imageResize.js new file mode 100644 index 00000000..37309ce3 --- /dev/null +++ b/docs/dws/umn/public_sys-resources/imageResize.js @@ -0,0 +1,18 @@ +/** IDP renames $ to $$$,jQueryHW2 */ +var $$$, jQueryHW2; +jQueryHW2 = $$$ = $; + +function image_size(a) { + $$$(window).on('load', function () { + $$$(a).each(function () { + var e = $$$(this); + var f = e.width(); + var d = e.height(); + var b = f; + var c = d; + e.click(function () { + tb_show("", this.src, false) + }) + }) + }) +}; \ No newline at end of file diff --git a/docs/dws/umn/public_sys-resources/imageclose.gif b/docs/dws/umn/public_sys-resources/imageclose.gif new file mode 100644 index 00000000..3a3344af Binary files /dev/null and b/docs/dws/umn/public_sys-resources/imageclose.gif differ diff --git a/docs/dws/umn/public_sys-resources/imageclosehover.gif b/docs/dws/umn/public_sys-resources/imageclosehover.gif new file mode 100644 index 00000000..8699d5e3 Binary files /dev/null and b/docs/dws/umn/public_sys-resources/imageclosehover.gif differ diff --git a/docs/dws/umn/public_sys-resources/imagemax.gif b/docs/dws/umn/public_sys-resources/imagemax.gif new file mode 100644 index 00000000..99c07dc2 Binary files /dev/null and b/docs/dws/umn/public_sys-resources/imagemax.gif differ diff --git a/docs/dws/umn/public_sys-resources/imagemaxhover.gif b/docs/dws/umn/public_sys-resources/imagemaxhover.gif new file mode 100644 index 00000000..d01d77d6 Binary files /dev/null and b/docs/dws/umn/public_sys-resources/imagemaxhover.gif differ diff --git a/docs/dws/umn/public_sys-resources/jquery-migrate-1.2.1.min.js b/docs/dws/umn/public_sys-resources/jquery-migrate-1.2.1.min.js new file mode 100644 index 00000000..88f4844b --- /dev/null +++ b/docs/dws/umn/public_sys-resources/jquery-migrate-1.2.1.min.js @@ -0,0 +1,2 @@ +/*! jQuery Migrate v1.2.1 | (c) 2005, 2013 jQuery Foundation, Inc. and other contributors | jquery.org/license */ +jQueryHW2.migrateMute===void 0&&(jQueryHW2.migrateMute=!0),function(e,t,n){function r(n){}function a(t,a,i,o){if(Object.defineProperty)try{return Object.defineProperty(t,a,{configurable:!0,enumerable:!0,get:function(){return r(o),i},set:function(e){r(o),i=e}}),n}catch(s){}e._definePropertyBroken=!0,t[a]=i}var i={};e.migrateWarnings=[],!e.migrateMute,e.migrateTrace===n&&(e.migrateTrace=!0),e.migrateReset=function(){i={},e.migrateWarnings.length=0},"BackCompat"===document.compatMode&&r("jQueryHW2 is not compatible with Quirks Mode");var o=e("",{size:1}).attr("size")&&e.attrFn,s=e.attr,u=e.attrHooks.value&&e.attrHooks.value.get||function(){return null},c=e.attrHooks.value&&e.attrHooks.value.set||function(){return n},l=/^(?:input|button)$/i,d=/^[238]$/,p=/^(?:autofocus|autoplay|async|checked|controls|defer|disabled|hidden|loop|multiple|open|readonly|required|scoped|selected)$/i,f=/^(?:checked|selected)$/i;a(e,"attrFn",o||{},"jQueryHW2.attrFn is deprecated"),e.attr=function(t,a,i,u){var c=a.toLowerCase(),g=t&&t.nodeType;return u&&(4>s.length&&r("jQueryHW2.fn.attr( props, pass ) is deprecated"),t&&!d.test(g)&&(o?a in o:e.isFunction(e.fn[a])))?e(t)[a](i):("type"===a&&i!==n&&l.test(t.nodeName)&&t.parentNode&&r("Can't change the 'type' of an input or button in IE 6/7/8"),!e.attrHooks[c]&&p.test(c)&&(e.attrHooks[c]={get:function(t,r){var a,i=e.prop(t,r);return i===!0||"boolean"!=typeof i&&(a=t.getAttributeNode(r))&&a.nodeValue!==!1?r.toLowerCase():n},set:function(t,n,r){var a;return n===!1?e.removeAttr(t,r):(a=e.propFix[r]||r,a in t&&(t[a]=!0),t.setAttribute(r,r.toLowerCase())),r}},f.test(c)&&r("jQueryHW2.fn.attr('"+c+"') may use property instead of attribute")),s.call(e,t,a,i))},e.attrHooks.value={get:function(e,t){var n=(e.nodeName||"").toLowerCase();return"button"===n?u.apply(this,arguments):("input"!==n&&"option"!==n&&r("jQueryHW2.fn.attr('value') no longer gets properties"),t in e?e.value:null)},set:function(e,t){var a=(e.nodeName||"").toLowerCase();return"button"===a?c.apply(this,arguments):("input"!==a&&"option"!==a&&r("jQueryHW2.fn.attr('value', val) no longer sets properties"),e.value=t,n)}};var g,h,v=e.fn.init,m=e.parseJSON,y=/^([^<]*)(<[\w\W]+>)([^>]*)$/;e.fn.init=function(t,n,a){var i;return t&&"string"==typeof t&&!e.isPlainObject(n)&&(i=y.exec(e.trim(t)))&&i[0]&&("<"!==t.charAt(0)&&r("$(html) HTML strings must start with '<' character"),i[3]&&r("$(html) HTML text after last tag is ignored"),"#"===i[0].charAt(0)&&(r("HTML string cannot start with a '#' character"),e.error("JQMIGRATE: Invalid selector string (XSS)")),n&&n.context&&(n=n.context),e.parseHTML)?v.call(this,e.parseHTML(i[2],n,!0),n,a):v.apply(this,arguments)},e.fn.init.prototype=e.fn,e.parseJSON=function(e){return e||null===e?m.apply(this,arguments):(r("jQueryHW2.parseJSON requires a valid JSON string"),null)},e.uaMatch=function(e){e=e.toLowerCase();var t=/(chrome)[ \/]([\w.]+)/.exec(e)||/(webkit)[ \/]([\w.]+)/.exec(e)||/(opera)(?:.*version|)[ \/]([\w.]+)/.exec(e)||/(msie) ([\w.]+)/.exec(e)||0>e.indexOf("compatible")&&/(mozilla)(?:.*? rv:([\w.]+)|)/.exec(e)||[];return{browser:t[1]||"",version:t[2]||"0"}},e.browser||(g=e.uaMatch(navigator.userAgent),h={},g.browser&&(h[g.browser]=!0,h.version=g.version),h.chrome?h.webkit=!0:h.webkit&&(h.safari=!0),e.browser=h),a(e,"browser",e.browser,"jQueryHW2.browser is deprecated"),e.sub=function(){function t(e,n){return new t.fn.init(e,n)}e.extend(!0,t,this),t.superclass=this,t.fn=t.prototype=this(),t.fn.constructor=t,t.sub=this.sub,t.fn.init=function(r,a){return a&&a instanceof e&&!(a instanceof t)&&(a=t(a)),e.fn.init.call(this,r,a,n)},t.fn.init.prototype=t.fn;var n=t(document);return r("jQueryHW2.sub() is deprecated"),t},e.ajaxSetup({converters:{"text json":e.parseJSON}});var b=e.fn.data;e.fn.data=function(t){var a,i,o=this[0];return!o||"events"!==t||1!==arguments.length||(a=e.data(o,t),i=e._data(o,t),a!==n&&a!==i||i===n)?b.apply(this,arguments):(r("Use of jQueryHW2.fn.data('events') is deprecated"),i)};var j=/\/(java|ecma)script/i,w=e.fn.andSelf||e.fn.addBack;e.fn.andSelf=function(){return r("jQueryHW2.fn.andSelf() replaced by jQueryHW2.fn.addBack()"),w.apply(this,arguments)},e.clean||(e.clean=function(t,a,i,o){a=a||document,a=!a.nodeType&&a[0]||a,a=a.ownerDocument||a,r("jQueryHW2.clean() is deprecated");var s,u,c,l,d=[];if(e.merge(d,e.buildFragment(t,a).childNodes),i)for(c=function(e){return!e.type||j.test(e.type)?o?o.push(e.parentNode?e.parentNode.removeChild(e):e):i.appendChild(e):n},s=0;null!=(u=d[s]);s++)e.nodeName(u,"script")&&c(u)||(i.appendChild(u),u.getElementsByTagName!==n&&(l=e.grep(e.merge([],u.getElementsByTagName("script")),c),d.splice.apply(d,[s+1,0].concat(l)),s+=l.length));return d});var Q=e.event.add,x=e.event.remove,k=e.event.trigger,N=e.fn.toggle,T=e.fn.live,M=e.fn.die,S="ajaxStart|ajaxStop|ajaxSend|ajaxComplete|ajaxError|ajaxSuccess",C=RegExp("\\b(?:"+S+")\\b"),H=/(?:^|\s)hover(\.\S+|)\b/,A=function(t){return"string"!=typeof t||e.event.special.hover?t:(H.test(t)&&r("'hover' pseudo-event is deprecated, use 'mouseenter mouseleave'"),t&&t.replace(H,"mouseenter$1 mouseleave$1"))};e.event.props&&"attrChange"!==e.event.props[0]&&e.event.props.unshift("attrChange","attrName","relatedNode","srcElement"),e.event.dispatch&&a(e.event,"handle",e.event.dispatch,"jQueryHW2.event.handle is undocumented and deprecated"),e.event.add=function(e,t,n,a,i){e!==document&&C.test(t)&&r("AJAX events should be attached to document: "+t),Q.call(this,e,A(t||""),n,a,i)},e.event.remove=function(e,t,n,r,a){x.call(this,e,A(t)||"",n,r,a)},e.fn.error=function(){var e=Array.prototype.slice.call(arguments,0);return r("jQueryHW2.fn.error() is deprecated"),e.splice(0,0,"error"),arguments.length?this.bind.apply(this,e):(this.triggerHandler.apply(this,e),this)},e.fn.toggle=function(t,n){if(!e.isFunction(t)||!e.isFunction(n))return N.apply(this,arguments);r("jQueryHW2.fn.toggle(handler, handler...) is deprecated");var a=arguments,i=t.guid||e.guid++,o=0,s=function(n){var r=(e._data(this,"lastToggle"+t.guid)||0)%o;return e._data(this,"lastToggle"+t.guid,r+1),n.preventDefault(),a[r].apply(this,arguments)||!1};for(s.guid=i;a.length>o;)a[o++].guid=i;return this.click(s)},e.fn.live=function(t,n,a){return r("jQueryHW2.fn.live() is deprecated"),T?T.apply(this,arguments):(e(this.context).on(t,this.selector,n,a),this)},e.fn.die=function(t,n){return r("jQueryHW2.fn.die() is deprecated"),M?M.apply(this,arguments):(e(this.context).off(t,this.selector||"**",n),this)},e.event.trigger=function(e,t,n,a){return n||C.test(e)||r("Global events are undocumented and deprecated"),k.call(this,e,t,n||document,a)},e.each(S.split("|"),function(t,n){e.event.special[n]={setup:function(){var t=this;return t!==document&&(e.event.add(document,n+"."+e.guid,function(){e.event.trigger(n,null,t,!0)}),e._data(this,n,e.guid++)),!1},teardown:function(){return this!==document&&e.event.remove(document,n+"."+e._data(this,n)),!1}}})}(jQueryHW2,window); \ No newline at end of file diff --git a/docs/dws/umn/public_sys-resources/jquery-ui.min.js b/docs/dws/umn/public_sys-resources/jquery-ui.min.js new file mode 100644 index 00000000..50b036f4 --- /dev/null +++ b/docs/dws/umn/public_sys-resources/jquery-ui.min.js @@ -0,0 +1,6 @@ +/*! jQuery UI - v1.13.2 - 2022-07-14 +* http://jqueryui.com +* Includes: widget.js, position.js, data.js, disable-selection.js, effect.js, effects/effect-blind.js, effects/effect-bounce.js, effects/effect-clip.js, effects/effect-drop.js, effects/effect-explode.js, effects/effect-fade.js, effects/effect-fold.js, effects/effect-highlight.js, effects/effect-puff.js, effects/effect-pulsate.js, effects/effect-scale.js, effects/effect-shake.js, effects/effect-size.js, effects/effect-slide.js, effects/effect-transfer.js, focusable.js, form-reset-mixin.js, jquery-patch.js, keycode.js, labels.js, scroll-parent.js, tabbable.js, unique-id.js, widgets/accordion.js, widgets/autocomplete.js, widgets/button.js, widgets/checkboxradio.js, widgets/controlgroup.js, widgets/datepicker.js, widgets/dialog.js, widgets/draggable.js, widgets/droppable.js, widgets/menu.js, widgets/mouse.js, widgets/progressbar.js, widgets/resizable.js, widgets/selectable.js, widgets/selectmenu.js, widgets/slider.js, widgets/sortable.js, widgets/spinner.js, widgets/tabs.js, widgets/tooltip.js +* Copyright jQuery Foundation and other contributors; Licensed MIT */ + +!function(t){"use strict";"function"==typeof define&&define.amd?define(["jquery"],t):t(jQuery)}(function(V){"use strict";V.ui=V.ui||{};V.ui.version="1.13.2";var n,i=0,a=Array.prototype.hasOwnProperty,r=Array.prototype.slice;V.cleanData=(n=V.cleanData,function(t){for(var e,i,s=0;null!=(i=t[s]);s++)(e=V._data(i,"events"))&&e.remove&&V(i).triggerHandler("remove");n(t)}),V.widget=function(t,i,e){var s,n,o,a={},r=t.split(".")[0],l=r+"-"+(t=t.split(".")[1]);return e||(e=i,i=V.Widget),Array.isArray(e)&&(e=V.extend.apply(null,[{}].concat(e))),V.expr.pseudos[l.toLowerCase()]=function(t){return!!V.data(t,l)},V[r]=V[r]||{},s=V[r][t],n=V[r][t]=function(t,e){if(!this||!this._createWidget)return new n(t,e);arguments.length&&this._createWidget(t,e)},V.extend(n,s,{version:e.version,_proto:V.extend({},e),_childConstructors:[]}),(o=new i).options=V.widget.extend({},o.options),V.each(e,function(e,s){function n(){return i.prototype[e].apply(this,arguments)}function o(t){return i.prototype[e].apply(this,t)}a[e]="function"==typeof s?function(){var t,e=this._super,i=this._superApply;return this._super=n,this._superApply=o,t=s.apply(this,arguments),this._super=e,this._superApply=i,t}:s}),n.prototype=V.widget.extend(o,{widgetEventPrefix:s&&o.widgetEventPrefix||t},a,{constructor:n,namespace:r,widgetName:t,widgetFullName:l}),s?(V.each(s._childConstructors,function(t,e){var i=e.prototype;V.widget(i.namespace+"."+i.widgetName,n,e._proto)}),delete s._childConstructors):i._childConstructors.push(n),V.widget.bridge(t,n),n},V.widget.extend=function(t){for(var e,i,s=r.call(arguments,1),n=0,o=s.length;n",options:{classes:{},disabled:!1,create:null},_createWidget:function(t,e){e=V(e||this.defaultElement||this)[0],this.element=V(e),this.uuid=i++,this.eventNamespace="."+this.widgetName+this.uuid,this.bindings=V(),this.hoverable=V(),this.focusable=V(),this.classesElementLookup={},e!==this&&(V.data(e,this.widgetFullName,this),this._on(!0,this.element,{remove:function(t){t.target===e&&this.destroy()}}),this.document=V(e.style?e.ownerDocument:e.document||e),this.window=V(this.document[0].defaultView||this.document[0].parentWindow)),this.options=V.widget.extend({},this.options,this._getCreateOptions(),t),this._create(),this.options.disabled&&this._setOptionDisabled(this.options.disabled),this._trigger("create",null,this._getCreateEventData()),this._init()},_getCreateOptions:function(){return{}},_getCreateEventData:V.noop,_create:V.noop,_init:V.noop,destroy:function(){var i=this;this._destroy(),V.each(this.classesElementLookup,function(t,e){i._removeClass(e,t)}),this.element.off(this.eventNamespace).removeData(this.widgetFullName),this.widget().off(this.eventNamespace).removeAttr("aria-disabled"),this.bindings.off(this.eventNamespace)},_destroy:V.noop,widget:function(){return this.element},option:function(t,e){var i,s,n,o=t;if(0===arguments.length)return V.widget.extend({},this.options);if("string"==typeof t)if(o={},t=(i=t.split(".")).shift(),i.length){for(s=o[t]=V.widget.extend({},this.options[t]),n=0;n
"),i=e.children()[0];return V("body").append(e),t=i.offsetWidth,e.css("overflow","scroll"),t===(i=i.offsetWidth)&&(i=e[0].clientWidth),e.remove(),s=t-i},getScrollInfo:function(t){var e=t.isWindow||t.isDocument?"":t.element.css("overflow-x"),i=t.isWindow||t.isDocument?"":t.element.css("overflow-y"),e="scroll"===e||"auto"===e&&t.widthx(k(s),k(n))?o.important="horizontal":o.important="vertical",u.using.call(this,t,o)}),a.offset(V.extend(h,{using:t}))})},V.ui.position={fit:{left:function(t,e){var i=e.within,s=i.isWindow?i.scrollLeft:i.offset.left,n=i.width,o=t.left-e.collisionPosition.marginLeft,a=s-o,r=o+e.collisionWidth-n-s;e.collisionWidth>n?0n?0")[0],w=d.each;function P(t){return null==t?t+"":"object"==typeof t?p[e.call(t)]||"object":typeof t}function M(t,e,i){var s=v[e.type]||{};return null==t?i||!e.def?null:e.def:(t=s.floor?~~t:parseFloat(t),isNaN(t)?e.def:s.mod?(t+s.mod)%s.mod:Math.min(s.max,Math.max(0,t)))}function S(s){var n=m(),o=n._rgba=[];return s=s.toLowerCase(),w(g,function(t,e){var i=e.re.exec(s),i=i&&e.parse(i),e=e.space||"rgba";if(i)return i=n[e](i),n[_[e].cache]=i[_[e].cache],o=n._rgba=i._rgba,!1}),o.length?("0,0,0,0"===o.join()&&d.extend(o,B.transparent),n):B[s]}function H(t,e,i){return 6*(i=(i+1)%1)<1?t+(e-t)*i*6:2*i<1?e:3*i<2?t+(e-t)*(2/3-i)*6:t}y.style.cssText="background-color:rgba(1,1,1,.5)",b.rgba=-1o.mod/2?s+=o.mod:s-n>o.mod/2&&(s-=o.mod)),l[i]=M((n-s)*a+s,e)))}),this[e](l)},blend:function(t){if(1===this._rgba[3])return this;var e=this._rgba.slice(),i=e.pop(),s=m(t)._rgba;return m(d.map(e,function(t,e){return(1-i)*s[e]+i*t}))},toRgbaString:function(){var t="rgba(",e=d.map(this._rgba,function(t,e){return null!=t?t:2").addClass("ui-effects-wrapper").css({fontSize:"100%",background:"transparent",border:"none",margin:0,padding:0}),e={width:i.width(),height:i.height()},n=document.activeElement;try{n.id}catch(t){n=document.body}return i.wrap(t),i[0]!==n&&!V.contains(i[0],n)||V(n).trigger("focus"),t=i.parent(),"static"===i.css("position")?(t.css({position:"relative"}),i.css({position:"relative"})):(V.extend(s,{position:i.css("position"),zIndex:i.css("z-index")}),V.each(["top","left","bottom","right"],function(t,e){s[e]=i.css(e),isNaN(parseInt(s[e],10))&&(s[e]="auto")}),i.css({position:"relative",top:0,left:0,right:"auto",bottom:"auto"})),i.css(e),t.css(s).show()},removeWrapper:function(t){var e=document.activeElement;return t.parent().is(".ui-effects-wrapper")&&(t.parent().replaceWith(t),t[0]!==e&&!V.contains(t[0],e)||V(e).trigger("focus")),t}}),V.extend(V.effects,{version:"1.13.2",define:function(t,e,i){return i||(i=e,e="effect"),V.effects.effect[t]=i,V.effects.effect[t].mode=e,i},scaledDimensions:function(t,e,i){if(0===e)return{height:0,width:0,outerHeight:0,outerWidth:0};var s="horizontal"!==i?(e||100)/100:1,e="vertical"!==i?(e||100)/100:1;return{height:t.height()*e,width:t.width()*s,outerHeight:t.outerHeight()*e,outerWidth:t.outerWidth()*s}},clipToBox:function(t){return{width:t.clip.right-t.clip.left,height:t.clip.bottom-t.clip.top,left:t.clip.left,top:t.clip.top}},unshift:function(t,e,i){var s=t.queue();1").insertAfter(t).css({display:/^(inline|ruby)/.test(t.css("display"))?"inline-block":"block",visibility:"hidden",marginTop:t.css("marginTop"),marginBottom:t.css("marginBottom"),marginLeft:t.css("marginLeft"),marginRight:t.css("marginRight"),float:t.css("float")}).outerWidth(t.outerWidth()).outerHeight(t.outerHeight()).addClass("ui-effects-placeholder"),t.data(j+"placeholder",e)),t.css({position:i,left:s.left,top:s.top}),e},removePlaceholder:function(t){var e=j+"placeholder",i=t.data(e);i&&(i.remove(),t.removeData(e))},cleanUp:function(t){V.effects.restoreStyle(t),V.effects.removePlaceholder(t)},setTransition:function(s,t,n,o){return o=o||{},V.each(t,function(t,e){var i=s.cssUnit(e);0");l.appendTo("body").addClass(t.className).css({top:s.top-a,left:s.left-r,height:i.innerHeight(),width:i.innerWidth(),position:n?"fixed":"absolute"}).animate(o,t.duration,t.easing,function(){l.remove(),"function"==typeof e&&e()})}}),V.fx.step.clip=function(t){t.clipInit||(t.start=V(t.elem).cssClip(),"string"==typeof t.end&&(t.end=G(t.end,t.elem)),t.clipInit=!0),V(t.elem).cssClip({top:t.pos*(t.end.top-t.start.top)+t.start.top,right:t.pos*(t.end.right-t.start.right)+t.start.right,bottom:t.pos*(t.end.bottom-t.start.bottom)+t.start.bottom,left:t.pos*(t.end.left-t.start.left)+t.start.left})},Y={},V.each(["Quad","Cubic","Quart","Quint","Expo"],function(e,t){Y[t]=function(t){return Math.pow(t,e+2)}}),V.extend(Y,{Sine:function(t){return 1-Math.cos(t*Math.PI/2)},Circ:function(t){return 1-Math.sqrt(1-t*t)},Elastic:function(t){return 0===t||1===t?t:-Math.pow(2,8*(t-1))*Math.sin((80*(t-1)-7.5)*Math.PI/15)},Back:function(t){return t*t*(3*t-2)},Bounce:function(t){for(var e,i=4;t<((e=Math.pow(2,--i))-1)/11;);return 1/Math.pow(4,3-i)-7.5625*Math.pow((3*e-2)/22-t,2)}}),V.each(Y,function(t,e){V.easing["easeIn"+t]=e,V.easing["easeOut"+t]=function(t){return 1-e(1-t)},V.easing["easeInOut"+t]=function(t){return t<.5?e(2*t)/2:1-e(-2*t+2)/2}});y=V.effects,V.effects.define("blind","hide",function(t,e){var i={up:["bottom","top"],vertical:["bottom","top"],down:["top","bottom"],left:["right","left"],horizontal:["right","left"],right:["left","right"]},s=V(this),n=t.direction||"up",o=s.cssClip(),a={clip:V.extend({},o)},r=V.effects.createPlaceholder(s);a.clip[i[n][0]]=a.clip[i[n][1]],"show"===t.mode&&(s.cssClip(a.clip),r&&r.css(V.effects.clipToBox(a)),a.clip=o),r&&r.animate(V.effects.clipToBox(a),t.duration,t.easing),s.animate(a,{queue:!1,duration:t.duration,easing:t.easing,complete:e})}),V.effects.define("bounce",function(t,e){var i,s,n=V(this),o=t.mode,a="hide"===o,r="show"===o,l=t.direction||"up",h=t.distance,c=t.times||5,o=2*c+(r||a?1:0),u=t.duration/o,d=t.easing,p="up"===l||"down"===l?"top":"left",f="up"===l||"left"===l,g=0,t=n.queue().length;for(V.effects.createPlaceholder(n),l=n.css(p),h=h||n["top"==p?"outerHeight":"outerWidth"]()/3,r&&((s={opacity:1})[p]=l,n.css("opacity",0).css(p,f?2*-h:2*h).animate(s,u,d)),a&&(h/=Math.pow(2,c-1)),(s={})[p]=l;g").css({position:"absolute",visibility:"visible",left:-s*p,top:-i*f}).parent().addClass("ui-effects-explode").css({position:"absolute",overflow:"hidden",width:p,height:f,left:n+(u?a*p:0),top:o+(u?r*f:0),opacity:u?0:1}).animate({left:n+(u?0:a*p),top:o+(u?0:r*f),opacity:u?1:0},t.duration||500,t.easing,m)}),V.effects.define("fade","toggle",function(t,e){var i="show"===t.mode;V(this).css("opacity",i?0:1).animate({opacity:i?1:0},{queue:!1,duration:t.duration,easing:t.easing,complete:e})}),V.effects.define("fold","hide",function(e,t){var i=V(this),s=e.mode,n="show"===s,o="hide"===s,a=e.size||15,r=/([0-9]+)%/.exec(a),l=!!e.horizFirst?["right","bottom"]:["bottom","right"],h=e.duration/2,c=V.effects.createPlaceholder(i),u=i.cssClip(),d={clip:V.extend({},u)},p={clip:V.extend({},u)},f=[u[l[0]],u[l[1]]],s=i.queue().length;r&&(a=parseInt(r[1],10)/100*f[o?0:1]),d.clip[l[0]]=a,p.clip[l[0]]=a,p.clip[l[1]]=0,n&&(i.cssClip(p.clip),c&&c.css(V.effects.clipToBox(p)),p.clip=u),i.queue(function(t){c&&c.animate(V.effects.clipToBox(d),h,e.easing).animate(V.effects.clipToBox(p),h,e.easing),t()}).animate(d,h,e.easing).animate(p,h,e.easing).queue(t),V.effects.unshift(i,s,4)}),V.effects.define("highlight","show",function(t,e){var i=V(this),s={backgroundColor:i.css("backgroundColor")};"hide"===t.mode&&(s.opacity=0),V.effects.saveStyle(i),i.css({backgroundImage:"none",backgroundColor:t.color||"#ffff99"}).animate(s,{queue:!1,duration:t.duration,easing:t.easing,complete:e})}),V.effects.define("size",function(s,e){var n,i=V(this),t=["fontSize"],o=["borderTopWidth","borderBottomWidth","paddingTop","paddingBottom"],a=["borderLeftWidth","borderRightWidth","paddingLeft","paddingRight"],r=s.mode,l="effect"!==r,h=s.scale||"both",c=s.origin||["middle","center"],u=i.css("position"),d=i.position(),p=V.effects.scaledDimensions(i),f=s.from||p,g=s.to||V.effects.scaledDimensions(i,0);V.effects.createPlaceholder(i),"show"===r&&(r=f,f=g,g=r),n={from:{y:f.height/p.height,x:f.width/p.width},to:{y:g.height/p.height,x:g.width/p.width}},"box"!==h&&"both"!==h||(n.from.y!==n.to.y&&(f=V.effects.setTransition(i,o,n.from.y,f),g=V.effects.setTransition(i,o,n.to.y,g)),n.from.x!==n.to.x&&(f=V.effects.setTransition(i,a,n.from.x,f),g=V.effects.setTransition(i,a,n.to.x,g))),"content"!==h&&"both"!==h||n.from.y!==n.to.y&&(f=V.effects.setTransition(i,t,n.from.y,f),g=V.effects.setTransition(i,t,n.to.y,g)),c&&(c=V.effects.getBaseline(c,p),f.top=(p.outerHeight-f.outerHeight)*c.y+d.top,f.left=(p.outerWidth-f.outerWidth)*c.x+d.left,g.top=(p.outerHeight-g.outerHeight)*c.y+d.top,g.left=(p.outerWidth-g.outerWidth)*c.x+d.left),delete f.outerHeight,delete f.outerWidth,i.css(f),"content"!==h&&"both"!==h||(o=o.concat(["marginTop","marginBottom"]).concat(t),a=a.concat(["marginLeft","marginRight"]),i.find("*[width]").each(function(){var t=V(this),e=V.effects.scaledDimensions(t),i={height:e.height*n.from.y,width:e.width*n.from.x,outerHeight:e.outerHeight*n.from.y,outerWidth:e.outerWidth*n.from.x},e={height:e.height*n.to.y,width:e.width*n.to.x,outerHeight:e.height*n.to.y,outerWidth:e.width*n.to.x};n.from.y!==n.to.y&&(i=V.effects.setTransition(t,o,n.from.y,i),e=V.effects.setTransition(t,o,n.to.y,e)),n.from.x!==n.to.x&&(i=V.effects.setTransition(t,a,n.from.x,i),e=V.effects.setTransition(t,a,n.to.x,e)),l&&V.effects.saveStyle(t),t.css(i),t.animate(e,s.duration,s.easing,function(){l&&V.effects.restoreStyle(t)})})),i.animate(g,{queue:!1,duration:s.duration,easing:s.easing,complete:function(){var t=i.offset();0===g.opacity&&i.css("opacity",f.opacity),l||(i.css("position","static"===u?"relative":u).offset(t),V.effects.saveStyle(i)),e()}})}),V.effects.define("scale",function(t,e){var i=V(this),s=t.mode,s=parseInt(t.percent,10)||(0===parseInt(t.percent,10)||"effect"!==s?0:100),s=V.extend(!0,{from:V.effects.scaledDimensions(i),to:V.effects.scaledDimensions(i,s,t.direction||"both"),origin:t.origin||["middle","center"]},t);t.fade&&(s.from.opacity=1,s.to.opacity=0),V.effects.effect.size.call(this,s,e)}),V.effects.define("puff","hide",function(t,e){t=V.extend(!0,{},t,{fade:!0,percent:parseInt(t.percent,10)||150});V.effects.effect.scale.call(this,t,e)}),V.effects.define("pulsate","show",function(t,e){var i=V(this),s=t.mode,n="show"===s,o=2*(t.times||5)+(n||"hide"===s?1:0),a=t.duration/o,r=0,l=1,s=i.queue().length;for(!n&&i.is(":visible")||(i.css("opacity",0).show(),r=1);l li > :first-child").add(t.find("> :not(li)").even())},heightStyle:"auto",icons:{activeHeader:"ui-icon-triangle-1-s",header:"ui-icon-triangle-1-e"},activate:null,beforeActivate:null},hideProps:{borderTopWidth:"hide",borderBottomWidth:"hide",paddingTop:"hide",paddingBottom:"hide",height:"hide"},showProps:{borderTopWidth:"show",borderBottomWidth:"show",paddingTop:"show",paddingBottom:"show",height:"show"},_create:function(){var t=this.options;this.prevShow=this.prevHide=V(),this._addClass("ui-accordion","ui-widget ui-helper-reset"),this.element.attr("role","tablist"),t.collapsible||!1!==t.active&&null!=t.active||(t.active=0),this._processPanels(),t.active<0&&(t.active+=this.headers.length),this._refresh()},_getCreateEventData:function(){return{header:this.active,panel:this.active.length?this.active.next():V()}},_createIcons:function(){var t,e=this.options.icons;e&&(t=V(""),this._addClass(t,"ui-accordion-header-icon","ui-icon "+e.header),t.prependTo(this.headers),t=this.active.children(".ui-accordion-header-icon"),this._removeClass(t,e.header)._addClass(t,null,e.activeHeader)._addClass(this.headers,"ui-accordion-icons"))},_destroyIcons:function(){this._removeClass(this.headers,"ui-accordion-icons"),this.headers.children(".ui-accordion-header-icon").remove()},_destroy:function(){var t;this.element.removeAttr("role"),this.headers.removeAttr("role aria-expanded aria-selected aria-controls tabIndex").removeUniqueId(),this._destroyIcons(),t=this.headers.next().css("display","").removeAttr("role aria-hidden aria-labelledby").removeUniqueId(),"content"!==this.options.heightStyle&&t.css("height","")},_setOption:function(t,e){"active"!==t?("event"===t&&(this.options.event&&this._off(this.headers,this.options.event),this._setupEvents(e)),this._super(t,e),"collapsible"!==t||e||!1!==this.options.active||this._activate(0),"icons"===t&&(this._destroyIcons(),e&&this._createIcons())):this._activate(e)},_setOptionDisabled:function(t){this._super(t),this.element.attr("aria-disabled",t),this._toggleClass(null,"ui-state-disabled",!!t),this._toggleClass(this.headers.add(this.headers.next()),null,"ui-state-disabled",!!t)},_keydown:function(t){if(!t.altKey&&!t.ctrlKey){var e=V.ui.keyCode,i=this.headers.length,s=this.headers.index(t.target),n=!1;switch(t.keyCode){case e.RIGHT:case e.DOWN:n=this.headers[(s+1)%i];break;case e.LEFT:case e.UP:n=this.headers[(s-1+i)%i];break;case e.SPACE:case e.ENTER:this._eventHandler(t);break;case e.HOME:n=this.headers[0];break;case e.END:n=this.headers[i-1]}n&&(V(t.target).attr("tabIndex",-1),V(n).attr("tabIndex",0),V(n).trigger("focus"),t.preventDefault())}},_panelKeyDown:function(t){t.keyCode===V.ui.keyCode.UP&&t.ctrlKey&&V(t.currentTarget).prev().trigger("focus")},refresh:function(){var t=this.options;this._processPanels(),!1===t.active&&!0===t.collapsible||!this.headers.length?(t.active=!1,this.active=V()):!1===t.active?this._activate(0):this.active.length&&!V.contains(this.element[0],this.active[0])?this.headers.length===this.headers.find(".ui-state-disabled").length?(t.active=!1,this.active=V()):this._activate(Math.max(0,t.active-1)):t.active=this.headers.index(this.active),this._destroyIcons(),this._refresh()},_processPanels:function(){var t=this.headers,e=this.panels;"function"==typeof this.options.header?this.headers=this.options.header(this.element):this.headers=this.element.find(this.options.header),this._addClass(this.headers,"ui-accordion-header ui-accordion-header-collapsed","ui-state-default"),this.panels=this.headers.next().filter(":not(.ui-accordion-content-active)").hide(),this._addClass(this.panels,"ui-accordion-content","ui-helper-reset ui-widget-content"),e&&(this._off(t.not(this.headers)),this._off(e.not(this.panels)))},_refresh:function(){var i,t=this.options,e=t.heightStyle,s=this.element.parent();this.active=this._findActive(t.active),this._addClass(this.active,"ui-accordion-header-active","ui-state-active")._removeClass(this.active,"ui-accordion-header-collapsed"),this._addClass(this.active.next(),"ui-accordion-content-active"),this.active.next().show(),this.headers.attr("role","tab").each(function(){var t=V(this),e=t.uniqueId().attr("id"),i=t.next(),s=i.uniqueId().attr("id");t.attr("aria-controls",s),i.attr("aria-labelledby",e)}).next().attr("role","tabpanel"),this.headers.not(this.active).attr({"aria-selected":"false","aria-expanded":"false",tabIndex:-1}).next().attr({"aria-hidden":"true"}).hide(),this.active.length?this.active.attr({"aria-selected":"true","aria-expanded":"true",tabIndex:0}).next().attr({"aria-hidden":"false"}):this.headers.eq(0).attr("tabIndex",0),this._createIcons(),this._setupEvents(t.event),"fill"===e?(i=s.height(),this.element.siblings(":visible").each(function(){var t=V(this),e=t.css("position");"absolute"!==e&&"fixed"!==e&&(i-=t.outerHeight(!0))}),this.headers.each(function(){i-=V(this).outerHeight(!0)}),this.headers.next().each(function(){V(this).height(Math.max(0,i-V(this).innerHeight()+V(this).height()))}).css("overflow","auto")):"auto"===e&&(i=0,this.headers.next().each(function(){var t=V(this).is(":visible");t||V(this).show(),i=Math.max(i,V(this).css("height","").height()),t||V(this).hide()}).height(i))},_activate:function(t){t=this._findActive(t)[0];t!==this.active[0]&&(t=t||this.active[0],this._eventHandler({target:t,currentTarget:t,preventDefault:V.noop}))},_findActive:function(t){return"number"==typeof t?this.headers.eq(t):V()},_setupEvents:function(t){var i={keydown:"_keydown"};t&&V.each(t.split(" "),function(t,e){i[e]="_eventHandler"}),this._off(this.headers.add(this.headers.next())),this._on(this.headers,i),this._on(this.headers.next(),{keydown:"_panelKeyDown"}),this._hoverable(this.headers),this._focusable(this.headers)},_eventHandler:function(t){var e=this.options,i=this.active,s=V(t.currentTarget),n=s[0]===i[0],o=n&&e.collapsible,a=o?V():s.next(),r=i.next(),a={oldHeader:i,oldPanel:r,newHeader:o?V():s,newPanel:a};t.preventDefault(),n&&!e.collapsible||!1===this._trigger("beforeActivate",t,a)||(e.active=!o&&this.headers.index(s),this.active=n?V():s,this._toggle(a),this._removeClass(i,"ui-accordion-header-active","ui-state-active"),e.icons&&(i=i.children(".ui-accordion-header-icon"),this._removeClass(i,null,e.icons.activeHeader)._addClass(i,null,e.icons.header)),n||(this._removeClass(s,"ui-accordion-header-collapsed")._addClass(s,"ui-accordion-header-active","ui-state-active"),e.icons&&(n=s.children(".ui-accordion-header-icon"),this._removeClass(n,null,e.icons.header)._addClass(n,null,e.icons.activeHeader)),this._addClass(s.next(),"ui-accordion-content-active")))},_toggle:function(t){var e=t.newPanel,i=this.prevShow.length?this.prevShow:t.oldPanel;this.prevShow.add(this.prevHide).stop(!0,!0),this.prevShow=e,this.prevHide=i,this.options.animate?this._animate(e,i,t):(i.hide(),e.show(),this._toggleComplete(t)),i.attr({"aria-hidden":"true"}),i.prev().attr({"aria-selected":"false","aria-expanded":"false"}),e.length&&i.length?i.prev().attr({tabIndex:-1,"aria-expanded":"false"}):e.length&&this.headers.filter(function(){return 0===parseInt(V(this).attr("tabIndex"),10)}).attr("tabIndex",-1),e.attr("aria-hidden","false").prev().attr({"aria-selected":"true","aria-expanded":"true",tabIndex:0})},_animate:function(t,i,e){var s,n,o,a=this,r=0,l=t.css("box-sizing"),h=t.length&&(!i.length||t.index()",delay:300,options:{icons:{submenu:"ui-icon-caret-1-e"},items:"> *",menus:"ul",position:{my:"left top",at:"right top"},role:"menu",blur:null,focus:null,select:null},_create:function(){this.activeMenu=this.element,this.mouseHandled=!1,this.lastMousePosition={x:null,y:null},this.element.uniqueId().attr({role:this.options.role,tabIndex:0}),this._addClass("ui-menu","ui-widget ui-widget-content"),this._on({"mousedown .ui-menu-item":function(t){t.preventDefault(),this._activateItem(t)},"click .ui-menu-item":function(t){var e=V(t.target),i=V(V.ui.safeActiveElement(this.document[0]));!this.mouseHandled&&e.not(".ui-state-disabled").length&&(this.select(t),t.isPropagationStopped()||(this.mouseHandled=!0),e.has(".ui-menu").length?this.expand(t):!this.element.is(":focus")&&i.closest(".ui-menu").length&&(this.element.trigger("focus",[!0]),this.active&&1===this.active.parents(".ui-menu").length&&clearTimeout(this.timer)))},"mouseenter .ui-menu-item":"_activateItem","mousemove .ui-menu-item":"_activateItem",mouseleave:"collapseAll","mouseleave .ui-menu":"collapseAll",focus:function(t,e){var i=this.active||this._menuItems().first();e||this.focus(t,i)},blur:function(t){this._delay(function(){V.contains(this.element[0],V.ui.safeActiveElement(this.document[0]))||this.collapseAll(t)})},keydown:"_keydown"}),this.refresh(),this._on(this.document,{click:function(t){this._closeOnDocumentClick(t)&&this.collapseAll(t,!0),this.mouseHandled=!1}})},_activateItem:function(t){var e,i;this.previousFilter||t.clientX===this.lastMousePosition.x&&t.clientY===this.lastMousePosition.y||(this.lastMousePosition={x:t.clientX,y:t.clientY},e=V(t.target).closest(".ui-menu-item"),i=V(t.currentTarget),e[0]===i[0]&&(i.is(".ui-state-active")||(this._removeClass(i.siblings().children(".ui-state-active"),null,"ui-state-active"),this.focus(t,i))))},_destroy:function(){var t=this.element.find(".ui-menu-item").removeAttr("role aria-disabled").children(".ui-menu-item-wrapper").removeUniqueId().removeAttr("tabIndex role aria-haspopup");this.element.removeAttr("aria-activedescendant").find(".ui-menu").addBack().removeAttr("role aria-labelledby aria-expanded aria-hidden aria-disabled tabIndex").removeUniqueId().show(),t.children().each(function(){var t=V(this);t.data("ui-menu-submenu-caret")&&t.remove()})},_keydown:function(t){var e,i,s,n=!0;switch(t.keyCode){case V.ui.keyCode.PAGE_UP:this.previousPage(t);break;case V.ui.keyCode.PAGE_DOWN:this.nextPage(t);break;case V.ui.keyCode.HOME:this._move("first","first",t);break;case V.ui.keyCode.END:this._move("last","last",t);break;case V.ui.keyCode.UP:this.previous(t);break;case V.ui.keyCode.DOWN:this.next(t);break;case V.ui.keyCode.LEFT:this.collapse(t);break;case V.ui.keyCode.RIGHT:this.active&&!this.active.is(".ui-state-disabled")&&this.expand(t);break;case V.ui.keyCode.ENTER:case V.ui.keyCode.SPACE:this._activate(t);break;case V.ui.keyCode.ESCAPE:this.collapse(t);break;default:e=this.previousFilter||"",s=n=!1,i=96<=t.keyCode&&t.keyCode<=105?(t.keyCode-96).toString():String.fromCharCode(t.keyCode),clearTimeout(this.filterTimer),i===e?s=!0:i=e+i,e=this._filterMenuItems(i),(e=s&&-1!==e.index(this.active.next())?this.active.nextAll(".ui-menu-item"):e).length||(i=String.fromCharCode(t.keyCode),e=this._filterMenuItems(i)),e.length?(this.focus(t,e),this.previousFilter=i,this.filterTimer=this._delay(function(){delete this.previousFilter},1e3)):delete this.previousFilter}n&&t.preventDefault()},_activate:function(t){this.active&&!this.active.is(".ui-state-disabled")&&(this.active.children("[aria-haspopup='true']").length?this.expand(t):this.select(t))},refresh:function(){var t,e,s=this,n=this.options.icons.submenu,i=this.element.find(this.options.menus);this._toggleClass("ui-menu-icons",null,!!this.element.find(".ui-icon").length),e=i.filter(":not(.ui-menu)").hide().attr({role:this.options.role,"aria-hidden":"true","aria-expanded":"false"}).each(function(){var t=V(this),e=t.prev(),i=V("").data("ui-menu-submenu-caret",!0);s._addClass(i,"ui-menu-icon","ui-icon "+n),e.attr("aria-haspopup","true").prepend(i),t.attr("aria-labelledby",e.attr("id"))}),this._addClass(e,"ui-menu","ui-widget ui-widget-content ui-front"),(t=i.add(this.element).find(this.options.items)).not(".ui-menu-item").each(function(){var t=V(this);s._isDivider(t)&&s._addClass(t,"ui-menu-divider","ui-widget-content")}),i=(e=t.not(".ui-menu-item, .ui-menu-divider")).children().not(".ui-menu").uniqueId().attr({tabIndex:-1,role:this._itemRole()}),this._addClass(e,"ui-menu-item")._addClass(i,"ui-menu-item-wrapper"),t.filter(".ui-state-disabled").attr("aria-disabled","true"),this.active&&!V.contains(this.element[0],this.active[0])&&this.blur()},_itemRole:function(){return{menu:"menuitem",listbox:"option"}[this.options.role]},_setOption:function(t,e){var i;"icons"===t&&(i=this.element.find(".ui-menu-icon"),this._removeClass(i,null,this.options.icons.submenu)._addClass(i,null,e.submenu)),this._super(t,e)},_setOptionDisabled:function(t){this._super(t),this.element.attr("aria-disabled",String(t)),this._toggleClass(null,"ui-state-disabled",!!t)},focus:function(t,e){var i;this.blur(t,t&&"focus"===t.type),this._scrollIntoView(e),this.active=e.first(),i=this.active.children(".ui-menu-item-wrapper"),this._addClass(i,null,"ui-state-active"),this.options.role&&this.element.attr("aria-activedescendant",i.attr("id")),i=this.active.parent().closest(".ui-menu-item").children(".ui-menu-item-wrapper"),this._addClass(i,null,"ui-state-active"),t&&"keydown"===t.type?this._close():this.timer=this._delay(function(){this._close()},this.delay),(i=e.children(".ui-menu")).length&&t&&/^mouse/.test(t.type)&&this._startOpening(i),this.activeMenu=e.parent(),this._trigger("focus",t,{item:e})},_scrollIntoView:function(t){var e,i,s;this._hasScroll()&&(i=parseFloat(V.css(this.activeMenu[0],"borderTopWidth"))||0,s=parseFloat(V.css(this.activeMenu[0],"paddingTop"))||0,e=t.offset().top-this.activeMenu.offset().top-i-s,i=this.activeMenu.scrollTop(),s=this.activeMenu.height(),t=t.outerHeight(),e<0?this.activeMenu.scrollTop(i+e):s",options:{appendTo:null,autoFocus:!1,delay:300,minLength:1,position:{my:"left top",at:"left bottom",collision:"none"},source:null,change:null,close:null,focus:null,open:null,response:null,search:null,select:null},requestIndex:0,pending:0,liveRegionTimer:null,_create:function(){var i,s,n,t=this.element[0].nodeName.toLowerCase(),e="textarea"===t,t="input"===t;this.isMultiLine=e||!t&&this._isContentEditable(this.element),this.valueMethod=this.element[e||t?"val":"text"],this.isNewMenu=!0,this._addClass("ui-autocomplete-input"),this.element.attr("autocomplete","off"),this._on(this.element,{keydown:function(t){if(this.element.prop("readOnly"))s=n=i=!0;else{s=n=i=!1;var e=V.ui.keyCode;switch(t.keyCode){case e.PAGE_UP:i=!0,this._move("previousPage",t);break;case e.PAGE_DOWN:i=!0,this._move("nextPage",t);break;case e.UP:i=!0,this._keyEvent("previous",t);break;case e.DOWN:i=!0,this._keyEvent("next",t);break;case e.ENTER:this.menu.active&&(i=!0,t.preventDefault(),this.menu.select(t));break;case e.TAB:this.menu.active&&this.menu.select(t);break;case e.ESCAPE:this.menu.element.is(":visible")&&(this.isMultiLine||this._value(this.term),this.close(t),t.preventDefault());break;default:s=!0,this._searchTimeout(t)}}},keypress:function(t){if(i)return i=!1,void(this.isMultiLine&&!this.menu.element.is(":visible")||t.preventDefault());if(!s){var e=V.ui.keyCode;switch(t.keyCode){case e.PAGE_UP:this._move("previousPage",t);break;case e.PAGE_DOWN:this._move("nextPage",t);break;case e.UP:this._keyEvent("previous",t);break;case e.DOWN:this._keyEvent("next",t)}}},input:function(t){if(n)return n=!1,void t.preventDefault();this._searchTimeout(t)},focus:function(){this.selectedItem=null,this.previous=this._value()},blur:function(t){clearTimeout(this.searching),this.close(t),this._change(t)}}),this._initSource(),this.menu=V("