The available fields in a DBQLogTbl row are listed in the following table.
|AbortFlag||If the query being logged was aborted, the collected
data could be incomplete.
A query consisting of a multistatement or iterated request with simple INSERT statements can be successful and yet have statement errors, as indicated by the ErrorCode column.
|AcctString||The account string at the time the row was
committed. Because accounts can be changed dynamically at the query
or session level, this may not be the same account that:
|AcctStringDate||Value of the expanded &D ASE code in the account
string. If none exists, the value is denoted with a “?” and is
Even if ASE truncates the expanded account string, DBQL will report the full value. For example, if &D is expanded into position 26 or higher in the account definition and truncation occurs, DBQL will still report the entire value of the date in the AcctStringDate field.
|AcctStringHour||Value of the expanded &H ASE code in the account string. If none exists, the value is denoted with a “?” and is null.|
|AcctStringTime||Value of the expanded &T ASE code in the account
string. If none exists, the value is denoted with a “?” and is
Even if ASE truncates the expanded account string, DBQL will report the full value.
|AMPCPUTime||Total AMP time used for the query in CPU
The I/O, CPU, and spool usage may not be accurate for aborted queries.
|AMPCPUTimeNorm||Normalized AMP CPU seconds for co-existence systems.|
|AppID||Application (executable) or utility name; for example, BTEQ from LogonSource for network clients.|
|CacheFlag||This field is blank if the query is not found in the
request cache. It could also be one of the following:
For more information on specific plans and generic plans, see “Peeking at Parameterized Values in the Data Parcel” in SQL Request and Transaction Processing.
|CalendarName||The name of the business calendar the session uses. Possible values include ISO, COMPATIBLE, and TERADATA (the default).|
|CallNestingLevel||The level of nesting when running in stored procedures.|
|CheckpointNum||The checkpoint number when loading data into an MLOADX staging table. The default is zero.|
|ClientAddr||The client IP address of the submitted query as obtained from Logonsource from a network client.|
|ClientID||The network client user name under which this session is logged (for example, ADMIN) and the PK/FK for the table.|
|CollectTimeStamp||A date and time unique to each buffer cache, which
changes for each new buffer. Part of the multi-column NUPI for the
table (see also ProcID).
This time will be set when the cache is ready to receive new data, not when rows are written to the database.
For more information on CollectTimeStamp, see Comparing CollectTimeStamp Value Between Tables.
|CPUDecayLevel||Contains the most severe decay level reached for CPU usage on any one node for requests using the default Timeshare workload management method. Values are 0, 1, or 2. A value of 0 indicates that the request is running at the default priority. A value of 1 indicates that the priority level is reduced and the resource allotment is halved. A value of 2 indicates that the priority level is reduced again, the resource allotment is halved again, and it will not be reduced more.|
|DataCollectAlg||CPU/IO collection algorithm used by DBQL. Possible
|DBQLStatus||Internal DBQL logging status. Zero indicates no status conditions. This field is NULL if you are not using DBQL CPU/IO Collection algorithm 3.|
|DefaultDatabase||Name of the default database for the query.|
|DelayTime||The seconds a query was delayed by the Teradata dynamic workload management software.|
|DisCPUTime||Dispatcher CPU time in seconds.|
|DisCPUTimeNorm||Dispatcher normalized CPU time in seconds.|
|ErrorCode||If greater than 0, this field is the number of the error message in ErrorText. This field contains a code if the query caused a Parser syntax error.|
|ErrorText||If not null, this field provides processing errors and Parser errors. For example, the text would explain that the query was not processed due to a Parser syntax error.|
|EstMaxRowCount||The largest number of rows handled by a single step in the query, as estimated by the Optimizer.|
|EstProcTime||Sum of minimum estimated processing time for steps
in the query as generated by the Optimizer.
This time is reported in seconds.
|EstResultRows||Estimated result rows as generated by the Optimizer.|
|ExceptionValue||Specifies what type of Teradata dynamic workload management software exception occurred.|
|ExpandAcctString||The expanded account name under which the query is
submitted if account expansion is invoked.
The &I, which gives the host, session, and request number for the query is different for a stored procedure call. For stored procedure calls, the request number is the client request number which is the request of the CALL statement.
|FeatureUsage||A bitmap of which features are used by the SQL request. Reports features visible on PEs only. Does not report features visible on AMPs only.|
|FinalWDID||Indicates the workload definition in which the query completed execution.|
|FinalWDName||Final workload name of the utility job.|
|FirstRespTime||The timestamp when the first response packet is sent to the client unless the request is held by TASM to meet the minimum response time. In this case, it is the timestamp when the first response packet is ready to be sent to the client.|
|FirstStepTime||The timestamp when the first step is dispatched.|
|FlexThrottle||Whether TASM released the request because of dynamic (flex) throttles, which relax workload throttle limits when the system is less busy. If flex throttles released the request, the value is T. If not, the value is NULL.|
|InternalRequestNum||The internal request number.
For commands, other than those within a stored procedure, the internal request number and the number in the RequestNum field will be the same.
For stored procedures invoked within a session, the internal request number increments by 1 for every request made by the stored procedure. This means that RequestNum will be the request number of the CALL and the value in InternalRequestNum will continue to increment for all other queries issued by the session.
|IODecayLevel||Contains the most severe decay level reached for I/O usage on any one node for requests using the default Timeshare workload management method. Values are 0, 1, or 2. A value of 0 indicates that the request is running at the default priority. A value of 1 indicates that the priority level is reduced and the resource allotment is halved. A value of 2 indicates that the priority level is reduced again, the resource allotment is halved again, and it will not be reduced more.|
|IterationCount||The number of data rows used by a parameterized request.|
|KeepFlag||Whether the response parcel should be kept until the client responds that it is no longer needed. The value is either Y or N.|
|LastRespTime||The timestamp of the last response. This field is NULL if you are not using DBQL CPU/IO Collection algorithm 3.|
|LastStateChange||Time of the last State change by the Teradata dynamic workload management software.|
|LockDelay||Maximum wait time to get a lock on an object in centiseconds. The maximum value is 32,767 centiseconds.|
|LockLevel||The highest lock level (Access/Read/Write/Exclusive) for locks associated with this request. For explicit transactions, the lock level for the transaction. Does not include row hash locks.|
|LogicalHostID||Unique identifier of the logon source for the logged query. A value of 0 indicates an internal session.|
|LogonDateTime||The timestamp of the start of the session.|
|LogonSource||The logon source string text.|
|LSN||The Logon Sequence Number used for a load utility.|
|MaxAMPCPUTime||CPU seconds of the highest CPU utilized AMP in the query.|
|MaxAMPCPUTimeNorm||Normalized maximum CPU seconds for an AMP.|
|MaxAmpIO||Logical I/O count of the highest utilized AMP in the query.|
|MaxAmpsMapNo||The map number with the maximum number of AMPs.|
|MaxCPUAmpNumber||The number of the AMP with the highest CPU activity.|
|MaxCPUAmpNumberNorm||Number of the AMP with the maximum normalized CPU seconds for co-existence systems.|
|MaxIOAmpNumber||The number of the AMP with the highest I/O usage for this step.|
|MaxNumMapAMPs||The number of AMPs in the largest map used by the request.|
|MaxOneMBRowSize||Actual size in bytes of the largest 1 MB row in the set of rows returned for the query.|
|MaxStepMemory||The maximum amount of memory in MBs used by any one AMP in any step in this request. This field can be compared with the TDWM estimated memory usage field, TDWMEstMemUsage, also in DBQLogTbl. This field does not apply to INSERT/UPDATE/DELETE requests.|
|MaxStepsInPar||The maximum number of Level 2 steps done in parallel for the query.|
|MinAmpCPUTime||CPU seconds of the lowest CPU utilized AMP in the query.|
|MinAmpCPUTimeNorm||Normalized minimum CPU seconds for an AMP.
Normalized columns, such as MinAmpCPUTimeNorm, are for co-existence systems only.
|MinAmpIO||Logical I/O count of the lowest logical I/O utilized AMP in the query.|
|MinNumMapAMPs||The number of AMPs in the smallest contiguous map used by this request.|
|MinRespHoldTime||The number of seconds the query was held to meet the TASM minimum response time.|
|NoClassification||Indicates if the query was not classified.|
|NumAmpsImpacted||The number of AMPs impacted by the request.|
|NumFragments||For a request for which a dynamic plan is generated, this field indicates the number of plan fragments. For a static plan, this field is NULL.|
|NumOfActiveAmps||Number of AMPs active for the query. Use it to compute the average CPU or I/O per AMP.|
|NumRequestCtx||The number of request contexts associated with the session.|
|NumResultOneMBRows||The number of 1 MB rows in the set of rows returned for the query.|
|NumResultRows||The total number of rows returned for the query.|
|NumSteps||Total number of Level 1 steps required to process
the query. The value is 0 if:
|NumStepswPar||Total number of Level 1 steps with parallel steps.|
|OpEnvID||The internal identifier of the Operating Environment / Planned Environment currently enforced by the Teradata dynamic workload management software.|
|OpEnvName||Operating environment name of the utility job.|
|ParamQuery||Indicates if the request contains any parameterized query.|
|ParserCPUTime||Total Parser and Dispatcher CPU seconds used for the query.|
|ParserCPUTimeNorm||Normalized parser CPU seconds for co-existence systems.|
|ParserExpReq||Seconds the parser waited on an express request.|
|PersistentSpool||The persistent portion of the DBQLogTbl.SpoolUsage column.|
|ProcID||Unique processor ID of the Dispatcher and part of the multi-column NUPI for the table (see also CollectTimeStamp).|
|ProfileID||The name of the profile, if any, under which the user submitted the query.|
|ProfileName||Profile name of the user who submitted the query.|
|ProxyRole||The rolename of a proxy connection.|
|ProxyUser||The username of a proxy connection.|
|ProxyUserID||The ID of the ProxyUser being charged for spool and temp space. If the field is NULL, the session user ID was used for spool and temp space.|
|QueryBand||The query band under which the query is
Possible values include:
|QueryID||Internally generated identifier of the query and the
FK to other DBQL tables.
QueryID is a system-wide unique field; you can use QueryID to join DBQL tables or the DBC.TdwmExceptionLog table with DBQL tables without needing ProcID as an additional join field.
|QueryRedriven||Whether the query was redriven if redrive protection
was enabled. Possible values are:
|QueryText||The first characters of the SQL query. Up to 200
characters are captured by default.
If you use the LIMIT SQLTEXT option, you can specify that the first n characters be captured where n is 0-10000.
|RedriveKind||Whether the query has redrive protection. Possible
|RemoteQuery||Indicates if the request contains a remote query to the foreign server.|
|ReqIOKB||Total logical I/O usage in kilobytes.|
|ReqMaxSpool||The maximum spool space used by the request, determined at the end of each step.|
|ReqPhysIO||The number of physical I/Os.|
|ReqPhysIOKB||Total physical I/O usage in kilobytes.|
|RequestMode||Request mode from parcel request processing option:
|RequestNum||Unique identifier of the query.
The request number for the commands that occur within a stored procedure CALL statement will all appear as the same number of the CALL statement itself. For more information on request numbers for stored procedures, see note for ExpandAcctString.
|ResponseTimeMet||Indicates if the query met service level goals.|
|SeqRespTime||Sum of the response time of all steps as if they had been executed sequentially, in seconds.|
|SessionID||Unique session identifier.|
|SessionTemporalQualifier||When a DML or SELECT request refers to a temporal table but omits a temporal qualifier, the system uses the value of the session temporal qualifier. This is the session temporal qualifier in effect when the query is logged. For more information on the qualifier, see ANSI Temporal Table Support and Temporal Table Support.|
|SessionWDID||Workload ID class associated with the session. It determines the priority of the session when the TDWM workload classification is active.|
|SessionWDName||Session workload name of the utility job.|
|SpoolUsage||If you are using algorithm 3 (the DBQLogTbl
DataCollectAlg field= 3), the peak spool usage in bytes for any step
of the query.
For other algorithms, the maximum amount of spool used while processing the query.
If SpoolUsage is 0, then there is no usage. If it is null, the data on usage was not valid.
|StartTime||The timestamp when the query is submitted.|
|StatementGroup||If there is a DDL statement in a request,
StatementGroup reports which type:
If the statement has only one DML statement or multiple DML statements that are all of the same type, StatementGroup will indicate the type. For example if there are three DELETE statements in a request, StatementGroup will report:
Similarly, for requests with individual or multiple INSERT, INSERT... SELECT, UPDATE or SELECT statements, StatementGroup will report:
In a multistatement request with different types of DML statements, you will see a list showing the number of statements of each type in the request. For example, a request with one insert and two update statements will appear as:DML Del=0 Ins=1 InsSel=0 Upd=2 Sel=0
|Statements||Number of statements in a request:
|StatementType||The type of statement of the query.
In a multistatement request, this is the last statement of the request. However, this may not accurately describe the request. For more statement information, see StatementGroup.
|SysConID||The internal identifier of the System Condition (SysCon)/ System Health currently enforced by the Teradata dynamic workload management software.|
|SysConName||System condition name of the utility job.|
|SysDefNumMapAmps||The number of AMPs in the system-default map.|
|TacticalCPUException||The number of nodes that had a CPU exception for the request.|
|TacticalIOException||The number of nodes that had an I/O exception for the request.|
|TDWMAllAmpFlag||Indicates whether one of the steps of the query is an all-amp step. This is used to classify a query into a workload definition.|
No longer a TASM rule attribute. The letter 'N' will always be logged.
|TDWMEstLastRows||The estimated last row count generated by the Optimizer used to classify a query into a workload definition.|
|TDWMEstMaxRows||The estimated maximum row count generated by the Optimizer used to classify a query into a workload definition.|
|TDWMEstMaxStepTime||TDWM estimated maximum step time.|
|TDWMEstMemUsage||The estimated memory used by the request (in megabytes). It represents the largest step in the request.|
|TDWMEstTotalTime||The total estimated time of a query by the Teradata
dynamic workload management software (based on Optimizer estimates)
and applied against rules read from the TDWM database.
This time is reported in milliseconds in DBC.DBQLogTbl, but it is reported in seconds in the view DBC.QryLogTDWM[V].
|TDWMRuleID||Rule identifier of the query.|
|ThrottleBypassed||Whether an active request is active solely due to
the ThrottleBypass ruleset attribute. This attribute overrides the
throttle limits if the session owning the request has an object lock
higher than the Access level. Possible values include:
|TnxUniq||The unique value within the transaction number. Other transaction number components (userid, procid) are already in DBQLogTbl. Combined with TxnUniq, these fields represent the complete transaction id for the logged request.|
|TotalFirstRespTime||The total time (in seconds) from when the request was submitted to the time the first response was sent.|
|TotalIOCount||Total logical I/O used by the query.
The I/O, CPU, and spool usage may not be accurate for aborted queries.
|TTGranularity||Possible values include:
For more information, see Temporal Table Support.
|UnitySQL||Time in seconds the stored procedure request was processed by Unity.|
|UnityTime||Time in seconds the stored procedure request was processed by Unity.|
|Usediota||I/O tokens used by the request.|
|UserID||The unique ID of the user whose query is logged.|
|UserName||Name under which the session being logged was initiated.|
|UtilityByteCount||The number of bytes transferred by MultiLoad or FastLoad insertion, updates, or deletions.|
|UtilityInfoAvailable||Indicates whether an SQL request has utility
information available in DBQLUtilityTbl. Possible values include:
|UtilityRowCount||The number of rows inserted, updated, and deleted by MultiLoad or FastLoad for target tables.|
|VHLogicalIO||VERYHOT logical I/O count per query.|
|VHLogicalIOKB||VERYHOT logical I/Os in KB per query.|
|VHPhysicalIOKB||VERYHOT physical I/Os in KB per query.|
|VHPhysIO||VERYHOT physical I/O count per query (VERYHOT cylinder and data block I/Os that were handled by physical disk I/O).|
|WarningOnly||Indicator if the error was only a warning. That is, warning mode.|
|WDID||The workload definition number assigned to the query.|
|WDName||The name of the workload definition assigned to the query.|
|WDOverride||Indicates if the workload definition assignment was overridden.|