Preparing the DB2 for Linux, UNIX, and Windows Database for Table Conversions

The upgrade process requires specific database preparation to account for the various CPU-bound and data size requirements. It is important to note that during execution of the Table Conversion Workbench database data files and transaction log need to be large enough to accommodate two copies of tables being converted. To account for this data files and transaction log requirement, you should identify the four largest tables which you plan to convert, determine their current size, and multiple that by two. You must also change your data files to allow them to extend by that amount. Alternately, you can preallocate the extra space that will be required, which will improve performance.

For example, the following table shows a hypothetical environment where the largest tables are F0911, F42199, F42119, and F41021.

Largest Tables	Existing Size (see Note)	Existing Size Doubled
F0911	120 MB	240 MB
F42199	80 MB	160 MB
F42119	90 MB	180 MB
F41021	56 MB	112 MB
Total Amount of Space Required to Run Tables Conversions		692 MB

Note: This includes the size of the table and all unique indexes on that table.That is, if N is the number of concurrent jobs in the TC Workbench, then the data files and transaction log should be as large as the N largest tables combined, including all indexes.

For the SQL Server database, you will also need to increase the size of your transaction log by the same amount to account for log entries which are created for each table insert.