14.7.2 Configuration Options

Table 14.6 IBMDB2I Storage Engine Features

NameCmd-LineOption FileSystem VarStatus VarVar ScopeDynamic
ibmdb2i_assume_exclusive_useYesYesYes GlobalYes
ibmdb2i_async_enabledYesYesYes BothYes
ibmdb2i_compat_opt_allow_zero_date_valsYesYesYes BothYes
ibmdb2i_compat_opt_blob_colsYesYesYes BothYes
ibmdb2i_compat_opt_time_as_durationYesYesYes BothYes
ibmdb2i_compat_opt_year_as_intYesYesYes BothYes
ibmdb2i_create_index_optionYesYesYes BothYes
ibmdb2i_lob_alloc_sizeYesYesYes BothYes
ibmdb2i_max_read_buffer_sizeYesYesYes BothYes
ibmdb2i_max_write_buffer_sizeYesYesYes BothYes
ibmdb2i_propogate_default_col_valsYesYesYes BothYes
ibmdb2i_rdb_nameYesYesYes GlobalNo
ibmdb2i_system_trace_levelYesYesYes GlobalYes
ibmdb2i_transaction_unsafeYesYesYes BothYes

The values specified for ibmdb2i_create_index_option, ibmdb2i_create_time_columns_as_tod, ibmdb2i_map_blob_to_varchar, ibmdb2i_compat_opt_allow_zero_date_vals, ibmdb2i_propagate_default_col_vals, and ibmdb2i_propagate_default_col_val will be applied whenever an IBMDB2I table is created. Tables are implicitly destroyed and re-created when an offline ALTER TABLE is performed on an IBMDB2I table. Therefore it is highly recommended that the values of these variables be consistent across the lifetime of a table to prevent an ALTER TABLE from running under a different set of options than were used to originally create the table. If this recommendation is not followed, the ALTER TABLE may fail upon encountering incompatible data when re-creating the table.