This topic provides answers to some frequently asked questions (FAQ) about the precheck.
Why does the account of my destination database not have sufficient permissions to migrate data?
- You specified a standard account for the destination database in the Username parameter when you created a migration project.
- Create another migration project. Specify a privileged account or the administrator account for the destination database in the Username parameter. Specify the corresponding password in the Security Token parameter. A high-privilege account can be created in the destination database console.
Why is the plug-in of a destination database missing?
- The plug-in on which the migration objects depend is not installed on the destination database server. If you use the software version of a database that uses an earlier version of kernels, the automatic check performed by the database may return an inaccurate result. In this case, the precheck result prevails.
- Use a privileged account to log on to the destination database.
- Execute the following SQL statement to install the missing plug-in: Replace
Plug-in namewith the name of the plug-in.
CREATE EXTENSION IF NOT EXISTS "Plug-in name" schema pg_catalog;
If multiple plug-ins are missing, execute the preceding statement multiple times. The missing plug-ins shown in the preceding figure are used in the following example:
CREATE EXTENSION IF NOT EXISTS "polar_anydata" schema pg_catalog; CREATE EXTENSION IF NOT EXISTS "polar_nvl" schema pg_catalog; CREATE EXTENSION IF NOT EXISTS "polar_agg" schema pg_catalog;Note If a returned message indicates that the destination database does not support the plug-in, upgrade the database, and then execute the SQL statement again. After you upgrade the database and install the missing plug-in, perform the following steps:
Why is the specified database version in a database evaluation project inconsistent with the actual database version?
Note This is not an urgent issue that may cause data migration failure. You can ignore it if you have a tight schedule.
- If you use the latest destination database version and Advanced Database & Application Migration (ADAM) cannot evaluate this version, ignore this issue.
- If the destination database version is earlier than the evaluation version, go to the destination database console to upgrade the version. Then, perform the precheck again.