HCL Workload Automation, Version 9.4

Parallel data migration from Oracle to DB2

About this task

With the following steps all scheduling object definitions and global options can be migrated from the Oracle database of a HCL Workload Automation version 9.4 instance to the DB2® database of another instance (freshly installed or upgraded to version 9.4).
  1. Fresh-install another instance of HCL Workload Automation version 9.4 or upgrade an existing instance to version 9.4 making it point to a DB2 database, by defining the MDM_DB2 as master domain manager workstation name. The installation process automatically defines in the DB2 database the following workstations:
    • MDM_DB2_DWB is the broker workstation name.
    • MDM_DB2_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 master domain manager that points to Oracle. The fault-tolerant agent agent workstation name must be MDM_DB2 that you specified in the installation process.
  3. On the current master domain manager pointing to the Oracle database run the dataexport command or script to export all scheduling object definitions and global options. 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 that points to the Oracle database.
    export_dir
    The directory where the export files are to be created.
    For example: 
    dataexport.cmd F:\TWS93\twsORACLEuser F:\TWS93\export
    The object definitions and the global options are retrieved from the Oracle database and placed in the F:\TWS93\export directory.
  4. Verify the following files were created in export_dir:
    • calendars.def
    • erules.def
    • jobs.def
    • globalOpts.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 current master domain manager that points to Oracle 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_ORACLE master domain manager workstation name in the Oracle database with the value MDM_DB2 master domain manager workstation name in the DB2 database.
    • MDM_ORACLE_DWB broker workstation name in the Oracle database with the value MDM_DB2_DWB broker workstation name in the DB2 database.
    • MDM_ORACLE_1 agent workstation name in the Oracle database with the value MDM_DB2_1 agent workstation name in the DB2 database.
  7. On the new instance run the dataimport command or script to import all scheduling object definitions and global options to DB2. 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 instance of HCL Workload Automation that points to the DB2 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\twsDB2user F:\TWS93\export
    The object definitions and the global options are retrieved from the F:\TWS93\export directory and stored in the DB2 database.
  8. On the master domain manager that points to Oracle run the conman switchmgr command to make the HCL Workload Automation instance pointing to DB2 as the acting master domain manager. For information on the switchmgr command see User's Guide and Reference.
You have now completed the data migration steps.