•    1 -  Log on to the DB2 server as the DB2 instance owner that you want to migrate.

•    2 -  Stop the instance by running the db2stop command.

•    3 - From a DB2 command line prompt move to the appropriate directory:

          -  On UNIX or Linux operating systems, change to the $DB2DIR/bin directory where DB2DIR is the location that you specified during the DB2 Version 9.5 installation.
          -  On Windows® operating system, you need to insert the DB2 Version 9.5 product CD in the drive and change to the \db2\Windows\utilities directory.

•   4 -  Run the db2ckmig command to verify that the databases that are owned by the current instance are ready to be migrated and to generate a log file.

db2ckmig sample -l db2ckmig.log -u adminuser -p password

Output:

         db2ckmig was successful.  Database(s) can be migrate

If you don't receive the message below. check the conditions below to your database:

•     A catalogued database actually exists.

•     A database is not in an inconsistent state.

•     A database is not in a backup pending state.

•     A database is not in a restore pending state.

•     A database is not in roll-forward pending state.

•     Table spaces are in a normal state.

•     A database does not contain user-defined types (UDTs) with the name ARRAY, BINARY, DECFLOAT, VARBINARY and XML.

•     A database does not contain the system-defined DATALINK data type.   

•     A database does not have orphan rows in system catalog tables that would cause database migration to fail.

•     A database enabled as an HADR primary database allows successful connections.

•     An HADR database role is not standby.

•     If SYSCATSPACE is a DMS table space and the automatic resizing functionality is not enabled, SYSCATSPACE has at least 50% free pages of  
      total pages.
  

A database must pass all of these checks to succeed at the migration process.