"Aria Operations upgrade failure from 8.12.1 to 8.17.2 at step 9 with the error: "Failed resource key=pak_manager.action_failed resource args=[run sql db upgrade]"
search cancel

"Aria Operations upgrade failure from 8.12.1 to 8.17.2 at step 9 with the error: "Failed resource key=pak_manager.action_failed resource args=[run sql db upgrade]"

book

Article ID: 388660

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

Upgrade from 8.12.1 to 8.17.2 failing at Step 9 of 14 with the error Failedresource key=pak_manager.action_failed resource args=[run sql db upgrade]

The following errors can be observed in the sqldbupgrade.log file:

10:35:31.688 [main] INFO  com.vmware.vcops.dbupgrade.postgres.sharded.UpgradeActionExecutorManager - Upgrading to version: 181
10:35:31.688 [main] INFO  com.vmware.vcops.dbupgrade.postgres.sharded.UpgradeActionExecutorManager - Executing sql script: /postgres/sharded/818/remove_dt_events.sql
...
10:35:38.954 [main] ERROR com.vmware.vcops.dbupgrade.postgres.sharded.UpgradeActionExecutorManager - Upgrade failed on action: UpgradeAction [dataChanged=false, cleanUpBadData=false, steps=[Step [action=818/remove_dt_events.sql, type=SQL]], version=181, transactional=true]
java.lang.RuntimeException: java.lang.RuntimeException: java.lang.RuntimeException: org.postgresql.util.PSQLException: ERROR: MultiXactId 1702194274 has not been created yet -- apparent wraparound

Environment

Aria Operations 8.12.1

Cause

The upgrade is failing due to data db upgrade script running a monolithic delete on large alarm tables, that results in a transaction that is too large for the default memory settings used during upgrade, and that are causing postgres transaction wraparound errors.

 

Resolution

If you need assistance with the workaround, contact technical support and note this Knowledge Article ID (388660). For more information, see How to Submit a Support Request