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

Delphix Support Policies specifically list Major and Minor release coverage. If a minor release is listed as covered, then all patch releases under that minor release are certified.

Supported Db2 Database Editions

  1. Enterprise Server Edition
  2. Advanced Enterprise Server Edition
  3. For the supported Db2 versions, Delphix supports the corresponding Db2 Developer edition with Db2 plugin support

Db2 supports only 64-bit OS.

Red Hat Enterprise Linux (RHEL) 

Support for RHEL 8.x requires installing the libncurses.5 library onto the host. Please reference KBA 5622 for actionable steps.

ESE and AESE Support

Supported DBMS Version

ESE 10.5AESE 10.5ESE 11.1AESE 11.1


Supported OS Version
RHEL 6.0Not SupportedNot SupportedNot SupportedNot Supported
RHEL 6.1Not SupportedNot SupportedNot SupportedNot Supported
RHEL 6.2Not SupportedNot SupportedNot SupportedNot Supported
RHEL 6.3Not SupportedNot SupportedNot SupportedNot Supported
RHEL 6.4SupportedSupportedNot SupportedNot Supported
RHEL 6.5SupportedSupportedNot SupportedNot Supported
RHEL 6.6SupportedSupportedNot SupportedNot Supported
RHEL 6.7SupportedSupportedSupportedSupported
RHEL 6.8SupportedSupportedSupportedSupported
RHEL 6.9SupportedSupportedSupportedSupported
RHEL 7.0SupportedSupportedSupportedSupported
RHEL 7.1SupportedSupportedSupportedSupported
RHEL 7.2SupportedSupportedSupportedSupported
RHEL 7.3SupportedSupportedSupportedSupported
RHEL 7.4SupportedSupportedSupportedSupported
RHEL 7.5SupportedSupportedSupportedSupported
RHEL 7.6SupportedSupportedSupportedSupported
RHEL 7.7Not SupportedNot SupportedNot SupportedSupported
RHEL 7.8Not SupportedNot SupportedNot SupportedSupported

Supported Db2 Fixpack with Delphix Engine

Delphix does not support different Db2 versions for interdependent datasets at the same time if they are in a parent-child relationship. VDB provision or refresh may fail in the case where the instance containing its parent dataset is on a different Db2 version. Before you upgrade the Db2 version of the instance containing the VDB dataset, ensure that the instance containing the parent dataset is also upgraded to the same version. Refer to the Db2 support matrix.

Db2 11.1 Fix Packs 

Db2 11. Fix Packs Non-HADR Linking

SourceStaging
11.1.1.111.1.2.211.1.3.3
11.1.1.1SupportedSupportedSupported
11.1.2.2Not SupportedSupportedSupported
11.1.3.3

Not Supported

SupportedSupported

Db2 11. Fix Packs HADR Linking

SourceStaging
11.1.1.111.1.2.211.1.3.3
11.1.1.1SupportedSupportedSupported
11.1.2.2Not SupportedSupportedSupported
11.1.3.3

Not Supported

SupportedSupported

Db2 11. Fix Packs Provisioning

StagingTarget
11.1.1.111.1.2.211.1.3.3
11.1.1.1SupportedSupportedSupported
11.1.2.2Not SupportedSupportedSupported
11.1.3.3

Not Supported

SupportedSupported

Db2 10.5 Fix Packs

Db2 10.5 Fix Packs - NON HADR linking

SourceStaging
10.5.0.110.5.0.210.5.0.310.5.0.410.5.0.510.5.0.610.5.0.710.5.0.810.5.0.9
10.5.0.1SupportedSupportedSupportedSupportedSupportedSupportedSupportedSupportedSupported
10.5.0.2SupportedSupportedSupportedSupportedSupportedSupportedSupportedSupportedSupported
10.5.0.3SupportedSupportedSupportedSupportedSupportedSupportedSupportedSupportedSupported
10.5.0.4SupportedSupportedSupportedSupportedSupportedSupportedSupportedSupportedSupported
10.5.0.5SupportedSupportedSupportedSupportedSupportedSupportedSupportedSupportedSupported
10.5.0.6SupportedSupportedSupportedSupportedSupportedSupportedSupportedSupportedSupported
10.5.0.7SupportedSupportedSupportedSupportedSupportedSupportedSupportedSupportedSupported
10.5.0.8SupportedSupportedSupportedSupportedSupportedSupportedSupportedSupportedSupported
10.5.0.9SupportedSupportedSupportedSupportedSupportedSupportedSupportedSupportedSupported

Db2 10.5 Fix Packs - HADR Linking

