Skip to main content
Skip table of contents

Fixed issues (IBM Db2)

Release 4.8.0

Key

Summary

DB2-2402 

Db2 dSources following end of logs from before shouldn't be forced to resync after 4.6.0.

Release 4.7.4

Key

Summary

DB2-2375

Unable to use a valid Db2 database name when linking dSource.

DB2-2379

DB2 VDB provision/refresh from parent VDB results in failed relocate database attempt

Release 4.7.3

This release version has been removed. Please install or upgrade to a later version.

Release 4.7.2

Key

Summary

DB2-1606

Custom mount base fails with 'attribute error' during VDB enable.

DB2-2349

Update Db Storage paths  if old path structure, <mount_path>/<db_path> is found

Release 4.7.1

Key

Summary

DB2-2305

Custom mount base fails with 'attribute error' during VDB enable.

Release 4.7.0

There are no fixed issues in this release.

Release 4.6.1

Key

Summary

DB2-2190

Instead of failing the process, the housekeeping job should issue a warning.

Release 4.6.0

Key

Summary

DB2-2068

"VDB Name" requested to be entered twice during provisioning.

DB2-2117

Update LOGARCHCOMPR1 and LOARCHCOMPR2 to off during dSource creation

DB2-2155

db2greg should run from the latest installation of db2 on staging/target for environment discovery

DB2-2156

All DB2 dSources with Backup+logs should only rollforward to PIT

DB2-2178

MRT query fails with SQL1262N on staging hosts that are ahead of UTC timezone

DB2-2179

If DB2LOADREC registry value already set raise error.

Release 4.5.1

Key

Summary

DB2-2112

DB2 pre-snapshot phase runs rollforward to EOL on RF pit configuration

Release 4.5.0

There are no fixed issues in this release.

Release 4.4.2

Ticket number

Summary

DB2-2004

Some DB2 VDB deletes/refresh when canceled leave database running on instance in strange state

Release 4.4.1

Ticket number

Summary

DB2-2044

Db2 plugin shouldn’t implement Source sizing for VDB datasets

DB2-2045

VDB provisioning fails with SQl5153N due to LOGSECOND value

DB2-2053

Provisioning VDB failed during db2relocatedb due to multiple storage group paths

Release 4.4.0

Ticket number

Summary

DB2-2033

Resync fails on staging hosts with fuser command

DB2-2041

HADR linking is failing for low privilege user environment

Release 4.3.2

Ticket number

Summary

DB2-1682

Db2 vSDK plugin should support all product editions

DB2-1971

Environment addition and other workflows fail when .profile is configured with banners

DB2-1992

Restore on dpf environment continues even when one or more nodes' restore fails in dSource creation

DB2-1997

Db2 staging push doesn't test for missing tablespaces/datapaths while running db2dart

Release 4.3.1

Ticket number

Summary

DB2-1973

Make sure the data paths are configured under "db_mount/DB_NAME" in staging push

Release 4.3.0

Ticket number

Summary

DB2-1952

remove_event_bin_files may fail due to regular expression mismatch for DIAGPATH value

Release 4.2.1

There are no fixed issues in this release.

Release 4.2.0

Ticket number

Summary

DB2-1901

VDB provision from dsource with rollforward to PIT is running rollforward to end of logs and stop instead of rollforward stop

DB2-1911

DB2 rollforward command failing with syntax error for dpf environments

DB2-1913

The rollforward command should work with timezone only when timestamp is provided.

DB2-1920

VDB provision fails with Failed to execute rollforward command on database BDN9NAJZ in case of dsource with backup and log ingestion.

Release 4.1.3

Ticket number

Summary

DB2-1812

CLI operations during snapsync may fail if commands return error messages in a different locale

DB2-1856

VDB provision fails with an issue during db2relocatedb

DB2-1875

VDB behavior when we provision them using the first snapshot vs the latter ones

DB2-1921

 Fix permissions for “/toolkit_dir/DB2” along with mnts/ and logs

DB2-1904

Staging push vSDK: snapsync operation on dSource fails with TypeError: unhashable type: ‘SnapshotDefinitionDataPaths’

Release 4.1.2

Ticket number

Summary

DB2-1826

Moved Staging Push redirect restore template out of the plugin and added contextual values to plugin logs

DB2-1796

Unable to get the complete content of redirect restore script in case the script size is more than 1MB

DB2-1824

DB2 VDB provisioning fails during relocateDB

Release 4.1.1

There are no fixed issues in this release.

Release 4.1.0

There are no fixed issues in this release.

Release 4.0.1

Key

Summary

DB2-1684

[Staging Push]Enable operation on dSource should generate the Restore and Rollforward template file if it is missing

Release 4.0.0

There are no fixed issues in this release.

Release 3.1.1

There are no fixed issues in this release.

Release 3.1.0

There are no fixed issues in this release.

Release 3.0.2

There are no fixed issues in this release.

Release 3.0.1

There are no fixed issues in this release.

Release 3.0.0

There are no fixed issues in this release.

JavaScript errors detected

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

If this problem persists, please contact our support.