## Patch Installation with SDBUPD

### Use

You use the SDBUPD program to upgrade a database instance. When you do this, only the database software is replaced.

You can use this procedure for software version 7.6.x where only the version build number has changed between source and target version and for upgrades from 7.4.03 to 7.6.x and version 7.5.x to 7.6.x (see also Selecting an Upgrade Strategy).

You use this upgrade strategy if your database instance is part of an SAP system.

You can use this procedure even if the database instance is not integrated in an SAP system. To do this, however, the following prerequisites must be fulfilled:

● The SDBINST program must have been used to install the existing software (that is, with a tgz package or a zip file, and not an rpm package).

● Each database instance must refer to a separate software installation.

The procedure depends on whether your source version is lower than 7.5.00, or is 7.5.00 or higher, and on your operating system.

If your operating system is UNIX or Linux and your source version is lower than 7.5.00, then you must stop the X Server and all database instances before the upgrade. Remember that this interrupts communication between the clients and all local database instances. If your source version is 7.5.00 or higher, then the X Server software supports an update of the database software while X Server is running. You no longer need to stop the X Server. The database instance that you want to upgrade is stopped by SDBUPD during the upgrade.

If you are working on Microsoft Windows, you must always stop the X Server and all database instances.

### Prerequisites

Before you start upgrading a database instance, make sure that you have up-to-date log backups and/or data backups for recovering this database instance in the event of errors.

The database parameters of the database instance you want to upgrade must not have been changed since the last restart.

● The database instance you want to upgrade is the only instance that refers to the installation path of the software you want to update.

● The database instance is in a defined operational state - in other words, no errors may exist.

### Procedure

...

1. If necessary, stop each database instance with the following command one by one:

>dbmcli –d <database_name> -u <dbm_operator>,<dbm_operator_password> db_offline

2. If necessary, stop every individual scheduler:

>dbmcli –d <database_name> -u <dbm_operator>,<dbm_operator_password> scheduler_stop

3. If necessary, stop the X Server:

>x_server stop

4. Start the SDBUPD program for the database instance by entering the following commands:

UNIX, Linux: | Microsoft Windows:
>./SDBUPD –d <database_name> -u <dbm_user>,<password> [-o <sdb_user> -g <sdba_group>] | >sdbupd –d <database_name> -u <dbm_operator>,<dbm_operator_password>

You only need to specify the <sdb_user>special operating system user and the <sdba_group> if you are performing an upgrade for a software version below 7.5.00 (see Concepts of the Database System, Special Operating System Users and Groups UNIX/Linux)).

SDBUPD performs the upgrade, and displays a message to indicate that the upgrade has been completed successfully. It then flags the installation as complete.

### Result

The specified database instance and software belonging to the Server profile have been updated.

With this procedure, the software not belonging to the Server installation profile is not updated. To update this software, use SDBINST as described under Installing and Updating the Database Software.

If you have upgraded a liveCache database instance, it is now in the OFFLINE operational state.

If you have upgraded an OLTP database instance, it is now in the ONLINE operational state.