Performing prechecks before migrating delta data

This section describes scenarios that you might encounter issues during the migration process. Review the following list of prechecks to determine whether they are applicable, and follow the procedure as described for the scenario.

Precheck 1: Application GUID conflict exists

The BMC Service Impact Manager or BMC ProactiveNet Performance Management applications have the same application Globally Unique Identifier (GUID). If you have one of these applications installed on your current source server, verify and update the configuration.xml file.

Applicable scenario

BMC Service Impact Manager or BMC ProactiveNet Performance Management are installed.

Applicable version

All versions.

Procedure

  1. Go to the directory where BMC Remedy Migratior is installed: 
    <MigratorInstallDirectory>\DeltaDataMigration
  2. Open the configuration XML file.
  3. Perform one of the following actions:
  • If BMC ProactiveNet Performance Management is installed, comment out the SIM code lines.

  • If BMC Service Impact Manager is installed, comment out the BPPM code lines.
    For example, to comment out the BPPM code lines, insert <!- and -> tags as follows:

    <!--BPPM PACKAGE FOR VERSIONS SUPPORTED-->
    <!--
    <application name="BMC_PN: Service Management Data" dir=".\Packages\BPPM" file="BPPM_Package.xml" enabled="true" custom="false">
    <guid>OS-129D647E3DD74A26AAACFD3BA1358C94</guid>
    <package src-version="8.5.00" src-patch=""/>
    </application>
    -->

Precheck 2: BMC Service Impact Manager is installed

BMC Service Impact Manager and BMC Atrium CMDB update the same CMDB forms. Therefore, you must run data migration in sequence if you have these products installed on your server.

Applicable scenario

BMC Service Impact Manager is installed on your production server.

Applicable version

All versions.

Procedure

If you have installed BMC Service Impact Manager, perform the delta data migration for BMC Atrium Core before you run the Delta Data Migration tool for BMC Service Impact Manager.

 

Precheck 3: BMC Remedy Service Desk 7.1 is installed

On the production server, the Delta Data Migration tool cannot detect BMC Remedy Service Desk 7.1 integration because the integration details are not registered in the SHARE: Application_Properties form.

Applicable scenario

BMC Remedy Service Desk 7.1 is installed on your production server.

Applicable version

7.1.00 to 7.1.xx

Procedure

  1. Create an entry for Integration for BMC Remedy Service Desk 7.1 in the SHARE:Application_Properties form.
  2. Import the SW00388960_fix.arx file from the <MigratorInstallDirectory>\DeltaDataMigration\Utilities\pre_DDM folder.

 

Precheck 4: Update Reopen_ fields changes for CTM:CFG-ApplicationPreferences

The CTM_CFG_ApplicationPreferences form has Reopen_ fields (one for each application: BMC Remedy Incident, BMC Remedy Change, and so on). The Reopen_ field had a No Action value in versions 7.6.03 and earlier. This value was removed from version 7.6.04 and later, as part of an upgrade.

Applicable scenario

Data did not migrate due to changes in selection field values for the CTM:CFG-ApplicationPreferences form.

Applicable version  

All version prior to BMC Remedy ITSM 8.0.

Procedure

  1. If you are upgrading to 7.6.04 or later, to map the selection value, run the following UPDATE SQL statement on the production system before you begin the DDM:

    ctm_app_pref_update.sql
  2. From the <MigratorInstallDirectory>\DeltaDataMigration\Utilities\pre_DDM folder, execute the following SQL statements on the production system (the UPDATE SQL statement is the same as the one used in the upgrade) to update the delta records that have the issue.
    During an upgrade, the installer updates other records by calling the UPDATE SQL statement through a filter.
    • SELECT–The SELECT SQL statement will give you the number of records to update.
    • UPDATE–The UPDATE SQL statement will fix the mapping.

  3. Work with your database administrator to execute these ANSI SQL scripts on the database.

    Note: These issues do not result in loss of functionality. The fixes are required to ensure that the DDM does not produce errors.

  4. Follow the instructions as given in the <MigratorInstallDirectory>\DeltaDataMigration\Utilities\pre_DDM\Readme_for_Ctm_App_Pref_Sql_Fix.txt file to apply the SQL fixes.

 

Precheck 5: Update negative values on fields in ITSM forms

Certain data will not be migrated on the following forms:

  • TMS:Task — The Seconds_before_Time_Out hidden field is designed to accept values between 0 and 2147483647. Occasionally, this field can be set inappropriately to negative values through a workflow. When BMC Remedy Migrator uses the BMC Remedy AR System API to conduct its activities, the field definition violations are not allowed. This issue results in errors and data not being migrated.
  • TMS:Summary — The Task or Task Group Status field accepts values between 1000 and 7000. Occasionally, this field can be set inappropriately to values of 0 and 1 through a workflow. When BMC Remedy Migrator uses the BMC Remedy AR System API to conduct its activities, the field definition violations are not allowed. This issue results in errors and data not being migrated.
  • CTM:People — The Open Tasks field is designed to accept values between 0 and 2147483647. Occasionally, this field can be set inappropriately to negative values through a workflow. When BMC Remedy Migrator uses the BMC Remedy AR System API to conduct its activities, the field definition violations are not allowed. This issue results in errors and data not being migrated.

Note

