IBM Support

LO47094: DATABASE IS NOT ACCESSIBLE AFTER AN FILE ACCESS ERROR OCURRED IN HTTP TASK

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Problem Description:
    
    If you try to access a DWA mail database from DWA Client(Web
    Browser) when the
    database is being processed by fixup command, the following
    phenomena will
    happen:
    1. "HTTP 500 internal server error" is returned to the browser,
    and nothing can
    be displayed in the browser.And the following error message is
    output to the
    server console:
    "HTTP Web Server: Lotus Notes Exception - This database is
    currently being used
    by some one else.In order to share a Notes database, all users
    must use a
    Domino Server instead of a File Server"
    2. Although the fixup command is finished,  if you try to open
    the database
    from notes client, the following message will be displayed in a
    message box,
    and the file cannot be opened:
    "This database is currently being used by some one else.In order
    to share a
    Notes database, all users must use a Domino Server instead of a
    File Server"
    3. If you try to fixup the database again, the same error
    message will be
    output to the server console.
    4. "drop all" & "dbcache flush" command cannot fix this
    problem.
    5. After you restart the Domino server, the database can be
    accessed by DWA and
    notes client.
    
    Since this issue does not match any existing SPR. I created this
    new one. I
    think the problem of this issue is that the database cannot be
    accessed unless
    you restart the Domino server. This issue is reported from our
    client by PMR
    55769,999,760.
    
    Please research the root cause of this issue.
    
    For the following question from Jon:
    Can HTTP access the database after fixup completes? Fixup should
    get exclusive
    access to the file while it is processing it so if it allows
    access once it
    completes then this is working as designed.
    
    The answer is:
    Even after fixup completes, the database is still not accessible
    from both
    Notes client and DWA Client. The database will be accessible
    only after a
    restart of Domino server,
    
    Environment:
    Domino Server: Domino 7.0.1 (It is also reproduced on Domino
    7.0.3 FP1)
    OS: Windows 2003 Server
    Browser: Microsoft Internet Explorer V6.0
    
    Steps to Reproduce:
    1. Set up a test environment as following:
       Domino Server: 7.0.3 FP1
       OS: Windows 2003 Server
       Browser: Microsoft Internet Explorer V6.0
    2. Add a DWA user to Domino directory, and send some mail to
    this user.
    3. Open the DWA user's mail database from a DWA client.
    4. Try to do the following operations as quickly as possible:
    a. Execute "load fixup "or "load fixup -O" command from server
    console to fixup
    the DWA user's mail database
    b. After the fixup command was started, try to open a mail from
    DWA user's
    mailbox as quickly as possible (This operation should be done
    before the fixup
    command is finished)
    5. "HTTP 500 internal server error" is returned to the browser,
    and nothing can
    be displayed in the browser.And the following error message is
    output to the
    server console:
    "HTTP Web Server: Lotus Notes Exception - This database is
    currently being used
    by some one else.In order to share a Notes database, all users
    must use a
    Domino Server instead of a File Server"
    6. After the complete of fixup command which was issued in step
    4, try to open
    the database from notes client, the following message will be
    displayed in a
    message box, and the file cannot be opened:
    "This database is currently being used by some one else.In order
    to share a
    Notes database, all users must use a Domino Server instead of a
    File Server"
    7. Try to fixup the database, the same error message will be
    output to the
    server console.
    8. Execute "drop all" & "dbcache flush" command from server
    console, the
    database still cannot be accessed with the same error message.
    9. Restart the Domino server, then the database can be
    accessed.
    
    Additional Information:
    If you do the following steps at first, and then do the
    reproducing steps of
    this SPR, you can find that the mail database will not be
    locked.
    1. Create a new user group named "TestGroup"
    2. Add the owner of the dwa mail database to "TestGroup"
    3. Add "TestGroup" into  the "administrators" field of [Server
    
    Document]-[Security] tab.
    4. Add "TestGroup" to the ACL of the mail database, give the
    group with the
    mananger's right of the database.
    5. Remove the owner from the ACL of the mail database.
    6. Restart the server to make the change of the server document
    effective.
    7. Do Step 2 - Step 8 of the SPR's reproducing steps, you will
    find that
    without restarting the domino server, the owner can access the
    mail database
    and a new fixup command can be executed.
    
    Anyway this can not be used as a workaround for this SPR.
    

Local fix

  • Restart the Domino server
    

Problem summary

  • A programming error was found and will be corrected in a future
     release.
    

Problem conclusion

  • A programming error was found and will be corrected in a future
     release.
    

Temporary fix

Comments

  • This APAR is associated with SPR# UTOO7F3B3K.
    

APAR Information

  • APAR number

    LO47094

  • Reported component name

    DOMINO SERVER

  • Reported component ID

    5724E6200

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-12-09

  • Closed date

    2010-05-20

  • Last modified date

    2010-05-20

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

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

Modules/Macros

  • NA
    

Fix information

  • Fixed component name

    DOMINO SERVER

  • Fixed component ID

    5724E6200

Applicable component levels

  • R800 PSN

       UP

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

Document Information

Modified date:
20 May 2010