In-Place Migration with SDBINST and Follow-Up
Actions 
You
are using the program SDBINST to upgrade
database
instances. First install the new version of the SAP DB software. Then
migrate the database instance(s).
The source version of the database software is Version 7.3.00 Build ³ 025, the target version is ³ 7.4.03 (Selection of the Upgrade Strategy).
Use this procedure for database systems that are not combined with an SAP system, particularly if multiple database instances refer to the same installation path.
This
upgrade strategy is valid for database instances of the type
SAP DB OLTP only.
It is valid for all supported
operating system
platforms.
· The database instance you want to update is not part of an SAP system.
·
You have a
backup medium
for a
complete
data backup.

To guarantee the security of your data if any errors
occur in the migration, we recommend that you make a
complete data
backup of the instance in step 6, in the
operational state
COLD. This causes downtime because the database instance has to stop. However,
the resulting data backup can be used to
recover the database
instance in both Version 7.3 and Version 7.4.
Alternatively, you can make a complete data backup in the operational state WARM before you start the migration. However, you can use this backup to recover a Version 7.3 database instance only, and is not a completely valid alternative to a data backup in the operational state COLD.
...
1. Install Version 7.4 of the software with SDBINST ( zip file or tgz package) in the installation path <dependent_path><7.4> in parallel with Version 7.3.
or
Install Version 7.4 with the Red Hat Package Manager ( rpm package).

If you use the Red Hat Package Manager to install SAP DB Version 7.3 on your server, you will then be able to use only this program for any other installations. SDBINST installations are no longer possible.
2. Perform the following migration steps for each of your database instances with Version 7.3.
|
|
Procedure |
Command |
|
... 1. |
Call the Database Manager CLI as the DBM user and connect to the database instance that you want to migrate. |
dbmcli –d <database_name> -u <dbm_user>,<password> |
|
2. |
Stop the database instance correctly
Use the command db_offline and not db_stop. This is the only way of making sure you can restart the database instance if there are errors. |
db_offline |
|
3. |
Switch the database instance to the operational state COLD. |
db_cold |
|
4. |
Execute the command that prepares the migration. |
util_execute migrate |
|
5. |
Open a utility session. |
util_connect |
|
6. |
Make a complete data backup in the operational state COLD. |
backup_start <medium> |
|
7. |
Exit the utility session. |
util_release |
|
8. |
Switch the database instance to the operational state OFFLINE. |
db_offline |
|
9. |
UNIX: Assign the database instance to Version 7.4 of the software. Microsoft Windows: Delete the registration of the database instance. Use Version 7.4 of the DBMCLI software to create the new database instance. |
UNIX: db_register –R <dependent_path><7.4> Microsoft Windows: db_drop WITHOUTFILES |
|
10. |
Exit the Database Manager CLI. |
exit | release | quit | bye |
|
11. |
Log
on to the Database Manager CLI again. |
dbmcli –d <database_name> -u <dbm_user>,<password> |
|
12. |
Start the migration of the database parameters. |
param_checkall |
|
13. |
Switch the database instance to the operational state ADMIN. |
db_admin |
|
14. |
Execute the migration command.
The execution of this command may take some time, depending on the size of the database instance. Do not terminate it. |
util_execute migrate database |
|
15. |
Switch the database instance to the operational state OFFLINE. |
db_offline |
|
16. |
Start the database instance again. The database catalog migrates from 7.3 to 7.4. |
db_online |
|
17. |
Load the system tables again. You see a message about the successful completion of the procedure. |
load_systab |
You have migrated your database instance from Version 7.3 of the software to Version 7.4.
It is in the operational state ONLINE.