Plan, execute, measure and optimize customer experiences

SAS Marketing Optimization - Troubleshooting Failure of Optimization Scenario

Reply
New Contributor
Posts: 4

SAS Marketing Optimization - Troubleshooting Failure of Optimization Scenario

[ Edited ]

Hello,

 

We are trying to setup MO in our company and i am running some tests on creating campaign groups and some Optimization scenarios. Since yesterday i am facing an issue where we i execute an optimization scneario it goes into submitted state and never finishes. When i cancel the optimization the below error shows up in  the log. Optimizing scenarios was working fine before yesterday, but i am unable to find what is causing the below issue. 

 

Optimizing scenarios works in the DEV environment which seems to suggest this is more environmental. Any pointers on where to look would be appreciated.

 


NOTE: There were 1 observations read from the data set MOMETA.OPTIMIZATION_JOBS.
NOTE: The data set MOMETA.OPTIMIZATION_JOBS has been updated. There were 1 observations rewritten, 0 observations added and 0
observations deleted.
NOTE: There were 1 observations read from the data set WORK.OPTIMIZATION_JOBS.
NOTE: DATA statement used (Total process time):
real time 0.01 seconds
cpu time 0.01 seconds

NOTE: PROCEDURE SQL used (Total process time):
real time 0.00 seconds
cpu time 0.00 seconds


NOTE: There were 1 observations read from the data set MOMETA.SCENARIOS.
NOTE: The data set MOMETA.SCENARIOS has been updated. There were 1 observations rewritten, 0 observations added and 0 observations
deleted.
NOTE: There were 1 observations read from the data set WORK.SCENARIOS.
NOTE: DATA statement used (Total process time):
real time 0.01 seconds
cpu time 0.01 seconds

 

MO MAIN .................................. Start Time 16:06:39
Initialization ........................... Start Time 16:06:39

3 The SAS System 16:06 Monday, May 1, 2017

Entering optimization code hook preprocess_during_load_batch

Checking for Optimisation Flag
74 Records Identified from WORK.COMMUNICATIONS as Required Campaigns
74 Records Identified from CI_CDM.CI_CELL_PACKAGE as Published Campaigns
All Required Campaigns are published. Continuuing to check Optimise Flag
Finished Checking for Optimisation Flag
Optimisation Flag is set to Y. Performing Preprocessing Code Hook.
Starting Preprocess Budget Constraints
Identified 1 Active Budget Constraints from VHA_MO_BUDGETS to be included.
WARNING: Multiple lengths were specified for the BY variable constraint_id by input data sets. This might cause unexpected results.
0 Active Budget Constraints Matched with Constraint_IDs in WORK.Constraints.
1 Active Budget Constraints unmatched.
Ending Preprocess Budget Constraints

Exiting optimization code hook preprocess_during_load_batch

WARNING: Sensitivity analysis will not be run since no constraints have been flagged for sensitivity analysis.
WARNING: Multiple lengths were specified for the variable Campaign_Type by input data set(s). This can cause truncation of data.

WARNING: Objective measure Expected_Offer_Profit will be added to the solution table because it is needed to compute the offer
summary.

WARNING: ROI denominator measure Offer_Cost will be added to the solution table because it is needed to compute the offer summary.
.......................................... End Time 16:06:47
Generate Constraints ..................... Start Time 16:06:47
.......................................... End Time 16:06:47
Generate Contact Policies ................ Start Time 16:06:47
WARNING: Multiple lengths were specified for the variable Campaign_Type by input data set(s). This can cause truncation of data.
WARNING: All contact policies are redundant. Contact history will be ignored.
.......................................... End Time 16:06:48
Create Optimization Data ................. Start Time 16:06:48
.......................................... End Time 16:06:48
Create Contact Policy Assignments ........ Start Time 16:06:48
.......................................... End Time 16:06:48
MO Proc .................................. Start Time 16:06:48

ERROR: An exception has been encountered.
Please contact technical support and provide them with the following traceback information:

The SAS task name is [MO (2) ]
Segmentation Violation

Traceback of the Exception:

