Monday, May 31, 2010

Resolving “ The specified database lookup generated..” Lotus Notes Error

IBM Lotus Notes is a popular email client and personal information manager, which stores all your significant data in a database, called NSF (Notes Storage File). It stores all the data in the form of columns and rows. The meta database about Lotus Notes database column is stored in a structure, known as DBColumn. You can update the information in DBColumn, as per your requirements, using @DBColumn and @DB lookups commands. However, sometimes, you may come across critical situations of database corruption and data loss if you incorrectly update the database columns. In such cases, you need Lotus Notes Recovery software.

In a practical scenario, you may come across the below error message when you try to update information in the Lotus Notes database column:

“The specified database lookup generated more than 65,000 bytes of results, which is too large to return in this context.”

After the above error message, the database column can not be updated and you can not even access the particular table of your NSF database. In such situations, your valuable data become inaccessible. To extract precious data from the Lotus Notes database, you need to find out the reason behind the problem and fix it using NSF File Recovery solutions.

Cause

You may come across this problem due to any of the following reasons:

(1) You run @DBColumn command on your Lotus Notes database and it returns more than 42,000 bytes of information.

(2) The size of database column is exceeding 65.000 bytes.

(3) The Lotus Notes database is damaged and the application can not read it. Corruption can be caused by numerous reasons, such as application malfunction, virus infection, file system errors, operating system problems, unexpected system shutdown, and user errors.

Resolution

Try out any of the below methods to fix this problem and Repair Lotus Notes database:

(1) Decrease the size of database columns.

(2) Restore Lotus Notes database from the most recent backup.

(3) Repair and restore damaged database using third-party applications.

The Lotus Notes recovery software are particularly designed to methodically scan entire database using powerful scanning techniques and extract all inaccessible data from it. They do not demand sound and prior technical skills to repair the damaged database as of their simple and interactive graphical user interface.

Stellar Phoenix Lotus Notes Recovery is a powerful, yet easy to use application for assured recovery of damaged NSF file. This NSF File Recovery tool is able to display the preview of headers of five items per folder. In addition, this tool provides the Live Update option to get the latest definitions of the software from the Internet. It supports Lotus Notes 6.x and 7.x versions. It is compatible with Windows 7, Vista, Server 2003, XP, and Server 2000.

Friday, May 28, 2010

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. Let's say, you try to perform an LEI activity from your Lotus Notes client to DB2, but the operation doesn't 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. Know more about tool - http://www.stellarservertools.com/lotus-notes-recovery.php