Upgrade OCP

You can upgrade OceanBase Cloud Platform (OCP) V3.2.4 and later to V4.2.0 through the GUI of OceanBase Admin Toolkit (OAT).

Prerequisites

OAT has taken over the target OCP.

Procedure

1. Log on to the OAT console.

2. In the left-side navigation pane, choose Product Service > Products.

3. On the OCP tab of the Product Management page, find the target OCP and click its name in the Name column to go to the details page.

   Note

   If there are too many OCPs, you can also search for the target OCP by product name in the upper-right corner of the page.

4. In the upper-right corner of the details page, click Upgrade.

   

5. In the Upgrade dialog box, enter the required information.

   The following table describes the related fields.

   Field	Description
   Upgrade Mode	The upgrade method. At present, OAT only supports Upgrade with Services Stopped, which is suitable for products without business continuity requirements. In this upgrade mode, OAT stops the services of the old version of OCP, which cannot provide external services.
   Select an image file for the upgrade	The image file of the target version.
   Username	The username of OCP. This field is not displayed if the source version is OCP V4.0.1 or later.
   Password	The password of OCP. This field is not displayed if the source version is OCP V4.0.1 or later.

   

6. Click OK.

7. After an upgrade task is submitted, choose System and Security > Tasks. On the page that appears, click the name of the task to view its details.

   

8. Log on to the OCP console. If the page of OCP appears, the major components in the system architecture of OCP have been upgraded. Some time-consuming tasks continue to run in the background.

   You need to verify the upgrade from the following aspects:

   1. In the task list, check whether the task for upgrading OCP-Agent is properly running.

   2. Open the bootstrap.log file of OCP-Server, which is located in /home/admin/logs/ocp by default, and find the tasks marked as DELAYED, such as ALTER_TABLES_DELAYED and MIGRATIONS_DELAYED. Then, check whether the tasks are marked as END. The BEGIN and END marks appear in pairs.

   3. If the upgrade fails, open the ocp.log file of OCP-Server, which is located in /home/admin/logs/ocp by default, and check for unexpected errors in logs with the keyword "BootstrapRunListener" or "DataSourceInterceptor". Such logs are generated after ocp-bootstrap registers with a listener, which is used to block Spring bean initialization events. If an unexpected error is reported, contact OCP Technical Support.