Post patching ALCM (Aria lifecycle Manager) and VIDM (VMware identity manager), new versions are not updated in SDDC Manager

Products

• VMware SDDC Manager

Issue/Introduction

This article outlines the procedure to manually update the SDDC Manager database to reflect accurate ALCM and VIDM versions.

VIDM was recently patched outside of SDDC manager and is showing older version/build.

Environment

VMware Cloud foundation 5.x

Cause

This is a expected behavior when VIDM and ALCM is updated from outside the SDDC Manager.

SDDC Manager maintains its own inventory database of product versions. When VIDM and ALCM is upgraded outside of the SDDC Manager lifecycle management workflow (out-of-band upgrade), the inventory database is not automatically updated. This causes the SDDC Manager UI to display the old version even though the VIDM and ALCM are running the new version.

Resolution

Workaround : 
Note: Ensure a valid backup or snapshot of the SDDC Manager is taken prior to implementing any modifications.

To manually update the wsa component version in the SDDC Manager database, execute the following procedure:

1. Access the SDDC Manager via SSH as the root user.

2. Connect to the PostgreSQL database using the local connection:
psql -h localhost -U postgres

3. Switch to the platform database context:
\c platform

4. Identify the target wsa ID by listing existing records:
SELECT * FROM wsa;

5. Update the version for the identified record:
UPDATE wsa SET version = '<VERSION_STRING>' WHERE id = '<TARGET_ID>';

6. Verify the update by re-running the selection query:
SELECT * FROM wsa;

Log in to the SDDC Manager and verify that the updated component version is correctly reflected in the inventory view.