Support Article
BadSqlGrammarException noticed in Java console while opening VBD
SA-5149
Summary
Developer was trying to load the Visual Business Director (VBD), however it was failing. In the Java console debug logs, developer has observed the stack trace with BadSqlGrammarException and ORA-00942 error message. User has verifed that all the database objects (Table and Columns) referenced in the SQL statement exists. Developer has tried with and without GridGain running and has observed the same error message.
Error Messages
>>> Type: org.springframework.jdbc.BadSqlGrammarException
>>> Message: PreparedStatementCallback; bad SQL grammar [select * from (select Action.pyIssue as "Action.pyIssue", Action.pyGroup as "Action.pyGroup", Action.pyName as "Action.pyName", Application.pyApplication as "Application.pyApplication", Application.pyComponent as "Application.pyComponent", Application.pyStrategy as "Application.pyStrategy", Application.pyInteraction as "Application.pyInteraction", Channel.pyChannel as "Channel.pyChannel", Channel.pyDirection as "Channel.pyDirection", Op.pyDivision as "Operator.pyDivision", Op.pyOperator as "Operator.pyOperator", Op.pyOrganization as "Operator.pyOrganization", Op.pyUnit as "Operator.pyUnit", Outcome.pyOutcome as "Outcome.pyOutcome", ft.pxpriority as "pxPriority", ft.pxRank as "pxRank", ft.pypropensity as "pyPropensity", ft.pylatitude as "pyLatitiude", ft.pylongitude as "pyLongitude", ft.pxoutcometime as "Timestamp", ft.pxfactid as "pxFactId" from PR_DATA_IH_FACT ft join pr_data_ih_dim_action Action on ft.pzactionid = Action.PZID join pr_data_ih_dim_application Application on ft.pzapplicationid = Application.PZID join pr_data_ih_dim_channel Channel on ft.pzchannelid = Channel.PZID join pr_data_ih_dim_operator Op on ft.pzoperatorid = Op.PZID join pr_data_ih_dim_outcome Outcome on ft.pzoutcomeid = Outcome.PZID) query1 where "Timestamp">=? and "Timestamp"<=?]; nested exception is java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist
Steps to Reproduce
Open Visual Business Director
Root Cause
The root cause of this issue was due to a misconfiguration in the ihDataSource which was pointed to Pega_Admin schema instead of PegaDATA schema
Resolution
Suggested developer to update the ihDataSource with PegaData schema
Published January 31, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.