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-51600 -- GAUSS-51699

GAUSS-51600 -- GAUSS-51699

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

View PDF

GAUSS-51600 : "Failed to obtain the cluster status."

SQLSTATE: None

Description: Failed to obtain the cluster status.

Solution: Check whether the cluster has been set up. Check whether the created cluster is started as expected.

GAUSS-51601 : "Failed to check %s status."

SQLSTATE: None

Description: Failed to check the cluster or local node status.

Solution: Check whether the cluster or local node status is normal.

GAUSS-51602 : "The cluster status is Abnormal."

SQLSTATE: None

Description: The cluster status is abnormal.

Solution: Check whether the cluster status is not restored because the tool script command is not executed.

GAUSS-51603 : "Failed to obtain peer %s instance."

SQLSTATE: None

Description: Failed to obtain the peer instance.

Solution: Ensure that the gtm.conf path exists if you want to obtain GTMs. Check whether the configuration is correct.

GAUSS-51605 : "Failed to check whether the %s process exists."

SQLSTATE: None

Description: Failed to check whether the process exists.

Solution: Ensure that the user has the permission to check the process and that the process is correctly checked.

GAUSS-51606 : "Failed to kill the %s process.

SQLSTATE: None

Description: Failed to kill the process.

Solution: Ensure that the user has the permission to kill the process and that the execution command is correct.

GAUSS-51607 : "Failed to start %s."

Description: Failed to start the cluster, node, or instance.

Solution: Ensure that the network connection is normal and that the configuration file is correct.

GAUSS-51608 : "Failed to lock cluster."

SQLSTATE: None

Description: Failed to lock the cluster.

Solution: Do not perform the closure or stop operations before the session is complete.

GAUSS-51609 : "Failed to unlock cluster."

SQLSTATE: None

Description: Failed to unlock the cluster.

Solution: Do not perform the closure or stop operations before the session is complete.

GAUSS-51610 : "Failed to stop %s."

SQLSTATE: None

Description: Failed to stop the cluster, node, or instance.

Solution: Ensure that the command is correctly executed and that the cluster, node, and, instance statuses are normal.

GAUSS-51612 : "The instance IDs [%s] are not found in %s."

SQLSTATE: None

Description: The ID of an instance is not found in the node information.

Solution: Check whether the CN in the XML file is correctly configured when you add or delete the CN.

GAUSS-51613 : "There is no instance in %s to be built."

SQLSTATE: None

Description: No instance needs to be created.

Solution: The XML file is incorrectly configured when the user manages the CN. No instance is configured on the new node in the XML file

GAUSS-51614:"Received signal[%d]."

SQLSTATE: None

Description: Received the signal %d.

Solution: Try again.

GAUSS-51615 : "Failed to initialize instance."

SQLSTATE: None

Description: Failed to initialize the instance.

Solution: Ensure that the gs_initdb or gs_initcm utility exists. Ensure that the gs_initdb or gs_initcm command is correct. Verify that the cluster, node, and instance statuses are normal.

GAUSS-51616 : "Failed to dump %s schema."

SQLSTATE: None

Description: Failed to dump the CN or DN schema.

Solution: Ensure that the dumpall or dump tool exists. Ensure that the dumpall or dump command is correctly executed. Verify that the cluster, node, and instance statuses are normal.

GAUSS-51617:"Failed to rebuild %s"

SQLSTATE: None

Description: Rebuilding failed.

Solution: Run the command again.

GAUSS-51618 : "Failed to get all hostname."

SQLSTATE: None

Description: Failed to obtain all the host names.

Solution: Ensure that the SSH trust is normal.

GAUSS-51619 : "The current node [%s] is not in the cluster."

SQLSTATE: None

Description: The current node is not in the cluster.

Solution: Check whether the node is configured in the XML file.

GAUSS-51620 : "Failed to obtain %s instance information."

SQLSTATE: None

Description: Failed to obtain the instance information.

Solution: Ensure that the XML file is correctly configured and that the cluster, host, and instance statuses are normal.

GAUSS-51621 : "HA IP is empty."

SQLSTATE: None

Description: The HA IP address is empty.

Solution: Check the configuration information in the XML file. If the HA IP address is configured in the XML file, you need to ensure that the value is correctly configured. If the HA IP address is not configured in the XML file, the backIP will be used by default, and you need to ensure that backIP is correctly configured in the XML file.

GAUSS-51622 : "There is no %s on %s node."

SQLSTATE: None

Description: No CN/DN instance exists on the node.

Solution: Check whether the CN or DN instance is configured on the node in the XML file. Verify that the current cluster, host, and instance statuses are normal.

GAUSS-51623 : "Failed to obtain version."

SQLSTATE: None

Description: Failed to obtain the cluster version.

Solution: Ensure that the version.cfg file exists. Check whether the data format of the version.cfg file is correct. Verify that the current cluster, host, and instance statuses are normal.

GAUSS-51624 : "Failed to get CN connections."

SQLSTATE: None

Description: Failed to obtain the number of CN connections.

Solution: Ensure that the cluster, node, and instance are running properly.

GAUSS-51625 : "Cluster is running."

SQLSTATE: None

Description: The cluster is running.

Solution: Stop the cluster.

GAUSS-51626 : "Failed to rollback."

SQLSTATE: None

Description: Rollback failed.

