Not able to view/edit rmcm configurations from node2 appadmin in an HA setup
From DocWiki
(Difference between revisions)
| Line 5: | Line 5: | ||
! '''Problem Summary''' | ! '''Problem Summary''' | ||
| Node1 Appadmin displays the entire rmcm configuration correctly. However from node2 appadmin experiencing database inconsistency and unable to access/view the configurations under RMCM subsystem. Displaying the following message in the Appadmin. | | Node1 Appadmin displays the entire rmcm configuration correctly. However from node2 appadmin experiencing database inconsistency and unable to access/view the configurations under RMCM subsystem. Displaying the following message in the Appadmin. | ||
| - | |||
"There was an error reading/updating the database. Please contact the administrator." | "There was an error reading/updating the database. Please contact the administrator." | ||
| Line 14: | Line 13: | ||
|- | |- | ||
! '''Possible Cause''' | ! '''Possible Cause''' | ||
| - | | Node1 and node2 Config datastores are not in sync | + | | Node1 and node2 Config datastores are not in sync. |
|- | |- | ||
! '''Recommended Action''' | ! '''Recommended Action''' | ||
| - | | Deactivate and Activate Config and Historical datastores on node2 from the appadmin control center->component activation page. | + | | Deactivate and Activate Config and Historical datastores on node2 from the appadmin control center->component activation page. |
|- | |- | ||
! '''Release''' | ! '''Release''' | ||
Latest revision as of 06:52, 4 May 2010
Not able to view/edit rmcm configurations from node2 appadmin in an HA setup
| Problem Summary | Node1 Appadmin displays the entire rmcm configuration correctly. However from node2 appadmin experiencing database inconsistency and unable to access/view the configurations under RMCM subsystem. Displaying the following message in the Appadmin.
"There was an error reading/updating the database. Please contact the administrator." |
|---|---|
| Error Message | "There was an error reading/updating the database. Please contact the administrator." |
| Possible Cause | Node1 and node2 Config datastores are not in sync. |
| Recommended Action | Deactivate and Activate Config and Historical datastores on node2 from the appadmin control center->component activation page. |
| Release | Release 7.0, Release 5.0 |
| Associated CDETS # | None |
