1. Applications Upgrade Guide for UNIX with Oracle
  2. Table Conversion Considerations for All From Releases

Table Conversion Considerations for All From Releases

Note: In the jde.ini file on the server, change the [UBE] and [TCENGINE] sections as shown below:

Follow these steps for Simplified Upgrade with Tools Release 9.2.6.x:

With 9.2.6.1 there was a change to the folder structure of the path code on the Enterprise Server. This change breaks Table Conversions with Simplified Upgrade, as you cannot access the new table specifications on the server.

For One-Click, JDE_9.2_Simplified_Upgr_Migration_Utility downloads have a fix for the issue.

If you perform a Simplified Upgrade starting with the GA Installation CDs, you must download the scripts to create a standard package in the path code you are upgrading. Search for Bug 33784730 on Update Center.

In either case, verify that the spec.ini files on the Enterprise Server for your target path code are correct. They should not point to PS920FA. They should look similar to the spec.ini file in the PS920 path code, but should point to the path code (for example, DV920FA in DV920).

Follow these steps to perform Table Conversion:

  1. If you start from the GA Install CDs, download the scripts to create the standard package in your target path code, for example, DV920FA in DV920. After you install the GA CDs, run the scripts and verify that the package repository tables (for example, DV920.F98710DV920FA) were created.
  2. On the Enterprise Server, review the spec.ini file in your target path code and verify that it looks similar to the spec.ini file in PS920. Also, it must point to the package repository you just created. For Simplified Upgrade, the GA Platform Pack lays down a different spec.ini file, which is not applicable for Tools Release 9.2.6.
  3. The GA CDs are 32-bit. After you implement 64-bit on the Deployment Server, you must copy the bin64 from PLANNER to each of the path codes. Additionally, you must copy the 64-bit glbltbl, dddict, and ddtext files from PLANNER\spec to each path code’s spec directory. Without these files, no Table Conversions (including *ALTER in ESUs) can run.