Support Article

Join is not working across database instances



A report runs on a class that points to the rules database and has a join with a class that points to the work/data database.

When the report runs, the sub report queries the rules database instead of the work.

Error Messages

Error: ** An error occured on executing the query for the report definition - There was a problem getting a list: code: 208 SQLState: S0002 Message: Invalid object name 'PEGA_DATA.vw_XXX_WorkList'. DatabaseException caused by prior exception: Invalid object name 'PEGA_DATA.vw_XXX_WorkList'. | SQL Code: 208 | SQL State: S0002

Steps to Reproduce

  1. Create rules and work/data databases in two separate instances.
  2. Create a report definition in a class which is in Rules database.
  3. Join with a class which is in work/data database.
  4. Run the report.

Root Cause

Pega 7 supports split schema within one database but has not totally eliminated queries that join rules to data.

Thus, Pega 7 does not support configuring rules and data in two totally separate databases instances.


Usage of spilt schema is preferred in this situation.

Published May 1, 2017 - Updated May 31, 2017

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.