LO48876: ADMINP ERROR "CANNOT PERFORM THE NAME CHANGE: <XXX> NAME IS NOT UNIQUE AMONG ALL REFERENCED DIRECTORIES"

APAR status

• Closed as returned (APAR cannot be resolved without additional info from IBM or customer.)

Error description

• Customer has an environment with 3 Servers.
  It should be pointed out that one of the key requirements was
  that when
  addressing emails (using the Notes client or iNotes web
  interfaces), access
  should be restricted so that name selection of people from
  another OU in the
  organization should not be possible.
  
  
  
  
  Two of the servers (SERVER1 and SERVER2) are used for email
  and hosting
  varying web applications that make up our solution.
  They have a multi NAB environment with a separate NAB for each
  OU in the
  organisation's hierarchy.
  All users are created in the main NAMES.NSF and the 'Directory
  Cataloger'
  copies all relevant 'Person' documents into the appropriate NAB.
  
  'Directory Assistance' is switched on so that these users can
  authenticate and
  lookup names in the OU NABs.
  
  
  When attempting to rename a user they get the following error in
  admin4.nsf:
  Title: System Directory (No Access) File name: names.nsf
  Cannot perform the name change:
  XX-NameChange name is not
  unique among
  all referenced Directories.
  
  The reason this does not work is that the user is present in the
  main NAB and
  also in the OU NAB and so AdminP complains that the entry is not
  unique.
  The customer is currently looking at the option of of batch
  processing 'Rename'
  and 'Move' actions on the weekends when 'Directory Assistance'
  can
  be disabled on the Server, but this is not ideal.
  
  
  Is there a way to get the 'Administration Process' to ignore
  sub-NABs without
  disabling 'Directory Assistance' ?
  
  
  This issue is very similar to SPR: PFOI6BNCTF.
  Maybe both issues could be solved with a notes.ini parameter
  that tells AdminP
  not to check secondary/additional directories when performing a
  name
  change/move.
  

Local fix

• Disabling the Directory Assistance Database and then perform the
  name change.
  

Problem summary

Problem conclusion

Temporary fix

Comments

• This APAR is associated with SPR# PFOI6CGEV6.
  The record was returned to the person who created it for more
   information.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels