Blu Age DB2 migration execute error

The error you're encountering during the DB2 migration process with Blu Age appears to be related to a missing table in the target database. Specifically, the error message indicates that the "LOGLEVEL" table does not exist in the PostgreSQL database you're trying to migrate to.

This issue can occur for a few reasons:

1. The table creation step may have been skipped or failed during the migration process.
2. There might be a mismatch between the source DB2 schema and the target PostgreSQL schema.
3. The migration tool may not have the necessary permissions to create or access the table.

To resolve this issue, you can try the following steps:

1. Verify that the schema migration step completed successfully before the data migration step. This should have created all necessary tables, including the "LOGLEVEL" table.

2. Check the permissions of the database user being used for the migration. Ensure it has the necessary rights to create tables and insert data.

3. Manually create the "LOGLEVEL" table in the target PostgreSQL database if it's missing. You can do this by examining the structure of the table in the source DB2 database and creating an equivalent table in PostgreSQL.

4. Review the migration logs for any earlier errors that might have prevented the table creation.

5. If you're using a migration configuration file, double-check that it correctly specifies all tables that need to be migrated, including the "LOGLEVEL" table.

6. Ensure that your PostgreSQL driver is correctly located in the path specified in your migration.ini file.

If the issue persists after trying these steps, you may need to reach out to Blu Age support or consult their documentation for more specific troubleshooting steps related to DB2 to PostgreSQL migrations.

Sources
Error in Executing Data migrator - 4.2.0 Image | AWS re:Post
AWS Blu Age L3 Workshop: TRANBKP error - { "exitCode": -1, "stepName": "PRC001", "program": "IDCAMS", "status": "Error" } | AWS re:Post

I realized that this was due to misconfiguration. It happens for not copying SQLModel.json to Generate Configuration after Transform step. It generates correct tables with SQL model inclusion. now DB2 migration step proceeded successfully and observed new error.

Having SQL model support the generated database looks like this.

migration.cmd with updated database schema

I got the issue resolved via debug/support session do these steps on pgAdmin4

1. drop carddemo_primary
2. delete (cascade) opeation on two tables (loglevel, logtable)
3. execute migrate.cmd, completed full script with no errors.
4. verify migration is successful and 2 records are found for SELECT * FROM loglevel;