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

GenerateAdvice can't parse Query



Customer SQL appears to be too complex for PRPC parser. Specifically there appears to be an issue with the "CASE" operation in the SQL.

Error Messages

2014-06-16 08:03:31,036 | ERROR | WorkManager.PRPCWorkManager_WM : 2 | : | GenerateAdvice.PegaAES_Work_Action_QueryPerformance.Action | Msg: Encountered error while trying to parse the following SQL:
SELECT . . . 

Expected FROM token!: {type=LPAREN, spos=236, epos=236, text='('}
Expected FROM token!: {type=LPAREN, spos=236, epos=236, text='('}
at com.pega.aes.utils.sql.SQLParser.parseSelectStatement(
at com.pega.aes.utils.sql.SQLParser._parse(
at com.pega.aes.utils.sql.SQLParser.parse(

Steps to Reproduce

Any SQL statements that contain a CASE expression will not be parsed correctly by the AES SQL Parser.

Root Cause

The root cause of this problem is a defect in Pegasystems’ code/rules.


This issue is addressed by HFix-9570. Further problems with SQL statements that cannot be properly parsed by the AES SQL Parser are addressed by HFix-9842.

Published March 21, 2016 - Updated December 2, 2021

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