High availability, backup, logging, resiliency, and recovery enhancements
version 11.1 includes enhancements that help ensure that your data remains available.
| Enhancement | Description |
|---|---|
| Db2 backup compression and log archive compression support for Nest Accelerator | Db2 backup compression and log archive compression now support Nest Accelerator of POWER® 7+ and POWER 8 processors. This enhancement is done through the special hardware compression unit NX842 on POWER CPUs. For more information, see: Hardware accelerated backup and log file compression. |
| New options for the ADMIN_MOVE_TABLE | The ADMIN_MOVE_TABLE now includes two new options: REPORT and TERM. The REPORT option can be used to monitor the progress of table moves. The TERM option can be used to terminate a table move in progress. For more information, see: ../../com.ibm.db2.luw.sql.rtn.doc/doc/r0055069.html. |
| Fast pre-allocation for log file creation and resize | To enable fast pre-allocation for creating and resizing a log file, you can use the DB2_USE_FAST_LOG_PREALLOCATION registry variable to enable this feature. For more information, see: ../../com.ibm.db2.luw.admin.regvars.doc/doc/r0005665.html. |
| New option for db2relocatedb | The db2relocatedb includes a new option: -g. The -g option can be used to generate scripts that can be used as input for database relocation operations. For more information, see: ../../com.ibm.db2.luw.admin.cmd.doc/doc/r0004500.html. |
| New option for backup database | The backup database has a new option: NO TABLESPACE. A NO TABLESPACE backup does not contain tablespaces. For more information, see: ../../com.ibm.db2.luw.admin.cmd.doc/doc/r0001933.html. |
| No HADR reinitialization after an upgrade for specific Db2 users | The upgrade of a HADR pair from a supported release and fix pack will no longer need the re-initialization of the standby through the use of a backup image that is shipped from the primary after upgrade. Reinitialization of the standby is still an option if the user wishes, but is no longer the recommended option. The supported HADR upgrade procedure requires the primary and standby databases to both be, at a minimum, at 10.5fp7 level for single partition Enterprise Server Edition or refer to the FAQ technote "http://www-01.ibm.com/support/docview.wss?uid=swg21298716" for supported 10.5 Fix Pack levels for pureScale®. Any other prior level is not supported and attempts to use the documented procedure fail. For these prior level databases, the standby still require reinitialization by a backup image that is shipped from the primary after upgrade. |
| Db2 log records | To help support the ability to roll forward (replay) through a database upgrade, two, new propagatable log records have been introduced. The database migration begin log record is written to mark the start of database upgrade, while the database migration end log record is written to mark the successful completion of database upgrade. |
| INPLACE table reorganization that is supported for range partitioned tables | The manageability of large range partitioned tables has been improved. A single partition of a partitioned table can now be reorganized with the INPLACE option if the table has no nonpartitioned indexes. For more information, see: ../../com.ibm.db2.luw.admin.cmd.doc/doc/r0001966.html |