## In-Place Migration with SDBINST and Follow-Up Actions

### Use

You use the SDBINST program to upgrade database instances for version 7.3 and above. You first need to install the new version of the database software. You then need to migrate the database instance(s).

The start version of the database software is version 7.3.00 Build 025 or higher, and the target version is 7.5.00 or higher (see also Selecting an Upgrade Strategy).

If you would like to upgrade from version 7.3.00 to a version 7.6.00, the build of Version 7.6.00 must be greater than/equal to 12.

Use this procedure for database systems that are not part of an SAP system, particularly if multiple database instances refer to the same installation path.

This upgrade strategy is only valid for database instances that are of the OLTP instance type. It is valid for all supported operating system platforms.

### Prerequisites

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

● You have defined a backup template for a complete data backup.

### Procedure

To guarantee the security of your data in case of errors during migration, we recommend that you perform a complete data backup of the instance in the operational state COLD (in step 6 of the migration). This causes downtime because the database instance has to be stopped. However, if an error occurs, the data backup produced in this way can be imported into a database instance of the source version or a database instance of the target version.

Alternatively, you can perform a complete data backup in the operational state WARM before you start the migration. However, in the event of an error, you can only use this backup to recover the start version of the database instance. It is therefore not equivalent to a data backup in the operational state COLD during the migration process.

...

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

or

Install the software of the target version using the Red Hat Package Manager (rpm package).

If you have installed Version 7.3 of the database software on your computer using the Red Hat Package Manager, you must use this program to perform subsequent installations. It is not possible to use SDBINST for subsequent installations.

2. Perform the following migration steps for each of the database instances of your source version.

| Procedure | Command
... | Call Database Manager CLI as the DBM operator and connect to the database instance that you want to migrate. | >dbmcli –d <database_name> -u <dbm_operator>,<dbm_operator_password>
| Stop the database instance in the correct manner. Use the db_offline command; do not use db_stop. This is the only way of making sure that you can restart the database instance if an error occurs. | db_offline
| Transfer the database instance to the COLD operational state. | db_cold
| Open a utility session | util_connect
| Execute the command that prepares the migration. | util_execute migrate
| Perform a complete data backup in the COLD operational state. | backup_start <medium>
| Exit the utility session. | util_release
| Transfer the database instance to the OFFLINE operational state. | db_offline
| UNIX: Assign the database instance to the new software version. Microsoft Windows: Delete the database instance registration. | UNIX: db_reg –R <dependent_path_new> Microsoft Windows: db_drop WITHOUTFILES
| Exit Database Manager CLI. For Microsoft Windows only: Register the installation path of the new database software with Database Manager and create a database instance of this new software version. | exit | release | quit |bye >dbmcli –R <dependent_path_new> db_create <database_name> <dbm_operator>,<dbm_operator_password>
| Log on to Database Manager CLI again. | >dbmcli –d <database_name> -u <dbm_operator>,<dbm_operator_password>
| Start the migration of the database parameters. | param_checkall

If you are upgrading from database version 7.5.00 or lower to database version 7.5.00 or higher on a UNIX operating system, perform the following steps. Otherwise, proceed as described under point 14.

a. Log off from the Database Manager CLI.

b. Call the program SDBINST of the software version to which you want to upgrade. This program changes the owner, group, and access rights to the volumes of the database instance according to the authorization concept for UNIX (see Concepts of the Database System, Special Operating System Users and Groups (UNIX/Linux)).

c. Log on to Database Manager CLI again.

exit | release | quit |bye

>./SDBINST—main SAPDB::Install::Instance::ChVolPerm::main -d <database_name>

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

| If you are upgrading from a database version 7.3.00 to a database version 7.5.00, perform the following additional steps: Otherwise, proceed as described under point 15. d. Transfer the database instance to the ADMIN operational state. e. Enter the migration command. f. Transfer the database instance to the OFFLINE operational state. | db_admin util_execute migrate database db_offline
| Start the database instance again. The database catalog is migrated from 7.3 to the target version. | db_online
| Load the system tables. A message is displayed indicating that the procedure has been successful. | load_systab

### Result

You have migrated your database instance from software version 7.3 to the required target version.

The database instance is now in the ONLINE operational state.