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

Incorrect SQL Generated for Subsegments after upgrading to PM7.4

SA-61983

Summary



Post Pega Marketing (PM) 7.4 upgrade, incorrect SQL is generated for subsegments.


Error Messages



Error executing SQL for Tab Set 1, Group Group 1 : ORA-00904: "PC3S"."PYSUBJECTID": invalid identified


Steps to Reproduce

  1. Upgrade PM 7.31 to PM 7.4.
  2. In the upgraded environment, create a new Segment.
  3. Refer to the pre-existing segment and run this segment.


Root Cause



A defect in Pegasystems’ code or rules

If a new Segment rule is created and a pre-existing subsegment is included (created in PM 7.31), then the generated SQL is incorrect. Instead of referring to the CUSTOMERID column, it referred to PYSUBJECTID column for a subsegment created in PM 7.31. The PM 7.31 segments do not have PYSUBJECTID column.
The segment fails to execute. The susbsegment when run individually works, however, the main segment referring it fails as the SQL is incorrect.


Resolution



Apply HFix-46007.


 
Suggest Edit

Published September 19, 2018 - Updated December 2, 2021

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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