Teradata DSA currently has the following limitations:
- DSA does not support archiving or restoring journal definitions and data.
- DSA does not backup or restore volatile tables.
- Multibyte characters are not supported in the DSA command-line interface.
- [Teradata Database 15.0] Backup and restore jobs are subject to a database lock limit of up to 5,000 database objects.
- [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 is aborted.
- [Advanced SQL Engine 16.20 and later / Teradata Database 16.0 and later] 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.
- If the Teradata system restarts during an archive or restore operation, the host utility lock remains 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.
[Advanced SQL Engine 16.20 and later / Teradata Database 16.10.01 and later] There is no longer a restriction, but Teradata recommends a maximum of three concurrent restore jobs be run on a system (based on 80 AWT). You can customize this value using Teradata Workload Management. See Teradata Vantage™ - Workload Management User Guide, B035-1197.
- Up to 20 backup jobs can be run concurrently (based on 80 AWT).
- DSA does not support an Advanced SQL Engine / Teradata Database version that is later than the DSA version.
- DSA does not support the Advanced Job Status Enhancements feature for Analyze and Repository jobs.