This documentation supports the 19.02 version of Remedy with Smart IT.

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

Migrating data from 2.0 and earlier schemas

Starting with the Smart IT 18.05 release, Remedy Smart IT and BMC Digital Workplace products are separated. Due to the product separation, when you upgrade to Smart IT 18.05 and onward versions, data from the old schemas must be copied into the new schemas of the Smart IT database if you are upgrading from the earlier version of Smart IT.

The upgrade installer runs the data migration utility automatically. 

Note

The data migration utility should not be run during the business hours of a day.


Run this utility manually in the following scenarios:

  • When performing a fresh installation, and you plan to copy the old data. Ensure that you run this utility before you start using Smart IT.
  • If an error occurs during the data migration.

You can run this utility several times without causing data inconsistencies if the last run of the utility was successful. The utility generates a migration_<yyyymmdd_currenttime>.log file in the logs folder.

The data migration utility runs in the following modes:

  • Mode 0 - Migrate data from old My IT + Smart IT System database schema to new Smart IT System database schema
  • Mode 1 - Migrate data from old My IT + Smart IT Business database schema to new Smart IT Business database schema
  • Mode 2 - Migrate data from old Openfire schema to new Openfire schema. Use this mode only if you are installing a new Openfire server.
  • Mode 3 - Migrate data from Shared AR server forms to ITSM AR server forms. (This mode is for BMC internal purposes only)

To run the data migration utility

  1. Extract the data-migration.zip file located in the C:\Program Files\BMC Software\Smart_IT\SmartITCustomizationUtil folder to a location on the Smart IT server, for example, C:\Utility folder.

  2. At a command prompt, type the following command:
    (Windows): data-migration.bat
    (UNIX): data-migration.sh

    The following example shows the complete command syntax for Mode 0 - to migrate System schema tables with SQL Server as both source and target:

    C:\utility\data-migration.bat -m 0 -sdbv sql 
    -sdbh sourceDb.calbro.com 
    -sdbt 1433 
    -sdbu sa -sdbp password 
    -sdbs MyIT -sdbsc MyITSM_System 
    -tdbv sql -tdbh target.calbro.com -tdbt 1433 
    -tdbu sa -tdbp password
    -tdbs SmartIT 
    -tdbsc SmartIT_System -T 000000000000001

    The following example shows the complete command syntax for Mode 1 to migrate Business Schema tables with SQL server as source and Oracle as target:

    C:\utility\data-migration.bat -m 1 -sdbv sql 
    -sdbh sourceDb.calbro.com -sdbt 1433 
    -sdbu sa -sdbp password 
    -sdbs MyIT -sdbsc MyITSM_Business 
    -tdbv oracle -tdbh target.calbro.com -tdbt 1521 
    -tdbu SmartIT_Business -tdbp password 
    -tdbs ORCL -tdbsc SmartIT_Business -T 000000000000001


    (UNIX): data-migration.sh
    The following example shows the complete command syntax for Mode 0: 

    /tmp/data-migration.sh -m 0 -sdbv sql 
    -sdbh sourceDb.calbro.com 
    -sdbt 1433 
    -sdbu sa -sdbp password 
    -sdbs MyIT -sdbsc MyITSM_System 
    -tdbv sql -tdbh target.calbro.com -tdbt 1433 
    -tdbu sa -tdbp password 
    -tdbs SmartIT -tdbsc SmartIT_System -T 000000000000001

    The data is migrated to the new schemas. Upon successful run, a success message is logged in the log file.

Data migration utility parameters

The following table provides additional information about the utility parameters:

ParameterDescription
mIndicates the migration mode
sdbv  Source DB vendor name
sdbhSource DB host name
sbdt

Source DB TCP Port

sdbi 

Source DB instance name (if MS SQL server). This needs to be passed only if the named instance is used in SQL server.

sdbu  Source DB Admin User
sdbp  

Source DB Admin Password

sdbs  

Source DB Name in case of SQL Server OR SID/Service name in case of Oracle

sdbsc 

Source DB Schema Name

tdbv  

Target DB vendor name

tdbhTarget DB host name
tbdt

Target DB TCP Port

tdbi Target DB instance name (if MS SQL server). This needs to be passed only if the named instance is used in SQL server.
tdbu  Target DB Admin User
tdbp  

Target DB Admin Password

tdbs  

Target DB Name in case of SQL Server OR SID/Service name in case of Oracle

tdbsc 

Target DB Schema Name

TTenant ID
Parameters for running the utility in Mode 3 (for BMC internal purposes only)
garhShared AR host name
gartShared AR port number
garuShared AR admin user
garpShared AR admin password
iarhITSM AR host name
iart  ITSM AR port number
iaru  ITSM AR admin user
iarp  ITSM AR admin password

Troubleshooting data migration issues

The following table describes the resolution to errors that may occur during data migration:

ErrorResolution
Out of Memory error

Open the data-migration.bat/data-migration.sh file and change the value of the JVM Heap size parameter from

-Xmx2048m to -Xmx4096 or -Xmx8192 (depending upon your system memory)

Tenant table does not exists error

This error occurs due to a mismatch between the schema name and the mode in which you are running the utility. For example, you want to run the utility in Mode 0, but in the command you specified the name of the schema as Business instead of System.

Ensure that you use the correct schema name for a mode as follows:

  • Mode 0 for migrating System schema
  • Mode 1 for migrating Business schema
Was this page helpful? Yes No Submitting... Thank you

Comments