You use the program SDBINST to upgrade database instances from Version 7.3 to 7.5. First you install the new version of the database 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.5.00 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 OLTP only. It is valid for all supported operating system platforms.
· The database instance you want to upgrade 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 be stopped. 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 the target version.
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 the source version of the database instance only. Therefore, it is not equivalent to a data backup in the operational state COLD during the migration process.
...
1. Install the source version of the software with SDBINST (zip file or tgz package) in the installation path <dependent_path><target_version> in parallel with the installation path of Version 7.3.
or
Install the software of the target version with the Red Hat Package Manager (rpm package).
If you have installed Version 7.3 of the database software 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 the source version.
|
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 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 the new software version <target_version>. |
UNIX: db_reg –R <dependent_path><target_version> Microsoft Windows: db_drop WITHOUTFILES |
10. |
Exit the Database Manager CLI. For Microsoft Windows only: Register the installation path of the new database software with the Database Manager and create a database instance of this new software version. |
exit | release | quit | bye
dbmcli –R <dependent_path><target_version> db_create –d <database_name> -u <dbm_user>,<password> |
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. |
If you are upgrading to database version 7.5.00 or higher on a UNIX operating system, then perform the following steps. Otherwise, proceed as described under point 14: 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 –d <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. The execution of this command may take some time, depending on the size of the database instance. Do not cancel it under any circumstances. |
util_execute migrate database |
16. |
Transfer the database instance to the operational state OFFLINE. |
db_offline |
17. |
Restart the database instance. The database catalog is migrated from 7.3 to the target version. |
db_online |
18. |
Reload the system tables. You see a message about the successful completion of the procedure. |
load_systab |
You have migrated your database instance from software version 7.3 to the required target version.
It is in the operational state ONLINE.