Technote Number: 1200473
Problem:
When the "No documents found" error occurs, it prevents the agent list of
processed documents from being updated. Therefore the next time this agent
runs, it will run on the previous documents as well as newly eligible
documents. The agent will continue to include previous documents (since the
last successful search) until the search returns at least one document that
meets the selection criteria. For example, if an agent ran on 10 documents and
none of them matched the search criteria, and the next time the agent ran it
was expected to run on 5 documents, it would run on the previous 10 as well as
the new 5.
Because the agent may act on a greater document collection size than expected,
in databases which are not full-text indexed, the additional error condition
may occur. This is expected given the document collection size.
The fact that an agent's processed list is not updated in cases where the
document selection returns no documents has been reported to Quality
Engineering as SPR# KCAR69V437, and has been fixed in Notes and Domino 6.5.5.
Excerpt from the Lotus Notes and Domino Release 6.5.5 MR fix list (available at
http://www.ibm.com/developerworks/lotus):
Agents
SPR# KCAR69V437 - Error "no documents found" was displayed when no matches were
found on databases that were not full-text indexed, which was inconsistent with
the behavior when no matches were found in a database that was full text
indexed. With this fix, no error message is displayed, matching documents are
returned as zero.
Refer to the Upgrade Central site for details on upgrading Notes/Domino.
Workaround
If using a LotusScript agent do not use the agent Document Selection (search)
functionality, but instead use the NotesDatabase classes UnprocessedFTSearch
method to search through documents the agent hasn't acted on previously. The
agent must be coded to mark documents as acted on (processed) to keep them from
being acted on in subsequent executions of the agent. This can be done using
the UpdateAll method (of the NotesDocumentCollection class) or the
UpdateProcessedDoc method (of the NotesSession class).
If the agent is not a LotusScript agent then it may be necessary to ensure that
at least one document meets the selection criteria each time the agent executes.
Additionally, for the "Maximum allowable documents exceeded..." error:
Either create a full text index for the database or use the NOTES.INI parameter
"TEMP_INDEX_MAX_DOC" to increase the number of documents allowed in the
temporary index. Note: If the database resides on a server then the parameter
must be set in the server's NOTES.INI.
Supporting Information
When an agent uses the Document Selection (search) feature, a full-text search
is performed to select the documents that match the search criteria even if
that database is not full-text indexed. In such cases, a temporary on-the-fly
full text index will be created. The NOTES.INI parameter "TEMP_INDEX_MAX_DOC"
controls how many documents can be indexed in an on-the-fly index, by default
the limit is 5000. This parameter was added in Notes 6.0, and has a maximum
value of 2147483647. More >
|  |
|
|
|
|
|