Post-patching to CSP-102547 vIDM services fails to start due to out-of-space condition during PostgreSQL upgrade
search cancel

Post-patching to CSP-102547 vIDM services fails to start due to out-of-space condition during PostgreSQL upgrade

book

Article ID: 443990

calendar_today

Updated On:

Products

VMware Aria Operations (formerly vRealize Operations) 8.x

Issue/Introduction

After applying a patch to VMware Identity Manager 3.3.7, the vIDM services fails to start. When reviewing the Horizon logs, reveals database connectivity errors indicating that the application cannot retrieve the SuiteToken signing certificate from the EncryptionService due to missing chunks in the PostgreSQL TOAST tables.

YYYY-MM-DDT HH:MM:SEC ERROR org.hibernate.engine.jdbc.spi.SqlExceptionHelper - ERROR: missing chunk number 0 for toast value 21406 in pg_toast_16621
YYYY-MM-DDT HH:MM:SEC ERROR com.vmware.horizon.components.identity.SuiteTokenService - Failed to get SuiteToken signing cert from EncryptionService.

Environment

VMware Identity Manager 3.3.7

Cause

The underlying root cause is an out-of-space condition on the appliance disk during the automated PostgreSQL database migration sequence. The migration process fails abruptly with No space left on device error while attempting to copy data relations within the saas.OAuth2RefreshToken_value schema:

error while copying relation "saas.OAuth2RefreshToken_value": could not write file "/db/data/base/16402/17237": No space left on device
Failure, exiting
Postgres upgrade from 9.6 to 14.x failed

Since the upgrade routine terminates mid-process, the database is left in an inconsistent, partially migrated state, which prevents the vIDM services from initializing post-patching.

Resolution

To resolve this issue, manually extend the appliance partitions to provide adequate disk space and re-run the patch execution utility.

  1. Increase the space allocated to the virtual appliance disks via vCenter

  2. Expand the sdb and sdc storage partitions on the appliance by at least 20 GB by following the validated procedures in How to increase vIDM appliance disk space.

  3. Once the partitions are successfully extended and verified, re-run the patch execution script. The script will complete the database schema copy operations and start the vIDM services normally. vIDM patch