Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gmmastros on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

DDR is down on replication

Status
Not open for further replies.

degurly

Programmer
Mar 1, 2002
8
0
0
US
When I do an onstat -g ddr it returns with the DDR--Down

Informix Dynamic Server Version 7.31.UD1 -- On-Line -- Up 00:35:08 -- 536784 Kbytes

DDR -- Down --

Also on the repl server the receive queue is extremely high (a bug with v7.3 as I re-call, so replication is fully established due to tables being out of sync) v9 should fix this.

But what causes the DDR-- Down? We have been on the phone with Informix, to no avail...

Thanks,
de
 
time difference,
short network problem,
too slow (by bandwidth or latency) network,
onconfig differences...
etc etc

(hic) 7.31 UC5 fixes ~ everything and is in marketing
 
Are you getting any errors, when your restart ERM?
Check your online.log, it may have something like
There is a table in syscdr.pendingstates which holds your pending replication requests.
Sometimes if you suspend your ERM server too long these fill up.
I have found that if your logical logs (which holds these transactions) are lost (because we backup to /dev/null) or the logs have wrapped around, then DDR is down because it cannot locate the transaction.
DDR has something to do with replay actions.
Check your log for details for the logical log which it cannot locate. You could backup your syscdr.replaytab and delete the entries which are bad.
It may be your ERM is not working now.
Some useful ERM commands
onstat -g nif - shows your ERm sends and receives, can use to check if you are sending and receiving your replication packets.
onstat -g cdr - overall picture
onstat -g grp A - shows your grouper, when run on your sending server, you can see it if the replicates are ok. If it shows "stopped" then you are not replicating.

If you see errors in the logs with "participants", it may be your pendingstates table has some bad records.

BTW, if your ERM is not replicating, Iguess you may have to do a full resync.
 
Now,I met the same problem.When I have started my informix replicat server for a long time,there is a DDR message appending the command "onstat -" and I can not communicate with my informix server.How can I resolve this problem?Please tell me,thanks!!!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top