SUPPORT / SAMPLES & SAS NOTES
Problem Note 59648: The SAS® 360 Discover ECV ETL can fail, in rare instances, when the matching process does not label a website visitor the same as before
 |  |  |  |  |
When there is a website visitor to a customer's webpage, the main matching process labels the visitor as a customer who has a cookie or a customer who does not have a cookie. In rare cases, a website visitor is labeled as a visitor with a cookie. But later, in another session, that same visitor is labeled as a visitor without a cookie. If this mismatch occurs, the following error is produced in the SAS 360 Discover extended customer view's (ECV) extract, transform, and load (ETL) process:
"ERROR:""Could not read ECVDATA.SESSION_X_CUSTOMER for customer_sk= .."
"ERROR:""Message was ERROR: No matching observation was found in MASTER data set.
. _iorc_ was 1230015. Aborting."
_last_=0 session_csk=209319960 VISITOR_ID=b6adb2309c4a4bcab398a36cf3f66899 load_dttm=15NOV2016:01:41:30.253000 FIRST.VISITOR_ID=1
LAST.VISITOR_ID=0 ACCOUNT_ID= ADDRESS_LINE1_TXT= ADDRESS_LINE2_TXT=
ADDRESS_LINE3_TXT= ADDRESS_LINE4_TXT= BUSINESS_EMAIL_TXT=
CITY_NM= COUNTRY_NM= COOKIE_ONLY_FLG=Y DAYTIME_PHONE_NO= DATE_OF_BIRTH=
EVENING_PHONE_NO= FIRST_NM= GENDER_CD= LAST_NM=
MIDDLE_NM= MOBILE_PHONE_NO= POSTAL_CD= PRIMARY_EMAIL_TXT= PRIVATE_EMAIL_TXT=
TITLE_NM= USER_ID= COMPANY_NM= INDUSTRY_NM=
STATE_REGION_NM= FACEBOOK_USER_NM= TWITTER_USER_NM= LINKEDIN_USER_NM=
GOOGLEPLUS_USER_NM= FACEBOOK_USER_ID=
GOOGLEPLUS_USER_ID= match_operand_code=14
match_operand_hash=)?l???_?Pa?custMatch= batchNo=. customer_sk=.
next_customer_dimension=103738382 newAdd=Y incoming_sas_customer_dimension=-99
insert_dttm=. _outer_iorc_=0 maxDateTime=0
mcustomer_sk=44664695 update_dttm=04NOV2016:10:57:10.036000 errmsg=ERROR: No
matching observation was found in MASTER data set.
_put_rec_="ERROR:""Message was ERROR: No matching observation was found in MASTER data set.
"ERROR:""Message was ERROR: No matching observation was found in MASTER data set.
. _iorc_ was 1230015. Aborting."
_last_=0 session_csk=209319960 VISITOR_ID=b6adb2309c4a4bcab398a36cf3f66899 load_dttm=15NOV2016:01:41:30.253000 FIRST.VISITOR_ID=1
LAST.VISITOR_ID=0 ACCOUNT_ID= ADDRESS_LINE1_TXT= ADDRESS_LINE2_TXT=
ADDRESS_LINE3_TXT= ADDRESS_LINE4_TXT= BUSINESS_EMAIL_TXT=
CITY_NM= COUNTRY_NM= COOKIE_ONLY_FLG=Y DAYTIME_PHONE_NO= DATE_OF_BIRTH=
EVENING_PHONE_NO= FIRST_NM= GENDER_CD= LAST_NM=
MIDDLE_NM= MOBILE_PHONE_NO= POSTAL_CD= PRIMARY_EMAIL_TXT= PRIVATE_EMAIL_TXT=
TITLE_NM= USER_ID= COMPANY_NM= INDUSTRY_NM=
STATE_REGION_NM= FACEBOOK_USER_NM= TWITTER_USER_NM= LINKEDIN_USER_NM=
GOOGLEPLUS_USER_NM= FACEBOOK_USER_ID=
GOOGLEPLUS_USER_ID= match_operand_code=14
match_operand_hash=)?l???_?Pa?custMatch= batchNo=. customer_sk=.
next_customer_dimension=103738382 newAdd=Y incoming_sas_customer_dimension=-99
insert_dttm=. _outer_iorc_=0 maxDateTime=0
mcustomer_sk=44664695 update_dttm=04NOV2016:10:57:10.036000 errmsg=ERROR: No
matching observation was found in MASTER data set.
_put_rec_="ERROR:""Message was ERROR: No matching observation was found in MASTER data set.
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 Customer Intelligence 360 | N/A | 1.0 | |||