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

VBD does not work and ORA-00942 errors are seen in logs

SA-13299

Summary



Visual Business Director (VBD) is not running and user witness errors in the server log file.

Error Messages




Issue-1

Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'localEngine' defined in class path resource [vbd-service-config.xml]: Unsatisfied dependency expressed through constructor argument with index 0 of type [com.pega.decision.vbd.service.engine.VBDConfiguration]: : Error creating bean with name 'vbdConfiguration' defined in class path resource [vbd-service-config.xml]: Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.pega.decision.vbd.service.engine.configuration.impl.VBDConfigurationImpl]: Constructor threw exception; nested exception is org.springframework.jdbc.BadSqlGrammarException: PreparedStatementCallback; bad SQL grammar [select pzCollectionName, pzConfigurationData from PR_DATA_VBD_COLLECTION_CONFIG where pzCollectionName=?]; nested exception is java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist

Issue-2

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



1. Log into PRPC.
2. Start VBD.


Root Cause



VBD datasource was pointed to admin schema user. However, this is a Split schema, VBD data source must point to PegaDATA schema user.

Resolution



For issue-1 Map vbdDataSource to PegaDATA schema user.
For issue-2 Run pzUpdateActualsConfiguration to correct the VBD loading issue.

 

Published August 27, 2015 - 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