↧
Channel:
Teradata Developer Exchange - Blog activity for carrie's blog
X
Are you the publisher?
Claim or
contact us
about this channel.
X
0
Channel Details:
- Title: Teradata Developer Exchange - Blog activity for carrie's blog
- Channel Number: 4274858
- Language: English
- Registered On: September 10, 2012, 9:21 pm
- Number of Articles: 1058
- Latest Snapshot: June 6, 2019, 4:01 am
- RSS URL: http://developer.teradata.com/blog/carrie/rss.xml
- Publisher: http://downloads.teradata.com/blog/carrie
- Description:
- Catalog: //teradata138.rssing.com/catalog.php?indx=4274858
© 2025 //www.rssing.com
Hi Carrie,
Today i noticed an interesting case where SessionWDID=WDID=FinalWDID=Same Workload id number.
We have parser only workload, let us say the WDID of PARSER-only workload=1.
For one of the sessions procedure CALL statement, i am seeing the SessionWDID=1, WDID=1, and FINALWDID=1.
I am seeing this behavior with statementype=Call, and also statementtype=Check Workload (specifically Check workload for begin mload).
I am kind of confused why these 2 statetementtypes are showing 3 types of WDIDs as PARSER-only workload.