On this page

Show all

Help Center/ GaussDB/ User Guide/ Instance Upgrade/ Hot Patch Update

Hot Patch Update

Updated on 2025-02-17 GMT+08:00

View PDF

Scenarios

You can install a hot patch for your GaussDB instance to rectify product issues. A hot patch can be loaded without interrupting services and can be used to resolve some emergent database kernel problems online without affecting services. Hot patch update supports manual rollback.

Precautions

During the update, hot patch packages will be downloaded and decompressed, which occupies certain disk space. It is recommended that the disk usage on the DN be less than or equal to the disk usage threshold minus 10%.
NOTE:

To check the current DN disk usage, go to the metric monitoring page on the management console.

To obtain the disk usage threshold, contact technical support.
Version upgrade is unavailable if instance nodes are in an abnormal state.
If a hot patch conflicts with the backup, the differential backup and full backup of the instance will be stopped during hot patch installation.
During an upgrade or rollback, the following operations cannot be performed: scaling up storage, changing specifications, backing up data, resetting passwords, rebooting instances, and deleting instances.
You are advised to perform an upgrade during off-peak hours because there are more idle CPU, disk, and memory resources.
Hot patch update is available only when there is a hot patch for installation. If no hot patch is available, hot patch update is not displayed.
Hot patch update and rollback can be performed in batches for different patch versions of a single instance. During the update, hot patches are installed in ascending order of version numbers. During the rollback, hot patches are rolled back in descending order of version numbers.
If the upgrade fails, the system automatically rolls back the instance to the source version. You can contact Huawei Cloud technical support, and Huawei Cloud engineers will help you upgrade the instance if necessary.
After the upgrade is complete, you can manually roll back the upgrade.
A maximum of 30 instances can be selected at a time for batch upgrade.
GaussDB can also automatically install hot patches for an instance after the instance is created or after a cold patch is installed for it. You can submit a service ticket to request this function at Service Tickets > Create Service Ticket in the upper right corner of the management console. Note that automatic hot patch update is not supported for new instances created using backups of existing instances.

Procedure

Step 1: Perform a Pre-upgrade Check

Before an upgrade, check the instance status and whether monitoring metrics such as the CPU usage, memory usage, and disk usage of the instance are normal.

Check instance status.
1. Log in to the management console.
2. Click in the upper left corner and select a region and project.
3. Click in the upper left corner of the page and choose Databases > GaussDB.
4. On the Instances page, check whether the target instance is available.
  Figure 1 Instance status
  
  If the instance is in an abnormal state, contact Huawei Cloud technical support.
Check monitoring metrics.
1. Click in the upper left corner of the page, and choose Management & Governance > Cloud Eye.
2. In the navigation pane, choose Cloud Service Monitoring > GaussDB.
3. On the Cloud Service Monitoring page, click the target instance to go to the metric monitoring page.
  - On the DB Instance tab, view the value of Instance Disk Usage to check whether the disk usage is insufficient.
  - On the Node tab, view the value of CPU Usage to check whether the CPU usage remains high for a long time.
  - On the Node tab, view the value of Memory Usage to check whether the memory usage increases sharply.
  If any of the metrics are abnormal, contact Huawei Cloud technical support.

Step 2: Perform the Upgrade

[Method 1: upgrading a single instance]

Click in the upper left corner of the page and choose Databases > GaussDB.
On the Instances page, click More in the Operation column of the target instance and choose Upgrade.
In the Upgrade Instance dialog box, select Hot patch for Upgrade Method, enter YES, and click OK.
NOTE:

All available patch versions are displayed in the Target Version area. If multiple patches are to be installed, they will be installed in ascending order of version numbers after the upgrade task is submitted.

Figure 2 Upgrading an instance
Check the upgrade result on the Instances page.
- During the upgrade, the instance status is Upgrading version.
- After the upgrade is complete, the instance status changes to Available.

[Method 2: upgrading instances in batches]

Click in the upper left corner of the page and choose Databases > GaussDB.
On the Instances page, select the target instances and click Batch Upgrade.
Figure 3 Batch upgrade
In the Batch Upgrade dialog box, select Hot patch for Upgrade Method.
Enter YES and click OK.

Figure 4 Auto-commit of a hot patch update

NOTE:

All available patch versions are displayed in the Target Version area. If multiple patches are to be installed, they will be installed in ascending order of version numbers after the upgrade task is submitted.
Check the upgrade result on the Instances page.
- During the upgrade, the instance status is Upgrading version.
- After the upgrade is complete, the instance status changes to Available.

Step 3: Verify the Upgrade

