|Applies To||RSA Product Set: RSA Identity Governance & Lifecycle |
RSA Version/Condition: 6.x, 7.0.x, 7.1.x, 7.2.x
|Issue||The server or servers that the RSA Identity Governance & Lifecycle application runs on are listed in the RSA Identity Governance & Lifecycle user interface under Admin > System > Server Nodes and in table T_SERVER_NODES in the AVUSER schema. Sometimes the server node configuration contains incorrect information. We have seen this problem after an upgrade, a database migration, or a restoration of a database from another system where the server node(s) still point to the original system. This RSA Knowledge Base Article describes how to restore the Server Nodes to their correct configuration.|
|Resolution||This issue may be resolved by truncating the T_SERVER_NODES table and restarting RSA Identity Governance & Lifecycle.|
NOTE: Truncating this table is a safe approach and will remove all data from the table. Removing all the data from this table ensures that the startup will be able to re-configure the data in this table correctly.
If you have access to the user interface and there are Action buttons available under the Admin > System > Server Nodes > Action column, you may follow the instructions on the buttons (Delete, Make next SON) and restart RSA Identity Governance & Lifecycle later. However, the truncate table solution that is documented here will work in any situation where the server nodes are incorrectly configured.
This will repopulate the T_SERVER_NODES table with the correct node (or nodes if this is a cluster.)