DB2 Cross-platform database migration steps and considerations

DB2 is a relational database software with a wide range of commercial applications. As a database administrator, it is a complicated and arduous process to be confronted with the migration of database system. The Internet and DB2 help documents have many descriptions of DB2 database migrations, but are rarely mentioned for cross-platform migrations of DB2 databases. This article will be based on the author's successful practice, summed up the Cross-platform database migration steps and considerations.

Brief introduction

Imagine that you are an administrator of a DB2 business database system. You are given a task to support the business development and testing team in the ongoing development of the business system, creating a database system that is independent of the product environment, without impacting day-to-day business operations. For a variety of reasons, this development and test database system will run in a different operating system from the product environment. We know that DB2 provides a number of convenient database management tools, for example, the database's overall backup and restore capabilities, users can easily use it to transfer a DB2 database from one physical node to another physical node, but the DB2 backup and restore function currently only support the homogeneous operating system platform migration between, such as from Windows platform to the Windows platform, AIX platform to AIX platform. There is no specific tool that can be easily implemented for Cross-platform database migrations that are required by the above tasks.

Migration steps

After the author's practice, summed up the DB2 database of the cross-platform migration steps are as follows:

Record source database management system configuration parameters, in case of migration after the database system performance tuning;

Check the source database system objects to identify which database system objects to migrate;

Export the data set of the source database system;

Generate the Data object definition statement of the source database system;

Create a new database on the target platform and set it in reference to the source system;

Import the source data set;

Check the data set import process log to troubleshoot possible errors;

Execute data Object definition statement;

Check the Data object statement execution log to troubleshoot possible errors;

Check the definition of the update stored procedure;

Connect the application system and test the success of the database migration.

A specific example of following these steps is given below, which gives a specific DB2 command to perform these steps for reference.

1. Record source database management system configuration parameters. These are important data environment settings, some of which are related to the success of the migration.

Listing 1. command to display database management system configuration parameters

DB2 get dbm CFG

Listing 2. command to display database configuration parameters

DB2 get DB CFG for Source_db_name

Note: Italic part should is replaced by your settings.

Note: For a more complex source database, be aware of its application group memory size parameters (APPGROUP_MEMO_SZ). If it is not large enough, there will be a problem generating the data object definition later.

Listing 3. command to display database registry variables

Db2set-all

Listing 4. command to display database tablespace

DB2 List tablespaces Show Detail

Listing 5. command to display the database package

DB2 List Packages

The above commands for displaying tablespaces and packages need to establish a connection to the source database first.