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

Segment Population Error



When user is trying to run or create a New Segment, user is facing issue on Screen.

Error Messages

Segment Populate Error.

Steps to Reproduce

  1. Create a New segment with some filter criteria.
  2. Save and then run it.

Root Cause

An issue in the custom application code or rules.

User has created a new customer Class which is mapped to a table in external database instead of EXternalMKTData.


Here’s the explanation for the reported behavior:

ExternalMKTData is a data-admin-database instance is used to identify where user create segments, batchoutput tables, query customer tables and the location of a number of other key tables.

User must typically join between these entities during various points of processing when marketing is working, this is why they need to be in the same instance and since using one DB-admin-db instance ( ExternalMKTData ) it is always going to be using one schema.

It's the expectation that the schema ( and db instance) for the customer data, the mkt_customer_segments table and the schema that user creates segment tables in are all the same, so one DB instance and one schema hosting all.

User can overcome the one schema constraint through the use of synonyms on Oracle.

Published May 4, 2017 - Updated December 2, 2021

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