The Log Reader is configured with the server-side configuration parameters in the LogReader section of the solid.ini configuration file.
About this task
Important: The LogReaderEnabled, MaxSpace, and MaxLogSize parameters are also used with Universal Cache and IBM InfoSphere CDC replication.
Procedure
▪Enable the Log Reader by setting LogReaderEnabled to yes.
This enables the Log Reader, allowing reads from SYS_LOG. The transaction logging mode is also more verbose.
▪As necessary for your environment, set the following parameters:
– Set MaxSpace value to define the maximum number of log records buffered into memory before throttling occurs.
– Set MaxLogSize value to define the maximum size of the log available for a catchup.
When the log reaches the defined size, old log data is deleted and catchup is not possible from the older LOGADDR log positions.
– Set MaxMemLogSize value to define the maximum size of the Log Reader logfile in memory, when logging is not enabled (Logging.LogEnabled=No).
Example
[LogReader] LogReaderEnabled=yes ;Default: no ; ;MaxLogSize=100000 ;default: 10240 (MB) ; The amount of the log files (in MB) that will be always maintained ; for the sake of a possible catchup. The size should be adjusted to ; the biggest size of a catchup that is reasonable. The space declared ; is always fully occupied. ; MaxSpace=500000 ;default:100000 ; The size of the in-memory log reader buffer used in throttling, ; in records. When the buffer fills up, the throttling (slowing down) ; is enacted. If the buffer is used, the size adds up to the : footprint of the solidDB® server process.