To ensure a smooth upgrade process and a better experience, PolarDB provides an upgrade assessment feature for major engine version upgrades. Before starting the upgrade, run a precheck on prerequisites such as cluster status, upgrade task dependencies, and source cluster properties. This helps identify and resolve issues that could delay the upgrade, reducing processing time and resource costs.
Supported regions
The following regions support the upgrade assessment feature:
China (Hangzhou), China (Shanghai), China (Shenzhen), China (Beijing), China (Zhangjiakou), China (Ulanqab), China (Chengdu), China (Hong Kong), Singapore, Indonesia (Jakarta), US (Silicon Valley), and US (Virginia).
Impact
Upgrade assessment does not affect your business operations.
Create an upgrade assessment task
-
Log on to the PolarDB console.
-
Create an upgrade assessment task. PolarDB offers four ways to create an assessment task:
-
Create from the Clusters page: In the upper-left corner of the Clusters page, click the Migrate/Upgrade Assessment button.
In the Migrate/Upgrade Assessment panel that appears on the right, set Creation Method (for example, Migrate from RDS), Source RDS Version (for example, MySQL 5.6), Source RDS Instance, Target Database Engine, and Edition. Then click Next.
-
Create from the Migrate/Upgrade page: In the upper-left corner of the Migrate/Upgrade page, click the Create Migration/Upgrade Assessment button.
-
On the PolarDB purchase page, perform a one-click upgrade. After selecting Upgrade from PolarDB as the creation method, specifying the Source PolarDB Version and Source PolarDB Cluster, and choosing the target Database Engine and Edition, click the Migration Assessment button.
-
-
Enter the parameters for the upgrade assessment task.
Parameter name
Parameter description
Creation method
Select Upgrade from PolarDB.
If you create the upgrade assessment task from the PolarDB purchase page, this option is automatically selected.
Source PolarDB version
Select the database engine version of the source PolarDB cluster.
Source PolarDB instance
Select a specific cluster from the drop-down list as the source instance.
Target database engine
Select the database engine version for the target PolarDB for MySQL cluster.
Edition
Select the edition for the target PolarDB for MySQL cluster.
Only Enterprise Edition is supported.
Then click Next.
-
PolarDB runs a precheck and assessment from four aspects: Basic Information Validation, Migration Task Dependency Validation, Critical Information Validation, and Other Validations. Address any issues based on the assessment results.
PolarDB provides common issues encountered during upgrade assessments and their solutions. For details, see FAQ and solutions.
After all checks show Success, click Go to Purchase to proceed. If any check fails, click the expand icon to view details, follow the instructions to resolve the issue, and then click Reassess.
-
Click Continue Purchase or Go to Purchase to go to the PolarDB purchase page for the next steps. For details, see Upgrade steps.
Manage migration evaluation tasks
To view the details of an existing evaluation task, go to the Migration/Evaluation page. After an evaluation is complete, you can re-evaluate or proceed to purchase.
Migration evaluation tasks are automatically deleted after seven days. If a task has expired, you can create a new one.

FAQ and solutions
|
Classification |
Check item |
Solution if validation fails |
|
Source instance basic information validation |
Source instance running status |
The source PolarDB cluster must be in the running state. |
|
Source instance read/write status |
The source PolarDB cluster must be in the running state and support both reads and writes. |
|
|
PolarDB service-linked role |
The service-linked role for PolarDB has been created in your account. Follow the steps in Check whether the service-linked role for PolarDB exists, or create it using OpenAPI. | |
Migration task dependency validation | DTS service permissions | Your Alibaba Cloud account must have granted DTS permission to access cloud resources. Follow the steps in Grant DTS permission to access cloud resources. |
Source instance binlog validation | Before a major engine version upgrade, enable binary logging (Binlog) on the source PolarDB cluster. For details, see Enable Binlog. | |
Is the source instance an empty database? | The source PolarDB cluster has no databases. You must create a database in the cluster before upgrading. | |
Source instance trigger validation | The source PolarDB cluster has triggers. Delete them before upgrading, or the upgrade will break. You can manually recreate the triggers in the target PolarDB cluster after the upgrade completes. | |
Source instance table without primary key validation | The source PolarDB cluster contains tables without primary keys. This may cause duplicate data in the target database after synchronization. Connect to the source PolarDB cluster using a privileged account and run the following SQL query to find tables without primary keys: Add primary keys to the tables returned by the query. If you confirm that duplicate records will not affect your workload, you can ignore this assessment result. During the major engine version upgrade, select Continue Upgrade when prompted. | |
Source instance critical information validation | Source instance root account validation | To prevent system accounts in the target PolarDB cluster from being overwritten after migration, the source PolarDB cluster must not contain both root and aliyun_root accounts. Before upgrading, delete any extra system accounts from the source cluster. For details, see Delete extra system accounts from the source PolarDB for MySQL cluster. |