Support Article
GenerateAdvice can't parse Query
SA-617
Summary
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(SQLParser.java:581)
at com.pega.aes.utils.sql.SQLParser._parse(SQLParser.java:597)
at com.pega.aes.utils.sql.SQLParser.parse(SQLParser.java:823)
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.
Resolution
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
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.