External Database information in the 2nd vApp node was not replicated properly.
This is a known issue that is recorded in bug ticket DE471066
Release : vApp 14.3 with vApp 14.3 CP2
Component : CA IDENTITY SUITE (VIRTUAL APPLIANCE)
This is a known issue that is recorded in bug ticket DE471066 and permanent fix for this issue is planned in vApp 14.3 CP3. At the time this article is written, vApp 14.3 CP3 has not been released.
At the moment, we can do the following workaround.
a. Restart the 1st vApp if it is down and then access 1st vApp's dashboard and go to Setup screen and edit the database, reconfigure database with the same configuration, click the test database connections and then Apply, the following dialog will be shown
Database configuration changes require application restart, Click Ok to proceed.
Then click Ok.
Applied Database Configuration dialog will appear, and show all the green check marks.
b. Now power off the 1st vApp node
c. Access the 2nd vApp's dashboard and go to Setup Screen and remove the 1st vApp (click the 'x' icon in the vApp box) and deploy
There is available fix, please check https://knowledge.broadcom.com/external/article?articleId=201481