Simple logical log question

Hi everyone. With IDS 9.4 database does the following mean that one should add more logical logs, or perhaps make some onconfig change? Is it serious? Thanks...... 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.

On 10/06/2008, WILL LANDSTROM <willlandstrom@yahoo.com> wrote: > Hi everyone. With IDS 9.4 database does the following mean that one should add > more logical logs, or perhaps make some onconfig change? Is it serious? > > Thanks...... > 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. > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > Will It really depends on the amount of work being done on the servers and the speed with which this is replicated around the replicants. Are you seeing Replay and Snoopy dropping significantly behind Current? The recommendations I tend to adhere to is for each log to be able to hold 45-60 minutes of transactions in normal work environment, and enough logs to hold 24 hours of transactions in total. This may need to be increased if you are using timed transfer of transactions rather than continuous update. Keith

Hi, well, when using ER I would probably heed the advice and add more logical logs, possibly with bigger size. I would do this using the "onparams" utility, rather than changing the onconfig file. [ ER uses logical log records to replicate data changes to other IDS instances. If one replicate target instance falls behind with applying log records, then old log records cannot be overwritten (even though the log files were backed up and there is no long transaction). With that the system may get blocked (until the the replication target instance has caught up). With a bigger log space you can avoid the block situation (hoping that the other instance can catch up before log space is depleted). At least I think that is the background of this warning. Madison Pruet could explain it more correctly to you ... :) ] If you are not using ER, then you can most probably ignore the warning. Regards, Martin -- Martin Fuerderer IBM Informix Development Munich, Germany Information Management IBM Deutschland Entwicklung GmbH Chairman of the Supervisory Board: Martin Jetter Board of Management: Herbert Kircher Corporate Seat: Boeblingen, Germany Reg.-Gericht: Amtsgericht Stuttgart, HRB 243294 "WILL LANDSTROM" <willlandstrom@yahoo.com> Sent by: ids-bounces@iiug.org 10.06.2008 01:31 Please respond to ids@iiug.org To ids@iiug.org cc Subject Simple logical log question [12352] Hi everyone. With IDS 9.4 database does the following mean that one should add more logical logs, or perhaps make some onconfig change? Is it serious? Thanks...... 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. ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.

We display this message when we 'sense' a risk of a log wrap. We calcu= late the log consumption over a period of time and compare that against the processing of replicated transactions during that same time period. I'd suggest activating dynamic logs and then setting CDR_MAX_DYNAMIC_LO= GS. By doing that, we will allocate an additional log file rather than go i= nto a DDRBLOCK state - and thus will avoid a log wrap. If that is done, th= en the message can be ignored. M.P. ------------------------------------- Madison Pruet, STSM IDS Replication Architect = "Martin = Fuerderer" = <MARTINFU@de.ibm. = To com> ids@iiug.org = Sent by: = cc ids-bounces@iiug. = org Subj= ect Re: Simple logical log question = [12355] = 06/10/2008 05:59 = AM = = = Please respond to = ids@iiug.org = = = Hi, well, when using ER I would probably heed the advice and add more logical logs, possibly with bigger size. I would do this using the "onparams" utility, rather than changing the onconfig file. [ ER uses logical log records to replicate data changes to other IDS instances. If one replicate target instance falls behind with applying log records, then old log records cannot be overwritten (even though the log files were backed up and there is no long transaction). With that the system may get blocked (until the the replication target instance has caught up). With a bigger log space you can avoid the block situation (hoping that the other instance can catch up before log space is depleted). At least I think that is the background of this warning. Madison Pruet could explain it more correctly to you ... :) ] If you are not using ER, then you can most probably ignore the warning. Regards, Martin -- Martin Fuerderer IBM Informix Development Munich, Germany Information Management IBM Deutschland Entwicklung GmbH Chairman of the Supervisory Board: Martin Jetter Board of Management: Herbert Kircher Corporate Seat: Boeblingen, Germany Reg.-Gericht: Amtsgericht Stuttgart, HRB 243294 "WILL LANDSTROM" <willlandstrom@yahoo.com> Sent by: ids-bounces@iiug.org 10.06.2008 01:31 Please respond to ids@iiug.org To ids@iiug.org cc Subject Simple logical log question [12352] Hi everyone. With IDS 9.4 database does the following mean that one sho= uld add more logical logs, or perhaps make some onconfig change? Is it serious?= Thanks...... 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. ***********************************************************************= ******** Forum Note: Use "Reply" to post a response in the discussion forum. ***********************************************************************= ******** Forum Note: Use "Reply" to post a response in the discussion forum. =

Madison and all. Thank you for the responses. As it turns out this database is configured to use ER so changing the on onconfig CDR_MAX_DYNAMIC_LO= GS parameter sounds promising. I appreciate all of your information.