Identify applications that are incompatible with online migration
Before scheduling an online migration, you can identify applications, activities, and Db2 resources that might be incompatible with catalog migrations and updates and take appropriate actions beforehand to minimize the possibility of a failed migration.
About this task
Recommendation: Complete the following steps on a regular basis during potential migration windows to identify any and all applications that might be incompatible with migration processing.
Procedure
To identify applications that might interfere with online migration, take one of the following actions:
- Issue the DISPLAY BLOCKERS command, which displays locks and claims that active threads hold against specified databases. You can use the optional DETAIL keyword to receive additional report information about each lock or claim.
- Invoke the BLOCKING_THREADS built-in function, which returns a table that contains one row for each lock or claim that threads hold against specified databases.
What to do next
- Terminate any active threads that hold locks or claims against the specified databases. See Canceling threads for more information.
- Schedule the migration during a time window when the incompatible applications are not running.
- Schedule a planned outage for running the CATMAINT utility.
