New Features

The Db2 Plugin version 2.7.2 introduces major changes that will improve customer's experience and expand the functionality.

Enhanced logging for DB2 Plugin

This feature adds three options to provide enhanced logging:

1. To set debug log levels
2. To set log retention levels
3. To set trace size limit

Each host (added as an environment to DE) will have its own property file <Toolkit directory>/DB2/plugin-logging.properties. Delphix users can modify the parameters within this property file to configure the logging mechanism.

Setting debug log levels

Delphix users can set log levels for plugin generated logs by setting the parameter level. Higher logging levels will help to expedite debugging issues. There are three levels of logging which are: Level 1 (info), Level 2 (debug) and Level 3 (trace). All the objects (both dSources and VDBs) present on a staging/target host will refer to a single property file. For example; if we have 4 dSources on a host associated with a Delphix Engine then the log level applies to all the dSources.

Log level description:

• level=1: This level will print only informational logs.
• level=2: This level will print informational logs and debug statements. This is the default log level.
• level=3: Besides informational and debug logs, this level will enable the traces. 

Setting log retention levels

Delphix users can set a retention level for diag logs (<Db name>.diag.log) using parameter retention in the file. As per this parameter, the log files are moved (archived), renamed or deleted once they are too old or too big. New incoming log data is directed into a new fresh file (at the same location).

By default, this value 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 plugin 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

Setting trace size limit

In case trace level logging is enabled, users can set the size of the trace folder using parameter traceFolderLimit. By default, the value of this parameter will be 10, which signifies that the size limit for this folder will be 10 MB. This parameter is configurable and the user can set its value to any positive integer. The traces are stored within a separate folder for traces created under directory <Toolkit directory>/DB2/logs/<User>/. The filename format for traces would be <DB Name>.<sciprt name>.trace.<epoch time>.  

If the file is accidentally removed from the location, the plugin will generate the property file <Toolkit directory>/DB2/plugin-logging.properties with default values at runtime. For example, when the user will upload the plugin to DE, the first call to log function will check for the existence of <Toolkit directory>/DB2/plugin-logging.properties. If the plugin does not find this property file, it’ll create a property file with the content shown below.  The logs will start generating per the level defined inside the file. Below is the sample <Toolkit directory>/DB2/plugin-logging.properties file:

# This flag will set the debug level of logging. There are three levels:

# 1: Logging will be in info mode.

# 2: Logging will be in Debug mode.

# 3: Traces will be enabled along with debug level logging.

# The default value is 2.

# level=<positive integer>

level=2

# Whenever the size of <DB Name>.diag.log file exceeds 1MB the plugin will rename the active log file to  <DB Name>.diag.log.<number> and a new log file with name <DB Name>.diag.log will be generated.

# For example, if LogRetention is set to 4, the plugin 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.4 will be the oldest one.

# File <DB Name>.diag.log.1 will be the most recent archive log file.

# File <DB Name>.diag.log will be the active log file.

# For example, if LogRetention is set to 4, the plugin 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.

# The default value for retention flag is 2, minimum value is 2 and maximum value is 50.

# retention=<positive integer>

retention=2

# The value for this property is configurable and must be a positive integer.

# The default value is 10.

# traceFolderLimit=<positive number>

traceFolderLimit=10

Support for named pipe type DB2 backup

Previously, the Db2 plugin was able to ingest the file type Db2 backups. Now users can also provide Db2 backups of type named-pipe. Db2 plugin will check the type (type will be either named-pipe or a file) of backup and will use the restore syntax accordingly.

Migration and Compatibility

Supported DBMS Versions

• Db2 Enterprise Server Edition 10.5

• Db2 Advanced Enterprise Server Edition 10.5

• Db2 Enterprise Server Edition 11.1

• Db2 Advanced Enterprise Server Edition 11.1

• Db2 Developer Edition 11.1 (on RHEL 6.7)

Supported Operating Systems

Plugin Upgrade Path

Use the table below to determine the most efficient upgrade path from your current version to the latest version of the Db2 Plugin.

Known Issues 

Db2 plugin version 2.7.2 contains the following known issue: