In-Place Migration with SDBUPD


You use the SDBUPD program to upgrade a database instance.

You use this procedure if the database instance is part of an SAP system.

This upgrade strategy is valid only for an OLTP instance. It is valid for all supported operating system platforms.


?     The database instance that you want to upgrade is part of an SAP system.

?     The database instance is in ONLINE operating state or, in the case of version 7.3, in WARM state.

?     The database instance is the only instance that refers to the installation path of the software version you want to update.

?     The database parameters of the database instance that you want to upgrade have not changed since the last restart.

?     The source version of the database software is Version 7.3 Build 025 or higher and the target version 7.5.00 or higher (See also: Selecting an Upgrade Strategy).





Call the Database Manager CLI as the DBM operator, and connect to the database instance to be migrated

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

Log on to Database Manager CLI and stop the database instance that you want to upgrade.

If the existing X Server has a version lower than 7.5, then use this command to stop all database instances one by one.


Transfer the database instance you want to upgrade to the operational state COLD (up to Version 7.3) or ADMIN (from Version 7.4).

db_cold | db_admin

If you have a more recent data backup, perform an incremental data backup and a log backup. Otherwise, perform a full complete backup (backup start).

backup_start <medium> [<type>] [AUTOIGNORE]

Exit Database Manager CLI.

exit | release | quit |bye

If the source version is lower than 7.5.00, stop the X Server.

If your source version is 7.5.00 or higher, then the X Server software supports an update of the database software while the database is running. In this case, you no longer need to stop the X Server.

>x_server stop

Start the SDBUPD program.

SDBUPD performs the upgrade, and displays a message when it is completed successfully. It then flags the installation as complete.

The execution of this command can take a long time. Under no circumstances should you terminate it. If you do, you risk losing all your data. Your only option in this event is to use data backups to revert to the database instance state that is stored in these backups.


>./SDBUPD –d <database_name> -u <dbm_operator>,<dbm_operator_password>
[-o <sapdb_user>
-g <sapdb_admin>]

You then only need to specify the special operating system user <sdb_user> and the group <sdba_group> if you are performing an upgrade for software version 7.5.x (see Concepts of the Database System, UNIX: Special Operating System Users and Groups (UNIX/Linux)).

Microsoft Windows:

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


The specified OLTP database instance and software belonging to the Server profile have been updated.

With this procedure, the software not belonging to the Server installation profile is not updated. To update this software, use SDBINST as described under Installing and Updating the Database Software.

The database instance is in the ONLINE operational state.