Different issues occured during the IP address change for VMware Identity Manager 3.3.7

Products

• VMware Aria Suite

Issue/Introduction

While changing the assigned IP address for VMware Identity Manager 3.3.7 as outlined in the Documentation "Changing the IP Address of VMware Identity Manager 3.3.7 Appliance" below issues occurred:

1. 1. trying to access the database failed with this error:
      
   2. updating the database has returned "UPDATE 0" instead of "UPDATE 1"
   3. the Inventory sync has failed as it was not able to find the VM using the IP address

Environment

VMware Identity Manager 3.3.7

Resolution

Issue 1:

It can occur that vPostgres did not create a socker connection, to access the database please modify the command to connect via localhost: 

psql -h localhost -U horizon saas

Issue 2:

You may find the database records have already been updated after starting the vIDM appliance/-s. To validate current assigned IPs you can use this command instead:

select * from "ServiceInstance";

Issue 3:

If the Inventory sync was not able to locate the vIDM node/-s via IP address then please skip this step and afterwards run another Inventory Sync which should complete as the globalenvironment was updated in previous Inventory Sync.