Patch Installation with SDBINST and Follow-Up Actions 

Use the program SDBINST to upgrade database instances. This switches 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

Before you start the upgrade, 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 update refer to the same software installation.

Procedure

...

       1.      Stop the X Server.

x_server stop

       2.      On UNIX/Linux, stop the database instance that you want to update.
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:

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

exit | release | quit | bye

       3.      Start SDBINST with the options for installing the installation profile Server. Make sure that you enter the correct <dependent_path> of each database instance that you want to update.

UNIX/Linux:	Microsoft Windows:
./SDBINST [-b] -profile server -indep_data <independent_data_path> -indep_prog <independent_program_path> -depend <dependent_path> -o <owner> -g <group>	sdbinst [-b] -profile server -indep_data <independent_data_path> -indep_prog <independent_program_path> -depend <dependent_path>

       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 user, 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 update.	dbmcli –d <database_name> -u <dbm_user>, <password>
2.	Update the software version of the database instance.	db_register
3.	Update the parameters of the database instance.	param_checkall
4.	Switch the database instance to the operational state WARM (up to Version 7.3) or ONLINE (from Version 7.4).	db_online | db_warm
5.	Load the system tables again. You see a message about the successful completion of the procedure.	load_systab
6.	Exit the Database Manager CLI.	exit | release | quit | bye

Result

The OLTP database instance and its software has been updated.

It is in the operational state ONLINE.