Posts: 60
Registered: Jul 06, 2007 02:02:51 AM URGENT: Chmaster Issue in MultiSite.
Posted: Nov 30, 2010 06:28:30 AM Hello CC Friends,
Greetings to all! I am getting one Multisite Issue. Could anyone please resolve the same and do let me know.
One of our Client asked me to changed the mastership of our replica and send the data packets to reflect the changes. I did the same. But data packets are not going and giving the error.
I changed the Mastership & send the packets by using the below commands:
multitool chmaster -all -long replica@/vob
Changed mastership of all objects
multitool syncreplica -export -fship -maxsize 10m replica@/vob
multitool: Error: Could not determine synchronization mode for replica "xyz"
Generating synchronization packet /usr/atria/shipping/ms_ship/outgoing/a_b_c_30-Nov-10.15:27:01_8918
Shipping order "/usr/atria/shipping/ms_ship/outgoing/sync_abc_xyz_30-Nov-10.15:27:01_8918" generated.
Attempting to forward/deliver generated packets...
-- Forwarded/delivered packet /usr/atria/shipping/ms_ship/outgoing/abc_xyz_30-Nov-10.15:27:01_8918
If you find any solution, please revert back to this Query. Its urgent for me. I am googling in iNET...My Client is keep on pinging me :o(
Thanks,
SuKumar.
Posts: 88
Registered: Sep 14, 2006 05:05:14 AM Re: URGENT: Chmaster Issue in MultiSite.
Posted: Nov 30, 2010 07:00:26 AM
in response to: Mr.India's post I had a similar error a long time ago - but mine was with an import. We were running version 6 at the time and had applied a CC/MS patch which changed the structure of the regsistry files. Our patching strategy wasnt good (we ran a de-install and then a fresh install rather than just patching the existing install) and we ended up restoring the "pre patch" version of the registry files. So - we ended up with registry files whose structure wasnt compatible with our patch level. There was an IBM program available called rgy_upgrade which fixed it. I think you can tell whether you have this problem by running "ct lsvob". If the output marks the replicated VOBs with "(replicated)" then the registry is OK and its not this particular problem. Probably worth raising a support ticket on IBM to get help. Having said all that .. apart from that error it looks like hte syncro worked. It seems to have created and forwarded a packet.Posts: 426
Registered: Mar 15, 2005 04:40:07 AM Re: URGENT: Chmaster Issue in MultiSite.
Posted: Nov 30, 2010 07:13:49 AM
in response to: topman's post topman wrote:> It seems to have created and forwarded a packet.
Besides, now that all the local object masterships (including this of the the local replica) have been released, there is not much you can do...
I would recommend not to use this command (the -all flag): you want to retain the mastership of your own replica. Probably when/if the packets get delivered and imported, you could ask it back...
Marc
Posts: 60
Registered: Jul 06, 2007 02:02:51 AM Re: URGENT: Chmaster Issue in MultiSite.
Posted: Dec 01, 2010 02:16:59 AM
in response to: 314's post Thanks a lot Topman and Marc. I did cleartool lsvob, later unregistered and registered the VOB.
then executed the same commands. Packets reached to my client location.
I will look after rgy_update. I dont know about it.
Thanks,
SuKumar.
Posts: 426
Registered: Mar 15, 2005 04:40:07 AM Re: URGENT: Chmaster Issue in MultiSite.
Posted: Dec 01, 2010 06:12:26 AM
in response to: Mr.India's post Mr.India wrote:> I did cleartool lsvob, later unregistered and registered the VOB.
> then executed the same commands. Packets reached to my client location.
I am surprised.
This should affect neither the mastership nor the synchronisation.
In fact, a new chmaster -all should have produced no new event (unless somebody created new objects in the meanwhile), following which the syncreplica -export should have produced an empty packet, which it would have thrown away (unless there were other oplogs e.g. coming from other replicas).
You may look at the history of some objects (e.g. your own replica object, which I'd assume you ought to have mastered until you ran the command), as well as this of the replica you synched (either directly or indirectly...), and then the shipping logs on the different hosts if you can reach them.
Your own replica, you get with:
ct des -fmt "%[replica_name]p\n" vob:.Its recent history, looking for the chmaster event, you get with:
ct lshis -fmt "%d %o\n" -since yesterday replica:$(ct des -fmt "%[replica_name]p\n" vob:.)For the other replica, you may want to see the epochs at the different export times, and these are in the comment field... You more or less need to use perl to avoid a verbose output.
Marc
Use the search field to find all types of content in My developerWorks with that tag.
Use the slider bar to see more or fewer tags.
Popular tags shows the top tags for this particular type of content or application that you're viewing.
My tags shows your tags for this particular type of content or application that you're viewing.
Use the search field to find all types of content in My developerWorks with that tag. Use the slider bar to see more or fewer tags. Popular tags shows the top tags for this particular type of content or application that you're viewing. My tags shows your tags for this particular type of content or application that you're viewing.MoreLess 
No comments:
Post a Comment