DB2 Server for VM: System Administration

Chapter 3. Planning for Database Migration

If your installation already has a previous release of the database manager installed, you must consider the effect that migration to the new release will have on your existing databases and applications.

You can migrate to a DB2 Server for VM Version 7 Release 1 database from:

• Version 6 Release 1
• Version 5 Release 1
• Version 3 Release 5
• Version 3 Release 4
• Version 3 Release 3
• Version 3 Release 2
• Version 3 Release 1

Note:

If you are on an earlier release, you will have to migrate to Version 3 Release 5 first and then to Version 7 Release 1.

Before migrating:

• Read the discussions on release-to-release incompatibilities in Appendix I, Incompatibilities Between Releases for changes that may be required in application programs.
• Ensure that the requirements discussed in Chapter 1, Planning for Installation are met. For information on the actual installation and migration steps, see the DB2 Server for VM Program Directory .
• It is strongly recommended that you archive your databases before migrating, so that you can back out of the migration process should it become necessary.
• Consider installing the database manager and generating a starter database to try out the new functions before migrating your existing databases.

This chapter also contains sections on the following:

• Release coexistence considerations

  It can be impractical to migrate all the databases in a local or distributed environment to the current level at the same time. For information on the level of coexistence that is possible see Release Coexistence Considerations.

• Migration from a VSE to a VM operating system

  It is possible to move a DB2 Server for VSE database to a VM operating system. There is no need to convert the data in a database when you move from VSE to VM; the data is system-independent. You move data from VSE to VM by taking a database archive of the DB2 Server for VSE database and then restoring the database archive tape on the VM operating system.

  If you have moved a database from VSE to VM, you may have some VSE application programs that you do not want to convert. These programs can access the databases on VM using VSE guest sharing. For more information, see Migrating from a VSE to a VM Operating System.

• System migration from one IBM VM system to another

  You can migrate your databases to a new VM operating system in two ways:

  • Archive them in the original VM operating system, install the database manager on your new VM operating system, and restore the databases in the new operating system.
  • Install a new VM operating system on the processor you use to access your databases. You can then access your databases as you did in the original operating system.

  See the information about the operating systems involved, beginning on page Migrating from a VM/XA to a VM/ESA Environment.

• Converting a service machine to a database machine

  For any particular processor, you may need to convert a service machine to a database machine if a database machine is required on that processor. Converting a Service Machine to a Database Machine explains this process.