Troubleshooting Import – Missing data when importing from JDBC source via MID server
This issue is related to loading data from an external database (JDBC import) via the MID server. After the load, when you check the import set, the number of the records loaded is lower than what you expected.
- Import does not complete
- Import stopped in the middle
- Import says complete, but not all data is present
Import set did not process all records from the ECC queue. Looking at the import log, you might be able to find the error that is causing the import process to stop processing data. One possiblity is that you failed to parse the data (XML format) message that causes the processor to stop processing data. The other possibility is that you run an import via a MID server that is part of a cluster.
Here are the possible cause possibilities:
- Data set is very large and sending the data in the payload versus the attachment causes a parsing failure.
- Netcool integration (if activated on the instance) might send events that our processor mistakenly identifies as part of the result set, then tries to parse and fails.
- MID server is part of a cluster, so some of the results are processed by different MID servers.
|Note: Import process does not support import via a MID server that is part of a cluster.|
To solve the issue with the large data set:
- If it is not already installed, install the Integration - JDBC plugin (ID: com.snc.integration.jdbc).
- Go to the data source that is currently failing and find the field, Jdbcprobe result set rows. (You may need to add the field to the form or list.)
- Set the value to 1000. (By default, the value is 200.)
- Start the import again.
- Shut down the Netcool integration or upgrade to CP5 and up, which includes the fix for this issue.
To solve the issue with the MID in cluster:
- Remove the MID server from the cluster or install another MID server that is dedicated for the import.