Sometimes files may get corrupted in transit when LogLogic LMI is collecting them. If this occurs it is due to environmental issues with the network and, because of that, the likelihood of this occurring is extremely rare because modern networks are much more reliable and robust. There is a greater likelihood, but still low, of files getting corrupted on the source systems before LMI can collect them.

The exact consequence of files getting corrupted cannot be described because corruption can occur in different ways with varying magnitudes. Sometimes a file cannot be opened at all while in other cases only some text in the file may become corrupted leaving the vast majority of the file unaffected.

Generally speaking, as long as the file can still be opened then LogLogic LMI will process as much as it can. If the file cannot be opened then nothing can be processed.

If you think you have a corrupted file that needs processing then contact TIBCO Support for assistance. The file can be reviewed to determine the level of corruption and an assessment can be provided to gauge whether it can still be processed.

Note that binary data is not corruption even though it isn't human-readable however, LogLogic LMI can only process ASCII-based data.

This article discusses the repercussions of files getting corrupted before or during transit when using LogLogic LMI.