Node2 config and historical datastore component activation fails with the error message:java.rmi.NoSuchObjectException: no such object in table

From DocWiki

Jump to: navigation, search

Node2 config and historical datastore component activation fails with the error message:java.rmi.NoSuchObjectException: no such object in table

Problem Summary Node2 config and historical datastore component activation fails with the below error message:

java.rmi.NoSuchObjectException: no such object in table 21468: Feb 02 20:10:44.216 JST %MADM-ADM_CFG-3-EXCEPTION:com.cisco.cluster.ClusterException: Component Controller CRS Config Datastore on node 2 : Enable; nested exception is: 21469: Feb 02 20:10:44.216 JST %MADM-ADM_CFG-3-EXCEPTION: com.cisco.database.util.DBException: setupLinkedServers; nested exception is: 21470: Feb 02 20:10:44.216 JST %MADM-ADM_CFG-3-EXCEPTION: com.cisco.database.util.DBException: Setting up linked servers failed.

Error Message java.rmi.NoSuchObjectException: no such object in table

21468: Feb 02 20:10:44.216 JST %MADM-ADM_CFG-3-EXCEPTION:com.cisco.cluster.ClusterException: Component Controller CRS Config Datastore on node 2 : Enable; nested exception is: 21469: Feb 02 20:10:44.216 JST %MADM-ADM_CFG-3-EXCEPTION: com.cisco.database.util.DBException: setupLinkedServers; nested exception is: 21470: Feb 02 20:10:44.216 JST %MADM-ADM_CFG-3-EXCEPTION: com.cisco.database.util.DBException: Setting up linked servers failed

Possible Cause DB Component during setting the LinkedServer seems to perform the activity on the remote node using RMI. DBManager during its startup exports an object to the RMI registry in CVD. Though it seems to be successful, the entry could be stale.
Recommended Action Restart Node1 Node manager and try the component activation again.
Release Release 7.0, Release 5.0
Associated CDETS # None

Rating: 0.0/5 (0 votes cast)

Personal tools