## Patch Installation with SDBINST and Follow-Up Actions

### Use

You use the SDBINST program to upgrade database instances. When you do this, only the database software is replaced. You must then perform the necessary follow-up actions on the command line using Database Manager CLI.

This upgrade strategy is valid for OLTP database instances only (see Selecting an Upgrade Strategy). It is valid for all supported operating system platforms.

The procedure depends on whether your source version is 7.5.00 or higher, or lower than 7.5.00, 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. In such cases, it is not necessary to stop the X Server and all the database instances. However, you do need to stop the database instance that is assigned to the installation directory that is being updated.

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

### Prerequisites

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

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

### Procedure

...

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

>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 SDBINST program with the options for installing the installation profile Server. For the <dependent_path>, make sure that you enter the correct software installation path of the database instance or instances 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 <sdb_user> -g <sdba_group>] | >sdbinst [-b] -profile server -indep_data <independent_data_path> -indep_prog <independent_program_path> -depend <dependent_path>

When you are upgrading the software from a version lower than 7.5.00, specify the <sdb_user> special operating system user and the <sdba_group> group according to the authorization concept for UNIX (see Database System Concepts, Special Operating System User and Groups (UNIX/Linux)).

5. Start the X Server with the following command:

>x_server start

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

| Procedure | Command
... | Log on to Database Manager CLI with the data of the database instance that you want to upgrade. | >dbmcli –d <database_name> -u <dbm_operator>,<dbm_operator_password>
| Update the software version of the database instance. | db_reg
| Update the parameters of the database instance. | param_checkall

If you are upgrading from a database version < 7.5.00 on a UNIX operating system, proceed as follows:

a. Log off from Database Manager CLI.

b. Call the chvolperm program. 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 Database Manager CLI again.

exit | release | quit |bye

<dependent_path>/bin/chvolperm –d <database_name>

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

| Transfer the database instance to the operational state WARM (up to Version 7.3) or ONLINE (from Version 7.4). | db_online | db_warm
| Load the system tables. A message is displayed indicating that the procedure has been successful. | load_systab
| Exit Database Manager CLI. | exit | release | quit |bye

### Result

The OLTP database instance specified and the software belonging to the Server installation 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.

The database instance is now in the ONLINE operational state.