SourceStaging
10.5.0.110.5.0.210.5.0.310.5.0.410.5.0.510.5.0.610.5.0.710.5.0.810.5.0.9
10.5.0.1SupportedNot SupportedNot SupportedNot SupportedNot SupportedSupportedSupportedSupportedSupported
10.5.0.2Not SupportedSupportedNot SupportedNot SupportedSupportedSupportedSupportedSupportedSupported
10.5.0.3Not SupportedNot SupportedSupportedSupportedSupportedSupportedSupportedSupportedSupported
10.5.0.4Not SupportedNot SupportedNot SupportedSupportedNot SupportedSupportedSupportedSupportedSupported
10.5.0.5Not SupportedNot SupportedNot SupportedNot SupportedSupportedNot SupportedSupportedSupportedSupported
10.5.0.6Not SupportedNot SupportedNot SupportedNot SupportedNot SupportedSupportedSupportedSupportedSupported
10.5.0.7Not SupportedNot SupportedNot SupportedNot SupportedNot SupportedNot SupportedSupportedSupportedSupported
10.5.0.8Not SupportedNot SupportedNot SupportedNot SupportedNot SupportedNot SupportedNot SupportedSupportedSupported
10.5.0.9Not SupportedNot SupportedNot SupportedNot SupportedNot SupportedNot SupportedNot SupportedNot SupportedSupported

Db2 10.5 Fick Packs HADR-NON HADR Provision

StagingTarget
10.5.0.110.5.0.210.5.0.310.5.0.410.5.0.510.5.0.610.5.0.710.5.0.810.5.0.9
10.5.0.1SupportedSupportedSupportedSupportedSupportedSupportedSupportedSupportedSupported
10.5.0.2SupportedSupportedSupportedSupportedSupportedSupportedSupportedSupportedSupported
10.5.0.3SupportedSupportedSupportedSupportedSupportedSupportedSupportedSupportedSupported
10.5.0.4SupportedSupportedSupportedSupportedSupportedSupportedSupportedSupportedSupported
10.5.0.5SupportedSupportedSupportedSupportedSupportedSupportedSupportedSupportedSupported
10.5.0.6SupportedSupportedSupportedSupportedSupportedSupportedSupportedSupportedSupported
10.5.0.7SupportedSupportedSupportedSupportedSupportedSupportedSupportedSupportedSupported
10.5.0.8SupportedSupportedSupportedSupportedSupportedSupportedSupportedSupportedSupported
10.5.0.9SupportedSupportedSupportedSupportedSupportedSupportedSupportedSupportedSupported

Advanced Interactive eXecutive (AIX)


Supported DBMS Version

ESE 10.5AESE 10.5ESE 11.1AESE 11.1AESE 11.5


 Supported OS Version
AIX 6.1Not SupportedNot SupportedN/AN/AN/A
AIX 7.1SupportedSupportedSupported
Supported
Supported
AIX 7.2Supported
Supported
SupportedSupportedNot Supported

Plugin/Delphix Engine Compatibility

Plugins should be installed on compatible Delphix Engines per the table below:

Delphix EngineDb2_2.0.1Db2_2.1.0Db2_2.2.1Db2_2.3.0Db2_2.4.0Db2_2.4.1Db2_2.4.2Db2_2.5.1Db2_2.6.0Db2_2.6.1Db2_2.7.0Db2_2.7.1Db2_2.7.2Db2_2.7.3Db2_3.0.0Db2_3.0.1Db2_3.0.2
6.0.0.xNoYesYesYesYesYesYesYesYesYesYesYesYesYesYesYesYes
6.0.1.xNoYesYesYesYesYesYesYesYesYesYesYesYesYesYesYesYes
6.0.2.xNoYesYesYesYesYesYesYesYesYesYesYesYesYesYesYesYes
6.0.3.xNoYesYesYesYesYesYesYesYesYesYesYesYesYesYesYesYes

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.

Your Version

Recommended upgrade path to Db2 2.7.2

2.0.1

Upgrade to 2.1.0, and follow the paths below.

2.1.0

Upgrade to 2.2.1, and follow the paths below.

2.2.1

Upgrade to 2.3.0, and follow the paths below.

2.3.0

Upgrade to 2.4.0, and follow the paths below.

2.4.0

2.4.1

2.4.2

Upgrade to 2.5.1, and follow the paths below.

2.5.1Upgrade to 2.6.0, and follow the paths below.

2.6.0

2.6.1

Upgrade to 2.7.0, and follow the paths below.

2.7.0

2.7.1

Upgrade directly to the latest version

Known Issues 

Db2 plugin version 2.7.2 contains the following known issue:

Key

Summary

Workaround / Comments

DB2-619

VDB Migration feature is restricted

For Db2 datasets, we can only migrate VDB with the following pre-requisites:

  1. Instance name and installation path must be the same on the target host (where we are migrating the VDB).
  2. Toolkit directory on the old target host and new target host should be the same.
  3. OS version and Db2 release version should be the same on both the targets.