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

Cannot search Smart Disputes Framework Work Objects



Cannot search for work objects created from 6.3SP1 Smart disputes framework.

Error Messages

2015-01-15 12:22:51,343 [j2ee14_ws,maxpri=10]] [ STANDARD] [ PegaRULES:06.03] ( search.internal.RuleScanner) INFO [email protected] - Scanning class MyCoCardSd-Work-RunProcess
2015-01-15 12:22:51,355 [j2ee14_ws,maxpri=10]] [ STANDARD] [ PegaRULES:06.03] ( search.internal.RuleScanner) DEBUG [email protected] - executeQuery = select pzInsKey as "pzInsKey" , pyID AS "pyID" from {Class:MyCoCardSd-Work-RunProcess} where pxObjClass = {queryPage.pyPreparedValues(1)}
2015-01-15 12:22:51,380 [j2ee14_ws,maxpri=10]] [ STANDARD] [ PegaRULES:06.03] ( search.internal.RuleScanner) ERROR [email protected] - Database exception occured performing rule scan. Database-General There was a problem getting a list -302 22001 THE VALUE OF INPUT VARIABLE OR PARAMETER NUMBER 1 IS INVALID OR TOO LARGE FOR THE TARGET COLUMN OR THE TARGET VALUE. SQLCODE=-302, SQLSTATE=22001, DRIVER=3.65.97
2015-01-15 12:22:51,381 [j2ee14_ws,maxpri=10]] [ STANDARD] [ PegaRULES:06.03] ( search.internal.RuleScanner) INFO [email protected] - Processed 0 instances, skipped 0

Steps to Reproduce

Run re-index on Work- class from search landing page.

Root Cause

 Root cause  of this issue is with SDV_WORK view table's "pxObjClass" column size. Column size is too small for the length of the string "MyCoCardSd-Work-RunProcess”.  The 'pxObjClass' column size defined in framework out of the box database view table "sdv_work" is 15 which is smaller than "MyCoCardSd-Work-RunProcess" length = 26.


Altering the table view SDV_WORK’s pxObjClass column value to have a VARCHAR2 (96) is the correct solution. The SDV_WORK is not a table, it’s actually a Pega view that Joins/Unions two tables (SD_CLAIM and SD_DISPUTE).  As such the view column will take the size definition from the base table(s), but because of the literal string used in the view definition (the Select statement), the column in the view was defined with the smaller size (Char 15) of the literal/string.  Hence, to fix this issue concatenate 81 (96-15) to the column definition to increase it to 96.

Published January 31, 2016 - 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