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
Parameter type
Configurable Online
Configurable by member in a Db2® pureScale® environment
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 perform any non-logged operations on the primary database, the standby database must be reinitialized. 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 CREATE TABLE and ALTER TABLE statements will fail if one of the following conditions is true:
    • The NOT LOGGED INITIALLY parameter is specified.
    • The NOT LOGGED parameter is specified for a LOB column.
    • A CLOB, DBCLOB, or BLOB column is defined as not logged.
  • 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.