SUPPORT / SAMPLES & SAS NOTES
Problem Note 67428: A failure occurs when you upload or refresh input data and you run an optimization via the sasmolauncher utility in SAS® Marketing Optimization
 |  |  |  |  |
In SAS Marketing Optimization, a failure might occur when you either upload or refresh input data and you follow that by running the optimization step in batch via the sasmolauncher utility. This failure happens intermittently.
When the failure occurs, the following exception is displayed in the SASMarketingOptimization6.6.log:
2021-01-13 13:46:46,961 ERROR [tomcat-http--61] [efbe027b5deaf67a:5d80c930:176fb905527:-534c] [sasdemo] com.sas.analytics.mo.db.InputDataDB
- java.lang.NullPointerException
at com.sas.analytics.mo.db.InputDataDB.getInputDataAuthorizationLevel(InputDataDB.java:4695)
at com.sun.proxy.$Proxy481.getInputDataAuthorizationLevel(Unknown Source)
at com.sas.analytics.mo.db.ScenarioDB.getNextScenarioConcise(ScenarioDB.java:3519)
at com.sas.analytics.mo.db.ScenarioDB.getScenarioConciseList(ScenarioDB.java:2962)
at com.sun.proxy.$Proxy778.getScenarioConciseList(Unknown Source)
at com.sas.analytics.mo.db.DBQueryManager.getScenarioConciseList(DBQueryManager.java:325)
at com.sas.analytics.mo.services.impl.ScenarioServiceImpl.getScenarioConciseList(
ScenarioServiceImpl.java:3227)
- java.lang.NullPointerException
at com.sas.analytics.mo.db.InputDataDB.getInputDataAuthorizationLevel(InputDataDB.java:4695)
at com.sun.proxy.$Proxy481.getInputDataAuthorizationLevel(Unknown Source)
at com.sas.analytics.mo.db.ScenarioDB.getNextScenarioConcise(ScenarioDB.java:3519)
at com.sas.analytics.mo.db.ScenarioDB.getScenarioConciseList(ScenarioDB.java:2962)
at com.sun.proxy.$Proxy778.getScenarioConciseList(Unknown Source)
at com.sas.analytics.mo.db.DBQueryManager.getScenarioConciseList(DBQueryManager.java:325)
at com.sas.analytics.mo.services.impl.ScenarioServiceImpl.getScenarioConciseList(
ScenarioServiceImpl.java:3227)
In addition, the scheduled job flow exits with a return code of 1, as shown below:
Launcher complete...1
21/01/13 13:46:53 Job xxx exited 1
21/01/13 13:46:53 Flow xxx exiting 1
21/01/13 13:46:53 Job xxx exited 1
21/01/13 13:46:53 Flow xxx exiting 1
If you re-execute the scheduled job, it should complete successfully.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Marketing Optimization | Microsoft® Windows® for x64 | 6.6 | |||
| 64-bit Enabled AIX | 6.6 | |||||
| 64-bit Enabled Solaris | 6.6 | |||||
| Linux for x64 | 6.6 | |||||