These issues do not result in loss of functionality. The fixes are required to ensure that DDM does not produce errors.

Applicable scenario

 Data not migrated from specific forms due to negative values.

Applicable version

 All version prior to BMC Remedy ITSM 8.0.

You must perform this precheck before every DDM run.

Procedure

Work with your database administrator to execute the following ANSI SQL scripts on the database:

  1. From <MigratorInstallDirectory>\DeltaDataMigration\Utilities\pre_DDMfolder, extract the tms_select.sql and tms_update.sql scripts.
  2. Execute the tms_select.sql script.

  3. If records are reported or found, run the tms_update.sql script to correct the data.

    Note: If you are running on a DB2 database, replace the corresponding T table names in the form names in tms_update.sql script.
     

Precheck 6: Update the data migration mapping file if you modified a field ID before or during an upgrade

If you modified an existing field ID before or during an upgrade, you must update the data migration mapping file to reflect those changes.

Applicable scenario

Updated Field ID before the upgrade process started.

Applicable version

 All versions.

Procedure

  1. In the packages folder, open the custom package folder.
  2. Open the instruction file for which you will update form mapping information
    If you have more than one instruction file, open the file that contains the form for which delta data mapping is available.
  3. Create a mapping (.arm) file and map the custom source field ID to the destination field ID (which has a new ID after you run the ARCHGID utility).
    The following image shows an example of a mapping file:

    cmdb_map_file_contents.gif
  4. Add the mapping file name to the form reference in the instruction file, as shown in the following example:

    cmdb_field_mappings.gif

Precheck 7: BMC Process Designer is installed

If you are migrating BMC Process Designer data from version 8.3.03, perform the following steps:

  1. On the SHARE:Application_Properties form of the source server, import the SHARE_Application_Properties_PD8303.arx file  by using the Data Import tool
  2. Update the package files for BMC Remedy ITSM and BMC Service Request Management.
  3. Update the package file for BMC Service Request Management.


Applicable scenario              

If BMC Process Designer is installed

Applicable version

8.3.03

Procedure

  1. Perform the following steps to import the share application properties file:
    1. On the source server, Open the Data Import Tool 
    2. Navigate to <installation directory>\Program Files\BMC Software\ARSystem\dataimporttool
    3. Click File > New Mapping.
    4. Select the Source Data File located at <installation directory>\Program Files\BMC Software\Migrator\migrator\DeltaDataMigration\Utilities\pre_DDM\PD8303\SHARE_Application_Properties_PD8303.arx
    5. Select the Target server.
    6. Select the Target Form name as SHARE:Application_Properties.
    7. Click Auto Map.
    8. Start import. 
    9. Verify if the records are imported.
      Typically, you might view up to seven records imported.
  2. If you have installed BMC Process Designer with BMC Remedy ITSM, update the following package files:
    1. Open the following file: 
      <installation directory>\Program Files\BMC Software\Migrator\migrator\DeltaDataMigration\Packages\ITSM\<version>\ITSM_SD_Package.xml

    2. Update the file as shown in the example:

      <instructions file="Remedy_Incident_Management.xml" type="all" command="migrate" enabled="false"/>
      <instructions file="Remedy_Incident_Management_PD8303.xml" type="all" command="migrate" enabled="true"/>
      <instructions file="Remedy_Problem_Management.xml" type="all" command="migrate" enabled="false"/>
      <instructions file="Remedy_Problem_Management_PD8303.xml" type="all" command="migrate" enabled="true"/>
    3. Save the file.
    4. Open the following file: <installation directory>\Program Files\BMC Software\Migrator\migrator\DeltaDataMigration\Packages\ITSM\<version>\ITSM_Fnd_Package.xml.

    5. Update the file as shown in the following example:

       

      <instructions file="Remedy_Task_Management.xml" type="all" command="migrate" enabled="false"/>
      <instructions file="Remedy_Task_Management_PD8303.xml" type="all" command="migrate" enabled="true"/>
    6. Save the file.
    7. Open the following file: <installation directory>\Program Files\BMC Software\Migrator\migrator\DeltaDataMigration\Packages\ITSM\<version>\ITSM_Change_Package.xml.

    8. Update the file as shown in the following example:

      <instructions file="Remedy_Change_Management.xml" type="all" command="migrate" enabled="false"/>
      <instructions file="Remedy_Change_Management_PD8303.xml" type="all" command="migrate" enabled="true"/>
  3. If you have installed BMC Process Designer with BMC Service Request Management, update the following package files:
    1. Open the following file <installation directory>\Program Files\BMC Software\Migrator\migrator\DeltaDataMigration\Package\SRM\<version>\SRM_Package.xml

    2. Update the file as shown in the example:

      <instructions file="Remedy_Service_Request_Management.xml" type="all" command="migrate" enabled="false"/>
      <instructions file="Remedy_Service_Request_Management_PD8303.xml" type="all" command="migrate" enabled="true"/>
      <instructions file="Remedy_Service_Request_and_Catalog_System.xml" type="all" command="migrate" enabled="false"/>
      <instructions file="Remedy_Service_Request_and_Catalog_System_PD8303.xml" type="all" command="migrate" enabled="true"/>
    3. Save the file.

 

Where to go from here

Next task

Up to process

To return to the delta data migration process, go to Migrating-delta-data.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*