DB2 Version 9.7 for Linux, UNIX, and Windows

Reversing DB2 server upgrade

Reversing DB2® server upgrade involves creating a plan using the steps in this procedure to fall back to the DB2 release from which you upgraded your DB2 server. There is no utility to fall back to a previous release of DB2 database after upgrading your DB2 server.

Performing an upgrade in a test environment will help you identify any issues with the process and avoid having to reverse the upgrade.

About this task


Before you begin


To reverse a DB2 server upgrade, you need to perform the following steps:

  1. Log on to the DB2 server as a user with SYSADM authority.
  2. Drop all databases in DB2 Version 9.7 by running the DROP DATABASE command.
  3. Log on to the DB2 server as root on Linux and UNIX operating systems or a user with Local Administrator authority on Windows operating systems.
  4. Drop your DB2 Version 9.7 instances by running the db2idrop command. This command does not remove the database files; you need to drop your databases before dropping your instances.
  5. If you upgraded your pre-Version 9.7 instances to DB2 Version 9.7, re-create your instances in the pre-Version 9.7 by running the db2icrt. Then restore the database manager configuration parameter values for each instance using the UPDATE DATABASE MANAGER CONFIGURATION command.
  6. For each pre-Version 9.7 instance, log on to the DB2 server as the instance owner and restore your upgraded databases from a pre-Version 9.7 offline full backup by running the RESTORE DATABASE command. You cannot upgrade your databases from DB2 Version 9.7 to pre-Version 9.7 release.

    If you recreated the instances using the same instance owner they had prior to upgrade and you did not upgrade a database to a DB2 Version 9.7 instance, the database is still in pre-Version 9.7 release and you can access it by just re-cataloging it.

  7. If you have recoverable databases and you want to rollforward through the log files you had before the upgrade, rename all the S*.MIG files in the active log path using the .LOG extension and issue the ROLLFORWARD DATABASE command as shown in the following example on Windows operating system:
    cd E:\DB2_01\NODE0000\SQL00001\SQLOGDIR
    dir S*.MIG
    25/02/2008  10:04 AM            12,288 S0000000.MIG
    25/02/2008  10:10 AM            12,288 S0000001.MIG
    25/02/2008  09:59 AM         4,104,192 S0000002.MIG
    25/02/2008  10:10 AM         4,104,192 S0000003.MIG
    25/02/2008  10:19 AM         4,104,192 S0000004.MIG
                   5 File(s)     12,337,152 bytes
                   2 Dir(s)   4,681,842,688 bytes free
    rename S*.MIG S*.LOG
    dir S*.LOG
    25/02/2008  10:04 AM            12,288 S0000000.LOG
    25/02/2008  10:10 AM            12,288 S0000001.LOG
    25/02/2008  09:59 AM         4,104,192 S0000002.LOG
    25/02/2008  10:10 AM         4,104,192 S0000003.LOG
    25/02/2008  10:19 AM         4,104,192 S0000004.LOG
                   5 File(s)     12,337,152 bytes
                   2 Dir(s)   4,681,842,688 bytes free