Entering content frame

 Patch Installation with SDBINST and Follow-Up Actions 

Use

You use the program SDBINST to upgrade database instances. When you do this, only the database software is replaced. 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 OLTP only (see Selection of the Upgrade Strategy). It is valid for all supported operating system platforms.

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

If you work on 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 the 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 the X Server is running. In this case, you no longer need to stop the X Server and all database instances. However, you do need to stop the database instance that is assigned to the installation directory that is being updated.

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

Prerequisites

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.      If necessary, stop each database instance with the following command:

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

       2.      If necessary, stop the X Server.

x_server stop

       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 <sdb_user> -g <sdba_group>]

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

 

When you upgrade the software to Version 7.5.00, specify the special operating system user <sdb_user> and the group <sdba_group> according to the authorization concept for UNIX operating systems.

       4.      Start the X Server with the following command:

x_server start

       5.      Log on again 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.       

Update the software version of the database instance.

db_reg

       3.       

Update the parameters of the database instance.

param_checkall

       4.       

If you are upgrading to database version 7.5.00 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 –d <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