0 - 20 of 20 tags for tdwm

Am looking for some insights on setting appropriate CPU Skew Exceptions using Workload Designer.  Current VP version 15.11, Teradata 15.0.

If you are user DBC or user TDWM and you log onto a Teradata Database, you might get treated somewhat differently than other users.  This posting describes what user DBC and user TDWM do, some of the special things about them, and when you can expect them to get treated differently.   We’ll also look at any implications in setting up workload management for these two special users.

I am a Teradata user rather than developer. My team uses SAS (9.4, windows desktop SAS) to access Teradtata (version 14) via the SAS SQL pass-through.  In the past few months we have begun receiving errors from Teradata similar to these:

Hi - We have a Active-active setup and are looking for options in case of a failover. I wasnt sure where to start, can experts help me with suggestions please?

Hi all. I have a requirement to generate reports based on our operating windows via DBQL. As the operating windows are subject to change, I would like to use the OpEnvName field that is populated via the PDCR process.

Can someone provide a description of the fields delayedcount and delayedqueries in the table DBC.TDWMSummaryLog? What's the difference between them?


In non-VM Teradata we used to have the 'Teradata Dynamic Workload Manager' setup in the 'Teradata Tools and Utilities' media.
The Teradata VM for Linux consists of a prepackaged Teradata installation where I could not find TDWM nor any way to configure/install it. Any idea on how to proceed?
FYI: We are using Teradata 13 VM 40Gb

Hello Masters,

Is there any way to find out who, when and what changes done in TDWM/TASM rule set? We have DBQL enabled for user TDWM but DBQL is showing most of stored procedure call statement. It is not straight forward to analyze that data.

Any suggestion? I need to check it for TD13 as well as TD13.10 systems.

-- Shrinivas

Hi, we have just upgraded our Teradata system from 13.0 to 13.10 and installed Viewpoint for the first time, running version 14.0.

Teradata's Workload Management offerings have drastically changed over the past few years.  Further, not only has the functionality changed, but the product delivery mechanisms have changed as well.  This blog entry will focus on these delivery mechanisms, and how they have changed.

This workshop is led by a Sr. Professional Services expert who has delivered successful TASM & priority scheduler implementations. Priority scheduling concepts, TASM set up, Teradata Dynamic Systems Management, best practices when assigning priorities, and Teradata Manager monitoring tools are covered. The most common problems that must be corrected before TASM is turned on are also discussed. A sample mixed workload problem is used to illustrate the steps needed to analyze and correct the problem, such as DBQL inspection, capacity analysis, and query tuning. The session emphasizes real world best practices, tips, and traps. This education isn’t found in books -- it only comes from top experts.

Long before TASM, there were throttles.  We call them “system throttles” or “object throttles” today in order to differentiate them from TASM’s workload throttles.

For those not already familiar with the Teradata Workload Analyzer (TWA), TWA is one of the products affiliated with TASM (Teradata Active System Management).

TDWM is working and TASM is enabled on the system. I can see WDID in the DBQLogTbl however the OpeEnvId and SysConId are null. How can this be possible?
I think that when appropriate SysCon and OpEnv aren't selected then the 'Base' state is selected, which is comprised of 'Normal' SysCon and 'Always' OpEnv.

CreateDate and RemoveDate are two fields in many of the tables related to TDWM e.g. in WlcDefs. The values and their meanings (according to me) are like:

1100301 - 2010/03/01 1091114 - 2009/11/14

What does the first '1' represent in these date fields? and is my interpretation correct?

We have begun discussions on the next candidate products for transition to Teradata Viewpoint. As you may already know, complete feature equivalence of Teradata Manager and Teradata Dynamic Workload Manager (TDWM) in Viewpoint will be realized in 1H2010.

We have installed Teradata on Windows machine. Now on running Database Setup and providing the following information (in the WIndows GUI):
Database Name : db1
Super User: DBC
Super User Password: dbc
Console Password: dbc
Set up DB for Teradata Manager: Yes
Perm Space: 100 MB
Spool Space: Same as Parent

Create a Teradata Manager User: Yes
User Account String: $H-DBC-MANAGER
User Password: dbcmngr
Perm Space: 100MB
Spool Space: Same as Parent
Give user privilages to run: Selected all options in combo
Migrate TDQM Database: Yes

Chances are that if you’re into workload management at all, your using at least one throttle. Maybe you are using more. On the other hand, maybe you’re just thinking about it. Object Throttles (as opposed to Workload Throttles) allow you stray from the straight and narrow, because they offer you an array of options and can be used creative combinations.