WDName is 'Unassigned' in PDCRINFO.DBQLOGTBL_HST when the WDID is NULL in DBC.DBQLOGTBL.
WDID is NULL for the TASM bypassed users by design. Generally in many client places, TDWM, DBC, VIEWPOINTUSER(optional) will be bypassed. So these ID sessions will be logged under UNASSIGNED WLName.
In addition, queries like: 'sel database','BT','ET','help session'..will not be assigned with a workload.
I got exactly same situation. As Geeta mentioned, I checked at my end and I do not see any of those conditions (like user DBC, TDWM and etc; help, show.. My requests are data extract SQLs ). Requests on Teradata are delayed when there is no WDID assigned.
Have you figured it out any solution or the reason? Can you please share your recent findings?
This may help explain.
I log K's/ day , all have 0 ampcputime, many do have small parsercputime.
- all the unassigned ones are on the 24th, the ones with a WD are on the 23rd. Did a change to TASM settings occur?
- all the unassigned ones have 0 cpu time and 0 execution time. This suggests that they were parser only - an error? prepare? condition in the query that was known by the parser to result in no rows qualifying?