Since upgrading to Notes 8. Then to 8.5 We have had continuous issues with deleted documents remaining in views.
F9 Wont, work, but Shift-F9 will but that’s just a band aid, I need to make this go away.
The problem is this often occurs in views that are for agents, and they error out when they try to access these documents.
And yes, the views are setup to automatically update.
Is anyone else running into this, and have they had any luck reducing or eliminating this problem?
Subject: If F9 does not work, but Shift-F9 does …
…then you either have a Cache corruption issue, or an un-synchronized clock.
F9 is a view Refresh. It tells Notes to look at any documents that have changed since the view index was last refreshed and update the view with their changes.
Shift-F9 is a view rebuild, and so discards the current index, and looks at all documents in the database to build the view. (Which is slower then a refresh)
If F9 is not picking up changes like your deletion, then one possible cause is that Notes thinks the view index was build after the document was deleted, and so that change will not be shown in a refresh.
You could try deleting your local Cache.NDK (C:/Notes/Data/) to correct a cache corruption issue.
A common cause of an un-syncronized clock is if you change the Windows date/time into the future while Notes is running. Even if you cancel such a change, you’ve inadvertently modified the Notes clock, and it won’t reset until you restart the client.
Subject: Re: Document has been deleted… Then why is it still in the view?
Check out SPR DCHR7NSUY9 and the associated hot fix(es). This was for v8, but may apply to v8.5 as well.
After eons of beating my head against the wall with IBM support on a very similar issue (and giving up like 9 months later), someone else finally was able to work with IBM to help with the issue.
This SPR fixed it for 90+% of our cases (we still seem to have a few occasionally…but it was extremely widespread before applying the hotfix).