This documentation applies to the 8.1 version of Remedy IT Service Management Suite, which is in "End of Version Support." You will not be able to leave comments.

To view the latest version, select the version from the Product version menu.

Reviewing the migration results and resolving issues

This page lists activities you should perform after you migrate:

Threshold set for errors

If a form encounters more than a 1000 errors during the delta data migration run, then delta data migration stops migration of the form and continues with the next one. After you fix the cause of errors, then re-run delta data migration with the same product selections and date. Delta data migration re-runs for any failed forms and failed records.

Reviewing log files

After you run the Delta Data Migration (DDM) Tool, you will see a Working folder under <MigratorInstallFolder>\DeltaDataMigration.  This folder contain the package and instruction xml files for all your products. Under the Working folder, a Logs folder holds the .html, Compare.xml and .mgrresult files.  These files are discussed below.

The DDM tool creates HTML-based log files by using the package names that have the .html suffix:

  • Migrate.html
  • Compare.html

Search the HTML log files for the following keywords:

  • ERROR — Lists the form information and data for a server, API, or SQL error.
  • WARNING or WARN — Describes warnings from BMC Remedy AR System that do not stop the package migration.

The DDM tool also creates .mgrresult files and comparison output XML files:

  • Migrate script details — The migrate script creates a .mgrresult file for each instruction with the instruction name and suffix _Migrate that includes the results of migrating all the form data (entries). The file lists the number of entries that were migrated for each form and includes the same error information (if any) that the HTML log file contains.Open this file with BMC Remedy Migrator. Examples of BMC Remedy Migrator output file names are:
    • ITSM_Package_Migrate.html — The migrator log file (you will have one of these for each package).
    • Remedy_Service_Request_Management_Migrate.mgrresult — The migrator result file (you will have one of these for each instruction file).
  • Compare script details — Apart from the HTML log file, the comparison script also creates an .xml result file for each instruction with the instruction name and suffix _Compare. These files include all data entries that are either different or missing in the destination server. (A comparison that is run after a successful migration should not report any differences in form data, but the report will show differences if a field's data type was changed even if the data is the same.)
    Examples of compare output file names are:
    • ITSM_Package_Compare.html — The compare log file (you will have one of these for each package).
    • Remedy_Service_Request_Management_Compare.xml — The compare .xml result file (you will have one of these for each instruction file).

Reviewing errors

This section lists the known errors and warnings that might occur in your log files. Check the log files for errors and contact Customer Support as needed for assistance.

The following warning in the SRM_Package_Migrate and SRM_Package_Compare HTML files can be ignored:

Keyword

Error

Description

WARN

Instruction Interpreter

The Form Name defined in the mapping file is not the same as specified in the Instruction File.
This warning occurs due to data migrating from the SRM:CFG_Rules Form on the production server to a different form on the staging server.

The following error in the SLM_Package_Migrate, SRM_Package_Migrate, SLM_Package_Compare and SRM_Package_Compare HTML files can be ignored:

Keyword

Error

Description

ERROR

Comparison Generator

Form does not exist on server: INT:SLMSRS:ConfigServiceTarget:Defaults.
The error is displayed if BMC Service Level Management or BMC Service Request Management integration is not present.

The following error in the Atriumpackage_Migrate and Atriumpackage_Compare HTML files can be ignored if BMC Atrium Integration Engine or Enterprise Integration Engine is not installed in your servers:

Keyword

Error

Description

ERROR

Migrations

[ars81:4] - [ars81:303]-[Form does not exist on server EIE:ApplicationSettings]
This error results from the form being not available in the server.

The following errors in the BMC Remedy Foundation Elements_Migrate and BMC Remedy Foundation Elements_Compare HTML files can be ignored:

Keyword

Error

Description

ERROR

Migrations

An Error Occurred with Data 'CFG:Geography State-Province'

ERROR

Migrations

[ars81:4] - [ars81:303]-[Form does not exist on server CFG:Geography State-Province]

Form names for these forms and the CFG:Pred-Succ Associations form had a slash (/ ) in their names, which was changed to a hyphen (-) in BMC Remedy ITSM Suite 7.0.3 Patch 010 and later. Depending on your version, you might see an error for the form name that contains either ‘ / ‘ or ‘ -‘. This can be ignored because the data will be migrated with the form name that matches your server.

The following errors in the ITSM_Foundation_Migrate and ITSM_Foundation_Compare HTML files can be ignored if the forms are not on your source server:

Keyword

Error

Description

ERROR

Migrations

An Error Occurred with Data 'AST:AssetAdvancedSearchCriteria

ERROR

Migrations

[ars81:4] - [ars81:303]-[Form does not exist on server AST:AssetAdvancedSearchCriteria]

ERROR

Migrations

An Error Occurred with Data ' AST:CILifeCycleStatus '

ERROR

Migrations

[ars81:4] - [ars81:303]-[Form does not exist on server 'AST:CILifeCycleStatus']

The following errors in the BMC Remedy Task_Management_Migrate and BMC Remedy Task_Management _Compare HTML files can be ignored if the forms are not on your source server:

Keyword

Error

Description

ERROR

Migrations

An Error Occurred with Data 'TMS:RelationshipsInterface_Create'

ERROR

Migrations

[ars81:4] - [ars81:303] - [Form does not exist on server 'TMS:RelationshipsInterface_Create']

The following errors in the BMC Remedy Foundation Elements_Migrate and BMC Remedy Foundation Element_Compare HTML files can be ignored if the forms are not on your source server:

Keyword

Error

Description

ERROR

Migrations

An Error Occurred with Data 'CFG:HTMLCatalog'

ERROR

Migrations

[ars81:4] - [ars81:303]-[Form does not exist on server 'CFG:HTMLCatalog']

If you run a compare report after a successful migration, then no data with "state=different" or missing data is expected. The compare report should not report any differences.
The Remedy_Contract_Management_<datetime>_compare.xml output file might report the following differences, which can be ignored because the source server does not have default value data for the fields listed. However, the destination server does have this data.

<data destination-form="CTR:ContractBase" source-form="CTR:ContractBase" unique-field-id="179"> {{<entry entry-id="000000000000001" id="CO0050560C63F20vnfQwlG06AALAMA" state="different">
<field id="260600003" name="Purchase Cost" state="different" />
<field id="260600004" name="Renewal Cost" state="different" />
<field id="270002042" name="Cost per Asset" state="different" />
<field id="270002043" name="Cost per Component" state="different" />

If you are migrating data from BMC Remedy ITSM versions 7.0.02 or 7.0.03 with or without patches, you will see the following errors in the ITSM_Foundation_migrate_<datetime>.html file. This is a known issue that occurs because data migration in the APR:Approver Lookup and APR:SYS-Approval Definition forms is not supported.

The following errors might appear for the APR:Approver Lookup form:

Keyword

Error

Description

ERROR

Migrations

An Error Occurred with Data 'APR:Approver Lookup'

ERROR

Migrations

[ars81:4] - [ars81:986] - [ars81:Currency fields can not be used for grouping.]

The following errors might appear for the APR:SYS-Approval Definition form:

Keyword

Error

Description

ERROR

Migrations

An Error Occurred with Data 'APR:SYS-Approval Definition'

ERROR

Migrations

[ars81:4] - [ars81:985] - [ars81:No active Currency Code found on the Currency Code form.]

If you are migrating data from BMC Remedy ITSM versions 7.0.02 or 7.0.03 with or without patches, you will see the following errors in the ITSM_Change_Management_migrate_<datetime>.html, ITSM_Change_Management_compare_<datetime>.html, and Remedy_Change_Worklog_DetailDesc_Null_<datetime>_migrate.mgrresult files. You can ignore these errors as the form does not exist on your source server.

Keyword

Error

Description

ERROR

Migrations

An error occurred with Data RMS:WorkLog

ERROR

Migrations

[ars81:4]-[ars81:303]-[Form does not exist on server RMS:WorkLog]

If your source BMC Service Request Management version is 2.2 or 2.2 patch 1, you might see the following errors in the .html log file, and you can ignore these errors as they are benign.

Keyword

Error

Description

ERROR

Migrations

An Error Occurred with Data 'WOI:Associations'

ERROR

Migrations

[ars81:4] - [ars81:303] - [Form does not exist on server WOI:Associations]

The SRD:AuditDisplay form is not to be updated during the delta data period, so the following errors can be ignored:

Keyword

Error

Description

ERROR

Migrations

An Error Occurred with Data 'SRD:AuditDisplay'

ERROR

Migrations

for this form does not match that in owning application SRD:AuditDisplay]

ERROR

Migrations

[ars81:4] - [ars81:9858] - [ars81:The application is not licensed Remedy Service Request and Catalog System]

Resolving unique index violations

A unique index violation can happen in the following scenarios:

  • The request ID coming from the source server is already used by another record in the destination server. This can happen if the same record is already on the destination server, but is using a different ID.
  • The request ID is not used, but the GUID (value for field 179) or the unique indexed field of that form is used by another record in the destination server. This can be caused by test data created on the destination server, which has the same ID as an item being imported.

These situations can occur if test data is created on the destination server but is not reverted to a clean state, or if an escalation or a process (such as from Atrium Integration Engine, DSO, or Reconcilation Engine) has not been disabled and created these records on the destination server.

An error looks something like this:

ERROR Migrations 07:01:32 : [4][The value(s) for this entry violate a unique index that has been defined for this form schema: CTM:Support Group Alias, entry: SGS000000006670, 2 unique index(es), field(s): 1000000079 1000000293 179]

To resolve index violations

  1. Delete the records with the duplicate indexes from the destination server.
    1. Find the entry ID (field ID 1) in the error message.
    2. Search the source server for a record with that field ID.
    3. Find the fields and the values of the unique index fields from that form.
    4. On the destination server, run a search with those values (not with the field ID 1).
    5. Review the data and see if the values for Field ID 1 and field 179 are different.
    6. Look for the Last Modified By and Date to confirm who created or updated the record.
    7. After you confirm that it is a duplicate, delete the record on the destination server.
  2. Run the Delta Data Migration Tool again with same product selections and date used, so that DDM can look into the working folder instruction xml files and only process records in forms that had errors.
    You should choose all the products or applications you selected during the previous run even if some of them did not have errors for the re-run. Otherwise, the working folder is replaced and DDM is not be able to process only the records with errors.

Benign migration errors

In any form, you might see the following errors:

Keyword

Error

Description

ERROR

Migrations

[Migration failed for schema BMC.CORE:BMC_BaseElement. Entry missing for entry id :000000023575792]

ERROR

Migrations

An Error Occured with Data 'BMC.CORE:BMC_BaseElement'

ERROR

Comparison Generator

Form does not exist on server: CMDB.SC:ServiceContextAuthenticationInfo

ERROR

Migrations

If your source (current production) server is running BMC Atrium 7.6.0.3, you might encounter the following error in the Product_Catalog_package_Migrator and Product_Catalog _package_Compare HTML files:
[4] -[303] -[Form does not exist on server PCT:TrustedDataset]
This form exists on the destination (upgraded) server but is not available in Atrium 7.6.03 version, so you can safely ignore this benign error.

These errors are benign, and you can safely ignore them. The Delta Data Migration Tool is run with a live source server, and you have not yet committed the record ID that the utility is trying to migrate. Therefore, the record ID so not in the source server's database yet.

Related topics

Restrictions on product activities in production after restoring database on staging server (with overlays)
Using the AREntryCounter utility

Where to go from here

Extending Delta Data Migration to include customizations

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments