Skip to Content
Information
Unsupported content 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.

Preparing for delta data migration

After the upgrade is complete and customizations are re-applied, the environment is ready for delta data migration. Perform the following procedures to prepare your destination server to migrate the delta data:

To disable DSO

The Distributed Server Option (DSO) must be disabled on all application servers before conducting the delta data migration. For more information, see Administering BMC Remedy DSO for BMC Remedy AR System and the BMC Remedy Distributed Server Option Guide for BMC Remedy AR System 7.7 on the Customer Support website.

To disable escalations

Escalations must be disabled on all application servers before conducting the delta data migration. For more information, see the BMC Remedy Action Request System 7.7.00 Configuring on the Customer Support website.

To disable database triggers

All database triggers within the ARSystem schema must be disabled. Work with your database administrator to disable the triggers.

To fix backend data on the production server

The following known issues must be corrected by using SQL scripts on the production server before running the BMC Remedy Migrator scripts.

  • On the TMS:Task form, 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 workflow. When BMC Remedy Migrator utilizes the BMC Remedy AR System API to conduct its activities, the field definition violations are not allowed. This results in errors and data not being migrated.
  • On the TMS:Summary data form, 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 workflow. When BMC Remedy Migrator utilizes the BMC Remedy AR System API to conduct its activities, the field definition violations are not allowed. This results in errors and data not being migrated.
  • On the CTM:People form, the Open Tasks field is designed to accept values between 0 and 2147483647. Occasionally, this field can be set inappropriately to negative values through workflow. When BMC Remedy Migrator utilizes the BMC Remedy AR System API to conduct its activities, the field definition violations are not allowed. This results in errors and data not being migrated.

Solution

  1. From the package zip file , extract the tms_select.sql and tms_update.sql scripts.
  2. Execute the tms_select.sql script.
  3. If records are reported or found, execute the tms_update.sql script to correct the data.

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

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

 

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

BMC Cloud Lifecycle Management 3.1