Diagnosis In query &V1&, you have created the join criterion &V2& that uses inputfield &V3& of the secondary search connector &V4&. For this field, onlyselection mode Single Value> or Interval> is available. Thismeans that the system cannot pass a set of field values to searchconnector &V4& in one search request.System Response When processing a join, the system collects all different valuesreturned by the output field of the primary search connectorcorresponding to field &V3&. Since it can only pass one field value tosearch connector &V4& at a time it might have to call the searchconnector multiple times. Depending on the data provision technology andthe amount of data inside the data provider this may result in longruntimes or even in aborting query processing due to lack of memory. Procedure To avoid the problem, pay attention to the following:
- Use query fields with selection modes Single Value> or
Interval> as input field in join criteria only in exceptionalcases.
- Use a fast data provision technology.
- Use a small set of field values to be passed to the secondary search
connector (not more than 10).
- If possible, look for an equivalent search connector that can handle the
problematic field in selection mode Multiple Values> or SelectOption>. If you have to use search connector &V4&, ensure the following:
- You have set the MaxExec >(
Maximum Number of Executions ofSecondary Search Connector>) feld of the query join definition to themaximum number of calls of the search connector that you consideracceptable.
- You have checked whether setting the Dld. Sel.> (
Delayed Selection by Optional InputFields Allowed>) indicator of the query join definition could reducethe number of necessary calls.
|