Troubleshooting the migration utility

Consult this topic for information about troubleshooting the migration utility, such as problems you might encounter during installation, configuration, and use of the product, as well as error messages and how to enable logs and collect diagnostic information.

Event data is not migrated to BMC Helix Operations Management because of a condition

Issue symptoms

When you try to migrate event data from  to , an error is displayed and the event data is not migrated.

Issue scope

This might occur because the policy uses the $CLOSE_EV.CLASS equals $EV.CLASS condition in . This condition is not supported in .

Workaround

Remove the $CLOSE_EV.CLASS equals $EV.CLASS condition from the policy in  and migrate the policy again.

This does not impact the policy execution in  because the CLASS equals condition is already present in .

Event rules are not migrated to BMC Helix Operations Management

Issue symptoms

While migrating event data from  to , event rules are not migrated and the following error message appears in the event_migration.logs file:

Issue scope

This error occurs because the .mrl file that is used for migration contains invisible characters. 

Workaround

Create a new .mrl file with the same content and then migrate the event rules.

Perform the following steps to create a new .mrl file:

1. Copy the content of the .mrl file.
2. Rename the file to easily identify it. For example, you can add the word old as a suffix in the file name, such as <file_name>_old.mrl.
3. Create a new file and paste the copied content in it. 
4. Save the new file with the original .mrl file name, for example <file_name>.mrl.
5. Run the migration utility.

Event data is not migrated to BMC Helix Operations Management because the opadd function is not in the correct format

Issue symptoms

When you try to migrate event data from  to , an error related to the opadd function is displayed in the log files and the event data is not migrated.

Issue scope

Thiss issue occurs because the opadd function data is not in the correct format.

Workaround

Ensure that the opadd function data is in the correct format and run the migration utility again.

The following example shows the opadd fuction in the correct format:

opadd($E, "ITOpsOperations:OWNERSHIP_TAKEN","Notifiation sent to");

This fomat contains the following parameters:

• The first parmater $E is the entity name 
• The second parameter is an acceptable operation. The following operations are acceptable:
  • ITOpsOperations:ACKNOWLEDGED
  • ITOpsOperations:OWNERSHIP_TAKEN
  • ITOpsOperations:OWNERSHIP_DECLINED
  • ITOpsOperations:OVERRIDE_CLOSED
  • ITOpsOperations:ASSIGNED_TO
  • ITOpsOperations:PRIORITY_SET
  • ITOpsOperations:UNACKNOWLEDGED
• The third parameter is the opadd function. Make sure that the third parameter is not empty.

The event migration utility does not start

Issue symptoms

The event migration utility does not start.

Issue scope

This issue occurs because either the MCELL_HOME directory is not set correctly, or the etc directory does not exist. One of the following error messages is displayed:

• MCELL-HOME is not properly set.
• MCELL_HOME is not properly set. Unable to locate /etc directory. Exiting application.

Workaround

Ensure the following points and run the utility again:

• The MCELL_HOME directory is set correctly.
• The etc directory exists.