After the upgrade is complete, check the instance status, backup creation status, and instance connectivity, and whether you can add, delete, update, and query data in the instance.

On the Instances page, check whether Status of the target instance is Available.
On the Instances page, click the name of the target instance. On the Basic Information page that is displayed, check that the target versions are displayed in the Upgraded Hot Patch Version and Upgraded Kernel Hot Patch Version fields in the Configuration area.
Check that the instance is properly connected and you can add, delete, update, and query data in the instance.
1. Log in to the database. For details, see Connecting to an Instance Through DAS.
2. Go to the SQL Query page.
  Figure 5 SQL query
3. Create a database.
  CREATE DATABASE database_name;
  
  In this example, run the following command to create a database named db_tpcds:
  
  CREATE DATABASE db_tpcds;
  
  Switch to the newly created database in the upper left corner.
  
  Figure 6 Switching to the new database
4. Create a table and add, delete, update, and query data in the table.
  1. Create a schema.
    CREATE SCHEMA myschema;
  2. Create a table named mytable that has only one column. The column name is firstcol and the column type is integer.
    CREATE TABLE myschema.mytable (firstcol int);
  3. Insert data into the table.
    INSERT INTO myschema.mytable VALUES (100);
  4. View the data in the table.
    SELECT * FROM myschema.mytable;
```
   | firstcol | 
---+----------+
1  |   100    |
```
  5. Update data in the table.
    UPDATE myschema.mytable SET firstcol = 200;
  6. View the data in the table again.
    SELECT * FROM myschema.mytable;
```
   | firstcol | 
---+----------+
1  |   200    |
```
  7. Drop the table.
    DROP TABLE myschema.mytable;

Rollback Operations

If a rollback is required after the upgrade, perform the following operations to roll back an instance to the source version.

NOTE:

After the upgrade is rolled back, you can perform the upgrade again. If the problem persists, contact Huawei Cloud technical support, and Huawei Cloud engineers will help you upgrade the instance if necessary.

[Method 1: Rolling Back a Single Instance]
[Method 2: Rolling Back Instances in Batches]

In the Upgrade Instance dialog box, select Hot patch for Upgrade Method.
Select Rollback for Action.
Select the target version, enter YES, and click OK.
On the Instances page, check the rollback status. After the rollback is complete, the instance status changes to Available.
On the Instances page, click the name of the target instance. On the Basic Information page that is displayed, check that the target versions are not displayed in the Upgraded Hot Patch Version and Upgraded Kernel Hot Patch Version fields in the Configuration area.
Check that the instance is properly connected and you can add, delete, update, and query data in the instance.
1. Log in to the database. For details, see Connecting to an Instance Through DAS.
2. Go to the SQL Query page.
  Figure 7 SQL query
3. Create a database.
  CREATE DATABASE database_name;
  
  In this example, run the following command to create a database named db_tpcds:
  
  CREATE DATABASE db_tpcds;
  
  Switch to the newly created database in the upper left corner.
  
  Figure 8 Switching to the new database
4. Create a table and add, delete, update, and query data in the table.
  1. Create a schema.
    CREATE SCHEMA myschema;
  2. Create a table named mytable that has only one column. The column name is firstcol and the column type is integer.
    CREATE TABLE myschema.mytable (firstcol int);
  3. Insert data into the table.
    INSERT INTO myschema.mytable values (100);
  4. View the data in the table.
    SELECT * FROM myschema.mytable;
```
   | firstcol | 
---+----------+
1  |   100    |
```
  5. Update data in the table.
    UPDATE myschema.mytable SET firstcol = 200;
  6. View the data in the table again.
    SELECT * FROM myschema.mytable;
```
   | firstcol | 
---+----------+
1  |   200    |
```
  7. Drop the table.
    DROP TABLE myschema.mytable;

On the Instances page, select the target instances and click Batch Upgrade.
In the Batch Upgrade dialog box, select Hot patch for Upgrade Method and Rollback for Action, select a target version, enter YES, and click OK.
On the Instances page, check the rollback status. After the rollback is complete, the instance status changes to Available.
On the Instances page, click the name of the target instance. On the Basic Information page that is displayed, check that the target versions are not displayed in the Upgraded Hot Patch Version and Upgraded Kernel Hot Patch Version fields in the Configuration area.
Check that the instance is properly connected and you can add, delete, update, and query data in the instance.
1. Log in to the database. For details, see Connecting to an Instance Through DAS.
2. Go to the SQL Query page.
  Figure 9 SQL query
