Troubleshooting issues with importing data
The following table describes the troubleshooting tips that you can use to resolve issues that you might face when importing data.
|Error or issue||Applies to the Pentaho package for||Description or procedure|
|Viewing logs of the import jobs||All||Log files are created in the folder where you have saved the KJB files. Success and failure rows files are also created in the same folder. If a failure occurs, the error code and its description are provided in the failure row file. You can also use the failure row file to import data to Salesforce.|
|Not all records are imported||All||Delete the delta time stamp file of the job that you ran, and run the job again.|
|An "out of memory" error occurs||All|
While importing a large number of records, if you get the OutofMemoryError or Java heap size error, increase the heap size in the Spoon.bat file.
|A "too many script statements" error occurs||All||When you run an import, if you receive "Too many script statements" as an onscreen Apex error message or in an email, reduce the batch size by 10 in the Batch Size field in the Settings section on the Salesforce Upsert window.|
|Importing data by using the failure rows file|
A failure row file is a text file that is saved in the folder where you have saved your KJB files. Perform the necessary steps to remove the error provided for the failure rows in the failure rows file, and then import the data by using the following steps.
The following Pentaho packages provide a sample job file in the FailureRowsInput folder. You can use this sample job file as a base to create transformation files for importing data from the failure rows file to the Salesforce organization.
In the following steps, it is assumed that you are using the sample KTR file provided by BMC.
To import data from the failure rows file
|Failed in writeToSalesForce: java.lang.IllegalArgumentException: The char '0x0' after 'Print' is not a valid XML character||All||Some unicode characters that cannot be parsed by XML parser are present in the any of the mapped BMC Atrium CMDB fields. Either delete these characters in data or delete the mapping of such BMC Atrium CMDB fields.|
|Unable to query Salesforce||All||Check your Salesforce organization credentials in the Salesforce Upsert and Salesforce Input(CMDB_Classes) steps.|
|The job does not appear in Atrium Integrator.||BMC Atrium CMDB||Ensure that you have saved your KTR and KJB files in a folder in Atrium Integrator.|
|Error setting value #2 [ARDelta_1 Integer] on prepared statement (Integer)||BMC Atrium CMDB||This error is generated if multiple records are created in the BMC Remedy AR System NGIE:Delta form for the running transformation. Delete the additional ARDelta entries that are created for the error transformation file by deleting the records. To find the duplicate records for a transformation file, open the NGIE:Delta form in BMC Remedy AR System. In the TransName field, enter the transformation file name, and click Search.|
|Did not find Remedy Application Service password for server<server name> in UDM:RAppPassword Form on server <server name>||BMC Atrium CMDB||Check your Atrium Server Connection credentials in the ARInput step.|
|'Oracle Database Server 10g Release 2' is not valid for the type xsd: <data type >||BMC Atrium CMDB||Check the data type of the mapped fields in the Salesforce Upsert step.|