Upgrading the Database

About Upgrading Database

If you have a newly created 9.1.9 database or if you are upgrading from 9.1.7 level, you can ignore the Critical Notes and go directly to Points to Remember Before Upgrading Your Database.

If you are upgrading an existing database to 9.1.9 level, before running the Upgrade CES Database option, you must run the succeeding manual steps.

Critical Notes

  1. In prior releases, the user defined functions (UDFs) were created by aspadm during database creation. From this release onwards, the UDFs will be created by cisdba during database upgrade. If you are upgrading a database to 9.1.9 level, you must:

    • Log on as aspadm.

    • Run the following script to drop all Stored Procedures, Stored Functions and User Defined Functions:

      $EDS_HOME/dbUtil/drop_storedproc.sh

    • Log on as cisdba and run the Upgrade CES Database option.

      Note: The preceding script should be run only once.

  2. The datatype of the Session Process ID (S_MON_PID) of the License Monitor class (S_MON_CLASS) has been changed. Due to this change, the S_MON_CLASS table is dropped and recreated during the CES Database Server Upgrade. This leads to loss of data.
    If you need to retain the S_MON_CLASS data, before upgrading the database to 9.1.9 level, you need to do the following in the given sequence.

  •  Save the S_MON_CLASS data

  • Run the Upgrade CES Database option

  • Restore the S_MON_CLASS data

Points to Remember Before Upgrading Your Database

  1. Once the Upgrade process starts, you cannot cancel or downgrade the database.

  2. Before upgrading, take a backup of the database depending on your requirement.

  3. A successful upgrade of a database should have no connections to the database while running the upgrade. To check if all the connections to the database are closed, login to the database instance as the instance owner or as aspadm and run the command:

    $ DB2 list applications

    If there are connections displayed, close all connections using the command:

    $ DB2 force applications all