Introduction

This Oracle by Example (OBE) provides instructions to migrate your JD Edwards EnterpriseOne 9.2 data from an on-premises system with Oracle database on Linux to One-Click instance on Oracle Cloud.

In this OBE, you will:

  • Run the export script on the on-premises database server.
  • Run the UBEs manually on the on-premises deployment server.
  • Run the import script on the Database Server on the One-Click instance.
  • Run the UBEs manually on the Deployment Server on One-Click instance.
  • Complete the post migration tasks.

Time to Complete

Migration time can vary and may take several hours, based on the number of tables and the size of the data being imported.

Background

Oracle Cloud migration supports the migration of Applications 9.2 on-premises environment to Oracle Cloud (One-Click).

Before starting the migration process, make sure all traditional objects are checked in for the path code you plan to migrate. Project information will not be migrated to the One-Click instance. User Defined Objects (UDOs) that are reserved to a real project, will be moved to the users default project at the end of the migration process.

To migrate JD Edwards EnterpriseOne to Oracle Cloud for Linux, the on-premises environment must be running Tools Release 9.2.1 or later with Applications 9.2. After the migration is complete, your migrated environment will be on the same applications release as the rest of your One-Click installation.

Supported on-premises environment:

  • EnterpriseOne Tools Release 9.2.1 and later
  • EnterpriseOne Applications Release 9.2
  • Oracle database on Linux

Prerequisites

Before the migration, ensure that:

  • The on-premises environment is on Applications 9.2 and Tools Release 9.2.1 or later.
  • A full package build is completed, populating the repository tables.
  • You have provisioned PS920 on the One-Click Enterprise Server, and have the services running against PS920. The system overwrites the target environment (for example, DV920) for the first migration.
  • One-Click is on 9.2.8 with UN8 or later.
  • Old packages are cleaned up to speed up the migration process.

What do You Need?

To perform the steps in this OBE, you must have:

  • A subscription to Oracle Cloud. You must be a user with the Compute Operations role. For more information, see How to Begin with Oracle Compute Cloud Service Subscriptions in Using Oracle Compute Cloud Service.
  • Verified the database size on the One-Click instance is large enough for the import and that database configuration/parameters are validated or tuned for your business needs (for example: maximum extend and extend size parameters).
  • Created a JD Edwards EnterpriseOne Multi Tier Deployment on Oracle Cloud One-Click Instance. See the Multi Tier or One-Click Provisioning OBEs for more information.
  • Downloaded JDE_9.2_Migration_Utility_9.2.26_for_Linux.zip from the Oracle Update Center.

    The JDE_9.2_Migration_Utility_9.2.26_for_Linux.zip contains:

    • Export folder with export scripts (move this folder to the on-premises database server.)
    • Import folder with import scripts (move this folder to the database server on the Oracle One-Click instance.)
  • Verified you can execute the following command on the source and destination machines;

    sqlplus <dbuser>/<dbpass>@<netname></netname>

Task 1: Running the Export Script on On-Premises Database Server

The exp_set.sh script file exports the schemas on the on-premises database server. The dump files can then be moved to the database server on the One-Click instance.

  1. Before starting, run the Work with Software Updates program (P96470) program on the on-premises Deployment Server. As this application starts, it synchronizes the ESU history between System – 920 and System Local. After the process is complete, you can close the application.
  2. Navigate to where you downloaded the export scripts on the on-premises Database Server (for example: /u01/OracleDB/MoveandImprove).
  3. Edit the exp_set file with these settings.
    The exp_set file
    The exp_set file
    Field Description
    PATHCODE_PREFIX The prefix of the path code to export. Enter DV.
    Valid values are PY, PD, and DV.
    PATHCODE_RELEASE The path code release to export. Enter 920.
    SHARED Export data dictionary schema. Enter YES to export data dictionary.
    Otherwise enter NO.
    DUMP_DEST The full path to the folder where you want to store the database dump files. Enter /u01/OracleDB/MoveAndImprove.
    *Ensure the directory exists*
    DBUSER The database user with privileges to perform EXPDP operations. Enter system.
    DBPASS The password for DBUSER. Enter the system password.
    Note: If your database password contains any allowable special character like $ you must put single quotes around the database password in both the exp_set and the imp_set files. For example, if your database password includes a $ symbol, you would specify this value like this:
    DBPASS='Hello$123'
    NETNAME The TNS name for the database (for example, enter orcl).
  4. Save and close exp_set.
  5. Run the export.sh script.
    The exp_set file
    export.sh
  6. Verify that successfully completed is found in all generated log files.
  7. Verify that the .dmp files were successfully created in the specified location.
  8. Transfer the .dmp files to a folder on the database server on the One-Click instance for importing in a later step.

