Entering content frame

Procedure documentation In-Place Migration with SDBINST and Follow-Up Actions Locate the document in its SAP Library structure

Use

You use the program SDBINST to upgrade database instances. First you install the new version of the SAP DB software. Then you migrate the database instance(s).

The source version of the database software is Version 7.3.00 Build 025 or higher, the target version is 7.4.03 or higher (see also Selection of the Upgrade Strategy).

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 valid for database instances of the type SAP DB OLTP only. It is valid for all supported operating system platforms.

Prerequisites

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

·        You have a backup medium for a complete data backup.

Procedure

Recommendation

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, in the event of an error, 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, in the event of an error, you can use this backup to recover a Version 7.3 database instance only. Therefore, it is not equivalent to a data backup in the operational state COLD during the migration process.

...

       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).

Note

If you have installed the SAP DB Version 7.3 on your server with the Red Hat Package Manager, you can now perform subsequent installations with this program only. You can not use the SDBINST program for subsequent installations.

       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 operator 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

Caution

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

db_offline

       3.        

Transfer 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.        

Transfer 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 recreate the 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.
You connect to Version 7.4 of the DBM server. Previously, you communicated with Version 7.3 of the DBM server.

dbmcli –d <database_name> -u <dbm_user>,<password>

   12.        

Start the migration of the database parameters.

param_checkall

   13.        

If you are upgrading to database version 7.4.04 on a UNIX operating system, then perform the following steps:

a.  Log off from the Database Manager CLI.

b.  Call the program chvolperm. This program changes the owner, group, and access rights to the volumes of the database instance according to the authorization concept for UNIX operating systems.

c.  Log on to the Database Manager CLI again.

 

 

 

 

exit | release | quit | bye

 

<dependent_path>/bin/chvolperm <database_name>

 

 

dbmcli –d <database_name> -u <dbm_user>, <password>

   14.        

Transfer the database instance to the operational state ADMIN.

db_admin

   15.        

Execute the migration command.

Caution

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

   16.        

Transfer the database instance to the operational state OFFLINE.

db_offline

   17.        

Restart the database instance. The database catalog migrates from 7.3 to 7.4.

db_online

   18.        

Reload the system tables.

You see a message about the successful completion of the procedure.

load_systab

Result

You have migrated your database instance from Version 7.3 of the software to Version 7.4.

It is in the operational state ONLINE.

 

Leaving content frame