HCL
Skip to main content  
 
   


SPRTechnote


'Move user to another server' AdminP request causes 'Insufficient disk space' error

Technote Number: 1196823


Problem:
This issue was reported to Quality Engineering as SPR# ASCR68ZRZ6 and has been
fixed in Domino 6.5.5 and Domino 7.0.

This issue can occur when a new server is being added into an existing server
network that is administered by a main administration server and the admin4.nsf
is not replicated from the administration server to the new server.
Replicating admin4.nsf from the administration server to the new server should
resolve the issue in this case.

AIX-specific issue:
If your target server is running on the AIX platform, an AIX-specific issue was
reported to Quality Engineering as SPR# ASCR68ZRZ6 and has been fixed in Domino
6.5.5 and Domino 7.0. As a workaround in prior versions, create the database
replica manually instead of using the "Move user to another server" function.

Excerpt from the Lotus Notes and Domino Release 6.5.5 MR fix list (available at
http://www.ibm.com/developerworks/lotus):
Administration
SPR# ASCR68ZRZ6 - When the Administration Process checks disk space for a new
replica, it might match the wrong physical directory statistics and thus the
wrong disk when deciding which disk a new replica should reside on. For
example, if the 'mail' directory is on a different drive from the 'domino data'
directory, Adminp might choose the 'domino data' directory (back one directory
from mail). It would then use those drive statistics (the wrong drive) when
testing for enough disk space. This was based on physical drive layout on the
machine or drive search data. With this fix, Adminp will match only the correct
physical drive statistics. This regression was introduced in 6.0.4.

Supporting Information:
In one instance a customer was receiving this error when creating a new
replica. The source server was running Domino 6.5.3 on Windows and the
destination server was running Domino 6.5.5 on Linux. The source server was
upgraded to 6.5.5 to resolve this issue, however the error persisted. It was
found that adding the following INI parameter to both servers resolved the
error and the new replicas were created without issue:

enableremotediskstats=1

More information about the ini parameter enableremotediskstats=1 can be found
in Document 1155930.
More >





  Document options
Print this document
Print view

  Search
Search Advanced Search


  Fix list views

 RSS feeds   RSS
Subscribe to the fix list

  Resources
Using this database
View notices

  HCL Support
HCL Support


    About HCL Privacy Contact