Berkeley DB High Availability Works Error( New 4.6.18)

Question

Master:
ex_rep_mgr -M -p 100 -n 4 -h DIR1 -m localhost:6000
Client:
When client first run or clear up all file, press enter immediately after run ex_rep_mgr as client, client works error, like this:
(windows xp 32 bits)
ex_rep_mgr -C -p 50 -n 4 -h DIR2 -m localhost:6001 -o localhost:6000
D:\1234\db-4.6.18\db-4.6.18\build_windows\Debug>ex_rep_mgr -C -p 50 -n 4 -h DIR2 -m localhost:6001 -o localhost:6000
QUOTESERVER (read-only)> ---->>>>press enter immediately
ex_rep: DB->open: DB_LOCK_DEADLOCK: Locker killed to resolve a deadlock
ex_rep: Client failed: DB_LOCK_DEADLOCK: Locker killed to resolve a deadlock
D:\1234\db-4.6.18\db-4.6.18\build_windows\Debug>
D:\1234\db-4.6.18\db-4.6.18\build_windows\Debug>
D:\1234\db-4.6.18\db-4.6.18\build_windows\Debug>
vxworks as same , cann't works as client, client's database cann't open.
(vxworks , PPC 824X)

Answer 1

That's true. In a real application, you would of course want to handle deadlock errors. But this is just a simple toy example, just to show you how to get started using replication.
If you like, you can turn on the "-v" command line flag, to see a verbose listing of the messaging interaction that goes on behind the scenes. Wait until the start-up synchronization with the master is complete, and then press Enter to read the database.
Alan Bram
Oracle