DB2 Version 9.7 for Linux, UNIX, and Windows

blocknonlogged - Block creation of tables that allow non-logged activity configuration parameter

This parameter specifies whether the database manager will allow tables to have the NOT LOGGED or NOT LOGGED INITIALLY attributes activated.

Configuration type: Database
Parameter type: Configurable Online
Default [range]: No [Yes, No ]

By default, blocknonlogged is set to NO: non-logged operations are permitted and you gain the performance benefits associated with reduced logging. There are some potential drawbacks associated with this configuration, however, particularly in high availability disaster recovery (HADR) database environments. DB2® HADR database environments use database logs to replicate data from the primary database to the standby database. Non-logged operations are allowed on the primary database, but are not replicated to the standby database. If you want non-logged operations to be reflected in the standby database, you must take extra steps to cause this to happen. For example, you can use online split mirrors or suspended I/O support to resynchronize the standby database after non-logged operations.

Usage notes

If blocknonlogged is set to YES, then the CREATE TABLE and ALTER TABLE statements fail if any of the following situations exist:
- The NOT LOGGED INITIALLY parameter is specified.
- The NOT LOGGED parameter is specified for a LOB column.
If blocknonlogged is set to YES, then the LOAD command fails if the following situations exist:
- You specify the NONRECOVERABLE option.
- You specify the COPY NO option.