Changes to This Book - Teradata Database

Teradata Database Administration

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



Teradata Database Release 15.10

April 2018

Reflected table schema changes in several DBQL topics:

  • Updated the instructions and examples in Shredding the Data in the DBQLXMLLockTbl.
  • Replaced Output of Shredding.
  • Added a new topic: Investigating Deadlocks: Querying Shredded_LockTbl.
  • Teradata Database Release 15.10

    September 2017

    Added information about the following target tables used in shredding the lock plan information in DBQLXMLLockTbl:

  • Shredded_LockTbl: blocking transaction lock shredding target table
  • Shredded_TransTbl: blocked transaction lock shredding target table
  • Teradata Database Release 15.10

    July 2015

  • Updated information on mainframe channel and network connections.
  • The WITH option of END QUERY LOGGING is deprecated.
  • Specified that you cannot log use count information for account strings.
  • Added the QryLogParamJSON view. Changed the QryLogParam view output to CLOB type.
  • Added step names and their explanations for DBQLStepTbl.
  • The Recovery Manager commands LIST ROLLBACK TABLES and LIST CANCEL ROLLBACK TABLES now include DBQL and ResUsage tables.
  • Updated the description of the RollbackPriority DBS control field.
  • Teradata Database Release 15.10

    June 2015

  • Moved the data compression chapter from this book to Database Design.
  • Reflected that PDE tool mboxchk replaces dbschk in detecting database hangs and slowdowns.
  • Incorporated Trusted Sessions, CheckTable Enhancements, MLOADX Enhancements, Load Isolation, Secure Zones, Columnar Enhancements, DSA: Allow Restore Jobs To Complete Even When Out of Space, SQL Equivalents of Ferret Output, Support Audit Trail of DBS Control GDO, New AWT Resource Throttle, NO COLUMNS suboption to the OBJECT logging option of BEGIN QUERY LOGGING, and Combining Multiple DBQL XML Plan Rows in One Document.
  • Added expanded deadlock information and revised shredding instructions to the DBQLXMLLockTbl section.
  • Noted that Teradata logs a warning if the number of crashdumps saved on a node is near the limit.
  • Removed documentation on troubleshooting a snapshot dump. The Onsite System and Dump Analysis tool is for Teradata Customer Support only.
  • Removed references to 30-character limits for object names. Teradata Database supports object names up to 128 characters long in most cases. For more information on object naming see SQL Fundamentals.