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-52000 -- GAUSS-52999/ GAUSS-52600 -- GAUSS-52699

GAUSS-52600 -- GAUSS-52699

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

View PDF

GAUSS-52600 : "Can not obtain any cluster ring."

SQLSTATE: None

Description: No ring is obtained from the cluster.

Solution: Check whether the CN in the XML file is correctly configured.

GAUSS-52601 : "Redistribution failed due to user request."

SQLSTATE: None

Description: Redistribution failed due to user requests.

Solution: Check whether users have performed invalid operations during the scale-in or scale-out process.

GAUSS-52602 : "There is no CN in old nodes. "

SQLSTATE: None

Description: No CN is available on old nodes.

Solution: Check whether the CN is configured in the XML file and whether the cluster status is normal.

GAUSS-52603 : "There is no CN on the contraction of the remaining nodes."

SQLSTATE: None

Description: No CN exists on the remaining nodes after the scale-in.

Solution: Check whether a normal CN is available on the remaining nodes after the scale-in.

GAUSS-52605 : "Can not contract local node(%s). "

SQLSTATE: None

Description: The local node cannot be scaled in.

Solution: Ensure that the node where the scale-in command is executed has been configured in the XML.

GAUSS-52606 : " Contract too many nodes. It should left three nodes to format a cluster at least."

SQLSTATE: None

Description: Too many nodes were removed. Retain at least three nodes in the cluster after scale-in.

Solution: Check whether the number of nodes in the XML file after the scale-in is smaller than three.

GAUSS-52607 : " [%s] does not at the end of instance list."

SQLSTATE: None

Description: The node is not at the end of the instance list.

Solution: Check whether the scale-in nodes configured in the XML file are the nodes at the end of the cluster in sequence.

GAUSS-52608 : " [%s] contains %s instance."

SQLSTATE: None

Description: The code contains CM Servers/GTMs.

Solution: Check whether the scale-in nodes include CM Servers/GTMs. If they are included, reconfigure corresponding nodes to exclude them, and then run the command again.

GAUSS-52609 : " All contracted nodes do not contain DN instance."

SQLSTATE: None

Description: All the scale-in nodes cannot contain the DN instance

Solution: Check whether the scale-in nodes in the XML file contain the DN instance.

GAUSS-52610 : "The current node group are node group after contraction. "

SQLSTATE: None

Description: The current node group is the group after the scale-in.

Solution: Check whether the scale-in node group is identical with the group after the scale-in.

GAUSS-52611 : " There must be only one record in the current node group."

SQLSTATE: None

Description: Only one record exists in the current node group.

Solution: Check whether several information records exist in the current node group.

GAUSS-52612 : " All dilatation nodes do not contain the DN instance."

SQLSTATE: None

Description: All the scale-out nodes cannot contain DNs.

Solution: Check whether the scale-out nodes in the XML file contain DNs.

GAUSS-52613 : " Static configuration is not matched on some nodes. Please handle it first."

SQLSTATE: None

Description: The static configuration file on the node does not match the new XML file.

Solution: Run the preinstall script again.

GAUSS-52614: Timeout. The current cluster status is %s."

SQLSTATE: None

Description: The operation timed out.

Solution: Try again.

GAUSS-52615 : "Cluster lock unlocked due to timeout. "

SQLSTATE: None

Description: Failed to unlock the cluster due to timeout.

Solution: Check whether the cluster status is normal. Check whether the database can write data. View corresponding logs and detailed error information.

GAUSS-52616 : "Can not find a similar instance for [%s %s]. "

SQLSTATE: None

Description: A similar instance [the host name and instance directory] cannot be found.

Solution: Check whether the cluster status is normal and whether the node information in the XML file is correctly configured.

GAUSS-52617 : "Invalid check type. "

SQLSTATE: None

Description: The check type is invalid.

Solution: The check types of the node groups in the scale-out module should be precheck and postcheck. Other check types are incorrect.

GAUSS-52620 : " Not all nodes found. The following is what we found: %s."

SQLSTATE: None

Description: All nodes are not found. The nodes that we found are as follows:

Solution: Check whether the cluster status is normal and whether the configured scale-in node in the XML name is correct.

GAUSS-52623 : "Failed to check node group numbers: Node group numbers is [%d]. "

SQLSTATE: None

Description: The number of the node groups fails to be checked.

Solution: Ensure that the number of node groups is 1 or 2.

GAUSS-52624 : "Failed to check %s node group members: Invalid group name or nodes. "

SQLSTATE: None

Description: Failed to check the members of the %s node group. Invalid group name or node.

Solution: The obtained node group names or the node group members are empty when the node groups are checked during a scale-in. Check whether data in the pgxc_group system catalog is normal.

GAUSS-52626 : "The CN connection on the old nodes are abnormal. "

SQLSTATE: None

Description: The CN connection on the old node is abnormal.

Solution: Check the number of the CN connections on the old nodes of the scale-out module, and ensure that the current number of connections on each CN cannot exceed 90% of the maximum connections.

GAUSS-52627 : " The current cluster is locked."

SQLSTATE: None

Description: The cluster has been locked.

Solution: In the scale-out module, the old node cluster has been locked. Unlock it and continue scaling out the current cluster.

GAUSS-52628 : "Static configuration has already been updated on all nodes, expansion has been completed possibly. "

SQLSTATE: None

Description: The static configuration file has been updated on each node. The scale-in is probably complete.

Solution: Check whether the cluster status is normal after the scale-out. If the cluster includes the scale-out nodes and the cluster status is normal, do not execute any scale-out commands anymore.

GAUSS-52629 : "Cluster ring(%s) can not obtain less than three nodes. "

SQLSTATE: None

Description: The number of cluster rings cannot be less than three.

Solution: Check the XML file configuration in the scale-in scenario to see whether the number of scale-in nodes to be executed is smaller than three.

GAUSS-52630 : "Failed to set the read-only mode parameter for all CN and DN instances. "

SQLSTATE: None

Description: Failed to set the read-only mode for all CNs and DNs.

Solution: Check to ensure gs_guc exists and that the cluster status is normal. Reset the read-only mode again.

GAUSS-52631 : "Invalid value for GUC parameter comm_max_datanode: %s. "

SQLSTATE: None

Description: The value of comm_max_datanode of CNs in the cluster is invalid.

Solution: Set comm_max_datanode to a value greater than the total number of DNs in the cluster.

GAUSS-52632 : "Cluster breakdown or abnormal operation during expanding online, lock process for expansion is lost."

SQLSTATE: None

Description: During online expansion, the cluster breaks down or an abnormal operation is performed. As a result, the lock process for the expansion is lost.

Solution: Call the online expansion operation again.

GAUSS-52633 : "There is no primary datanode."

SQLSTATE: None

Description: The primary DN is not obtained.

Solution: Contact technical support.

GAUSS-52634 : "There is no normal CN and primary DN on local node."

SQLSTATE: None

Description: No normal primary CN or DN has been obtained.

Solution: Contact technical support.

Parent topic: GAUSS-52000 -- GAUSS-52999

Previous topic: GAUSS-52500 -- GAUSS-52599

Next topic: GAUSS-52700 -- GAUSS-52799