ULT4DB2

In Focus

[su_spoiler title=”Can ULT4DB2 handle the reordered row format of Db2 V9?” icon=”arrow-circle-1″]Yes.[/su_spoiler]

[su_spoiler title=”Can ULT4DB2 monitor changes in real time?” icon=”arrow-circle-1″]ULT4DB2 does not run continuously, but when executing it in short intervals it is possible to achieve near real time monitoring.[/su_spoiler]

[su_spoiler title=”Can ULT4DB2 work with compressed table spaces?” icon=”arrow-circle-1″]Yes. ULT4DB2 fetches the compression dictionaries from the page sets when the ULT4DB2L2SQL program processes the minilog. It is recommended to use the option KEEPDICTIONARY when reorganizing a table space in order to enable processing of log records that were created both before and after the reorganization.[/su_spoiler]

[su_spoiler title=”Can ULT4DB2 work with LOB or XML table spaces?” icon=”arrow-circle-1″]No. Tables that contain BLOB, CLOB, DBCLOB or XML columns can be processed by ULT4DB2, but only non-LOB columns will be included in the output.[/su_spoiler]

[su_spoiler title=”Can ULT4DB2 work without DATA CAPTURE CHANGES?” icon=”arrow-circle-1″]Yes, ULT4DB2 can work with and without DATA CAPTURE CHANGES. Nevertheless, activating DATA CAPTURE CHANGES improves performance.[/su_spoiler]

[su_spoiler title=”How does ULT4DB2 handle changes that were made by triggers?” icon=”arrow-circle-1″]Changes that were made by triggers appear in the log normally just like any other kind of changes to a table. Therefore ULT4DB2 will create the statements that reflect the actions of the trigger as well. If such the same triggers also exist in the target tables, ULT4DB2 allows you to skip such operations to get the correct workload for the target tables.[/su_spoiler]

[su_spoiler title=”How does ULT4DB2 handle columns with GENERATED ALWAYS?” icon=”arrow-circle-1″]The contents of these columns appear on the Db2 log normally just like any other value. Therefore, if an INSERT statement is generated, it will contain this column. This has to be taken into consideration if the INSERT statement is supposed to be executed against a target table. It is recommended to remove the GENERATED ALWAYS clause from the target table’s column because it is important that the row receives the same value for the column in question. Otherwise, subsequent UPDATE or DELETE operations may cause the wrong target row to be affected.[/su_spoiler]

[su_spoiler title=”How does ULT4DB2 handle mass deletes?” icon=”arrow-circle-1″]ULT4DB2 creates one delete for each row that has been affected by a mass delete.[/su_spoiler]

[su_spoiler title=”How does ULT4DB2 handle ON DELETE CASCADE?” icon=”arrow-circle-1″]Changes that were made by an ON DELETE CASCADE clause appear on the log normally just like any other kind of changes to a table. Therefore ULT4DB2 will create the statements that reflect the actions of the ON DELETE CASCADE clause as well. If the same clauses also exist in the target environment, ULT4DB2 allows you to skip such records to get a correct workload for the target tables.[/su_spoiler]