Troubleshoot: Error when running migratedb script

During a migration, the migratedb script fails because the database is not catalogued.

 

Problem

When you run the migratedb script, you receive an error in your database tier migration log file that is similar to the following example:

Info : Trace -
com.ibm.commerce.migration.massload.massloadCommand.loadData()-
dbname mall -dbuser db2inst1 -dbpwd ***
-infile
/usr/WebSphere/CommerceServer56/schema/migration/../xml/wcs.bootstrap.xml
-method sqlimport -schemaname db2inst1 -commitcount 100
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver]
SQL1224N A database agent could not be started to service a
request, or was terminated
as a result of a database system shutdown or a force command.
SQLSTATE=55032

 

Solution

The local DB2 database needs to be cataloged as remote, using a database alias.

Complete the steps in "Creating a remote alias for your database" in the DB2 Information Center, and run the database tier migration script again.

Related tasks

Migrate the WebSphere Commerce database

Migrate the development environment database

Migrate the WebSphere Commerce database using the migration script