Procedure documentationUpgrade if Several Databases Use the Software Installation Locate this document in the navigation structure

 

Use the SDBINST program for an upgrade if several databases refer to the same installation path. Use this procedure to upgrade one or more of these databases.

Within the upgrade process, you first install the new version of the database software additionally to the old one, and then upgrade one or more database/s that use the old software version to the new software version. At the end of the upgrade process, both software versions exist in parallel on the database computer. Depending on the number of databases you have upgraded, you may have databases still using the old software version and upgraded databases now using the new software version.

Before starting the SDBINST program on any operating system, stop all databases that use the software installation to be upgraded (not only those you plan to upgrade to the new version), and stop all DBM Server processes.

On Microsoft Windows also stop X Server before starting the SDBINST program. Remember that this interrupts the communication between the clients and all local databases. On Unix/Linux, stopping X Server is not necessary since from version 7.5 the X Server software supports an update of the database software while X Server is running.

Recommendation Recommendation

If you have changed parameters of a database to be upgraded after the last restart , we also recommend that you first restart that database. This will prove that your database is still restartable and that no inconsistent changes have been made. Only then start the upgrade process to make sure that it does not fail because of parameter inconsistencies.

End of the recommendation.

Prerequisites

  • The databases to be upgraded are in a defined operational state - in other words, no errors may exist.

  • You have a backup template for a complete data backup for each of the databases to be upgraded.

Procedure

Caution Caution

To ensure the security of your data in the case of a possible error during the upgrade process, we strongly recommend that you perform a complete data backup of the database in the ADMIN operational state as part of the upgrade process. This causes additional downtime while the backup is performed. However, if an error occurs, the data backup produced in this way can be imported into a database of the start or target version.

Alternatively, you can perform a complete data backup in the ONLINE operational state before starting the upgrade process. However, in the event of an error, you can use this backup to recover the start version of the database only. It is therefore not equivalent to a data backup performed in the ADMIN operational during the upgrade process.

End of the caution.

  1. Install the target version software (zip file or tgz package) using SDBINST in the installation path <dependent_path_new> parallel to the installation path of the old software version (in other words, without overwriting the old software version).

  2. Perform the following series of steps for each of the databases to be upgraded:

    Action

    Command

    1.

    Call Database Manager CLI, log on as a DBM operator and connect to the database to be upgraded.

    >dbmcli –d <database_name> -u <dbm_operator>,<dbm_operator_password>

    2.

    Transfer the database to the OFFLINE operational state.

    Note Note

    Use the DBM command db_offline, and not db_stop. This is the only way of making sure that you can restart the database if an error occurs.

    End of the note.

    >db_offline

    3.

    Transfer the database to the ADMIN operational state.

    >db_admin

    4.

    For databases of the start version 7.5, open a utility session.

    For databases of the start version ≥ 7.6, open a database session.

    >util_connect

    >db_connect

    6.

    Perform a complete data backup in the current operational state ADMIN.

    >backup_start <medium_name>

    7.

    Exit the utility session or the database session, respectively.

    >util_release

    or

    db_release

    8.

    Transfer the database to the OFFLINE operational state.

    >db_offline

    9.

    Assign the database to the new software version.

    >db_reg –R <dependent_path_new>

    10.

    Exit Database Manager CLI.

    >exit | release | quit | bye

    11.

    Call Database Manager CLI again, log on as a DBM operator and connect to the database to be upgraded (session mode).

    >dbmcli –d <database_name> -u <dbm_operator>,<dbm_operator_password>

    12.

    Start the upgrade of the database parameters.

    >param_checkall

    13.

    Restart the database. The database catalog is upgraded from source version to the target version.

    >db_online

    14.

    Load the system tables.

    >load_systab

Result

A message is displayed indicating that the procedure has been successful.

You have upgraded your database/s from the source version of the database software to the target version.

The relevant database/s is/are now in the ONLINE operational state.