Hello all, I have a few questions regarding MaxDB replication:
1) I am currently testing a simple MaxDB replication scenario. We have one Master unit and two clients units, all of which are in/out units. Synchronization works fine when empty client tables are populated with content from the master. However if a client goes down, I am having trouble getting the client to re-sync properly without clearing the database first. If any updates to existing records take place while the client is down, these changes are not propagated to the client. And any future tables to the table are not propagated. I have read in a MaxDB user report that MaxDB has problem when you try to synchronize a client table with data already exisiting in it. Must the client records be deleted in order to properly resynchronize or is there any way to resynchronize without clearing the database?
2) Is it possible to automate the startup procedure replication rather than use the SyncManGUI? I read on #maxdb IRC that I would have to write some Java code which calls the synchronization functions used by SyncManGUI. However there is no documentation of the Java synchronization classes and the source files are not included in the JAR files. Has there been any work done on automatically starting Master and Client replication units? Is there any documentation available that may assist in creating an automated startup procedure?
Thanks, Andres Rebolledo www.zebraprojects.com -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
