Re: [firebird-support] Replication SW experience

[Slavomir Skopalik skopa...@elektlabs.cz [firebird-support]]

Hi Helen,
sorry for question too specific to ibReplicator.

I still looking for replication SW, because all SW mentioned here 
(ibReplicator,  symmetricds, CopyCat) has some issues.
Or experience with writing it by self from someone who already did it.

Thank you for understanding.

Slavek

Ing. Slavomir Skopalik
Executive Head
Elekt Labs s.r.o.
Collection and evaluation of data from machines and laboratories
by means of system MASA (http://www.elektlabs.cz/m2demo)
-
Address:
Elekt Labs s.r.o.
Chaloupky 158
783 72 Velky Tynec
Czech Republic
---
Mobile: +420 724 207 851
icq:199 118 333
skype:skopaliks
e-mail:skopa...@elektlabs.cz
http://www.elektlabs.cz

On 28.11.2015 19:05, Helen Borrie hele...@iinet.net.au 
[firebird-support] wrote:
> Sunday, November 29, 2015, 2:08:01 AM, Slavomir Skopalik 
> skopa...@elektlabs.cz wrote:
>
>> Thank you,
>> I was try (IBP Replicator) and I found few problems.
> This list is for Firebird.  Questions about third-party applications
> are off-topic here.
>
> For help with IBP Replicator, please subscribe to the mailing list for
> that application:
>
> List-Subscribe: ,
>   
>
>
> Helen (Moderator)
>
>








++

Visit http://www.firebirdsql.org and click the Documentation item
on the main (top) menu.  Try FAQ and other links from the left-side menu there.

Also search the knowledgebases at http://www.ibphoenix.com/resources/documents/ 

++


Yahoo Groups Links

<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/firebird-support/

<*> Your email settings:
Individual Email | Traditional

<*> To change settings online go to:
http://groups.yahoo.com/group/firebird-support/join
(Yahoo! ID required)

<*> To change settings via email:
firebird-support-dig...@yahoogroups.com 
firebird-support-fullfeatu...@yahoogroups.com

<*> To unsubscribe from this group, send an email to:
firebird-support-unsubscr...@yahoogroups.com

<*> Your use of Yahoo Groups is subject to:
https://info.yahoo.com/legal/us/yahoo/utos/terms/

Re: [firebird-support] Replication SW experience

[Slavomir Skopalik skopa...@elektlabs.cz [firebird-support]]

Thank you,
I was try and I found few problems.

1. I failed to set up replication on Db Event (in manual is mentioned).
Any idea how to do with IBreplicator?

2. I failed to transfer all table operation.
Only last values are transfered.
This fail, if is circular link between records like
record A have FK to record B
record B have FK to record A
present is data.
Is it possible to setup ibReplicator to sync all changes, not only final 
view?

3. REPL users in triggers
AS
DECLARE VARIABLE C_OP CHAR(1) = '?';
BEGIN
C_OP = CASE WHEN (INSERTING) THEN 'I' WHEN (UPDATING) THEN 'U' WHEN 
(DELETING) THEN 'D' END;
IF (USER <> 'REPL') THEN BEGIN
   INSERT INTO REPL$LOG(REPLNO,SUBDBNO,RELATIONNO,REPTYPE,NEWKEY,OLDKEY,SEP)
   VALUES(1,2,1,:C_OP,NEW.ID,OLD.ID,'  ');
END
END
Is it possible to use context variables instead REAL user?
Like this example:
CREATE OR ALTER PROCEDURE GetUserID
  RETURNS( rid INTEGER ) AS
BEGIN
   rid=RDB$GET_CONTEXT('USER_TRANSACTION','REALUSERID');
   IF(rid IS NULL)THEN
 rid=RDB$GET_CONTEXT('USER_SESSION','ConnectedUser');
   IF(rid IS NULL)THEN
 EXECUTE PROCEDURE GetUserIDEx(USER) RETURNING_VALUES rid;
END

4. ReplManager.exe.manifest
I have to delete this file, it causes that I cannot start 
ReplManager.exe as normal user.

Slavek

Ing. Slavomir Skopalik
Executive Head
Elekt Labs s.r.o.
Collection and evaluation of data from machines and laboratories
by means of system MASA (http://www.elektlabs.cz/m2demo)
-
Address:
Elekt Labs s.r.o.
Chaloupky 158
783 72 Velky Tynec
Czech Republic
---
Mobile: +420 724 207 851
icq:199 118 333
skype:skopaliks
e-mail:skopa...@elektlabs.cz
http://www.elektlabs.cz

On 26.11.2015 12:22, Alexey Kovyazin a...@ib-aid.com [firebird-support] wrote:
> Hi,
>
> Try IBReplicator.
>
> Regards,
> Alexey Kovyazin
> IBSurgeon
>
>
>
>
>> Hi all,
>> we are preparing new project with bidirectional replication.
>>
>> Customer idea is to have master database in head quoter
>> and slave databases on production plant (to solve network performance
>> and availability issues).
>>
>> Witch replication SW you can recommend for this bidirectional 
>> replication?
>> What is typical issues and weakness of this SW.
>>
>> Thank you.
>>
>> Slavek
>>
>> -- 
>> Ing. Slavomir Skopalik
>> Executive Head
>> Elekt Labs s.r.o.
>> Collection and evaluation of data from machines and laboratories
>> by means of system MASA (http://www.elektlabs.cz/m2demo)
>> --
>> Address:
>> Elekt Labs s.r.o.
>> Chaloupky 158
>> 783 72 Velky Tynec
>> Czech Republic
>> --
>> Mobile: +420 724 207 851
>> icq:199 118 333
>> skype:skopaliks
>> e-mail:skopa...@elektlabs.cz
>> http://www.elektlabs.cz
>>
>>
>
>

Re: [firebird-support] Replication SW experience

[Helen Borrie hele...@iinet.net.au [firebird-support]]

Sunday, November 29, 2015, 2:08:01 AM, Slavomir Skopalik skopa...@elektlabs.cz 
wrote:

> Thank you,
> I was try (IBP Replicator) and I found few problems.

This list is for Firebird.  Questions about third-party applications
are off-topic here.

For help with IBP Replicator, please subscribe to the mailing list for
that application:

List-Subscribe: ,
 


Helen (Moderator)

Re: Re: [firebird-support] Replication SW experience

[Sudheer Palaparambil sudheer....@gmail.com [firebird-support]]

Hi,

Please have a look at SymmetricDS (http://www.symmetricds.org/). I have
been using it for the past 4 years with Firebird.

Thanks and regards.

Sudheer Palaparambil

On Thu, Nov 26, 2015 at 9:05 PM, liviuslivius liviusliv...@poczta.onet.pl
[firebird-support] <firebird-support@yahoogroups.com> wrote:

>
>
> hi,
>
> modification datetime is not enaugh to replication. think about
>
> 1. transaction started and modify data
> 2. synchronization started and fetch data from last modifird datetime
> 3. synchronization end
> 4. transaction commit data from point 1 and store datetime before synch
> started
> 5. synchronization start and omit modification from point 1 because date
> is older
>
> regards,
> Karol Bieniaszewski
>
>
>
> Pozdrawiam
>
>
>  Oryginalna wiadomość 
> Od: "Slavomir Skopalik skopa...@elektlabs.cz [firebird-support]" <
> firebird-support@yahoogroups.com>
> Data: 26.11.2015 12:46 (GMT+01:00)
> Do: firebird-support@yahoogroups.com
> Temat: Re: [firebird-support] Replication SW experience
>
>
>
> Hi Aldis,
> more info about situation.
>
> 1. Normal operation
> - Asynchronous replication will wait for DB Event and than
> immediately start transfer.
> All data changes will be logged by triggers into log table.
>
> 2. Disaster
> Local production will continue works because have production plan and
> records data into local DB.
> When connection will be back all data will be synchronized.
> There are no so much real possibilities to conflict.
>
> Each table has UTC time stamp of last modification. In most cases,
> latest wins.
> Rest of conflict we have to program manually.
>
> I have idea how to do it (it is nice work), but I don't want to invent
> "wheel".
>
> I'm looking on something like copycat, but web site is little bit
> confusing.
>
> Any experience?
>
> Slavek
>
> Ing. Slavomir Skopalik
> Executive Head
> Elekt Labs s.r.o.
> Collection and evaluation of data from machines and laboratories
> by means of system MASA (http://www.elektlabs.cz/m2demo)
> --
> Address:
> Elekt Labs s.r.o.
> Chaloupky 158
> 783 72 Velky Tynec
> Czech Republic
> --
> Mobile: +420 724 207 851
> icq:199 118 333
> skype:skopaliks
> e-mail:skopa...@elektlabs.cz
> http://www.elektlabs.cz
>
> On 26.11.2015 9:00, Alan J Davies alan.dav...@aldis-systems.co.uk
> [firebird-support] wrote:
> > Hi Slavek, there are a number of issues you need to resolve before
> > making a decision. If network performance is an issue then replication
> > is not the answer - unless you can send the changes back to head office
> > 'out of hours'. This means the different databases will be out of sync
> > for some time. Is this acceptable from your customer's point of view?
> > Are there different production plants making the same item? What happens
> > if plant 1 and plant 2 make the same item on the same day?
> >
> > I think you may have to generate your own version because replication is
> > not what you need (imho) but you could create a series of triggers and
> > tables to do what you want. e.g. if you have a table called PARTS,
> > create SYNC_PARTS and each time there is a change to PARTS you add a
> > record. You could then send your updates to HO via a scheduled update or
> > even within the same transaction if your network access allows for that.
> >
> > Alan J Davies
> > Aldis
> >
> >
> > On 25/11/2015 21:35, Slavomir Skopalik skopa...@elektlabs.cz
> > [firebird-support] wrote:
> >> Hi all,
> >> we are preparing new project with bidirectional replication.
> >>
> >> Customer idea is to have master database in head quoter
> >> and slave databases on production plant (to solve network performance
> >> and availability issues).
> >>
> >> Witch replication SW you can recommend for this bidirectional
> replication?
> >> What is typical issues and weakness of this SW.
> >>
> >> Thank you.
> >>
> >> Slavek
> >>
> >> --
> >> Ing. Slavomir Skopalik
> >> Executive Head
> >> Elekt Labs s.r.o.
> >> Collection and evaluation of data from machines and laboratories
> >> by means of system MASA (http://www.elektlabs.cz/m2demo)
> >> --
> >> Address:
> >> Elekt Labs s.r.o.
> >> Chaloupky 158
> >> 783 72 Velky Tynec
> >> Czech Republic
> >> --
> >> Mobile: +420 724 207 851
> >> icq:199 118 333
> >> skype:skopaliks
> >> e-mail:skopa...@elektlabs.cz
> >> http://www.elektlabs.cz
> >>
> >>
>
> 
>

Re: [firebird-support] Replication SW experience

[Alan J Davies alan.dav...@aldis-systems.co.uk [firebird-support]]

Hi Slavek, there are a number of issues you need to resolve before 
making a decision. If network performance is an issue then replication 
is not the answer - unless you can send the changes back to head office 
'out of hours'. This means the different databases will be out of sync 
for some time. Is this acceptable from your customer's point of view?
Are there different production plants making the same item? What happens 
if plant 1 and plant 2 make the same item on the same day?

I think you may have to generate your own version because replication is 
not what you need (imho) but you could create a series of triggers and 
tables to do what you want. e.g. if you have a table called PARTS, 
create SYNC_PARTS and each time there is a change to PARTS you add a 
record. You could then send your updates to HO via a scheduled update or 
even within the same transaction if your network access allows for that.

Alan J Davies
Aldis


On 25/11/2015 21:35, Slavomir Skopalik skopa...@elektlabs.cz 
[firebird-support] wrote:
> Hi all,
> we are preparing new project with bidirectional replication.
>
> Customer idea is to have master database in head quoter
> and slave databases on production plant (to solve network performance
> and availability issues).
>
> Witch replication SW you can recommend for this bidirectional replication?
> What is typical issues and weakness of this SW.
>
> Thank you.
>
> Slavek
>
> --
> Ing. Slavomir Skopalik
> Executive Head
> Elekt Labs s.r.o.
> Collection and evaluation of data from machines and laboratories
> by means of system MASA (http://www.elektlabs.cz/m2demo)
> --
> Address:
> Elekt Labs s.r.o.
> Chaloupky 158
> 783 72 Velky Tynec
> Czech Republic
> --
> Mobile: +420 724 207 851
> icq:199 118 333
> skype:skopaliks
> e-mail:skopa...@elektlabs.cz
> http://www.elektlabs.cz
>
> 

Re: [firebird-support] Replication SW experience

[Alexey Kovyazin a...@ib-aid.com [firebird-support]]

Hi,

Try IBReplicator.

Regards,
Alexey Kovyazin
IBSurgeon





Hi all,
we are preparing new project with bidirectional replication.

Customer idea is to have master database in head quoter
and slave databases on production plant (to solve network performance
and availability issues).

Witch replication SW you can recommend for this bidirectional replication?
What is typical issues and weakness of this SW.

Thank you.

Slavek

--
Ing. Slavomir Skopalik
Executive Head
Elekt Labs s.r.o.
Collection and evaluation of data from machines and laboratories
by means of system MASA (http://www.elektlabs.cz/m2demo)
--
Address:
Elekt Labs s.r.o.
Chaloupky 158
783 72 Velky Tynec
Czech Republic
--
Mobile: +420 724 207 851
icq:199 118 333
skype:skopaliks
e-mail:skopa...@elektlabs.cz
http://www.elektlabs.cz

ODP: Re: [firebird-support] Replication SW experience

[liviuslivius liviusliv...@poczta.onet.pl [firebird-support]]

hi,
modification datetime is not enaugh to replication. think about
1. transaction started and modify data2. synchronization started and fetch data 
from last modifird datetime3. synchronization end4. transaction commit data 
from point 1 and store datetime before synch started5. synchronization start 
and omit modification from point 1 because date is older
regards,Karol Bieniaszewski


Pozdrawiam

 Oryginalna wiadomość 
Od: "Slavomir Skopalik skopa...@elektlabs.cz [firebird-support]" 
<firebird-support@yahoogroups.com> 
Data: 26.11.2015  12:46  (GMT+01:00) 
Do: firebird-support@yahoogroups.com 
Temat: Re: [firebird-support] Replication SW experience 


 



  



  
  
  Hi Aldis,

more info about situation.



1. Normal operation

   - Asynchronous replication will wait for DB Event and than 

immediately start transfer.

   All data changes will be logged by triggers into log table.



2. Disaster

   Local production will continue works because have production plan and 

records data into local DB.

   When connection will be back all data will be synchronized.

   There are no so much real possibilities to conflict.



Each table has UTC time stamp of last modification. In most cases, 

latest wins.

Rest of conflict we have to program manually.



I have idea how to do it (it is nice work), but I don't want to invent 

"wheel".



I'm looking on something like copycat, but web site is little bit confusing.



Any experience?



Slavek



Ing. Slavomir Skopalik

Executive Head

Elekt Labs s.r.o.

Collection and evaluation of data from machines and laboratories

by means of system MASA (http://www.elektlabs.cz/m2demo)

--

Address:

Elekt Labs s.r.o.

Chaloupky 158

783 72 Velky Tynec

Czech Republic

--

Mobile: +420 724 207 851

icq:199 118 333

skype:skopaliks

e-mail:skopa...@elektlabs.cz

http://www.elektlabs.cz



On 26.11.2015 9:00, Alan J Davies alan.dav...@aldis-systems.co.uk 

[firebird-support] wrote:

> Hi Slavek, there are a number of issues you need to resolve before

> making a decision. If network performance is an issue then replication

> is not the answer - unless you can send the changes back to head office

> 'out of hours'. This means the different databases will be out of sync

> for some time. Is this acceptable from your customer's point of view?

> Are there different production plants making the same item? What happens

> if plant 1 and plant 2 make the same item on the same day?

>

> I think you may have to generate your own version because replication is

> not what you need (imho) but you could create a series of triggers and

> tables to do what you want. e.g. if you have a table called PARTS,

> create SYNC_PARTS and each time there is a change to PARTS you add a

> record. You could then send your updates to HO via a scheduled update or

> even within the same transaction if your network access allows for that.

>

> Alan J Davies

> Aldis

>

>

> On 25/11/2015 21:35, Slavomir Skopalik skopa...@elektlabs.cz

> [firebird-support] wrote:

>> Hi all,

>> we are preparing new project with bidirectional replication.

>>

>> Customer idea is to have master database in head quoter

>> and slave databases on production plant (to solve network performance

>> and availability issues).

>>

>> Witch replication SW you can recommend for this bidirectional replication?

>> What is typical issues and weakness of this SW.

>>

>> Thank you.

>>

>> Slavek

>>

>> --

>> Ing. Slavomir Skopalik

>> Executive Head

>> Elekt Labs s.r.o.

>> Collection and evaluation of data from machines and laboratories

>> by means of system MASA (http://www.elektlabs.cz/m2demo)

>> --

>> Address:

>> Elekt Labs s.r.o.

>> Chaloupky 158

>> 783 72 Velky Tynec

>> Czech Republic

>> --

>> Mobile: +420 724 207 851

>> icq:199 118 333

>> skype:skopaliks

>> e-mail:skopa...@elektlabs.cz

>> http://www.elektlabs.cz

>>

>>






 

Re: ODP: Re: [firebird-support] Replication SW experience

[Slavomir Skopalik skopa...@elektlabs.cz [firebird-support]]

I know,
what is better?

It is same in normal client server.
Two client start editing same record. Who will win?

In paranoia system, you will use dummy update before edit starts.
But in real, mainly web, system?

Slavek

Ing. Slavomir Skopalik
Executive Head
Elekt Labs s.r.o.
Collection and evaluation of data from machines and laboratories
by means of system MASA (http://www.elektlabs.cz/m2demo)
-
Address:
Elekt Labs s.r.o.
Chaloupky 158
783 72 Velky Tynec
Czech Republic
---
Mobile: +420 724 207 851
icq:199 118 333
skype:skopaliks
e-mail:skopa...@elektlabs.cz
http://www.elektlabs.cz

On 26.11.2015 16:35, liviuslivius liviusliv...@poczta.onet.pl 
[firebird-support] wrote:
>  
> hi,
> modification datetime is not enaugh to replication. think about
> 1. transaction started and modify data2. synchronization started and fetch 
> data from last modifird datetime3. synchronization end4. transaction commit 
> data from point 1 and store datetime before synch started5. synchronization 
> start and omit modification from point 1 because date is older
> regards,Karol Bieniaszewski
>
>
> Pozdrawiam
>
>  Oryginalna wiadomość 
> Od: "Slavomir Skopalik skopa...@elektlabs.cz [firebird-support]" 
> <firebird-support@yahoogroups.com>
> Data: 26.11.2015  12:46  (GMT+01:00)
> Do: firebird-support@yahoogroups.com
> Temat: Re: [firebird-support] Replication SW experience
>
>
>   
>
>
>
>
>
>
>  
>
>
>Hi Aldis,
>
> more info about situation.
>
>
>
> 1. Normal operation
>
> - Asynchronous replication will wait for DB Event and than
>
> immediately start transfer.
>
> All data changes will be logged by triggers into log table.
>
>
>
> 2. Disaster
>
> Local production will continue works because have production plan and
>
> records data into local DB.
>
> When connection will be back all data will be synchronized.
>
> There are no so much real possibilities to conflict.
>
>
>
> Each table has UTC time stamp of last modification. In most cases,
>
> latest wins.
>
> Rest of conflict we have to program manually.
>
>
>
> I have idea how to do it (it is nice work), but I don't want to invent
>
> "wheel".
>
>
>
> I'm looking on something like copycat, but web site is little bit confusing.
>
>
>
> Any experience?
>
>
>
> Slavek
>
>
>
> Ing. Slavomir Skopalik
>
> Executive Head
>
> Elekt Labs s.r.o.
>
> Collection and evaluation of data from machines and laboratories
>
> by means of system MASA (http://www.elektlabs.cz/m2demo)
>
> --
>
> Address:
>
> Elekt Labs s.r.o.
>
> Chaloupky 158
>
> 783 72 Velky Tynec
>
> Czech Republic
>
> --
>
> Mobile: +420 724 207 851
>
> icq:199 118 333
>
> skype:skopaliks
>
> e-mail:skopa...@elektlabs.cz
>
> http://www.elektlabs.cz
>
>
>
> On 26.11.2015 9:00, Alan J Davies alan.dav...@aldis-systems.co.uk
>
> [firebird-support] wrote:
>
>> Hi Slavek, there are a number of issues you need to resolve before
>> making a decision. If network performance is an issue then replication
>> is not the answer - unless you can send the changes back to head office
>> 'out of hours'. This means the different databases will be out of sync
>> for some time. Is this acceptable from your customer's point of view?
>> Are there different production plants making the same item? What happens
>> if plant 1 and plant 2 make the same item on the same day?
>> I think you may have to generate your own version because replication is
>> not what you need (imho) but you could create a series of triggers and
>> tables to do what you want. e.g. if you have a table called PARTS,
>> create SYNC_PARTS and each time there is a change to PARTS you add a
>> record. You could then send your updates to HO via a scheduled update or
>> even within the same transaction if your network access allows for that.
>> Alan J Davies
>> Aldis
>> On 25/11/2015 21:35, Slavomir Skopalik skopa...@elektlabs.cz
>> [firebird-support] wrote:
>>> Hi all,
>>> we are preparing new project with bidirectional replication.
>>> Customer idea is to have master database in head quoter
>>> and slave databases on production plant (to solve network performance
>>> and availability issues).
>>> Witch replication SW you can recommend fo

[firebird-support] Replication SW experience

[Slavomir Skopalik skopa...@elektlabs.cz [firebird-support]]

Hi all,
we are preparing new project with bidirectional replication.

Customer idea is to have master database in head quoter
and slave databases on production plant (to solve network performance 
and availability issues).

Witch replication SW you can recommend for this bidirectional replication?
What is typical issues and weakness of this SW.

Thank you.

Slavek

-- 
Ing. Slavomir Skopalik
Executive Head
Elekt Labs s.r.o.
Collection and evaluation of data from machines and laboratories
by means of system MASA (http://www.elektlabs.cz/m2demo)
-
Address:
Elekt Labs s.r.o.
Chaloupky 158
783 72 Velky Tynec
Czech Republic
---
Mobile: +420 724 207 851
icq:199 118 333
skype:skopaliks
e-mail:skopa...@elektlabs.cz
http://www.elektlabs.cz