Migration errors v55
During the migration process, the migration summary displays the progress of the migration. If an error occurs, the summary displays information about the error. The migration summary is also written to a log file.
On Linux, the default location for the log files is:
$HOME/.enterprisedb/migration-toolkit/logs
On Windows, the log files are saved to:
%HOMEDRIVE%%HOMEPATH%\.enterprisedb\migration-toolkit\logs
You can specify an alternative log file location with the -logdir <log_path>
option in Migration Toolkit.
Connection errors
Migration Toolkit uses information from the toolkit.properties file to connect to the source and target databases. Most of the connection errors that occur when using Migration Toolkit are related to the information specified in the toolkit.properties
file.
Invalid username/password
When I try to perform a migration from an Oracle database with Migration Toolkit, I get the following error:
To resolve this error, edit the toolkit.properties
file, specifying the name and password of a valid user with privileges to perform the migration in the SRC_DB_USER
and SRC_DB_PASSWORD
properties.
Invalid file permissions
When I try to perform a migration with Migration Toolkit, I get the following error:
To resolve this error, ensure the operating system user account running the Migration Toolkit is the owner of the toolkit.properties
file with a minimum of read permission on the file. In addition, there must be no permissions of any kind for group and other users.
The following is an example of the recommended file permissions, where user enterprisedb is running the Migration Toolkit.
-rw------- 1 enterprisedb enterprisedb 191 Aug 1 09:59 toolkit.properties
Connection rejected: FATAL: password
When I try to perform a migration with Migration Toolkit, I get the following error:
The user name or password specified in the toolkit.properties
file is not valid to use to connect to the Postgres database.
To resolve this error, edit the toolkit.properties
file, specifying the name and password of a valid user with privileges to perform the migration in the TARGET_DB_USER
and TARGET_DB_PASSWORD
properties.
Exception: ORA-28000: the account is locked
When I try to perform a migration from an Oracle database with Migration Toolkit, I get the following error message:
To resolve this error, you can either unlock the user account on the Oracle server or edit the toolkit.properties
file, specifying the name and password of a valid user with privileges to perform the migration in the SRC_DB_USER
and SRC_DB_PASSWORD
parameters.
Exception: oracle.jdbc.driver.OracleDriver
When I try to perform a migration with Migration Toolkit, the migration fails and I get the error message:
Before using Migration Toolkit, you must download and install the appropriate JDBC driver for the database that you are migrating from. See Installing a JDBC driver for complete instructions.
I/O exception: The Network Adapter could not establish the connection
When I try to perform a migration with Migration Toolkit, I get the following error:
The JDBC URL for the source database specified in the toolkit.properties
file contains invalid connection properties.
To resolve this error, edit the toolkit.properties file, specifying valid connection information for the source database in the SRC_DB_URL
property. The SRC_DB_URL
value is database specific. See Building the toolkit-properties file for detailed information for your source database type.
Exception: The URL specified for the “target” database is invalid
When I try to perform a migration with Migration Toolkit, I get the following error:
The JDBC URL for the target database (EDB Postgres Advanced Server) specified in the toolkit.properties
file contains invalid connection properties.
To resolve this error, edit the toolkit.properties
file, specifying valid connection information for the target database in the TARGET_DB_URL
property. For information about forming a JDBC URL for EDB Postgres Advanced Server, see Defining an EDB Postgres Advanced Server URL.
Migration errors
The following errors can occur after Migration Toolkit has successfully connected to the target and source database servers.
ERROR: Extra data after last expected column
When migrating a table online, I get the error message: