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.5.x if only the build number of the version has changed between the source and target version, and also for upgrades from 7.4.03 to 7.5.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 combined with 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 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. 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.
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 that you want to upgrade must not have been changed since the last restart.
· The database instance that you want to upgrade must be the only instance that refers to the installation path of the software that you want to update.
· The database instances is in one of the three defined operational states, which means that there are no errors.
...
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 SDBUPD program for the database instance by entering the following commands:
UNIX, Linux: |
Microsoft Windows: |
./SDBUPD –d
<database_name> -u <dbm_user>,<password> |
sdbupd –d <database_name> -u <dbm_user>,<password> |
You then only need to specify the <sdb_user>special operating system user and the <sdba_group> group if you are performing an upgrade for software version 7.5.00 (see Database System Concepts, UNIX: Special Operating System Users and Groups).
SDBUPD performs the upgrade, and displays a message to indicate that the upgrade has been completed successfully. It then flags the installation as complete.
The specified database instance and its software have been upgraded.
If you have upgraded a liveCache database instance, it is now in the operational state OFFLINE.
If you have upgraded an OLTP database instance, it is now in the operational state ONLINE.