Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

KM article search is not working for a particular String

SA-33786

Summary



KM article search is not working when doing a search for "milk" or "milka", no results are being returned.


Error Messages



Not Applicable


Steps to Reproduce



1. Launch Interaction portal.
2. Click on Knowledge tab on left side.
3. in search field enter "Milk" or "Milka".


Root Cause



A third-party product issue.

Issue seems to be because of current limitation with ORACLE where in it allows only maximum of 1000 expressions (basically a space holder ‘?’) currently in a query. We observed that in the tracer we were getting below error.

“There was a problem getting a list: code: 1795 SQLState: 42000 Message: ORA-01795: maximum number of expressions in a list is 1000”.

When searched for “Milka”, the result count returned by RD ContentSearch is 1001 (called from Step 5 of activity KMSearchRD).

The resultset of these keys are passed as input for retrieving Taxonomy Content Keys.

This is where the code is breaking. The query that is getting build (something on below lines) has more than 1000 expressions and ORACLE is making noise here.

“SELECT "PC0".CONTENTKEY AS "ContentKey" , "PC0".TAXONOMYKEY AS "TaxonomyKey" FROM RULES.pfw_km_link_contentcategory "PC0" WHERE "PC0".CONTENTKEY IN (? , ? , ? , ? , ? , ? , ?.........”.


Resolution



Perform the following local-change:

The quick fix for this would be to limit the search results returned to some where around 990.

This limit can be set to parameter pyMaxResults in Step 5 of KMSearchRD.


Published March 14, 2017 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us