Command to Compact NSF File from Lotus Domino Console

To Compact Notes Database follow the below steps :

Run these commands in Lotus Domino Console

Step 1: Run the command

load Fixup -f datbase.nsf                     (Use path like, mail\user1.nsf)

Wait for completion of this step.              ( Database Fixup: Shutdown )

Step 2: Run the command

load Compact -B Database.nsf             (Use path like, mail\user1.nsf)

Wait for completion of this step.                (Database compactor process shutdown)

Step 3: Run the command

load Compact -c Database.nsf                (Use path like, mail\user1.nsf)

 Wait for completion of this step.                (Database compactor process shutdown) 


Note : These steps will also helps if Notes database size get increased abnormally.
 

Database is damaged and can't be repaired (UNID index)" when move files to a new server

Problem

The error: "Database is damaged and can't be repaired (UNID index)" occurs after moving files from one version of Domino to another. The files cannot be opened.

Symptom

The following message appears and the file cannot be opened: "Database is damaged and can't be repaired (UNID index)".

Cause

After moving mail files via OS from Domino 851 FP1 on W2003 to a new machine with Domino 853 FP2 on W2008 64bit, many mail files could not be opened. No corruption or problems were reported in the original version of Domino. After the move, the error "Database is damaged and can't be repaired (UNID index)" occurred.

Environment

Domino 851 FP1 on W2003;
Domino 853 FP2 on W2008 64bit

Diagnosing the problem

The error "Database is damaged and can't be repaired (UNID index)" occurs after moving files from one version of Domino to another. The files cannot be opened.

Resolving the problem

In one case, running maintenance prior to moving the mail files resolved the problem. For example:

updall -R -X
fixup -F
compact -c -i

This is the same maintenance that is recommended in the 'Domino Server Upgrade' section of Technote #7006573, Administrator Guide for Domino Server maintenance.

In other cases, running ''fixup -b' or 'fixup -b -J' (if transactional logging enabled) resolved the problem. Fixup -b rebuilds the UNID index.

Ref : http://www-01.ibm.com/support/docview.wss?uid=swg21611794&myns=swglotus&mynp=OCSSKTMJ&mync=R

Server crash on HTTP after upgrade to 8.5.3 FP2

Problem

Server crash on http after upgrade to 853FP2

Cause

The cause looks to be issue with the JVM folder under Domino program directory.

Environment

Domino 8.5.3 FP2; Windows 2003

Diagnosing the problem

Server crashed on HTTP task after upgrade to 853FP2 from the existing 852 with the below stack. The issue seems to be with HTTP JVM files unable to load properly after the upgrade.
############################################################
### FATAL THREAD 1/9 [ nHTTP: 0bf0: 0bf4]
### FP=0x000af200, PC=0x7ff0925b, SP=0x000af198
### stkbase=000b0000, total stksize=393216, used stksize=3688
### EAX=0x00000000, EBX=0x60f97e68, ECX=0x00000000, EDX=0x00000000
### ESI=0x0017d000, EDI=0x00000000, CS=0x0000001b, SS=0x00000023
### DS=0x00000023, ES=0x00000023, FS=0x0000003b, GS=0x00000000
Flags=0x00210206
Exception code: c0000005 (ACCESS_VIOLATION)
############################################################
@[ 1] 0x7ff0925b j9vm24.getMethodOrFieldID+107
(17d000,0,60f97e74,60f97e68) @jnicsup.c(1723)
@[ 2] 0x603cb0fd nnotes.CSocket::GlobalInit+45
(17d000,17d000,af7a8,60d9b97c)
@[ 3] 0x603cb27d nnotes.CWEBGlobalInit+13
(17d000,17d000,60d9ca12,606b1070)
@[ 4] 0x60d9b97c nnotes.setupWS+12 (606b1070,2,af83c,0)
@[ 5] 0x60d9cef7 nnotes.JavaMachine::GetJavaMachine+503
(606b1070,9c2c018,0,2)
@[ 6] 0x60d997e9 nnotes.JavaSession::GetJavaVM+25
(606b1070,2,af83c,2a769b4)
@[ 7] 0x606b13ae nnotes.AgentJavaVMSub+46 (af834,2,100570e9,3f50c4)
@[ 8] 0x10010f2d nhttpstack.HTProcessExtContainer::Initialize+285
(1,3f50c4,1004c5a8,1000ccbf)
@[ 9] 0x1000b4f9 nhttpstack.HTControlBlock::InitializeExtensions+41
(1,3f50c4,1,1)
@[10] 0x1001c197 nhttpstack.HTAddInMain@12+631 (400000,1,3f50c4)
@[11] 0x0040103f nHTTP.NotesMain@8+47 (1,400000)
@[12] 0x00401174 nHTTP.notes_main+212 (0,0)
@[13] 0x00401066 nHTTP.main+22 (1,e61af0)
@[14] 0x0040134d nHTTP.mainCRTStartup+323 (0,0)
[15] 0x77e6f23b kernel32.ProcessIdToSessionId+521 (40120a,0)


The following errors were seen in the console log:

[0BF0:0002-0BF4] 08/22/2012 08:25:30 PM HTTP JVM: Exception in thread "main"
[0BF0:0002-0BF4] 08/22/2012 08:25:30 PM JVM: The lotus/domino/websvc/client/Service class could not be loaded.
[0BF0:0002-0BF4] 08/22/2012 08:25:30 PM JVM: The lotus/domino/axis/transport/http/NotesSocket class could not be loaded.

Resolving the problem

Deleting the JVM folder and re-running the Domino install resolved the issue.

Unable to set password history to 0 when "Check password on Notes id file" is enabled via policy

Problem

You have enabled the "Check password on Notes id file" option in a security policy.
By default, "Password History (Notes only)" under "Password Expiration Settings" section is set automatically to 50 passwords.
You set the password history value to 0, then saved and closed the document:

You opened the document again and observed that the "Password History" was set back to default value (50).

Cause

The minimal value you can specify in this field is 1. At least one password (actual) needs to be saved in the password history of the ID file

Resolving the problem

Set the "Password history" value to 1. Save and close the document.

Reference : IBM RSS (http://www-01.ibm.com/support/docview.wss?uid=swg21613869&myns=swglotus&mynp=OCSSKTMJ&mync=R)

The attachment is corrupted in the affected database.

Problem

The attachment is corrupted in the affected database.

Resolving the problem

In this case running "load compact <database_name> -C -ZU -i" resolved the issue and compact process was completed.
After this action, running compact without "-i" switch completed successfully also.

How do I accept a meeting I previously delegated?

If you want to accept a meeting you previously delegated to someone, that person must decline it and delegate it back to you.
 The person you delegated to must click Decline on the invitation, then click Delegate this invitation/meeting and return control back to your name, on the message that appears:

 

After the person delegated the meeting back to you, you can accept it.