Resolving Error: File truncated - file may have been damaged Error

Resolving Error: File truncated - file may have been damaged Error

Resolving Error: File truncated - file may have been damaged Error

Accessing enterprise data stored on non-Lotus Notes Domino applications is easy with IBM LEI (Lotus Enterprise Integrator). This gives you the leverage of accessing data placed on various platforms while also using different applications. But for an LEI activity to complete successfully, the integrity of Notes document is a must. If a Notes document gets corrupt for some reasons, LEI activity can fail giving some errors on screen. Such situations further require you to use Lotus Notes Recovery softwares. As discussed, one of the common reason for LEI failover is Notes database corruption. To specify this problem, here is a real-time example. Lets say, you try to perform an LEI activity from your Lotus Notes client to DB2, but the operation doesnt proceed as expected and the following error message is received: "Error: File truncated - file may have been damaged. Connector Connector_name(B), Method -Fetch- (265)" On retrying the same activity, the below mentioned error is received: "Error: [IBM][CLI Driver][DB2/6000] SQL0206N "SP1720248" is not a column in an inserted table, updated table, or any table identified in a FROM clause or is not a valid transition variable for the subject table of a trigger. SQLSTATE=42703, Activity_Connector_Name, Method -Select- (-206)" Further, when you try to open the problematic Notes document in Lotus Notes database manually, another error is encountered: "Lotus Notes ! Server Error: File truncated - file may have been damaged." When this occurs, you observe that the affected document contains SP1720248 data in one of its fields. Usually, this happens when a bad sector or block of hard drive has corrupted the Notes document. User Action Try one of the suitable solutions:
(1) If possible, delete the damaged document.
(2) Execute fixup command to Repair Lotus Notes database.
(3) Make a new database replica and use it to replace the corrupted database. Since the corrupted document has not been replicated, this will be recreated when you will again perform the LEI activity.
(4) Use your previous good backup to restore the Notes database.
(5) Use a third-party tool to Repair NSF File.
Stellar Phoenix Lotus Notes Recovery is a high-end tool with proven scanning algorithms that can repair your corrupted Lotus Notes database with just simple clicks. This Lotus Notes Recovery software can repair & restore Lotus Notes database that has been created with Lotus Notes 6.x or Lotus Notes 7.x. It can restore Lotus Notes e-mails, attachments, calendar entries, journals, etc. at a safe, user-defined location. About The Author: Mohit Mathur has passion for writing Technical articles. He is right now writing articles related to products like Repair Lotus Notes & PST Password Recovery and has now become a professional writer. For more information please visit:- http://www.lotus-notes-recovery.com/