rpm -ivh ‑‑dbpath /usr/soam/db ‑‑prefix /usr/soam symphonyDE‑linux2.6‑glibc2.3-x86-4.0.0-build_number.rpm ‑‑nomd5
For RPM 4.3.3_11, 4.2, and 4.1, the RPM database directory, as --dbpath specifies, must exist on the local disk before installing. Also, these RPM versions do not support the rpm --prefix option. RPM uses the RPM_INSTALL_PREFIX to determine the installation directory. To install in a different directory, set RPM_INSTALL_PREFIX so that RPM can install the product to the specified destination directory.
For RPM version 3.0.6, the RPM database directory you specify with the --dbpath option must exist on the local disk before installing. You must also specify the --nodeps option
mkdir /opt/symphonyDE/DE40/dbsetenv RPM_INSTALL_PREFIX /opt/symphonyDE/DE40ln -s ./opt/symphonyDE/DE40 /soamrpm -iv --dbpath /opt/symphonyDE/DE40/db --prefix /soam symphonyDE-linux2.6-glibc2.3-x86-4.0.0-build_number.rpm --nodeps
If you install the product using the customized dbpath, use the same dbpath when you uninstall the product.
For RPM versions 4.2, 4.1.1, and 4.0.3, during upgrade, the installer is not able to remove the previous version of EGO from the RPM database. For RPM version 4.2, the installer reports success at this step, for other versions it shows an error message. The change to the RPM database is only done to prevent accidental uninstallation, but for these versions of RPM, this change is not possible.
This problem is not serious because it does not affect the operation of the cluster, but you must never uninstall the previous version of Platform EGO. The upgraded cluster uses many files and components from the original installation, and cannot work if you uninstall the original software.