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 you will need sufficient disk space to accommodate two copies of tables being converted. To account for this disk space requirement, you should identify the four largest tables which you plan to convert, determine their current size, and multiple that by two.
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 |
For DB2 for IBM i databases, ensure that:
Your IBM i machine is running the supported OS version and latest database PTFs as detailed in the MTRs for JD Edwards EnterpriseOne. Refer to Accessing Certifications.
You do not enable journaling during the conversion.
Your Deployment Server is running with the latest iSeries Access PTF.