Troubleshooting data import issues by using custom delimiter

BMC Helix Data Manager flags potential migration issues when there are errors in parsing the records when there is a delimiter present in the record. During import, this delimiter splits the record as an additional field and gives error.

Symptom

You may get the following error message after data import:

Fatal error processing T file at line 72559 with requestId of 1234 
java.lang.NumberFormatException: For input string: "abcd" 
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) ~[?:?] 
at java.lang.Integer.parseInt(Integer.java:652) ~[?:?] at java.lang.Integer.valueOf(Integer.java:983) ~[?:?]

Resolution

If you encounter this error or any extra fields created in the target system after importing data, use a custom delimiter and run the export migration job again on the forms with these errors. We recommend you to use a custom delimiter with a lower memory value. For example, you can use :hdm:.

For running the export migration job by using a custom delimiter, perform the steps in the topic Running-an-export-migration-job and set the Delimiter field value to a custom value.