The final step of the direct migration process is to “turn off" Oracle's JD Edwards World completely from the production environment. After the migration process is fully tested and all users are now running Oracle's JD Edwards EnterpriseOne in production, JD Edwards World can be removed.
During the migration process, JD Edwards World libraries/databases were restored or created on the JD Edwards EnterpriseOne Server(s). During the direct migration process data is migrated from these libraries/databases into new JD Edwards EnterpriseOne tables. These temporary databases / libraries can be backed up and removed from the system. For example, the CLTDTA and CLTCOM libraries containing UDC, Next Numbers and business data are removed.
For customers migrating, other JD Edwards World libraries can also be removed. These would include:
Library Name |
Description |
Examples |
|---|---|---|
JDFOBJ |
Compiled Programs |
J01051, P4210 |
JDFDATA |
All Files and Logicals with Demo Data |
F0101, F0082, F0092 |
JDFSRC |
Source for Compiled Objects |
JDESRC, JDECPY |
CLTSEC |
Security Files |
F0092, F0094 |
CLTCOM |
Control Tables |
F0082, F9200 |
CLTDTA |
Business Data Files |
F0101, F4211 |
Custom Name |
Custom program, file and source libraries |
N/A |
JDFINS |
JD Edwards World Install Libraries |
Planner files |
JDEINSTAL |
JD Edwards World Install Libraries |
Planner programs |
Also, for customers migrating on the same box, other JD Edwards World software IBM i objects could be removed. Please validate those not being used by other applications, including JD Edwards EnterpriseOne. These objects could include:
Subsystems
Out Queues
Job Queues
User Profiles
Job Descriptions
Printers (Writers)
User Indexes in QGPL
SQL Packages - DB2 stores historical SQL commands to more efficiently retrieve data.
The SQL packages need to be deleted so that DB2 creates new SQL commands for the new table definition. Refer to Document ID 626568.1 on My Oracle Support.
Data Areas in QGPL
Data queues
Message queues