Users Guide

B
Upgrade failure recovery on Linux
operating system
Use install.sh command in the new OMPC version package to do upgrade or install OMPC. The
install.sh command detects the version of OMPC. if there is an old version installed, upgrade process
is initialized. If not, then a new version is installed.
Check OMPC status
If the installer process is stopped or server is switched off during upgrade, the upgrade fails. Follow the
steps to troubleshoot the upgrade failure scenario:
1. Run rpm –q OpenManage_PowerCenter command on the command line interface to get the
current version OMPC.
2. If the OMPC old version is displayed, for example 3.0.1.XXXX, it means OMPC upgrade operation has
not been started, see Recover OMPC section.
3. If the OMPC new version is displayed, for example “3.1.0.XXXX”, it means OMPC upgrade has been
started, see Check OMPC database daemon status section.
4. If neither old nor new version is displayed, see Rollback to previous OMPC version section.
5. See OMPC database upgrade status to view the upgrade status.
Recover OMPC
1. Copy any files in /etc/ompc/backup/[OMPCFODLER] back to the [InstDir] with the same folder
structure: cp –rf /etc/ompc/backup/[OMPCFODLER] [InstDir].
2. Move the backup pgdata folder (e.g. /opt/dell/pgdatabak) back to [InstDir], rename it to the original
name (e.g. pgdata) if changed.
rm -r -f /opt/dell/ompc/pgdata
and
mv -f /opt/dell/pgdatabak /opt/dell/ompc/pgdata
3. Run the [InstDir]/startup.sh command to start the old OMPC daemons.
4. Remove /etc/ompc if they exist.
Check OMPC database daemon status
Check if the file upgradeok exists in /etc/ompc. If yes, it means that the upgrade is completed
successfully. If not, run [InstDir]/ompcstatus command to check OMPC database daemon status.
1. Run [InstDir]/tools/ompc-pgsql-daemon start command to start the database daemon.
NOTE: If the OMPC database daemon cannot be started, it means that the OMPC upgrade has
failed, see Rollback to previous OMPC version.
135