PDSet to Workload Mapping Considerations - Teradata Workload Analyzer

Teradata Workload Analyzer User Guide

Teradata Workload Analyzer
Release Number
English (United States)
Last Update
Product Category
Teradata Tools and Utilities

PDSet to Workload Mapping Considerations

PDSets must meet the following requirements to successfully map to workloads:

  • There must be a one-to-one correlation between workloads and performance groups.
  • Only one performance period is allowed per performance group.
  • One workload is created for each account. However, if the total number of accounts for all PDSets is 35 or more, one workload is created per performance group.
  • If multiple accounts are available for a workload/performance group, the account names are OR’d in the classification table, creating multiple rows - one per account.
  • If no associated account is found in DBQL for a performance group, then it is marked inactive. There is no workload created in this case.
  • The Classify Condition for Acct is AcctName.
  • If an “inactive performance group” is overridden to an “active” one, then the Classify Condition is: Acct = $PGName (the Priority Group part of the performance group).
  • Note: If the message “The PSA database is Locked by another user” appears when running PSA migration, it means that either the PSA database is currently being accessed or that a previous user of the PSA database exited without freeing the lock. The standard resolution in this case would be to wait to for the lock to be released. If after a period of time you suspect the lock is hung, you should determine if it is safe to free the lock manually and then repeat the operation.