Skip to main content
Skip table of contents

Managing IBM Db2 log rotation and log level

Setting the log level (level)

Delphix users can set the logging level of the connector-generated logs by setting the parameter level under the plugin_logging_parameters header. Higher logging levels will help to expedite debugging issues. There are two levels of logging which are: Info and Debug. The configured logging level will apply to all the objects (both dSources and VDBs) present on a staging/target host. For example; if we have 4 dSources on a host associated with a Delphix Engine then the log level will apply to all the dSources.

Log level description:

  • level=INFO: This level will print only informational logs. This is the default log level.

  • level=DEBUG: This level will print informational logs and debug statements.

Setting maximum size (logFileSize)

Delphix users can set the maximum size of the active log file by defining the value of the logFileSize parameter under the plugin_logging_parameters header of the db2_plugin.conf file. Once this maximum size limit is reached, the connector will rotate the log as per the retention property described below. This parameter only takes in a positive integer value. The minimum value of this parameter is 1 MB and the maximum value is 10 MB. The default value is 1 MB.

Setting the number of log files to retention (retention)

Delphix users can set a retention level for connector-generated logs for each dataset (<Db name>.diag.log) using the parameter retention under the plugin_logging_parameters header. As per this parameter, the log files are moved (archived), renamed, or deleted once they reach the value set in the logFileSize parameter. New incoming log data is directed into a new fresh file (at the same location).

By default, the value for this parameter will be set to a minimum value of 2. The user can change this value and set its value within the range 2 and 50. For example; if retention is set to 4, the connector will have the following log files: <DB Name>.diag.log, <DB Name>.diag.log.1, <DB Name>.diag.log.2, <DB Name>.diag.log.3, <DB Name>.diag.log.4. 

  • File <DB Name>.diag.log is the active log file

  • File <DB Name>.diag.log.1 is the most recent archive log file

  • File <DB Name>.diag.log.4 is the oldest one

For known issues, refer to the Known issues section from the release notes.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.