Entering content frame

 Case 2: Downgrade for Dependent Software 

Use

Database instances exist that refer to a higher software version. You want to downgrade the software that is used exclusively by the database instance (Dependent Software).

Procedure

Delete the existing database instances before a downgrade.

·        If you want to perform the downgrade at build level only, there will be no incompatibilities between the database instances of the higher version and the software of the lower version you want to install. Proceed as follows for each database instance:

 

Procedure

Command

...

       1.        

Call the Database Manager CLI as the DBM operator and connect to the database instance.

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

       2.        

Delete the registration of the database instance.

db_drop WITHOUTFILES

       3.        

Exit the Database Manager CLI.

exit | release | quit | bye

       4.        

Uninstall at least the database kernel and the chosen software component(s) with the higher version.

sdbuninst –package "Database Kernel" [, <package_name2>…]

       5.        

Install your chosen installation profile with the lower version (for OLTP database instances at least Server, for liveCache database instances at least APO liveCache).

 If you are installing the software in SAP systems, read the important note below.

sdbinst –profile Server | "APO LiveCache" [, <inst_profile2>…]

       6.        

Register the database instance again. Enter the name and DBM user of the old database instance, and the path of the newly installed lower software version.

Unix/Linux:

<dependent_path>\bin
\dbmcli –s –R <dependent_path> db_create <database_name> <dbm_user>,<password>

Microsoft Windows:

"<dependent_path>\pgm
\dbmcli" –s –R "<dependent_path>" db_create <database_name> <dbm_user>,<password>

 

·        If the downgrade is combined with a change of version (minor or major release, see also: Version Notation) of the database software, proceed as follows:

 

Procedure

Command

 

Call the Database Manager CLI as the DBM operator and connect to the database instance.

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

       1.        

Delete the database instance

db_drop

       2.        

Exit the Database Manager CLI.

exit | release | quit | bye

       3.        

Uninstall at least the database kernel and the chosen software component(s) with the higher version.

sdbuninst –package "Database Kernel" [, <package_name2>…]

       4.        

Install your chosen installation profile with the lower version (for OLTP database instances at least Server, for liveCache database instances at least APO liveCache).

 If you are installing the software in SAP systems, read the important note below.

sdbinst –profile Server | "APO LiveCache" [, <inst_profile2>…]

       5.        

Start the Database Manager GUI. Use the Installation Wizard to create a new database instance by using the parameter file from a backup.

Choose Instance   ® Install.
Follow the instructions for creating or initializing a database instance. For the new database instance, specify the database administrator that is saved in the backup parameter file.

       6.        

Exit the Database Manager GUI.

Choose File ® Exit.

If you want to use this procedure in SAP systems, do not accept the system defaults. Specify the following settings instead:

<group>

For target version 7.5.00 or higher: sdba

For all previous database versions: sapsys

<owner>

For target version 7.5.00 or higher always: sdb

For all previous database versions

·        For OLTP database instances: sqdsid

·        For liveCache database instances: sidadm

<independent_data_path>

UNIX/Linux: /sapdb/data

Microsoft Windows: <drive>:\sapdb\data

<independent_program_path>

UNIX/Linux: /sapdb/programs

Microsoft Windows: <drive>:\sapdb\programs

<dependent_path>

UNIX/Linux: /sapdb/<SID>/db

Microsoft Windows: <drive>:\sapdb\<SID>\db

 

 

 

Leaving content frame