Problem Note 38892: Incorrect results occur in SAS® Data Surveyor for Clickstream Data when you perform a Visitor ID completion
Visitor ID completion does not function properly for a multi-log job. Records that should be added (re-headed) to a session are now possibly treated as a separate session.
In a multi-log job scenario, the Clickstream Parse transformation places incoming records into groups so that the Clickstream Sessionize transformation can run in parallel. If a session record does not have a Visitor ID assigned yet, then the record is grouped according to client IP address and user agent. However, this might be a different group than is calculated using the Visitor ID. When the common groups are merged and passed to the Clickstream Sessionize transformation, the combined group might not contain all the records for a session. All the records that are grouped by Visitor ID might be in one group and those that are grouped by client IP address and user agent might be in a different group.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS Data Surveyor for Clickstream Data | Microsoft Windows XP Professional | 2.1_M1 | 2.1_M1 | 9.2 TS2M2 | 9.2 TS2M3 |
Windows 7 Enterprise 32 bit | 2.1_M1 | 2.1_M1 | 9.2 TS2M2 | 9.2 TS2M3 |
Windows 7 Home Premium 32 bit | 2.1_M1 | 2.1_M1 | 9.2 TS2M2 | 9.2 TS2M3 |
Windows 7 Home Premium x64 | 2.1_M1 | 2.1_M1 | 9.2 TS2M2 | 9.2 TS2M3 |
Windows 7 Professional 32 bit | 2.1_M1 | 2.1_M1 | 9.2 TS2M2 | 9.2 TS2M3 |
Windows 7 Professional x64 | 2.1_M1 | 2.1_M1 | 9.2 TS2M2 | 9.2 TS2M3 |
Windows 7 Ultimate 32 bit | 2.1_M1 | 2.1_M1 | 9.2 TS2M2 | 9.2 TS2M3 |
Windows 7 Ultimate x64 | 2.1_M1 | 2.1_M1 | 9.2 TS2M2 | 9.2 TS2M3 |
Windows Vista | 2.1_M1 | 2.1_M1 | 9.2 TS2M2 | 9.2 TS2M3 |
Windows Vista for x64 | 2.1_M1 | 2.1_M1 | 9.2 TS2M2 | 9.2 TS2M3 |
64-bit Enabled AIX | 2.1_M1 | 2.1_M1 | 9.2 TS2M2 | 9.2 TS2M3 |
64-bit Enabled Solaris | 2.1_M1 | 2.1_M1 | 9.2 TS2M2 | 9.2 TS2M3 |
HP-UX IPF | 2.1_M1 | 2.1_M1 | 9.2 TS2M2 | 9.2 TS2M3 |
Linux for x64 | 2.1_M1 | 2.1_M1 | 9.2 TS2M2 | 9.2 TS2M3 |
Solaris for x64 | 2.1_M1 | 2.1_M1 | 9.2 TS2M2 | 9.2 TS2M3 |
Microsoft Windows Server 2008 for x64 | 2.1_M1 | 2.1_M1 | 9.2 TS2M2 | 9.2 TS2M3 |
Windows 7 Enterprise x64 | 2.1_M1 | 2.1_M1 | 9.2 TS2M2 | 9.2 TS2M3 |
Microsoft Windows Server 2008 | 2.1_M1 | 2.1_M1 | 9.2 TS2M2 | 9.2 TS2M3 |
Microsoft Windows Server 2003 for x64 | 2.1_M1 | 2.1_M1 | 9.2 TS2M2 | 9.2 TS2M3 |
Microsoft Windows Server 2003 Standard Edition | 2.1_M1 | 2.1_M1 | 9.2 TS2M2 | 9.2 TS2M3 |
Microsoft Windows Server 2003 Enterprise Edition | 2.1_M1 | 2.1_M1 | 9.2 TS2M2 | 9.2 TS2M3 |
Microsoft Windows Server 2003 Datacenter Edition | 2.1_M1 | 2.1_M1 | 9.2 TS2M2 | 9.2 TS2M3 |
Microsoft® Windows® for x64 | 2.1_M1 | 2.1_M1 | 9.2 TS2M2 | 9.2 TS2M3 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | alert |
Date Modified: | 2010-03-02 15:58:11 |
Date Created: | 2010-03-01 15:52:35 |