http://docwiki.cisco.com/w/index.php?title=Datastore_component_activations_fails_when_trying_to_activate_node2_components&feed=atom&action=history 2013-05-19T10:34:05Z Revision history for this page on the wiki MediaWiki 1.16.0 http://docwiki.cisco.com/w/index.php?title=Datastore_component_activations_fails_when_trying_to_activate_node2_components&diff=29704&oldid=prev 2010-05-04T07:50:06Z

<p><span class="autocomment">Datastore component activations fails when trying to activate node2 components</span></p> <table style="background-color: white; color:black;"> <col class='diff-marker' /> <col class='diff-content' /> <col class='diff-marker' /> <col class='diff-content' /> <tr valign='top'> <td colspan='2' style="background-color: white; color:black;">← Older revision</td> <td colspan='2' style="background-color: white; color:black;">Revision as of 07:50, 4 May 2010</td> </tr><tr><td colspan="2" class="diff-lineno">Line 17:</td> <td colspan="2" class="diff-lineno">Line 17:</td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>|-</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>|-</div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>! '''Recommended Action'''</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>! '''Recommended Action'''</div></td></tr> <tr><td class='diff-marker'>-</td><td style="background: #ffa; color:black; font-size: smaller;"><div>| <del class="diffchange diffchange-inline">: </del>If there is a size mismatch between the actual size and the CET-&gt;Cluster Dependent Config entry, correct the size same as in node1 using node2 CET and restart Node Manager in both the nodes. Do node2 component activation again.</div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>| If there is a size mismatch between the actual size and the CET-&gt;Cluster Dependent Config entry, correct the size same as in node1 using node2 CET and restart Node Manager in both the nodes. Do node2 component activation again.</div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>|-</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>|-</div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>! '''Release'''</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>! '''Release'''</div></td></tr> </table>

Jayark http://docwiki.cisco.com/w/index.php?title=Datastore_component_activations_fails_when_trying_to_activate_node2_components&diff=29703&oldid=prev 2010-05-04T07:49:31Z

<p>New page: == Datastore component activations fails when trying to activate node2 components == {| border=&quot;1&quot; |- ! &#39;&#39;&#39;Problem Summary&#39;&#39;&#39; | Datastore component activations fails when trying to activa...</p> <p><b>New page</b></p><div>== Datastore component activations fails when trying to activate node2 components ==<br /> <br /> {| border=&quot;1&quot;<br /> |-<br /> ! '''Problem Summary'''<br /> | Datastore component activations fails when trying to activate node2 components.<br /> <br /> |-<br /> ! '''Error Message'''<br /> | <br /> <br /> |-<br /> ! '''Possible Cause'''<br /> | This can be due to database size mismatch in both the nodes.<br /> Check the database size from SQL Enterprise Manager-&gt;Select the database, right click and select properties and find the size. Check the size from CET ClusterDependentConfig and the Serviceability tool. The size should be same in all the places. This size should be same in both the nodes as well.<br /> <br /> |-<br /> ! '''Recommended Action'''<br /> | : If there is a size mismatch between the actual size and the CET-&gt;Cluster Dependent Config entry, correct the size same as in node1 using node2 CET and restart Node Manager in both the nodes. Do node2 component activation again.<br /> |-<br /> ! '''Release'''<br /> | Release 7.0, Release 5.0<br /> |-<br /> ! '''Associated CDETS #'''<br /> | None'''<br /> |-<br /> |}<br /> <br /> [[Category:Unified CCX, Release 7.0]]</div>

Jayark