Problem Note 56694: The %TKMI_JOB_RO etl_end_service task does not report an error in SAS® Promotion Optimization
 |  |  |  |  |
The SAS® Promotion Optimization %TKMI_JOB_RO etl_end_service task might fail to report errors during processing. When this issue occurs, the etl_end_service task incorrectly reports that it completed successfully and the DDMONYYY_HH_MM_SS_STATUS.log file does not contain entries for batch_prep for each captain.
An example of DDMONYYY_HH_MM_SS_STATUS.log file with the problem follows.
Task Name: etl_end_service Start Time: DDMONYYYY:HH:MM:SS.ss
>ETL end starting.
>Waiting for Cleanup RDBMS Before BATCH OPT/PREP
>Waiting for batch optimization
> ERROR: Plan_sk=xxxxxx
> Failure with DQ: n
> Success with DQ: n
> Min/Avg/Max Units Processed: n/n/n
> Min/Avg/Max Elapse Time(s) : n/n/n
> Total Units Processed: n
> Total Elapse Time(s) : n
>Exceptions occurred during batch optimization
>Waiting for Cleanup RDBMS After BATCH OPT/PREP
>Uploading batch opt/prep results.
>Waiting for batch optimization uploads
>Waiting for rebuild indices after batch uploads
>ETL end complete.
Task Name: etl_end_service End Time: DDMONYYYY:HH:MM:SS.ss
Task Name: etl_end_service Elapsed Time:nseconds
Task Name: etl_end_service Processed Units:n
Task Name: etl_end_service Processed Throughput : nper second
Task Name: etl_end_service Completed Successfully.Continuing to next step.
An example of a normal DDMONYYY_HH_MM_SS_STATUS.log file that does not have the problem follows. Note that each captain has an entry for batch_prep.
Task Name: etl_end_service Start Time: DDMONYYYY:HH:MM:SS.ss
>ETL end starting.
>Waiting for Cleanup RDBMS Before BATCH OPT/PREP
>Waiting for batch optimization
> Success with DQ: n
> Success with DQ: n
> Min/Avg/Max Units Processed: n/n/n
> Min/Avg/Max Elapse Time(s) : n/n/n
> Total Units Processed: n
> Total Elapse Time(s) : n
>Waiting for batch optimization
>grid_captain_name: batch_prep (partition_id= n)
> Prod_Hier_Sks: n
> Success with DQ: n
> Min/Avg/Max Units Processed: n/n/n
> Min/Avg/Max Elapse Time(s) : n/n/n
> Total Units Processed: n
> Total Elapse Time(s) : n
>Waiting for Cleanup RDBMS After BATCH OPT/PREP
>Uploading batch opt/prep results.
>Waiting for batch optimization uploads
>Waiting for rebuild indices after batch uploads
>ETL end complete.
Task Name: etl_end_service End Time: DDMONYYYY:HH:MM:SS.ss
Task Name: etl_end_service Elapsed Time:nseconds
Task Name: etl_end_service Processed Units:n
Task Name: etl_end_service Processed Throughput : nper second
Task Name: etl_end_service Completed Successfully.Continuing to next step.
This occurs when there is at least one plan that fails during batch optimization. The following issues occur when batch preparation does not run:
- The DI_TRANS.GEO_PROD_AGG table might be empty. When the DI_TRANS.GEO_PROD_AGG table is empty, you are not able to add products to promotion plans in the SAS® Merchandise Intelligence Client.
- Category and calendar plans that are set to aggregate during the batch processes are not aggregated.
The workaround for this issue is to look in the MerchIntelGridSvr.log file to determine the cause of the optimization failures and resolve those errors. Once the errors are resolved, rerun the %TKMI_JOB_RO etl_end_service task.
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 Promotion Optimization | Microsoft® Windows® for x64 | 5.2_M4 | 5.4 | 9.3 TS1M2 | 9.4 TS1M1 |
| Linux for x64 | 5.2_M4 | 5.4 | 9.3 TS1M2 | 9.4 TS1M1 | ||
A fix for this issue for SAS Revenue Optimization 5.2_M4 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/P20.html#56694A fix for this issue for SAS Size Optimization 3.2_M4 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/P21.html#56694| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2015-11-18 11:26:40 |
| Date Created: | 2015-10-01 09:04:58 |