Task 2: Running the UBEs on Your On-Premises Deployment Server

  1. Run the R98403XA versions on the on-premises deployment server to copy system tables including ESU tables ((F9670, F9671, and F9672) and Object Librarian tables.
    • XJDE0002 copies the system tables including the ESU tables ((F9670, F9671, and F9672).
    • XJDE0003 copies the Object Librarian. Do not change the data selection.
    The exp_set file
    R98403XA Report- Copy tables to XML
  2. After running the UBE versions, verify that all the XML files exist in the target directory. Also verify the PDF reports for errors, if any.
  3. For all versions, change the Processing Option for target XML Path if storing the XML files in a different location.
    The exp_set file
    R98403XA Processing Options
  4. R98403XA, XJDE0002 copies a subset of system tables (Security,  Media Objects, and ESU history).
    R98403XA XJDE0002 Report
    R98403XA, XJDE0002 Report
  5. R98403XA, XJDE0003 copies a subset of Object Librarian tables to c:\PlannerData. Copying the Object Librarian ensures that the data for custom objects are copied (ADD mode). The database scripts do not copy the on-premises Object Librarian to One-Click.
    R98403XA XJDE0003 Report
    R98403XA, XJDE0003 Report
  6. Zip the c:\PlannerData folder from where the Object Librarian and System data was copied.
  7. Copy PlannerData.zip to the Oracle Cloud Deployment Server and extract it.

Task 3: Running the Import Script on Oracle Cloud Database Server

After running the on-premises export script on the database server, run the import script on the Oracle Cloud Database Server.

The import.sh script imports data from the dump files (generated by the export script) into the database server on the One-Click service.

  1. Extract the Linux/Oracle scripts JDE_9.2_Migration_Utility_9.2.26_for_Linux.zip on the cloud database server.
  2. Copy the dump files directory to your Cloud database server.
  3. Open the import folder and edit the imp_set file.
    The exp_set file
    The imp_set file
    Field Description
    FROM_PATHCODE_PREFIX The prefix of the path code you exported on the on-premises Database Server. Enter DV.
    Valid values are PY, PD, and DV.
    TO_PATHCODE_PREFIX The prefix of the target path code on Oracle Cloud Database Server.
    Can be the same or different from FROM_PATHCODE_PREFIX.
    PATHCODE_RELEASE Enter 920. Do not change.
    SHARED Enter YES to import data dictionary. You only need to import the data dictionary once.
    Otherwise enter NO.
    DUMP_DEST The full path to the folder where you copied the database dump files. Enter /u01/OracleDB/MoveAndImprove.
    DBUSER The database user with privilege to perform IMPDP operations.
    DBPASS The password for DBUSER. Enter the system password.
    Note: If your database password contains any allowable special character like $ you must put single quotes around the database password in both the exp_set and the imp_set files. For example, if your database password includes a $ symbol, you would specify this value like this:
    DBPASS='Hello$123'
    NETNAME The TNS name for the database (for example, enter orcl).
    DEP_SVR_NAM The name of the Oracle Cloud Deployment Server in uppercase.
    PRE_DEP_SVR The name of the on-premises Deployment Server in uppercase.
    SYSTEM Enter YES. This should only be imported once.
    ENT_SVR_NAM Oracle cloud enterprise server name. Match the case as the name in the SY920.F9650 table.
    PRE_ENT_SVR On-Premises Enterprise Server name. Match the case as the name in the SY920.F9650 table in the on-premises Enterprise Server.
  4. Switch (su) to your oracle user and navigate to your scripts folder.
  5. Run the import.sh. Logs are created in the dump directory. Check the logs to ensure that the import was successful.
    The exp_set file
    import.sh

Task 4: Running the UBEs on Oracle Cloud Deployment Server

On the Oracle Cloud Deployment Server, run the R98403XB versions to copy the data from on-premises to Cloud. Do not change the data selection on each version and verify the PDF reports.

  1. Run the R98403XB versions on the Oracle Cloud deployment server to copy the data from on-premises to the Oracle Cloud deployment server. 
    • R98403XB, XJDE0034 copies system rows in ADD mode. Note that this process does not copy OCM mappings, environment definitions, and ESU history.
    • R98403XB, XJDE0035 copies a subset of Object Librarian tables to Data Dictionary Local, as input to the Object Librarian Merge R98605.
    • R98403XB, XJDE0037 copies the ESU history tables to Data Dictionary Local, as input to the ESU History Merge R96723.
    The exp_set file
    R98403XA Report- Copy tables to XML
  2. Change Enter the XML Data Path processing option value for each of these versions to the location where you copied the PlannerData from your on-premises deployment server.
    The exp_set file
    R98403XA Processing Options
  3. Check the PDF files to ensure that copies were successful.
  4. Run the UBE R98605 - Merge OL records from On-Prem To One-Click.
    • R98605 deletes the F9861, F98602, F98603, F9861W rows for target path code.
    • Copies the F9861, F98602, F98603, F9861W rows for source path code from the on-premises deployment server and substitutes the target path code and target deployment server. For example, copy PD920 to DV920 or DV920 to DV920.
    • Copies the F9860, F9860W, F98601, F9862, F9863, F9865 rows in APPEND mode for custom objects found in F9861 for the source path code.
    • Adds the missing F9860W row for each F9861W.
    R98605 - Merge OL records from On-Prem To One-Click
    R98605 - Merge OL records from On-Prem To One-Click
  5. Verify the processing options. Do not change the Source Data Source value.
    R98605 Processing Options - Process Tab
    R98605 Processing Options - Process Tab

    Summary/Detail field - 1 only displays the row counts. 0 also lists all the object rows that were copied.

    R98605 Processing Options - Display Tab
    R98605 Processing Options - Display Tab
  6. Review the Summary and Detail reports.
    R98605 Summary Report
    R98605 Summary Report

    Detail (0) lists all objects that have been copied and displays the row counts.

    R98605 Detail Report
    R98605 Detail Report
  7. Run the UBE R96723, ZJDE0002 in Final mode. It copies ESU history to System Local and System - 920. ZJDE0001 is the same report in Proof Mode and does not perform any updates. Proof Mode only displays row counts that would be inserted in Final Mode.
    R96723 ZJDE0002 UBE
    R96723 ZJDE0002 UBE

    The R96723, ZJDE0002 UBE:

    • Deletes F9671 in System Local / System - 920 for target environment.
    • Copies F9671 for source environment, substituting target environment. (For example PD920 -> DV920 or DV920 –> DV920).
    • Deletes F9672 in System Local / System - 920 for target path code.
    • Copies F9672 for source path code, substituting target path code. (For example PD920 -> DV920 or DV920 –> DV920).
    • At this point the ESU history for the target environment / path code matches the on-premises Central Objects that were exported and imported.
  8. In the processing options for R96723, change the Source Environment to the environment you want to copy from and Target Environment to where you want to copy the data. Do not change the Source ESU Data Source value or the data selection.
    R96723 Processing Options - Process Tab
    R96723 Processing Options - Process Tab
  9. Proof mode does not update the tables but displays the row counts. Final mode updates the tables.
    R96723 Processing Options - Update Tab
    R96723 Processing Options - Update Tab
  10. Review the R96723 - Copy ESU History Move and Improve report.
    R96723 - Copy ESU History Move and Improve Report
    R96723 - Copy ESU History Move and Improve Report

Post Migration Tasks

After running all the scripts and UBEs:

  1. Deploy the following to the target path code on the Oracle cloud database server:
    • Latest Planner Update to the target path code, if not installed.
    • Latest Tools Roll-up ESU.
    • UN9 update or the update that matches the rest of your Oracle Cloud (One-Click)  installation (this is equivalent to doing a E920 to E920 Simplified Upgrade).
    • Run the Special Instructions and Table Conversions for UN9 update.
  2. Security/Password Reset
    Sign in to DEP920 on the deployment server, and change the passwords for any new security overrides. P98LPSEC for F98OWSEC and P980001 for System Users F98OWPU. Look for the security override for Server Map from the on-premises enterprise server and delete the row. For example, <OnPrem> - 920 Server Map.

    Note:

    The passwords in the F98OWSEC and F98OWPU rows that were copied in APPEND mode, likely have the wrong password (different site key or different hashing algorithm).
  3. Build and deploy a full package to the target path code. The package build does not work if there are any security overrides with invalid passwords.
  4. You can now change the jde.ini on the enterprise server so that services can run using the migrated environment.


More Learning Resources

For more learning resources, visit the LearnJDE. 

For product documentation, visit JD Edwards on Oracle Help Center.