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.

Server configuration adjustments

Before running the Delta Data Migration Tool, perform the following server configuration adjustments.

Adjustments for the destination server

Note

Leave the configuration as is until after you complete the delta data migration.

Make the following adjustments on the destination server:

  • Set the Max Entries Returned by GetList parameter to 0 on the Configuration tab to cover all delta data in the forms. After completing the delta data migration process, be sure to set this parameter back to the original value.
  • Disable the Distributed Server Option (DSO) on all application servers.
  • Disable escalations on all application servers.
  • Disable all database triggers within the BMC Remedy AR System schema. Work with your database administrator to disable the triggers.
  • To help increase the delta data migration performance, configure the following items on the the Server Information page of the AR System Administration Console. After running the delta data migration, you should set all of these items back to their values from before you make these changes.
    • Select the Disable FTS Indexer and Disable Full Text Searching check boxes on the FTS tab.
    • Unselect the Localize Server check box on the Advanced tab. If you leave this box selected, the migration tool looks for localized data twice, which has a significant impact on system performance.
  • Set the isolation level for MS SQL Server on the source and destination server databases.  Otherwise, data in forms is not migrated successfully and you might see an error like this in the HTML log files:
    11/22/2011 17:51:07 1612 *ERROR* Migrations 17:51:07 : An Error Occured with Data 'NTE:Notifier Log' 11/22/2011
    
    17:51:07 1612 *ERROR* Migrations 17:51:07 : [4][The SQL database operation failed. The ROLLBACK TRANSACTION request has no corresponding BEGIN TRANSACTION. (SQL Server 3903)]
    If it is not already set correctly, set the isolation level for MS SQL Server databases on the source and destination server as follows:
    1. Run the following commands from the SQL Server Management Studio:
      SELECT snapshot_isolation_state FROM sys.databases where name = 'ARSystem'
      SELECT is_read_committed_snapshot_on FROM sys.databases where name = 'ARSystem'
      
    2. If the commands return 0, stop the AR System server, and run the following ALTER commands. (If the AR System server is running, the ALTER commands might take a long time to complete.)
      ALTER DATABASE ARSystem SET ALLOW_SNAPSHOT_ISOLATION ON
      ALTER DATABASE ARSystem SET READ_COMMITTED_SNAPSHOT ON
      

Adjustments for the source server

Note

Leave the configuration as is until after you complete the delta data migration.

For initial runs of the Delta Data Migration Tool, make the following adjustment on the source server. 

  • Set the Max Entries Returned by GetList parameter to 0 on the Configuration tab to cover all delta data in the forms. After completing the delta data migration process, be sure to set this parameter back to the original value.

Optionally, you can make the adjustments listed in the previous section, "Adjustments for the destination server."

For the final run of the Delta Data Migration Tool:

  • Make all of the adjustments listed in the previous section, "Adjustments for the destination server."
  • For forms where the amount of data is large and the total number of records is greater than 1 million, create the index at the database level in the T table, and index field ID 6 (Last Modified Date). An additional index is required for delta data migration purposes.

Important

After the final delta data migration run is completed, you must revert the previous changes back to their original state.

Related topics from the BMC Remedy AR System documentation

Configuring BMC Remedy Distributed Server Option
Definition for Disable Escalations in Setting administrative options

Where to go from here

Resolving issues before performing the migration

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

  1. John Daley

    Where it reads:

    Unselect the Localize Server check box on the Configuration tab. The Delta Data Migration Tool already looks for localized data. if this box is selected during the operation, it will look for localized data twice and slow the system down considerably

    It should read:

    Unselect the Localize Server check box on the Advanced tab. The Delta Data Migration Tool already looks for localized data. if this box is selected during the operation, it will look for localized data twice and slow the system down considerably

    Oct 09, 2013 11:58
    1. Bruce Cane

      Thanks for the suggestion. I made the update.

      Oct 09, 2013 12:29
  2. David Petter

    Please consider adding a step to process the pre_DDM scripts, such as

    ctm_app_pref_select, that are included in the [installpath]\migrator\DeltaDataMigration\Utilities\pre_DDM.  These have been referenced by Product Developers as a critical activity of the DDM process.
    Oct 21, 2013 11:26
    1. Bruce Cane

      Thanks for the suggestion David. Where, specifically, in this topic do you thing the step should fit? 

      Oct 21, 2013 12:09