On 24 Aug 2004 at 10:37, Helen Borrie wrote:

>Creating/changing metadata isn't the same as changing data. I'm sure
>IBReplicator does have *some* strategy for managing a two-phase commit
>for metadata commits, though I don't know what it is.

I'm sotty to disappoint you, but IBReplicator creates the triggers
and other system objects in source database in an ordinary (non 2PC)
transaction.
I can't imagine any special strategy to protect this process from
unexpected disconnects.

>that, as a minimum, it would be totally separated from the data
>replication and wouldn't be allowed while replication was going on...

Unfortunatelly, IBReplicator doesn't have any special protection in
this area.

>The right place to ask about this would be the IBReplicator list.

I'm not sure. Whatever IBReplicator do, database must stay
incorrupted. So, it is also DBMS problem, not just replicator's.

SY, Dimitry Sibiryakov.