3. Create a database.
  CREATE DATABASE database_name;
  
  In this example, run the following command to create a database named db_tpcds:
  
  CREATE DATABASE db_tpcds;
  
  Switch to the newly created database in the upper left corner.
  
  Figure 10 Switching to the new database
4. Create a table and add, delete, update, and query data in the table.
  1. Create a schema.
    CREATE SCHEMA myschema;
  2. Create a table named mytable that has only one column. The column name is firstcol and the column type is integer.
    CREATE TABLE myschema.mytable (firstcol int);
  3. Insert data into the table.
    INSERT INTO myschema.mytable VALUES (100);
  4. View the data in the table.
    SELECT * FROM myschema.mytable;
```
   | firstcol | 
---+----------+
1  |   100    |
```
  5. Update data in the table.
    UPDATE myschema.mytable SET firstcol = 200;
  6. View the data in the table again.
    SELECT * FROM myschema.mytable;
```
   | firstcol | 
---+----------+
1  |   200    |
```
  7. Drop the table.
    DROP TABLE myschema.mytable;

In the Upgrade Instance dialog box, select Hot patch for Upgrade Method.
Select Rollback for Action.
Select the target version, enter YES, and click OK.
On the Instances page, check the rollback status. After the rollback is complete, the instance status changes to Available.
On the Instances page, click the name of the target instance. On the Basic Information page that is displayed, check that the target versions are not displayed in the Upgraded Hot Patch Version and Upgraded Kernel Hot Patch Version fields in the Configuration area.
Check that the instance is properly connected and you can add, delete, update, and query data in the instance.
1. Log in to the database. For details, see Connecting to an Instance Through DAS.
2. Go to the SQL Query page.
  Figure 7 SQL query
3. Create a database.
  CREATE DATABASE database_name;
  
  In this example, run the following command to create a database named db_tpcds:
  
  CREATE DATABASE db_tpcds;
  
  Switch to the newly created database in the upper left corner.
  
  Figure 8 Switching to the new database
4. Create a table and add, delete, update, and query data in the table.
  1. Create a schema.
    CREATE SCHEMA myschema;
  2. Create a table named mytable that has only one column. The column name is firstcol and the column type is integer.
    CREATE TABLE myschema.mytable (firstcol int);
  3. Insert data into the table.
    INSERT INTO myschema.mytable values (100);
  4. View the data in the table.
    SELECT * FROM myschema.mytable;
```
   | firstcol | 
---+----------+
1  |   100    |
```
  5. Update data in the table.
    UPDATE myschema.mytable SET firstcol = 200;
  6. View the data in the table again.
    SELECT * FROM myschema.mytable;
```
   | firstcol | 
---+----------+
1  |   200    |
```
  7. Drop the table.
    DROP TABLE myschema.mytable;

On the Instances page, select the target instances and click Batch Upgrade.
In the Batch Upgrade dialog box, select Hot patch for Upgrade Method and Rollback for Action, select a target version, enter YES, and click OK.
On the Instances page, check the rollback status. After the rollback is complete, the instance status changes to Available.
On the Instances page, click the name of the target instance. On the Basic Information page that is displayed, check that the target versions are not displayed in the Upgraded Hot Patch Version and Upgraded Kernel Hot Patch Version fields in the Configuration area.
Check that the instance is properly connected and you can add, delete, update, and query data in the instance.
1. Log in to the database. For details, see Connecting to an Instance Through DAS.
2. Go to the SQL Query page.
  Figure 9 SQL query
3. Create a database.
  CREATE DATABASE database_name;
  
  In this example, run the following command to create a database named db_tpcds:
  
  CREATE DATABASE db_tpcds;
  
  Switch to the newly created database in the upper left corner.
  
  Figure 10 Switching to the new database
4. Create a table and add, delete, update, and query data in the table.
  1. Create a schema.
    CREATE SCHEMA myschema;
  2. Create a table named mytable that has only one column. The column name is firstcol and the column type is integer.
    CREATE TABLE myschema.mytable (firstcol int);
  3. Insert data into the table.
    INSERT INTO myschema.mytable VALUES (100);
  4. View the data in the table.
    SELECT * FROM myschema.mytable;
```
   | firstcol | 
---+----------+
1  |   100    |
```
  5. Update data in the table.
    UPDATE myschema.mytable SET firstcol = 200;
  6. View the data in the table again.
    SELECT * FROM myschema.mytable;
```
   | firstcol | 
---+----------+
1  |   200    |
```
  7. Drop the table.
    DROP TABLE myschema.mytable;

Parent Topic: Instance Upgrade

Previous topic: Overview

Next topic: In-place Upgrade

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