Support Article
VBD not joining VBD cluster
SA-27901
Summary
Pega environment has DSM Interaction History tables externalised to a different database schema.
As part of externalisation the Interaction history tables from PegaData schema were deleted.
After this change, adding a PRPC node to Visual Business Director (VBD) Cluster fails with JOINING_FAILED status.
Error Messages
2016-08-17 08:39:50,784 [eb15.cached.thread-8] [ STANDARD] [ ] [ ] (ition.InternalPartitionService) INFO - [<you IP>]:5751 [vbd] [3.4.1] Initializing cluster partition table first arrangement...
2016-08-17 08:39:52,844 [eb15.cached.thread-8] [ STANDARD] [ ] [ ] (l.access.ConnectionManagerImpl) ERROR - Not returning connection 4 for database "pegarules" to the pool as it previously encountered the following error
User ID: (unknown)
Last SQL: select min(pxOutcomeTime),max(pxOutcomeTime) from PEGADATA.pr_data_ih_fact
java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396)
at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:879)
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:450)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:192)
at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:207)
at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:884)
at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1167)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1289)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3584)
at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3628)
at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeQuery(OraclePreparedStatementWrapper.java:1493)
at org.apache.tomcat.dbcp.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)
Steps to Reproduce
- Externalise Interaction history tables to different schema.
- Drop the interaction history tables from pega data schema.
- Add prpc node to VBD cluster management.
Root Cause
A defect in Pegasystems’ code or rules. There is a reference to PegaDATA schema when running queries on Interacion history tables when initialising VBD context.
Resolution
Apply HFix-29156.
Published September 21, 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.