/opt/sas/sw/SASHome/SASFoundation/9.4/sasexe/sas() [0x52815e]
/opt/sas/sw/SASHome/SASFoundation/9.4/sasexe/sas() [0x41f0ee]
/opt/sas/sw/SASHome/SASFoundation/9.4/sasexe/tkmk.so(bkt_signal_handler+0x144) [0x7f9c87e405d4]
/lib64/libpthread.so.0() [0x31e080f7e0]
/opt/sas/sw/SASHome/SASFoundation/9.4/sasexe/mo(moReadCustData+0x18c0) [0x7f9c236788d0]
/opt/sas/sw/SASHome/SASFoundation/9.4/sasexe/mo(moReadData+0x10c7) [0x7f9c2366eff7]
/opt/sas/sw/SASHome/SASFoundation/9.4/sasexe/mo(mo+0x650) [0x7f9c2366c7d0]
/opt/sas/sw/SASHome/SASFoundation/9.4/sasexe/sas(vvtentr+0x101) [0x41ed01]
/lib64/libpthread.so.0() [0x31e0807aa1]
/lib64/libc.so.6(clone+0x6d) [0x31e04e8aad]

WARNING: The data set WORK.PROC_SOLUTION_1 may be incomplete. When this step was stopped there were 0 observations and 0 variables.
WARNING: The data set WORK.MO_SUMMARY_1 may be incomplete. When this step was stopped there were 0 observations and 0 variables.
4 The SAS System 16:06 Monday, May 1, 2017

WARNING: The data set WORK.MO_DUAL_1 may be incomplete. When this step was stopped there were 0 observations and 0 variables.
WARNING: The data set WORK.MO_SENSITIVITY_1 may be incomplete. When this step was stopped there were 0 observations and 0
variables.
WARNING: The data set WORK.MO_INFEASIBLE_1 may be incomplete. When this step was stopped there were 0 observations and 0 variables.
WARNING: The data set WORK.MO_SCORE_CODE_1 may be incomplete. When this step was stopped there were 0 observations and 0 variables.
WARNING: The data set WORK.DATA1 may be incomplete. When this step was stopped there were 0 observations and 0 variables.

NOTESmiley Sadmo_stpstatus) 16:06:48 Return package name-value pairs: status=SUCCESS*error_code=0


NOTESmiley SadMO_OPTIMIZE_EXECUTE) 16:06:48 --- END (elapsed= 0:00:10.83, rc=0)
================================================================================

 

SAS Employee
Posts: 9

Re: SAS Marketing Optimization - Troubleshooting Failure of Optimization Scenario

David,

You mention the scenario was working yesterday, was it working in the DEV environment or was it working in the new PROD environment?

Has the campaign group (including the optimization of the scenario) ever completed in DEV, in PROD?

As you know, the key is to figure out what is new and what changed fromt the time when everything was running okay to the time when the problem occurred.

Can you check that you have the same inputs to the optimization in this new scenario compared to the old one? Do you have the same counts comming from the MA campaigns, the same setting for the MA communication nodes, same settings in the Campaign group, are the analytical scores non-empty? Is the offer_cost ALWAY different from zero? IF all of those are the same as before, then please open a tech support track.

 

 

New Contributor
Posts: 4

Re: SAS Marketing Optimization - Troubleshooting Failure of Optimization Scenario

Hi Patricia,

 

thanks for your reply. We are currently still in our TEST environment and the solution has not been promoted yet in PROD. The scenario was actiually working in the Test environment and stopped working a couple of days later. 

As this is a test environment the underlying data and scores did not change.

 

The counts from the campaigns and the input data set has not changed. i will verify the cost related values again.

SAS Employee
Posts: 70

Re: SAS Marketing Optimization - Troubleshooting Failure of Optimization Scenario

A seg fault like that is an issue that you'll really need to address with technical support; it's very unlikely this is caused by your input data or scenario. Often there are hotfixes or environmental changes that are needed to address that kind of low-level error, and I'm certain they'll be able to help you with that!

New Contributor
Posts: 4

Re: SAS Marketing Optimization - Troubleshooting Failure of Optimization Scenario

That was the quick guess i got from SAS TS, but unfortunately the hotfix is not available for 6.4(our version). SAS TS are still looking at the logs to see if it is data or config related.

Ask a Question
Discussion stats
  • 4 replies
  • 131 views
  • 0 likes
  • 3 in conversation