Solution: Ensure that the command is correctly executed. Verify that the current cluster, host, and instance statuses are normal. View the corresponding log information.

GAUSS-51627: Configuration failed.

SQLSTATE: None

Description: Configuration failed.

Solution: Try again.

GAUSS-51628 : "The version number of new cluster is [%s]. It should be float."

SQLSTATE: None

Description: The version number format of the new cluster is incorrect.

Solution: Ensure that the version.cfg file exists. Check whether the data format of the version.cfg file is correct. Verify that the current cluster, host, and instance statuses are normal.

GAUSS-51629 : "The version number of new cluster is [%s]. It should be greater than or equal to the old version."

SQLSTATE: None

Description: The version number of the new cluster is incorrect. It should be later than or equal to the old version number.

Solution: Ensure that the version.cfg file exists. Check whether the version number in the version.cfg file is earlier than that of the existing cluster. Verify that the cluster, node, and instance statuses are normal.

GAUSS-51630 : "No node named %s."

SQLSTATE: None

Description: The node name does not exist.

Solution: Check whether the node is configured in the XML file. Verify that the cluster, node, and instance statuses are normal.

GAUSS-51631 : "Failed to delete the %s instance."

SQLSTATE: None

Description: Failed to delete the CN.

Solution: Ensure that SSH trust is normal, that the command is correctly executed, and that the cluster, host, and instance statuses are normal.

GAUSS-51632 : "Failed to do %s."

SQLSTATE: None

Description: Failed to execute the python script.

Solution: Ensure that the python script exists, that the command is correctly executed, and that the cluster, node, and instance statuses are abnormal.

GAUSS-51633 : "The %s must be a digit."

SQLSTATE: None

Description: The ID must be composed of digits.

Solution: Ensure that specified instance exists, that the command is correctly executed, and that the cluster, node, and instance statuses are normal.

GAUSS-51635 : "Failed to check SHA256."

SQLSTATE: None

Description: Failed to check SHA-256.

Solution: Ensure that SHA-256 file exists. Ensure that the command is correctly executed. Verify that the cluster, node, and instance statuses are normal.

GAUSS-51636 : "Failed to obtain %s node information."

SQLSTATE: None

Description: Failed to obtain the node information.

Solution: Ensure that the node is configured in the XML file, that the command is correctly executed, and that the cluster, node, and instance statuses are normal.

GAUSS-51637: "The %s does not match with %s."

SQLSTATE: None

Description: Cluster information does not match.

Solution: Ensure that the two parties to be matched are updated simultaneously. Ensure that the command is correctly executed. Verify that the cluster, node, and instance statuses are normal.

GAUSS-51638 : "Failed to append instance on host [%s]."

SQLSTATE: None

Description: Failed to add an instance on the node.

Solution: Check whether the XML file is correctly configured and whether the path conflict exists. Verify that the cluster, node, and instance statuses are normal.

GAUSS-51640 : "Can't connect to cm_server, cluster is not running possibly."

SQLSTATE: None

Description: cm_server is not connected and the cluster is probably not running.

Solution: Restart the cluster.

GAUSS-51641 : "Cluster redistributing status is not accord with expectation."

SQLSTATE: None

Description: The redistribution status does not meet the requirements.

Solution: Check whether the cluster status is normal. Verify that the cluster, node, and instance statuses are normal.

GAUSS-51642 : "Failed to promote peer instances."

SQLSTATE: None

Description: Failed to start the peer instance.

Solution: Ensure that specified instance exists, that the command is correctly executed, and that the cluster, node, and instance statuses are normal.

GAUSS-51643 : "Failed to restart %s."

SQLSTATE: None

Description: Failed to restart the cluster or logical cluster.

Solution: 1. Ensure that the network connection is normal. 2. Check whether the configuration file is correct.

GAUSS-51644 : "Failed to set resource control for the cluster."

SQLSTATE: None

Description: Failed to set cluster resource control.

Solution: Contact technical support.

GAUSS-51645 : "Failed to restart %s."

SQLSTATE: None

Description: Failed to restart the cluster or logical cluster.

Solution: 1. Ensure that the network connection is normal. 2. Check whether the configuration file is correct.

GAUSS-51646: "The other OM operation is currently being performed in the cluster node: '%s'."

SQLSTATE: None

Description: Other O&M operations are being performed on cluster nodes.

Solution: Call the operation again, after other O&M operations complete.

GAUSS-51647 : "The operation step of OM components in current cluster nodes do not match with each other: %s."

SQLSTATE: None

Description: The current O&M operation does not match the operation procedure recorded in cluster nodes.

Solution: Delete the operation procedure file from the $PGHOST directory and call the operation again.

GAUSS-51648 : "Waiting for redistribution process to end timeout."

SQLSTATE: None

Description: The redistribution process times out.

Solution: Call the redistribution operation again.

GAUSS-51649 : "Capture exceptions '%s' : %s."

SQLSTATE: None

Description: The exception information is out of the defined exception range.

Solution: Rectify the fault based on the captured exception information.

GAUSS-51650 : "Unclassified exceptions: %s."

SQLSTATE: None

Description: The exception information is out of the defined exception range.

Solution: Rectify the fault based on the captured exception information.

Parent topic: GAUSS-51000 -- GAUSS-51999

Previous topic: GAUSS-51500 -- GAUSS-51599

Next topic: GAUSS-51700 -- GAUSS-51799

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