HCL Workload Automation, Version 9.4

Parallel data migration from DB2 to Oracle

About this task

With the following steps all scheduling object definitions and global options can be migrated from the DB2® database of a HCL Workload Automation version 9.4 instance to the Oracle database of another instance.
  1. Fresh-install another instance of a HCL Workload Automation version 9.4 master domain manager and make it point to an Oracle database, by defining the MDM_ORACLE as master domain manager workstation name. The installation process automatically defines in the Oracle database the following workstations:
    • MDM_ORACLE_DWB is the broker workstation name.
    • MDM_ORACLE_1 is the agent workstation name.
  2. Use composer or the Dynamic Workload Console to define this instance as a fault-tolerant agent in the database of the current master domain manager that points to DB2. The fault-tolerant agent workstation name must be MDM_ORACLE that you specified in the installation process.
  3. On the master domain manager that points to DB2 run the dataexport command or script to export all scheduling object definitions and global options from DB2. Find this file in the bin subdirectory of the HCL Workload Automation home directory.
    Run dataexport from a Windows or UNIX command prompt as follows: 
    dataexport <source_dir> <export_dir>
    where:
    source_dir
    The installation directory of the instance of HCL Workload Automation version 9.4 that points to the DB2 database.
    export_dir
    The directory where the export files are to be created.
    For example: 
    dataexport.cmd F:\TWS93\twsDB2user F:\TWS93\export
    The object definitions and the global options are retrieved from the DB2 database and placed in the F:\TWS93\export directory.
  4. Verify the following files were created in export_dir:
    • calendars.def
    • jobs.def
      Note: The record length supported by DB2 is 4095 characters, but it decreases to 4000 characters with Oracle. When you migrate your job definitions to Oracle, any job scripts or commands exceeding 4000 characters in length are not migrated. In such case, the data import utility replaces the job definition with a dummy job definition and sets the job priority to 0, guaranteeing that successors are not run.
    • globalOpts.def
    • erules.def
    • parms.def
    • prompts.def
    • resources.def
    • scheds.def
    • topology.def
    • users.def (includes encrypted user passwords)
    • vartables.def
    • rcgroups.def
    • acls.def
    • sdoms.def
    • srols.def
  5. On the master domain manager that points to DB2 do the following:
    1. Ensure that the carry forward option is set to ALL. Run: 
      optman chg cf=ALL
    2. Add the new instance (that you installed in step 1 and that you momentarily defined as a fault-tolerant agent) in the current plan. To do this, run: 
      JnextPlan -for 0000
    3. Check that the new instance was linked by running: 
      conman sc
  6. Open the export_dir\topology.def file and substitutes the following values:
    • MDM_DB2 master domain manager workstation name in the DB2 database with the value MDM_ORACLE master domain manager workstation name in the Oracle database.
    • MDM_DB2_DWB broker workstation name in the DB2 database with the value MDM_ORACLE_DWB broker workstation name in the Oracle database.
    • MDM_DB2_1 agent workstation name in the DB2 database with the value MDM_ORACLE_1 agent workstation name in the Oracle database.
  7. On the new instance run the dataimport command or script to import all scheduling object definitions and global options to the Oracle database. Find this file in the bin subdirectory of the HCL Workload Automation home directory.
    Run dataimport from a Windows or UNIX command prompt as follows: 
    dataimport <source_dir> <export_dir>
    where:
    source_dir
    The installation directory of the new instance of HCL Workload Automation version 9.4 pointing to the Oracle database.
    export_dir
    The directory from where the export files are to be read from. This directory is the same export_dir directory specified for dataexport.
    For example: 
    dataimport.cmd F:\TWS93\twsORACLEuser F:\TWS93\export
    The object definitions and the global options are retrieved from the F:\TWS93\export directory and stored in the Oracle database.
  8. On the master domain manager that points to DB2 run the conman switchmgr command to make the HCL Workload Automation instance pointing to Oracle as the acting master domain manager. For information on this command see HCL Workload Automation: User's Guide and Reference.
You have now completed the data migration steps.