Entering content frame

Procedure documentation Patch Installation with SDBINST and Follow-Up Actions Locate the document in its SAP Library structure

Use

You use the program SDBINST to upgrade database instances. This substitutes the SAP DB software only. You must then perform the necessary follow-up actions in the command line with the Database Manager CLI.

This upgrade strategy is valid for database instances of the type SAP DB OLTP only (Selection of the Upgrade Strategy). It is valid for all supported operating system platforms.

Prerequisites

Recommendation

Before you start the upgrade process, make sure that you have up-to-date log backups and/or data backups for recovering the database instances in the event of errors.

·        All database instances that you want to upgrade refer to the same software installation.

Procedure

...

       1.      Stop the X Server.

x_server stop

       2.      On UNIX/Linux, stop the database instances that you want to upgrade.
On Microsoft Windows, stop all database instances.

To do this, execute the following commands for logging on to the Database Manager CLI, stopping the database instance, and exiting the Database Manager CLI for each database instance in the order that you want to upgrade the instances:

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

exit | release | quit | bye

       3.      Start the SDBINST program with the options for installing the installation profile Server. Make sure that, for the <dependent_path>, you enter the correct software installation path of the database instance or instances that you want to upgrade.

UNIX/Linux:

Microsoft Windows:

./SDBINST [-b] -profile server -indep_data <independent_data_path> -indep_prog <independent_program_path> -depend <dependent_path>
[-o <sapdb_user> -g <sapdb_admin>
[-gs <sapdb_support>]]

sdbinst [-b] -profile server -indep_data <independent_data_path> -indep_prog <independent_program_path> -depend <dependent_path>

 

Note

When you upgrade the software to Version 7.4.04, specify the special operating system user <sapdb_user>, and the groups <sapdb_admin> and <sapdb_support> according to the authorization concept for UNIX operating systems.

If you are upgrading the software to a version lower than 7.4.04, then use the options –o and -g to specify the owner and group of the database software.

       4.      Start the X Server with the following command:

x_server start

       5.      Log on to each of the database instances in sequence as the DBM operator, and perform the specified actions:

 

Procedure

Command

...

       1.       

Log on to the Database Manager CLI with the data of the database instance that you want to upgrade.

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

       2.       

Upgrade the software version of the database instance.

db_register

       3.       

Upgrade the parameters of the database instance.

param_checkall

       4.       

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>

       5.       

Transfer the database instance to the operational state WARM (up to Version 7.3) or ONLINE (from Version 7.4).

db_online | db_warm

       6.       

Load the system tables.

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

load_systab

       7.       

Exit the Database Manager CLI.

exit | release | quit | bye

Result

The specified OLTP database instance and its software have been updated.

It is in the operational state ONLINE.

 

Leaving content frame