After you create a migration project, Advanced Database & Application Migration (ADAM)
automatically runs a precheck. A precheck may involve the account permissions and
plug-ins of the destination database. You can fix issues based on precheck results
as prompted.
Background information
After you create a migration project, ADAM automatically runs a precheck.
Note ADAM automatically runs a precheck only when you migrate data to PolarDB for Oracle
databases. If you migrate data to other databases, ADAM automatically skips the precheck.
Procedure
- Log on to the Data Management (DMS) console V5.0.
- In the top navigation bar, move the pointer over DTS. Choose .
- On the Transform and Migrate DB page, find the project that you want to precheck and click Details in the Actions column.
Note The project to be prechecked must be in the ACTIVE state.
- Click Precheck to view the precheck result.
If the precheck fails, click
View Details to fix errors as prompted.
- Permissions of the account that is used to access the destination database: If your
account does not have the required permissions, recreate a migration project. For
more information, see Why does the account of the destination database not have sufficient permissions to migrate data?.
- ADAM checks whether the account of the destination database has the permissions to
create users.
- ADAM checks whether the account of the destination database has the permissions to
authorize users.
- ADAM checks whether the account of the destination database has the permissions to
create and delete schemas.
- ADAM checks whether the account of the destination database has the permissions to
create and delete DDL statements.
- Plug-ins of the destination database
ADAM checks whether the required plug-ins are installed on the destination database.
If a plug-in is not installed, execute the corresponding SQL statement to install
the plug-in. For more information, see Why is a plug-in of the destination database missing?.
- Version of the destination database
ADAM checks whether the version of the evaluated destination database is the same
as the version of the destination database that is used to migrate schemas. If the
two versions are inconsistent, recreate a project to evaluate the destination database.
For more information, see Why is the specified database version in a created database evaluation project inconsistent with the actual database version?.
- Character sets of the source and destination databases
ADAM checks whether the character sets of the source and destination databases match
each other.
- Time clocks of the source and destination databases
ADAM checks whether the time clocks of the source and destination databases are consistent.
- Resources of the destination database
ADAM checks whether the destination database has sufficient resources.
Note If the precheck still fails, you can click Precheck Again to reperform a precheck or ignore the precheck result.
What to do next
Click Next: Verify Source Database to verify the source database. For more information, see Verify the source database.