Review the source and target system configurations.

1. Review the source and target system configurations by performing the following tasks:
   1. Log in to BMC Helix Data Manager.
   2. On the System Configuration page, select Source or Target System Configuration.
   3. Under Action, select Test System Connectivity.
      
      

For more information, see Registering-source-and-target-systems.

2. Review the defined file system connections by performing the following tasks:

1. 
   
   1. Confirm that the default connection path is correct.
      1. Log in to BMC Helix Data Manager.
      2. Select Configuration > Configure File System connections.
         Then, select Defined File Systems > Review Path.
   2. Confirm that the Test Write Data and Test Read Data & Files are successful.
      1. Under Configure, select the correct Source and Target Systems > Configure Connections.
      2. Validate Test Write Data and Test Read Data & Files.

For more information, see Validating-file-system-configuration.

3. Review the discovered Data Dictionary from the source and target system, and make sure that the Forms & Fields tab shows a valid list of forms (Base, Custom, Overlay).

1. 
   
   1. Log in to BMC Helix Data Manager.
   2. From Discovery & Analysis, select the Discovered Dictionary.
      
       
      
      
   3. Under Forms & Fields, select the correctly labeled and dated Data Dictionary and review the Custom, Base, and Overlay forms list.
      

 For more information, see Discovering-data-dictionaries.

4. To review if the version of the Migration Pack that is imported and published is valid:

1. 
   
   1. Log in to BMC Helix Data Manager.
   2. Select Data Migration > Migration Packs.
   3. Confirm that the Migration Pack Name and its Status are correct.
   4. Review the Included Forms tab to confirm that the correct form list is displayed.
      

BMC Helix Data Manager Logs are enabled under the BMC Helix Data Manager directory on both source and target systems.
Find the logs in the following path:
\BMC Software Install Directory\Helix Data Manager\Engine\log\hdm.log.

Check the hdm.log to verify whether the Date and Time details of when the activity was carried out are recorded.    

Detail:  The import fails on a specific form with a permission denied error.

Error:

Error while executing SQL org.postgresql.util.PSQLException:ERROR:

To view the error:

1. Click the Error tab to see the primary error (Unable to import T table data).
2. Click the Advanced tab for additional details on the error.

1. With the help of a database administrator, get complete access to the BMC Helix Data Manager database user for the specific table for which the error is occurring.
2. If you encounter too many tables with access issues, drop and recreate the database integration step.
   
   
   
   or

If you do not have access to run the database integration from BMC Helix Data Manager, provide the database administrator with the manual integration scripts found at this location. 

After importing the data, if you encounter an error or observe that the target system has extra fields, use a custom delimiter and rerun the export migration job on the forms.

• Review the data in the specified field on the source system to determine if it is needed. If the data is needed, increase the field length on the target system by creating an overlay; otherwise, ignore the error.

Use the following query on the staging table or the source table to find the maximum length of a field and alter the length of that column on the target system.

<column_name> is the column name whose maximum length you want to find.

<form_name> is the name of the form where the column is present.

1. Under Errors & Warnings, select a migration job for data import.
2. Click the Error tab to see the primary error (Unable to import T table data).
   

1. Click the Advanced tab to get more information about the error.
   

• Duplicate data exists between the source system and the target system.
  For example, the custom Group ID in the source system matches with the new out-of-the-box Group ID in the target system. This match causes an error as both the IDs must be unique but they are the same.
  For more details about the custom Group ID range to be used, see Creating and managing access control groups.
  
  
• Out-of-the-box data with conflicting Request IDs exists on the source system.
  This use case applies if the source system data is imported using the Data Import Tool.
  A unique key violation occurs because the user might have selected the following options on the Data Import Tool:
  • Handle Duplicate Request IDs By field with the value Generate New ID for All Records.
  • Match Duplicate Request By field with the value Request ID.

• The issue can occur when you change the database from case-sensitive to case-insensitive mode. This use case applies when moving from Oracle case-sensitive to Oracle case-insensitive mode or when moving from Oracle database to Microsoft SQL Server or PostgreSQL database, resulting in a unique key violation.
  For Oracle database considerations, see the AR System case-insensitive option for Oracle section in Database considerations for Oracle.

  
  

Detail: Data Mapping errors can directly affect the import of specific form data. Therefore, resolving any Data Mapping errors and warnings identified after configuring the Migration Pack is necessary.

The Data Mapping errors are as follows:

Review the different Data Mapping Status to understand the errors:

1. Target Field not mapped:  This issue occurs when the corresponding field is unavailable in the source system.
   In this case, generate a new field mapping or ignore it if not required.
   
   
   
2. Source Field not mapped: This issue occurs when no corresponding field is available in the target system.
   In this case, generate a new field on the target system or ignore it if not required.
   
   
   
3. Target Field required:  This status confirms that the Target Field is defined as Required, but the Source Field is Optional.
   In this case, manage the null value or set it to the default value.
   
   
4. Enum warning: Review the data on the specified field on the source system and validate whether the data is required or ignore it if not required.
   

Additional steps:

• Re-run the Data Dictionary again if any changes are made in the source or target system for the HDM tool to read the changes.
• If new data is discovered, you must use the latest version to create a copy of the Migration Pack to include the changes while analyzing the Data Mapping.

1. Locate and fix the data in the source system.

2. Locate the form and run the following query for negative values:

   SELECT * from <form_name> where <field_name> <0 or<field_name>>2147483647

   <form_name> is the name of the affected form.
   <field_name> is the name of the time stamp field that needs to be checked.

3. If the data is fixed in the source, perform the data export and import again.
   Important: For an Integer out-of-range scenario, you must locate the field or the column where the out-of-range error occurs.
4. Compare the specific field properties in the source system and the target system to validate whether there are any differences.
5. If the data cannot be fixed on the source, raise a support case to work with BMC R&D or Support to resolve the issue.