Problem Note 58482: The SAS® 360 Discover ETL Reset job fails the first time it is run and it does not always work reliably the next time you run it
 |  |  |  |  |
When the SAS 360 Discover extract, transform, and load (ETL) Reset job fails on first execution, it does not always work reliably the next time it is executed. The SAS 360 Discover warehouse contains certain control tables. If those tables are deleted in the first failed job run, the job does not try to delete those tables from the warehouse the next time you run the job.
As a workaround for this problem, you can run the DELETE statements shown below directly in Oracle SQL Developer. For PostgreSQL, wrap the DELETE statements in the SQL procedure shown below so that you can submit the code in SAS®.
proc sql;
connect to postres as con1 (dbmax_text=4000 database=cxtwh serve=ci64cxt.unx.sas.com port=10463
authdomain=CXTDataBaseAuthDomain);
execute (delete from business_process_step_details where load_dttm not in (select load_dttm from load_history);
delete from business_process_x_exception where load_dttm not in (select load_dttm from load_history);
delete from cart_activity_detail_fact where load_dttm not in (select load_dttm from load_history);
delete from cxa_custom_attributes where load_dttm not in (select load_dttm from load_history);
delete from cxt_error_log where load_dttm not in (select load_dttm from load_history);
delete from detail_fact where load_dttm not in (select load_dttm from load_history);
delete from detail_fact_ext where load_dttm not in (select load_dttm from load_history);
delete from detail_x_document where load_dttm not in (select load_dttm from load_history);
delete from detail_x_int_promotion_display where load_dttm not in (select load_dttm from load_history);
delete from detail_x_int_promotion_use where load_dttm not in (select load_dttm from load_history);
delete from detail_x_in_page_error where load_dttm not in (select load_dttm from load_history);
delete from detail_x_product where load_dttm not in (select load_dttm from load_history);
delete from form_detail where load_dttm not in (select load_dttm from load_history);
delete from goal_x_session where load_dttm not in (select load_dttm from load_history);
delete from media_detail where load_dttm not in (select load_dttm from load_history);
delete from media_x_session where load_dttm not in (select load_dttm from load_history);
delete from order_detail_fact where load_dttm not in (select load_dttm from load_history);
delete from order_summary_fact where load_dttm not in (select load_dttm from load_history);
delete from profile_x_session where load_dttm not in (select load_dttm from load_history);
delete from search_results where load_dttm not in (select load_dttm from load_history);
delete from session_attribution where load_dttm not in (select load_dttm from load_history);
delete from session_fact where load_dttm not in (select load_dttm from load_history);
delete from social_action_x_detail where load_dttm not in (select load_dttm from load_history);
delete from social_network_user_x_session where load_dttm not in (select load_dttm from load_history);
) by con1;
disconnect from con1;
quit;
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Customer Intelligence 360 | N/A | 1.0 | |||
A fix for this issue for SAS Customer Experience Targeting Server 6.4 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/Y67.html#58482| Type: | Problem Note |
| Priority: | medium |
| Date Modified: | 2016-06-23 10:29:15 |
| Date Created: | 2016-06-23 08:44:28 |