CDR_LOG_LAG_ACTION shutdown issues
Posted in 2013
Hello, I have an Enterprise Replication setup in a lab environment, and I am specifically testing to see if setting CDR_LOG_LAG_ACTION to shutdown will turn off replication when the replay position is in danger of being overrun. I have three 256MB logical log files, and I pulled the network connection to the backup server in order to test this. I am using the OpenAdmin Tool to monitor the progress. I verified that the OAT Configuration tab has CDR_LOG_LAG_ACTION set to shutdown. I observed the Proximity to DDRBLOCK go from about 57,000 to -21,000. cdr list server still shows the primary to be in an Active state, and the OAT Proximity to DDR Block is continually decreasing to a negative value then resetting to a large positive value. I would have thought that cdr list server would have given me an Enterprise Replication not active error. When can I expect ER to shut down? Here are the particulars: IBM Informix Dynamic Server Version 11.70.FC5GE Tail of online log: 13:59:18 CDR Spool transaction queue completed 14:07:00 CDR Spool transaction queue completed 14:10:04 CDR connection to server lost, id 22, name <testbk_server> Reason: ASF connect attempt failed 14:10:31 Warning - The log space appears to be configured too small for use with Enterprise Replication (ER). ER may require additional logical logs to avoid a DDRBLOCK state and/or replay position log wrap. It is recommended that the logical log configuration be expanded. 14:10:32 Logical Log 195 Complete, timestamp: 0xbd1029b. 14:10:32 Process exited with return code 1: /bin/sh /bin/sh -c /informix/11.70/etc/alarms.sh 2 23 "Logical Log 195 Complete, timestamp: 0xbd1029b." "Logical Log 195 Complete, timestamp: 0xbd1029b." "" 23001 14:10:48 CDR Spool transaction queue completed 14:28:14 Checkpoint Completed: duration was 5 seconds. 14:28:14 Tue Oct 8 - loguniq 196, logpos 0xb69b118, timestamp: 0xbda6380 Interval: 3450 14:28:14 Maximum server connections 128 14:28:14 Checkpoint Statistics - Avg. Txn Block Time 0.013, # Txns blocked 10, Plog used 206859, Llog used 138662 Capture Log Position: 196:335163392 Capture Log Position: 196:335160568 Replay Log Position: 196:2908200 Last Data ACKed: 193:183484832 I also observed the Proximity to DDRBLOCK value go from -71720 to 51274 in 30 seconds, and at the same time, the Proximity to Log Wrap went from 55257 to 178251. These were both steadily decreasing over a period of 30 minutes or so. Thanks in advance. Jeff