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 your tablespaces must be of sufficient size to accommodate two copies of tables being converted. To account for this tablespace requirement, you should identify the four largest tables which you plan to convert, determine their current size, and multiple that by two. Then increase the size of your business data tablespaces by that amount.

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 Undo and tablespaces should be as large as the N largest tables combined, including all indexes. If desired, you can resize your Temp tablespaces after you complete the upgrade.

For Oracle databases, you must ensure that:

• Tablespace logging is turned off during the upgrade.

• Existing table fragmentation is minimized.

• Archive logging is turned off during the upgrade.

• Undo and Temp tablespaces are large enough to accommodate the largest tables (including all their indexes) in your JD Edwards EnterpriseOne database.