IBM Support

LO60436: NAMELOOKUP DEBUG SHOWS EXCESSIVE NAME LOOKUP ACTIVITY

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as user error.

Error description

  • A customer has been having slow lookup times, and the following
    debug was enabled:
    
    Client_Clock=1
    Console_Log_Enabled=1
    CLIENT_CLOCK_PROCESS=nlnotes
    CLIENT_CLOCK_MAINTHREADGROUP=1
    LOGSTATUSBAR=1
    DEBUG_BUSY=30
    Debug_Directory_Assistance=1
    Debug_Namelookup=1
    
    We would like to understand what appears to be excessive name
    lookup activity, even though dircat is in
    use, with location doc set to stop after first match.
    
    Here are some concerning entries:
    
    NAMELookup::<Lookup> PID:TID ( 6C4:2) start of routine
    NAMELookup::<lookup> Searching view '$Users' (1 of 1 views).
    NAMELookup::<lookup>Searching name='CN=Mickey Mouse/O=ACME' (1
    of 3 names).
    NAMELookup::<lookup> Searching DBIndex=1.
    NAMELookup::<LocateNameSpace> locate namespace in DBIndex=1,
    view='$Users'
    NAMELookup::<ReturnNameInfo> name='CN=Mickey Mouse/O=ACME' was
    found '0' match(es)
    NAMELookup::<lookup> No matches found for name 'CN=Mickey
    Mouse/O=ACME' in dbIndex '1'
    NAMELookup::<lookup> NumReturned=0, TotalNumReturned=0 match(es)
    for name='CN=Mickey Mouse/O=ACME'
    NAMELookup::<lookup>Searching name='CN=Mickey Mouse/O=ACME' (1
    of 3 names).
    NAMELookup::<lookup> Searching DBIndex=2.
    NAMELookup::<LocateNameSpace> locate namespace in DBIndex=2,
    view='$Users'
    NAMELookup[DirCat]::<LNABLookupInfo> Not able to follow links!
    NAMELookup[DirCat]::<LNABLookupInfo> Not able to follow links!
    NAMELookup[DirCat]::<LNABLookupInfo> Not able to follow links!
    NAMELookup[DirCat]::<LNABLookupInfo> Not able to follow links!
    NAMELookup[DirCat]::<LNABLookupInfo> Not able to follow links!
    NAMELookup[DirCat]::<LNABLookupInfo> Not able to follow links!
    NAMELookup[DirCat]::<LNABLookupInfo> Not able to follow links!
    NAMELookup[DirCat]::<LNABLookupInfo> Not able to follow links!
    NAMELookup[DirCat]::<LNABLookupInfo> Not able to follow links!
    NAMELookup[DirCat]::<LNABLookupInfo> Not able to follow links!
    NAMELookup[DirCat]::<LNABLookupInfo> Not able to follow links!
    NAMELookup::<lookup> Found '1' match(es) for name 'CN=Mickey
    Mouse/O=ACME' in dbIndex '2'
    NAMELookup::<lookup> NumReturned=1, TotalNumReturned=1 match(es)
    for name='CN=Mickey Mouse/O=ACME'
    NAMELookup::<lookup> Skipping to next view/namespace (stop at
    first match)!
    
    And
    
    NAMELookup::<LocateNameSpace> locate namespace in DBIndex=1,
    view='$ServerAccess'
    NAMELookup::<LocateNameSpace> locate namespace in DBIndex=2,
    view='$ServerAccess'
    NAMELookup::<LocateNameSpace> could not find namespace!
    
    And  Primarily .... when it can't find the user doing the lookup
    herself  .... don't
    
    NAMELookup::<Lookup> PID:TID ( 880:A) start of routine
    NAMELookup::<lookup> Searching view '$Connections' (1 of 1
    views).
    NAMELookup::<lookup>Searching name='CN=THIS USER/O=ACME' (1 of 4
    names).
    
    I'm also concerned about certain areas in the console log - for
    example:
    NAMELookup::<lookup>Searching name='CN=THIS USER/O=ACME' (1 of 1
    names).
    NAMELookup::<lookup> Searching DBIndex=1.
    NAMELookup::<LocateNameSpace> locate namespace in DBIndex=1,
    view='$Servers'
    NAMELookup::<LocateNameSpace> could not find namespace!
    
    
    "THIS USER" is the one doing the lookup and Notes debug states
    "could not find namespace!"
    

Local fix

  • N/A
    

Problem summary

Problem conclusion

Temporary fix

Comments

  • This APAR is associated with SPR# DCHR8GBHHS.
    The problem was caused by a user error or user
     misunderstanding.
    

APAR Information

  • APAR number

    LO60436

  • Reported component name

    DOMINO SERVER

  • Reported component ID

    5724E6200

  • Reported release

    852

  • Status

    CLOSED USE

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-04-27

  • Closed date

    2011-05-06

  • Last modified date

    2011-05-06

  • 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

[{"Business Unit":{"code":"BU055","label":"Cognitive Applications"},"Product":{"code":"SSKTMJ","label":"Lotus Domino"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5.2","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
06 May 2011