What's New
Function Overview
Product Bulletin
- Product Notice
- Version Support Notes
Service Overview
- GaussDB(DWS) Infographics
- What Is GaussDB(DWS)?
- Data Warehouse Types
- Data Warehouse Flavors
- Advantages
- Application Scenarios
- Functions
- Concepts
- Related Services
- Security
- GaussDB(DWS) Permissions Management
- GaussDB(DWS) Access
- Restrictions
- Technical Support
- Service Quotas
- GaussDB(DWS) Technical Specifications
Billing
- GaussDB(DWS) Billing Overview
- Billing Modes
- Item
- Billing Examples
- Billing Mode Change
- Renewal
  - Overview
  - Manual Renewal
- Bills
- Arrears
- Stopping Billing
- Cost Management
- Billing FAQs
Getting Started
- Checkpoint Vehicle Analysis
- Supply Chain Requirement Analysis of a Company
- Operations Status Analysis of a Retail Department Store
- Creating a Time Series Table
- Best Practices of Hot and Cold Data Management
- Best Practices for Automatic Partition Management
- Creating a Cluster and Connecting to It
- Using CDM to Migrate MySQL Data to the GaussDB(DWS) Cluster
- Using DLI Flink Jobs to Write Kafka Data to GaussDB(DWS) in Real Time
- Basic SQL Operations
- Database Quick Start
- Getting Started with Common Practices
User Guide
- Using GaussDB(DWS)
- Preparations
- Creating a GaussDB(DWS) Cluster
- Connecting to a GaussDB(DWS) Cluster
- Creating a GaussDB(DWS) Database and User
- Migrating Service Data to a GaussDB(DWS) Cluster
  - Migrating Data to a GaussDB(DWS) Cluster Using GDS-Kafka
  - Data Source Management
- GaussDB(DWS) Cluster Data Security and Encryption
- GaussDB(DWS) Cluster Management
- GaussDB(DWS) Cluster O&M
Best Practices
- Import and Export
- Data Migration
- Data Analytics
- Decoupled Storage and Compute
  - DWS 3.0 Decoupled Storage and Compute Usage Suggestions and Performance Optimization
- Data Development
- Database Management
- Performance Tuning
  - Optimizing Table Structure Design to Enhance GaussDB(DWS) Query Performance
  - Analyzing SQL Statements That Are Being Executed to Handle GaussDB(DWS) Performance Issues
- Cluster Management
  - Binding Different Resource Pools to Two Types of Jobs to Balance Load for GaussDB(DWS)
  - Scaling Options for GaussDB(DWS) with a Coupled Storage-Compute Architecture
Data Migration and Synchronization
- Data Migration to GaussDB(DWS)
- Importing Data
- Full Database Migration
  - Using CDM to Migrate Data to GaussDB(DWS)
  - Using DSC to Migrate SQL Scripts
- Real-time Import
  - Using DRS to Import Data to GaussDB(DWS)
  - Real-time Data Import From Kafka GaussDB(DWS)
- Metadata Migration
  - Using gs_dump and gs_dumpall to Export Metadata
  - Using gs_restore to Import Data
