Troubleshooting Control-M Migration

The following topics describe errors and how to troubleshoot issues during migration:

  • Debugging the Control-M/EM export and import processes

  • SLA Management Web Application settings from the old environment

Debugging the Control-M/EM Export and Import Processes

This procedure describes how to set the debugging mode for the Control-M/EM export and import stages, and where the logs are located.

Begin

  1. To check the installation, open the installation log file:

    • UNIX: <em_home>/Upgrade_Export/logs/em_upgrade.log

    • Windows: <em_home>\Upgrade_Export\logs\em_upgrade.log

  2. If a problem occurs during the export stage, run one of the following commands in the previous version environment:

    • UNIX: <em_Home>/Upgrade_Export/export -debug

    • Windows: <em_Home>\Upgrade_Export\export.bat -debug

    The debug information for the export is saved in the em_upgrade.txt Control-M Upgrade log file, which is located in the previous version in the following location:

    • UNIX: <em_Home>/Upgrade_Export/logs

    • Windows: <em_Home>\Upgrade_Export\logs

  3. If a problem occurs during the import stage, run one of the following commands in the new version environment:

    • UNIX:<em_Home>/Upgrade/Import/import -debug

    • Windows: <em_Home>\Upgrade\Import\import.bat -debug

    The import debugging information is saved in the em_upgrade.txt Control-M Upgrade log file, which is located in the new version environment in the following location:

    • UNIX: <em_Home>/Upgrade/Import/logs

  4. Windows: <em_Home>\Upgrade\Import\logs

    Additional debugging information is saved in the util.log and util_auth.log files, which are located at:

    • Export debugging information

      • UNIX: <em_Home>/Upgrade/Export/logs

      • Windows: <em_Home>\Upgrade\Export\logs

    • Import debugging information

      • Windows: <em_Home>\Upgrade\Import\logs

      • UNIX: <em_Home>/Upgrade/Import/logs

    5. If a problem occurs during the execution stage of the util utility as part of the Control-M Migration operation, use the -debug_util flag (not the -debug flag).

SLA Management Web Application Settings from the Old Environment

To preserve the filter setting on the Services List display, you must copy the <old>bim_filters.xml file to the SLA Management Server (previously known as the BMC Batch Impact Manager Server) home folder in the new environment.

  • UNIX: <emHome>/appl/bim/etc/bim_filters.xml

  • Windows: <emHome>\bim\etc\bim_filters.xml