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.1 or later versions/ Transaction/ xlog

xlog

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

View PDF

GS_113040326

errmsg:syntax error in history file: %s.

errhint: Expected a numeric timeline ID.

level:FATAL

GS_113040327

errmsg:invalid data in history file: %s.

errhint: Timeline IDs must be in increasing sequence.

level:FATAL

GS_113040328

errmsg:invalid data in history file %s.

errhint: Timeline IDs must be less than child timeline's ID.

level:FATAL

GS_113040337

errmsg:recovery command file %s specified neither primary_conninfo nor restore_command.

errhint: The database server will regularly poll the pg_xlog subdirectory to check for files placed there.

level:WARNING

GS_113120083

errmsg:could not reset replication slot at the end of recovery.

errhint: Delete replication slot or increase max_replication_slots.

level:WARNING

GS_113120111

errmsg:Could not locate required checkpoint record.

errhint: If you are not restoring from a backup, try removing the file "%s/backup_label".

level:FATAL

GS_113120112

errmsg:could not find redo location referenced by checkpoint record.

errhint: If you are not restoring from a backup, try removing the file "%s/backup_label".

level:FATAL

GS_113120168

errmsg:invalid replication slot recptr.

errhint: Check slot configuration or setup standby/secondary.

level:WARNING

GS_113120188

errmsg:WAL generated with full_page_writes=off was replayed since last restartpoint.

errhint: This means that the backup being taken on the standby is corrupt and should not be used. Enable full_page_writes and run CHECKPOINT on the master.

level:ERROR

GS_113120190

errmsg:the standby was promoted during online backup.

errhint: This means that the backup being taken is corrupt and should not be used. Try taking another online backup.

level:ERROR

GS_113120191

errmsg:WAL generated with full_page_writes=off was replayed during online backup.

errhint: This means that the backup being taken on the standby is corrupt and should not be used. Enable full_page_writes and run CHECKPOINT on the master.

level:ERROR

GS_113120192

errmsg:pg_stop_backup still waiting for all required WAL segments to be archived (%d seconds elapsed).

errhint: Check that your archive_command is executing properly. pg_stop_backup can be canceled safely.

level:WARNING

GS_113140042

errmsg:recovery is in progress.

errhint: This xlog function cannot be executed during recovery.WAL control functions cannot be executed during recovery.Recovery control functions can only be executed during recovery.Cannot make new WAL entries during recovery.Roach backup cannot be executed during recovery.

level:ERROR

GS_113140188

errmsg:a backup is already in progress.

errhint: If you're sure there is no backup in progress.

level:ERROR

GS_113150041

errmsg:WAL level not sufficient for making an online roach backup.

errhint: wal_level must be set to archive.

level:ERROR

GS_113200318

errmsg:WAL level not sufficient for creating a restore point.

errhint: wal_level must be set to \archive\ or \hot_standby\ at server start.

level:ERROR

GS_113200827

errmsg:backup_label contains data inconsistent with control file.

errhint: This means that the backup is corrupted and you will have to use another backup for recovery.

level:FATAL

GS_113200862

errmsg:WAL ends before end of online backup.

errhint: All WAL generated while online backup was taken must be available at recovery.

level:FATAL

GS_113201237

errmsg:database files are incompatible with server.

errhint: This could be a problem of mismatched byte ordering. It looks like you need to gs_initdb.

level:FATAL

GS_113201249

errmsg:database files are incompatible with server.

errdetail: The database cluster was initialized without HAVE_INT64_TIMESTAMP but the server was compiled with HAVE_INT64_TIMESTAMP.

errhint: It looks like you need to recompile or gs_initdb.

level:FATAL

GS_113201258

errmsg:database system was interrupted while in recovery at %s.

errhint: This probably means that some data is corrupted and you will have to use the last backup for recovery.

level:LOG

GS_113201259

errmsg:database system was interrupted while in recovery at log time %s.

errhint: If this has occurred more than once some data might be corrupted and you might need to choose an earlier recovery target.

level:LOG

GS_113201322

errmsg:hot standby is not possible because %s = %d is a lower setting than on the master server (its value was %d).

errhint: You might need to increase the value of %s.

level:ERROR

GS_113201323

errmsg:WAL was generated with wal_level=minimal.

errhint: This happens if you temporarily set wal_level=minimal without taking a new base backup.

level:WARNING

GS_113201324

errmsg:hot standby is not possible because wal_level was not set to \hot_standby\ or higher on the master server.

errhint: Either set wal_level to \hot_standby\ on the master.

level:ERROR

GS_113201383

errmsg:recovery is in progress.

errhint: WAL control functions cannot be executed during recovery.

level:ERROR

Parent topic: Transaction

Previous topic: GTM

Next topic: Checkpoint

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