Tuesday, November 26, 2013

Remove Notes file truncation error using adroit recovery tool

Lotus Notes is an efficient email client application developed by widely popular organization known as IBM. The Lotus Notes client application is in collaboration with Domino Server. The interesting aspect of Lotus Notes and Domino Server is that they both share .nsf file formatting. This feature facilitates the user as the hectic and confusing task of file management is quite simple using the respective Client-Server application.
The Domino Server is also known as Lotus Enterprise Integrator administrator database. The application creates forms and various activities. The objective of the activity is to define the protocol for collaborating enterprise data and Lotus Domino Server. The program is related to alien data source and handle data as per the instruction that are mentioned in the activity. Inorder to experience a successful Lotus Enterprise Integrator activity, the collaboration of Notes data is must. In case the Notes file gets malfunctioned then user may encounter following error message.      

“Error: File truncated - file may have been damaged. Connector 'Connector_name(B)', Method -Fetch- (265)"
On  continuous trying, finally user will confront with complex and detailed error message.
"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)"
On opening the specific corrupt Notes file another error message is shown 
"Lotus Notes ! Server Error: File truncated - file may have been damaged."

The error message occurred because the specific Notes file is incomplete. The incomplete means, the end of the file is missing hence cannot be read. Generally such kind of file truncation takes place due to the malfunctioned part of hard drive

  • Run command Fixup  (It will verify all the files in the database. ).
  • Create a new database replacing the old damaged NSF file. 
  • Make use of backup data instead of corrupt one.
  • Permanently delete the corrupt NSF file.
The above mentioned steps seems to be quite simple and easy to run. But the success rate of such trouble shooting depends upon the severity of problem. Sometimes the situation becomes much worse as the user performs incorrect recovery steps. It happens with most of the users because Lotus Notes is very complex application. In that case the only best and recommended option left with the user is to go for third party NSF recovery tool.
Stellar Phoenix Lotus Notes Recovery tool is one the best option for the aforementioned situation. The tool is loaded with wide range of features that makes the recovery task extremely simple. The free demo version of the tool can be downloaded from the respective website.