View of the Object Log Table: QryLogObjects[V] - Teradata Database

Teradata Database Administration

Teradata Database
Release Number
English (United States)
Last Update
Product Category

With the WITH OBJECTS option, DBQL logs one row in DBQLObjTbl and the associated view, QryLogObjects[V], for each data object referenced by the query. An object can be a database, data table, column, secondary index, join index, or journal table. (If the object is a secondary index, its number is logged rather than a name.) DBQL gets the use counts from the Optimizer and not the SQL statement itself. The system logs a count of the number of times the Optimizer accessed the object.

Note: Any DBC database tables and columns used by the system while processing a query are not reflected in the DBQL object rows for that query. This means, for example, that statements like CREATE TABLE or SELECT FROM will not have objects logged through DBQL because they deal with DBC tables and columns.

The following table lists the fields populated in the object log view.


QryLogObjects[V] Field



Time that the rows were written to the database.

For more information on CollectTimeStamp, see “Comparing CollectTimeStamp Value Between Tables” on page 380.


Number of times the object was accessed, as determined by the Optimizer, to process the query.


Name of the column. Or if the ObjectType is 'Idx' or Index, this field returns the name of the column associated with the index.

Some queries will not provide a name, such as COLLECT STATISTICS.

For multicolumn indexes, there will be one additional row for each column in the index and each row will have the same object number.


Name of the database that owns the target object.


Unique internal identifier of this object.


Number of the column or secondary index.


Name of the table or view.


Character code indicating the type of object targeted.

For the possible values for this column, see “Chapter 15 ObjectType.”


Unique processor ID of the Dispatcher and part of the multi-column NUPI (see also CollectTimeStamp).


Internally generated identifier of the query.


Describes the use of the object. TypeOfUse contains the following numerical values:

  • 1 = Found in the resolver
  • 2 = Accessed during query processing
  • 4 = Found in a conditional context
  • 8 = Found in inner join condition
  • 16 = Found in outer join condition
  • 32 = Found in a sum node
  • 64 = Found in a full outer join condition
  • More than one of these values can be used.