Operational Defect Database
BugZero updated this defect 58 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
VMware | 74698
vRealize Operations Manager Application upgrade fails with the error “run sql db upgrade” failed
Last update date:
3/22/2024
Affected products:
vRealize Operations
Affected releases:
6.67.06.7
Fixed releases:
No fixed releases provided.
Description:
Symptoms
The OS portion of the vRealize Operations Manager upgrade completes successfully.When attempting to apply the vRealize Operations Manager application PAK file, the upgrade fails with this message: Installation failed with error FailedPAK action “run sql db upgrade” failed The /storage/vcops/log/sqldbupgrade.log contains entries similar to: 2019-09-05 11:35:38,862 ERROR [main]com.vmware.statsplatform.persistence.util.sql.UpgradeActionExecutorManagerexecute - Upgrade failed java.lang.RuntimeException: java.lang.RuntimeException:java.lang.RuntimeException: java.lang.RuntimeException:org.postgresql.util.PSQLException: ERROR: right sibling's left-link doesn'tmatch: block 432 links to 6065 instead of expected 265 in index"idx_alarm_resource_canceltime" atcom.vmware.statsplatform.persistence.util.sql.UpgradeActionExecutorManagerupgradeDatabase(UpgradeActionExecutorManager.java:201) atcom.vmware.statsplatform.persistence.util.sql.UpgradeActionExecutorManagerexecute(UpgradeActionExecutorManager.java:70) atcom.vmware.statsplatform.persistence.util.sql.SqlDbUpgrade.main(SqlDbUpgrae.java:49) Caused by: java.lang.RuntimeException: java.lang.RuntimeException:java.lang.RuntimeException: org.postgresql.util.PSQLException: ERROR: rightsibling's left-link doesn't match: block 432 links to 6065 instead ofexpected 265 in index "idx_alarm_resource_canceltime" atcom.vmware.statsplatform.persistence.util.sql.UpgradeActionExecutorManagerexecuteSteps(UpgradeActionExecutorManager.java:226) atcom.vmware.statsplatform.persistence.util.sql.UpgradeActionExecutorManagerupgradeDatabase(UpgradeActionExecutorManager.java:197)
Cause
The issue can be caused by corruption on the disk or SEsparse.
Resolution
To resolve this issue, run a re-index on the alarms table in the postgres database. Log into the vRealize Operations Manager Primary node as root vi SSH or Console.Run the following command to reindex the alarm table: su - postgres -c "/opt/vmware/vpostgres/current/bin/psql -d vcopsdb -c 'reindex table alarm'"Note: The prompt will display REINDEX once the reindex is completed. Run \q to exit the database.Repeat steps 1-3 on all other vRealize Operations Manager Analytic nodes in the cluster. With the re-index successful, take new snapshots of the vRealize Operations Manager nodes and attempt the upgrade process again. It should now complete successfully.
Related Information
For more information on SRsparse, see Virtual Machines running on an SEsparse snapshot may report guest data inconsistencies.For more information on taking vRealize Operations Manager snapshots, see How to take a Snapshot of vRealize Operations Manager 6.x and later.