- Exporting Data
- Other Operations
Developer Guide
- Standard data warehouse (9.1.0.x)
- Standard data warehouse (8.1.3.x)
- Hybrid Data Warehouse (9.1.0.x）
- Hybrid Data Warehouse (8.1.3.x）
- Historical Versions
SQL Syntax Reference
- SQL Syntax Reference (9.1.0.x)
- SQL Syntax Reference (8.1.3.x)
- Historical Versions
Performance Tuning
- Overview of Query Performance Optimization
- Query Execution Process
- SQL Execution Plan
- SQL Optimization Guide
- Optimization Cases
- SQL Execution Troubleshooting
- query_band Load Identification
- Common Performance Parameter Optimization Design
Tool Guide
- Overview
- Downloading Related Tools
- gsql
- Data Studio
- GDS
- DSC
- DataCheck
- DWS-Connector
- Server Tool
API Reference
- Before You Start
- API Overview
- Calling APIs
- Getting Started
- API Description
- Application Cases
  - Using Postman to Call the API for Creating a Cluster
  - Using Postman to Call the API for Creating a Snapshot
- Introduction
- Appendix
SDK Reference
- SDK Overview
FAQs
- Top FAQs
- Product Consulting
- Database Connections
- Data Migration
- Database Usage
- Cluster Management
- Account Permissions
- Database Performance
- Backup and Restoration
  1. Why Does It Take a Long Time to Create an Automated Snapshot in GaussDB(DWS)?
  2. Does a GaussDB(DWS) Snapshot Have the Same Function as an EVS Snapshot?
Troubleshooting
- Database Connections
- JDBC/ODBC
- Data Import and Export
- Database Parameter Modification
- Account/Permission/Password
- Cluster Performance
- Cluster Exceptions
  - The Disk Usage Alarm Is Frequently Generated
- Database Use
Videos
Performance White Paper
- Overview
- Test Result
  - TPC-H Single Query Test
  - TPC-DS Single Query Test
- Test Methods
- Appendixes
  - TPC-H Test Sets
  - TPC-DS Test Sets
Technical White Paper
- GaussDB(DWS)
- Platforms and Technical Specifications Supported by GaussDB(DWS)
  - Technical Specifications
- GaussDB(DWS) Core Technologies
- GaussDB(DWS) Tools
  - Client Tools
  - Database Monitoring Tool
- External APIs
Error Code Reference
- 8.2.0 and earlier versions
  - Management Console Error Code
  - Data Warehouse Service Error Codes
- 8.2.1 or later versions
Glossary
More Documents
- User Guide
- API Reference (ME-Abu Dhabi Region)
- Developer Guide (ME-Abu Dhabi Region)
- SQL Syntax Reference (ME-Abu Dhabi Region)
- Tool Guide (ME-Abu Dhabi Region)
- Error Code Reference (ME-Abu Dhabi Region)
  - Management Console Error Code
- User Guide (Paris Region)
- API Reference (Paris Region)
- Developer Guide (Paris Region)
- SQL Syntax Reference (Paris Region)
- Tool Guide (Paris Region)
- Error Code Reference (Paris Region)
  - Management Console Error Code
- User Guide (Kuala Lumpur Region)
- API Reference (Kuala Lumpur Region)
- Developer Guide (Kuala Lumpur Region)
- SQL Syntax Reference (Kuala Lumpur Region)
- Tool Guide (Kuala Lumpur Region)
- Error Code Reference (Kuala Lumpur Region)
  - Management Console Error Code
General Reference
- Glossary
- Service Level Agreement
- White Papers
- Endpoints
- Permissions

On this page

Show all

Help Center/ GaussDB(DWS)/ 8.2.0 and earlier versions/ Data Warehouse Service Error Codes/ GAUSS-51000 -- GAUSS-51999/ GAUSS-51200 -- GAUSS-51299

GAUSS-51200 -- GAUSS-51299

Updated on 2023-12-22 GMT+08:00

View PDF

GAUSS-51200: "The parameter [%s] in the XML file does not exist."

SQLSTATE: None

Description: The %s parameter is not found in the XML.

Solution: Check the configuration parameters in the XML file.

GAUSS-51201 : "Node names must be configured."

SQLSTATE: None

Description: The node name needs to be configured.

Solution: Configure node name.

GAUSS-51203 : "Failed to obtain the %s information from static configuration files."

SQLSTATE: None

Description: The cluster information fails to be obtained from the static configuration file.

Solution: Ensure that the static configuration file exists, that you have the access permission, and that the system is normal.

GAUSS-51204 :" Invalid %s instance type: %d."

SQLSTATE: None

Description: The data distribution type is invalid.

Solution: Check and change the instance type.

GAUSS-51205 : "Failed to refresh the %s instance ID."

SQLSTATE: None

Description: The instance ID failed to be updated.

Solution: Check whether the static configuration file exists, or it has been broken, and check whether the user has the access permission.

GAUSS-51206 : "The MPPRC file path must be an absolute path: %s."

SQLSTATE: None

Description: The MPPRC path must be an absolute path.

Solution: Change the MPPRC path to an absolute path.

GAUSS-51207 : "Failed to obtain backIp from node [%s]."

SQLSTATE: None

Description: backIp on the node failed to be obtained.

Solution: Check and correctly configure the backIP address on the node.

GAUSS-51208 : "Invalid %s number [%s]."

SQLSTATE: None

Description: The quantity is invalid.

Solution: Ensure that the quantity is valid.

GAUSS-51209 : "Failed to obtain %s configuration on the host [%s]."

SQLSTATE: None

Description: The configuration on this node fails to be obtained.

Solution: Ensure that the configuration is correct on the node.

GAUSS-51212 : "There is no information about %s."

SQLSTATE: None

Description: There is no information about %s.

Solution: Configure corresponding information for %s.

GAUSS-51213 : "The port number of XML [%s] conflicted."

SQLSTATE: None

Description: The port number is occupied.

Solution: Check whether the occupied port process is available. If the process is unavailable, kill it, or change a new port number.

GAUSS-51214 : "The number of capacity expansion nodes cannot be less than three."

SQLSTATE: None

Description: The number of nodes before scaling cannot be less than three.

Solution: Verify that the number of nodes before scaling is greater than or equal to three.

GAUSS-51215 : "The capacity expansion node [%s] cannot contain GTM/CM."

SQLSTATE: None

Description: GTM/CM cannot be contained on the scale-out node.

Solution: Delete GTM/CM on the scale-out node.

GAUSS-51216 : "The capacity expansion node [%s] must contain CN or DN."

SQLSTATE: None

Description: The node to be added to the cluster for scale-out does not have any CN or DN.

Solution: Add CNs or DNs on the scaling node.

GAUSS-51217 : "The cluster's static configuration does not match the new configuration file."

SQLSTATE: None

Description: The cluster's static configuration is inconsistent with the new configuration.

Solution: Modify the new XML configuration file, leaving it consistent with the cluster static configuration.

GAUSS-51219 : "There is no CN in cluster."

SQLSTATE: None

Description: The CN is not installed in the cluster.

Solution: Reconfigure the XML file and execute the preparation and installation operations.

GAUSS-51220 : "The IP address %s is incorrect."

SQLSTATE: None

Description: The IP address is incorrect.

Solution: Correct the IP address configured in the XML.

GAUSS-51221 : "Failed to configure hosts mapping information."

SQLSTATE: None

Description: The host mapping fails to be configured.

Solution: Check whether the /etc/hosts file exists and whether the host name and IP address configured in the hostname is consistent.

GAUSS-51222 : "Failed to check hostname mapping."

SQLSTATE: None

Description: The host mapping fails to be configured.

Solution: Check whether the trust relationship between nodes is normal.

GAUSS-51224 : "The ip(%s) has been used on other nodes."

SQLSTATE: None

Description: The IP address has been used on another node.

Solution: Check whether the IP addresses of the nodes in the XML file conflict.

GAUSS-51226 : "Virtual IP(s) and Back IP(s) do not have the same network segment."

SQLSTATE: None

Description: The virtual IP address and backIP are not in the same network segment.

Solution: Set the virtual IP address and backIP in the XML file to be in the same network segment.

GAUSS-51227 : "The number of %s on all nodes are different."

SQLSTATE: None

Description: The number of backIP addresses on all nodes is different from that of the sshIP addresses.

Solution: Set the number of backIP addresses in the XML to be the same as that of the sshIP addresses.

GAUSS-51229 : "The DN listenIp(%s) is not in the virtualIp or backIp on the node(%s)."

SQLSTATE: None

Description: listenIp on the DN is not virtualIp or backIp.

Solution: Change listenIp to virtualIp or backIp in the XML file.

GAUSS-51230 : "The number of %s must %s."

SQLSTATE: None

Description: The number of CM Servers or GTMs is incorrect.

Solution: Configure correct numbers for CM Servers and GTMs in the XML file.

GAUSS-51231 : "Old nodes is less than 2."

SQLSTATE: None

Description: The number of old nodes is less than two.

Solution: Set the number of the configured nodes in the XML file to be greater than or equal to three.

GAUSS-51232 : "XML configuration and static configuration are the same."

SQLSTATE: None

Description: The XML configuration and static configuration file are the same

Solution: Before the scaling-out, scaling-in, and CN management operations, ensure that the XML is different from that for the installed clusters.

GAUSS-51233 : "The Port(%s) is invalid on the node(%s)."

SQLSTATE: None

Description: The port is invalid.

Solution: Correct the port number configured in the XML.

GAUSS-51234 : "The configuration file [%s] contains parsing errors"

SQLSTATE: None

Description: The XML file is analyzed incorrectly.

Solution: Check whether the configuration file is broken. If the file has been broken, copy a file from other node. If the file is not broken, reinstall the cluster.

GAUSS-51235 : "Invalid directory [%s]."

SQLSTATE: None

Description: The directory is invalid.

Solution: Modify the directory.

GAUSS-51236: "Failed to parsing xml."

SQLSTATE: None

Description: An error occurred during XML parsing.

Solution: Ensure that the XML file is successfully opened.

GAUSS-51239: "These virtual IP(%s) are not accessible after configuring."

SQLSTATE: None

Description: The virtual IP address of the current node fails the ping.

Solution: Check the host and network configuration. Run the command after the virtual IP address is pinged successfully.

Parent topic: GAUSS-51000 -- GAUSS-51999

Previous topic: GAUSS-51100 -- GAUSS-51199

Next topic: GAUSS-51300 -- GAUSS-51399

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot