Procedure documentationUpgrade if an Indidual Database Uses the Software Installation Locate this document in the navigation structure


Use the SDBUPD program to upgrade a database. In this process, update the existing software and simultaneously upgrade the existing database to this new version.

The SDBUPD program automatically stops the database to be upgraded during this process.

For source versions < 7.8 on Microsoft Windows, the SDBUPD program also stops the X server, provided that no other databases are running on this computer. If there are other databases running on this computer, you must transfer them to the OFFLINE operational state before starting the upgrade. Otherwise, the upgrade process will stop with an error. On Unix/Linux, stopping the 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.

In case the scheduler is running on the database to be upgraded, stop the scheduler before starting the SDBUPD program. After having performed the upgrade, you must re-start the scheduler for the jobs to be executed.

Recommendation Recommendation

Before you start the upgrade process, make sure you have up-to-date log backups and data backups for recovering the database in the event of an error.

If you have changed parameters of the database to be upgraded after the last restart , we also recommend that you first restart the 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.


  • The SDBINST program or Installation Manager has been used to install the existing software.

  • The database is in a defined operational state - in other words, no errors may exist.

  • It is the only database which uses the software to be updated.

  • For the SAP MaxDB communication server the following prerequistes must be fulfilled:

    For Source Version ≥ 7.8

    On Unix and Linux

    On Windows

    From Source Version ≥ 7.8

    Stopping the global listener is not necessary.

    If the global software is to be changed, stop the global listener before the installation or update (see: Utilities, Stopping the Global Listener and/or Installation-Specific X Servers).

    Note that as per the system default, the global software is updated only if the target version of the global software is higher than the source version.

    If the target version of the global software is lower than the source version, the update process will not change the global software unless you explicitly specify the -update_global option.


  1. Call Database Manager CLI in session mode, 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. Check whether the scheduler function is active:


  3. If the scheduler function is active, stop it using the following command:


    Otherwise proceed with step 4.

  4. Exit Database Manager CLI:


  5. Start the SDBUPD program by entering the following command:

    Microsoft Windows


    >sdbupd -d <database_name> -u <dbm_operator>,<dbm_operator_password>

    >./SDBUPD -d <database_name> -u <dbm_operator>,<dbm_operator_password>

    SDBUPD performs the upgrade and displays a message to indicate that the upgrade has been completed successfully. It then flags the installation as complete.


The specified database and its server software, that is the software stored in the installation path, have been updated.

Caution Caution

With this procedure, the global software is not updated. To update this software, use the SDBINST program as described under Installations or Updates in the Command Line.

End of the caution.

The database that has been upgraded is now in the ONLINE operational state.