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 not joining VBD cluster



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(
at oracle.jdbc.driver.T4CTTIoer.processError(
at oracle.jdbc.driver.T4C8Oall.processError(
at oracle.jdbc.driver.T4CTTIfun.receive(
at oracle.jdbc.driver.T4CTTIfun.doRPC(
at oracle.jdbc.driver.T4C8Oall.doOALL(
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(
at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(
at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(
at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(
at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeQuery(
at org.apache.tomcat.dbcp.dbcp.DelegatingPreparedStatement.executeQuery(

Steps to Reproduce

  1. Externalise Interaction history tables to different schema.
  2. Drop the interaction history tables from pega data schema.
  3. 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.


Apply HFix-29156.


Published September 21, 2016 - 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