Here are two possible solutions:
1) with the evil twin triggers on both replicas - sync when elements are
created... probably not what you want, but it is a solution.
2) (a better solution) in addition to the evil twin at each site (btw - if
you need the code it is here:
http://www.abs-consulting.com/abs_consulting_triggers.html) You could have
another trigger that after elements are created, the path name is appended
to a file called "fromsite<replicaname>" and then create a packet and sent
that to replicas... The packet should be of a dedicated class
crate a class called fromsite and then a special receipt handler that
expects and takes only this file and dumps it in a regular flat file
directory in a known location. Create preop trigger at each site so that
when elements are created the file is greped for a match first. Only
proceed id there is no match. To keep the file small and quick.. you can
set it to empty after receiving a proper sync from a replica.
These have worked for us in the past.
hope this helps
-Charles
Try ClearTrigger and ClearTrigger Lite at http://www.abs-consulting.com
A Better Solution, Inc.
----------------------------------------------------
Charles Clarke III ClearCase Consultant
A Better Solution, Inc. (770) 252-1500 x22 [phone]
1973 East Hwy. 34
Newnan, Ga. 30265 (770) 252-1501 [fax]
Email:
charles@abs-consulting.com
http://www.abs-consulting.com
At 05:47 PM 7/5/2001 +0530, Gopalakrishnan Krishnamoorthi wrote:
>Yes, trigger a small perl script will do for local replica. But as Axel said
>what can be for different replicas?
>-GK
>
>-----Original Message-----
>From: owner-cciug@rational.com [mailto:owner-cciug@rational.comOn
>Behalf Of Axel Mahler
>Sent: Thursday, July 05, 2001 5:29 PM
>To: Steve Kerxhalli; Gopalakrishnan Krishnamoorthi
>Cc: cciug@rational.com
>Subject: AW: [cciug] Way to avoid duplicate elements creation
>
>
>
>I think Gopal was referring to the evil-twin problem in *multisite
>settings*. If the same element is created simultaneously in different
>replicas, no evil-twin-prevention trigger can help you. I don't think there
>is a solution to this problem.
>
>- Axel.
>
> > -----Ursprüngliche Nachricht-----
> > Von: owner-cciug@rational.com [mailto:owner-cciug@rational.comIm
> > Auftrag von Steve Kerxhalli
> > Gesendet am: Donnerstag, 5. Juli 2001 13:18
> > An: Gopalakrishnan Krishnamoorthi
> > Cc: cciug@rational.com
> > Betreff: Re: [cciug] Way to avoid duplicate elements creation
> >
> >
> > Hello,
> >
> > Check the archives for past discussions on this topic
> > (a search for "evil twin" should be fruitful).
> > There are various trigger scripts out there which attempt
> > to deal with this problem. A word of caution though, some of
> > them are UNIX only and some do not work in snapshot views.
> >
> > Regards,
> >
> > Steve K.
> >
> > Gopalakrishnan Krishnamoorthi wrote:
> > >
> > > Hi All,
> > > In a distributed development often we face problems
> > because of two users at
> > > different sites or in the same site but on different branches creating
> > > elements with the same name under a directory. This ends up in
> > creating two
> > > different elements under the same directory. We feel the
> > problem only when a
> > > merge is done across these branches. That time may be too late for us to
> > > remove one of these elements, since both of them may have lots
> > of history
> > > left behind. Unfortunately Clearcase does not check up
> > (obviously it can not
> > > know what is created in another site without a sync update).
> > > Question is any way to avoid this (if not in different
> > site, at least in
> > > the same site on different branches).
> > > Thanks in advance,
> > > GK
> > >
> > ...
> > --
> > .......................................................
> > Steve Kerxhalli Stephan.Kerxhalli@kodak.com
> > Eastman Kodak Company voice: (716) 477-8420
> > Rochester, New York FAX: (716) 477-8788
> > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> >
> >
> >
> > http://clearcase.rational.com/cciug/mailing_list.html
> >
>
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>
>
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This archive was generated by hypermail 2b29 : Tue Jul 31 2001 - 22:03:51 EDT