ER - Log space too small ?
Good morning/evening, We use ER to replicate one primary server on two secondary servers. Primary IDS 9.40.UC2 Secondary IDS 9.40.UC2 and IDS 9.30.FC3 On the primary server, we observe the following message in online.log : "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." We have 1 Go of logical log space (500 x 2Mo files), and we use about 80 files in one normal activity day. One peak activity day use about 300 files. We replicate whole databases, so that all transactions on the primary server are replicated on the secondary servers. Do you know how to avoid the warning message ? We have doubled the number of logical log files, passing from 250 to 500, but the warning remains. Thank you, Philippe
The message is displayed based on an internal analysis of log consumption and replay position advancement. I would guess that you have some periodic large consumption of log usage. M.P. "Ph. Chantry" <nospam@nomail.com> wrote in message news:btc43g$fsq$1@news-reader5.wanadoo.fr... > Good morning/evening, > > We use ER to replicate one primary server on two secondary servers. > Primary IDS 9.40.UC2 > Secondary IDS 9.40.UC2 and IDS 9.30.FC3 > > > On the primary server, we observe the following message in online.log : > > "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." > > > We have 1 Go of logical log space (500 x 2Mo files), and we use about 80 > files in one normal activity day. One peak activity day use about 300 files. > We replicate whole databases, so that all transactions on the primary server > are replicated on the secondary servers. > > Do you know how to avoid the warning message ? We have doubled the number of > logical log files, passing from 250 to 500, but the warning remains. > > Thank you, > Philippe > >
"Madison Pruet" <mpruet@comcast.net> a 'crit dans le message de news:EwgKb.750591$Tr4.2076788@attbi_s03... > The message is displayed based on an internal analysis of log consumption > and replay position advancement. I would guess that you have some periodic > large consumption of log usage. Indeed we observe some peaks of activity in one day, but the warning does not occur every time. For example: - sunday : 28 logical log files used in 24 hours, with 13 logical log files used between 23:20 and 23:23 -> warning occurs at 23:23:28 - monday : 53 logical log files used in 24 hours, with 14 logical log files used between 23:20 and 23:23, and no warning occurs monday. The rule that IDS uses to display (or not) the warning seems to be very hard to understand. I guess that we may ignore the warning, no ? If not, what are the parameters to tune to avoid it ? Thank you, Philippe