Installing and migrating DB2

The essential steps are similar for both installing DB2® 10 and migrating to DB2 10 conversion mode (from Version 8 or Version 9). From conversion mode (from Version 8 or Version 9), you must complete additional steps to migrate to DB2 10 new-function mode.

Before you begin

Prepare your system for DB2 installation or migration, as described in Preparing your system to install or migrate to DB2 10.

About this task

Installation and migration tools
DB2 provides a set of tools that automate the process of installing or migrating. These tools include:
  • Most of the job control language (JCL) that is needed to install and migrate DB2 10. This JCL constitutes the installation and migration jobs. Each of these jobs helps you perform an installation or migration task.
  • The installation CLIST (command list) to help tailor the installation and migration jobs. This CLIST is also called the migration CLIST, or simply the CLIST. It contains the necessary code for tailoring the jobs to suit your needs.
    Tip: You can capture most settings of an existing DB2 subsystem by running the DSNTIJXZ job, which invokes the DSNTXAZP tool. Running this job reduces the effort to manually compare settings in the current DSNTIJUZ job with the values that are defined in the defaults input member. For details, see Updating the CLIST defaults input member: job DSNTIJXZ and DSNTXAZP tool.
  • A series of ISPF panels that you can use to pass information to the CLIST. With Interactive Systems Productivity Facility (ISPF) and Interactive Systems Productivity Facility/Program Development Facility (ISPF/PDF), you can use a series of ISPF panels to pass parameter values to the CLIST. The CLIST uses these values to tailor the installation and migration jobs. This process is called the ISPF tailoring session.
  • Sample applications to help determine if you installed or migrated DB2 correctly . DB2 provides a set of sample programs and procedures that help you determine if DB2 is operating correctly.

All references to SYS1.PARMLIB also imply the logical PARMLIB data set that is used for DB2.

Minimal assemblies
Because it is distributed as object code, DB2 requires few assemblies. You must complete an assembly to specify DB2 initialization parameters, but this assembly requires only a few seconds.
Ability to defer decisions about DB2 characteristics:
DB2 allows you to specify many subsystem characteristics during DB2 operation. You can modify initialization parameters, authorize users, define databases and tables, and tune DB2 while DB2 is running. Therefore, you can defer many decisions until after you finish installing or migrating DB2.
Ability to update installation and migration options
During the process of installing and migrating, DB2 uses ISPF panels to prompt you for many options. DB2 allows you to update most of these options without requiring you to reinstall or remigrate. You can accept the default values for certain options and, after acquiring experience with DB2, tailor them to suit your needs.

Procedure

To install or migrate to DB2 10, you complete the following procedures:

  1. Estimate storage needs.
  2. Determine which new functions you need.
  3. If you are using distributed data, install VTAM® and, optionally, TCP⁄IP.
  4. Set up a Parallel Sysplex® if you plan to use data sharing.
  5. Load the DB2 libraries (do the SMP/E steps). If you plan to use the callable SQL interface of DB2, see Configuring DB2 ODBC and running sample applications for the additional installation jobs that you need to run.If you plan to use DB2 for z/OS® Java Edition, see Installing the IBM® Data Server Driver for JDBC and SQLJ for additional installation jobs that you need to run.
  6. If you are migrating, install needed service on the prior release. See the DB2 Program Directory for information about needed service.
    Important: Apply the fallback SPE and stop and restart DB2 9 for every subsystem or data sharing member that you plan to migrate to DB2 10. For data sharing, every member must be started in DB2 9 after the fallback SPE is applied. After migration to DB2 10 new-function mode, any active members that did not start in DB2 9 with the fallback SPE applied prevent DB2 10 from starting. Inactive members that never started with the fallback SPE applied in DB2 9 cannot start in DB2 10 or DB2 9 after migration to DB2 10 completes on any other member.
  7. If you are migrating, check release incompatibilities, and make the necessary changes in your applications.
  8. If you are installing, provide an SMS environment for managing DB2 catalog and directory data sets. The SMS environment must include a data class for allocating the data sets in extended format and using extended addressability. You are not required to convert existing DB2 catalog and directory data sets to the SMS environment before migrating to DB2 10. These data sets will be converted the next time the related table space is reorganized.
  9. Tailor the installation or migration jobs.
  10. Install DB2 10 or migrate to DB2 10 conversion mode (from Version 8 or Version 9).
  11. Connect the DB2 attachment facilities.
  12. Prepare DB2 for use.
  13. Verify the DB2 10 installation or migration to DB2 10 .
  14. Verify the DB2 10 installation or migration to conversion mode (from Version 8 or Version 9).
  15. If you encounter problems during or after migration to DB2 10 conversion mode (from Version 8 or Version 9), you can complete the following procedures:
    1. Fall back to your previous version (Version 8 or DB2 9).
    2. Remigrate to DB2 10 conversion mode (from Version 8 or Version 9).
  16. After you migrate to conversion mode (from Version 8 or Version 9), complete the following procedures to migrate to DB2 10 new-function mode:
    1. Verify that DB2 is stable in conversion mode (from Version 8 or Version 9). For data sharing, verify that all members are stable.
    2. Tailor the enabling-new-function jobs.
    3. Change to enabling-new-function mode (from Version 8 or Version 9) to convert the catalog.
    4. Start new-function mode.