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 data not inserting into Segment table

SA-20325

Summary



Developer was trying to create a Segment and has defined criteria which select the Intersection resulting in a single customer being selected for the Segment.
When they run the Segment, it creates the appropriate table in the database but does not populate the table with the selected intersection audience. The Segment run hangs and never ends.


Error Messages



Error snippet from the PegaRULES.log

2016-02-12 00:48:24,117 [http-bio-8080-exec-7] [TABTHREAD0] [                    ] [     PegaRULES:07.10] ( pega.highavailability.quiesce) ERROR {Server Ipaddress}|{Ip address} [email protected] - Schedule for ruleset PegaMKT-Engine not available
2016-02-12 00:48:24,117 [http-bio-8080-exec-7] [TABTHREAD0] [                    ] [     PegaRULES:07.10] ( pega.highavailability.quiesce) ERROR {Server Ipaddress}|{Ip address} [email protected] - Agent Queue for DeferredSegments not found
2016-02-12 00:48:24,117 [http-bio-8080-exec-7] [TABTHREAD0] [                    ] [     PegaRULES:07.10] (          internal.async.Agent) INFO  {Server Ipaddress}|{Ip address} [email protected] - Trying to restart agent queue in PegaMKT-Engine ruleset having queue name DeferredSegments
2016-02-12 00:49:10,497 [ttp-bio-8080-exec-38] [TABTHREAD0] [                    ] [     PegaRULES:07.10] ( pega.highavailability.quiesce) ERROR {Server Ipaddress}|{Ip address} [email protected] - Schedule for ruleset PegaMKT-Engine not available
2016-02-12 00:49:10,497 [ttp-bio-8080-exec-38] [TABTHREAD0] [                    ] [     PegaRULES:07.10] ( pega.highavailability.quiesce) ERROR {Server Ipaddress}|{Ip address} [email protected] - Agent Queue for AnalysisSchedule not found
2016-02-12 00:49:10,497 [ttp-bio-8080-exec-38] [TABTHREAD0] [                    ] [     PegaRULES:07.10] (          internal.async.Agent) INFO  {Server Ipaddress}|{Ip address} [email protected] - Trying to restart agent queue in PegaMKT-Engine ruleset having queue name AnalysisSchedule
2016-02-12 00:50:03,917 [ttp-bio-8080-exec-38] [TABTHREAD1] [                    ] [     PegaRULES:07.10] ( pega.highavailability.quiesce) ERROR {Server Ipaddress}|{Ip address} [email protected] - Schedule for ruleset PegaMKT-Engine not available
2016-02-12 00:50:03,917 [ttp-bio-8080-exec-38] [TABTHREAD1] [                    ] [     PegaRULES:07.10] ( pega.highavailability.quiesce) ERROR {Server Ipaddress}|{Ip address} [email protected] - Agent Queue for PegaMKTStartupAgent not found

Steps to Reproduce


 

  1. Create a Segment rule with criteria in OOTB Pega Marketing (using PegaMKT-Data-Customer).
  2. Select appropriate intersection.
  3. Run the Segment.


Root Cause



The Agents included with Pega Marketing 7.13 were shipped disabled by default. It was not enabled in this environment.

Resolution



Developer is suggested to make following changes to the PRPC environment: 


Step1) Follow below steps to enable agent schedules for PegaNBAM-Artifacts, PegaMKT-Engine and PegaMKT-PushNotification .
       a. From the Records Explorer, navigate to SysAdmin>Agent Schedules.
       b. Open the agent schedule of each node on which you want to run the agent.
       c. Check Enable this agent and ensure that each individual agent is enabled.
       d. Click Save.
Step2) Update the Pega-RULES Agent Schedule on each active node.
       a. Open the agent schedule and select the Security tab.
       b. Set the Access Group to PegaNBAM:Agents.
       c. Ensure that the Bypass Activity authentication checkbox is selected.
 
After making the above changes the Agents should be running when verified in the System Management Application. With the above changes, Segment run completed successfully.

Suggest Edit

Published March 3, 2016 - 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