Skip to main content
This forum is closed to new posts and responses. New discussions are now taking place in the IBM Developer Answers forum.
Information Mgmt
New to Lotus
How to buy
Live demos
Technical library
Forums & community
Java™ technology
Open source
SOA and Web services
Web development
My developerWorks
About dW
Submit content

developerWorks  >  Lotus  >  Forums & community  >  IBM Lotus Notes/Domino 8.5 Forum (includes Lotus Notes Traveler)

IBM Lotus Notes/Domino 8.5 Forum (includes Lotus Notes Traveler)

Previous Next
Subject: Please bring your Lotus Support Contracts to bear! A doozy of an SPR.
Feedback Type: Problem
Product Area: Domino Server
Technical Area: Error Message
Platform: ALL
Release: Beta 1
Reproducible: Intermittent

I wouldn't normally poll the forum like this, but there is a significant regression bug in ND6/7/8 that still exists in 8.5 Beta 1 and 8.0.1. The ticket on this SPR (# DCOE6N82TP) has been open a couple of years because it is such a horrific bear to reproduce.

IBM has finally acknowledged that it is a bug, and a fairly significant one. However the fix for it will require an ODS update, meaning that 8.5.1 is the first candidate release for a fix. It needs just a bit more weight added to it though before they'll commit to the fix, so if you find this bug important please open a PMR ticket and mention SPR # DCOE6N82TP.

The Short Story:
        If enabled, the database property "optimize document table map" can -- on rare occasion -- cause documents to remain in a view even though they should no longer be there according to the view's selection formula.

        Refreshing an affected view (e.g. F9 in the client) does NOT fix the problem.

        Rebuilding the view index via one of the following methods will fix the problem, temporarily:
        1. Shift-F9 in the client
        2. A Fixup followed by Updall -R on the affected database
        3. Ctrl-Shift-F9 in the client

        Once fixed, the problem may never manifest in that DB again. Or it may re-manifest in the same view (or a different view) in 5 minutes. It's very intermittent.

        The problem is also extremely rare -- we do massive amounts of doc updates daily and are only seeing this problem manifest a couple of times a week.

        Turning off the database property (followed by a compact) will avoid the problem, but at a massive performance penalty (see below).

Why should you care?

        1. This is a cornerstone of Domino workflow functionality:
        - doc appears in a view
        - doc's fields get changed
        - doc should no longer appear in view <<< with this bug, this step is not 100% reliable

        2. This property is enabled by default on many core Domino database (including the NAB). Due to the extreme rarity and intermittence of the bug, it is possible that a wide variety of all-around "strange" behavior is related to this obscure problem.

        3. If you have any custom apps on Domino, this bug can obviously cause severe problems.

        4. Since fixing this bug will require an ODS update, it *must* get fixed in a major release. This bug has taken literally years to track down so if a plan isn't made to address it in early 8.5, it will need to wait until N/D 9 or later.

"I've seen this property but I don't know what it does exactly..."

From the Help:

That's a bit vague, though. Here's an example that might make things more clear. Picture a database with 100,000 docs:
    99,500 form field of "A"
    500 form field of "B"
With "Optimize Document Table Map" OFF, A view or NotesDatabase.Search() with a formula of SELECT FORM="B" will iterate through ALL 100,000 docs looking for matches.

WIth "Optimize Document Table Map" ON, A view or NotesDatabase.Search() with a formula of SELECT FORM="B" will iterate through ONLY the 500 "B" docs looking for matches. The other 99,500 docs are skipped.

This can result in HUGE performance improvements for large DBs with small subsets of documents. This property worked brilliantly in R5, but has been glitchy since ND 6.0.

Thanks for reading. Without this bug being fixed, we all have two options:

1. Accept "mostly accurate" view indexes throughout many DBs in Domino (including the NAB).
2. Avoid using one of the most performance-enhancing options of Domino.

Feedback number ECBS7F9Q6U created by Erik C. Brooks on 06/03/2008

Status: Open

Please bring your Lotus Support Con... (Erik C. Brooks 3.Jun.08)
. . Been fighting this for years.... (Mark Taylor 21.Nov.14)


Search this forum

Member Tools

RSS Feeds

 RSS feedsRSS
All forum posts RSS
All main topics RSS
More Lotus RSS feeds


Forum use and etiquette
Native Notes Access
Web site Feedback

Lotus Support

 Lotus Support
IBM Support Portal - Lotus software
Lotus Support documents
Lotus support by product
Lotus support downloads
Lotus support RSS feeds


IBM Composite Applications
IBM Mashup Center
IBM Connections
IBM Connections Cloud Developers
IBM Docs
IBM Forms
IBM Mobile Connect
IBM Sametime
IBM SmartCloud for Social Business
IBM Web Experience Factory
Lotus Domino
Lotus Domino Designer
Lotus Expeditor
Lotus Foundations
Lotus iNotes
Lotus Instructor Community Courseware
Lotus Notes
Lotus Notes & Domino Application Development
Lotus Notes Traveler
Lotus Protector
Lotus Quickr
Lotus Symphony
IBM Web Content Manager
WebSphere Portal

Lotus Forums

 Lotus Forums
Notes/Domino 9.0
Notes/Domino 8.5 + Traveler
Notes/Domino XPages development forum
Notes/Domino 8
Notes/Domino 6 and 7
IBM Connections
IBM Mobile Connect
IBM Sametime
IBM SmartCloud Notes
Lotus Enterprise Integration
Lotus Protector
Lotus Quickr
Lotus SmartSuite