Preparing for and Checking the Upgrade
This section describes preparations before the upgrade.
Upgrade Preparation Checklist
Table 1 Upgrade preparation
NOTE: Time required varies according to the particulars for the site (such as the data volume and server performance).
Collecting Node Information
Contact the database system administrator to obtain names and IP addresses of database nodes. You have obtained the passwords of users root and omm for logging in to the nodes, as shown in Table 2.
Table 2 Node information
Backing Up Data
If the upgrade fails, services may be affected. Back up data in advance so that services can be restored as soon as possible after a failure occurs.
For details, see section “Backup and Restoration” in the Administrator Guide.
Obtaining the Upgrade Package
https://opengauss.org/zh/download/
Obtain the upgrade package from the website.
Checking the OS Health Status
Use the gs_checkos tool to check the OS status.
Prerequisites
The hardware and network are working properly.
The trust relationship of user root among the hosts is normal.
Only user root is authorized to run the gs_checkos command.
NOTE: This tool cannot be independently invoked. For security purposes, it is automatically deleted after the preinstallation is complete.
Procedure
Log in to the server as user root.
Run the following command to check OS parameters of the server:
gs_checkos -i A
Check the OS parameters to ensure that the database has passed the pre-installation check and can efficiently operate after it is installed. For details about the check items, see see “Server Tools > gs_checkos > Table 1 OS check items” in the Tool Reference.
Checking the Disk Usage of the Database Node
You are advised to perform the upgrade when the disk usage of the database node is less than 80%.
Checking the Database Status
This section describes how to query the database status.
Procedure
Log in to the node as the database user (for example, omm) and run the source command to set the environment variables.
Run the following command to check the database status:
gs_om -t status
Ensure that the database is normal.