![](https://pdfstore-manualsonline.prod.a.ki/pdfasset/8/54/8541f916-e424-418e-bd7f-3736e57d9313/8541f916-e424-418e-bd7f-3736e57d9313-bg4c.png)
BMC Software, Inc., Confidential and Proprietary Information
2-26 Administrative Products for DB2 Installation Guide
Migrating DB2 Objects Between Releases
Migrating DB2 Objects Between Releases
Summary: When you install a new release, you can copy data from an old release to the
new release, using identical DB2 object names (for example, database and
table names). To use existing DB2 object names for a new release, follow the
procedure below and refer to the example job listing in Figure 2-5 on
page 2-27.
Warning! Using the same object names between releases is not
recommended because it replaces your current DB2 structures.
To Use Existing DB2 Object Names for a New Release
Step 1 When the Object/Storage Verification panel prompts you, select the option to
migrate data.
Step 2 Change the DB2 object names of the BMC Software product to your naming
conventions.
Step 3 After you generate the installation batch jobs, run all of the jobs that are
listed before $xnnINST.
Step 4 Run the first $xnnMIG job to unload the data from the current DB2
databases.
Step 5 Drop the current DB2 databases for the BMC Software product, using
$I98DROP from the previous install JCL.
Step 6 Resume installation with job $xnnBNDI (to bind the install plan just freed)
until you get to the first $xnnMIG job.
Step 7 Run the second $xnnMIG job to load the data into the new tables.
Step 8 Run the remaining jobs, starting with $xnnCOPY and ending just before
$I98DROP.
Warning! Do not run $I98DROP or $I99DLTE until you are ready to
uninstall the product.