Migration logs

This section lists the errors that are logged during the migration process. These errors must not be ignored.

• E SQLExceptioncom.microsoft.sqlserver.jdbc.SQLServerException: The '<table_name>' object already exists in the database.
• E SQLExceptioncom.microsoft.sqlserver.jdbc.SQLServerException: Column names in each table must be unique. Column name '<column_name>' in table '<table_name>' is specified more than once.
• E SQLExceptioncom.microsoft.sqlserver.jdbc.SQLServerException: Column already has a DEFAULT value.
• E SQLExceptioncom.microsoft.sqlserver.jdbc.SQLServerException: '<constraint_name>' is not a constraint.
• E SQLExceptioncom.microsoft.sqlserver.jdbc.SQLServerException: The parameter @objname is ambiguous or the claimed @objtype (COLUMN) is incorrect.
• E SQLExceptioncom.microsoft.sqlserver.jdbc.SQLServerException: The operation failed as an index or statistics with name '<index_name>' already exists on the '<table_name>' table.
• E DBUtilityModel-SQLException:com. microsoft.sqlserver.jdbc.SQLServerException: Invalid column name 'season_start_date'.
• E SQLExceptioncom.microsoft.sqlserver.jdbc.SQLServerException: ALTER TABLE DROP COLUMN failed as the 'season_start_date' column does not exist in the 'alpd_conus_oconus_perdiem' table.
• E SQLExceptioncom.microsoft.sqlserver.jdbc.SQLServerException: ALTER TABLE DROP COLUMN failed as the 'season_end_date' column does not exist in the 'alpd_conus_oconus_perdiem' table.