Database Corruption and Troubleshooting

DATABASE CORRUPTION

Database corruption is when some or all parts of the database objects are unreadable or the integrity is questionable. It may occurs due to internal issues ( software problems in the Notes Client code ) or external issues which effect expected Notes operations.

The corruption could be a result of:

  • Improper operation procedures ( such as improper shutdown )
  • Third party software applications
  • Operating system or network problems
  • Hardware failures

"Future Date” Issue

If the user is complaining that is able to see incoming emails in All Documents, All by Date and All by Person views, but not in the Inbox folder, the mailbox has to be checked for  "future date” problem.

“Future Date” issue is caused by setting the operating system clock to a time in the future. The date selected remains in Notes, even though it is reset by the operating system.

Windows applies a selected date immediately and then reverts, if the Cancel button is clicked.
Lotus Notes does not accept backward time changes at the operating system level while the client is running. ( restart is needed to synchronize Lotus Notes with the operating system settings ).
Any documents created or modified in that state are stamped with future date, which is preventing the incoming mails to be visible under Inbox folder.

Solution:

Create new view and named it FutureDate:Future Date Lotus Notes Issue

  1. Open user’s mailbox database from his/her home mail server
  2. From the main menu select Create –> View…
    View name: FutureDate
    Selection Conditions: By Formula
  3. Paste the future date formula:
    SELECT (@Modified > @Today) | (@Created > @Today)
  4. Click OK

 

 

 

 

LN Client must be restarted after the correction. Then open the mail file from the user’s home mail server and go to the FutureDate view, select all the documents in this view / Ctrl-A /. Ctrl+X, then Ctrl+V. The documents will be cut and pasted back with the current date as modified. After this action no document should be visible in that view.
 


       Corrupted Local Replica

  Before recreating local replica from the server ( in some cases the mailbox database is too large and it will take long time to be recreated from the server ) there are few steps that you have to do first:

  If you think that the local replica is corrupted ( in case that everything is working as expected on server replica and you are sure  that the problem persists only on local replica ):

  1. Go to command prompt and navigate to Lotus Notes installation folder ( generally C:\Program Files\notes )
  2. Use these tree executables in order to fix the corrupted database:

  nfixup.exe, ncompact.exe, nupdall.exe

Syntax Examples:Fixup Compact Updall

  •   nfixup -J -F [database name]

  [J] Fixup transaction-logged databases

  [F] Scan all documents

  •  ncompact -c -i [database name]

  [c] Copy-style

  [i] Ignore errors and proceed

  • nupdall -R [database name]

  [R] Rebuild all used views
 

Note: Nfixup without any options will perform fixup to all Notes databases in the folder where it was executed.

 

 

       Corrupted Local Replica

Error: "Database is corrupt Cannot allocate space" is received when opening local replica.

Resolution:

  1. Remove the database from the workspace.
  2. Compact the workspace. ( right click on free space in Workspace, select Properties and click the Second Tab. Click on Compact ).
  3. Recreate local replica.

Error: “The database is being taken offline and cannot be opened”

  • While opening the mailbox database:

       The error message is usually caused by a Lotus Domino task running on a database during the time you try to open it. Some Domino tasks ( e.g. fixup -o , compact -c ) do NOT allow access to a database while they are running. The duration where the database is unavailable should not be significant.

  •  When launching the Lotus Notes client:

  On the second attempt, however, Notes will launch successfully. The issue continues, resulting in the customer having a successful launch with every other attempt.

     

Solution:

      After closing the Notes Client and deleting the local cache.ndk, the customer was able to repeatedly launch Notes without a problem.

 

Share This Post

Recent Articles

Leave a Reply

© 2014 IBM Lotus Tech Blog. All rights reserved. Site Admin · Entries RSS · Comments RSS
Powered by WordPress · Designed by Theme Junkie