DSA Restrictions - Data Stream Architecture

Teradata Data Stream Architecture (DSA) User Guide

Product
Data Stream Architecture
Release Number
16.10
Published
August 2017
Language
English (United States)
Last Update
2018-04-17
dita:mapPath
mbk1487616377418.ditamap
dita:ditavalPath
3150_DSA_UG_1610.ditaval.ditaval
dita:id
B035-3150
lifecycle
previous
Product Category
Software
Teradata Tools and Utilities
Teradata DSA currently has the following limitations:
  • There can only be one target device (tape drive or disk) per NetBackup policy.
  • Multi-byte characters are not supported in the DSA command-line interface.
  • Backup and restore jobs are subject to a database lock limit of up to 5,000 database objects for Teradata Database releases 15.0 and below. This limitation no longer applies in Teradata Database release 15.10.
  • Beginning with Teradata Database release 16.0, the same user ID can run multiple restore jobs at once. However legacy BAR may reject the job, if the DSA job is started first for the same user.
  • For Teradata Database 15.10.xx and earlier, the same user ID can run only one restore job at a time. If the user is already logged on and is running a BAR operation (including legacy BAR jobs), a DSA restore job will be aborted.
  • If the Teradata Database system restarts during an archive or restore operation, the host utility lock will remain on the remaining unprocessed objects. The user must release the lock manually.
  • To allow for parallelism during restore, the number of AMP Worker Tasks (AWT) dictates the number of DSA jobs that can run in parallel.
  • A maximum of three concurrent restore jobs can be run on a system.
  • Up to 20 backup jobs can be run concurrently (based on 80 AWT).
  • DSA does not support any Teradata Database version that is higher than the DSA version.