Teradata Manager. User Guide

Transcription

1 Teradata Manager User Guide Release 12.0 B A July 2007

2 The product or products described in this book are licensed products of Teradata Corporation or its affiliates. Teradata, BYNET, DBC/1012, DecisionCast, DecisionFlow, DecisionPoint, Eye logo design, InfoWise, Meta Warehouse, MyCommerce, SeeChain, SeeCommerce, SeeRisk, Teradata Decision Experts, Teradata Source Experts, WebAnalyst, and You ve Never Seen Your Business Like This Before are trademarks or registered trademarks of Teradata Corporation or its affiliates. Adaptec and SCSISelect are trademarks or registered trademarks of Adaptec, Inc. AMD Opteron and Opteron are trademarks of Advanced Micro Devices, Inc. BakBone and NetVault are trademarks or registered trademarks of BakBone Software, Inc. EMC, PowerPath, SRDF, and Symmetrix are registered trademarks of EMC Corporation. GoldenGate is a trademark of GoldenGate Software, Inc. Hewlett-Packard and HP are registered trademarks of Hewlett-Packard Company. Intel, Pentium, and XEON are registered trademarks of Intel Corporation. IBM, CICS, DB2, MVS, RACF, Tivoli, and VM are registered trademarks of International Business Machines Corporation. Linux is a registered trademark of Linus Torvalds. LSI and Engenio are registered trademarks of LSI Corporation. Microsoft, Active Directory, Windows, Windows NT, and Windows Server are registered trademarks of Microsoft Corporation in the United States and other countries. Novell and SUSE are registered trademarks of Novell, Inc., in the United States and other countries. QLogic and SANbox trademarks or registered trademarks of QLogic Corporation. SAS and SAS/C are trademarks or registered trademarks of SAS Institute Inc. SPARC is a registered trademarks of SPARC International, Inc. Sun Microsystems, Solaris, Sun, and Sun Java are trademarks or registered trademarks of Sun Microsystems, Inc., in the United States and other countries. Symantec, NetBackup, and VERITAS are trademarks or registered trademarks of Symantec Corporation or its affiliates in the United States and other countries. Unicode is a collective membership mark and a service mark of Unicode, Inc. UNIX is a registered trademark of The Open Group in the United States and other countries. Other product and company names mentioned herein may be the trademarks of their respective owners. THE INFORMATION CONTAINED IN THIS DOCUMENT IS PROVIDED ON AN AS-IS BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, SO THE ABOVE EXCLUSION MAY NOT APPLY TO YOU. IN NO EVENT WILL TERADATA CORPORATION BE LIABLE FOR ANY INDIRECT, DIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS OR LOST SAVINGS, EVEN IF EXPRESSLY ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. The information contained in this document may contain references or cross-references to features, functions, products, or services that are not announced or available in your country. Such references do not imply that Teradata Corporation intends to announce such features, functions, products, or services in your country. Please consult your local Teradata Corporation representative for those features, functions, products, or services available in your country. Information contained in this document may contain technical inaccuracies or typographical errors. Information may be changed or updated without notice. Teradata Corporation may also make improvements or changes in the products or services described in this information at any time without notice. To maintain the quality of our products and services, we would like your comments on the accuracy, clarity, organization, and value of this document. Please [email protected] Any comments or materials (collectively referred to as Feedback ) sent to Teradata Corporation will be deemed non-confidential. Teradata Corporation will have no obligation of any kind with respect to Feedback and will be free to use, reproduce, disclose, exhibit, display, transform, create derivative works of, and distribute the Feedback and derivative works thereof without limitation on a royalty-free basis. Further, Teradata Corporation will be free to use any ideas, concepts, know-how, or techniques contained in such Feedback for any purpose whatsoever, including developing, manufacturing, or marketing products or services incorporating Feedback. Copyright by Teradata Corporation. All Rights Reserved.

3 Preface Purpose This book provides information about Teradata Manager, which is a Teradata Tools and Utilities product. Teradata Tools and Utilities is a group of products designed to work with Teradata Database. This book helps the Teradata Manager user get started with this versatile product. First get familiar with the capabilities and structure of this product by reading Chapter 3: Getting Started With Teradata Manager. Next, set up Teradata Manager by following the configuration procedures in Chapter 4: Configuring Teradata Manager. After Teradata Manager is configured, either go straight through this guide chapter by chapter or skip around to the sections applicable to your work situation. Audience This book is intended for use by: System users Programmers Application programmers Technical personnel using Teradata Manager Supported Releases This book supports the following releases: Teradata Database Teradata Tools and Utilities Teradata Manager 12.0 Note: See the About Teradata Manager command in Table 10 on page 43 to verify the Teradata Manager version number. To locate detailed supported-release information: 1 Go to 2 Navigate to General Search>Publication Product ID. 3 Enter Teradata Manager User Guide 3

4 Preface Prerequisites 4 Open the version of the Teradata Tools and Utilities ##.##.## Supported Versions spreadsheet associated with this release. The spreadsheet includes supported Teradata Database versions, platforms, and product release numbers. Prerequisites The following prerequisite knowledge is required for this product: Computer technology and terminology Teradata SQL Teradata Database Connectivity software, such as ODBC or CLIv2 Microsoft Windows operating system Changes to This Book The following changes were made to this book in support of the current release. Changes are marked with change bars. For a complete list of changes to the product, see the Release Definition associated with this release. Date and Release August July Description Fixed context-sensitive help. Added a new report that shows a ranked list of queries on each workload delay queue, allowing queries to be released or aborted based on their position in the delay queue. See Monitoring the Workload Delay Queue List on page 113. Specify an external DBQL for trend reporting. See Specifying an External DBQL for Data Collection and Trend Reporting on page 66. Added new columns to the Workload Definition Usage Report for reporting summary statistics. See Workload Definition Usage Report on page 149. Support for Unicode 4.0 as follows: See Setting the Security Mechanism and Character Set on page 83. See To run Database Setup twice if upgrading the Teradata Database on page 51. See To run the script twice if upgrading the Teradata Database on page 53. See Unicode Migration on Teradata Database 12 on page 53. See Table 12 on page Teradata Manager User Guide

5 Preface Changes to This Book Date and Release July Description Added new session level methods. See Table 95 on page 270 and Table 105 on page 279. Added a new report that monitors the status of an event. See Monitoring Event Status on page 117. Added the ARC utility to the Object Utility Statistics Report. See Table 29 on page 117. Added five new columns to the Teradata DWM Workload Definition Summary Report. See Table 34 on page 129. Added one new column to the Workload Definition Detail Report. See Table 35 on page 130. Added Delayed, QTDelayed, and SesDelayed columns to the Session Information Summary Report. See the Session Information online help. Updated PMON online help for session character sets when logging on. Added documentation for security mechanism to the Logon dialog box introduced in a previous release. Updated Alert Policy Editor online help for session character sets when logging on. Added documentation for security mechanism to the Logon dialog box introduced in a previous release. Define a Policy Refresh Failed alert. See Alerting on Policy Refresh Time on page 250. Enhanced the documentation for Teradata Manager Alert Policies. See Chapter 15: Using Alerts to Monitor Your System. Clarified reset peak spool space and clean up of data collection tasks. See Step 8 - Enabling Data Collection on page 61. Changed the name of the Teradata DWM Dump utility that runs using Remote Console. See Table 116 on page 293. Added a caution when configuring table space data collection parameters. See Configuring Table Space Data Collection Parameters on page 76. Using Teradata Manager alerts, monitor the Teradata software event log on Windows databases for Teradata Database or later. See Step 6 - Defining System Parameters on page 57 and Alerting on Teradata Event Messages From Teradata Database V2R6.x on Windows 2000 on page 248. Updated version numbers. Added clarification on workload classifications and Priority Scheduler. See Introduction on page 208. Support for WinCLI is discontinued. Migrate the tdwm database. See Step 1 - Creating the Teradata Manager Databases, Tables, and Macros on page 48 and TDWM Setup on Teradata Database 12 on page 54. Miscellaneous updates to match documentation to the current Teradata Manager application. Teradata Manager User Guide 5

6 Preface Additional Information Date and Release July Description Removed information related to the Computer Associates (CA) Unicenter TNG Framework. Added a caution when generating the Query List report. See Analyzing Workload Definition Query Trends on page 150. Added support for the Query Banding feature as follows: Configure query band pairs data collection parameters. See Configuring Query Band Pairs Data Collection Parameters on page 74. Added support for query bands to the Session Detail Report. See Getting Session Details on page 103. View query band names and values. See Viewing Query Band Pairs on page 111. Added support for query bands in the Object Model. See Table 95 on page 270 and Table 105 on page 279. Updated the PMON online help to support query bands. Additional Information Additional information that supports this product and Teradata Tools and Utilities is available at the web sites listed in the table that follows. In the table, mmyx represents the publication date of a manual, where mm is the month, y is the last digit of the year, and x is an internal publication code. Match the mmy of a related publication to the date on the cover of this book. This ensures that the publication selected supports the same release. Type of Information Description Access to Information Release overview Late information Use the Release Definition for the following information: Overview of all of the products in the release Information received too late to be included in the manuals Operating systems and Teradata Database versions that are certified to work with each product Version numbers of each product and the documentation for each product Information about available training and the support center 1 Go to 2 Select the General Search check box. 3 In the Publication Product ID box, type Click Search. 5 Select the appropriate Release Definition from the search results. 6 Teradata Manager User Guide

7 Preface Additional Information Type of Information Description Access to Information Additional product information CD-ROM images Ordering information for manuals Use the Teradata Information Products Publishing Library site to view or download specific manuals that supply related or additional information to this manual. Access a link to a downloadable CD-ROM image of all customer documentation for this release. Customers are authorized to create CD-ROMs for their use from this image. Use the Teradata Information Products Publishing Library site to order printed versions of manuals. 1 Go to 2 Select the Teradata Data Warehousing check box. 3 Do one of the following: For a list of Teradata Tools and Utilities documents, click Teradata Tools and Utilities and then select a release or a specific title. Select a link to any of the data warehousing publications categories listed. Specific books related to Teradata Manager are as follows: Database Administration B mmyx Workload Management API: PM/API and Open API B mmyx Teradata Administrator User Guide B mmyx Teradata AWS User Guide B mmyx Teradata Dynamic Workload Manager User Guide B mmyx Teradata Manager Installation Guide B mmyx Teradata SQL Assistant for Microsoft Windows User Guide B mmyx Teradata Query Scheduler Administrator Guide B mmyx Teradata Query Scheduler User Guide B mmyx Teradata Tools and Utilities Installation Guide for Microsoft Windows B mmyx Utilities B mmyx 1 Go to 2 Select the General Search check box. 3 In the Title or Keyword box, type CD-ROM. 4 Click Search. 1 Go to 2 Select the How to Order check box under Print & CD Publications. 3 Follow the ordering instructions. Teradata Manager User Guide 7

8 Preface Additional Information Type of Information Description Access to Information General information about Teradata The Teradata home page provides links to numerous sources of information about Teradata. Links include: Executive reports, case studies of customer experiences with Teradata, and thought leadership Technical information, solutions, and expert advice Press releases, mentions, and media resources 1 Go to Teradata.com. 2 Select a link. 8 Teradata Manager User Guide

9 Table of Contents Preface Purpose Audience Supported Releases Prerequisites Changes to This Book Additional Information Chapter 1: Introduction Where to Find Answers Getting an Overview of Teradata Manager Getting Help with Installation or Viewing Program Fixes Getting Instructions for Specific Tasks Getting Help for Teradata Manager Chapter 2: Late-Breaking News, Installation, and Related Documentation Installation Information Program Fixes and Changes Chapter 3: Getting Started With Teradata Manager What Is Teradata Manager? Finding Your Way Around the Teradata Manager Interface File Menu Edit Menu Teradata Manager User Guide 9

10 Table of Contents Options Menu Monitor Menu Investigate Menu Analyze Menu Administer Menu Graph Menu Window Menu Help Menu Teradata Manager File Locations Printing or Saving the Currently Displayed Report or Graph Creating a Batch Version of a Teradata Manager Report Chapter 4: Configuring Teradata Manager Step 1 - Creating the Teradata Manager Databases, Tables, and Macros Step 2 - Adding Teradata Manager Users Alternative to Steps 1 and 2 - Using the Setup Script Instead of Database Setup Step 3 - Starting Teradata Manager Step 4 - Restricting User Access with Profiles Step 5 - Authorizing User Access to Profiles Step 6 - Defining System Parameters Step 7 - Setting RSS Collection Rates Step 8 - Enabling Data Collection Specifying an External DBQL for Data Collection and Trend Reporting Configuring AMP Usage Data Collection Parameters Configuring DBQL Data Collection Parameters Configuring Teradata Dynamic Workload Management Data Collection Parameters Configuring Heartbeat Query Data Collection Parameters Configuring Priority Scheduler Data Collection Parameters Configuring Query Band Pairs Data Collection Parameters Configuring Resource Usage Data Collection Parameters Configuring Spool Space Data Collection Parameters Configuring Table Space Data Collection Parameters Configuring Your Color Display Options Checking the Status of the Teradata Manager Server Changing Logon Settings Restoring the Default Preferences for Tables and Graphs Teradata Manager User Guide

11 Table of Contents Adding Application Specific Entries to the Registry Adding Additional Applications to the Teradata Manager Menu Bar Setting the Port Number for TCP/IP Setting the Security Mechanism and Character Set Chapter 5: Configuring the SNMP Agent Teradata Manager Alerts SNMP MIB SNMP Troubleshooting Tips Chapter 6: Monitoring Real-Time System Activity Monitoring Overall System Activity Using the Dashboard Getting History Data Details Monitoring Virtual Utilization Getting Virtual Utilization Details Monitoring Physical Utilization Getting Physical Utilization Details Monitoring Session Status Getting Session Details Modifying Session Priority Aborting Sessions Viewing What the Selected Session is Blocking Viewing What the Selected Session is Blocked By Viewing Query Band Pairs Monitoring Delay Queue Statistics Monitoring the Workload Delay Queue List Monitoring Object Logon Statistics Monitoring Object Query Statistics Monitoring the Object Delay Queue List Monitoring Object Utility Statistics Monitoring Event Status Using Performance Monitor (PMON) Using Session Information The Graph Legend Teradata Manager User Guide 11

12 Table of Contents Chapter 7: Monitoring the Delay Queue Viewing a Snapshot of the Workload Delay Queue Getting Workload Delay Queue Statistics Viewing Workload Delay Queue History Viewing and Releasing Requests in the Workload Delay Queue Chapter 8: Monitoring Workload Activity Checking Workload Status Getting Workload Summary Statistics Getting Workload Detail Statistics Getting Workload History Statistics Specifying the Display for Workload Snapshot Graphs Chapter 9: Analyzing Workload Trends Analyzing CPU Utilization CPU Utilization Report Analyzing Disk I/O Utilization Analyzing Table Growth Analyzing Spool and Temp Space Usage Analyzing Heartbeat Query Response Time Analyzing User Count Analyzing Workload Definition Usage Trends Analyzing Workload Definition Query Trends Analyzing Resource Usage Trends Analyzing DBQL Usage Trends Analyzing DBQL Step Usage Trends Viewing the DBQL Summary Histogram Teradata Manager User Guide

13 Table of Contents Chapter 10: Analyzing Historical Resource Utilization Analyzing Node CPU Utilization Analyzing AMP CPU Utilization Analyzing PE CPU Utilization Analyzing Node Utilization Analyzing Disk Utilization Analyzing Network (Bynet) Utilization Analyzing Memory Utilization Analyzing Host Utilization Non-Grouped Reports History Query Filter Chapter 11: Investigating Disk Space Utilization Reallocating Disk Space Changing Options for Space Usage Reports Transferring Database Ownership Viewing Database Space Usage Viewing Space Usage By Table Viewing Table Space Usage by Vproc Viewing the CREATE TABLE Statement Viewing All Objects In a Database Viewing Hierarchical Space Usage Viewing Overall Space Usage by Vproc Viewing Cylinder Space By Vproc Chapter 12: Investigating System Behavior Investigating the Error Log Investigating Logon Activity Investigating Lock Contentions Investigating System Performance Parameters Teradata Manager User Guide 13

14 Table of Contents Chapter 13: Investigating the Audit Log Before Creating Audit Reports Setting the Audit Log Filter to Narrow Your Results Auditing Database and User Activity Auditing Table, View and Macro Activity Auditing Grant and Revoke Activity Auditing Index Activity Auditing Checkpoint, Dump and Restore Activity Auditing Denials Creating an Audit Summary Report Creating a Custom Audit Report Chapter 14: Using Teradata Priority Scheduler Administrator Introduction Step 1 - Starting Teradata PSA Step 2 - Defining PD Set and Resource Partition Parameters Step 3 - Defining Performance Group Parameters Step 4 - Defining Allocation Group Parameters Adding or Deleting an Allocation Group Viewing a Priority Definition Set Description Viewing the Schmon Commands Used to Create a Priority Definition Set Saving and Deleting Priority Definition Set Information Creating a New Priority Definition Set Viewing Performance Data Viewing Session Information Viewing a Session Report Scheduling a Priority Definition Set Comparing Relative Weights of Allocation Groups or Resource Partitions Comparing Relative CPU Use of an Allocation Group or Resource Partition Changing the Operating System Type Defining Advanced PD Set and Resource Partition Parameters Configuring the Priority Scheduler Administrator Display Priority Scheduler Administrator Command Line Parameters Teradata Manager User Guide

15 Table of Contents Chapter 15: Using Alerts to Monitor Your System Introduction to the Alerts Facility Creating a New Alert Policy Defining Actions to the Policy Defining Actions - Sending a Page Defining Actions - Sending Configuring the System to Send Alerts Defining Actions - Running a Program Defining Actions - Running a BTEQ Script Defining Actions - Generating an SNMP Trap Defining Actions - Action Lists Defining Events to the Policy Defining Events - Database Space Defining Events - System Level Performance Defining Events - Node Level Performance Defining Events - Vproc Level Performance Defining Events - Session Level Performance Defining Data Collection Rates for the Policy Applying the Policy to the Database Displaying the Performance Status of the Database Alerting on Teradata Event Messages From Teradata Database V2R6.x on Windows Alerting on Policy Refresh Time Alerts Examples Chapter 16: System Administration Administering Workloads with Priority Scheduler Administrator Administering Using the Database Console (Remote Console) Administering System Alarms Using Alerts (Alert Policy Editor) Administering Using the BTEQ Window Administering Using Database Statistics (Statistics Collection) Teradata Manager User Guide 15

16 Table of Contents Chapter 17: Using the Scheduler Introduction to the Scheduler Scheduling Tasks That Launch Applications Example 1: Scheduling a Task To Run Once a Day Example 2: Specifying the Days and Times Example 3: Specifying Multiple Daily Runs Chapter 18: Using the Performance Monitor Object Prerequisite Knowledge Application Distribution Requirements The Object Model Object Model Error Messages Chapter 19: Teradata Manager Applications Alert Policy Editor Alert Viewer BTEQ Window Configuration Check Error Log Analyzer Locking Logger LogOnOff Usage Database Setup Priority Scheduler Administrator Remote Console Session Information Statistics Collection Teradata Performance Monitor Teradata Manager User Guide

17 Table of Contents Glossary Index Teradata Manager User Guide 17

18 Table of Contents 18 Teradata Manager User Guide

19 List of Figures Figure 1: Teradata Manager Dashboard Figure 2: Teradata Performance Monitor Figure 3: Teradata Manager Database Space Report Figure 4: Teradata Manager Alert Viewer Figure 5: Teradata Manager Resource Usage Trend Report Figure 6: Teradata Manager Administration Tabs Figure 7: Example of an Event Status Report Figure 8: Scheduling a task to run once a day Figure 9: Scheduling a task to run once a day specifying the days and time Figure 10: Scheduling a task to run many times on a specified day Teradata Manager User Guide 19

20 List of Figures 20 Teradata Manager User Guide

21 List of Tables Table 1: File Menu Commands Table 2: Edit Menu Commands Table 3: Options Menu Commands Table 4: Monitor Menu Commands Table 5: Investigate Menu Commands Table 6: Analyze Menu Commands Table 7: Administer Menu Commands Table 8: Graph Menu Commands Table 9: Window Menu Commands Table 10: Help Menu Commands Table 11: Teradata Manager File Locations Table 12: Perm Space Requirements for Data Collection Table 13: Summary Graph Data Points Table 14: Vproc Utilization Report Table 15: Vproc Utilization Detail Report Table 16: Node Utilization Report Table 17: Node Utilization Detail Report Table 18: Session Status Report Table 19: Session Detail Report Table 20: Abort Session Report Table 21: Blocking Sessions Report Table 22: Blocked By Report Table 23: Query Bands Report Table 24: Delay Queue Statistics Report Table 25: Workload Delay Queue List Report Table 26: Object Logon Statistics Report Table 27: Object Query Statistics Report Table 28: Object Delay Queue List Report Table 29: Object Utility Statistics Report Table 30: Event Status Report Table 31: Workload Delay Queue Detail Report Table 32: Workload Delay Queue History Report Teradata Manager User Guide 21

22 List of Tables Table 33: Workload Delay Queue Session List Table 34: Teradata DWM Workload Definition Summary Report Table 35: Workload Definition Detail Report Table 36: Workload Definition Summary History Report Table 37: Criteria Used to Determine the Top Workloads Table 38: CPU Utilization Report Table 39: Disk I/O Utilization Report Table 40: Table Growth Report Table 41: Spool/Temp Space Usage Report Table 42: Response Time Report Table 43: User Count Report Table 44: Workload Definition Usage Report Table 45: Rejected Query List Report Table 46: Delayed Query List Report Table 47: Exception Query List Report Table 48: Exceeded SLG Query List Report Table 49: Completed Query List Report Table 50: Resource Usage Report: CPU Usage Table 51: Resource Usage Report: Disk Usage Table 52: Resource Usage Report: Memory Usage Table 53: Resource Usage Report: Bynet Usage Table 54: Resource Usage Report: System Utilization Table 55: DBQL Usage Report: Condition Indicator Count Table 56: DBQL Usage Report: Response Time Table 57: DBQL Usage Report: Resource Usage Table 58: DBQL Usage Report: Parallelism Table 59: DBQL Step Usage Report Table 60: DBQL Summary Histogram Table 61: Node CPU Utilization Report Table 62: AMP CPU Utilization Report Table 63: PE CPU Utilization Report Table 64: Node Utilization Report Table 65: Disk Utilization Report Table 66: Network Utilization Report Table 67: Memory Utilization Report Table 68: Host Utilization Report Teradata Manager User Guide

23 List of Tables Table 69: Non-Grouped Report Table 70: Move Space Fields and Controls Table 71: Space By Database Report Table 72: Table Space Report Table 73: Table Space By Vproc Report Table 74: Help Database Report Table 75: Hierarchy Report Table 76: Space By Vproc Report Table 77: Cylinder Space By Vproc Report Table 78: Logon Activity Reports Table 79: Audit Database and Users Activity Report Table 80: Audit Table, View, Macro Activity Report Table 81: Audit Grant and Revoke Activity Report Table 82: Audit Index Activity Report Table 83: Audit Checkpoint, Dump and Restore Activity Report Table 84: Audit Denials Report Table 85: Audit Summary Report Table 86: Physical Actions Table 87: Built-in Actions Table 88: Alert Message Table 89: Event Data Items Table 90: Event Message Files Table 91: Alert Request Table Column Descriptions Table 92: Monitor Request Table Column Definitions Table 93: Required Teradata Manager Support Files Table 94: Required Third Party Support Files Table 95: Monitor (Object) Descriptions Table 96: VprocSummary Descriptions Table 97: Node Summary Descriptions Table 98: AMPs Descriptions Table 99: AMP (Object) Descriptions Table 100: PEs Descriptions Table 101: PE Object Descriptions Table 102: Nodes Descriptions Table 103: Node (Object) Descriptions Table 104: Sessions Descriptions Teradata Manager User Guide 23

24 List of Tables Table 105: Session (Object) Descriptions Table 106: Blocks Descriptions Table 107: Block (Object) Descriptions Table 108: Steps Descriptions Table 109: Step (Object) Descriptions Table 110: Workloads Descriptions Table 111: Workload (Object) Descriptions Table 112: Query Bands Descriptions Table 113: Query Band (Object) Descriptions Table 114: Object Model Error Messages Table 115: LogOnOff Usage Report Descriptions Table 116: Remote Console Utility Descriptions Table 117: Session Information Report Descriptions Teradata Manager User Guide

25 CHAPTER 1 Introduction The following topics provide information on where to find answers and how to get help for Teradata Manager. Where to Find Answers To learn about the product, Teradata Manager comes with a number of instructional components. including: Getting an Overview of Teradata Manager For an overview of the capabilities of Teradata Manager, as well as an introduction to the Teradata Manager menu bar in the interface, see Chapter 3: Getting Started With Teradata Manager. Getting Help with Installation or Viewing Program Fixes For help with Teradata Manager installation, the installation of related products, or documentation of program fixes, see Chapter 2: Late-Breaking News, Installation, and Related Documentation. Getting Instructions for Specific Tasks To get familiar with the Teradata Manager interface, look at the following: Task Set up a new installation of Teradata Manager, or change program configuration settings Set up an SNMP agent that allows third party management applications such as HP OpenView to monitor Teradata system performance and to be notified of exceptions using SNMP traps Monitor overall system utilization in real time Monitor jobs that are in the delay queue Monitor real-time and historical workload statistics Location Chapter 4: Configuring Teradata Manager Chapter 5: Configuring the SNMP Agent Chapter 6: Monitoring Real-Time System Activity Chapter 7: Monitoring the Delay Queue Chapter 8: Monitoring Workload Activity Teradata Manager User Guide 25

26 Chapter 1: Introduction Where to Find Answers Task Analyze workload usage through time Get a historical view of how your system is being utilized Monitor space usage and move space from place to place Analyze the maximum and average usage for Logical Devices (LDVs), AMP vprocs, nodes, and PE vprocs on your system Check the results of privilege checks Schedule system priorities Set up alert actions to generate notifications of, and actively respond to, Teradata Database events Investigate the various system administration options available with your Teradata Manager software Schedule activities on your system Set up an ActiveX (COM) object that exposes methods to allow retrieval of PMPC data Use the various Teradata Manager applications Location Chapter 9: Analyzing Workload Trends Chapter 10: Analyzing Historical Resource Utilization Chapter 11: Investigating Disk Space Utilization Chapter 12: Investigating System Behavior Chapter 13: Investigating the Audit Log Chapter 14: Using Teradata Priority Scheduler Administrator Chapter 15: Using Alerts to Monitor Your System Chapter 16: System Administration Chapter 17: Using the Scheduler Chapter 18: Using the Performance Monitor Object. Chapter 19: Teradata Manager Applications. Getting Help for Teradata Manager Teradata Manager is linked to the HTML version of this user guide. Use the Help menu on the Teradata Manager menu bar to launch the help system. To see context-sensitive help for the active dialog box, press F1. 26 Teradata Manager User Guide

27 CHAPTER 2 Late-Breaking News, Installation, and Related Documentation The following topics provide information on installation and program fixes: Installation Information Program Fixes and Changes Installation Information For information on installing Teradata Manager, as well as the rest of the Teradata Tools and Utilities, see the following: Teradata Manager Installation Guide Teradata Tools and Utilities Installation Guide for Microsoft Windows Program Fixes and Changes For the latest documentation on program fixes and changes included in this release, see Teradata Tools and Utilities Release Definition. Teradata Manager User Guide 27

28 Chapter 2: Late-Breaking News, Installation, and Related Documentation Program Fixes and Changes 28 Teradata Manager User Guide

29 CHAPTER 3 Getting Started With Teradata Manager The following topics provide basic information to get started using Teradata Manager: What Is Teradata Manager? Finding Your Way Around the Teradata Manager Interface Teradata Manager File Locations Printing or Saving the Currently Displayed Report or Graph Creating a Batch Version of a Teradata Manager Report What Is Teradata Manager? As the command center for the Teradata Database, Teradata Manager supplies an extensive suite of indispensable DBA tools for managing your Teradata Database. Teradata Manager collects, analyzes, and displays database performance and utilization information in either report or graphic format, displaying it all on a Windows PC. The client-server feature in Teradata Manager replicates performance data on the server for access by any number of clients. Because data is collected once, workload on the database remains constant while the number of client applications varies. The following sections highlight some of the main Teradata Manager features. For a complete list of features and capabilities, see Finding Your Way Around the Teradata Manager Interface on page 35. Monitoring in Real Time: The Teradata Manager Dashboard The heart of Teradata Manager is the Teradata Manager Dashboard (Figure 1) and is available from the Monitor menu. Teradata Manager User Guide 29

30 Chapter 3: Getting Started With Teradata Manager What Is Teradata Manager? Figure 1: Teradata Manager Dashboard The Teradata Manager Dashboard provides a single tabbed page view of current performance and workload information, as well as recent trends. This is accomplished by showing real-time gauges and graphs displaying: Virtual and physical CPU utilization Requests-per-minute I/O-per-request Response time Sessions (idle, active, blocked, responding, Parsing, aborting, details, and prolonged idles) Recent history graphs showing trends and providing analytic data Workload snapshots and history All this enables rapid problem resolution to drill down quickly to the most useful detailed information. 30 Teradata Manager User Guide

31 Chapter 3: Getting Started With Teradata Manager What Is Teradata Manager? Teradata Performance Monitor (PMON) Teradata Performance Monitor provides the system status at a glance with seven functional areas for monitoring system activity. See Figure 2. These include Configuration Summary, Performance Summary and Resource Usage (both physical and virtual), Session and Lock information, Session History, Control functions and graphic displays of Resource and Session data. Figure 2: Teradata Performance Monitor PMON uses charting facilities to present the data to identify abnormalities. Color is used to indicate warning conditions. Configure the Alert thresholds, color settings, and automatic data refresh rate values by using the PMON Options tabs. Detailed session and user information is useful for analyzing system activity and blocked sessions. Lock information helps determine which sessions are blocking other sessions and why. After analyzing running queries, drill down from a blocked session to the query and the step level of the explain for the query. Session Information Session Information dynamically monitors the status of sessions on logical host processors attached to the Teradata Database. The status can be updated as frequently as every six seconds depending on the size of the database and the workload. Information is reported on the current status of a session including Idle, Active, Blocked, Responding, Parsing, Aborting, Teradata Manager User Guide 31

32 Chapter 3: Getting Started With Teradata Manager What Is Teradata Manager? Details, and Prolonged Idles. With Session Information, quickly identify abnormal conditions in the Teradata Database, and abort any unnecessary jobs. Investigating System Logs and Alerts The Investigate menu provides access to system logs and to the Alerts facility, providing reports that show: Privilege checks for various types of Database activity The Error log Space usage statistics Logon statistics Lock contentions The Teradata Manager Database Space Report (Figure 3) is available from the Investigate menu, and shows space usage by database. Figure 3: Teradata Manager Database Space Report 32 Teradata Manager User Guide

33 Chapter 3: Getting Started With Teradata Manager What Is Teradata Manager? The Alert Viewer The Alert Viewer (Figure 4) is a component of the Alerts Facility where it is easy to view system status for one or more Teradata Databases. The Alerts Facility facilitates the monitoring of performance characteristics and faults on the Teradata Database. The Alerts Facility can automatically activate actions, such as sending a page, sending , or sending a message to an SNMP system. Other applications and utility programs can also make use of the Alert function by using a built-in request interface. The Alert Policy Editor is used to define actions. Specify when the actions are taken by setting thresholds for Teradata Database performance parameters, database space utilization, and messages in the database Event Log. Figure 4: Teradata Manager Alert Viewer Teradata Manager User Guide 33

34 Chapter 3: Getting Started With Teradata Manager What Is Teradata Manager? Analyzing Trends in Resource Usage The Analyze menu provides views of various historical trends in resource usage. For example, see the Teradata Manager Resource Usage Trend Report (Figure 5). In most cases, these trends can be viewed in either graph or table format, and can be filtered in many ways to customize your historical system view. Figure 5: Teradata Manager Resource Usage Trend Report Administering Various Aspects of the Database The Teradata Manager Administration tabs (Figure 6) assist in managing users and tables, allowing: Creation of users, databases, tables, and modification of access rights Collection of database statistics Moving free disk space between databases Setting of job performance parameters 34 Teradata Manager User Guide

35 Chapter 3: Getting Started With Teradata Manager Finding Your Way Around the Teradata Manager Interface Figure 6: Teradata Manager Administration Tabs Priority Scheduler Administrator Teradata Priority Scheduler Administrator helps to prevent bottlenecks and speeds responses to queries by automatically balancing the data warehouse workload. Teradata Priority Scheduler Administrator ensures that queries requiring immediate handling are fast-tracked by letting the jobs cut in line ahead of lower priority work. Finding Your Way Around the Teradata Manager Interface There are a wide array of reporting and administrative options that can all be easily accessed from the Teradata Manager menu bar. After becoming comfortable with the menus displayed on the menu bar, using Teradata Manager becomes quite intuitive. Teradata Manager User Guide 35

36 Chapter 3: Getting Started With Teradata Manager Finding Your Way Around the Teradata Manager Interface File Menu The Teradata Manager menu bar is structured as follows. Table 1: File Menu Commands Command Description Additional Information Open Load a Teradata Manager report or graph that has been saved in XML format using the Save As command Creating a Batch Version of a Teradata Manager Report on page 46 Close Close a report Not applicable Save As Append Command to Batch File Print Preview Save a report or graph in XML format so it can be loaded back into Teradata Manager for viewing, or in other formats so it can be transferred to external applications Create a batch version of a Teradata Manager report Preview the report image to be printed Printing or Saving the Currently Displayed Report or Graph on page 45 Creating a Batch Version of a Teradata Manager Report on page 46 Printing or Saving the Currently Displayed Report or Graph on page 45 Print Print a report Printing or Saving the Currently Displayed Report or Graph on page 45 Exit Close the Teradata Manager application Not applicable Edit Menu Table 2: Edit Menu Commands Command Description Additional Information Cut Copy Paste Move the selected text to the clipboard Copy the selected text to the clipboard Paste the text on the clipboard at the insertion point Not applicable Not applicable Not applicable 36 Teradata Manager User Guide

37 Chapter 3: Getting Started With Teradata Manager Finding Your Way Around the Teradata Manager Interface Options Menu Table 3: Options Menu Commands Command Description Additional Information Change Font Change the report display fonts Not applicable Restore Default Preferences Clear user preferences Restoring the Default Preferences for Tables and Graphs on page 79 Refresh Workload List Change Logon Settings Refresh the list of workloads in the cache Change to a different Teradata Manager server, database or profile Not applicable Changing Logon Settings on page 78 Monitor Menu Table 4: Monitor Menu Commands Command Description Additional Information Dashboard Sessions>(options) Nodes Vprocs Teradata DWM>Delay Queue Stats Teradata DWM>WD Summary Teradata DWM>WD Delay Queue List View a summary of the current state of the system on a single tabbed dialog. Note: For Teradata Manager to display the workload or delay queue data, Teradata Dynamic Workload Manager (DWM) must be enabled. See the instructions in the Teradata Dynamic Workload Manager User Guide. Get information on individual sessions Get information on Node usage Get information on vproc usage Get statistics on objects in the Delay Queue Get summary information on workloads View a list of workloads in the delay queue Monitoring Overall System Activity Using the Dashboard on page 90 and Viewing a Snapshot of the Workload Delay Queue on page 123 Monitoring Session Status on page 101 Monitoring Physical Utilization on page 97 Monitoring Virtual Utilization on page 94 Monitoring Delay Queue Statistics on page 112 Getting Workload Summary Statistics on page 128 Monitoring the Workload Delay Queue List on page 113 Teradata Manager User Guide 37

38 Chapter 3: Getting Started With Teradata Manager Finding Your Way Around the Teradata Manager Interface Table 4: Monitor Menu Commands (continued) Command Description Additional Information Teradata DWM>Object Logon Stats Teradata DWM>Object Query Stats Teradata DWM>Object Delay Queue List Teradata DWM>Object Utilities Stats Performance Monitor Session Information Get statistics on object logons Get statistics on object queries View a list of objects in the delay queue Get statistics on system utilities Analyze the performance of a Teradata machine and perform related control functions on that machine Get information on session status, modify session priority, view blocking or blocked sessions, and change session priority Monitoring Object Logon Statistics on page 114 Monitoring Object Query Statistics on page 115 Monitoring the Object Delay Queue List on page 115 Monitoring Object Utility Statistics on page 116 Using Performance Monitor (PMON) on page 120 Using Session Information on page 120 Investigate Menu Table 5: Investigate Menu Commands Command Description Additional Information. Audit Log>Filter Audit Log>Database/User Audit Log>Table/View/Macro Audit Log>Grants Audit Log>Indexes Audit Log>Maintenance Set the Audit Log report filter to narrow your results Audit privilege checks for database and user activity Audit privilege checks for table, view, or macro activity Audit privilege checks for Grant activity Audit privilege checks for Index activity Audit privilege checks for Maintenance activity Setting the Audit Log Filter to Narrow Your Results on page 200 Auditing Database and User Activity on page 200 Auditing Table, View and Macro Activity on page 201 Auditing Grant and Revoke Activity on page 202 Auditing Index Activity on page 202 Auditing Checkpoint, Dump and Restore Activity on page 203 Audit Log>Denials Audit privilege check denials Auditing Denials on page 204 Audit Log>Summary Create a summary report of privilege checks Creating an Audit Summary Report on page Teradata Manager User Guide

39 Chapter 3: Getting Started With Teradata Manager Finding Your Way Around the Teradata Manager Interface Table 5: Investigate Menu Commands (continued) Command Description Additional Information. Audit Log>Custom Create a custom report of privilege checks Creating a Custom Audit Report on page 205 Error Log Investigate the Error Log Investigating the Error Log on page 195 Space Usage>Space by Database Space Usage>Hierarchy Display space usage for each Teradata Database Display a database hierarchy report Viewing Database Space Usage on page 186 Viewing Hierarchical Space Usage on page 190 Space Usage>Space by Vproc Display space usage by vproc Viewing Overall Space Usage by Vproc on page 191 Space Usage>Cylinders by Vproc Logon/Logoff History Locking Logger Alert Viewer Display cylinder usage by vproc Present daily, weekly, and monthly logon statistics based on information in the DBC LOGONOFF view on the Teradata Database Determine whether system performance has been degraded by an inappropriate mix of SQL statements using a table of information extracted from the transaction logs Provide a single view point on the overall system performance of your Teradata Database systems Viewing Cylinder Space By Vproc on page 192 Investigating Logon Activity on page 196 Investigating Lock Contentions on page 196 Investigating System Performance Parameters on page 197 Analyze Menu Table 6: Analyze Menu Commands Command Description Additional Information Trends>CPU Utilization Trends>Disk I/O Utilization Trends>Table Growth Trends>Spool/Temp Space Usage View historical trends in CPU utilization View historical trends in Disk I/O utilization View historical trends in table growth View historical trends in space usage Analyzing CPU Utilization on page 135 Analyzing Disk I/O Utilization on page 138 Analyzing Table Growth on page 140 Analyzing Spool and Temp Space Usage on page 142 Teradata Manager User Guide 39

40 Chapter 3: Getting Started With Teradata Manager Finding Your Way Around the Teradata Manager Interface Table 6: Analyze Menu Commands (continued) Command Description Additional Information Trends>Response Time Trends>User Count Trends>Workload Definition Usage Trends>Workload Definition Query List Trends>Resource Usage Trends>DBQL Usage Trends>DBQL Step Usage Trends>DBQL Summary Histogram Resource History>Node CPU Resource History>AMP CPU Resource History>PE CPU Resource History>Node Utilization Resource History>Disk Utilization Resource History>ByNet Utilization Resource History>Memory Utilization Resource History>Host Utilization View historical trends in response time View historical trends in user count View workload definition usage trends View the workload definition list of queries View historical trends in resource usage View historical trends in DBQL usage View historical trends in DBQL step usage View DBQL summary statistics View the maximum and average CPU utilization View the maximum and average AMP CPU utilization View the maximum and average PE CPU utilization View the maximum and average Node utilization View the maximum and average Disk utilization View the maximum and average ByNet utilization View the maximum and average Memory utilization View the maximum and average Host utilization Analyzing Heartbeat Query Response Time on page 144 Analyzing User Count on page 146 Analyzing Workload Definition Usage Trends on page 147 Analyzing Workload Definition Query Trends on page 150 Analyzing Resource Usage Trends on page 155 Analyzing DBQL Usage Trends on page 158 Analyzing DBQL Step Usage Trends on page 163 DBQL Summary Histogram on page 166 Analyzing Node CPU Utilization on page 167 Analyzing AMP CPU Utilization on page 169 Analyzing PE CPU Utilization on page 171 Analyzing Node Utilization on page 172 Analyzing Disk Utilization on page 174 Analyzing Network (Bynet) Utilization on page 176 Analyzing Memory Utilization on page 177 Analyzing Host Utilization on page Teradata Manager User Guide

41 Chapter 3: Getting Started With Teradata Manager Finding Your Way Around the Teradata Manager Interface Administer Menu Table 7: Administer Menu Commands Command Description Additional Information Teradata Manager Teradata Database Database Console Alert Policies SQL Assistant BTEQ Window Teradata Database Setup Statistics Collection Move Space Configure Teradata Manager, change the database password, set up Alerts and data collection Perform administration functions on the Teradata Database Note: This option is available only if this product is installed on your Teradata Manager PC. Run many of the Teradata Database console utilities from your Teradata Manager PC Define the actions that can take place when specific events occur on your Teradata Database machines Send queries to the Teradata Database Note: This option is available only if this product is installed on your Teradata Manager PC Load and extract data from the Teradata Database using a version of BTEQ with a windows interface Set up the Database to run Teradata Manager Create, drop and update statistics for the Teradata Database Reallocate available disk space from one Teradata Database to another Chapter 4: Configuring Teradata Manager The Teradata Administrator User Guide Administering Using the Database Console (Remote Console) on page 257 Administering System Alarms Using Alerts (Alert Policy Editor) on page 258 The Teradata SQL Assistant for Microsoft Windows User Guide. Note: If an error appears when starting SQL Assistant indicating, Data source not found and no default driver specified, ensure the ODBC DSN name is the same as the system name (COP name) used when logging on to Teradata Manager. Administering Using the BTEQ Window on page 258 Step 1 - Creating the Teradata Manager Databases, Tables, and Macros on page 48 Administering Using Database Statistics (Statistics Collection) on page 259 Reallocating Disk Space on page 183 Teradata Manager User Guide 41

42 Chapter 3: Getting Started With Teradata Manager Finding Your Way Around the Teradata Manager Interface Table 7: Administer Menu Commands (continued) Command Description Additional Information Move Database Workload Management> Priority Scheduler Workload Management> Dynamic Workload Manager (Teradata DWM) Workload Management> Query Scheduler Transfer the ownership of a database to another user Control the allocation and consumption of computer resources available to the Teradata Database Set Workload Management rules. These rules must be in place for Teradata Manager to monitor the workload or delay queue data. Note: This option is available only if this product is installed on your Teradata Manager PC. Schedule queries on the Teradata Database Note: This option is available only if this product is installed on your Teradata Manager PC. Transferring Database Ownership on page 185 Chapter 14 Using Teradata Priority Scheduler Administrator on page 207 The Teradata Dynamic Workload Manager User Guide. The Teradata Query Scheduler User Guide and the Teradata Query Scheduler Administrator Guide Graph Menu Opening a graph, adds the Graph menu to the Teradata Manager menu bar. Table 8: Graph Menu Commands Command Description Additional Information Graph>Type Graph>Style Graph>Legend Change the type of graph from bar to line. Change the style of the graph from stacked to lines or symbols. Enable or disable the legend for graph views. Not applicable Not applicable The Graph Legend on page Teradata Manager User Guide

43 Chapter 3: Getting Started With Teradata Manager Teradata Manager File Locations Window Menu Table 9: Window Menu Commands Command Description Additional Information Cascade Tile Arrange the open windows in a cascading pattern Arrange the open windows in a tile pattern Not applicable Not applicable Help Menu Table 10: Help Menu Commands Command Description Additional Information Help Topics About Teradata Manager Open the Teradata Manager help file Get information about Teradata Manager, including the product version number and the date created, the current logon database, connection type, the client character set, name of the user, and profile name. Not applicable Not applicable Teradata Manager File Locations Teradata Manager files are stored in the various locations described in the following tables. In all cases: x - The drive selected during the installation procedure userid - The name of the logged on user DatabaseName - The name of the Teradata Database being monitored by Teradata Manager. Teradata Manager User Guide 43

44 Chapter 3: Getting Started With Teradata Manager Teradata Manager File Locations Table 11: Teradata Manager File Locations These types of files... Program files and other read-only files Data files, reports and logs Are stored in... The program files directory. The default is: x:\program Files\NCR\Teradata Manager 12.0 The Teradata Manager 12.0 directory contains the following subdirectories: BIN - Program executable files, resource files and some help files Data - Template files and data files Help - HTML Help files Samples - Sample code to get started with the Teradata Manager Performance Object Model Secure - All user applications and BTEQ scripts that are called by alert actions. It is recommended that write permission to this directory are only granted to users responsible for setting up the Teradata Alerts system. SQL - SQL scripts used to set up the Teradata Manager tables, and for various applications to retrieve data The user s My Documents directory. The default is: x:\documents and Settings\<userid>\My Documents\NCR\Teradata Manager This directory contains the following sub-directories: Data - Saved run-time data Profiles - Logs and other output files associated with databases being monitored by Teradata Manager Teradata Manager Service log files (tmgr.log) User s personal Teradata Manager log files (tmgr.log) Alert Action log file (alerts.log) Alert Policy Editor log file (ape.log) The system application data directory. The default is: x:\documents and Settings\All Users\Application Data\NCR\Teradata Manager The user s My Documents directory. The default is: x:\documents and Settings\<userid>\My Documents\NCR\Teradata Manager\Profiles\ <DatabaseName>\LOGS The system application data directory. The default is: x:\documents and Settings\All Users\Application Data\NCR\Teradata Manager\Databases\<DatabaseName>\ The user s My Documents directory. The default is: x:\documents and Settings\<userid>\My Documents\NCR\Teradata Manager\Data\ 44 Teradata Manager User Guide

45 Chapter 3: Getting Started With Teradata Manager Printing or Saving the Currently Displayed Report or Graph Printing or Saving the Currently Displayed Report or Graph After creating a report or graph using the Teradata Manager reporting features described throughout this user guide, there are several options for printing or saving the data in various formats, including tab-delimited and XML. To print a displayed report or graph 1 From the Teradata Manager menu bar, click File>Print. The Print dialog box appears. 2 Choose your print options, and click OK. To preview a displayed report or graph before printing 1 From the Teradata Manager menu bar, click File>Print Preview. The report or graph appears in the Preview window. 2 Use the buttons on the top of the window, to do the following: To move forward or back in a multiple page report, click Next Page or Prev Page. To view two pages of a multiple page report at once, click Two Page. To change the magnification of the report or graph, click Zoom In or Zoom Out. To print the report or graph, click Print to display the Print dialog box. Choose your print options, and click OK. To close the Preview window without printing the report or graph, click Close. To save a displayed report or graph 1 From the Teradata Manager menu bar, click File>Save As. The Save As dialog box appears. 2 In the Save in list, navigate to the folder to save the report or graph. 3 Enter a file name for the report in the File name box. 4 Select the format by using the Save as type list. Use the.xml format to load the report back into Teradata Manager where it can be viewed and analyzed by clicking File>Open. Use the other formats to open the data using external applications. Save a report using the following formats: Comma Separated Values (*.csv) Text with Tab Delimiters (*.txt) Extensible Markup Language (*.xml) Teradata Manager User Guide 45

46 Chapter 3: Getting Started With Teradata Manager Creating a Batch Version of a Teradata Manager Report Save a graph using the bitmap image (*.bmp) format. 5 Click Save to save the file to the selected location. Creating a Batch Version of a Teradata Manager Report Teradata Manager allows collection of all of the information about the currently displayed report where it can be saved to a batch file as a command. After this batch file is created, it can be scheduled to run at a specific time. When it is executed, the batch file creates an output file that can be opened in Teradata Manager. For example, click Monitor>Sessions>Blocked to schedule a report to run every hour and record any blocked sessions. Note: The command created when using this option contains your Teradata Database username and password. However, when the command is saved in a batch file, the password and authentication mechanism are encoded for security purposes. To create a batch version of a Teradata Manager report 1 Display the applicable report in Teradata Manager. For example, click Monitor>Sessions> Blocked. 2 With the report window active, click File>Append Command to Batch File. The Append Command to Batch File dialog box appears. The last argument of the displayed command is the name of the output file that the batch file creates. For example, Session.xml. 3 Click OK The Open dialog box appears. 4 Navigate to the Teradata Manager BIN directory. For example, C:\Program Files\NCR\Teradata Manager 12.0\BIN. Do one of the following: To create a new batch file that executes this command, enter a name for the batch file in the File Name field, using a file extension of.bat, and click Open to save the file to the BIN directory. To append this command to an existing batch file, select the applicable batch file so its name appears in the File Name field, then click Open. 5 Run the.bat file by scheduling it or executing it manually at any time. The executed file creates a report. 6 To see the report, click File>Open to open the.xml file. 46 Teradata Manager User Guide

47 CHAPTER 4 Configuring Teradata Manager Before using Teradata Manager, it must be configured. An overview of the process follows: 1 Set up the Teradata Database with the appropriate tables and macros 2 Add users, giving them access to the database contents 3 Define various system parameters 4 Enable data collection The following topics explain how to perform these procedures in detail. If configuring a new installation of Teradata Manager, complete steps one through eight. If upgrading Teradata Manager, perform steps one and two. Step 1 - Creating the Teradata Manager Databases, Tables, and Macros Step 2 - Adding Teradata Manager Users Alternative to Steps 1 and 2 - Using the Setup Script Instead of Database Setup Step 3 - Starting Teradata Manager Step 4 - Restricting User Access with Profiles Step 5 - Authorizing User Access to Profiles Step 6 - Defining System Parameters Step 7 - Setting RSS Collection Rates Step 8 - Enabling Data Collection The following topics explain how to configure parameters and change options and settings: Specifying an External DBQL for Data Collection and Trend Reporting Configuring AMP Usage Data Collection Parameters Configuring DBQL Data Collection Parameters Configuring Teradata Dynamic Workload Management Data Collection Parameters Configuring Heartbeat Query Data Collection Parameters Configuring Priority Scheduler Data Collection Parameters Configuring Query Band Pairs Data Collection Parameters Configuring Resource Usage Data Collection Parameters Configuring Spool Space Data Collection Parameters Configuring Table Space Data Collection Parameters Configuring Your Color Display Options Checking the Status of the Teradata Manager Server Teradata Manager User Guide 47

48 Chapter 4: Configuring Teradata Manager Step 1 - Creating the Teradata Manager Databases, Tables, and Macros Changing Logon Settings Restoring the Default Preferences for Tables and Graphs Adding Application Specific Entries to the Registry Adding Additional Applications to the Teradata Manager Menu Bar Setting the Port Number for TCP/IP Setting the Security Mechanism and Character Set Step 1 - Creating the Teradata Manager Databases, Tables, and Macros After Teradata Manager has been installed, the Teradata Database needs to be set up with the databases, tables, and macros necessary to run Teradata Manager. The Database Setup application assists in this task. Database Setup uses your parameters to generate SQL statements for creating and modifying databases, tables, and macros on the specified database. Each SQL statement and its execution status (whether it was submitted successfully or unsuccessfully) is logged in the main window of the application. Note: To use an SQL Script instead of Database Setup, see Alternative to Steps 1 and 2 - Using the Setup Script Instead of Database Setup on page 52. Note: If upgrading the Teradata Database from V2R6.x to 12.0, see To run Database Setup twice if upgrading the Teradata Database on page 51. To set up the database attributes required by Teradata Manager 1 From the Windows desktop, click Start>Programs>Teradata Manager 12.0>Database Setup. 2 Fill in the fields as follows: Database Name - the TDPid of the Teradata Database. Super User - the name of the primary administrator for the database. This defaults to DBC. Super User Password - the string the primary administrator enters to access the database. Console Password - the password of the console user. If the console user already exists, the Database Setup logs on to the database as console with the user s password. If the console user does not exist, the console user is created and assigned the supplied password. Set up Database for Teradata Manager must be checked. Perm Space - the amount of permanent space allocated to the new database. See Perm Space Requirements for Historical Trend Data Collection on page 63 for information on sizing the database. 48 Teradata Manager User Guide

49 Chapter 4: Configuring Teradata Manager Step 1 - Creating the Teradata Manager Databases, Tables, and Macros Database Type - select the type of operating system the new database is running on. Spool Space - the amount of spool space allocated to the new database. If the new database inherits the same amount of space as its parent, select the Same as Parent check box. Create a Teradata Manager User - select this check box to create a new user. For the sake of simplicity, clear this check box (this topic is covered in the next procedure). Migrate TDWM Database - select this check box to have Database Setup migrate the tdwm database from V2R6.x to TDWM Perm Space - the limit on permanent space assigned to the tdwm database. This field is ignored if the database is V2R6.x. The recommended setting is 2 MB per AMP vproc. For example, on a system with 128 AMPs, set to 256 MB or larger. Spool Space - the limit on spool and temporary space assigned to the tdwm database. This field is ignored if the database is V2R6.x. To have the tdwm database inherit the same amount of space as its parent, select the Same as Parent check box. 3 Click OK to run Database Setup with your parameters. A log of the program results display in the main window of the application. 4 Continue with the configuration by going to the next procedure: Step 2 - Adding Teradata Manager Users on page 50. Setting Up Coexistence Systems If the database is a coexistence (mixed platform) system, then customize the definitions of the dbcmngr.ampcpubynodetype view and the dbcmngr.dcinsnodeidtogroupid macro as part of the setup process. The data collection and trend reporting features use these objects in Teradata Manager to associate Teradata Database resource usage with the appropriate node groupings. To run Database Setup If the Database Setup program is being used, first run Database Setup to update the dbcmngr database, then extract the view and macro definitions from one of the scripts and modify them as described below. After modifying the definitions, apply them to the Database using Teradata SQL Assistant or BTEQ. To run the setup scripts If either of the setup scripts is being used (dbssetup.scr or dbsupgrd.scr) instead of Database Setup, then as part of editing the script, do the following: 1 Search the script for the definition of view AmpCpuByNodeType 2 Edit the CASE expression within the view definition, replacing the node names and model numbers with the system's actual node names and corresponding models. Teradata Manager User Guide 49

50 Chapter 4: Configuring Teradata Manager Step 2 - Adding Teradata Manager Users For example, if the DBS consists of two model 4700 nodes, named 1-01 and 1-02, and four model 4800 nodes, named 2-01, 2-02, 3-01, and 3-02, then the view's CASE expression would need to look like this: CASE WHEN NodeId IN ('001-01', '001-02') THEN '4700' ELSE '4800' END, Skip the remaining steps in this procedure if configuring Teradata Database 12; the dcinsnodeidtogroupid macro is only used on V2R6.x databases. 3 Search the script for the definition of macro dcinsnodeidtogroupid. 4 Replace the literal 'A' in the SELECT statement with a CASE expression that assigns each node to the proper GroupId. Using the example described above, the customized macro would look as follows: REPLACE MACRO DBCMNGR.dcInsNodeIdToGroupId(SDate INTEGER, STime INTEGER, EDate INTEGER, ETime INTEGER) AS ( LOCKING TABLE DBC.ResUsageSPMA FOR ACCESS INSERT DBCMNGR.tmNodeIdToGroupIdTbl (Id, GroupId, CPUCnt) SELECT NodeID,CASE WHEN NodeID IN ('001-01', '001-02') THEN '4700' ELSE '4800' END,AVG(NCPUs) FROM DBC.ResUsageSPMA WHERE ((TheDate = :SDate AND TheTime > :STime) OR TheDate > :SDate) AND ((TheDate = :EDate AND TheTime <= :ETime) OR TheDate < :EDate) GROUP BY 1,2; ); Step 2 - Adding Teradata Manager Users After setting up the Teradata Manager databases, tables, and macros, use the Database Setup application to add users and give them the various permissions necessary to run the Teradata Manager applications. To add a user with permission to run Teradata Manager applications 1 From the Windows desktop, click Start>Programs>Teradata Manager 12.0>Database Setup. 2 Clear the Set up Database for Teradata Manager check box. 3 Select the Create a Teradata Manager User check box. 4 Fill in the fields as follows: Database Name - the TDPid of the Teradata Database Super User - the name of the primary administrator for the database. This defaults to DBC 50 Teradata Manager User Guide

51 Chapter 4: Configuring Teradata Manager Step 2 - Adding Teradata Manager Users Super User Password - the string the primary administrator enters to access the database Console Password - the password of the console user. If the console user already exists, the Database Setup logs on to the database as console with the user s password. If the console user does not exist, the console user is created and assigned the supplied password. Set up Database for Teradata Manager must be unchecked User Name - the logon name for the Teradata Manager user User Account String - the database related account string for the new user User Password - the string the user enters to access Teradata Manager Confirm Password - the same as the User Password Perm Space - the amount of permanent space allocated to the new user. Spool Space - the amount of spool space allocated to the new user. To have the new user inherit the same amount of space as its parent, select the Same as Parent check box. The user can run all applications displayed in the Give user privileges to run list. 5 [Optional] If a user should not have privileges to run an application, click the application name in the Give user privileges to run list, and click the left arrow. The application appears in the Do not give user privileges to run list. 6 Click OK to run Database Setup with your parameters. A log of the program results are displayed in the main window of the application. 7 Continue with the configuration by going to: Step 3 - Starting Teradata Manager on page 55. If upgrading the Teradata Database from V2R6.x to 12.0, complete To run Database Setup twice if upgrading the Teradata Database on page 51 before continuing to Step 3 - Starting Teradata Manager on page 55. To run Database Setup twice if upgrading the Teradata Database Completing this procedure updates dbcmngr objects and re-establishes user access rights. 1 Perform Step 1 - Creating the Teradata Manager Databases, Tables, and Macros on page 48 and Step 2 - Adding Teradata Manager Users on page 50 before starting Teradata Manager 12.0 for the first time on either a V2R6.x or 12.0 Teradata Database. 2 Repeat Step 1 and Step 2 again after upgrading the Teradata Database from V2R6.x to 12.0, even if Teradata Manager 12.0 had already been set up on the V2R6.x database. For example, suppose Teradata Manager 12.0 is configured and operational on a V2R6.x database. Some time later, the Teradata Database is upgraded to After the database upgrade from V2R6.x to 12.0, Teradata Manager 12.0, Database Setup must be run again. Teradata Manager User Guide 51

52 Chapter 4: Configuring Teradata Manager Alternative to Steps 1 and 2 - Using the Setup Script Instead of Database Setup Alternative to Steps 1 and 2 - Using the Setup Script Instead of Database Setup As an alternative to creating the databases, tables and macros using Database Setup, Teradata Manager supplies an SQL script that can be edited to fit your installation requirements. Use the following procedure to tailor the supplied SQL script for your installation. The script has two sections: The first section creates databases, tables, views, and macros required by Teradata Manager to access the Teradata Database and to enable running Teradata Manager applications. This portion of the script should ordinarily be run once for each database; however, after upgrading the Teradata Database from V2R6.x to 12.0, the first section of the script needs to be run again. See To run the script twice if upgrading the Teradata Database on page 53. The second section is used for creating Teradata Database logon IDs for Teradata Manager users. The default user ID, DBCMANAGER, is pre-configured in the script. Note: Depending on your system configuration and the size of your system tables, there may be a need to increase the spool space to ensure the customized Teradata Manager SQL statements and macros run successfully. Note: The SQL scripts cannot be used to migrate the tdwm database. To migrate the tdwm database, run the Database Setup application as described in TDWM Setup on Teradata Database 12 on page 54. To set up the database using the Teradata Manager setup script 1 Start an ASCII text editor (for example, Windows Notepad) and open one of the following script files: If this is a new installation, open file \SQL\DBSSETUP.SCR in your Teradata Manager installation directory If this is an upgrade installation, open file \SQL\DBSUPGRD.SCR in your Teradata Manager installation directory 2 Replace the following fields to reflect the Teradata Database names and passwords in use at your installation: Database Name - the TDPid of the Teradata Database. DBC username - the name of the primary administrator for the database. This defaults to DBC. DBC password - the string the primary administrator enters to access the database Console password - the console user s password. If the console user already exists, then Database Setup logs on to the Database as console using the password supplied. If the console user does not exist, the console user is created and assigned the supplied password. DBCMANAGER username - the logon name for the Teradata Manager user. 52 Teradata Manager User Guide

53 Chapter 4: Configuring Teradata Manager Alternative to Steps 1 and 2 - Using the Setup Script Instead of Database Setup BOOLDBSTYPE - the type of operating system the new database is running on. Replace with 1 for Unix, 0 for Windows or Linux. SQLDIR - the path to the Teradata Manager SQL directory. 3 Save the file using a new name (for example, DBSSETUPNEW.SCR) and exit the editor. 4 Run the dbssetup script: a b c Click Start>Programs>Run. Enter the path to BTEQWIN. The default location is c:\program Files\NCR\Teradata Manager 12.0\Bin\bteqwin.exe. Select the character set. For Teradata Database 12.0, click UTF16. For V2R6.x, click ASCII for standard language systems and KANJISJIS_0S for Kanji systems. 5 In the BTEQWIN window, enter the SQL command to run the tailored start-up script that was previously edited. For example, if the start-up script is saved as a file called DBSSETUPNEW.SCR in your Temp directory, the command would be:.run file c:\temp\dbssetupnew.scr The script runs and BTEQWIN logs the results. 6 When the script execution is complete, use the scrolling window to ensure all the requests sent to the Database were successful. To run the script twice if upgrading the Teradata Database 1 Run the dbssetup or dbsupgrd script before starting Teradata Manager 12.0 for the first time on either a V2R6.x or 12.0 Teradata Database. 2 Run the dbsupgrd script after upgrading the Teradata Database from V2R6.x to 12.0, even if Teradata Manager 12.0 had already been set up on the V2R6.x database. For example, suppose Teradata Manager 12.0 is configured and operational on a V2R6.x database. Some time later, the Teradata Database is upgraded to After the database upgrade from V2R6.x to 12.0, the Teradata Manager 12.0 Database Setup must be run again. Unicode Migration on Teradata Database 12 The Teradata Manager tables in database dbcmngr support Unicode text on Teradata Database 12.0 and later databases. When the first section of Database Setup is run on a Teradata 12.0 system, it performs Unicode migration logic to translate text data in existing (pre-unicode) dbcmngr tables to the Unicode character set. Depending on the amount of data in the dbcmngr tables, Unicode migration may take a substantial amount of time. The following steps are recommended: 1 Stop all running Teradata Manager applications. 2 Stop the Teradata Manager Service. 3 Backup the dbcmngr database. Teradata Manager User Guide 53

54 Chapter 4: Configuring Teradata Manager Alternative to Steps 1 and 2 - Using the Setup Script Instead of Database Setup 4 Make sure there is sufficient available perm space in database dbcmngr before starting Database Setup. Sufficient space is considered approximately 150% of perm size of the largest dbcmngr table. TDWM Setup on Teradata Database 12 Database Setup creates the tdwm database on Teradata Database 12. If an existing V2R6 version of the tdwm database is found, Database Setup also migrates the existing rule sets to the new version 12 database. To create or migrate the tdwm database 1 From the Windows desktop, click Start>Programs>Teradata Manager 12.0>Database Setup. 2 Do one of the following: Select the Set up Database for Teradata Manager check box for Database Setup to run through the Teradata Manager (database dbcmngr) setup before creating and migrating TDWM. To perform the TDWM operations automatically, also select the Migrate TDWM Database check box. If the Migrate TDWM Database check box is not selected and an existing tdwm 6 database is found, a prompt displays to do one of the following: Create the tdwm 12 database Create the tdwm 12 database and migrate the tdwm 6 database Skip the operation which cancels the set up and migration Clear the Set up Database for Teradata Manager check box, and select the Migrate TDWM Database check box to bypass Teradata Manager (database dbcmngr) setup and perform the TDWM creation and migration process automatically. The tdwm 12 database is created and the tdwm 6 database is migrated automatically. In all of the above scenarios, if an old or unknown tdwm database is found, a prompt displays to do one of the following: Create the tdwm 12 database without migrating the old tdwm database Skip the operation which cancels the set up and migration If the Teradata Database does not have an existing tdwm database, the tdwm 12 database is simply created. If the Teradata Database has an existing tdwm database, it is backed up to a database named tdwm6 before any operation is performed. 54 Teradata Manager User Guide

55 Chapter 4: Configuring Teradata Manager Step 3 - Starting Teradata Manager Step 3 - Starting Teradata Manager After the appropriate database attributes and users have been established by running Database Setup, start Teradata Manager to enter logon information and choose a profile. To start Teradata Manager 1 From the Windows desktop, click Start>Programs>Teradata Manager 12.0>Teradata Manager. The Logon Information dialog box appears. 2 Fill in the fields as follows: System (DBS) Name - the TDPid of the Teradata Database Username - the name used to log on to Teradata Manager Password - the string used to access Teradata Manager for the above Username Account Id - the Database related account string 3 Select the applicable profile using the Profile box. To log in the first time, or if no other profiles have been created, click the DEFAULT profile. 4 For Teradata Manager to remember your login settings, select the Save as defaults check box. 5 If a security mechanism is in place or to select a different character set for logging on to the client, click Advanced. See To set for a client log on on page Connecting through the server provides the most efficient way to run Teradata Manager. To connect through a server, select Get data from Server, then enter the Server Name. To use your local PC as the server, enter the string localhost for the Server Name. If unable to connect through the server because the Teradata Manager Service has not been configured to monitor the selected system or the Service is not running, select Get data direct from Teradata Database to connect in direct mode. Note: For instructions on configuring the Teradata Manager Service to monitor a system, see Step 6 - Defining System Parameters on page For Teradata Manager to display this dialog box on subsequent logins, select Automatically show this dialog box next time. 8 Click OK. 9 After completing these steps, continue with the configuration by going to the next procedure, Step 4 - Restricting User Access with Profiles on page 56. Teradata Manager User Guide 55

56 Chapter 4: Configuring Teradata Manager Step 4 - Restricting User Access with Profiles Step 4 - Restricting User Access with Profiles Each Database contains a set of one or more profiles. A profile named DEFAULT is created when Database Setup is run. This DEFAULT profile provides access to all Teradata Manager features. Additional profiles can be created with more restricted feature sets. The Authorization tab is used to assign the list of database users that is allowed access to each profile. See Step 5 - Authorizing User Access to Profiles on page 57. A user can be authorized to use more than one profile. A user that is not authorized to use any profile is not able to start Teradata Manager. Profiles can be configured for only one database at a time. To work with a profile 1 From the Teradata Manager menu bar, click Administer>Teradata Manager. The Profiles tab appears. 2 In the Profile Name list, do one of the following: To modify an existing profile, select the name of the profile To add a new profile, select an existing profile that has similar attributes to the one to be created. Then edit the name in the box to that of the new profile To delete an existing profile, select the name of the profile, then click Delete. Caution: A warning appears when attempting to delete the last profile. To not delete the last profile, click Cancel. To delete the profile, click OK. If the last profile is deleted and the user cannot log on to Teradata Manager, consult your DBA to run Database Setup to recover the DEFAULT profile. 3 For the profile to be available when a user logs in to Teradata Manager, select the Enabled check box. 4 Using the Profile Options check box tree, select the Teradata Manager capabilities for users of this profile to access. If a check box is unchecked, all menu items that pertain to the corresponding capability are removed from the menu at run time. Note: Features marked with * can modify the database. 5 Do one of the following: To modify an existing profile, click Modify To add a new profile, click Add 6 Click OK. 7 After creating the profile, authorize its use by completing the next procedure: Step 5 - Authorizing User Access to Profiles on page Teradata Manager User Guide

57 Chapter 4: Configuring Teradata Manager Step 5 - Authorizing User Access to Profiles Step 5 - Authorizing User Access to Profiles By default your system is configured so that all users have access to all Teradata Manager features. If this is acceptable, skip this step. To authorize user access to profiles 1 From the Teradata Manager menu bar, click Administer>Teradata Manager. 2 Click the Authorization tab. 3 In the Choose a profile box, select the profile to set user access. 4 For all users to have access to the selected profile, select All users may use this profile. 5 To define a restricted set of users for the selected profile, do the following: a b c Select Only the following users may use this profile. Select the users to give access from the Not Allowed to Use Profile list and click Add->. This moves the selected users to the Allowed to Use Profile list. To remove users from the Allowed to Use Profile list, select the users to remove and click <-Remove. This moves the users back to the Not Allowed to Use Profile list. 6 Click Modify to save your changes. 7 Click OK. 8 Continue with the configuration by going to the next procedure: Step 6 - Defining System Parameters on page 57. Step 6 - Defining System Parameters This step is required to use any or all of the following Teradata Manager features: Alerts Client-Server mode Dashboard Workload trend analysis To set system parameters 1 From the Teradata Manager menu bar, click Administer>Teradata Manager. 2 Click the System tab. 3 In the System (DBS) Name box, do one of the following: To modify an existing system, select the name of the system. To add a new system, do one of the following: Teradata Manager User Guide 57

58 Chapter 4: Configuring Teradata Manager Step 6 - Defining System Parameters If one exists, select an existing system that has similar attributes to the one that is being adding, then edit the name in the box to that of the new system, and click Add. Type the database name in the System (DBS) Name box, enter the logon information, and click Add. To delete an existing system, select the name of the system, and click Delete. Skip the rest of this procedure. 4 To view a list of all currently enabled systems, click Summary. 5 For the system to be available when a user logs in to Teradata Manager, select the Enabled check box. Note: The Enabled check box tells the service that is running on that PC to monitor the selected database. To run Dashboard or any application that utilizes the service, it must connect to a service that has the system defined and enabled. 6 Enter the number of nodes that are running PDE, but are not running the Teradata Database in the Number of non-tpa nodes box. 7 If the Alerts service is running: Under Alerts, enter the priority string in the Lower Priority Action box. The <Lower Priority> action assigns the priority. If this box is left blank, the default $L (low priority) is used. Any system-defined priority like $M, or a user-defined performance group name like $TESTGRP$ can be used. A user-defined performance group name is surrounded by $ and can be up to 18 characters, including the $. Enter the name for your log in the Log File Name box and the maximum log file size, in kilobytes, in the Log Size box. To set the Log File Name to alerts.log and Log Size to 1024, click Defaults. Note: The log file is a circular file which overwrites old data once the maximum size has been reached. If a Microsoft client is used such as Outlook, click Configure and input your settings as follows in the Network Logon dialog box: Username - the client user name Password - the password for the client user name Domain - the client domain name To use SMTP mail, select the Use SMTP Mail check box, click Configure , and input your settings as follows: SMTP Server - name of the SMTP server. SMTP Port - the port STMP is available on. The default is port 25. Server Timeout - the amount of time, in seconds, the connection is attempted before timing out. The default is 30 seconds. This server requires a secure connection (SSL) - select this check box if your server requires a Secure Socket Layer connection. Reply Address - the address that appears in the reply field of the Teradata Manager User Guide

59 Chapter 4: Configuring Teradata Manager Step 6 - Defining System Parameters Authentication Method - click Anonymous Logon, Basic Authentication (requiring a username and password), or NTLM. NTLM is the Microsoft Windows NT Lan Manager or the Teradata Database NTLM security mechanism that supports it. For more information, see Security Administration. See Additional Information on page 6 to locate this resource. Test Recipient - entering an address and clicking Test allows the SMTP mail server to be tested instantly. Do this to confirm SMTP mail can be sent successfully. This step is strongly recommended before running the alert editor to configure mail alerts. Click Defaults to fill the fields with the default settings. Click OK to save the settings. 8 Complete this step for Teradata Database V2R6.x. Skip this step for Teradata Database 12.0 or later. If the Teradata Database is an SMP system running on a Windows operating system, do the following to enable the Teradata Manager Alert Service to check for Teradata error messages: a Select the Teradata on Windows OS check box b Click Configure Windows OS and enter the login information of a Windows user that can access the event log on the Teradata Database host. Note: For Teradata Database V2R6.x on Windows, the Teradata Manager event log alerting feature only supports SMP configurations. 9 Under Logon Information, fill in the Teradata Manager Service logon credentials as follows: Username, Password and Account - the values that the Teradata Manager Service uses to log onto the database to monitor it. Username is a user that was created using Database Setup. [Optional] Default Database - override the default database in the sessions that the Teradata Manager Service establishes. If a security mechanism is in place or to select a different character set for logging on to the Teradata Manager Service, click Advanced. See To set for the Teradata Manager Service on page 83. To change the password of the service user, click Change DBS Password. Fill in the fields as follows: Logon User Name - Type the service user s name or Super User name. Logon Password - Type the logon password for the above user New Password - Type the new password for the service user Confirm New Password - Type the new password again 10 Do one of the following: If modifying an existing system, click Modify If adding a new system, click Add 11 Click OK. Teradata Manager User Guide 59

60 Chapter 4: Configuring Teradata Manager Step 7 - Setting RSS Collection Rates 12 Continue with the configuration by going to the next procedure, Step 7 - Setting RSS Collection Rates on page 60. Step 7 - Setting RSS Collection Rates RSS collection rates determine how often PM/API data are refreshed. This affects many Teradata Manager applications and reports; therefore, RSS collection rates must be set if using the Dashboard, reports from the Teradata Manager Monitor menu, Session Information, Performance Monitor, Alerts, Historical Resource Usage, or Resource Usage Trends. RSS collection rates can be set in a number of ways. They can be set with utilities such as ctl, xctl, or cnscons, or PMON s Set Monitor Rates feature, or using the following procedure. To set collection rates 1 From the Teradata Manager menu bar, click Administer>Teradata Manager. 2 Click the Collection Rates tab. 3 Select the System (DBS) Name from the list. 4 Set the collection rates by entering a rate ranging from 0 to The node and vproc rates must be an integer divisor of When one of these rates is changed, the other is changed to the same value. Node - the current collection rate for the node. Vproc - the current collection rate for the vproc. Session - the current collection rate for the session. If -1 appears in the fields for collection rates, either collection has not been initiated or the server was unable to fetch the rates. The log rates display as read-only and correspond to the node and vproc logging rates. To change log rates, use PMON s Set Monitor Rates feature. 5 Click Modify. A message appears indicating the collection rates were modified successfully. 6 Click OK to close the message. 7 To restore the rates to the last saved values, click Cancel. 8 Continue with the configuration by going to the next procedure: Step 8 - Enabling Data Collection on page Teradata Manager User Guide

61 Chapter 4: Configuring Teradata Manager Step 8 - Enabling Data Collection Step 8 - Enabling Data Collection For the Teradata Manager Service to collect data, use the following procedure to configure, schedule, and enable data collection tasks. Note: The Teradata Manager client does not have to be running for the service to perform data collection. The Workload Trends reporting feature uses data collected from the Teradata Manager Service. For information about this feature, see Chapter 9: Analyzing Workload Trends. To enable data collection 1 From the Teradata Manager menu bar, click Administer>Teradata Manager. 2 Click the Data Collection tab. 3 View the following data collection information: Column Name Source Configured Summary Retention Detail Retention Next Event Description Lists all of the potential data collection tasks Contains a yes or no text field indicating if the task has been configured. A task must be configured before it can be scheduled. Lists the number of days that summary data is saved in the data collection tables Lists the number of days that data is retained in the underlying DBC tables. A value of N/A indicates that no historical information is saved. If the task has been scheduled and enabled, shows the date and time of the next scheduled collection. If the task has been scheduled but disabled, Disabled appears in this column. If the task has not been scheduled, Not Scheduled appears in this column. 4 To configure a task, click to highlight it. 5 Click Configure and follow these links for information on the task-specific configuration dialog boxes: Configuring AMP Usage Data Collection Parameters on page 70 Configuring DBQL Data Collection Parameters on page 71 Configuring Teradata Dynamic Workload Management Data Collection Parameters on page 72 Configuring Heartbeat Query Data Collection Parameters on page 72 Configuring Priority Scheduler Data Collection Parameters on page 73 Configuring Query Band Pairs Data Collection Parameters on page 74 Teradata Manager User Guide 61

62 Chapter 4: Configuring Teradata Manager Step 8 - Enabling Data Collection Configuring Resource Usage Data Collection Parameters on page Teradata Manager User Guide

63 Chapter 4: Configuring Teradata Manager Step 8 - Enabling Data Collection Configuring Spool Space Data Collection Parameters on page 75 Configuring Table Space Data Collection Parameters on page 76 Note: The following tasks do not require configuration. However, data collection logon credentials can be entered. See Assigning Data Collection Logon Credentials on page 65. Reset Peak Spool Space This task updates the peak spool and peak temp space statistics for all users in dictionary table dbc.databasespace. When the task runs, it sets PeakSpoolSpace to CurrentSpoolSpace and PeakTempSpace to CurrentTempSpace for all users. Cleanup This task deletes old data from the dbcmngr data collection tables depending on the setting of the Retention Period for Summary Data option of each collection task. For example, if this option is set for 2 years for the Ampusage collection task, the Cleanup task deletes rows from dbcmngr.logampusage where TheDate is older than 2 years. 6 After the parameters are saved, click OK to return to the Data Collection tab. 7 With the task still highlighted, click Schedule. 8 The Name box displays with an internal name that cannot be modified. Tasks that launch applications are called external tasks. Data collection tasks are called internal tasks. Although they are different, follow the same instructions for scheduling them. For instructions on scheduling, see Scheduling Tasks That Launch Applications on page 263. Note: Data Collection tasks execute on the Teradata Database as ordinary user sessions. To distribute the overhead of data collection on the Teradata Database, schedule the data collection tasks to start at different times. To do this, select At a Specific Date/Time when scheduling each task, as described in Scheduling Tasks That Launch Applications on page After saving the schedule, click Close to return to the Data Collection tab. Note: The data collection tasks record date and time values that the Teradata Database returns. Therefore, date and time stored in the log tables do not match the date and time of the Teradata Manager workstation if the clock on the workstation is in a different time zone from, or out of sync with, the Teradata Database. Perm Space Requirements for Historical Trend Data Collection The Teradata Manager Data Collection feature stores historical data in database dbcmngr. It is recommended the perm space (MaxPerm) setting be modified for database dbcmngr as indicated in Table 12. Teradata Manager User Guide 63

64 Chapter 4: Configuring Teradata Manager Step 8 - Enabling Data Collection Table 12: Perm Space Requirements for Data Collection Type of Data Table Name Space required Example AmpUsage dbcmngr.logampusage 510 KB per 100 active useraccounts DBQL dbcmngr.logdbql 3 KB per User ID per AcctString per AppID DBQL dbcmngr.logdbqlstep 100 bytes per User ID per StepName Heartbeat query dbcmngr.logheartbeat 7.1 KB per heartbeat In an environment with an average of 500 active user-accounts (distinct username and account string pairs), if Teradata Manager is configured to collect AmpUsage data every four hours (six times per day), then this table grows at a rate of 15.3 MB per day, or approximately 5.45 GB per year. With hourly summarization on a system having 20 active users and each having a single account string and a single AppID during the hour, this table grows approximately 60 KB per day, or 21.4 MB per year. With hourly summarization on a system having 20 active users and each user s queries generating an average of 10 different step types, this table grows approximately 80 KB per interval, or 28.5 MB per year. If Teradata Manager is configured to execute one heartbeat query every hour, and the heartbeat query remains constant, then this table will grow at a rate of 170 KB per day, or approximately 61 MB per year. Priority Scheduler configuration dbcmngr.logschmonrp, dbcmngr.logschmondag, dbcmngr.logschmonpg 12 KB per change in configuration On a Teradata Database that is configured with the DEFAULT resource partitions and allocation groups, if RP, AG, and PG settings are modified once per month, and if Teradata Manager is configured to collect Priority Scheduler Configuration daily, then these tables collectively grow approximately 144 KB per year (12 KB per month). Priority Scheduler node Priority Scheduler system dbcmngr.logschmonnode 7.5 KB per policy On a Teradata Database that is configured with the DEFAULT resource partitions and allocation groups, if Teradata Manager is configured to collect Priority Scheduler Node Performance once per hour, then this table grows at a rate of 180 KB per day, or approximately 65 MB per year. dbcmngr.logschmonsystem 7.5 KB per policy On a Teradata Database that is configured with the DEFAULT resource partitions and allocation groups, if Teradata Manager is configured to collect Priority Scheduler System Performance once per hour, then this table grows at a rate of 180 KB per day, or approximately 65 MB per year. 64 Teradata Manager User Guide

65 Chapter 4: Configuring Teradata Manager Step 8 - Enabling Data Collection Table 12: Perm Space Requirements for Data Collection (continued) Type of Data Table Name Space required Example Resource Usage dbcmngr.logresusagehost 300 bytes per GroupId per HstType Resource Usage dbcmngr.logresusagenode 1.5 KB per node group (GroupId) For a non-coexistence system with hourly summarization and a NETWORK hsttype, this table grows approximately 7 KB per day, or 2.5 MB per year. For a non-coexistence system with hourly summarization, this table grows approximately 36 KB per day, or 13 MB per year. Resource Usage dbcmngr.logresusagevpro c 4.0 KB per GroupId For a non-coexistence system with hourly summarization, this table grows approximately 96 KB per day, or 34 MB per year. Resource Usage dbcmngr.logsystemactivity 2.7 KB per collection Spool Space dbcmngr.logspool 42 KB per 100 users Table Space dbcmngr.logperm 42 KB per 100 tables TDWM dbcmngr.logwdsummary 400 bytes per workload definition If Teradata Manager is configured to collect Resource Usage data hourly, then this table grows at a rate of 64 KB per day, or approximately 23 MB per year. If Teradata Manager is configured to collect spool space usage for 200 users once daily, then this table grows at a rate of 84 KB per day, or approximately 30 MB per year. If Teradata Manager is configured to collect space usage for 200 tables once daily, then this table grows at a rate of 84 KB per day, or approximately 30 MB per year. With hourly summarization on a system having 10 workload definitions, this table grows approximately 4 KB per hour, or 17.5 MB per year. Assigning Data Collection Logon Credentials By default, all data collection queries run under the logon credentials specified for the Teradata Manager Service (see Step 6 - Defining System Parameters on page 57); this is typically a user that has been configured with a higher priority so the service can collect PMPC data even when the system is busy. However, to limit the resources allocated to the Data Collector, assign different logon credentials for a task. Since the priority is associated with the specified user, change a task to run at a lower priority than other functions in the service. This feature can also be used to run heartbeat queries at the same priority, or in the same workload, as the applications they are modeling. Teradata Manager User Guide 65

66 Chapter 4: Configuring Teradata Manager Specifying an External DBQL for Data Collection and Trend Reporting To assign data collection logon credentials Logon credentials are stored on the local PC; therefore, the following procedure must be done on the actual system(s) where the Teradata Manager Service executes. 1 From the Teradata Manager menu bar, click Administer>Teradata Manager. 2 Click the Data Collection tab, and highlight the task to configure different logon credentials by clicking on it. 3 Click Configure. If the logon information is left blank, the data collection queries run under the default user. If logon information is specified, the data collection queries run under the specified user. 4 Enter the logon information in the dialog box: Username - the username the data collection queries run under for the specified task. Password - the password for the username. Account ID - the account ID the data collection queries run under for the specified task. Authentication Mechanism - if a security mechanism is in place, select a mechanism Name from the list and enter the applicable authentication string in the Data box. 5 Click OK. Specifying an External DBQL for Data Collection and Trend Reporting The Teradata Manager Query Log and Dynamic Workload Management data collection tasks use database views and macros to access the base DBQL and Teradata DWM log tables. By default, the Teradata Manager views and macros reference base tables in the Teradata data dictionary. If "external" DBQL tables are set up, such as the HST tables recommended by the Teradata DBQL Maintenance best practices, then the Teradata Manager views and macros can be customized to collect data from the external tables instead of the Teradata Database dictionary tables. Typically an external DBQL is used for historical purposes to keep the internal version small for enhanced database performance. Note: Each external table must contain all of the columns of the original DBQL table, but may have different indexes selected. Data collection tasks can be scheduled after completing all of the following steps. Step 1: Customize the Teradata Manager Views Use the following procedure to replace DBQL and TDWM views. 66 Teradata Manager User Guide

67 Chapter 4: Configuring Teradata Manager Specifying an External DBQL for Data Collection and Trend Reporting To replace DBQL and TDWM views In the following REPLACE VIEW statements, substitute the name of the external table in place of the DBC dictionary table, shown in angle brackets. If there is no external table for one or more of the dictionary tables, skip the corresponding REPLACE VIEW statement. REPLACE VIEW dbcmngr.dbqlogvw AS LOCKING TABLE <dbc.dbqlogtbl> FOR ACCESS SELECT * FROM <dbc.dbqlogtbl>; REPLACE VIEW dbcmngr.dbqlsummaryvw AS LOCKING TABLE <dbc.dbqlsummarytbl> FOR ACCESS SELECT * FROM <dbc.dbqlsummarytbl>; REPLACE VIEW dbcmngr.dbqlstepvw AS LOCKING TABLE <dbc.dbqlsteptbl> FOR ACCESS SELECT * FROM <dbc.dbqlsteptbl>; REPLACE VIEW dbcmngr.dbqlsqlvw AS LOCKING TABLE <dbc.dbqlsqltbl> FOR ACCESS SELECT * FROM <dbc.dbqlsqltbl>; REPLACE VIEW dbcmngr.tdwmsummaryvw AS LOCKING TABLE <dbc.tdwmsummarylog> FOR ACCESS SELECT * FROM <dbc.tdwmsummarylog>; REPLACE VIEW dbcmngr.tdwmexceptionvw AS LOCKING TABLE <dbc.tdwmexceptionlog> FOR ACCESS SELECT * FROM <dbc.tdwmexceptionlog>; Step 2: Customize the Teradata Manager Macros Use the following procedure to replace DBQL and TDWM cleanup macros. To replace DBQL and TDWM cleanup macros In the following REPLACE MACRO statements, substitute the names of the external tables in place of the corresponding DBC dictionary tables, shown in angle brackets. REPLACE MACRO dbcmngr.dcdbqldeleteold (AgeDays INTEGER) AS ( DELETE <dbc.dbqlsummarytbl> WHERE CAST(CollectTimeStamp AS DATE) <= (DATE - :AgeDays); DELETE <dbc.dbqlsteptbl> WHERE CAST(CollectTimeStamp AS DATE) <= (DATE - :AgeDays); DELETE <dbc.dbqlogtbl> WHERE CAST(CollectTimeStamp AS DATE) <= (DATE - :AgeDays); DELETE <dbc.dbqlobjtbl> WHERE CAST(CollectTimeStamp AS DATE) <= (DATE - :AgeDays); Teradata Manager User Guide 67

68 Chapter 4: Configuring Teradata Manager Specifying an External DBQL for Data Collection and Trend Reporting DELETE <dbc.dbqlexplaintbl> WHERE CAST(CollectTimeStamp AS DATE) <= (DATE - :AgeDays); DELETE <dbc.dbqlsqltbl> WHERE CAST(CollectTimeStamp AS DATE) <= (DATE - :AgeDays); ); REPLACE MACRO dbcmngr.dctdwmdeleteold (AgeDays INTEGER) AS ( DELETE <dbc.tdwmsummarylog> WHERE CAST(BufferTS AS DATE) <= (DATE - :AgeDays); DELETE <dbc.tdwmeventlog> WHERE CAST(BufferTS AS DATE) <= (DATE - :AgeDays); DELETE <dbc.tdwmexceptionlog> WHERE CAST(BufferTS AS DATE) <= (DATE - :AgeDays); ); Step 3: Customize the Teradata Manager Temporary Work Tables Use the following procedure to replace DBQL and TDWM temporary work tables. To replace DBQL and TDWM temporary work tables If the Teradata Database is V2R6.x and the external tables contain PPI columns, skip to step 2, otherwise continue. 1 In the following CREATE TABLE statements, substitute the names of the external tables in place of the DBC dictionary table, shown in angle brackets. If there is no external table for one or more of the dictionary tables, skip the corresponding CREATE TABLE statement. DROP TABLE DBCMNGR.tmQLIntervalTbl; CREATE MULTISET GLOBAL TEMPORARY TABLE DBCMNGR.tmQLIntervalTbl, NO LOG, FALLBACK AS <DBC.DBQLogTbl> WITH NO DATA ON COMMIT PRESERVE ROWS; DROP TABLE DBCMNGR.tmQLSummIntervalTbl; CREATE MULTISET GLOBAL TEMPORARY TABLE DBCMNGR.tmQLSummIntervalTbl, NO LOG, FALLBACK AS <DBC.DBQLSummaryTbl> WITH NO DATA ON COMMIT PRESERVE ROWS; DROP TABLE DBCMNGR.tmQLStepIntervalTbl; CREATE MULTISET GLOBAL TEMPORARY TABLE DBCMNGR.tmQLStepIntervalTbl, NO LOG, FALLBACK AS <DBC.DBQLStepTbl> WITH NO DATA ON COMMIT PRESERVE ROWS; DROP TABLE DBCMNGR.tmWDIntervalTbl; CREATE MULTISET GLOBAL TEMPORARY TABLE DBCMNGR.tmWDIntervalTbl, NO LOG, FALLBACK 68 Teradata Manager User Guide

69 Chapter 4: Configuring Teradata Manager Specifying an External DBQL for Data Collection and Trend Reporting AS <DBC.DBQLogTbl> WITH NO DATA ON COMMIT PRESERVE ROWS; DROP TABLE DBCMNGR.tmWDSummaryIntervalTbl; CREATE MULTISET GLOBAL TEMPORARY TABLE DBCMNGR.tmWDSummaryIntervalTbl, NO LOG, FALLBACK AS <DBC.TDWMSummaryLog> WITH NO DATA ON COMMIT PRESERVE ROWS; 2 If the Teradata Database is V2R6.x and the external tables contain PPI columns, then use the following statements instead. Note: PPI columns are not supported in temporary tables on V2R6.x. CREATE MULTISET TABLE DBCMNGR.tmQLIntervalTbl, FALLBACK AS <DBC.DBQLogTbl> WITH NO DATA; CREATE MULTISET TABLE DBCMNGR.tmQLSummIntervalTbl, FALLBACK AS <DBC.DBQLSummaryTbl> WITH NO DATA; CREATE MULTISET TABLE DBCMNGR.tmQLStepIntervalTbl, FALLBACK AS <DBC.DBQLStepTbl> WITH NO DATA; CREATE MULTISET TABLE DBCMNGR.tmWDIntervalTbl, FALLBACK AS <DBC.DBQLogTbl> WITH NO DATA; CREATE MULTISET TABLE DBCMNGR.tmWDSummaryIntervalTbl, FALLBACK AS <DBC.TDWMSummaryLog> WITH NO DATA; Step 4: Grant to dbcmngr with Grant Option Use the following procedure to grant to dbcmngr with grant option. To grant to dbcmngr In the following GRANT statements, substitute the names of the external tables in place of the DBC dictionary table, shown in angle brackets. If there is no external table for one or more of the dictionary tables, skip the corresponding GRANT statement. GRANT SELECT, DELETE ON <dbc.dbqlogtbl> TO dbcmngr WITH GRANT OPTION; GRANT SELECT, DELETE ON <dbc.dbqlsummarytbl> TO dbcmngr WITH GRANT OPTION; GRANT SELECT, DELETE ON <dbc.dbqlsteptbl> TO dbcmngr WITH GRANT OPTION; GRANT SELECT, DELETE ON <dbc.dbqlobjtbl> TO dbcmngr WITH GRANT OPTION; GRANT SELECT, DELETE ON <dbc.dbqlexplaintbl> TO dbcmngr WITH GRANT OPTION; GRANT SELECT, DELETE ON <dbc.dbqlsqltbl> TO dbcmngr WITH GRANT OPTION; GRANT SELECT, DELETE ON <dbc.tdwmsummarylog> TO dbcmngr WITH GRANT OPTION; Teradata Manager User Guide 69

70 Chapter 4: Configuring Teradata Manager Configuring AMP Usage Data Collection Parameters GRANT SELECT, DELETE ON <dbc.tdwmexceptionlog> TO dbcmngr WITH GRANT OPTION; Step 5: Submit Statements to the Database Use the following procedure to submit the statements to the Teradata Database. To submit the statements to the database After customizing the statements, logon to the Teradata Database as user DBC (or other system administrator ID that is used to run the Teradata Manager Database Setup) and submit the statements. Step 6: Schedule the Data Collection Tasks To schedule the data collection tasks, go to Step 8 - Enabling Data Collection on page 61. Schedule the Query Log or Dynamic Workload Management data collection tasks so they run after the external tables are populated. For example, if a daily copy of DBQL data is implemented from the DBC database to an external database at midnight, then the Teradata Manager Query Log data collection task can be scheduled to run at 2:00 a.m. Note: The data collection task enforces a one hour delay interval between the current time and the time of the most recent data it will collect. For example, if the current time is 1:00 a.m., then the collection task will only collect and summarize DBQL data having FirstRespTime of midnight or earlier. DBQL data having FirstRespTime after midnight will be collected and summarized at the next scheduled collection time. Therefore, it is recommended that the data collection tasks be scheduled one hour or more after the daily DBQL maintenance script is run. Configuring AMP Usage Data Collection Parameters To configure AMP usage data collection parameters 1 From the Teradata Manager menu bar, click Administer>Teradata Manager. 2 Click the Data Collection tab. 3 Highlight the AMP Usage task by clicking on it. 4 Click Configure. 5 Fill in the fields as follows: Retention Period for Summary Data - the amount of time (in Days, Months or Years) summary information is kept in the data collection summary table 70 Teradata Manager User Guide

71 Chapter 4: Configuring Teradata Manager Configuring DBQL Data Collection Parameters Starting Position (of the Application Group ID Definition) - an optional field that allows specifying which character position in the Account String field of the AMPUSAGE view to start the Application ID. Length (of the Application Group ID Definition) - an optional field that allows specifying the character length of the Application ID [Optional] Logon Information - see Assigning Data Collection Logon Credentials on page Click OK to save your configuration settings. Configuring DBQL Data Collection Parameters To configure DBQL data collection parameters 1 From the Teradata Manager menu bar, click Administer>Teradata Manager. 2 Click the Data Collection tab. 3 Click the Query Log task to highlight it. 4 Click Configure. 5 Fill in the fields as follows: Retention Period for Detail Data - the amount of time data is kept in the dbc.dbql tables. The Cleanup task deletes data from each of the dbc.dbql tables that is older than the specified retention period. This includes the following data dictionary tables: dbc.dbqlogtbl dbc.dbqlsummarytbl dbc.dbqlsteptbl dbc.dbqlobjtbl dbc.dbqlexplaintbl dbc.dbqlsqltbl Retention Period for Summary Data - the amount of time information is kept in the dbcmngr summary tables - LogDBQL, LogDBQLStep Summarization Interval - the length of time represented by each row of summary data. For example, if the Summarization Interval is set to one hour, then each row summarizes one hour of DBQL data. [Optional] Logon Information - see Assigning Data Collection Logon Credentials on page Click OK to save your configuration settings. Teradata Manager User Guide 71

72 Chapter 4: Configuring Teradata Manager Configuring Teradata Dynamic Workload Management Data Collection Parameters Configuring Teradata Dynamic Workload Management Data Collection Parameters To configure Teradata Dynamic Workload Management data collection parameters 1 From the Teradata Manager menu bar, click Administer>Teradata Manager. 2 Click the Data Collection tab. 3 Highlight the Dynamic Workload Management task by clicking on it. 4 Click Configure. 5 Fill in the fields as follows: Retention Period for Detail Data - the amount of time data is kept in the dbc.tdwm tables. The Cleanup task deletes data from each of the dbc.tdwm tables that is older than the specified retention period. This includes the following data dictionary tables: dbc.tdwmsummarylog dbc.tdwmeventlog dbc.tdwmexceptionlog Retention Period for Summary Data - the amount of time information is kept in the dbcmngr summary table LogWDSummary Summarization Interval - the length of time represented by each row of summary data. For example, if the Summarization Interval is set to one hour, then each row summarizes one hour of Teradata DWM data. [Optional] Logon Information - see Assigning Data Collection Logon Credentials on page Click OK to save your configuration settings. Configuring Heartbeat Query Data Collection Parameters To configure heartbeat query data collection parameters 1 From the Teradata Manager menu bar, click Administer>Teradata Manager. 2 Click the Data Collection tab. 3 Highlight a Heartbeat Query task by clicking on it. 4 Click Configure. 72 Teradata Manager User Guide

73 Chapter 4: Configuring Teradata Manager Configuring Priority Scheduler Data Collection Parameters 5 Fill in the fields as follows: Query Application Id- an identifier for the query. This is a required field. Retention Period for Summary Data - the amount of time (in Days, Months or Years) summary data is kept Response Time Alarm Threshold - the maximum time (in Seconds or Minutes) that the query is expected to run Response Time Alarm Action - select the alarm action to be triggered when the response time threshold is exceeded Query SQL Text - the heartbeat query that is submitted to the database. This is a required field. Note: This field is limited to 30,000 characters due to limitations in the Teradata Database. [Optional] Logon Information - see Assigning Data Collection Logon Credentials on page Click OK to save your configuration settings. Configuring Priority Scheduler Data Collection Parameters To configure Priority Scheduler data collection parameters 1 From the Teradata Manager menu bar, click Administer>Teradata Manager. 2 Click the Data Collection tab. 3 Highlight a Priority Scheduler task by clicking on it. 4 Click Configure. 5 Fill in the fields as follows: Retention Period for Summary Data - the amount of time (in days, months or years) summary data is kept in the tables [Optional] Logon Information - see Assigning Data Collection Logon Credentials on page Click OK to save your configuration settings. Teradata Manager User Guide 73

74 Chapter 4: Configuring Teradata Manager Configuring Query Band Pairs Data Collection Parameters Configuring Query Band Pairs Data Collection Parameters Query band pairs data is used by the Teradata DWM Administrator utility. It allows the Teradata DWM user to classify workloads on query band names and values. To define workload classifications, see the Teradata Dynamic Workload Manager User Guide. Note: Query banding is only supported with Teradata Database To configure query band pairs data collection parameters 1 From the Teradata Manager menu bar, click Administer>Teradata Manager. 2 Click the Data Collection tab. 3 Highlight the Query Band Pairs task by clicking on it. 4 Click Configure. 5 Fill in the fields as follows: Retention Period for Summary Data - the amount of time (in days, months or years) summary data is kept in the QryBandPairs table. [Optional] Logon Information - see Assigning Data Collection Logon Credentials on page Click OK to save your configuration settings. Configuring Resource Usage Data Collection Parameters To configure resource usage data collection parameters 1 From the Teradata Manager menu bar, click Administer>Teradata Manager. 2 Click the Data Collection tab. 3 Highlight the Resource Usage task by clicking on it. 4 Click Configure. 5 Fill in the fields as follows: Retention Period for Detail Data - the amount of time data is kept in the dbc.resusage tables. The Cleanup task deletes data from each of the dbc.resusage tables that is older than the specified retention period. This includes the following data dictionary tables: dbc.resusagespma dbc.resusagesvpr dbc.resusageshst 74 Teradata Manager User Guide

75 Chapter 4: Configuring Teradata Manager Configuring Spool Space Data Collection Parameters dbc.resusageipma dbc.resusageivpr dbc.resusagescpu dbc.resusagesldv dbc.resusagesobj (on Teradata Database V2R6.x) dbc.resusagesawt (on Teradata Database or later) dbc.resusagesps (on Teradata Database or later) dbc.resusagespdsk (on Teradata Database or later) dbc.resusagesvdsk (on Teradata Database or later) Retention Period for Summary Data - the amount of time summary information is kept in the dbcmngr summary tables - LogSystemActivity, LogResUsageNode, LogResUsageVproc, and LogResUsageHost Summarization Interval - the length of time represented by each row of summary data. For example, if the Summarization Interval is set to one hour, then each row summarizes one hour of resusage data. This parameter does not apply to the LogSystemActivity table (which is simply a snapshot of session counts at the time the Resource Usage task is launched in the service). Collection Options: Node - select this check box to summarize node-related data from dbc.resusagespma and dbc.resusageipma. Summary data is collected in dbcmngr.logresusagenode. Vproc - select this check box to summarize vproc-related data from dbc.resusagesvpr. Summary data is collected in dbcmngr.logresusagevproc. Host - select this check box to summarize host-related data from dbc.resusageshst. Summary data is collected in dbcmngr.logresusagehost. Note: The Resource Usage task also collects session activity counts (using PM/API requests), which are written to dbcmngr.logsystemactivity. Session counts are collected even if none of the resusage options are selected [Optional] Logon Information - see Assigning Data Collection Logon Credentials on page Click OK to save your configuration settings. Configuring Spool Space Data Collection Parameters To configure spool space data collection parameters 1 From the Teradata Manager menu bar, click Administer>Teradata Manager. 2 Click the Data Collection tab. Teradata Manager User Guide 75

76 Chapter 4: Configuring Teradata Manager Configuring Table Space Data Collection Parameters 3 Highlight the Spool Space task by clicking on it. 4 Click Configure. 5 Fill in the fields as follows: Retention Period for Summary Data - the amount of time (in days, months or years) summary data is kept Current Spool Alarm Threshold - the maximum percentage of spool space usage allowable before the alarm action is triggered Current Spool Alarm Action - select the alarm action to be triggered when the current spool threshold is exceeded Peak Spool Alarm Threshold - the maximum percentage of peak spool space usage allowable before the alarm action is triggered Peak Spool Alarm Action - select the alarm action to be triggered when the peak spool threshold is exceeded To move the users to the Monitored Users list, highlight the users in the Available Users list, and click Add-> To monitor all users, select All Users To remove users from monitored status, highlight them in the Monitored Users list and click <-Remove [Optional] Logon Information - see Assigning Data Collection Logon Credentials on page Click OK to save your configuration settings. Configuring Table Space Data Collection Parameters To configure table space data collection parameters 1 From the Teradata Manager menu bar, click Administer>Teradata Manager. 2 Click the Data Collection tab. 3 Highlight the Table Space task by clicking on it. 4 Click Configure. 5 Fill in the fields as follows: Collect Cylinder Counts - select to enable population of the cylinder count, data block, row size and row count columns in the summary table. Clear this check box to reduce the overall cost of data collection. Caution: The Collect Cylinder Counts option uses the Ferret utility; therefore, selecting this option will have a significant adverse impact on Teradata Database performance. If this option is enabled, carefully evaluate the collection duration and scheduled collection time. Schedule the 76 Teradata Manager User Guide

77 Chapter 4: Configuring Teradata Manager Configuring Your Color Display Options collection task infrequently, during off-peak hours, and limit the number of tables by clearing the All Objects option and adding specific tables to the Monitored Tables list. Under Available Tables: Select the Ignore Users check box to display only database names. Otherwise database and user names are displayed. Select the All Objects check box to specify collection for all tables in all databases Select a database from the Databases list. After the database is selected, the tables in the database are displayed in the Available Tables list. Move any of the tables listed in the Available Tables list to the Monitored Tables list by selecting the table, then clicking Add-> After the tables are selected from one database, select another database and repeat the procedure Select the All Tables check box to specify collection for all tables in the currently selected database Remove any of the tables listed in the Monitored Tables list to the by selecting the table, then clicking <-Remove [Optional] Logon Information - see Assigning Data Collection Logon Credentials on page Click OK to save your configuration settings. Configuring Your Color Display Options To configure color display options 1 From the Teradata Manager menu bar, click Administer>Teradata Manager. 2 Click the Color Options tab. 3 To change the color of a Dashboard Gauge or Dashboard Status, select the object by clicking on the associated button, then click the color. The color indicator next to the object changes to match your selection. 4 To restore the colors to the same status before changes were made in this dialog box, click Restore. 5 To reset the colors to the default, click Default. 6 To configure the graph colors, click Graph Colors, and follow the instructions in Step 3. 7 Click OK to save your configuration settings. 8 To close the dialog box without saving your changes, click Close. Teradata Manager User Guide 77

78 Chapter 4: Configuring Teradata Manager Checking the Status of the Teradata Manager Server Checking the Status of the Teradata Manager Server Use this procedure to ensure the Teradata Manager Service is running. Note: The Teradata Manager Service is installed when the Server setup type is selected during the installation process. The Teradata Manager Service can also be installed from the Custom Setup screen during the installation process and selecting the Teradata Manager Service. To check the Teradata Manager Server status 1 Click Start>Settings>Control Panel>Administrative Tools>Services. 2 Find the Teradata Manager Service. 3 Ensure the Status column for the service displays, Started. 4 In the Name column, double-click Teradata Manager Service to open the Teradata Manager Service Properties dialog box. 5 If the Service status is not Started, change it as follows: Ensure the Startup type is Automatic and click Apply. Click Start to start the service. 6 Click OK to close the dialog box. Teradata Manager Service Registration Only one version of Teradata Manager Service can be registered at one time. When Teradata Manager 12.0 Service is installed, it becomes the registered version. To go back to a previous version of the Teradata Manager Service, that version must be manually registered. To do that, open a command window, make the Teradata Manager 6.x BIN directory the current directory, and execute the following command: isservice.exe /service. Changing Logon Settings Use this procedure to change logon settings for database name, database user name, password, account ID, profile, security mechanism, and connection mode. To change logon settings 1 From the Teradata Manager menu bar, click Options>Change Logon Settings. The Logon Information dialog box appears. 78 Teradata Manager User Guide

79 Chapter 4: Configuring Teradata Manager Restoring the Default Preferences for Tables and Graphs 2 Fill in the fields as follows: System (DBS) Name - the TDPid of the Teradata Database Username - the name used to log on to Teradata Manager Password - the string used to access Teradata Manager for the above Username Account Id - the Database related account string 3 Select a profile from the Profile list. When logging in for the first time, or if no other profiles have been created, click DEFAULT from the list. 4 For Teradata Manager to remember your login settings, select the Save as defaults check box. 5 If a security mechanism is in place or to select a different character set for logging on to the client, click Advanced. See Setting the Security Mechanism and Character Set on page Connecting through the server provides the most efficient way to run Teradata Manager. To connect through a server, select Get data from Server, then enter the Server Name. To use your local PC as the server, enter localhost for the Server Name. If a connection through the server cannot be made because the Teradata Manager Service has not been configured to monitor the selected system or the Service is not running, connect in direct mode by selecting Get data direct from Teradata Database. If the database is not accessible, a direct connection cannot be made. Note: For instructions on configuring the Teradata Manager Service to monitor a system, see Step 6 - Defining System Parameters on page To display this dialog box on subsequent logins, select the Automatically show this dialog next time check box. 8 Click OK. Restoring the Default Preferences for Tables and Graphs Use this procedure to reset the font, column width, and order for the table or the graph type and style for the graph in focus. This erases any preferences changes made. To restore default preferences From the Teradata Manager menu bar, click Options>Restore Default Preferences. Teradata Manager User Guide 79

80 Chapter 4: Configuring Teradata Manager Adding Application Specific Entries to the Registry Adding Application Specific Entries to the Registry The Application Specific Setup tab (located by clicking Administer>Teradata Manager) provides a menu-driven interface to control the menu items for specific applications. Note: This feature modifies the registry. It should only be used by expert users who are familiar with registry entries and how the applications work. By default, the Key List contains the following standard keys for Teradata Manager: Key Name ELA_Macros LG_LogonReportMacro RCONSLOGON RCONSUTILS Application Error Log Analyzer Logon/Logoff History Remote Console Logon Remote Console Utilities Application-Specific Entry Example As an example, the LG_LogonReportMacro key controls the menu items for the Logon/Logoff History application. It contains three value entries, each corresponding to an available History report: DailyReport:daily.lg WeeklyReport:weekly.lg MonthlyReport:monthly.lg Each value entry contains the name of the menu item, followed by a colon, and then the name of the report. The result is that when running the Logon/Logoff History application, the menu displays three items: DailyReport, WeeklyReport, and MonthlyReport. To work with application specific entries 1 From the Teradata Manager menu bar, click Administer>Teradata Manager. 2 Click the Application Specific Setup tab. 3 Configure the entries by doing the following: To add a new key, enter the name of the key in the Key field, then click Add. To add new value entries to an existing key, select the key, then edit the entries in the Value Entry box. After the entries are edited, click Change. To modify the existing key, select the key, make your changes, then click Change. To delete a key, select the key, then click Delete. 80 Teradata Manager User Guide

81 Chapter 4: Configuring Teradata Manager Adding Additional Applications to the Teradata Manager Menu Bar To restore the four default Teradata Manager keys, click Restore Defaults. This operation does not affect user-defined keys. To permanently save your changes to the registry, click Save to Registry. To abort your temporary changes and restore data from the registry, click Restore from Registry. Adding Additional Applications to the Teradata Manager Menu Bar Add your own applications or applications from third-party vendors to a Teradata Manager menu. Once added, the applications appears on their own menu on the Teradata Manager menu bar. Some applications, such as BTEQ scripts, benefit from not needing to include login information in the script, requiring less DBA maintenance. Note: This affects only your local copy of Teradata Manager. To add local applications to the Teradata Manager menu bar 1 Create a file in the Teradata Manager bin directory called localmenu.txt 2 Enter the code in the localmenu.txt file to build the menu as indicated in the following rules: Comments are optional, can be any text, and can be used anywhere in the file. The comment must be prefixed by a # in the first column. Commands have the form Label,AppPath where: Label - is the text that appears on the menu AppPath - is either a full pathname, or just the executable name, including any parameters, if required. If it is just the executable name, then the executable must be in the Teradata Manager bin directory or it must be registered under the AppPaths key in the registry. Note: Do not add a space after the comma. Also, do not add double quotes around the pathname. See Example on page 82. Popup menu commands that create submenus are optional, and have the form Label,POPUP where: Label - is the text that appears on the menu POPUP - this command creates the submenu, and must be followed by a submenu command. Teradata Manager User Guide 81

82 Chapter 4: Configuring Teradata Manager Setting the Port Number for TCP/IP Submenu commands must be preceded by a popup menu command, and have the form <tab>label,apppath where: <tab> - a tab must precede the label to put the menu item on a submenu. Label - is the text that appears on the menu AppPath - is either a full pathname, or just the executable name, including any parameters, if required. If it is just the executable name, then the executable must be in the Teradata Manager bin directory or it must be registered under the AppPaths key in the registry. Note: Only one level of submenus is supported. Use the following template as a guide: # Comment Label,AppPath Label,POPUP <tab>label,apppath <tab>label,apppath Label,AppPath Example First menu item Second menu item Third menu item The following example creates a menu on the Teradata Manager menu bar named Local with three menu items: # this is an example localmenu.text file Notepad,C:\Windows\System32\notepad.exe Reports,POPUP <tab>batch Summary,yourprogram.exe < C:\reports\batch.sql <tab>weekly Usage,yourprogram.exe < C:\reports\weekly.sql Calculator,C:\Windows\System32\calc.exe 2428A005 The first menu item appears as Notepad, and launches the Windows Notepad program. The second menu item appears as Reports. When selected, a second level menu appears containing items called Batch Summary and Weekly Usage. These two selections launch custom programs. The third menu item appears as Calculator, and launches the Windows Calculator program. Setting the Port Number for TCP/IP Teradata Manager uses port 1515 for TCP/IP communications between the Teradata Manager client and Service. If the Teradata Manager client is running outside of a firewall, configure your firewall to allow connections to this port. The Teradata Manager Service connects back to the client using a port that the operating system dynamically assigns. If your firewall is configured to block connections from the Service to the client, then open up a range of ports in this direction. Since the port number is 82 Teradata Manager User Guide

83 Chapter 4: Configuring Teradata Manager Setting the Security Mechanism and Character Set dynamically assigned, determining the correct range is difficult. Observation shows the port number usually falls in the range of Setting the Security Mechanism and Character Set Set the security mechanism and character set using the following procedures. To set for a client log on 1 Click Start>Programs>Teradata Manager 12.0>Teradata Manager. 2 Click Advanced. 3 Select the Authentication Mechanism from the list. The Authentication Mechanism identifies the mechanism used for connections to the data source. Each site implements their own security measures. If a list of mechanisms does not appear and users cannot log on to the Teradata Database, consult your DBA or the person responsible for the security of your Teradata Database. 4 If a mechanism is selected, enter the applicable Authentication String. If the specified mechanism does not require this string, leave this field empty. 5 Select the Character Set from the list. If left blank, the default character set for the database is used. This is the charset_id value as defined in the clispb.dat file. If the character set is not specified in the clispb.dat file, the default character set returned by CLIv2 is used. 6 Click OK to save the setting. 7 [Optional] Click the Save as defaults check box to use the same character set when logging in the next time. Note: Selecting this check box also saves the other Logon information that is specified. 8 [Optional] Click Help>About Teradata Manager to verify the client character set in use is the one that was set. To set for the Teradata Manager Service 1 From the Teradata Manager main window, click Administer>Teradata Manager, and click the System tab. 2 Click Advanced. 3 Select the Authentication Mechanism from the list. The Authentication Mechanism identifies the mechanism used for connections to the data source. Each site implements their own security measures. If a list of mechanisms does not appear and users cannot log on to the Teradata Database, consult your DBA or the person responsible for the security of your Teradata Database. Teradata Manager User Guide 83

84 Chapter 4: Configuring Teradata Manager Setting the Security Mechanism and Character Set 4 If a mechanism is selected, enter the applicable Authentication String. If the specified mechanism does not require this string, leave this field empty. 5 Select the Character Set from the list. If left blank, the default character set for the database is used. This is the charset_id value as defined in the clispb.dat file. If the character set is not specified in the clispb.dat file, the default character set returned by CLIv2 is used. 6 Click OK to close the Advanced dialog box. 7 From the System tab, click Modify to save the setting. 84 Teradata Manager User Guide

85 CHAPTER 5 Configuring the SNMP Agent Teradata Manager includes an SNMP agent that allows third party management applications such as HP OpenView to monitor Teradata Database performance and to be notified of exceptions using SNMP traps. The SNMP agent is installed as a component of the Teradata Manager Service. Use Alert Policy Editor to configure the conditions to generate a trap. The documentation of SNMP support includes the following: Teradata Manager Alerts SNMP MIB SNMP Troubleshooting Tips Teradata Manager Alerts SNMP MIB MIB Object Structure The Teradata Manager SNMP MIB is available in: <install_path>\data\tdatmgr.mib where <install_path> is the location that is chosen to install Teradata Manager. SNMP Object Identifiers (OIDs) for Teradata Manager are defined under NCR's enterprise-specific node: iso.org.dod.internet.private.enterprises.ncr.ncr-products.teradata-mgr Teradata Manager MIB objects are grouped into three main areas, representing Teradata system information (tdatmgrsysteminfo), event (SNMP trap) information (tdatmgreventinfo), and monitoring information (tdatmgrmonitorinfo). tdatmgrsysteminfo This group contains the following tables: Table Name tdsystemcount Description Defines a count of the Teradata Database systems known to the SNMP agent Teradata Manager User Guide 85

86 Chapter 5: Configuring the SNMP Agent Teradata Manager Alerts SNMP MIB Table Name tdsystemtable tdnodetable tdvproctable tdsessiontable Description Contains system-level data. Each row of this table contains the Teradata Database system name, the number of nodes and vprocs in the system, and related summary statistics (for example, Average CPU utilization). The table is indexed on Teradata system name (tdsystemname). The Teradata Manager Data Collector gathers statistics. Then at runtime the SNMP agent maintains the system count and table. Management applications may query the agent for this information using SNMP Get and GetNext requests. Describes the nodes (physical platform) in each Teradata Database Describes the vprocs (virtual platform) on each Teradata Database system Describes the user sessions on each Teradata Database system tdatmgreventinfo This group defines a table of SNMP events (traps) that the Teradata Manager Alerts system (tdeventtable) generates. This table is indexed on Teradata system name (tdsystemname) and event sequence number (tdeventseq). The agent generates event sequence numbers to uniquely identify each trap. The Teradata Manager Service supplies the rest of the data in each row, including tdeventdate and tdeventtime, which are the date and time taken from the Teradata Database for which the trap has been sent. The tdatmgreventinfo group also defines tdeventmaxpersystem. This is a limit on the number of rows per Teradata System that are put into the table. The default limit is 10. The agent enforces this limit at runtime by discarding trap information that is older than the 10 most recent trap entries for each Teradata Database system. Management applications may query the trap limit and table using SNMP Get and GetNext requests. The tdeventmaxpersystem object is defined with READ-WRITE access to allow management applications to change the number of trap entries that are retained, using an SNMP Set request. tdatmgrmonitorinfo This group defines the table tdratetable. This table describes the current monitoring rates the Teradata Manager Service uses. tdratephysicalresource indicates how often the data in tdnodetable is updated. Likewise, tdratevirtualresource and tdratesession indicate how often data in tdvproctable and tdsessiontable, respectively, are updated. Three other values, tdratedbspace, tdratedbeventlog, and tdratealertrequest, indicate the corresponding refresh rates in the Teradata Manager alert policy. Finally, the Teradata Manager MIB defines a single trap, tdalertevent, identified as trap 1340 under enterprise OID tdatmgralertevents. The trap includes MIB variables tdsystemname and all columns of the tdeventtable table. 86 Teradata Manager User Guide

87 Chapter 5: Configuring the SNMP Agent SNMP Troubleshooting Tips SNMP Troubleshooting Tips Install Teradata Manager as an Administrator Configuration If installing Teradata Manager Alerts on a Windows system, membership in the Windows Administrators group is required or the SNMP Agent does not install properly. If running the SNMP Agent on a Windows system, ensure the Windows SNMP Service and SNMP Trap Service have been started by using the Services Control Panel applet. Verify that SNMP community names and trap destinations have been configured. On Windows, do this using the Network Control Panel applet. See Microsoft documentation for further information. Set the System PATH Environment Variable on Windows 2000 On some Windows 2000 systems, it may be necessary to add the Teradata Manager 12.0 bin directory to the System Path environment variable for the SNMP agent to work. To set the Windows 2000 System PATH environment variable 1 From the Windows 2000 Control Panel, double-click System, then click the Advanced tab. 2 Click Environment Variables. 3 Under System variables, select Path, and click Edit. 4 Append the Teradata Manager bin directory (for example, C:\Program Files\NCR\Teradata Manager 12.0\bin) to the existing Path. 5 Reboot the system to allow the SNMP service to pick up the new Path. Teradata Manager User Guide 87

88 Chapter 5: Configuring the SNMP Agent SNMP Troubleshooting Tips 88 Teradata Manager User Guide

89 CHAPTER 6 Monitoring Real-Time System Activity Teradata Manager has many options for viewing real-time system activity on your system. To see an overall view of many aspects at once, use the Dashboard feature. This gives a summary of the current state of the system on a single page. For more detailed views of system utilization and session information, drill down from the Dashboard, or specifically select the detail reports from the Teradata Manager menu bar. The following topics give instructions on viewing, modifying, or abort activity on the system: Monitoring Overall System Activity Using the Dashboard Getting History Data Details Monitoring Virtual Utilization Getting Virtual Utilization Details Monitoring Physical Utilization Getting Physical Utilization Details Monitoring Session Status Getting Session Details Modifying Session Priority Aborting Sessions Viewing What the Selected Session is Blocking Viewing What the Selected Session is Blocked By Viewing Query Band Pairs Monitoring Delay Queue Statistics Monitoring the Workload Delay Queue List Monitoring Object Logon Statistics Monitoring Object Query Statistics Monitoring the Object Delay Queue List Monitoring Object Utility Statistics Monitoring Event Status Using Performance Monitor (PMON) Using Session Information The Graph Legend Teradata Manager User Guide 89

90 Chapter 6: Monitoring Real-Time System Activity Monitoring Overall System Activity Using the Dashboard Monitoring Overall System Activity Using the Dashboard Viewing the Dashboard The Dashboard provides a summary of the current state of the system on a single page. The page contains real-time data and trend charts showing resource consumption over the last 60 minutes. Drill down for more detailed information. Lights on the status bar at the top of the Dashboard indicate AMP, PE, Node and Bynet status: a green light indicates a status of ok, a red light indicates a status of down. The top level Dashboard screen shows current and recent historical information. It permits seeing the state of the system at a glance and to predict future problems by viewing recent trends. To view the Dashboard 1 From the Teradata Manager menu bar, click Monitor>Dashboard. The Dashboard appears with the System tab selected by default. 2 Click the links to drill down for more information. The following topics describe this feature: Getting History Data Details on page 92 Monitoring Virtual Utilization on page 94 Getting Virtual Utilization Details on page 95 Monitoring Physical Utilization on page 97 Getting Physical Utilization Details on page 99 Monitoring Session Status on page 101 Getting Session Details on page Teradata Manager User Guide

91 Chapter 6: Monitoring Real-Time System Activity Monitoring Overall System Activity Using the Dashboard Dashboard Display The Dashboard displays the current data as a snapshot from the last refresh or historical data for the last 60 minutes. To display the current data From the Dashboard, click the link under the following gauges: Gauge Data Label Description Virtual Utilization AMP Utilization % The average percent of CPU usage for all on-line AMPs in the configuration Physical Utilization PE Utilization % AMP Parallelism Node Utilization % Bynet Utilization % Disk Utilization % Node Parallelism The average percent of CPU usage for all on-line PEs in the configuration An indication of the parallelism that is being achieved across all nodes and vprocs. This value is a percentage calculated as: Average usage x 100 / Maximum usage The average percent of CPU usage for all on-line nodes in the configuration The percent of total ByNet utilization (i.e., average of the online Bynets). The average percent of disk usage for all on-line AMPs and nodes in the configuration An indication of the parallelism that is being achieved across all nodes. This value is a percentage calculated as: Average usage x 100 / Maximum usage Session Total Sessions The total number of sessions logged on to the Teradata Database Transaction Rate Response Time I/O Per Transaction Blocked Sessions Active Sessions Average Transaction Rate (TPM) Average Response Time Average I/O per Transaction The number of blocked sessions on the system The total number of active sessions logged on to the Teradata Database The average number of requests processed per minute The average response time required for each request (in seconds) The average number of logical reads and writes issued per request Teradata Manager User Guide 91

92 Chapter 6: Monitoring Real-Time System Activity Getting History Data Details To display the historical data From the Dashboard, click the link under the following graphs: Graph Data Label Description Virtual Utilization Summary Physical Utilization Summary Average Vprocs CPU% Low Vprocs CPU% High Vprocs CPU% Average Node CPU % Minimum Node CPU % Maximum Node CPU % The average percent CPU usage of all online vprocs currently in the Database configuration The vproc with the lowest CPU usage The vproc with the highest CPU usage The average percent of CPU usage for all on-line nodes in the configuration The node with the lowest disk usage The node with the highest disk usage Session Summary Total Sessions The total number of sessions logged on to the Teradata Database Active Sessions Blocked Sessions The total number of active sessions logged on to the Teradata Database The total number of blocked sessions logged on to the Teradata Database Getting History Data Details Get history data details from a summary graph that shows: Trend data over time Additional data not visible on the top level Dashboard window From this window, investigate problems by correlating your choice of many types of data. To view the Summary Graph 1 From the Dashboard, click any of the following links to view a summary graph: Virtual Utilization Summary Physical Utilization Summary Session Summary For a description of the columns, see Table 13 2 To change the display, click the View as table link. 92 Teradata Manager User Guide

93 Chapter 6: Monitoring Real-Time System Activity Getting History Data Details 3 To change the information displayed on the graph, select the appropriate data points, then click Refresh Graph. Summary Graph Data Points Table 13: Summary Graph Data Points Select this data point... Vproc Ave Vproc Min Vproc Max PE CPU Disk Node Ave Node Min Node Max Bynet Total Sessions Active Sessions Blocked Sessions TPM Response Time I/O per Tx Short TPM To chart... The average percent of CPU usage by vprocs over time The percent of CPU usage for the least busy vproc over time The percent of CPU usage for the most busy vproc over time The average percent of CPU usage of the PEs over time The average percent of disk usage of the nodes over time The average percent of CPU usage for all on-line nodes over time The percent of CPU usage for the least busy node over time The percent of CPU usage for the most busy node over time The average percent of Bynets usage over time The total number of sessions logged on to the Teradata Database over time The total number of active sessions logged on to the Teradata Database over time The total number of blocked sessions logged on to the Teradata Database over time The average number of requests per minute The average response time for a single request The average number of logical reads and writes per request The number of requests that completed in the last 60 seconds with a response time less than 20 seconds Short Resp Time The average response time of requests that completed in the last 60 seconds with a response time less than 20 seconds Short I/O per Tx The average number of I/Os for requests that completed in the last 60 seconds with a response time less than 20 seconds Medium TPM The number of requests that completed in the last 60 seconds with a response time from 20 to 60 seconds Medium Resp Time The average response time of requests that completed in the last 60 seconds with a response time from 20 to 60 seconds Medium I/O per Tx The average number of I/Os for requests that completed in the last 60 seconds with a response time from 20 to 60 seconds Teradata Manager User Guide 93

94 Chapter 6: Monitoring Real-Time System Activity Monitoring Virtual Utilization Table 13: Summary Graph Data Points (continued) Select this data point... Medium CPT Long TPM To chart... The average CPU usage per request for requests with a response time from 20 to 60 seconds The number of requests that completed in the last 60 seconds with a response time greater than 60 seconds Long Resp Time The average response time of requests that completed in the last 60 seconds with a response time greater than 60 seconds Long I/O per Tx The average number of I/Os for requests that completed in the last 60 seconds with a response time greater than 60 seconds Monitoring Virtual Utilization The Virtual Utilization Report provides information on vproc use. From this report, drill down on individual vprocs to get more detailed information. To view Virtual Utilization Vproc Utilization Report 1 Do one of the following: From the Teradata Manager menu bar, click Monitor>Vprocs From the Teradata Manager menu bar, click Monitor>Dashboard, and click the Virtual Utilization link below the corresponding display dial. For a description of the columns, see Table To sort the data, click any of the column titles to sort on that field. 3 To get a Vproc Detail Report, right-click an AMP or PE name, then click Vproc Details. Table 14: Vproc Utilization Report Data Label Name Node ID Status CPU Use % Disk Use % Channel Use % Description The name of the vproc The node the vproc is running on The status of the vproc The average percent CPU usage of all online vprocs currently in the Database configuration The percentage of disk use for this vproc The percentage of channel use for this vproc 94 Teradata Manager User Guide

95 Chapter 6: Monitoring Real-Time System Activity Getting Virtual Utilization Details Table 14: Vproc Utilization Report (continued) Data Label Disk Q Len Disk Reads Disk Writes Host Reads Host Writes Sessions (for each AMP and PE) AMP Worker Task Msg Queue Length Description The number of outstanding disk requests cued up for disk I/O The total number of physical disk reads for this vproc during the sample interval The total number of physical disk writes for this vproc during the sample interval The number of message blocks received from all hosts. A message block may consist of multiple messages. The number of message blocks sent to all hosts. A message block may consist of multiple messages. The number of sessions currently logged on to this PE The number of AMP worker tasks The number of messages in the queue Getting Virtual Utilization Details From the Vproc Utilization Report, view much more detailed information for a particular vproc. To view Vproc Utilization Details 1 Open the Vproc Utilization Report as described in Monitoring Virtual Utilization on page Double-click a vproc item, or right-click an AMP or PE name, then click Vproc Details. For a description of the columns, see Table The following buttons are available: << Previous - display detail information for the previous vproc Next >> - display detail information for the next vproc Close - close the Vproc Detail dialog box Vproc Utilization Detail Report The system name, Node ID, VProc ID and data refresh rate are displayed in the title bar of this report. The following table describes the data displayed in the body of the Vproc Utilization Detail Report. Teradata Manager User Guide 95

96 Chapter 6: Monitoring Real-Time System Activity Getting Virtual Utilization Details Table 15: Vproc Utilization Detail Report Data Label VProc Type Status Host ID/Cluster Session Log Count Session Run Count CPU Use PDE User Service AMP Worker Task % PE Parser PE Dispatcher AMP Disk Use AMP Worker Tasks CIC Use Disk Reads Disk Writes Avg Disk Req Description The type of vproc The status of the vproc Host Id is the logical host identifier associated with a PE or session Cluster is the cluster number associated with an AMP The number of sessions currently logged on to this PE The number of sessions sending TSR messages to this vproc. (Fastload and Multiload send messages directly to AMPs.) The percent of CPU usage that is not spent being idle Note: If the processing is skewed towards one or more AMPs (that is, the parallelism is not 100%), this field may display a value greater than 100%. This is due to the way the data is normalized. The percent of CPU resources spent in UNIX-PDE user service processing Note: If the processing is skewed towards one or more AMPs (that is, the parallelism is not 100%), this field may display a value greater than 100%. This is due to the way the data is normalized. The percent of CPU resources spent processing an AMP worker task Note: If the processing is skewed towards one or more AMPs (that is, the parallelism is not 100%), this field may display a value greater than 100%. This is due to the way the data is normalized. The percent of CPU resources spent in PE Parser processing Note: If the processing is skewed towards one or more Amps (that is, the parallelism is not 100%), this field may display a value greater than 100%. This is due to the way the data is normalized. The percent CPU resources spent in PE Dispatcher processing Note: If the processing is skewed towards one or more Amps (that is, the parallelism is not 100%), this field may display a value greater than 100%. This is due to the way the data is normalized. The percentage of disk usage for this vproc The number of AMP worker tasks The percent of Channel Interface Controller usage for this vproc The total number of physical disk reads for this vproc during the sample interval The total number of physical disk writes for this vproc during the sample interval The average number of outstanding disk requests for this vproc 96 Teradata Manager User Guide

97 Chapter 6: Monitoring Real-Time System Activity Monitoring Physical Utilization Table 15: Vproc Utilization Detail Report (continued) Data Label Host Block Reads Host Block Writes Mem Segs Allocated Mem KB Allocated Net Reads Net Writes Backup Segs Alloc Message Queue Length Average AMP Use Parallel Efficiency Description The number of message blocks received from all hosts. A message block may consist of multiple messages. The number of message blocks sent to all hosts. A message block may consist of multiple messages. The number of segments allocated to memory resources The number of Kilobytes allocated to memory resources The number of messages read from the ByNet and input into the node during the sample interval The number of messages written from the node and output to the ByNet during the sample interval The number of complete and partial nonvolatile memory allocations of disk segments read (written) for backup storage during the sample interval The number of messages in the queue The average usage across all AMPs An indication of the parallelism your system is achieving across all nodes and vprocs. This value is a percentage calculated as: Average usage x 100 / Maximum usage Monitoring Physical Utilization The Node Utilization Report provides information on Node use. From this report, drill down on individual nodes to get more detailed information. To view Physical Utilization 1 Do one of the following: From the Teradata Manager menu bar, click Monitor>Nodes From the Teradata Manager menu bar, click Monitor>Dashboard, and click the Physical Utilization link below the corresponding display dial. For a description of the columns, see Table To sort the data, click any of the column titles to sort on that field. 3 To get a Node Detail Report, right-click the name of the node to display the shortcut menu. 4 Click Node Details. Teradata Manager User Guide 97

98 Chapter 6: Monitoring Real-Time System Activity Monitoring Physical Utilization Node Utilization Report Table 16: Node Utilization Report Data Label Name Status CPU Use % Disk Use % Bynet Use % Channel Use % Disk Q Len Disk Reads Disk Writes Host Reads Host Writes Swap Reads Swap Writes Memory Allocation Failures Kernel CPU % Wait I/O CPU % User CPU % Description The Id of the selected node The status of the selected node The percent of CPU usage that is spent being active (not idle) The percentage of disk usage for this node The percentage of Bynet usage for this node The percentage of channel usage for this node The number of outstanding disk requests cued up for disk I/O The total number of physical disk reads for this node during the sample interval The total number of physical disk writes for this node during the sample interval The number of message blocks received from all hosts. A message block may consist of multiple messages. The number of message blocks sent to all hosts. A message block may consist of multiple messages The number of segments read into node memory from the disk during the sample interval due to swapping The number of segments written to disk from node memory during the sample interval due to swapping The number of segment allocation attempts that failed The percent of time spent in UNIX PDE Kernel that is spent being active (not idle) The percent of time spent in UNIX PDE Kernel waiting for I/Os to complete The percent of time spent in user (non-kernel) tasks 98 Teradata Manager User Guide

99 Chapter 6: Monitoring Real-Time System Activity Getting Physical Utilization Details Getting Physical Utilization Details From the Node Utilization Report, view much more detailed information for a particular node. To view Physical Utilization Details 1 Open the Node Utilization Report as described in Monitoring Physical Utilization on page Right-click the name of the node to display the shortcut menu. 3 Click Node Details. For a description of the columns, see Table The following buttons are available: << Previous - display detail information for the previous Node Next >> - display detail information for the next Node Close - close the Node Detail dialog box Node Utilization Detail Report The system name, Node ID, and data refresh rate are displayed in the title bar of this report. The following table describes the data displayed in the body of the Node Utilization Detail Report. Table 17: Node Utilization Detail Report Data Label Status AMP Count PE Count CPU Use I/O Wait PDE User Service Processing User Code Bynet Use Node Disk Use CIC Use Description The status of the node The total number of AMPs currently executing session requests on this node The number of PEs currently active on this node The percent of CPU usage that is spent being active (not idle) The percent of time spent in UNIX PDE Kernel waiting for I/Os to complete The percent of CPU resources spent in UNIX PDE user service processing The percent of CPU resources spent in non-service user code processing The percent of total ByNet usage. The percentage of disk usage for this node The percent of Channel Interface Controller usage for this node Teradata Manager User Guide 99

100 Chapter 6: Monitoring Real-Time System Activity Getting Physical Utilization Details Table 17: Node Utilization Detail Report (continued) Data Label Disk Reads Disk Writes Average Disk Req Host Block Reads Host Block Writes Swap Reads Swap Writes Swap Drops Mem Segs Allocated Mem KB Allocated Mem Failures Mem Segs Agings Net Reads Net Writes Backup Seg Agings Backup KB Allocated Backup Segs Allocated Average CPU Use Parallel Efficiency Description The total number of physical disk reads for this node during the sample interval The total number of physical disk writes for this node during the sample interval The average number of outstanding disk requests for this node The number of message blocks received from all hosts. A message block may consist of multiple messages. The number of message blocks sent to all hosts. A message block may consist of multiple messages. The number of segments read into node memory from the disk during the sample interval due to swapping The number of segments written to disk from node memory during the sample interval due to swapping The number of pages and segments dropped from node memory during the sample period due to swapping The number of segments allocated to memory resources The number of kilobytes allocated to memory resources The number of segment allocation attempts that failed The number of memory agings and collections done on old segments The number of messages read from the ByNet and input into the node during the sample interval The number of messages written from the node and output to the ByNet during the sample period The number of backup storage disk segments flushed from nonvolatile memory The number of Kilobytes of nonvolatile memory allocated for AMP backup storage during the sample interval The number of complete and partial nonvolatile memory allocations of disk segments read (written) for backup storage during the sample interval The average CPU usage An indication of the parallelism your system is achieving across all nodes and vprocs. This value is a percentage calculated as: Average usage x 100 / Maximum usage 100 Teradata Manager User Guide

101 Chapter 6: Monitoring Real-Time System Activity Monitoring Session Status Monitoring Session Status The Session Status reports provide information on individual sessions. To view Session Status 1 Open the Session Status Report by doing one of the following: From the Teradata Manager menu bar, click Monitor>Sessions, and choose the filter for the types of sessions to view: All - shows all sessions currently on the Database Active - shows all active sessions Blocked - shows sessions that are blocked by other sessions Idle - lists information about inactive and idle sessions Parsing - lists information about parsing sessions Responding - lists information about responding sessions Aborting - shows sessions that are in the process of aborting Other - lists information about sessions when there is a difference in the state of the AMP and PE or if the state is not Idle, Active, Blocked, Parsing, Responding, Aborting or Delayed, including those that are currently logged on to the Monitor Partition. Note: To view the state of the AMP and PE, right-click the session name to display the shortcut menu, and click Session Details. Delayed - shows sessions that are delayed From the Teradata Manager menu bar, click Monitor>Dashboard), and click the Sessions link below the corresponding display dial. For a description of the columns, see Table Use the menus at the top of the report window to filter your session report as described in Step 1. 3 To sort the data, click any of the column titles to sort on that field. 4 Right-click the name of the session to display the shortcut menu and click one of the following: Session Details - shows more details for this session Modify Session Priority - modify the priority of this session Abort Session - abort this session Blocked by - a report appears showing which sessions (if any) are blocking this one Blocking - a report appears showing which sessions this one is blocking Current SQL - view the SQL statements currently being executed by this session, along with job step information and associated Explain text Skew - a report appears showing skew (workload imbalance) for this session Teradata Manager User Guide 101

102 Chapter 6: Monitoring Real-Time System Activity Monitoring Session Status Modify Session Workload - modify session workload settings Release Request - release a request that is on hold Query Band - display a report showing the query band pairs applied to this session Session Status Report Table 18: Session Status Report Data Label Session Number User Name Account Workload Name Priority Request Count State AMP CPU Delta CPU CPU Skew AMP I/O Delta I/O Spool Host Description The session number for the session associated with this report The session owner The account name with which the user is logged in The workload for the current active query If the workload list on the server changes, Unknown WD ID <number> appears. To refresh the workloads in the cache, click Options>Refresh Workload List. The run priority of this session. This field may contain either systemdefault or user-created priority groups. The system-default priority groups are: R = Rush H = High M = Medium L = Low The number of requests processed by this session The current state of the session The total CPU time (in seconds) used on all AMPs by this session since the session was logged on The difference between the AMP CPU this time minus the value of the same field last time data was fetched The degree to which CPU activity was skewed for this session during the latest monitoring interval. Skew is a measure of workload balance amongst the CPUs in the system. Lower values of skew imply greater balance (better performance). Under optimal conditions, skew would be 0. The total number of logical input and output (reads and writes) issued across all AMPs by this session The difference between the AMP I/O this time minus the value of the same field last time data was fetched The total spool space for this session. The name of the host running the session 102 Teradata Manager User Guide

103 Chapter 6: Monitoring Real-Time System Activity Getting Session Details Table 18: Session Status Report (continued) Data Label Partition Blocked Time Idle Time Elapsed Time Logon Time Logon Source Description The partition name associated with this session The time that the session has been blocked. Teradata Manager is not aware of the session state before data collection was started. This means that a session may have been blocked for longer than the time shown. If fetching data directly from the Database, the earliest start time from which this period is calculated is the time at which Teradata Manager first collected session data. The time that the session has been Idle. Teradata Manager is not aware of the session state before data collection was started. This means that a session may have been idle for longer than the time shown. If fetching data directly from the Database, the earliest start time from which this period is calculated is the time at which Teradata Manager first collected session data. The total time that the current active request has been running The time (in yyyy-mm-dd hh:mm:ss format) that the session logged on The logon source information Getting Session Details From the Session Status Report, view details for any displayed session. To view Session Details 1 Open the Session Status Report by doing one of the following: From the Teradata Manager menu bar, click Monitor>Sessions, and choose the filter for the types of sessions to view: All - shows all sessions currently on the Database Active - shows all active sessions Blocked - shows sessions that are blocked by other sessions Idle - lists information about inactive and idle sessions Parsing - lists information about parsing sessions Responding - lists information about responding sessions Aborting - shows sessions that are in the process of aborting Teradata Manager User Guide 103

104 Chapter 6: Monitoring Real-Time System Activity Getting Session Details Session Detail Report Other - lists information about sessions when there is a difference in the state of the AMP and PE or if the state is not Idle, Active, Blocked, Parsing, Responding, Aborting or Delayed, including those that are currently logged on to the Monitor Partition. Delayed - shows sessions that are delayed From the Teradata Manager menu bar, click Monitor>Dashboard, and click the Sessions link below the corresponding display dial. For more information on viewing the Session Status Report, see Monitoring Session Status on page Double-click the session number, or right-click the number of the session to display the shortcut menu, and click Session Details. For a description of the columns, see Table From the Session Detail Report, choose the following options: << Previous - display detail information for the previous session Next >> - display detail information for the next session Modify Acct - modify account information for the session Note: Modifying accounts is allowed only in the DBC/SQL partition; therefore, this option is enabled only when the partition is DBC/SQL. Modify WD - modify session workload settings Abort - abort this session Release Request - release a request that is on hold Blocked By - display a report showing which sessions (if any) are blocking this one Blocking - display a report showing which sessions this one is blocking Query Band - display a report showing the query band pairs applied to this session Skew - display a report showing skew (workload imbalance) for this session SQL - view the SQL statements currently being executed by this session, along with job step information and associated Explain text Close - close the Session Detail dialog box The system name, host, session, and data refresh rate are displayed in the title bar of this report. The following table describes the data displayed in the body of the Session Detail Report. Table 19: Session Detail Report Data Label User Name Account Partition Description The session owner The account name with which the user is logged in The partition name associated with this session 104 Teradata Manager User Guide

105 Chapter 6: Monitoring Real-Time System Activity Getting Session Details Table 19: Session Detail Report (continued) Data Label Workload Classified By Priority AMP State PE State Logon Time/Date Logon Sequence Logon PE Number Run VProc Number Current Request Start Current Request CPU Current Request I/Os PE CPU Seconds Total AMP CPU Seconds Delta AMP CPU Seconds Description The workload associated with this session Indicates how the current workload was assigned: System = Automatically by TWM DBA-Session = Manually at Request Level DBA-Request = Manually at Session Level The run Priority of this session. This field may contain either system-default or user-created priority groups. The system-default priority groups are: R = Rush H = High M = Medium L = Low The current state of this session in AMP vprocs The current state of this session within the PE The time (in yyyy-mm-dd hh:mm:ss format) that the session logged on The Logon Sequence Number for this session. This value, which is associated with a session when the session logs on, is used to identify a collection of sessions performing a related activity. The vproc number of the PE the session is currently logged on to. It identifies the PE that has control responsibility for the session. The vproc number of the AMP or PE to which the session initiates requests Shows the year, month, and day and the hour, minutes, and seconds when the currently executing request was started. This field is blank if no request is executing on this session The amount of CPU time that the session has used since the current request was executed. This field is blank if no request is executing on this session. The number of logical I/Os that the session has issued since the current request was executed. This field is blank if no request is executing on this session. The current elapsed CPU usage in the Parser, Dispatcher portion of the PE for this session The total CPU time (in seconds) used on all AMPs by this session since the session was logged on The difference between the CPU Seconds values from the current collection (this time) and the previous collection (the last time data was fetched) Teradata Manager User Guide 105

106 Chapter 6: Monitoring Real-Time System Activity Getting Session Details Table 19: Session Detail Report (continued) Data Label CPU Skew AMP I/O Disk Skew Transaction Count Request Count Request Cache Hits Current Spool Temporary Space Block Count Time Blocked Time Idle Elapsed Time Logon Source Description The degree to which CPU activity was skewed for this session during the latest monitoring interval. Skew is a measure of workload balance amongst the CPUs in the system. Lower values of skew imply greater balance (better performance). Under optimal conditions, skew would be 0. The total number of logical input and output (reads and writes) issued across all AMPs by this session The degree to which disk activity was skewed for this session during the latest monitoring interval. Skew is a measure of workload balance amongst the disks in the system. Lower values of skew imply greater balance (better performance). Under optimal conditions, skew would be 0. The number of requests processed by this session The number of requests processed by this session The number of times the request cache has been used during this session The total spool space for this session The total amount of temporary space used by temporary tables within this session The number of sessions blocking this session. This number is displayed as: 1 = session blocked by one session 2 = session blocked by two sessions 3 = session blocked by three sessions greater than 3 = session blocked by more than three sessions The time that the session has been blocked. Teradata Manager is not aware of the session state before data collection was started. This means that a session may have been blocked for longer than the time shown. If fetching data directly from the database, the earliest start time from which this period is calculated is the time at which Teradata Manager first collected session data. The time that the session has been idle. Teradata Manager is not aware of the session state before data collection was started. This means that a session may have been idle for longer than the time shown. If fetching data directly from the database, the earliest start time from which this period is calculated is the time at which Teradata Manager first collected session data. The actual amount of elapsed time the current request used. The logon source information 106 Teradata Manager User Guide

107 Chapter 6: Monitoring Real-Time System Activity Modifying Session Priority Modifying Session Priority From the Session Status Report, modify the priority of the session. To modify session priority 1 Open the Session Status Report by doing one of the following: From the Teradata Manager menu bar, click Monitor>Sessions, and choose the filter for the types of sessions to view: All - shows all sessions currently on the Database Active - shows all active sessions Blocked - shows sessions that are blocked by other sessions Idle - lists information about inactive and idle sessions Parsing - lists information about parsing sessions Responding - lists information about responding sessions Aborting - shows sessions that are in the process of aborting Other - lists information about sessions when there is a difference in the state of the AMP and PE or if the state is not Idle, Active, Blocked, Parsing, Responding, Aborting or Delayed, including those that are currently logged on to the Monitor Partition. Note: To view the state of the AMP and PE, right-click the name of the session to display the shortcut menu, and click Session Details. Delayed - shows sessions that are delayed From the Teradata Manager menu bar, click Monitor>Dashboard, and click the Sessions link below the corresponding display dial. For more information on viewing the Session Status Report, see Monitoring Session Status on page Right-click the number of the session to display the shortcut menu. 3 Select Modify Session Priority. 4 In the Enter New Account box, add two characters to the beginning of the account string as follows: Priority Characters of the Account String Rush $R High $H Medium $M Low $L Teradata Manager User Guide 107

108 Chapter 6: Monitoring Real-Time System Activity Aborting Sessions 5 If this change is to apply to all requests, select Apply to All Requests. If this change is to apply to the current request only, select Apply to Current Request Only. 6 Click OK. 7 A message appears indicating the account string has been modified. Click OK. The Account column shows the priority that was assigned to the session(s). Note: Teradata Manager does not show the current priority if the account was modified for only the currently running request. Aborting Sessions From the Session Status Report, abort a session. To abort a session 1 Open the Session Status Report by doing one of the following: From the Teradata Manager menu bar, click Monitor>Sessions, and choose the filter for the types of sessions to view: All - shows all sessions currently on the Database Active - shows all active sessions Blocked - shows sessions that are blocked by other sessions Idle - lists information about inactive and idle sessions Parsing - lists information about parsing sessions Responding - lists information about responding sessions Aborting - shows sessions that are in the process of aborting Other - lists information about sessions when there is a difference in the state of the AMP and PE or if the state is not Idle, Active, Blocked, Parsing, Responding, Aborting or Delayed, including those that are currently logged on to the Monitor Partition. Delayed - shows sessions that are delayed From the Teradata Manager menu bar, click Monitor>Dashboard, and click the Sessions link below the corresponding display dial. For more information on viewing the Session Status Report, see Monitoring Session Status on page Right-click the number of the session to display the shortcut menu. Note: For SESDELAYED sessions, skip to step 4, then click OK to abort. 3 Click Abort Session. 4 Verify that the session information is correct. For a description of the columns, see Table Teradata Manager User Guide

109 Chapter 6: Monitoring Real-Time System Activity Viewing What the Selected Session is Blocking 5 For the session to automatically log itself off after aborting the transaction(s), select Logoff Session(s) after Aborting Current Transaction(s). 6 Click Abort. Abort Session Report Table 20: Abort Session Report Data Label Host Id Session Number User Name Description The account name with which the user is logged in The identifier for the session The logon name of the user Viewing What the Selected Session is Blocking From the Session Status Report, view what sessions the selected session is blocking. To view what the selected session is blocking 1 Open the Session Status Report by doing one of the following: From the Teradata Manager menu bar, click Monitor>Sessions, and choose the filter for the types of sessions to view: All - shows all sessions currently on the Database Active - shows all active sessions Blocked - shows sessions that are blocked by other sessions Idle - lists information about inactive or idle sessions Parsing - lists information about parsing sessions Responding - lists information about responding sessions Aborting - shows sessions that are in the process of aborting Other - lists information about sessions when there is a difference in the state of the AMP and PE or if the state is not Idle, Active, Blocked, Parsing, Responding, Aborting or Delayed, including those that are currently logged on to the Monitor Partition. Delayed - shows sessions that are delayed From the Teradata Manager menu bar, click Monitor>Dashboard, and click the Sessions link below the corresponding display dial. For more information on viewing the Session Status Report, see Monitoring Session Status on page Right-click the number of the session to display the shortcut menu. Teradata Manager User Guide 109

110 Chapter 6: Monitoring Real-Time System Activity Viewing What the Selected Session is Blocked By Blocking Sessions Report 3 Click Blocking. For a description of the columns, see Table 21. Table 21: Blocking Sessions Report Data Label User Host Session Locked Object Lock Mode Lock Status Lock Type Description Owner of the session Host on which the session is running The identifier for the session The database and table name or ID of the blocking session The lock mode of the blocking session The lock status of the blocking session The lock type of the blocking session Viewing What the Selected Session is Blocked By From the Session Status Report, view information about the session(s) that are blocking the displayed session. To view what the selected session is blocked by 1 Open the Session Status Report by doing one of the following: From the Teradata Manager menu bar, click Monitor>Sessions, and choose the filter for the types of sessions to view: All - shows all sessions currently on the Database Blocked - shows sessions that are blocked by other sessions From the Teradata Manager menu bar, click Monitor>Dashboard, and click the Sessions link below the corresponding display dial. For more information on viewing the Session Status Report, see Monitoring Session Status on page Right-click the number of the session to display the shortcut menu. 3 Click Blocked By. For a description of the columns, see Table Teradata Manager User Guide

111 Chapter 6: Monitoring Real-Time System Activity Viewing Query Band Pairs Blocked By Report Table 22: Blocked By Report Data Label Host Id Session Id User Status Mode Type Object Description The logical host ID of the blocking session The session ID of the blocking session The user ID or name of the most critical blocking session The lock status of the blocking session The lock mode of the blocking session The lock type of the blocking session The database and table name or ID of the blocking session Viewing Query Band Pairs From the Session Status Report, view information about the query band pairs for the selected session. To view the query band pairs for the selected session 1 Open the Session Status Report by doing one of the following: From the Teradata Manager menu bar, click Monitor>Sessions, and choose the filter for the types of sessions to view: All - shows all sessions currently on the Database Active - shows all active sessions Blocked - shows sessions that are blocked by other sessions Idle - lists information about inactive and idle sessions Parsing - lists information about parsing sessions Responding - lists information about responding sessions Aborting - shows sessions that are in the process of aborting Other - lists information about sessions when there is a difference in the state of the AMP and PE or if the state is not Idle, Active, Blocked, Parsing, Responding, Aborting or Delayed, including those that are currently logged on to the Monitor Partition. Delayed - shows sessions that are delayed From the Teradata Manager menu bar, click Monitor>Dashboard, and click the Sessions link below the corresponding display dial. 2 Right-click the number of the session to display the shortcut menu. Teradata Manager User Guide 111

112 Chapter 6: Monitoring Real-Time System Activity Monitoring Delay Queue Statistics Query Bands Report 3 Click Query Band. The Query Band Report appears if query bands are set for the session. For a description of the columns, see Table 23. Table 23: Query Bands Report Data Label Level Name Value Description The transaction (T) or session (S) level. The name part of the name/value pair. The value part of the name/value pair. Monitoring Delay Queue Statistics The Delay Queue Statistics Report shows details on the objects in the Workload Delay Queue. To get details on objects in the Workload Delay Queue From the Teradata Manager menu bar, click Monitor>Teradata DWM>Delay Queue Stats. For a description of the columns, see Table 24. To change the report view 1 To toggle between table and graph views, click the View as Graph or View as Table link at the top right corner of the window. 2 To toggle between showing and hiding options in the graph view, click the Show Options or Hide Options link on the right side of the window. 3 Explore other views of the data: a b Do one of the following to display the shortcut menu: If viewing a table report, right-click the workload name in the first column. If viewing a graph report, click the vertex. Click Session Report. For specifics on Session Report contents, see Session Status Report on page Teradata Manager User Guide

113 Chapter 6: Monitoring Real-Time System Activity Monitoring the Workload Delay Queue List Delay Queue Statistics Report Table 24: Delay Queue Statistics Report Data Label Workload Name WD ID Active Limit Delayed Description The name assigned to the workload The ID assigned to the workload The number of active Sessions for the object The maximum number of active Sessions for the object The number of Sessions on the Delay Queue for the object Monitoring the Workload Delay Queue List The Workload Delay Queue List Report shows all requests in the Workload Delay Queue. To view the workload delay queue list From the Teradata Manager menu bar, click Monitor>Teradata DWM>WD Delay Queue List. For a description of the columns, see Table 25. To change the report view 1 Right-click the name of the user to display the shortcut menu. 2 Click one of the following: Abort Session - aborts this session Release Request - releases a request that is on hold Workload Delay Queue List Report Table 25: Workload Delay Queue List Report Data Label (no label) User Host Session Request Description The sequence number of this session on the workload delay queue. The lower the number, the longer the request is on the queue The owner of the delayed request The Host ID of the session number associated with the delayed request The session number associated with the delayed request The request number that is delayed Teradata Manager User Guide 113

114 Chapter 6: Monitoring Real-Time System Activity Monitoring Object Logon Statistics Table 25: Workload Delay Queue List Report (continued) Data Label Workload Time Held Overridable Blocking Count Description The name of the workload on which the request is delayed The length of time the request has been held on the workload delay queue Whether or not the delayed state of the request can be overridden (released) The number of consecutive times that this request has been identified as blocking at least one other session Monitoring Object Logon Statistics The Object Logon Statistics Report shows details on the objects in the Workload Delay Queue. To get object logon statistics From the Teradata Manager menu bar, click Monitor>Teradata DWM>Object Logon Stats. For a description of the columns, see Table 26. To change the report view 1 Right-click a name in the first column to display the shortcut menu. 2 Click Session Report. This report shows session details on an object. For specifics on Session Report contents, see Session Status Report on page 102. Object Logon Statistics Report Table 26: Object Logon Statistics Report Data Label Object Type Name Active Limit Delayed Description The name assigned to the object The ID assigned to the object The number of active logons for the object The maximum number of active logons for the object The number of logons on the Delay Queue for the object 114 Teradata Manager User Guide

115 Chapter 6: Monitoring Real-Time System Activity Monitoring Object Query Statistics Monitoring Object Query Statistics The Object Query Statistics Report shows details on the objects in the Workload Delay Queue. To get object query statistics From the Teradata Manager menu bar, click Monitor>Teradata DWM>Object Query Stats. For a description of the columns, see Table 27. To change the report view 1 Right-click a name in the first column to display the shortcut menu. 2 Click Session Report. This report shows session details on an object. For specifics on Session Report contents, see Session Status Report on page 102. Object Query Statistics Report Table 27: Object Query Statistics Report Data Label Object Type Name Active Limit Delayed Description The name assigned to the object The ID assigned to the object The number of active queries for the object The maximum number of active queries for the object The number of queries on the Delay Queue for the object Monitoring the Object Delay Queue List The Object Delay Queue List shows all objects in the Workload Delay Queue. To view the object delay queue list From the Teradata Manager menu bar, click Monitor>Teradata DWM>Object Delay Queue List. For a description of the columns, see Table 28. Teradata Manager User Guide 115

116 Chapter 6: Monitoring Real-Time System Activity Monitoring Object Utility Statistics To change the report view 1 Right-click the name of the user to display the shortcut menu. 2 Click one of the following: Abort Session - aborts this session Release Request - releases a request that is on hold Object Delay Queue List Report Table 28: Object Delay Queue List Report Data Label (no label) User Host Session Request Workload Time Held Overrideable Blocking Count Description The sequence number of this session on the delay queue. The lower the number, the longer the request is on the queue. The owner of the delayed request The Host ID of the session number associated with the delayed request The session number The request number associated with the delayed object The workload this object is assigned to The length of time this object has been delayed Whether or not the delay state of this object can be overridden The number of consecutive times that this request has been identified as blocking at least one other session Monitoring Object Utility Statistics The Utility Statistics Report shows details about utilities running on the System. To get utility statistics From the Teradata Manager menu bar, click Monitor>Teradata DWM>Object Utilities Stats. For a description of the columns, see Table Teradata Manager User Guide

117 Chapter 6: Monitoring Real-Time System Activity Monitoring Event Status Object Utility Statistics Report Table 29: Object Utility Statistics Report Data Label Name Active Limit Description The type of utility, showing the following five categories: FastLoad + MultiLoad MultiLoad FastLoad FastExport Archive/Restore (ARC) Note: For ARC to appear, this report must be for Teradata Database or later. The number of utilities of this type that are active The current limit on the number of active utilities of this type Monitoring Event Status The Event Status Report gives a complete snapshot of the internal state of Teradata DWM at any point in time. The data returns several types of status of Teradata DWM. The Event Status Report shows the status of each defined event, expression, and state. System Condition (SysCon) events relate to system performance and availability, and can include user-defined events for externally-detected occurrences such as "dual system down." Operating Environment (OpEnv) events relate to time periods, and can include user-defined events such as "load jobs starting. To get event status From the Teradata Manager menu bar, click Monitor>Teradata DWM>Event Status. For a description of the columns, see Table 30. For an example of the report, see Figure 7 on page 120. Teradata Manager User Guide 117

118 Chapter 6: Monitoring Real-Time System Activity Monitoring Event Status Event Status Report The current state is shown in the title bar of the Event Status Report. Table 30: Event Status Report Column Data Label Description 1 Record Type Defines the type of data shown in this row. The type can be any of the following: SysCon is System Condition OpEnv is Operating Environment Notify is Notify Expression 2 Name Name of the System Condition or Operating Environment, depending on the Record Type, specified using Teradata DWM Administrator. 3 Status The current status of the System Condition or Operating Environment, depending on the Record Type. This can be Active or Inactive. 4 Duration If Record Type is OpEnv or Notify, then duration is NA. If the status in Column 8 in Active, the duration is NA: If the status in Column 8 is Inactive then: If True, SysCon is active since a minimum duration is specified for the System Condition to stay active although the Expression is no longer True. If False, SysCon is not active because there is no minimum duration or the duration has expired. 5 Active Date The date the record was set to its current status. 6 Active Time The time the record was set to its current status. Time is displayed in hours, minutes, and seconds (HH:MM:SS format). 7 Expression The expression previously defined using Teradata DWM Administrator. If blank, the event is not applicable to the Normal System Condition, the Always Operating Environment, and the notify Action. 8 Status The current status associated with an individual expression. This can be Active or Inactive. If blank, the event is not applicable to the Normal System Condition, the Always Operating Environment, and the notify Action. 118 Teradata Manager User Guide

119 Chapter 6: Monitoring Real-Time System Activity Monitoring Event Status Table 30: Event Status Report (continued) Column Data Label Description 9 Date The date the expression was last changed. This is the date when the expression status was set to Active or Inactive. If blank, the event is not applicable to the Normal System Condition, the Always Operating Environment, and the notify Action. 10 Time The time the expression was last changed. This is the time when the expression status was set to Active or Inactive. Time is displayed in hours, minutes, and seconds (HH:MM:SS format). If blank, the event is not applicable to the Normal System Condition, the Always Operating Environment, and the notify Action. 11 Event The event previously defined using Teradata DWM Administrator. If blank, the event is not applicable to this Normal System Condition, the Always Operating Environment, and the notify Action. 12 Status The current status associated with an individual event. This can be Active or Inactive. If blank, the event is not applicable to this Normal System Condition, the Always Operating Environment, and the notify Action. 13 Date The date the event was last changed. This is the date when the status was set to Active or Inactive. If blank, the event is not applicable to this Normal System Condition, the Always Operating Environment, and the notify Action. 14 Time The time, in seconds, the event was last changed. This is the time when the status was set to Active or Inactive. Time is displayed in hours, minutes, and seconds (HH:MM:SS format). If blank, the event is not applicable to this Normal System Condition, the Always Operating Environment, and the notify Action. Teradata Manager User Guide 119

120 Chapter 6: Monitoring Real-Time System Activity Using Performance Monitor (PMON) Example The following example shows a system running with an active SysCon named SysCon4 and an OpEnv named Always. The expression that activated SysCon4 is EC_JUMBO_1. This expression is comprised of a number of User Defined Events (UDE), some that are active and some that are inactive. Note: The current state is shown in the title bar of the Event Status Report. Figure 7: Example of an Event Status Report Using Performance Monitor (PMON) Teradata Performance Monitor is used to monitor in detail the general health of a Teradata Database. It also allows analysis of current performance and both current and historical session information, and to abort sessions that are causing system problems. For more information, see Teradata Performance Monitor on page 297. To start Teradata Performance Monitor From the Teradata Manager menu bar, click Monitor>Performance Monitor. Instructions for using this program are in the Teradata Performance Monitor online help. Using Session Information Session Information (SI) uses the Teradata Performance Monitor to collect the session PM data from the Teradata Database. It then formats and shows key information about each session, based on the current collection rate. SI shows logon sessions in different categories, and helps to identify blocked and long idle sessions and abort sessions on the Teradata Database. For more information, see Session Information on page Teradata Manager User Guide

121 Chapter 6: Monitoring Real-Time System Activity The Graph Legend To start Session Information From the Teradata Manager menu bar, click Monitor>Session Information. Instructions for using this program are in the Session Information online help. The Graph Legend After choosing an option that creates a graph, a legend displays and describes the graphing attributes. To get help for the graph 1 Click anywhere in the graph to make it active. 2 Press F1. To disable the legend Do the following to disable the legend so it does not appear when any graph is opened. From the Teradata Manager menu bar, click Graph>Legend>Disable. The legend closes and does not appear when graphs are opened in the future. To enable the legend From the Teradata Manager menu bar, click Graph>Legend>Enable. The legend opens and continues to appear when graphs are opened in the future. Teradata Manager User Guide 121

122 Chapter 6: Monitoring Real-Time System Activity The Graph Legend 122 Teradata Manager User Guide

123 CHAPTER 7 Monitoring the Delay Queue The Teradata Manager Dashboard shows both real-time and historical information about the Delay Queue. This information provides the administrator with the ability to easily visualize any unusual conditions related to workload performance. Note: For Teradata Manager to display the Delay Queue, Teradata Dynamic Workload Manager (Teradata DWM) must be enabled. See the instructions in the Teradata Dynamic Workload Manager User Guide. After enabling category 2 (throttle) rules in Teradata DWM, the tabs in the Dashboard display as Delay Queue Snapshot and Delay Queue History. The following topics provide information on monitoring the delay queue: Viewing a Snapshot of the Workload Delay Queue Getting Workload Delay Queue Statistics Viewing Workload Delay Queue History Viewing and Releasing Requests in the Workload Delay Queue Viewing a Snapshot of the Workload Delay Queue The Delay Queue tab shows all of the throttled objects that the Teradata Dynamic Workload Manager system delays. To view a snapshot of the Workload Delay Queue 1 From the Teradata Manager menu bar, click Monitor>Dashboard. 2 Click the Delay Queue Snapshot tab. A count of throttled objects appears in the Delay Queue. 3 From this tab, do the following: View the Delay Queue Report by clicking on the Delay Queue Statistics Report link View the Delay Queue History Report by clicking on the Delay Queue History Graph link Teradata Manager User Guide 123

124 Chapter 7: Monitoring the Delay Queue Getting Workload Delay Queue Statistics Getting Workload Delay Queue Statistics From the Delay Queue tab of the Dashboard, get details on the objects in the Workload Delay Queue. To get details on objects in the Workload Delay Queue 1 From the Teradata Manager menu bar, click Monitor>Dashboard. 2 Click the Delay Queue Snapshot tab. A count of throttled objects appears in the Delay Queue. 3 Click the Delay Queue Statistics Report link. To change the report view 1 To toggle between table and graph views, click the View as Graph or View as Table link at the top right corner of the window 2 To toggle between showing and hiding options in the graph view, click the Show Options or Hide Options link on the right side of the window. 3 Explore other views of the data: a b Do one of the following to display the shortcut menu: If viewing a table report, right-click the name in the first column. If viewing a graph report, click the vertex. Click Session Report. The Delayed Session Report appears and lists all delayed sessions in the selected Delay Queue. Workload Delay Queue Statistics Report Table 31: Workload Delay Queue Detail Report Data Label Workload Name WD ID Active Limit Delayed Description The name assigned to the workload The ID assigned to the workload The number of active Sessions for the object The maximum number of active Sessions for the object The number of Sessions on the Delay Queue for the object 124 Teradata Manager User Guide

125 Chapter 7: Monitoring the Delay Queue Viewing Workload Delay Queue History Viewing Workload Delay Queue History From the Delay Queue History tab of the Dashboard, get a historical view of the objects in the Workload Delay Queue. To get history information on objects in the Workload Delay Queue 1 From the Teradata Manager menu bar, click Monitor>Dashboard. 2 Click the Delay Queue History tab. The number of objects over time in the Delay Queue appears. 3 Click the Delay Queue History Graph link. 4 To get session details on an object, right-click the workload name to display the shortcut menu. 5 Select Session Report. For details on Session Report contents, see Session Status Report on page 102. Workload Delay Queue History Report Table 32: Workload Delay Queue History Report Data Label Workload Name WD ID Active Limit Delayed Description The name assigned to the workload The ID assigned to the workload The number of active Sessions for the object The maximum number of active Sessions for the object The number of Sessions on the Delay Queue for the object Viewing and Releasing Requests in the Workload Delay Queue The Delay Queue Session Report shows all of the requests that the Teradata Dynamic Workload Manager system delays. From this report, release a request from the delay queue. To view and release requests from the Workload Delay Queue 1 From the Teradata Manager menu bar, click Monitor>Dashboard. 2 Click the Delay Queue Snapshot tab. Teradata Manager User Guide 125

126 Chapter 7: Monitoring the Delay Queue Viewing and Releasing Requests in the Workload Delay Queue 3 Right-click and select Sessions. 4 Click OK. Workload Delay Queue Session List Table 33: Workload Delay Queue Session List Data Label Workload Name WD ID Active Limit Delayed Description The name assigned to the workload The ID assigned to the workload The number of active Sessions for the object The maximum number of active Sessions for the object The length of time (clock time) that the request has been held. 126 Teradata Manager User Guide

127 CHAPTER 8 Monitoring Workload Activity The Teradata Manager Dashboard shows both real-time and historical information about workloads. This information provides the administrator with the ability to easily visualize any unusual conditions related to workload performance. Note: For Teradata Manager to display Workload Definition data, Teradata Dynamic Workload Manager (Teradata DWM) must be enabled. See the instructions in the Teradata Dynamic Workload Manager User Guide. After enabling category 2 (throttle) and category 3 (workload) rules in Teradata DWM, the tabs in the Dashboard display as Workload Snapshot and Workload History. The following topics provide information on monitoring workload activity: Checking Workload Status Getting Workload Summary Statistics Getting Workload Detail Statistics Getting Workload History Statistics Specifying the Display for Workload Snapshot Graphs Checking Workload Status The Workload Snapshot tab graphically shows real-time status of all of the workloads on your system. Note: The graphs on this page are updated once per minute and only contain data collected over the previous minute. The update rate cannot be changed. To display the status of your workloads 1 From the Teradata Manager menu bar, click Monitor>Dashboard. 2 Click the Workload Snapshot tab. A set of graphs appear showing various workload statistics. 3 From this tab, do the following: Display the following reports by clicking on the respective link: Workload Definition Summary Report by clicking on WD Summary Report. See Teradata DWM Workload Definition Summary Report on page 129. Teradata Manager User Guide 127

128 Chapter 8: Monitoring Workload Activity Getting Workload Summary Statistics Active Requests History Graph, Arrival Rate History Graph or Response Time History Graph. See Workload Definition Summary History Report on page 132. Delay Queue Statistics Report. See Workload Delay Queue Statistics Report on page 124. Delay Queue History Graph. See Workload Delay Queue History Report on page 125. Right-click any graph vertex to display the shortcut menu that provides the following detail reports: WD Details -Workload Details. See Workload Definition Detail Report on page 130. Sessions Report. See Session Status Report on page 102. Workload History. See Workload Definition Summary History Report on page 132. Getting Workload Summary Statistics The Workload Definition Summary Report shows summary information about your workload definitions. To display summary workload information 1 Do one of the following: From the Teradata Manager menu bar, click Monitor>Dashboard, then click the Workload Snapshot tab, then click the WD Summary Report link. From the Teradata Manager menu bar, click Monitor>Teradata DWM>WD Summary. 2 To sort the data, click any of the column titles to sort on that field. To change the report view 1 To toggle between table and graph views. click the View as Graph or View as Table link at the top right corner of the window 2 To toggle between showing and hiding options in the graph view, click the Show Options or Hide Options link on the right side of the window. 3 Explore other views of the data: a b Do one of the following to display the shortcut menu: If viewing a table report, right-click the name in the WD Name column. If viewing a graph report, click the vertex. Click Session Report. 128 Teradata Manager User Guide

129 Chapter 8: Monitoring Workload Activity Getting Workload Summary Statistics The session detail information appears. For specifics on Session Report contents, see Session Status Report on page 102. c Click WD Details. The workload detail information appears. For specifics on Workload Detail Report contents, see Workload Definition Detail Report on page 130. Teradata DWM Workload Definition Summary Report In the following report, all time is in seconds and all counts are per minute, except those in the Active Requests and Delayed Requests columns. Those columns show a snapshot at the time the report was run. Table 34: Teradata DWM Workload Definition Summary Report Data Label WD Name WD ID Arrivals Completions Active Requests Delayed Requests Avg Response Time Avg CPU Time Avg Delay Time Exceptions Met SLG Abort Count Expected Arrivals Expected CPUTime Expected ResponseTime Expected Met SLG Description The name of the workload definition that this row represents. When the workload list on the server changes, Unknown WD ID <number> appears. To refresh the workloads in the cache, click Options>Refresh Workload List. The numerical ID assigned to the workload The number of queries that initiated in this workload The number of queries that completed in this workload The number of queries currently active in this workload The number of queries currently delayed in this workload The average time required to process a query for this workload The average CPU time required to process a query for this workload The average time a query in this workload is delayed The number of queries in this workload that were processed for exceptions The number of queries in this workload that met the service level goal The number of queries aborted in this workload The expected number of queries initiating in this workload The expected CPU time for queries in this workload The expected response time for queries in this workload The number of queries in this workload expected to meet the service level goal Teradata Manager User Guide 129

130 Chapter 8: Monitoring Workload Activity Getting Workload Detail Statistics Getting Workload Detail Statistics From the Workload Summary Report or from the Workload Snapshot tab on the Dashboard, view detailed information for a particular workload. To display workload detail information 1 Do one of the following: From the Workload Definition Summary Report in table format (see Getting Workload Summary Statistics on page 128), right-click the name of the workload to display the shortcut menu, and click WD Details. From the Workload Definition Summary Report in graph format, or from the Workload Snapshot tab on the Dashboard, right-click a graph vertex to display the shortcut menu, and click WD Details. 2 The following buttons are available: << Previous - detail information for the previous Workload Definition appears Next >> - detail information for the next Workload Definition appears Close - close the Workload Definition Detail dialog box Workload Definition Detail Report In the following report, all time is in seconds and all counts are per minute, except those in the Active Requests and Delayed Requests columns. Those columns show a snapshot at the time the report was run. Table 35: Workload Definition Detail Report Data Label Active Requests Arrivals Expected Arrivals Completions Min, Max and Avg Response Time Expected Avg Response Time Delayed Requests Avg Delay Times Description The number of queries currently active in this workload The number of queries that initiated in this workload The expected number of queries initiating in this workload The number of queries that completed in this workload The minimum, maximum and average response time for queries in this workload The expected average response time for queries in this workload The number of queries in this workload that were delayed The average delay time encountered by queries in this workload 130 Teradata Manager User Guide

131 Chapter 8: Monitoring Workload Activity Getting Workload History Statistics Table 35: Workload Definition Detail Report (continued) Data Label Min, Max and Avg CPU Time Expected Avg CPU Time Met SLG Expected Met SLG Exception Count Abort Count Description The minimum, maximum and average CPU time for queries in this workload The expected CPU time for queries in this workload The number of queries in this workload that met the service level goals of the workload The number of queries in this workload expected to meet the service level goals of the workload The number of queries in this workload that were processed for exceptions The number of queries aborted per second Getting Workload History Statistics The Workload History tab of the Dashboard graphically shows a historical view of workload performance. Note: The history graphs contain data for 60 one-minute intervals (one hour), with the most recent data on the right hand side of the graph. To display workload history data 1 From the Teradata Manager menu bar, click Monitor>Dashboard. 2 Click the Workload History tab. 3 From this tab, display the following reports by clicking on the respective link: Active Requests History Graph, Arrival Rate History Graph or Response Time History Graph (see Workload Definition Summary History Report on page 132) Delay Queue History Graph (see Workload Delay Queue History Report on page 125) To work with the history view 1 To toggle between table and graph views, click the View as Graph or View as Table link at the top right corner of the window 2 To toggle between showing and hiding options in the graph view, click the Show Options or Hide Options link on the right side of the window. 3 To change the graph options, make your new selections with the graph option check boxes, and click Update Graph. Teradata Manager User Guide 131

132 Chapter 8: Monitoring Workload Activity Specifying the Display for Workload Snapshot Graphs 4 Use the WD Filter list to display different workload definitions. Workload Definition Summary History Report Table 36: Workload Definition Summary History Report Data Label Time Arrivals Expected Arrivals Completions Active Queries Delayed Requests Min, Max and Avg Resp Time Exp Resp Time Min, Max and Avg CPU Time Exp CPU Time Avg Delay Time Exceptions Met SLG Exp Met SLG Description The time the data in the row was captured The number of queries that initiated in this workload The expected number of queries initiating in this workload The number of queries that completed in this workload The number of queries active in this workload at the time The number of requests in this workload that were delayed The minimum, maximum and average response time for queries in this workload The expected average response time for queries in this workload The minimum, maximum and average CPU time for queries in this workload The expected CPU time for queries in this workload The average delay time encountered by queries in this workload The number of queries in this workload that were processed for exceptions The number of queries in this workload that met the service level goals of the workload The number of queries in this workload expected to meet the service level goals of the workload Specifying the Display for Workload Snapshot Graphs By default, Teradata Manager uses specific criteria to pick the top eight workloads in the Workload Snapshot tab of the Dashboard. Alternatively, specify which workloads display on each graph. To specify which workloads display in the Workload Snapshot tab 1 From the Teradata Manager menu bar, click Monitor>Dashboard. 2 Click the Workload Snapshot tab. 132 Teradata Manager User Guide

133 Chapter 8: Monitoring Workload Activity Specifying the Display for Workload Snapshot Graphs 3 Right-click anywhere in the white background of the graph to display the shortcut menu. 4 Click Workload Options. 5 Select the User-Defined option. 6 Click to highlight the workload in the Available box, and click Add to move it to the Selected box or double-click the workload to move it to the Selected box. Select up to a maximum of eight workloads. The order the workloads appear in the Selected box determines how they display in the graph. Click Move Up or Move Down to change the display order. The graph shows them in order from left to right. 7 To remove the workload from the Selected box, select it and click Remove or double-click the workload. 8 To apply the same order to three of the four graphs, select the Apply to all graphs check box. The order is applied to the Active Requests, Response Time, and Arrival Rate graphs. Specify the display for Delay Queue separately. 9 Click OK to save your top workload preferences for future use. The next time the application is run, your workload preferences load. Any mismatched workloads are ignored. If there is no match at all, the Application Defaults option is used. To let Teradata Manager pick the top workloads with the highest value 1 From the Teradata Manager menu bar, click Monitor>Dashboard. 2 Click the Workload Snapshot tab. 3 Right-click anywhere in the white background of the graph to display the shortcut menu. 4 Click Workload Options. 5 Select Application Defaults. For the criteria used, see Table Click OK. Teradata Manager picks the top workloads with the highest value, and the top eight display in descending order. If there are less than eight workloads available, the graph shows all workloads. Table 37: Criteria Used to Determine the Top Workloads Graph Name Active Requests Response Time Arrival Rate Criteria Used to Determine the Top Workloads (Up to Eight) The top workloads (up to eight) that have the highest active request count. The top workloads (up to eight) that have the longest response time. The top workloads (up to eight) that have the highest arrival rate count. Teradata Manager User Guide 133

134 Chapter 8: Monitoring Workload Activity Specifying the Display for Workload Snapshot Graphs Table 37: Criteria Used to Determine the Top Workloads (continued) Graph Name Delay Queue Criteria Used to Determine the Top Workloads (Up to Eight) The top workloads (up to eight) that have the highest delayed request count, listed in descending order of delayed requests. 134 Teradata Manager User Guide

135 CHAPTER 9 Analyzing Workload Trends Based on data the Teradata Manager data collection service collects, Workload Analysis provides a historical view of how the system is being utilized. The data can be grouped in various ways, and trend tables and graphs can be filtered by many different criteria, depending on the type of report. For information on setting up the data collection service, see Step 8 - Enabling Data Collection on page 61. Teradata Manager provides the following workload trend tables and graphs: Analyzing CPU Utilization CPU Utilization Report Analyzing Disk I/O Utilization Analyzing Table Growth Analyzing Spool and Temp Space Usage Analyzing Heartbeat Query Response Time Analyzing User Count Analyzing Workload Definition Usage Trends Analyzing Workload Definition Query Trends Analyzing Resource Usage Trends Analyzing DBQL Usage Trends Analyzing DBQL Step Usage Trends Viewing the DBQL Summary Histogram Analyzing CPU Utilization The CPU Utilization Report provides several views of CPU usage on the system. To create the report 1 Click Analyze>Trends>CPU Utilization. 2 Select from the following: To recall previously saved filter settings and load the filter, click Load Filter, then locate the filter file using the Name of Filter File dialog box. Click Open. Teradata Manager User Guide 135

136 Chapter 9: Analyzing Workload Trends Analyzing CPU Utilization Note: When a saved filter is opened, the Duration remains the same as when it was last saved. The End Date is set to the current date, and the Start Date is calculated based on the Duration and End Date. Enter the filter parameters as follows: Either enter the Start Date and End Date, or just enter the End Date and the Duration. To display a calendar tool, click the arrow on the date fields. Select the report grouping from the Group By list (hour, day, week or month). Select the Start Hour and End Hour. Select the days of the week to display by checking the appropriate boxes in the Day of Week area. Select the entities to display data under Show Data for. To target specific objects such as specific users, click Specific User(s), and then click to highlight names in the Specific Users list. To add an entity that is not on the list, type the name in the Type in an entry box, and click Add to List. The wildcard characters * or? can be used. Under Report Type, select Table or Graph. Under Graph Data Fields, select an option to view a graph. For descriptions of the options see CPU Utilization Report on page 137. Note: The Graph report type is not available if All Users or All Accounts is selected under Show Data for. To save these filter settings, click Save Filter, then type in or select a name and location for the filter file using the Name of Filter File dialog box. Click Save. 3 Click OK to view the report. To change the report view 1 To toggle between table and graph views, click the View as Graph or View as Table link at the top right corner of the window 2 To toggle between showing and hiding options in the graph view, click the Show Options or Hide Options link on the right side of the window. 3 Explore other views of the data: a b Do one of the following to display the shortcut menu: If viewing a table report, right-click any name in the first column. If viewing a graph report, click the vertex. Click Session Report. The session detail information appears. For specifics on Session Report contents, see Session Status Report on page Teradata Manager User Guide

137 Chapter 9: Analyzing Workload Trends CPU Utilization Report c Click one of the following: Graph this entry - available when invoked from a table report that is not a system summary, this displays a graph of the selected user, account, application ID, and priority group Change Filter - the CPU Utilization Filter dialog box appears for changing the filter settings Display Disk I/O Utilization - the Disk I/O Utilization Report appears for the same filter criteria Display Resource History Node CPU Utilization - the Resource History Node CPU Utilization Report appears for the same time period CPU Utilization Report Depending on your filter options, this report contains some or all of the following fields: Table 38: CPU Utilization Report Column Name <Timestamp> User Name Account Application ID Priority Group Average CPU (%) Minimum CPU (%) Maximum CPU (%) Description This field shows the time of data capture. The contents change depending upon the time grouping selected (Date, Start of Week, Month, and so forth) The session owner The account name with which the user is logged in. The application ID The run priority of this session. This field may contain either systemdefault or user-created priority groups. The system-default priority groups are: R = Rush H = High M = Medium L = Low The percent of time the CPUs are busy, based on average CPU usage per node The minimum percent of time the CPUs are busy, based on minimum CPU usage per node The maximum percent of time the CPUs are busy, based on maximum CPU usage per node Teradata Manager User Guide 137

138 Chapter 9: Analyzing Workload Trends Analyzing Disk I/O Utilization Analyzing Disk I/O Utilization The Disk I/O Utilization Report provides several views of disk usage on the system. To create the report 1 Click Analyze>Trends>Disk I/O Utilization. 2 Select from the following: To recall previously saved filter settings and load the filter, click Load Filter, then locate the filter file using the Name of Filter File dialog box. Click Open. Note: When a saved filter is opened, the Duration remains the same as when it was last saved it. The End Date is set to the current date, and the Start Date is calculated based on the Duration and End Date. Enter the filter parameters as follows: Either enter the Start Date and End Date, or just enter the End Date and the Duration. Display a calendar tool by clicking the arrow on the date fields. Select the report grouping from the Group By list (hour, day, week or month). Select the Start Hour and End Hour. Select the days of the week to be displayed by checking the appropriate boxes in the Day of Week area. Select the entities to display data under Show Data for. To target specific objects such as specific users, click Specific User(s), and then click to highlight names in the Specific Users list. To add an entity that is not on the list, type the name in the Type in an entry box, and click Add to List. The wildcard characters * or? can be used. Under Report Type, select Table or Graph. Under Graph Data Fields, select an option to view a graph. For descriptions of the options see Disk I/O Utilization Report on page 139. Note: The Graph report type is not available if All Users or All Accounts is selected under Show Data for. To save these filter settings, click Save Filter, then type in or select a name and location for the filter file using the Name of Filter File dialog box. Click Save. 3 Click OK to view the report. To change the report view 1 To toggle between table and graph views, click the View as Graph or View as Table link at the top right corner of the window 2 To toggle between showing and hiding options in the graph view, click the Show Options or Hide Options link on the right side of the window. 138 Teradata Manager User Guide

139 Chapter 9: Analyzing Workload Trends Analyzing Disk I/O Utilization 3 Explore other views of the data: a b Activate the shortcut menu by doing the following: If viewing a table report, right-click any name in the first column If viewing a graph report, left-click the vertex Click one of the following: Graph this entry - available when invoked from a table report that is not a system summary, this displays a graph of the selected user, account, application ID, and priority group Change Filter - the Disk I/O Utilization Filter dialog box appears to change the filter settings Display CPU Utilization - the CPU Utilization Report appears for the same filter criteria Display Resource History Disk I/O Utilization - the Resource History Disk I/O Utilization Report appears for the same time period Disk I/O Utilization Report Depending on your filter options, this report contains some or all of the following fields: Table 39: Disk I/O Utilization Report Column Name <Timestamp> User Name Account Application ID Priority Group Average Disk I/O Minimum Disk I/O Maximum Disk I/O Description This field shows the time of data capture. The contents change depending upon the time grouping selected (Date, Start of Week, Month, and so forth) The session owner The account name with which the user is logged in The application Id The run Priority of this session. This field may contain either systemdefault or user-created priority groups. The system-default priority groups are: R = Rush H = High M = Medium L = Low The average number of disk I/Os The minimum number of disk I/Os The maximum number of disk I/Os Teradata Manager User Guide 139

140 Chapter 9: Analyzing Workload Trends Analyzing Table Growth Analyzing Table Growth The Table Growth Report provides several views of permanent space usage on the system. To create the report 1 Click Analyze>Trends>Table Growth. 2 Select from the following: To recall previously saved filter settings and load the filter, click Load Filter, then locate the filter file using the Name of Filter File dialog box. Click Open. Note: When a saved filter is opened, the Duration remains the same as when it was last saved. The End Date is set to the current date, and the Start Date is calculated based on the Duration and End Date. Enter the filter parameters as follows: Either enter the Start Date and End Date, or just enter the End Date and the Duration. Display a calendar tool by clicking the arrow on the date fields. Select the report grouping from the Group By list (hour, day, week or month). Select the Start Hour and End Hour. Select the days of the week to display by checking the appropriate boxes in the Day of Week area. Under Show Data for, select the entities to display data. To display data for specific tables, select the database in the Database Name box. To target specific objects such as specific tables, select the entities from the list by highlighting them. To add an entity that is not on the list, enter the name in the Type in an entry field, then click Add to List. The wildcard characters * or? can be used in this list. Under Report Type, select Table or Graph. Under Graph Data Fields, select an option to view a graph. For descriptions of the options, see Table Growth Report on page 141. To save these filter settings, click Save Filter, then type in or select a name and location for the filter file using the Name of Filter File dialog box. Click Save. 3 Click OK to view the report. To change the report view 1 To toggle between table and graph views, click the View as Graph or View as Table link at the top right corner of the window 2 To toggle between showing and hiding options in the graph view, click the Show Options or Hide Options link on the right side of the window. 140 Teradata Manager User Guide

141 Chapter 9: Analyzing Workload Trends Analyzing Table Growth 3 Explore other views of the data: a b Do one of the following to display the shortcut menu: If viewing a table report, right-click any name in the first column. If viewing a graph report, click the vertex. Click one of the following: Graph this entry - available when invoked from a table report that is not a system summary, this displays a graph of the selected database and table Change Filter - the Table Growth Filter dialog box appears to change the filter settings Table Growth Report Depending on your filter options, this report contains some or all of the following fields: Table 40: Table Growth Report Column Name <Timestamp> Database Name Current Perm Usage Table Name Table Size (MB) Primary Table Size (MB) Average Row Size Minimum Row Size Maximum Row Size Datablock Size Row Count Datablock Count Cylinder Count Index Count Description This field shows the time of data capture. The contents change depending upon the time grouping selected (Date, Start of Week, Month, and so forth) Name of the database Current permanent space usage Name of the table Table size, in megabytes. Includes index, fallback and journal subtables. Primary table size, in megabytes. Excludes index, fallback and journal sub-tables. Average size of a row in this table Minimum size of a row in this table Maximum size of a row in this table Average datablock size in bytes for this table Number of rows in the table Number of datablocks the table used Number of cylinders the table used Number of indexes the table used Teradata Manager User Guide 141

142 Chapter 9: Analyzing Workload Trends Analyzing Spool and Temp Space Usage Analyzing Spool and Temp Space Usage The Spool/Temp Space Usage Report provides several views of spool and temp space usage on your system. To create the report 1 Click Analyze>Trends>Spool/Temp Space Usage. 2 Select from the following: To recall previously saved filter settings and load the filter, click Load Filter, then locate the filter file using the Name of Filter File dialog box. Click Open. Note: When a saved filter is opened, the Duration remains the same as when it was last saved. The End Date is set to the current date, and the Start Date is calculated based on the Duration and End Date. Enter the filter parameters as follows: Either enter the Start Date and End Date, or just enter the End Date and the Duration. Display a calendar tool by clicking the arrow on the date fields. Select the report grouping from the Group By list (hour, day, week or month). Select the Start Hour and End Hour. Select the days of the week to display by checking the appropriate boxes in the Day of Week area. Select the entities to display data under Show Data for. To target specific objects such as specific users, click Specific User(s), and then click to highlight names in the Specific Users list. To add an entity that is not on the list, type the name in the Type in an entry box, and click Add to List. The wildcard characters * or? can be used. Under Report Type, select Table or Graph. Under Graph Data Fields, select an option to view a graph. See Spool/Temp Space Usage Report on page 143 for descriptions of the available data points. Note: The Graph report type is not available if All Users is selected under Show Data for. To save these filter settings, click Save Filter, then type in or select a name and location for the filter file using the Name of Filter File dialog box. Click Save. 3 Click OK to view the report. 142 Teradata Manager User Guide

143 Chapter 9: Analyzing Workload Trends Analyzing Spool and Temp Space Usage To change the report view 1 To toggle between table and graph views, click the View as Graph or View as Table link at the top right corner of the window 2 To toggle between showing and hiding options in the graph view, click the Show Options or Hide Options link on the right side of the window. 3 Explore other views of the data: a b Spool/Temp Space Usage Report Do one of the following to display the shortcut menu: If viewing a table report, right-click any name in the first column. If viewing a graph report, click the vertex. Click one of the following: Graph this entry - available when invoked from a table report that is not a system summary, this displays a graph of the selection Change Filter - the Spool/Temp Space Usage Filter dialog box appears to change the filter settings Depending on your filter options, this report contains some or all of the following fields: Table 41: Spool/Temp Space Usage Report Column Name <Timestamp> User Name Spool Space Limit Peak Spool Usage Minimum Peak Spool Maximum Peak Spool Current Spool Usage Minimum Current Spool Maximum Current Spool Temp Space Limit Description This field shows the time of data capture. The contents change depending upon the time grouping selected (Date, Start of Week, Month, and so forth) User name The sum of Maximum Current Spool across all vprocs for this user. For a system summary row, this is MaxSpool for 'DBC'. The sum of peak spool across all vprocs for this user. This field is not applicable if this is a system summary row. The minimum peak spool at the vproc level for this user. This field is not applicable if this is a system summary row. The maximum peak spool at the vproc level for this user. This field is not applicable if this is a system summary row. The sum of current spool usage across all vprocs. For a system summary row, this is summed across all databases. The minimum current spool at the vproc level The maximum current spool at the vproc level The sum of maximum temp space across all vprocs for this user. For a system summary row, this is MaxTemp for 'DBC'. Teradata Manager User Guide 143

144 Chapter 9: Analyzing Workload Trends Analyzing Heartbeat Query Response Time Table 41: Spool/Temp Space Usage Report (continued) Column Name Peak Temp Usage Minimum Peak Temp Maximum Peak Temp Current Temp Usage Minimum Current Temp Maximum Current Temp Description The sum of peak temporary space usage across all vprocs. This field is not applicable if this is a system summary row. Minimum peak temp usage at the vproc level for this user. This field is not applicable if this is a system summary row. Maximum peak temp usage at the vproc level for this user. This field is not applicable if this is a system summary row. The sum of current temp usage across all vprocs. For a system summary row, this is Current Temp usage summed across all databases. Minimum current temp usage at the vproc level Maximum current temp usage at the vproc level Analyzing Heartbeat Query Response Time The Response Time Report summarizes system query response times. To create the report 1 To toggle between table and graph views, click the View as Graph or View as Table link at the top right corner of the window 2 To toggle between showing and hiding options in the graph view, click the Show Options or Hide Options link on the right side of the window. 3 Select from the following: To recall previously saved filter settings and load the filter, click Load Filter, then locate the filter file using the Name of Filter File dialog box. Click Open. Note: When a saved filter is opened, the Duration remains the same as when it was last saved. The End Date is set to the current date, and the Start Date is calculated based on the Duration and End Date. Enter the filter parameters as follows: Either enter the Start Date and End Date, or just enter the End Date and the Duration. Display a calendar tool by clicking the arrow on the date fields. Select the report grouping from the Group By list (hour, day, week or month). Select the Start Hour and End Hour. Select the days of the week to display by checking the appropriate boxes in the Day of Week area. 144 Teradata Manager User Guide

145 Chapter 9: Analyzing Workload Trends Analyzing Heartbeat Query Response Time Under Show Data for, select the entities to display data. To target specific objects such as specific queries, select the entities from the list by highlighting them. Use the Specific Queries list to choose the queries to report on. If only one query is selected in the Specific Queries list, click Show Query to show the SQL text of the selected query Under Report Type, select Table or Graph. Under Graph Data Fields, select an option to view a graph. For descriptions of the options see Response Time Report on page 145. To save these filter settings, click Save Filter, then type in or select a name and location for the filter file using the Name of Filter File dialog box. Click Save. 4 Click OK to view the report. Response Time Report To change the report view 1 Click Analyze>Trends>Response Time. 2 Explore other views of the data: a b Do one of the following to display the shortcut menu: If viewing a table report, right-click any name in the first column. If viewing a graph report, click the vertex. Click one of the following: Graph this entry - available when invoked from a table report, this displays a graph of the selected query Change Filter - the Response Time Filter dialog box appears to enable changing the filter settings Display CPU Utilization - the CPU Utilization Report appears for the same time period Display Disk I/O Utilization - the Disk I/O Utilization Report appears for the same time period Table 42: Response Time Report Column Name <Timestamp> Query Name Description This field shows the time of data capture. The contents change depending upon the time grouping selected (Date, Start of Week, Month, and so forth) Note: <Timestamp> reflects the Teradata Database time at completion of the heartbeat query. The name assigned to the query Teradata Manager User Guide 145

146 Chapter 9: Analyzing Workload Trends Analyzing User Count Table 42: Response Time Report (continued) Column Name Response Time (ms) Retrieve Time (ms) Total Time (ms) Concurrency Blocking Duration (secs) Description The time (in milliseconds) it took to get the first response parcel from the Database The time required (in milliseconds) to retrieve all results Response time + retrieve time (in milliseconds) The average number of active tasks running on the Database while the heartbeat query was running The total time (in seconds) the heartbeat query was blocked. Analyzing User Count The User Count Report summarizes the number of concurrent and distinct users on your system. To create the report 1 Click Analyze>Trends>User Count. 2 Select from the following: To recall previously saved filter settings and load the filter, click Load Filter, then locate the filter file using the Name of Filter File dialog box. Click Open. Note: When a saved filter is opened, the Duration remains the same as when it was last saved. The End Date is set to the current date, and the Start Date is calculated based on the Duration and End Date. Enter the filter parameters as follows: Either enter the Start Date and End Date, or just enter the End Date and the Duration. Display a calendar tool by clicking the arrow on the date fields. Select the report grouping from the Group By list (hour, day, week, month). Select the Start Hour and End Hour. Select the days of the week to display by checking the appropriate boxes in the Day of Week area. Under Report Type, select Table or Graph. Under Graph Data Fields, select an option to view a graph. For descriptions of the options see User Count Report on page 147. To save these filter settings, click Save Filter, then type in or select a name and location for the filter file using the Name of Filter File dialog box. Click Save. 3 Click OK to view the report. 146 Teradata Manager User Guide

147 Chapter 9: Analyzing Workload Trends Analyzing Workload Definition Usage Trends User Count Report To change the report view 1 To toggle between table and graph views, click the View as Graph or View as Table link at the top right corner of the window 2 To toggle between showing and hiding options in the graph view, click the Show Options or Hide Options link on the right side of the window. 3 Explore other views of the data: a b Do one of the following to display the shortcut menu: If viewing a table report, right-click any name in the first column. If viewing a graph report, click the vertex. Click one of the following: Change Filter - the User Count Filter dialog box appears so filter settings can be changed Display CPU Utilization - the CPU Utilization Report appears for the same time period Display Disk I/O Utilization - the Disk I/O Utilization Report appears for the same time period Table 43: User Count Report Column Name <Timestamp> Number of Concurrent Users Number of Distinct Users Description This field shows the time of data capture. The contents change depending upon the time grouping selected (Date, Start of Week, Month, and so forth) Number of sessions logged on to the Database The number of distinct users logged on to the Database Analyzing Workload Definition Usage Trends This report shows trends in Workload Definition usage. To create the report 1 Click Analyze>Trends>Workload Definition Usage. Teradata Manager User Guide 147

148 Chapter 9: Analyzing Workload Trends Analyzing Workload Definition Usage Trends 2 Select from the following: To recall previously saved filter settings and load the filter, click Load Filter, then locate the filter file using the Name of Filter File dialog box. Click Open. Note: When a saved filter is opened, the Duration remains the same as when it was last saved. The End Date is set to the current date, and the Start Date is calculated based on the Duration and End Date. Enter the filter parameters as follows: Either enter the Start Date and End Date, or just enter the End Date and the Duration. Display a calendar tool by clicking the arrow on the date fields. Select the report grouping from the Group By list (time of day, hour, day, week or month) Select the Start Hour and End Hour Select the days of the week to display by checking the appropriate boxes in the Day of Week area Select the entities to display data under Show Data for. To target specific objects such as Specific Enforcement Priorities, click Specific User(s), and then click to highlight names in the Specific Users list. To add an entity that is not on the list, type the name in the Type in an entry box, and click Add to List. The wildcard characters * or? can be used. For an aggregate report, select the Aggregate check box. Under Report Type, select Table or Graph. Under Graph Data Fields, select an option to view the data. To save these filter settings, click Save Filter, then type in or select a name and location for the filter file using the Name of Filter File dialog box. Click Save. 3 Click OK to view the report. To change the report view 1 Right-click a name in the first column to display the shortcut menu. 2 Choose a report option: Change Filter - the Workload Definition Usage Filter dialog box appears so the filter settings can be changed Graph This Entry - available from a table report that is not a system summary, this displays a graph of the selected workload definition and enforcement priority Aggregate/De-Aggregate - aggregates or de-aggregates the report, depending on the current report status Display Workload Definition Query List - the Rejected Query List Report appears for the same time period 148 Teradata Manager User Guide

149 Chapter 9: Analyzing Workload Trends Analyzing Workload Definition Usage Trends Workload Definition Usage Report Table 44: Workload Definition Usage Report Column Name <Timestamp> WD Name Arrival Rate (hourly) (Ave., Min., Max. and Expected) Resp Time (secs.) (Ave., Min., Max. and Expected) CPU Time (secs.) (Ave., Min. and Max. Active Count (Ave., Min. and Max.) Completed Query Count Error Query Count Abort Query Count Rejected Query Count Delayed Query Count Exception Query Count Exceeded SLG Query Count Completed Query % Error Query % Abort Query % Rejected Query % Delayed Query % Exception Query % Exceeded SLG Query % Description This field shows the time of data capture. The contents change depending upon the time grouping selected (Date, Time of Day, Month, and so forth) The name of the workload definition that this row represents The average, minimum, maximum and expected arrival rate of queries in this workload during this collection interval The average, minimum, maximum and expected response time for queries in this workload during this collection interval The average, minimum, maximum and expected CPU time for queries in this workload during this collection interval The average, minimum and maximum active count for queries in this workload during this collection interval The number of queries that completed The number of queries that completed with errors The number of queries that were aborted The number of queries in this workload that were rejected during this collection interval The number of queries in this workload that were delayed during this collection interval The number of queries in this workload that were processed for exceptions during this collection interval The number of queries in this workload that exceeded the service level goals of the workload during this collection interval The percentage of queries that completed The percentage of queries that completed with errors The percentage of queries that were aborted The percentage of queries in this workload that were rejected during this collection interval The percentage of queries in this workload that were delayed during this collection interval The percentage of queries in this workload that were processed for exceptions during this collection interval The percentage of queries in this workload that exceeded the service level goals of the workload during this collection interval Teradata Manager User Guide 149

150 Chapter 9: Analyzing Workload Trends Analyzing Workload Definition Query Trends Analyzing Workload Definition Query Trends This report shows trends in Workload Definition Query usage. There are five workload definition query list reports. For the contents of each report, see the following: Rejected Query List Report on page 151 Delayed Query List Report on page 151 Exception Query List Report on page 152 Exceeded SLG Query List Report on page 153 Completed Query List Report on page 154 To create the report 1 Click Analyze>Trends>Workload Definition Query List. 2 Select from the following: To recall previously saved filter settings and load the filter, click Load Filter, then locate the filter file using the Name of Filter File dialog box. Click Open. Note: When a saved filter is opened, the Duration remains the same as when it was last saved. The End Date is set to the current date, and the Start Date is calculated based on the Duration and End Date. Enter the filter parameters as follows: Either enter the Start Date and End Date, or just enter the End Date and the Duration. Display a calendar tool by clicking the arrow on the date fields. Select the Start Hour and End Hour Select the days of the week to display by checking the appropriate boxes in the Day of Week area Select the entities to display data under Show Data for. To target specific objects such as specific users, click Specific User(s), and then click to highlight names in the Specific Users list. To add an entity that is not on the list, type the name in the Type in an entry box, and click Add to List. The wildcard characters * or? can be used. Under List Type, select the type of data to view. When choosing Completed Query List, specify a Minimum Row Count and Minimum Processing Time (in hh:mm:ss format). To save these filter settings, click Save Filter, then type in or select a name and location for the filter file using the Name of Filter File dialog box. Click Save. 3 Click OK to view the report. Caution: The amount of data generated by the Query List report can easily overwhelm the available memory on the Teradata Manager workstation and put the Teradata Manager application into a non-responsive state. To avoid this condition, change the Start Date, End Date, Start Hour, 150 Teradata Manager User Guide

151 Chapter 9: Analyzing Workload Trends Analyzing Workload Definition Query Trends and End Hour filter values so only a limited period of activity is reported. For example, 1 day between 9 a.m. and 12 p.m. If the report takes too long to process, simply close the window to cancel the query and stop the report from displaying. To change the report view Rejected Query List Report 1 Right-click a name in the first column to display the shortcut menu. 2 Choose a report option: Change Filter - the Workload Definition Query List Filter dialog box appears so the filter settings can be changed Display Workload Definition Usage - the Workload Definition Usage Report appears for the same Workloads and for the same time period Show SQL [only available for the Completed Query List Report] - the query text of the selected entry appears in a separate window. Note: The length of the query text can differ from a full to a partial display depending on your database query log (DBQL) setting. For information on this setting, see Database Administration. Refer to the LIMIT SQLTEXT option. Table 45: Rejected Query List Report Column Name Log Time Account User Name Session Logical Host ID Exception Code Error Text Query Text Description The time that the record was logged The Account String the query may be classified by The User Name the query may be classified by The Session under which the query was rejected The Logical Host ID of the query The Error Code encountered The text indicating what rule was violated The first 200 characters of the query text Delayed Query List Report Table 46: Delayed Query List Report Column Name Log Time Description The time that the record was logged Teradata Manager User Guide 151

152 Chapter 9: Analyzing Workload Trends Analyzing Workload Definition Query Trends Table 46: Delayed Query List Report (continued) Column Name WD Name Account User Name Session Profile Name Application ID Query Band Client Address Logical Host ID Delay Time Query Text Description The workload the query was assigned to The Account String the query may be classified by The User Name the query may be classified by The Session under which the query was run The Profile Name the query may be classified by The Application ID the query may be classified by The Query Band name the query may be classified by The Client Address the query may be classified by The Logical Host ID of the query The amount of time the query was delayed The first 200 characters of the query text Exception Query List Report Table 47: Exception Query List Report Column Name Log Time WD Name Account User Name Session Profile Name Application ID Query Band Client Address Logical Host ID Description The time that the record was logged The name of the workload The Account String the query may be classified by The User Name the query may be classified by The Session under which the query was run The Profile Name the query may be classified by The Application ID the query may be classified by The Query Band name the query may be classified by The Client Address the query may be classified by The Logical Host ID of the query 152 Teradata Manager User Guide

153 Chapter 9: Analyzing Workload Trends Analyzing Workload Definition Query Trends Table 47: Exception Query List Report (continued) Column Name Exception Type (Limit Exceeded) Exception Action New WD Name Exception Code Error Text Query Text Description Specifies what type of Teradata DWM exception occurred: Response time limit exceeded CPU time (AMP and PE) limit exceeded Number of AMPs limit exceeded AMP CPU skew limit exceeded AMP I/O count limit exceeded AMP I/O skew limit exceeded Max row count (for a step) exceeded Max row count (for a step) exceeded Blocked time limit exceeded Disk to CPU ratio exceeded Spool space limit exceeded Specifies the action taken: The request was aborted The request continued The request continued under a new WD The request continued but an Alert was sent The request continued but a (Windows) program was executed None. Warning mode Indicates the Workload Definition in which the query completed execution. This is different than the initial WD Name field if an exception condition was processed that specified the query be moved (downgraded) into another Workload. The Error Code encountered The text indicating what rule was violated The first 200 characters of the query text Exceeded SLG Query List Report Table 48: Exceeded SLG Query List Report Column Name Log Time WD Name Account User Name Session Description The time that the record was logged The name of the workload The Account String the query may be classified by The User Name the query may be classified by The Session under which the query was run Teradata Manager User Guide 153

154 Chapter 9: Analyzing Workload Trends Analyzing Workload Definition Query Trends Table 48: Exceeded SLG Query List Report (continued) Column Name Profile Name Application ID Query Band Client Address Logical Host ID CPU Time (CPU seconds) Response Time (seconds) Query Text Description The Profile Name the query may be classified by The Application ID the query may be classified by The Query Band name the query may be classified by The Client Address the query may be classified by The Logical Host ID of the query Specifies the actual CPU time for this query. Units are in seconds. Specifies the actual response time for this query. Units are in seconds The first 200 characters of the query text Completed Query List Report Table 49: Completed Query List Report Column Name Start Time WD Name Account User Name Session Profile Name Application ID Query Band Client Address Logical Host ID Est Rows Est Time Act Rows Act Time Query Text Description The time this query is submitted The name of the workload The Account String the query may be classified by The User Name the query may be classified by The Session under which the query was run The Profile Name the query may be classified by The Application ID the query may be classified by The Query Band name the query may be classified by The Client Address the query may be classified by The Logical Host ID of the query The estimated number of rows returned for this query. The estimated processing time in seconds. The total number of rows returned for this query. The actual processing time in seconds. The first 200 characters of the query text 154 Teradata Manager User Guide

155 Chapter 9: Analyzing Workload Trends Analyzing Resource Usage Trends Analyzing Resource Usage Trends The Resource Usage Trend Analysis feature provides tables and graphs of meaningful information from the Teradata ResUsage tables. This information can be used to understand: How busy the system is When the system is busy The balance between CPU usage and disk usage When row redistribution is taking place. There are five resource usage reports, each displaying specific trends in Resource usage. For the contents of each report, see the following: Resource Usage Report: CPU Usage on page 156 Resource Usage Report: Disk Usage on page 157 Resource Usage Report: Memory Usage on page 157 Resource Usage Report: Bynet Usage on page 157 Resource Usage Report: System Utilization on page 158 To create the report 1 Click Analyze>Trends>Resource Usage. 2 Select from the following: To recall previously saved filter settings and load the filter, click Load Filter, then locate the filter file using the Name of Filter File dialog box. Click Open. Note: When a saved filter is opened, the Duration remains the same as when it was last saved. The End Date is set to the current date, and the Start Date is calculated based on the Duration and End Date. Enter the filter parameters as follows: Either enter the Start Date and End Date, or just enter the End Date and the Duration. Display a calendar tool by clicking the arrow on the date fields. Select the report grouping from the Group By list (hour, day, week, month or time of day) Select the Start Hour and End Hour. Select the days of the week to display by checking the appropriate boxes in the Day of Week area. Under Show Data for, select the entities to display data. Under Report Type, select Table or Graph. Under Report/Graph Categories, select the report. To save these filter settings, click Save Filter, then type in or select a name and location for the filter file using the Name of Filter File dialog box. Click Save. 3 Click OK to view the report. Teradata Manager User Guide 155

156 Chapter 9: Analyzing Workload Trends Analyzing Resource Usage Trends To change the report view 1 To toggle between table and graph views, click the View as Graph or View as Table link at the top right corner of the window 2 To toggle between showing and hiding options in the graph view, click the Show Options or Hide Options link on the right side of the window. 3 Right-click a name in the first column to display the shortcut menu. 4 To change the data view, right-click a name in the first column to display the shortcut menu. 5 Choose a report option: Change Filter - the Resource Usage Filter dialog box appears enabling the filter settings to be changed Graph this entry - available when invoked from a table report that is not a system summary, this displays a graph of the selected node group Display CPU Usage - the system summary CPU Usage trend report appears for the same time period Display Disk/IO Usage - the system summary Disk I/O Usage trend report appears for the same time period Display Memory Usage - the system summary Memory Usage trend report appears for the same time period Display Bynet Usage - the system summary Bynet Usage trend report appears for the same time period Display System Usage - the system summary System Usage trend report appears for the same time period Resource Usage Report: CPU Usage Table 50: Resource Usage Report: CPU Usage Column Name <Timestamp> Total AMP CPU % Total Node CPU % Wait I/O CPU % Parallelism % Description This field shows the time of data capture. The contents change depending upon the time grouping selected (Date, Start of Week, Month, and so forth) Total AMP CPU utilization, in percent Total Node CPU utilization, in percent Percentage of I/O in wait Percentage of parallelism 156 Teradata Manager User Guide

157 Chapter 9: Analyzing Workload Trends Analyzing Resource Usage Trends Resource Usage Report: Disk Usage Table 51: Resource Usage Report: Disk Usage Column Name <Timestamp> Logical MB/Sec Ave I/O Size Read % of I/O Description This field shows the time of data capture. The contents change depending upon the time grouping selected (Date, Start of Week, Month, and so forth) Logical megabytes per second Average I/O size Percent of I/O that are reads Resource Usage Report: Memory Usage Table 52: Resource Usage Report: Memory Usage Column Name <Timestamp> Ave Free Mem MB Min Free Mem MB Swap Reads Description This field shows the time of data capture. The contents change depending upon the time grouping selected (Date, Start of Week, Month, and so forth) Average amount of free memory in megabytes Minimum amount of free memory in megabytes Number of swap reads Resource Usage Report: Bynet Usage Table 53: Resource Usage Report: Bynet Usage Column Name <Timestamp> MsgPtpReads MsgPtPWrites MsgPtPReadKB MsgPtPWriteKB MsgBrdReads MsgBrdWrites MsgBrdReadKB Description This field shows the time of data capture. The contents change depending upon the time grouping selected (Date, Start of Week, Month, and so forth) Point to point reads Point to point writes Point to point reads in kilobytes Point to point writes in kilobytes Broadcast message reads Broadcast message writes Broadcast message reads in kilobytes Teradata Manager User Guide 157

158 Chapter 9: Analyzing Workload Trends Analyzing DBQL Usage Trends Table 53: Resource Usage Report: Bynet Usage (continued) Column Name MsgBrdWriteKB NetMsgFCBlock NetMsgGroupBlock NetMsgResourceBlock NetMsgRxBlock Description Broadcast message writes in kilobytes Flow Control Block count Number of times the net software was blocked because the receiver could not implicitly enter the group Number of times the net software was blocked because the receiver could not get the necessary resources Number of times the net software could not accept a message and caused a transmitter to block Resource Usage Report: System Utilization Table 54: Resource Usage Report: System Utilization Column Name <Timestamp> CPU/Disk Ratio FSG Cache Miss Index Ratio Description This field shows the time of data capture. The contents change depending upon the time grouping selected (Date, Start of Week, Month, and so forth) The CPU/Disk ratio Physical I/Os divided by Logical I/Os Index I/Os divided by Data Block I/Os Analyzing DBQL Usage Trends The DBQL Trend Analysis feature allows the DBA to view historical trend data that the Teradata Manager Data Collector summarizes from the DBQL (Database Query Log). This information can be used to identify trends in queries that have been logged in the DBQL log. There are four reports, each displaying specific trends in DBQL usage. For the contents of each report, see the following: DBQL Usage Report: Condition Indicator Count on page 160 DBQL Usage Report: Response Time on page 161 DBQL Usage Report: Resource Usage on page 162 DBQL Usage Report: Parallelism on page Teradata Manager User Guide

159 Chapter 9: Analyzing Workload Trends Analyzing DBQL Usage Trends To create the report 1 Click Analyze>Trends>DBQL Usage. 2 Select from the following: To recall previously saved filter settings and load the filter, click Load Filter, then locate the filter file using the Name of Filter File dialog box. Click Open. Note: When a saved filter is opened, the Duration remains the same as when it was last saved. The End Date is set to the current date, and the Start Date is calculated based on the Duration and End Date. Enter the filter parameters as follows: Either enter the Start Date and End Date, or just enter the End Date and the Duration. Display a calendar tool by clicking the arrow on the date fields. Select the report grouping from the Group By list (hour, day, week, month or time of day) Select the Start Hour and End Hour Select the days of the week to display by checking the appropriate boxes in the Day of Week area Select the entities to display data under Show Data for. To target specific objects such as specific users, click Specific User(s), and then click to highlight names in the Specific Users list. To add an entity that is not on the list, type the name in the Type in an entry box, and click Add to List. The wildcard characters * or? can be used. Note: If Specific Error Code(s) is selected from the list, type the error code number in the Type in an entry box, and click Add to List. Highlight the error code by selecting it in the list box, and click OK or Save Filter. For an aggregate report, select the Aggregate check box. Use the Accounts selector to choose the account category to display data. Number of Amps, Row Count, Spool Usage - Only rows that meet these minimum and maximum threshold values are considered in the answer set. Under Report Type, select Table or Graph. Under Categories, select the type of data to view. To save these filter settings, click Save Filter, then type in or select a name and location for the filter file using the Name of Filter File dialog box. Click Save. 3 Click OK to view the report. Teradata Manager User Guide 159

160 Chapter 9: Analyzing Workload Trends Analyzing DBQL Usage Trends To change the report view 1 Right-click a name in the first column to display the shortcut menu. 2 Choose a report option: Change Filter - the DBQL Usage Filter dialog box appears enabling the filter settings to be changed Graph this entry - available when invoked from a table report that is not a system summary, this displays a graph of the selected data Aggregate/De-Aggregate - aggregates or de-aggregates the report, depending on the current report status Display DBQL Step Usage- the DBQL Step Usage Report appears for the same time period Display DBQL Histogram Report - the DBQL Histogram Report appears for the same time period Display DBQL xxxx Category Report - the report for the other categories appears for the same time period DBQL Usage Report: Condition Indicator Count Table 55: DBQL Usage Report: Condition Indicator Count Column Name <Timestamp> WD Name Warnings Aborts Cached No Classification WD Override SLG Met Time Limit Exception AMP/PE Exceptions AMP CPU Skew Exception Description This field shows the time of data capture. The contents change depending upon the time grouping selected (Date, Start of Week, Month, and so forth) Name assigned to the workload The number of queries with warnings The number of aborted queries The number of queries found in step cache The number of queries not classified into a workload group The number of queries having a workload classification that the user has overridden The number of queries that met the workload group service level goals The number of queries the service level goal allows to exceed the time limit The number of queries the service level goal allows to exceed the CPU Time The number of queries the service level goal allows to exceed the CPU Skew 160 Teradata Manager User Guide

161 Chapter 9: Analyzing Workload Trends Analyzing DBQL Usage Trends Table 55: DBQL Usage Report: Condition Indicator Count (continued) Column Name AMP I/O Count Exceptions AMP I/O Skew Exceptions Max Row Count for Steps Exception Row Count Exception Blocked Time Exception Disk to CPU Exception Spool Space Exception AMP Count Exception Description The number of queries the service level goal allows to exceed the AMP I/O count The number of queries the service level goal allows to exceed the AMP I/O skew The number of queries the service level goal allows to exceed the maximum row count for steps The number of queries the service level goal allows to exceed the row count The number of queries the service level goal allows to exceed the blocked time The number of queries the service level goal allows to exceed the disk to CPU ratio The number of queries the service level goal allows to exceed the spool space The number of queries the service level goal allows to exceed the Amp count DBQL Usage Report: Response Time Table 56: DBQL Usage Report: Response Time Column Name <Timestamp> First Response Time (Ave, Min, Max, and Std) Last Response Time (Ave, Min, Max, and Std) Query Seconds (Ave, Min, Max, and Std) Delay Time (Ave, Min, Max, and Std) Query Count Row Count (Ave, Min, Max, and Std) Description This field shows the time of data capture. The contents change depending upon the time grouping selected (Date, Start of Week, Month, and so forth) Average, minimum, maximum and standard deviation of the first response time Average, minimum, maximum and standard deviation of the last response time Average, minimum, maximum and standard deviation of the query run time Average, minimum, maximum and standard deviation of query delay time The number of queries logged in the DBQL Average, minimum, maximum and standard deviation of row count Teradata Manager User Guide 161

162 Chapter 9: Analyzing Workload Trends Analyzing DBQL Usage Trends DBQL Usage Report: Resource Usage Table 57: DBQL Usage Report: Resource Usage Column Name <Timestamp> WD Name I/O Count (Ave, Min, Max, and Std) Spool Usage (bytes) (Ave, Min, Max, and Std) CPU Time (Ave, Min, Max, and Std) CPU/DISK Ratio (Ave, Min, Max, and Std) Description This field shows the time of data capture. The contents change depending upon the time grouping selected (Date, Start of Week, Month, and so forth) The name assigned to the workload Average, minimum, maximum and standard deviation of I/O count Average, minimum, maximum and standard deviation of spool usage Average, minimum, maximum and standard deviation of CPU Time Average, minimum, maximum and standard deviation of CPU time to I/O count ratio DBQL Usage Report: Parallelism Table 58: DBQL Usage Report: Parallelism Column Name <Timestamp> WD Name Concurrency Number of Steps (Ave, Min, Max, and Std) Number of Steps with Parallelism (Ave, Min, Max, and Std) Max Steps in Parallelism (Ave, Min, Max, and Std) Number of Active Amps (Ave, Min, Max, and Std) AMP/CPU Skew (%) (Ave, Min, Max, and Std) AMP/IO Skew (%) (Ave, Min, Max, and Std) Description This field shows the time of data capture. The contents change depending upon the time grouping selected (Date, Start of Week, Month, and so forth) The name assigned to the workload The average number of simultaneously running (overlapping) queries recorded during the summary interval The average, minimum, maximum, and standard deviation of the number of query steps The average, minimum, maximum, and standard deviation of the number of query steps with parallel steps The average, minimum, maximum, and standard deviation of the number of level 2 query steps executed in parallel The average, minimum, maximum, and standard deviation of the number of active AMPs The average, minimum, maximum, and standard deviation of AMP CPU skew The average, minimum, maximum, and standard deviation of AMP I/O skew 162 Teradata Manager User Guide

163 Chapter 9: Analyzing Workload Trends Analyzing DBQL Step Usage Trends Analyzing DBQL Step Usage Trends This report shows trends in DBQL Step usage. To create the report 1 Click Analyze>Trends>DBQL Step Usage. 2 Select from the following: To recall previously saved filter settings and load the filter, click Load Filter, then locate the filter file using the Name of Filter File dialog box. Click Open. Note: When a saved filter is opened, the Duration remains the same as when it was last saved. The End Date is set to the current date, and the Start Date is calculated based on the Duration and End Date. Enter the filter parameters as follows: Either enter the Start Date and End Date, or just enter the End Date and the Duration. Display a calendar tool by clicking the arrow on the date fields. Select the report grouping from the Group By list (time of day, hour, day, week or month). Select the Start Hour and End Hour. Select the days of the week to display by checking the appropriate boxes in the Day of Week area. Select the entities to display data under Show Data for. To target specific objects such as specific users, click Specific User(s), and then click to highlight names in the Specific Users list. To add an entity that is not on the list, type the name in the Type in an entry box, and click Add to List. The wildcard characters * or? can be used. For an aggregate report, select the Aggregate check box. Use the Accounts selector to choose the account category to display data. Under Report Type, select Table or Graph. Under Graph Data Fields, select the type of data to view. To save these filter settings, click Save Filter, then type in or select a name and location for the filter file using the Name of Filter File dialog box. Click Save. 3 Click OK to view the report. To change the report view 1 Right-click a name in the first column to display the shortcut menu. 2 Choose a report option: Change Filter - the DBQL Step Usage Filter dialog box appears enabling filter settings to be changed Teradata Manager User Guide 163

164 Chapter 9: Analyzing Workload Trends Viewing the DBQL Summary Histogram DBQL Step Usage Report Aggregate/De-Aggregate - aggregates or de-aggregates the report, depending on the current report status Display DBQL Usage Report- the DBQL Usage Report appears using the same filter settings Display DBQL Summary Histogram Report - the DBQL Summary Histogram Report appears using the same filter settings Table 59: DBQL Step Usage Report Column Name Date User Name Step Count I/O Count Estimated Processing Time Total Processing Time Processing Time Differential (Ave, Min, Max, and Std) Estimated Row Count Total Row Count Ave Row Count Differential (Ave, Min, Max, and Std) Description This field shows the time of data capture. The contents change depending upon the time grouping selected (Date, Start of Week, Month, and so forth) User Number of steps in user queries Number of I/Os Estimated processing time of user queries Total processing time The average, minimum, maximum, and standard deviation of the differential between Total Processing Time and Estimated Processing Time Estimated number of rows Total number of rows The average, minimum, maximum, and standard deviation of the differential between Total Row Count and Estimated Row Count Viewing the DBQL Summary Histogram This report shows trends in DBQL usage. To create the report 1 Click Analyze>Trends>DBQL Summary Histogram. 2 Select from the following: To recall previously saved filter settings and load the filter, click Load Filter, then locate the filter file using the Name of Filter File dialog box. Click Open. 164 Teradata Manager User Guide

165 Chapter 9: Analyzing Workload Trends Viewing the DBQL Summary Histogram Note: When a saved filter is opened, the Duration remains the same as when it was last saved. The End Date is set to the current date, and the Start Date is calculated based on the Duration and End Date. Enter the filter parameters as follows: Either enter the Start Date and End Date, or just enter the End Date and the Duration. Display a calendar tool by clicking the arrow on the date fields. Select the report grouping from the Group By list (time of day, hour, day, week or month). Select the Start Hour and End Hour. Select the days of the week to display by checking the appropriate boxes in the Day of Week area. Select the entities to display data under Show Data for. To target specific objects such as specific users, click Specific User(s), and then click to highlight names in the Specific Users list. To add an entity that is not on the list, type the name in the Type in an entry box, and click Add to List. The wildcard characters * or? can be used. For an aggregate report, select the Aggregate check box. Use the Accounts selector to choose the account category to display data. Under Report Type, select Table or Graph. Under Graph Data Fields, select the type of data to view. To save these filter settings, click Save Filter, then type in or select a name and location for the filter file using the Name of Filter File dialog box. Click Save. 3 Click OK to view the report. To change the report view 1 Right-click a name in the first column to display the shortcut menu. 2 Choose a report option: Change Filter - the DBQL Summary Histogram Filter dialog box appears enabling the filter settings to be changed Aggregate/De-Aggregate - aggregates or de-aggregates the report, depending on the current report status Display DBQL Usage Report - the DBQL Usage Report appears using the same filter settings Display DBQL Step Usage Report - the DBQL Step Usage Report appears using the same filter settings Teradata Manager User Guide 165

166 Chapter 9: Analyzing Workload Trends Viewing the DBQL Summary Histogram DBQL Summary Histogram Table 60: DBQL Summary Histogram Column Name Date User Name Bucket (lowhist, highhist) Query Count Query Seconds (Ave, Min, Max, and Std) I/O Count (Ave, Min, Max, and Std) CPU Time (Ave, Min, Max, and Std) CPU/DISK Ratio (Ave, Min, Max, and Std) Description This field shows the time of data capture. The contents change depending upon the time grouping selected (Date, Start of Week, Month, and so forth) The name of the user These are the time intervals that were specified for summarized queries. For example, bucket (0,5) is the interval containing queries that ran from zero to five seconds. The number of queries for the indicated intervals The average, minimum, maximum, and standard deviation of the total run time for queries that ran within the indicated intervals The average, minimum, maximum, and standard deviation of I/O count for queries that ran within indicated intervals The average, minimum, maximum, and standard deviation of CPU time for queries that ran within the indicated intervals The average, minimum, maximum, and standard deviation of the CPU Disk ration for queries that ran within the indicated intervals 166 Teradata Manager User Guide

167 CHAPTER 10 Analyzing Historical Resource Utilization Use Historical Resource Utilization reports to analyze the maximum and average usage for Logical Devices (LDVs), AMP vprocs, Nodes, and PE vprocs on your system. ByGroup reports and graphs differentiate the node processor generations (for example, 5100 vs. 5200) in a coexistence system, allowing for more meaningful data analysis for Teradata Database coexistence (mixed platform) systems. The following topics describe how to use the Historical Resource Utilization reports: Analyzing Node CPU Utilization Analyzing AMP CPU Utilization Analyzing PE CPU Utilization Analyzing Node Utilization Analyzing Disk Utilization Analyzing Network (Bynet) Utilization Analyzing Memory Utilization Analyzing Host Utilization Non-Grouped Reports History Query Filter Analyzing Node CPU Utilization The Node Utilization Report describes how the nodes are utilizing the system CPUs. To create the report or graph 1 Click Analyze>Resource History>Node CPU, and select one of the following: NODECpuAverageUse - Shows the Node CPU average utilization (average of CPUBusyH / Secs over all CPUs in centiseconds) for the specified date range NODECpuByGroup - Shows how the Nodes are utilizing the system CPUs, summarized by Node Groups, as the GroupId defines. The resulting numbers become the average across the group. NODECpuEfficiency - Shows the Node CPU Efficiency (mean CPU utilization / max CPU utilization) for each hour for the specified date range Teradata Manager User Guide 167

168 Chapter 10: Analyzing Historical Resource Utilization Analyzing Node CPU Utilization NODECpuMaximumUse - Shows the Node CPU maximum utilization (maximum of CPUBusy / Secs over all CPUs in centiseconds) for each hour for the specified date range NODECpuMinumumUse - Shows the Node CPU minimum utilization (minimum of CPUBusy / Secs over all CPUs in centiseconds) for each hour for specified date range The History Query Filter dialog box appears. 2 To display the report, do the following: a b c d Under Report Type, select Table or Graph. Enter the Start Date and End Date. For Group reports and graphs, enter the Start Hour and End Hour. Click OK. To change the report or graph view 1 To toggle between the report and graph views, click the View as Graph or View as Table link. 2 To toggle between showing and hiding options in the graph view, click the Show Options or Hide Options link on the right side of the window. 3 To change the graph options, make your new selections with the graph option check boxes, then click Update Graph. 4 To create a related report, right-click the date column to activate the shortcut menu, then select the option. Node CPU Utilization Report Note: The NodeCpuByGroup Report shows all of the fields in the following table except the last two fields. The rest of the reports only display the last two fields. Table 61: Node CPU Utilization Report Column Name Date Time GroupId WIO % Total User Serv % Total User Exec % Description The date to which the statistics apply Nominal time of the entry Identifier representing the Grouping of nodes being summarized as one row Percent of CPU time idle and waiting for I/O Percent of CPU time busy doing user service work Percent of CPU time busy doing user execution work Total Busy % This is the sum of the Total User Serv % and Total User Exec % 168 Teradata Manager User Guide

169 Chapter 10: Analyzing Historical Resource Utilization Analyzing AMP CPU Utilization Table 61: Node CPU Utilization Report (continued) Column Name Description The average, maximum, minimum, or parallel CPU use for the indicated hour on the indicated date. 00 corresponds to midnight, 01 corresponds to 1 a.m., and so on. Day The average, maximum, minimum, or parallel CPU use for all hours on the indicated date Analyzing AMP CPU Utilization The AMP CPU Utilization Report describes how the AMPs are utilizing the system CPUs. Note: Report results are normalized. To create the report or graph 1 Click Analyze>Resource History>AMP CPU, and select one of the following: AMPCpuAverageUse - Shows the average of (AMPTotalUserExec + AMPTotalUserServ) / Secs over all nodes in centiseconds for the specified date range AMPCpuByGroup - Shows how the AMPs are utilitzing the system CPUs, summarized by Node Groups as the GroupId defines. The resulting numbers become the average across the group. AMPCpuMaximumUse - Shows the maximum of (AMPTotalUserExec + AMPTotalUserServ) / Secs over all nodes in centiseconds for the specified date range AMPCpuMinimumUse - Shows the minimum of (AMPTotalUserExec + AMPTotalUserServ) / Secs over all nodes in centiseconds for the specified date range AMPCpuParallelUse - Shows AMPCpuAverageUse / AMPCpuMaximumUse over all nodes in centiseconds for the specified date range The History Query Filter dialog box appears. 2 To display the report, do the following: a b c d Under Report Type, select Table or Graph. Enter the Start Date and End Date. For Group reports and graphs, enter the Start Hour and End Hour. Click OK. Teradata Manager User Guide 169

170 Chapter 10: Analyzing Historical Resource Utilization Analyzing AMP CPU Utilization To change the report or graph view AMP CPU Utilization Report 1 To toggle between report and graph views, click the View as Graph or View as Table link. 2 To toggle between showing and hiding options in the graph view, click the Show Options or Hide Options link on the right side of the window. 3 To change the graph options, make your new selections with the graph option check boxes, then click Update Graph. 4 To create a related report, right-click the date column to activate the shortcut menu, then select the option. The AMPCpuByGroup Report shows all of the fields in the following table except the last two fields. The rest of the reports only display the last two fields. Table 62: AMP CPU Utilization Report Column Name Date Time GroupId Awt User Serv % Misc User Serv % Awt User Exec % Misc User Exec % Total User Serv % Total User Exec % Total Busy % Description Date of the entry Nominal time of the entry Node type group (for co-existence) Percent of user service CPU time for the AMP Worker Task (AWT) partition. Percent of user service CPU time for the all other partitions except Partition 0 (Non-TPA tasks). Percent of user execution CPU time for the AMP Worker Task (AWT) partition. Percent of user execution CPU time for the all other partitions except Partition 0 (Non-TPA tasks). This is the sum of the four user service columns plus the AMP Partition 0 user service. This is the sum of the four user execution columns plus the AMP Partition 0 user service. This is the sum of the Total User Serv% and Total User Exec% The average, maximum, minimum, or parallel AMP CPU use for the indicated hour on the indicated date. 00 corresponds to midnight, 01 corresponds to 1 a.m., and so on. Day The average, maximum, minimum, or parallel AMP CPU use for all hours on the indicated date 170 Teradata Manager User Guide

171 Chapter 10: Analyzing Historical Resource Utilization Analyzing PE CPU Utilization Analyzing PE CPU Utilization The PE CPU Utilization Report describes how the PEs are utilizing the system CPUs. Note: Report results are normalized. To create the report or graph 1 Click Analyze>History>PE CPU Utilization, and select one of the following: PECpuAverageUse - Shows the average of (PETotalUserExec + PETotalUserServ) / Secs over all nodes in centiseconds for the specified date range PECpuByGroup - Shows how the PEs are utilitzing the system CPUs, summarized by Node Groups as the GroupId defines. The resulting numbers become the average across the group. PECpuMaximumUse - Shows the maximum of (PETotalUserExec + PETotalUserServ) / Secs over all nodes in centiseconds for the specified date range PECpuMinimumUse - Shows the minimum of (PETotalUserExec + PETotalUserServ) / Secs over all nodes in centiseconds for the specified date range PECpuParallelUse - Shows PECpuAverageUse / PECpuMaximumUse over all nodes in centiseconds for the specified date range The History Query Filter dialog box appears. 2 To display the report or graph, do the following: a b c d Under Report Type, select Table or Graph. Enter the Start Date and End Date. For Group reports and graphs, enter the Start Hour and End Hour. Click OK. To change the report or graph view 1 To toggle between the report and graph views, click the View as Graph or View as Table link. 2 To toggle between showing and hiding options in the graph view, click the Show Options or Hide Options link on the right side of the window. 3 To change the graph options, make your new selections with the graph option check boxes, then click Update Graph. 4 To create a related report, right-click the date column to activate the shortcut menu, then select the option. Teradata Manager User Guide 171

172 Chapter 10: Analyzing Historical Resource Utilization Analyzing Node Utilization PE CPU Utilization Report The PECpuByGroup Report shows all of the fields in the following table except the last two fields. The rest of the reports only display the last two fields. Table 63: PE CPU Utilization Report Column Name Date Time GroupId Pars User Serv % Disp User Serv % Ses User Serv % Misc User Serv % Pars User Exec % Disp User Exec % Ses User Exec % Misc User Exec % Description Date of the entry Nominal time of the entry Node type group (for co-existence) Percent of user service CPU time for the Parser partition. Percent of user service CPU time for the Dispatcher partition. Percent of user service CPU time for the Session Control partition. Percent of user service CPU time for the all other partitions except Partition 0 (Non-TPA tasks). Percent of user execution CPU time for the Parser partition. Percent of user execution CPU time for the Dispatcher partition. Percent of user execution CPU time for the Session Control partition. Percent of user execution CPU time for the all other partitions except Partition 0 (Non-TPA tasks). Total User Serv % This is the sum of the four user service columns plus the PE Partition 0 user service. Total User Exec % Total Busy % This is the sum of the four user execution columns plus the PE Partition 0 user service. This is the sum of the Total User Serv% and Total User Exec% The average, maximum, minimum, or parallel PE CPU use for the indicated hour on the indicated date. 00 corresponds to midnight, 01 corresponds to 1 a.m., and so on. Day The average, maximum, minimum, or parallel PE CPU use for all hours on the indicated date Analyzing Node Utilization The Node Utilization Report shows general system information averaged across nodes by node group. 172 Teradata Manager User Guide

173 Chapter 10: Analyzing Historical Resource Utilization Analyzing Node Utilization To create the report 1 Click Analyze>Resource History>Node Utilization, and select one of the following: NODEUtilizationByGroup - Provides general system information summarized by node grouping as the GroupId defines NODEDiskActivity - Shows the shows the Logical Disk activity per NODE for the specified date range The History Query Filter dialog box appears. 2 Do the following: a b c d Under Report Type, select Table or Graph. Enter the Start Date and End Date. For Group reports and graphs, enter the Start Hour and End Hour. Click OK. Node Utilization Report To change the report or graph view 1 To toggle between the report and graph views, click the View as Graph or View as Table link. 2 To toggle between showing and hiding options in the graph view, click the Show Options or Hide Options link on the right side of the window. 3 To change the graph options, make your new selections with the graph option check boxes, then click Update Graph. 4 To create a related report, right-click the date column to activate the shortcut menu, then select the option. The NodeUtilizationByGroup Report shows all of the fields in the following table. NODEDiskActivity Report data are self explanatory. Table 64: Node Utilization Report Column Name Date Time GroupId CPU Busy WIO % Description Date the data was collected Time the data was collected Node type group (for co-existence) Percent of time the CPUs are busy, based on average CPU usage per node group Percent of time the CPUs are idle and waiting for completion of an I/O operation Teradata Manager User Guide 173

174 Chapter 10: Analyzing Historical Resource Utilization Analyzing Disk Utilization Table 64: Node Utilization Report (continued) Column Name CPU Busy + WIO % Ldv IOs /Sec P+S % of IOs Read % of IOs Ldv KB / IO LDV MB/sec Free Mem % Mem Aloc/Sec Mem Fail % Bkup Rds /Sec A+R % of IOs TPtP IOs /Sec TMlt IOs / Sec Net Rtry % Prc Blks/Sec ms/blk Cache Hit Ratio Description Percent of time the CPUs were busy doing work + Percent of time spent waiting for I/O Average number of logical device (disk) reads and writes per second per node group Percent of logical device (disk) reads and writes that are for paging or swapping purposes. Percent of logical device (disk) reads and writes that are reads Average size of a logical device (disk) read or write Logical device I/O in MB per second Percent of memory that is unused Average number of memory allocations per second per node group Percent of memory allocation attempts that failed Number of backup segments read by a node that are sent from a virtual processor on another node Percent of logical device reads and writes that are disk segment reads and writes Total point-to-point net reads and writes per second, per node group Total multicast (broadcast or merge) net reads and writes per second, per node group Percent of transmission attempts that resulted in retries Number of times per second, per node, that precesses other than message and time waits are blocked Average time, in milliseconds, spent waiting for a blocked process other than message and timer waits Logical IOs / Physical IOs Analyzing Disk Utilization The Disk Utilization Report describes general logical disk utilization. 174 Teradata Manager User Guide

175 Chapter 10: Analyzing Historical Resource Utilization Analyzing Disk Utilization To create the report 1 Click Analyze>Resource History>Disk Utilization, and select one of the following: DiskActivity- Shows Logical Disk activity at the controller level for the specified date range DiskAverageUse - Shows the average of ScntlReadRespTot / (ScntlReads + ScntlWrites) over all SCSI controllers in milliseconds for each hour for the specified date range DiskByGroup - Provides general logical disk information, summarizing statistics by node grouping. Most of the resulting numbers become the average across the group. The exception is the Max number of concurrent requests, which reports the maximum value for any logical disk in the group. DiskMinimumUse - Shows the minimum of ScntlReadRespTot / (ScntlReads + ScntlWrites) over all SCSI controllers in milliseconds for each hour for the specified date range DiskMaximumUse - Shows the maximum of ScntlReadRespTot / (ScntlReads + ScntlWrites) over all SCSI controllers in milliseconds for the specified date range DiskParallelUse - Shows DiskAverageUse / DiskMaximumUse over all SCSI controllers in milliseconds for the specified date range The History Query Filter dialog box appears. 2 Do the following: a b c d Under Report Type, select Table or Graph. Enter the Start Date and End Date. For Group reports and graphs, enter the Start Hour and End Hour. Click OK. Disk Utilization Report To change the report or graph view 1 To toggle between the report and graph views, click the View as Graph or View as Table link. 2 To toggle between showing and hiding options in the graph view, click the Show Options or Hide Options link on the right side of the window. 3 To change the graph options, make your new selections with the graph option check boxes, then click Update Graph. 4 To create a related report, right-click the date column to activate the shortcut menu, then select the option. The DiskByGroup Report shows all of the fields in the following table except the last two fields. The rest of the reports only display the last two fields. DiskActivity Report data are self explanatory. Teradata Manager User Guide 175

176 Chapter 10: Analyzing Historical Resource Utilization Analyzing Network (Bynet) Utilization Table 65: Disk Utilization Report Column Name Date Time GroupId Reads/Sec Writes/Sec Rd KB / I/O Wt KB / I/O Avg I/O Resp Max Concur Rqsts Out Rqst Time % Description Date of the entry Nominal time of the entry Node type group (for co-existence) Average number of logical device reads per second Average number of logical device writes per second Average kilobytes read from the logical device per I/O Average kilobytes written to the logical device per I/O Average I/O response time for both reads and writes. Maximum number of concurrent requests Average percent of time there was any outstanding request The average, maximum, minimum, or parallel disk use for the indicated hour on the indicated date. 00 corresponds to midnight, 01 corresponds to 1 a.m., and so on. Day The average, maximum, minimum, or parallel disk use for all hours on the indicated date Analyzing Network (Bynet) Utilization The Network Utilization Report shows information about network traffic on the nodes summarized by Node Groups as the GroupId defines. The resulting numbers become the average across the group. To create the report or graph 1 Click Analyze>Resource History>Bynet Utilization. The History Query Filter dialog box appears. 2 Do the following: a Under Report Type, select Table or Graph. b Enter the Start Date and End Date. c Enter the Start Hour and End Hour. d Click OK. 176 Teradata Manager User Guide

177 Chapter 10: Analyzing Historical Resource Utilization Analyzing Memory Utilization To change the report or graph view Network Utilization Report 1 To toggle between the report and graph views, click the View as Graph or View as Table link. 2 To toggle between showing and hiding options in the graph view, click the Show Options or Hide Options link on the right side of the window. 3 To change the graph options, make your new selections with the graph option check boxes, then click Update Graph. Table 66: Network Utilization Report Column Name Date Time GroupId Description Date of the entry Nominal time of the entry Node type group (for co-existence) % Retries Percent of total net circuit attempts that caused software back-offs (BNS service blocked occurrences) Reads/Sec Writes/Sec IOs/Sec KB/IO Average number of net reads per second Average number of net writes per second Average number of net read and writes per second Average kilobytes per net read or write % PtP Percent of total net IOs that are point-to-point reads and writes. % Brd Percent of total net IOs that are broadcast reads and writes. Analyzing Memory Utilization The Memory Utilization Report shows memory allocation, aging, paging, and swapping activities on the nodes summarized by Node Groups as the GroupId defines. The resulting numbers become the average across the group. To create the report or graph 1 Click Analyze>Resource History>Memory Utilization. The History Query Filter dialog box appears. 2 Do the following: a Under Report Type, select Table or Graph. Teradata Manager User Guide 177

178 Chapter 10: Analyzing Historical Resource Utilization Analyzing Memory Utilization b c d Enter the Start Date and End Date. Enter the Start Hour and End Hour. Click OK. To change the report or graph view Memory Utilization Report 1 To toggle between the report and graph views, click the View as Graph or View as Table link. 2 To toggle between showing and hiding options in the graph view, click the Show Options or Hide Options link on the right side of the window. 3 To change the graph options, make your new selections with the graph option check boxes, then click Update Graph. Table 67: Memory Utilization Report Column Name Date Time GroupId Description Date of the entry Nominal time of the entry Node type group (for co-existence) % Mem Free Percent of memory that is unused Text Alocs/Sec VPR Alocs/Sec KB/VPR Aloc Aloc Fail % Ages/Sec Average number of text page allocations per second. Text pages are allocations of memory for code that is not associated with system-level overhead tasks. Average number of vproc-specific page and segment allocations per second Average kilobytes per vproc-specific page and segment allocation on a node Percent of memory allocation attempts that failed Average number of times memory pages were aged out per second # Proc Swap Current number of processes that are swapped out. Pg Drps/Sec Pg Rds/Sec Pg Wrts/Sec Average number of text pages dropped from memory per second. Page drops are text pages that are dropped from memory to increase the amount of available memory. Average number of text pages read from disk per second. Page reads include both memory text pages and task context pages, such as scratch, stack, and so forth Average number of memory pages written to disk per second. Page writes include only task context pages. 178 Teradata Manager User Guide

179 Chapter 10: Analyzing Historical Resource Utilization Analyzing Host Utilization Table 67: Memory Utilization Report (continued) Column Name Swp Drps/Sec Swp Rds/Sec KB/Swp Drp KB/Swp Rd P+S Drps/Sec P+S Rds/Sec P+S Wrts/Sec P+S IO % Description Average number of disk segments dropped from memory per second. Swap drops include all disk segments dropped from memory because their ancestor processes were swapped out. Average number of disk segments reread back into memory, after being swapped out, per second. Swap reads include all reread disk segments that had been previously dropped from memory because their ancestor processes were swapped out. Average size in kilobytes of disk segments dropped from memory because their ancestor processes were swapped out. Average size in kilobytes of reread disk segments that had been previously dropped from memory because their ancestor processes were swapped out. Average number of paged, swapped page, or segment drops per second. This statistic includes both the memory text pages (Pg Drps/Sec), and the disk segments (Swp Drps/Sec), that were dropped. Average number of paged, swapped page, or segment reads per second. Includes both the memory text pages and task context pages (Pg Rds/ Sec), and the disk segments (Swp Rds/Sec), reread back into memory after being swapped out. Average number of paged, swapped page, or segment writes per second. Percent of logical device inputs and outputs that are paging or swapping inputs and outputs. Analyzing Host Utilization This report provides general communication link information summarizing by Node Groups as the GroupId defines. The HstType is used in the GroupBy statement so that IBM Host channels and Network links can be differentiated in the output rows. To create the report 1 Click Analyze>Resource History>Host Utilization. The History Query Filter dialog box appears. 2 Do the following: a Under Report Type, select Table or Graph. b Enter the Start Date and End Date. c Enter the Start Hour and End Hour. d Click OK. Teradata Manager User Guide 179

180 Chapter 10: Analyzing Historical Resource Utilization Analyzing Host Utilization Host Utilization Report To change the report or graph view 1 To toggle between the report and graph views, click the View as Graph or View as Table link. 2 To toggle between showing and hiding options in the graph view, click the Show Options or Hide Options link on the right side of the window. 3 To change the graph options, make your new selections with the graph option check boxes, then click Update Graph. Table 68: Host Utilization Report Column Name Date Time GroupId HostType KBs Read/Sec KBs Write/Sec Blks Read/Sec Blks Write/Sec Blks Read Fail% Blks Write Fail% KBs/Blk Read KBs/Blk Write Msgs/Blk Read Msgs/Blk Write AvgReqQLen MaxReqQLen Description Date of the entry Nominal time of the entry Node type group (for co-existence) Type of connection: NETWORK for LAN connected hosts, IBMMUX for channel connected hosts. Average number of kilobytes read per second Average number of kilobytes written per second Average number of blocks read per second Average number of blocks written per second Percentage of block read attempts that failed Percentage of block write attempts that failed Average number of kilobytes per block read Average number of kilobytes per block written Average number of messages per block read Average number of messages per block written Average number of messages queued for output to the host Max number of messages queued for output to the host 180 Teradata Manager User Guide

181 Chapter 10: Analyzing Historical Resource Utilization Non-Grouped Reports Non-Grouped Reports Non-Grouped Report To change the report or graph view 1 To toggle between the report and graph views, click the View as Graph or View as Table link. 2 To toggle between showing and hiding options in the graph view, click the Show Options or Hide Options link on the right side of the window. 3 To change the graph options, make your new selections with the graph option check boxes, then click Update Graph. 4 To create a related report, right-click the date column to activate the shortcut menu, then select the option. Table 69: Non-Grouped Report Column Name Description The average, maximum, minimum, parallel for the indicated hour on the indicated date. 00 corresponds to midnight, 01 corresponds to 1 a.m., and so on. Day The average, maximum, minimum, parallel for all hours on the indicated date History Query Filter The History Query Filter dialog box displays after selecting a report. To display the report 1 Under Report Type, select Table or Graph. 2 Enter the Start Date and End Date. 3 For Group reports and graphs, enter the Start Hour and End Hour. 4 Click OK. Teradata Manager User Guide 181

182 Chapter 10: Analyzing Historical Resource Utilization History Query Filter 182 Teradata Manager User Guide

183 CHAPTER 11 Investigating Disk Space Utilization Teradata Manager offers an extensive set of reports for monitoring Teradata Database disk space usage. It also allows the reallocation of permanent disk space from one database to another, and contains direct support for changing the database hierarchy. Note: To use all of these functions, be sure to have CREATE DATABASE and DROP DATABASE rights to run the Ferret utility, as well as the following privileges on the associated database: The following topics provide instructions on changing and viewing disk space utilization: Reallocating Disk Space Changing Options for Space Usage Reports Transferring Database Ownership Viewing Database Space Usage Viewing Space Usage By Table Viewing Table Space Usage by Vproc Viewing the CREATE TABLE Statement Viewing All Objects In a Database Viewing Hierarchical Space Usage Viewing Overall Space Usage by Vproc Viewing Cylinder Space By Vproc Reallocating Disk Space Follow this procedure to move permanent disk space from one database to another. To move permanent space using drag and drop in the Hierarchy Report 1 From the Teradata Manager menu bar, click Investigate>Space Usage>Hierarchy. 2 Press and hold Ctrl, then click and hold the database or user to move space from, drag it to the database or user to move space to, and then release the mouse button. Teradata Manager User Guide 183

184 Chapter 11: Investigating Disk Space Utilization Reallocating Disk Space To move permanent space using the Move Space command 1 From the Teradata Manager menu bar, click Administer>Move Space. 2 Fill in the fields as described in Table Click OK. Move Space Fields and Controls Table 70: Move Space Fields and Controls Field Amount to Move From Permanent Space Allocation Maximum Current Unused To Permanent Space Allocation Maximum Current Unused Description Enter the amount of disk space to reallocate in bytes, kilobytes, megabytes, or gigabytes. As an alternative to selecting the buttons, type b, k, m, or g in the box after entering the amount. The appropriate button is automatically selected. Select the database the space is to be moved from Shows the maximum permanent disk space for the database specified in the From field Shows the amount of current permanent disk space for the database specified in the From field Shows the amount of unused permanent disk space for the database specified in the From field Select the database the space is to be moved to Shows the maximum permanent disk space for the database specified in the To field Shows the amount of current permanent disk space for the database specified in the To field Shows the amount of unused permanent disk space for the database specified in the To field 184 Teradata Manager User Guide

185 Chapter 11: Investigating Disk Space Utilization Changing Options for Space Usage Reports Changing Options for Space Usage Reports Follow this procedure to change options for the Space Usage reports. To change options for Space Usage reports 1 From the Teradata Manager menu bar, click Investigate>Space Usage>Options. 2 Fill in the fields as follows: Show space in - Bytes, Kilobytes (KB), Megabytes (MB), Gigabytes (GB) - select to set the report to show space in the specified unit. Define KB, MB, GB as multiples of 1000, instead of select this check box to express values as multiples of Clear this check box to express values as multiples of Hide Hierarchy elements whose max perm is 0 - select this check box to hide users on the Hierarchy Report that have been defined with 0 bytes of permanent disk space. 3 Click OK. The changes take effect when the reports are opened again. Transferring Database Ownership Follow this procedure to transfer the ownership of a database to another user. To transfer ownership using drag and drop in the Hierarchy Report 1 From the Teradata Manager menu bar, click Investigate>Space Usage>Hierarchy. 2 Click and hold the database or user to transfer, drag it to the database or user to transfer ownership to, and then release the mouse button. To transfer database ownership using the Move Database command 1 From the Teradata Manager menu bar, click Administer>Move Database. 2 Fill in the fields as follows: Give - specify the source database by either entering the database name in the field or selecting it from the Give list. To - specify the recipient for the operation by either entering the recipient name in the field or selecting it from the To list. 3 Click OK. Teradata Manager User Guide 185

186 Chapter 11: Investigating Disk Space Utilization Viewing Database Space Usage Viewing Database Space Usage To view database space usage Space By Database Report 1 From the Teradata Manager menu bar, click Investigate>Space Usage>Space by Database. 2 From this report, right-click a name in the Database Name column to display the shortcut menu. 3 Click one of the following: Table Space - reports space usage by table. For more information, see Viewing Space Usage By Table on page 187. Help Database - all the objects in the database appear. For more information, see Viewing All Objects In a Database on page 189. Table 71: Space By Database Report Data Label Database Name Account Name Max Perm Peak Perm Peak Perm % Current Perm Current Perm % Skew Unused Perm Unused Perm% Max Spool Description Name of the database Account Id associated with the database Total amount of permanent disk space, in bytes, for the database Highest amount of permanent disk space the database uses, in bytes Highest percentage of the maximum amount of disk space (MaxPerm) the database uses Amount of permanent disk space, in bytes, that the database is currently using Percentage of the maximum amount of disk space (MaxPerm) that the database is currently using A measure of data distribution across the AMPs for the selected database. A 'perfectly' distributed database (same amount of data on each AMP) has a Skew of 0. A database which has all the data on one AMP has a Skew of 100. Amount of permanent disk space, in bytes, that the database is currently not using Percentage of the maximum amount of disk space (MaxPerm) that the database is currently not using Total amount of temporary spool space, in bytes, for the database 186 Teradata Manager User Guide

187 Chapter 11: Investigating Disk Space Utilization Viewing Space Usage By Table Table 71: Space By Database Report (continued) Data Label Peak Spool Peak Spool % Max Temp Peak Temp Peak Temp % Current Temp Current Temp % Description Highest amount of temporary spool space the database uses, in bytes Highest percentage of the total amount of temporary spool space (MaxSpool) the database uses Amount of temporary space allocated to the database Highest amount of temporary space the database uses Peak Temp expressed as a percentage of Max Temp Amount of temporary space currently in use for the database Current Temp expressed as a percentage of Max Temp Viewing Space Usage By Table To view space usage by table 1 From the Teradata Manager menu bar, click Investigate>Space Usage>Space by Database. 2 From the displayed report, right-click a name in the Database Name column to display the shortcut menu. 3 Select Table Space. The Table Space in database name dialog box appears. 4 Fill in the fields as follows: Display space usage for all tables in this database - select this check box to display all tables in the database with no filtering Clearing the above check box activates the following boxes: Current Perm >= - to view only tables equal to or above a specified current perm amount, enter that amount here, in megabytes Skew >= - to view only tables equal to or above a specified skew amount, enter that amount here, in percent 5 Click OK. 6 From this report, right-click a name in the Table Name column to display the shortcut menu. 7 Click one of the following: Space by Vproc- reports table space usage by vproc. For more information, see Viewing Table Space Usage by Vproc on page 188. Show Table - the CREATE TABLE statement (DDL) appears. For more information, see Viewing the CREATE TABLE Statement on page 189. Teradata Manager User Guide 187

188 Chapter 11: Investigating Disk Space Utilization Viewing Table Space Usage by Vproc Table Space Report Table 72: Table Space Report Data Label Table Name Current Perm Peak Perm Skew Description Name of each table in the database Amount of permanent disk space, in megabytes, currently in use by each table Highest amount of permanent disk space, in megabytes, used by each table A measure of data distribution across the AMPs for the selected table. A 'perfectly' distributed table (same amount of data on each AMP) has a Skew of 0. A table which has all the data on one AMP has a Skew of 100. Viewing Table Space Usage by Vproc To view table space usage by Vproc 1 From the Teradata Manager menu bar, click Investigate>Space Usage>Space by Database. 2 From the displayed report, right-click the name in the Database Name column to display the shortcut menu. 3 Click Table Space. The Table Space in database name dialog box appears. 4 Click OK. 5 From the displayed report, right-click the name in the Table Name column to display the shortcut menu. 6 Click Space by Vproc. The Space by Vproc for table name dialog box appears. 7 Do one of the following: Display space on all vprocs for the selected table - select this check box to display all vprocs with no filtering Clearing the above check box activates the following fields: Deviation >= - to view only vprocs with a deviation equal to or above a specified amount, enter that amount here, in percent Absolute Value >= - to see vprocs with negative deviations as well as positive ones, select this check box 8 Click OK to display the report. 188 Teradata Manager User Guide

189 Chapter 11: Investigating Disk Space Utilization Viewing the CREATE TABLE Statement Table Space by Vproc Report Table 73: Table Space By Vproc Report Data Label Table Name Current Perm Peak Perm Skew Description Name of each table in the database Amount of permanent disk space, in megabytes, currently in use by each table Highest amount of permanent disk space, in megabytes, used by each table A measure of data distribution across the AMPs for the selected table. A 'perfectly' distributed table (same amount of data on each AMP) has a Skew of 0. A table which has all the data on one AMP has a Skew of 100. Viewing the CREATE TABLE Statement Follow this procedure to view the CREATE TABLE statement (DDL) for the selected table. To view the CREATE TABLE statement 1 From the Teradata Manager menu bar, click Investigate>Space Usage>Space by Database. 2 From the displayed report, right-click the name in the Database Name column to display the shortcut menu. 3 Click Table Space. 4 From the displayed report, right-click the name in the Table Name a column to display the shortcut menu. 5 Click Show Table. Viewing All Objects In a Database To view all objects in a database 1 From the Teradata Manager menu bar, click Investigate>Space Usage>Space by Database. 2 From the displayed report, right-click the name in the Database Name column to display the shortcut menu. 3 Click Help Database. Teradata Manager User Guide 189

190 Chapter 11: Investigating Disk Space Utilization Viewing Hierarchical Space Usage Help Database Report Table 74: Help Database Report Data Label TVM name Kind Fallback Owner Comment Description Name of each table, view, and macro in the database Type of object where: A = Aggregate function B = Combined aggregate and ordered analytical function E = External Stored Procedure F = Standard function G = Trigger H = Instance on Constructor Method I = Join Index J = Journal M = Macro N = Hash Index P = SQL Procedure Q = Trigger R = Table function S = Ordered analytical function T = Table U = User-defined data type V = View X = Authorization Protection value, where: N = None F = Fallback Name of the owner of the database element Comment information, if available Viewing Hierarchical Space Usage The total hierarchical permanent space and the current hierarchical space in use can be shown for each database. 190 Teradata Manager User Guide

191 Chapter 11: Investigating Disk Space Utilization Viewing Overall Space Usage by Vproc To view hierarchical space usage From the Teradata Manager menu bar, click Investigate>Space Usage>Hierarchy. To transfer ownership using drag and drop in the Hierarchy Report Click and hold on the database or user to transfer, drag it to the database or user to transfer ownership to, and then release the mouse button. Hierarchy Report To move permanent space using drag and drop in the Hierarchy Report Press and hold Ctrl, then click and hold on the database or user to move space from, drag it to the database or user to move space to, and then release the mouse button. Table 75: Hierarchy Report Data Label HSpace In Use Description Total hierarchical permanent space available for each database Total hierarchical permanent space in use by each database % in Use The percentage of the maximum amount of disk space (MaxPerm) that is currently in use (Current Perm) Viewing Overall Space Usage by Vproc Space By Vproc Report To view overall space usage by Vproc From the Teradata Manager menu bar, click Investigate>Space Usage>Space by Vproc. Table 76: Space By Vproc Report Data Label Max Perm Current Perm Description Maximum amount of permanent disk space, by processor Amount of permanent disk space that is currently in use, by processor % in Use The percentage of the maximum amount of disk space (MaxPerm) that is currently in use (Current Perm) Teradata Manager User Guide 191

192 Chapter 11: Investigating Disk Space Utilization Viewing Cylinder Space By Vproc Table 76: Space By Vproc Report (continued) Data Label Available Perm Skew % Description Amount of permanent disk space that is currently not in use, by processor (Available Perm = Max Perm - Current Perm) Compares the workload of each vproc to the system wide vproc workload average. When the workload is evenly distributed among all vprocs, the Skew is 0. The farther the number is from 0 the more unevenly distributed the workload is. Skew may be displayed as a positive or negative number. Viewing Cylinder Space By Vproc Follow this procedure to show the total amount of cylinder space that is currently in use and available, listed by processor. To view cylinder space by Vproc From the Teradata Manager menu bar, click Investigate>Space Usage>Cylinders by Vproc. Cylinder Space by Vproc Report Table 77: Cylinder Space By Vproc Report Data Label Total Avail Cyls Perm Data Cyls: Av Util per Cyl Perm Data Cyls: % of Total Avail Cyls Wal Cyls: % of Total Avail Cyls Wal Cyls: # Cyls Depot Cyls: Av Util per Cyl Depot Cyls: # Cyls Perm Data Cyls: # Cyls Spool Cyls: Av Util per Cyl Spool Cyls: % of Total Avail Cyls Spool Cyls: # Cyls Description Total number of cylinders available to each processor Average utilization, per cylinder, of permanent data cylinders Percentage of total available cylinders being used as permanent data cylinders Percentage of total available cylinders being used by Write Ahead Logging Total number of Write Ahead Logging cylinders Average utilization, per cylinder, of depot cylinders Total number of depot cylinders Total number of permanent data cylinders Average utilization, per cylinder, of spool cylinders Percentage of total available cylinders being used as spool cylinders Total number of spool cylinders 192 Teradata Manager User Guide

193 Chapter 11: Investigating Disk Space Utilization Viewing Cylinder Space By Vproc Table 77: Cylinder Space By Vproc Report (continued) Data Label Temp Cyls: Av Util per Cyl Temp Cyls: % of Total Avail Cyls Temp Cyls: # Cyls Jrnl Cyls: Av Util per Cyl Jrnl Cyls: % of Total Avail Cyls Jrnl Cyls: # Cyls Bad Cyls: % of Total Avail Cyls Bad Cyls: # Cyls Free Cyls: % of Total Avail Cyls Free Cyls: # Cyls Description Average utilization of cylinders allocated for temporary space Of all available cylinders, percentage that are allocated for temporary space Total number of cylinders used for temp space Average utilization, per cylinder, of journal cylinders Percentage of total available cylinders being used as journal cylinders Total number of journal cylinders Percentage of total available cylinders that have been identified as bad cylinders Total number of bad cylinders Percentage of total available cylinders that are free Total number of free cylinders Teradata Manager User Guide 193

194 Chapter 11: Investigating Disk Space Utilization Viewing Cylinder Space By Vproc 194 Teradata Manager User Guide

195 CHAPTER 12 Investigating System Behavior Teradata Manager provides several different ways to investigate system behavior. The following topics provide information on how to view behavior of the system. Investigating the Error Log Investigating Logon Activity Investigating Lock Contentions Investigating System Performance Parameters Investigating the Error Log Error Log Analyzer (ELA) allows viewing of the error log system tables on the Teradata Database. View the log tables by: category message screen reports The Teradata Database monitors software error events and logs error messages into the dbc.software_event_log. The ELA macros included with Teradata Manager include AllRestarts, BynetEvents, DiskEvents, EventCount, LogHistory, MemEvents, MiniCylPacks, PackDisk and RestartLogonEvents. For more information, see Error Log Analyzer on page 290. To start Error Log Analyzer From the Teradata Manager menu bar, click Investigate>Error Log. Instructions for using this program are in the Error Log Analyzer online help. Teradata Manager User Guide 195

196 Chapter 12: Investigating System Behavior Investigating Logon Activity Investigating Logon Activity LogOnOff Usage presents daily, weekly, and monthly logon statistics based on information in the DBC LOGONOFF view on the associated Teradata Database. Three macros are included with LogOnOff Usage to help retrieve this information: Table 78: Logon Activity Reports Report Name DailyReport WeeklyReport MonthlyReport Description The number of logons across several days, either in 10 minute or one hour intervals, grouped by time interval and user. A summary of all logons for the last ten weeks, grouped by week. A summary of all logons over the last month (from 30 days previous to the current date) grouped by date. For more information, see LogOnOff Usage on page 292. To start LogOnOff Usage From the Teradata Manager menu bar, click Investigate>Logon/Logoff History. Instructions for using this program are in the LogOnOff Usage online help. Investigating Lock Contentions The Teradata Manager Locking Logger application is an interface to the Locking Logger console utility of the Teradata Database. When Locking Logger is enabled, the Teradata Database maintains ongoing logs of: Transaction Identifiers Session Identifiers Lock Object Identifier Lock Levels associated with executing SQL statements which have been delayed because of database lock contention. For more information, see Locking Logger on page 291. To start Locking Logger From the Teradata Manager menu bar, click Investigate>Locking Logger. Instructions for using this program are in the Locking Logger online help. 196 Teradata Manager User Guide

197 Chapter 12: Investigating System Behavior Investigating System Performance Parameters Investigating System Performance Parameters The Alert Viewer provides a single view point on the overall system performance for one, or multiple, Teradata Database systems. Easily drill down from an overall picture to identify the problem area, possibly preventing a hazardous situation. The Alert Viewer also provides a graphing function, that displays a graph for any data point value by simply clicking on it. For more information on the program, see Alert Viewer on page 288. For instructions on getting started with the Alerts System, see Chapter 15: Using Alerts to Monitor Your System. To start Alert Viewer From the Teradata Manager menu bar, click Investigate>Alert Viewer. Instructions for using this program are in the Alert Viewer online help. Teradata Manager User Guide 197

198 Chapter 12: Investigating System Behavior Investigating System Performance Parameters 198 Teradata Manager User Guide

199 CHAPTER 13 Investigating the Audit Log Each row in the Audit Log reports indicates the results of a privilege check. Whether a privilege check is logged depends on the presence and the criteria of an access logging rule. Define your report criteria by setting Audit Log Filter parameters before running an audit report. The following topics provide instructions on investigating the audit log: Before Creating Audit Reports Setting the Audit Log Filter to Narrow Your Results Auditing Database and User Activity Auditing Table, View and Macro Activity Auditing Grant and Revoke Activity Auditing Index Activity Auditing Checkpoint, Dump and Restore Activity Auditing Denials Creating an Audit Summary Report Creating a Custom Audit Report Before Creating Audit Reports Before an audit report can be created, your system must be set up to create an access log. To set up your system to create an access log 1 Run the script DIPACC DBCSQL. This can be done by your system administrator. 2 Enable access logging on your system. One way to enable access logging is by using Teradata Administrator. (Start Teradata Administrator, and then from the Teradata Administrator menu bar, click Tools>Access Logging.) Teradata Manager User Guide 199

200 Chapter 13: Investigating the Audit Log Setting the Audit Log Filter to Narrow Your Results Setting the Audit Log Filter to Narrow Your Results Define your report criteria by setting Audit Log Filter parameters before running an audit report. All entries are optional. To set the Audit Log filter 1 Click Investigate>Audit Log>Filter. 2 To audit privilege checks that: Occurred within a certain time frame, enter the Access Log Date/Time parameters Were caused by sessions logged on within a certain time frame, enter the Session Logon Date options Belong to a specific user, enter the User to be audited Belong to a specific account, enter the Account to be audited Resulted in specific access outcomes, select one of the following: Both - Shows privilege checks that resulted in both granted and denied access Grant - Shows only privilege checks that resulted in granted access Deny - Shows only privilege checks that resulted in denied access Occurred on access to specific objects, select the Database/Table/Column to be audited. 3 Click OK to save your filter settings. Auditing Database and User Activity Use this report to view database access. To create the report 1 [Optional] Define the scope of your report by first setting the filter as described in Setting the Audit Log Filter to Narrow Your Results on page Click Investigate>Audit Log>Database/User. Audit Database and Users Activity Report Table 79: Audit Database and Users Activity Report Column Name Log Date Description The date of the access 200 Teradata Manager User Guide

201 Chapter 13: Investigating the Audit Log Auditing Table, View and Macro Activity Table 79: Audit Database and Users Activity Report (continued) Column Name Log Time User Name Access Type Result Database Name Description The time of the access The user initiating the access The type of access Whether or not the access was granted The name of the database that was accessed Auditing Table, View and Macro Activity Use this report to view access of Tables, Views and Macros. To create the report 1 Optionally define the scope of your report by first setting the filter as described in Setting the Audit Log Filter to Narrow Your Results on page Click Investigate>Audit Log>Table/View/Macro. Audit Table, View, Macro Activity Report Table 80: Audit Table, View, Macro Activity Report Column Name Log Date Log Time User Name Access Type Result Database Name Table, View, Macro Name Description The date of the access The time of the access The user initiating the access The type of access Whether or not the access was granted The name of the database that was accessed The name of the Table, View or Macro that was accessed Teradata Manager User Guide 201

202 Chapter 13: Investigating the Audit Log Auditing Grant and Revoke Activity Auditing Grant and Revoke Activity Use this report to view grant and revoke activity on the database. To create the report 1 Optionally define the scope of your report by first setting the filter as described in Setting the Audit Log Filter to Narrow Your Results on page Click Investigate>Audit Log>Grants. Audit Grant and Revoke Activity Report Table 81: Audit Grant and Revoke Activity Report Column Name Log Date Log Time User Name Result Database Name Table, View, Macro Name Description The date of the access The time of the access The user initiating the access Whether or not the access was granted The name of the database that was accessed The name of the Table, View or Macro that was accessed Auditing Index Activity Use this report to view access of indexes. To create the report 1 [Optional] Define the scope of your report by first setting the filter as described in Setting the Audit Log Filter to Narrow Your Results on page Click Investigate>Audit Log>Indexes. Audit Index Activity Report Table 82: Audit Index Activity Report Column Name Log Date Description The date of the access 202 Teradata Manager User Guide

203 Chapter 13: Investigating the Audit Log Auditing Checkpoint, Dump and Restore Activity Table 82: Audit Index Activity Report (continued) Column Name Log Time User Name Result Database Name Table, View, Macro Name Description The time of the access The user initiating the access Whether or not the access was granted The name of the database that was accessed The name of the Table, View or Macro that was accessed Auditing Checkpoint, Dump and Restore Activity Use this report to audit database maintenance activities. To create the report 1 [Optional] Define the scope of your report by first setting the filter as described in Setting the Audit Log Filter to Narrow Your Results on page Click Investigate>Audit Log>Maintenance. Audit Checkpoint, Dump and Restore Activity Report Table 83: Audit Checkpoint, Dump and Restore Activity Report Column Name Log Date Log Time User Name Access Type Result Database Name Table, View, Macro Name Description The date of the access The time of the access The user initiating the access The type of access Whether or not the access was granted The name of the database that was accessed The name of the Table, View or Macro that was accessed Teradata Manager User Guide 203

204 Chapter 13: Investigating the Audit Log Auditing Denials Auditing Denials This report shows all the access denials that occur on your system. Audit Denials Report To create the report 1 [Optional] Define the scope of your report by first setting the filter as described in Setting the Audit Log Filter to Narrow Your Results on page Click Investigate>Audit Log>Denials. Table 84: Audit Denials Report Column Name Log Date Log Time User Name Access Type Result Database Name Table, View, Macro Name Statement Text Description The date of the access The time of the access The user initiating the access The type of access Whether or not the access was granted The name of the database that was accessed The name of the Table, View or Macro that was accessed The query text Creating an Audit Summary Report Use this report to summarize all types of database access attempts. To create the report 1 Click Investigate>Audit Log>Summary. 2 Select the types of access to summarize in the report: Check All to summarize all types of access Checking the category names automatically checks all the boxes for that category (DB/ User, Objects, Access, Maintenance, Other). Clear any options. Select options one by one 3 Click OK to view the report. 204 Teradata Manager User Guide

205 Chapter 13: Investigating the Audit Log Creating a Custom Audit Report Audit Summary Report Table 85: Audit Summary Report Column Name Database Name <the type of access> Description The name of the database that was accessed The number of times that access was attempted Creating a Custom Audit Report Use this procedure to create a custom report of attempts to access the database. To create the report 1 Click Investigate>Audit Log>Custom. 2 Select the types of access to be included in the report by doing the following: Check All to include all types of access Check the category names to automatically check all the boxes for that category (DB/ User, Objects, Access, Maintenance, Other). Clear any options. Check the options one by one 3 Click Next. 4 Choose the columns to display in the report by moving the column names to the Selected list. To do this, highlight the column name in the Available list, then click Add->. 5 Click Next. 6 Set the order of the columns on the report by moving the column names up or down in the Left to Right Column Order list. To do this, highlight the column name, then click Up or Down, depending on the direction, to move the column. 7 Set the sort order of the report by moving the column names up or down in the Row Sort Order (Order By) list. To do this, highlight the column name, then click Up or Down, depending on the direction, to move the column. 8 Click OK to view the report. Teradata Manager User Guide 205

206 Chapter 13: Investigating the Audit Log Creating a Custom Audit Report 206 Teradata Manager User Guide

207 CHAPTER 14 Using Teradata Priority Scheduler Administrator The Teradata Priority Scheduler Administrator (Teradata PSA) is a resource management tool that provides an easy-to-use graphical interface to define Priority Definition Sets and generate schmon scrips to implement these sets. Read the following topics to learn how to use Teradata PSA: Introduction Step 1 - Starting Teradata PSA Step 2 - Defining PD Set and Resource Partition Parameters Step 3 - Defining Performance Group Parameters Step 4 - Defining Allocation Group Parameters Adding or Deleting an Allocation Group Viewing a Priority Definition Set Description Viewing the Schmon Commands Used to Create a Priority Definition Set Saving and Deleting Priority Definition Set Information Creating a New Priority Definition Set Viewing Performance Data Viewing Session Information Viewing a Session Report Scheduling a Priority Definition Set Comparing Relative Weights of Allocation Groups or Resource Partitions Comparing Relative CPU Use of an Allocation Group or Resource Partition Changing the Operating System Type Defining Advanced PD Set and Resource Partition Parameters Configuring the Priority Scheduler Administrator Display Priority Scheduler Administrator Command Line Parameters Teradata Manager User Guide 207

208 Chapter 14: Using Teradata Priority Scheduler Administrator Introduction Introduction Teradata PSA provides tools to monitor and control the Priority Scheduler environment, allowing for prioritization of different types of work in a mixed workload. Before using Teradata PSA, read the Priority Scheduler chapter of the Teradata Database Utilities - Volume 2 documentation. It includes important information about Priority Scheduler components including resource partitions, performance groups, performance periods, and allocation groups. The Priority Scheduler controls the allocation and consumption of computer resources available to the Teradata Database based on the following: A session-related priority designation from the account string The system-level Priority Definition Set that is defined; a Priority Definition Set is the collection of data, including the resource partition, performance group, allocation group, performance period type, and other definitions that control how the Priority Scheduler manages and schedules session execution. Use these capabilities by: Giving a low priority to applications that consume very large amounts of resources, such as data mining, so they have less influence on the performance of other active work. Giving a high priority to short-running, tactical queries, so they complete quickly. Dividing the resources based on sub-divisions in the company, making sure each group of users gets their fair share. When using Teradata PSA, keep the following in mind: Start out simple, monitor, and build from there. Change parameters at any time. Any change made to any parameter, including weight, takes place across all nodes in the configuration when the change is applied. A resource partition, performance group, or allocation group cannot be deleted. Because of this limitation, Teradata recommends changing the name of a defined, but unused, resource partition or performance group to make it obvious it is unused. For example, name the unused resource partition or performance group UNUSED or NULL. When workload classifications are activated in Teradata DWM, a Priority Scheduler configuration is created from the specifications in the rule set. At this point, schmon and xschmon cannot be used to make changes to Priority Scheduler. After the workload classifications are active, use Teradata DWM to create or change workload definitions, and use the Teradata Manager reports to monitor activity. To determine the actual allocation of CPU in real-world situations, look for any unseen loads across the system that might not be explicitly listed. Unseen loads include gateway and streams activity, interrupt service, and non-teradata applications. To begin using the application, see Step 1 - Starting Teradata PSA. 208 Teradata Manager User Guide

209 Chapter 14: Using Teradata Priority Scheduler Administrator Step 1 - Starting Teradata PSA Step 1 - Starting Teradata PSA To start Teradata PSA 1 Start Teradata Manager (from the Windows desktop, click Start>Programs>Teradata Manager 12.0>Teradata Manager). 2 From the Teradata Manager menu bar, click Administer>Workload Management>Priority Scheduler. Continue with Step 2 - Defining PD Set and Resource Partition Parameters. Step 2 - Defining PD Set and Resource Partition Parameters The following parameters are available in the Profile/Resource Partitions panel: PD Set Age Time Active Time CPU Limit Reserved AWT Limit AWT Resource Partition Weight Relative Weight CPU Limit Continue with Step 3 - Defining Performance Group Parameters. Define the parameters in the PD Set/Resource Partitions panel PD Set - Priority Definition Set is the name assigned to the collection of data, including the resource partition, performance group, allocation group, performance period type, and other definitions that control how the Priority Scheduler manages and schedules session execution. Priority Definition Set Parameters Age Time (schmon -t). The time period, in seconds, over which recent allocating group resource usage is measured. The range is 1 through The default is 60 seconds. Decreasing or increasing Age Time makes the Priority Scheduler respond quickly to changes in resource usage. This responsiveness affects the frequency and degree of changes Teradata Manager User Guide 209

210 Chapter 14: Using Teradata Priority Scheduler Administrator Step 2 - Defining PD Set and Resource Partition Parameters in process dispatch priorities and how the Priority Scheduler manages process resource allocation. Note: In this case, responsiveness is not the same as query response time. Modifying Age Time does not necessarily affect query response time. Monitor adjustments in Age Time carefully to judge their effects on Teradata Database system performance. Active Time (schmon -t). The time period, in seconds, during which an allocation group is considered active if any process assigned to the allocation group has been scheduled. Inactive allocation groups are not included in resource consumption or relative weight calculations. The range is 1 through The default is 61 seconds. During this period, the Allocation Group weight continues to influence relative weight calculations and resource allocations, just as if the Allocation Group or Resource Partition were still active. This period causes a smoothing effect in the scheduling algorithms when a few processes are associated with an Allocation Group at interrupted intervals. Note: If no process controlled by an Allocation Group has consumed resources within the preceding Active Time period, the Allocation Group is considered inactive. An Allocation Group and scheduling set are inactive when they have no active processes during the active time interval. A Resource Partition is inactive when it has no active Allocation Group within the active time. Priority Scheduler considers only active Resource Partitions and Allocation Groups when computing the total weight used to calculate the relative weight of Resource Partitions and Allocation Groups. Monitor adjustments to Active Time carefully to judge their effect onteradata Database system performance. CPU Limit (schmon -l). A percentage value to limit the total amount of CPU resources used by all the Teradata Database sessions. The range is 1 through 100. The default is 100. A value of 100 indicates that no limit is to be enforced. The CPU Limit does the following: Limits the total CPU resources consumed to a specified percentage value Has no affect on the scheduling strategy defined by other Priority Scheduler parameters Is enforced separately on each individual node of the Teradata Database system Reserved AWT (schmon -w). A value that indicates the number of AMP work tasks (AWTs) reserved within each AMP vproc for work requests assigned to allocation groups having the Expedite attribute. Teradata recommends the following: Initially select a low number for Reserved AWT (1-3). Expedite only allocation groups supporting short, response-sensitive queries. The range is 0 through 10. The default is Teradata Manager User Guide

211 Chapter 14: Using Teradata Priority Scheduler Administrator Step 2 - Defining PD Set and Resource Partition Parameters Limit AWT (schmon -w). A number that indicates the maximum number of AMP work tasks that can run at any time. The number of tasks that run might be less than this maximum, depending on the current limit. The range is 0 through 80. The default is 80 AWTs for each AMP. For more information on AWTs, see the Priority Scheduler chapter of the Teradata Database Utilities - Volume 2 documentation. Resource Partition Parameters (schmon -b) Resource Partition. The name assigned to the resource partition. The default names are Default, RP1, RP2, RP3, and RP4. Changing all names is permissible except for Default from the Performance Groups or PD Set/Resource Partitions panel. To set up a new resource partition, enter a value for the weight under one of the nondefault resource partition headings. A new Performance Groups panel (for example, Standard:RP1) is created and the relative weight and CPU limit are filled in automatically. To delete a resource partition (except Default), change the weight of the resource partition to be deleted to 0 or select the window of the resource partition to be deleted and click the X button at the right of the window title bar. Weight. A number used to compute a relative weight to determine the proportion of resources that the processes controlled by this resource partition are to receive. The maximum value is When changing the weight, Teradata PSA adjusts the relative weight in response to the value entered. When weights less than 100 are used, the relative weight is approximate. Relative Weight. The weight of this resource partition relative to the sum of the weights of all resource partitions. When the relative weight is changed, Teradata PSA adjusts the weight in response to the value entered. When weights less than 100 are used, the relative weight is approximate. Note: If the Resource Partitions have weights that are close to the maximum and a high relative weight is assigned, Teradata PSA may not be able to raise the weight for that Resource Partition to a high enough value for the desired relative weight. In this case, Teradata PSA gives the Resource Partition the maximum weight. CPU Limit. A percentage limit on total CPU usage by all sessions controlled by this resource partition. The range is 1 through 100. The default is 100. A value of 100 indicates that no limit is to be enforced. For more information on resource partition parameters, see the Priority Scheduler chapter of the Teradata Database Utilities - Volume 2 documentation. Teradata Manager User Guide 211

212 Chapter 14: Using Teradata Priority Scheduler Administrator Step 3 - Defining Performance Group Parameters Step 3 - Defining Performance Group Parameters Teradata PSA creates a window for each resource partition, called the Performance Groups panel. The following parameters are available in this panel: PD Set Resource Partition Performance Group Performance Period Type Limit Allocation Group Set Type Weight Continue with Step 4 - Defining Allocation Group Parameters. Define the parameters in the Performance Groups panel PD Set - Priority Definition Set is the name assigned to the collection of data, including the resource partition, performance group, allocation group, performance period type, and other definitions that control how the Priority Scheduler manages and schedules session execution. Resource Partition - The name assigned to the resource partition. The default names are Default, RP1, RP2, RP3, and RP4. All names can be changed except Default from the Performance Groups or PD Set/Resource Partitions panel. Performance Group - The name of the performance group that allows it to be associated with a session. In the Default resource partition, performance group names cannot be changed. When other resource partitions are created, Teradata PSA gives each Performance Group (PG) a default name. Before V2R6, each PG had a fixed number of four user PGs and four internal PGs per Resource Partition (RP). Teradata PSA shows four Performance Groups, Lx, Mx, Hx and Rx (where x is the resource partition ID) for the RP. For example, in RP2 the performance groups are initially named L2, M2, H2, and R2. In V2R6 and later, there are no longer any Internal PGs, and the maximum number of PGs per RP is 40. The total number of PGs over all RPs is 40. When a new RP is created for a V2R6 or later Teradata Database System, Teradata PSA shows only one PG, Mx. Performance group names can be changed to any alphanumeric string up to 16 characters long and starting with a letter. The name cannot be changed to the default name for another performance group. For example, a performance group in RP1 cannot be named L2. Also, Teradata PSA does not allow any name beginning with L, M, H, or R followed by digits (unless it is the default name for the performance group). For example, L8 is not allowed for any performance group. 212 Teradata Manager User Guide

213 Chapter 14: Using Teradata Priority Scheduler Administrator Step 3 - Defining Performance Group Parameters Performance group names L2abc, A2, and Teradata are acceptable except in the Default resource partition. Note: Only four performance groups are shown in the default resource partition: L (low), M (medium), H (high), and R (rush). These performance groups cannot be modified with Teradata PSA. Teradata PSA controls their definitions so they have the same allocation group as the first performance period of the associated performance group. Experience with the Priority Scheduler has shown that modifying the internal performance groups has unintended effects. In the other resource partitions, Teradata PSA shows a maximum of 40 performance groups and controls the definitions of internal performance groups in a similar way to the default resource partition. Performance Period Type - A code that indicates the type of milestone limits used in the performance period definitions for that performance group. Permissible values are: Resource (default): CPU time since the session started Time-of-Day: At least one performance period must be defined. To define the days of the week, click the Days cell in the Time-of-Day performance period row. On the dialog that appears, select the days, then click OK. The cell in the grid shows the days chosen. Query: CPU time since the query started Session: CPU time since the session started All performance periods of a performance group are the same type. Limit - The value of the threshold used to change performance periods for a performance group. This value can be expressed in the following units: A number of seconds of CPU usage A time-of-day, 0000 (midnight) through 2399 Days Teradata PSA sorts the milestone limit entries from low to high for each performance group, with 0 (Unlimited) as the highest (except Time-of-Day). Allocation Group - The name of the allocation group for this performance period. The Allocation Group name is a feature of Teradata PSA. Neither the Priority Scheduler itself nor schmon support the allocation group. If one of the existing allocation group names is chosen, the following warning may appear: Two Performance Periods have the same Milestone Limit Value. In the Allocation Groups panel, the Used by Performance Groups column shows which performance groups use each allocation group. If New is chosen, the Add Allocation Group dialog box appears. An Allocation Group name is not case sensitive and has a maximum of 16 characters. If text is entered for the new allocation group name, Teradata PSA assigns it the next available ID number (shown in the ID column of the Allocation Groups panel). If a number is entered for the new allocation group name, Teradata PSA puts AG in front of the number and uses the number for the ID. For example, if an allocation group is defined as 123, Teradata PSA gives it the name AG123 and the ID number 123. Valid ID numbers are 0 through 199. Teradata Manager User Guide 213

214 Chapter 14: Using Teradata Priority Scheduler Administrator Step 4 - Defining Allocation Group Parameters Change the other parameters in the Add Allocation Group dialog box, and click OK. When a new allocation group is added in the Performance Group panel, it is added to the list in the Allocation Group column. A new row is also added to the Allocation Groups panel. Set Type - The type of scheduling set division the allocation group enforces. A scheduling set is a collection of processes the allocation group controls. The resources of the allocation group are shared equally by its scheduling sets. The default is None. Permissible values are: None Session None - Expedite Session - Expedite Weight - A number used to compute the proportion of resources each process receives in the allocation group. The maximum value is Adding and Deleting Performance Groups - To add a performance group, click Add Performance Group. Teradata PSA adds a performance group at the bottom of the grid. To delete a performance group, delete all the Performance Periods, set the Type to Unused, then click Delete Performance Group. Adding and Deleting Performance Periods - To add a performance period, select one of the performance groups and click Add Performance Period. Teradata PSA adds a performance period below the original performance period for that performance group. Each performance group can have up to eight performance periods. To delete a performance period, select the period, and click Delete Performance Period. If one of two Time-of-Day performance periods is deleted, a warning message appears. Step 4 - Defining Allocation Group Parameters The following parameters are available in the Allocation Groups panel: Allocation Group Resource Partition Set Type CPU Limit Weight Used by Performance Group 214 Teradata Manager User Guide

215 Chapter 14: Using Teradata Priority Scheduler Administrator Adding or Deleting an Allocation Group Define the parameters in the Allocation Groups panel Allocation Group - The name of the allocation group. The Allocation Group name is a feature of Teradata PSA. Neither the Priority Scheduler itself nor schmon supports the allocation group. To add or delete an allocation group, see To add a new or delete an allocation group on page 215. Resource Partition - The name assigned to the resource partition. Set Type (schmon -a) - The type of scheduling set division the allocation group enforces. A scheduling set is a collection of processes the allocation group controls. The resources of the allocation group are shared equally by its scheduling sets. Permissible values are: None (default) Session None - Expedite Session - Expedite CPU Limit - The limit on the total CPU usage by sessions that the allocation group controls. The range is 1 through 100. The default is 100. A value of 100 indicates that no limit is to be enforced. Weight - A number used to compute the proportion of resources each process receives. The maximum value is Used by Performance Group- The performance groups and performance periods using this allocation group; an allocation group cannot be referenced by performance groups from more than one resource partition Adding or Deleting an Allocation Group To add a new or delete an allocation group 1 From the Teradata Manager menu bar, click Administer>Workload Management>Priority Scheduler. 2 From the Allocation Groups pane, click Add. The Add Allocation Group dialog box appears. An Allocation Group name is not case sensitive and has a maximum of 16 characters: 3 Enter text or a number as follows: If text is entered for the new allocation group name, Teradata PSA assigns it the next available ID number (shown in the ID column of the Allocation Groups panel). If a number is entered for the new allocation group name, Teradata PSA puts AG in front of the number and uses the number for the ID. For example, if an allocation group is defined as 123, Teradata PSA gives it the name AG123 and the ID number 123. Valid ID numbers are 0 through Enter the Weight and CPU Limit. Teradata Manager User Guide 215

216 Chapter 14: Using Teradata Priority Scheduler Administrator Viewing a Priority Definition Set Description 5 Select the Resource Partition to which this allocation group belongs. 6 Select the Set Type. For more information, see the Set Division Type and Expedite Attribute topics in the Priority Scheduler chapter of the Teradata Database Utilities - Volume 2 documentation. 7 Click OK. The new allocation group is also added to the list in the Allocation Group column of the Performance Groups panel of the appropriate resource partition. 8 To delete all unused allocation groups, click Delete Unused. 9 To delete one unused allocation group, highlight the group, and click Delete. Viewing a Priority Definition Set Description To view the text display of a Priority Definition Set 1 From the Priority Scheduler Administrator menu bar, click PDSet>Display. 2 [Optional] To print the text displayed, click Print. To view or print in plain text format, click Plain Text. To save it to a file, see To save a Priority Definition Set Description to a file on page 217. Viewing the Schmon Commands Used to Create a Priority Definition Set To view the schmon commands 1 From the Priority Scheduler Administrator menu bar, click PDSet>Schmon. 2 [Optional] To print the file, click Print. To view or print in plain text format, click Plain Text. Note: If the Copy Selected or Copy All do not work, check that active scripting is enabled in Internet Explorer. To do this, open Internet Explorer. Click Tools>Internet Options. Select the Security tab. Select the Local internet icon and click Custom Level. Under Scripting, click Enable for Active scripting. To save it to a file, see To save Schmon commands to a file on page 217. The file can be used with the UNIX cron program to schedule Priority Definition Set changes. However, Teradata Manager provides a scheduling facility that eliminates the need to use cron. 216 Teradata Manager User Guide

217 Chapter 14: Using Teradata Priority Scheduler Administrator Saving and Deleting Priority Definition Set Information Saving and Deleting Priority Definition Set Information After a Priority Definition Set is defined, save it or send it to the Teradata Database for the scheduling facility to use. Teradata PSA provides several functions to manage Priority Definition Sets, as described in the following procedures: To save a Priority Definition Set Description to a file To save Schmon commands to a file To save a Priority Definition Set to a file To open a Priority Definition Set from a file To save or load a Priority Definition Set to or from the Database To delete a Priority Definition Set To fetch or apply a Priority Definition Set to or from the Teradata Database To correct mismatch errors Priority Definition Sets that are no longer being used can be deleted. To correct resource partition errors, see Correcting Resource Partition Errors in a PDSet. To save a Priority Definition Set Description to a file 1 From the Priority Scheduler Administrator menu bar, click File>Save As. The Save As dialog box appears. 2 In Save as type, click Text to save a text description of the Priority Definition Set to a file. By default, the file name is PDSet Name.txt and the file is saved in the output folder for Teradata Manager. To save Schmon commands to a file 1 From the Priority Scheduler Administrator menu bar, click File>Save As. The Save As dialog box appears. 2 In Save as type, click Schmon commands to save the schmon commands to a file. By default, the file name is PDSet Name_SCH.txt and the file is saved in the output folder for Teradata Manager. To save a Priority Definition Set to a file 1 From the Priority Scheduler Administrator menu bar, click File>Save or File>Save As. The Save As dialog box appears. 2 In Save as type, click Priority Definition Set to save a Priority Definition Set file. Teradata Manager User Guide 217

218 Chapter 14: Using Teradata Priority Scheduler Administrator Saving and Deleting Priority Definition Set Information By default, the file name is PDSetName.psp and the file is saved in the output folder for Teradata Manager. To open a Priority Definition Set from a file 1 From the Priority Scheduler Administrator menu bar, click File>Open. The Open dialog box appears. 2 Select the Priority Definition Set file, then click Open. The selected Priority Definition Set is restored. To save or load a Priority Definition Set to or from the Database 1 From the Priority Scheduler Administrator menu bar, click PDSet>Save to DB. The Priority Definition Set is saved in Teradata Database tables. 2 From the PDSet menu, click Load from DB. 3 Select the Priority Definition Set, then click OK. The selected Priority Definition Set is loaded from the database. To delete a Priority Definition Set Priority Definition Sets that are no longer used can be deleted. For example, after they are converted to workloads in Teradata Workload Analyzer. 1 From the Priority Scheduler Administrator menu bar, click PDSet>Delete to DB. 2 Select the Priority Definition Set to delete, then click OK. A message appears indicating the Priority Definition Set was deleted from the database. To fetch or apply a Priority Definition Set to or from the Teradata Database 1 From the Priority Scheduler Administrator menu bar, click PDSet>Fetch. Teradata PSA uses the Teradata Manager remote console to execute schmon -d to get the current Priority Definition Set. 2 Click PDSet>Apply. The Apply command sends schmon commands for the Priority Definition Set currently defined in Teradata PSA to the Teradata Database. Caution: This command directly affects the operation of the Teradata Database. If mismatch errors occur, use the following procedure to correct. 218 Teradata Manager User Guide

219 Chapter 14: Using Teradata Priority Scheduler Administrator Creating a New Priority Definition Set To correct mismatch errors 1 From the Priority Scheduler Administrator menu bar, click Tools>Clean PSF>Run Clean PSF Commands. 2 If a message appears stating, Schmon clean command successful, click OK. 3 From the PDSet menu, click Apply. If errors persist, contact your DBA. Correcting Resource Partition Errors in a PDSet When loading PDSets created with versions from Teradata Tools and Utilities 8.0 or earlier, an error may occur if the PDSet had non-consecutive resource partitions. If an error occurs when loading the PDSet, either recreate the PDSet or Teradata PSA attempts to fix it. Teradata PSA performs a check on a PDSet when loading it. If Teradata PSA determines the PDSet is faulty and a fix is possible, the following message appears: There appears to be an error with the resource partitions in the PDSet. A fix appears possible. Proceed? Note: The fixed PDSet can be loaded into the version of Teradata PSA that it was originally created in. If No is selected, then use the same version of Teradata PSA used to create the PDSet and fix any non-consecutive resource partitions. If Teradata PSA determines a fix is not possible, the following message appears: There appears to be an error with the resource partitions in the PDSet. Use the same version of Teradata PSA used to create the PDSet and be sure there are no missing resource partitions. To avoid resource partition errors, save and load PDSets with the same version of Teradata PSA. Creating a New Priority Definition Set To create a new Priority Definition Set From the Priority Scheduler Administrator menu bar, click File>New or PDSet>New. Viewing Performance Data Schmon provides the -m command for performance data on the local node and the -M command for performance data for all the nodes. The Teradata Manager Data Collection service collects this data and saves it in tables to maintain a historical record of Priority Teradata Manager User Guide 219

220 Chapter 14: Using Teradata Priority Scheduler Administrator Viewing Performance Data Scheduler performance. Teradata PSA uses this data to create graphs and tables. Both trend graphs and a snapshot of most recent data are available. The data aggregation level can be chosen by resource partitions, performance groups, or allocation groups and select a time period for graphs and tables. If a Priority Definition Set has been constructed so that allocation groups are not shared by performance groups, tables and graphs can be created by performance groups. Teradata PSA merges adjacent user and internal performance groups for performance group reporting purposes. To control collection of data, see Priority Scheduler Data Collector. To view performance data 1 From the Priority Scheduler Administrator menu bar, click Tools>Performance. The Report Type and Time dialog box appears. 2 Select the Scope and Type of data to be shown, then click Next. The Priority Scheduler Groups dialog box appears. See Report Type and Time on page 220 for more information. 3 Select the Priority Scheduler Groups, and click Next. The Data Items dialog box appears. See Priority Scheduler Groups on page 222 for more information. 4 Select the Data Items, and click Finish. See Data Items on page 223 for more information. Priority Scheduler Data Collector Report Type and Time To control collection of Priority Scheduler data 1 From the Teradata Manager menu bar, click Administer>Teradata Manager. 2 Click the Data Collection tab. 3 Continue with Step 8 - Enabling Data Collection on page 61. Schmon provides the -m command for performance data on the local node and the -M command for performance data for all the nodes. Teradata PSA works with the new schmon data collector to provide tables and graphs of current and historical schmon data. Select the Scope of the data to be shown: Current data - Most recent data from schmon. 220 Teradata Manager User Guide

221 Chapter 14: Using Teradata Priority Scheduler Administrator Viewing Performance Data Single Data Sample - A single time period from past collected data. Enter a start date and start time. Teradata PSA displays data for that time (if any exists) or the first collected data after the specified time. Time Series - Group - A time series from past collected data for a single Priority Scheduler Group and multiple data items. Start and end dates and times can be specified. If the Start boxes are enabled, but unchecked, the time series begins with the earliest collected data. If Start Date is checked, but Start Time is unchecked, 0000 is used. If the End boxes are enabled, but unchecked, the time series ends with the most recently collected data. If End Date is checked, but End Time is unchecked, 2359 is used. Teradata PSA displays data collected between the beginning and ending times. Time Series - Data - A time series from past collected data for a single data item and multiple Priority Scheduler Groups. Start and end dates and times can be specified. If the Start boxes are enabled, but unchecked, the time series begins with the earliest collected data. If Start Date is checked, but Start Time is unchecked, 0000 is used. If the End boxes are enabled, but unchecked, the time series ends with the most recently collected data. If End Date is checked, but End Time is unchecked, 2359 is used. Teradata PSA displays data collected between the beginning and ending times. Teradata Manager User Guide 221

222 Chapter 14: Using Teradata Priority Scheduler Administrator Viewing Performance Data Select the Type of data to be shown: Table Line Chart Bar Chart Priority Scheduler Groups A Priority Scheduler Group refers to a resource partition, a performance group, or an allocation group. In a time series report, if a resource partition or performance group name has changed during the time being reported, only the most recent name is shown. All allocation group numbers for the time period are shown. Select the following: All resource partitions All performance groups All allocation groups All resource partitions combined with all allocation groups All resource partitions combined with all performance groups All resource partitions combined with all allocation groups and all performance groups Allocation groups in a selected resource partition Performance groups in a selected resource partition Performance groups in a selected resource partition combined with allocation groups in that performance group An individual selection using the following dialog. The dialog appears in one of two modes depending on the report type: When a report is being created for a single group, only one resource partition, performance group, or allocation group may be selected. The check boxes are disabled. All performance groups and allocation groups are in the lists. When a report is being created for multiple groups, 0 to all resource partitions can be selected. If at least one resource partition is selected, the performance groups and allocation groups lists only show the groups for the selected resource partitions. If no resource partitions are selected, all performance groups and allocation groups are shown in the lists. At least one resource partition, performance group, or allocation group must be selected. If the Time Series - Group report in the Report Type and Time window is selected, only a single group can be selected. 222 Teradata Manager User Guide

223 Chapter 14: Using Teradata Priority Scheduler Administrator Viewing Session Information Data Items Select the Data Items, and click Finish. The table, line chart, or bar chart display. If the Time Series - Data report in the Report Type and Time window is selected, only a single data item can be selected. Viewing Session Information The Priority Scheduler can be controlled in how it affects your workload in two major ways: by changing the Priority Definition Set and by moving sessions among performance groups. The Teradata Manager Session Information application provides functions to move sessions between performance groups by changing their account strings. Session Information allows the account string to be changed, which has the effect of moving a session from one performance group to another performance group in the same resource partition or in another resource partition. Session Information also lets a session to be aborted. Teradata PSA supports a drill across capability to Session Information where detailed information on each session can be observed. To view session information 1 From the Priority Scheduler Administrator menu bar, click Tools>Session Information. 2 Select the resource partitions, performance groups, and allocation groups, and click OK. Note: When the Session Information command starts, it retrieves the current Priority Definition Set from the Teradata Database. It does not disturb the Priority Definition Set in the GUI. When a resource partition is selected, a list of performance groups in that resource partition is displayed. When a performance group is selected, a list of allocation groups in that performance group is displayed. Teradata PSA uses the right-most selected item to select sessions. When OK is clicked, Session Information is called with all the active sessions in that group selected. Note: The Session Information command dynamically updates the session data in this report. The sessions selected for this report are not updated. Teradata Manager User Guide 223

224 Chapter 14: Using Teradata Priority Scheduler Administrator Viewing a Session Report Viewing a Session Report When faced with a performance problem, CPU resources for various sessions can be monitored. The Session Report tool enables the resource partition, performance group, or allocation group of interest to be chosen, then Teradata PSA creates a table showing the amount of CPU time and I/O used by each session in that group for the most recent collection period. To view a session report 1 From the Priority Scheduler Administrator menu bar, click Tools>Session Report. 2 Select the resource partitions, performance groups, and allocation groups, and click OK. A report from a single node or from the sum of all nodes can be selected. Each request can be reported separately or all requests in a session combined. This report is generated from schmon -s data and can be used with the Session Information Report to monitor session activity. Scheduling a Priority Definition Set To schedule a Priority Definition Set 1 From the Priority Scheduler Administrator menu bar, click Tools>Schedule PD Set. The Schedule Priority Definition Set window appears. 2 Enter a name and an optional description for the Scheduled PD Set change. 3 Check the box to override non-standard internal Performance Groups when the PD Set is applied. In interactive mode, Teradata PSA can override non-standard internal Performance Groups. Setting this flag tells Teradata PSA to override any non-standard internal Performance Groups with the standard internal Performance Groups that Teradata PSA creates. For more information, see Step 3 - Defining Performance Group Parameters on page Select the Priority Definition Set, and click Next. The Scheduler window appears. 5 Define the Schedule, and click Finish. 224 Teradata Manager User Guide

225 Chapter 14: Using Teradata Priority Scheduler Administrator Comparing Relative Weights of Allocation Groups or Resource Partitions Comparing Relative Weights of Allocation Groups or Resource Partitions When a Priority Definition Set is defined with several resource partitions and many allocation groups, it is difficult to compare the relative weights of various allocation groups or resource partitions. Not all allocation groups have active sessions at any given time. The relative amount of CPU time that is assigned to allocation groups with active sessions can be compared. Choose a subset of allocation groups among the resource partitions using the Compare Weights tool. Teradata PSA calculates the relative weights of the resource partitions and the relative weights of the allocation groups within their resource partitions. Teradata PSA also calculates the relative weight of each allocation group overall. This approximates the amount of CPU time each allocation group would be allocated if each allocation group has about the same workload. Plan how to allocate CPU time by assigning weights. Comparing Relative CPU Use of an Allocation Group or Resource Partition on page 226 shows how the plan is working by calculating the relative amount of CPU time being used by resource partitions and allocation groups. To compare the relative weights of allocation groups or resource partitions 1 From the Priority Scheduler Administrator menu bar, click Tools>Compare Weights. The Assigned Weights dialog box appears. 2 Select the first resource partition, and move the allocation groups to be compared to the Selected AG s column. 3 Select the next resource partition, and move the allocation groups to be compared to the Selected AG s column. 4 After the allocation groups to be compared have been selected, click OK. A table appears showing the weight, relative weight in the resource partition, and relative weight overall for each allocation group selected. 5 [Optional] Besides the numerical table, Teradata PSA provides a graph to help in visualizing the data that is partitioned proportionally to resource partitions and allocation groups relative weights. To see the graph, click the Assigned Weight tab, and click Visualize. A two-dimensional graph of the data appears in the Assigned Weight tab. Teradata Manager User Guide 225

226 Chapter 14: Using Teradata Priority Scheduler Administrator Comparing Relative CPU Use of an Allocation Group or Resource Partition Comparing Relative CPU Use of an Allocation Group or Resource Partition Plan how to allocate CPU time by assigning weights. Use the Relative CPU Use tool to see how the plan is working by calculating the relative amount of CPU time used by resource partitions and allocation groups. Similar to Comparing Relative Weights of Allocation Groups or Resource Partitions on page 225, use the Relative CPU Use tool to choose a subset of allocation groups among the resource partitions. Teradata PSA calculates the relative CPU use of the allocation groups and the relative CPU use of the allocation group overall. Teradata PSA retrieves current CPU usage data from schmon to generate this information. To compare the relative CPU use of an allocation group or resource partition 1 From the Priority Scheduler Administrator menu bar, click Tools>Relative CPU Use. 2 Select the resource partition, and move the allocation groups to be compared to the Selected AG s column. 3 Select the next resource partition, and move the allocation groups to be compared to the Selected AG s column. 4 After the allocation groups to be compared have been selected, click OK. A table appears showing the CPU time, percent CPU time in the resource partition, and percent CPU time overall for each allocation group selected. Besides the numerical table, Teradata PSA provides a visualization of the data with a twodimensional area that is partitioned proportionally to resource partitions and CPU times of allocation groups. In the Relative CPU time panel, click Visualize. Changing the Operating System Type Teradata PSA needs to know the operating system type of the Teradata Database to format Priority Scheduler commands correctly. It is possible that the wrong operating system type may have been specified with Teradata Manager Database Setup application. If this occurs, the Dispatch Queue Wait or the IO Concurrency commands may have the wrong value, causing the Priority Scheduler facility and the Teradata Database to perform in unexpected ways. To correct this situation, perform the following procedure. 226 Teradata Manager User Guide

227 Chapter 14: Using Teradata Priority Scheduler Administrator Defining Advanced PD Set and Resource Partition Parameters To change the operating system type 1 From the Priority Scheduler Administrator menu bar, click Tools>Operating System. The Operating System for Teradata dialog box appears. 2 Select the operating system to change. 3 Click OK. Defining Advanced PD Set and Resource Partition Parameters Note: Changing these values may have unintended performance impact on your Teradata Database system. Consult with your Teradata analyst for more information. To set the advanced parameters 1 From the Priority Scheduler Administrator menu bar, click Tools>Advanced Options. The Advanced Options dialog box appears. 2 Set the parameters as follows: I/O Prioritization (schmon -i or -I) - The prioritized queuing of FSG I/O requests. Check this box to enable the prioritized queuing of FSG I/O requests. Requests are serviced from the scheduling priority of the submitting process. This is the default. Leave box unchecked to disable the prioritized queuing of FSG I/O requests. Requests are serviced in an order the normal driver method establishes. Dispatch Queue Wait (schmon -t) - The time period, in seconds, that a process can wait in a ready-for-execution state in a dispatch queue without receiving access to a CPU. After this time, the process dispatch priority is promoted to the next-higher dispatch priority and its wait period re-initiated. The range is 0 through 127. The default is 0. A value of 0 indicates that processes are not to be promoted. I/O Concurrency (schmon -t) - A Windows 2000-only feature that shows the number of concurrent I/O requests that might be active for each AMP-type vproc. The range is 1 through 100. The default is 10. Note: The I/O Concurrency does not appear in the schmon -t and schmon -d output. To reset all the values back to their defaults, click Reset All to Defaults. 3 Click OK. Teradata Manager User Guide 227

228 Chapter 14: Using Teradata Priority Scheduler Administrator Configuring the Priority Scheduler Administrator Display Configuring the Priority Scheduler Administrator Display The configuration of the default Teradata PSA window depends on the size of the display. For large displays: the Performance Groups panel is a maximized single child window on the left the PD Set/Resource Partitions and Allocation Groups panels are docked vertically on the right For small displays, the three panels are cascaded child windows To change the configuration of the display From the Priority Scheduler Administrator menu bar, click View and one of the following: Dock - docks the PD Set/Resource Partitions and Allocation Groups panels vertically on the right Float - floats the PD Set/Resource Partitions and Allocation Groups panels above the main Teradata PSA window Window - makes the PD Set/Resource Partitions and Allocation Groups panels child windows, with selection tabs at the bottom of each panel. To turn tabs on and off, click View>Tabs Priority Scheduler Administrator Command Line Parameters Teradata PSA supports the following command line parameters: -s PDSetName Teradata PSA loads PDSetName from the Teradata Database and applies the PDSet to the Teradata Database using schmon. The Teradata PSA user interface does not start. This parameter is used with the Teradata Manager scheduler to apply a PDSet at a scheduled time. -d Teradata PSA starts in small display mode. -D Teradata PSA starts in large display mode. -o Teradata PSA overrides non-standard internal performance groups. 228 Teradata Manager User Guide

229 CHAPTER 15 Using Alerts to Monitor Your System Teradata Manager includes an alerting facility that monitors your Teradata Database and automatically invokes actions when interesting or critical events occur. Use the facility to define simple actions like paging the DBA, sending to the CIO, or escalating incidents to the help desk. Also, use it to define more sophisticated actions that perform corrective measures, such as lowering a session s priority or running a user-defined SQL script. The following topics provide information on the Teradata Manager Alert facility, discuss how to configure alert actions to generate notifications of, and actively respond to, Teradata Database events, and provide examples that can be applied to your Teradata alert policy: Introduction to the Alerts Facility Creating a New Alert Policy Defining Actions to the Policy Defining Actions - Sending a Page Defining Actions - Sending Configuring the System to Send Alerts Defining Actions - Running a Program Defining Actions - Running a BTEQ Script Defining Actions - Generating an SNMP Trap Defining Actions - Action Lists Defining Events to the Policy Defining Events - Database Space Defining Events - System Level Performance Defining Events - Node Level Performance Defining Events - Vproc Level Performance Defining Events - Session Level Performance Defining Data Collection Rates for the Policy Applying the Policy to the Database Displaying the Performance Status of the Database Alerting on Teradata Event Messages From Teradata Database V2R6.x on Windows 2000 Alerting on Policy Refresh Time Alerts Examples Teradata Manager User Guide 229

230 Chapter 15: Using Alerts to Monitor Your System Introduction to the Alerts Facility Introduction to the Alerts Facility The alerts facility consists of three components: Alert Policy Editor (APE) - The tool used for defining alert actions and events. The collection of actions and events, stored on your Teradata Database, is known as an alert policy. Alert Service - Monitors the Teradata Database for alertable conditions defined in the Alert Policy Alert Viewer - Shows the state of your Teradata Database system in graphical views and highlights events that have triggered alerts Running the Teradata Manager Alert System takes just a few simple steps. First, use the Alert Policy Editor to: Create a new policy Define alert actions Set thresholds and assign actions to Teradata Database events Apply the policy to your Teradata Database Next, configure the Alert Service: Select the Teradata Database(s) to be monitored Ensure the Teradata Manager Service is running Lastly, run the Alert Viewer to check on the status of your Teradata Database (this is optional). To view the status of your Database from more than one workstation, multiple copies of the Alert Viewer can be run (each running on a different client workstation) to display information from a single Teradata Alerts Server. Note: For Alert Viewer to display Monitor Alerts, it must be connected to the active Alerts Server. Creating a New Alert Policy The combination of action and event definitions is called an Alert Policy, and is created using the Alert Policy Editor. The first step in setting up the Alerts system is creating a new Alert Policy. To create a new Policy 1 Start Teradata Manager (Start>Programs>Teradata Manager 12.0>Teradata Manager). 2 Define the target systems to Teradata Manager. For information on defining systems to Teradata Manager, see Step 6 - Defining System Parameters on page Teradata Manager User Guide

231 Chapter 15: Using Alerts to Monitor Your System Defining Actions to the Policy 3 From the Teradata Manager menu bar, click Administer>Alert Policies to start the Alert Policy Editor. 4 Do one of the following: To create a new policy based on the Alert Policy Template: From the Alert Policy Editor menu bar, click File>New. To create a new policy based on an existing one: From the main window of the Alert Policy Editor, click Local or Active. Click a name in the list. Click File>Save As. 5 Enter a Name for the new alert policy. 6 Click OK to create the new policy. Although many policies can be created, only one policy can be active at a time. Alert Policy Editor Log File When changes are made to an alert policy, a log file (ape.log) is updated. For the default location of this file, see Table 11 on page 44. The ape.log file has no size limit. The ape.log file has five columns. System is the Teradata Database the policy is applied to. Policy is any of the following: The name of the applied policy; a system name if an active policy is retrieved; or a file name if the policy applied is contained in a file. To change the location of this directory, click Tools>Options from the Alert Policy Editor main window. Defining Actions to the Policy Physical Actions The key to the Alerts system is the user-defined action. An action can consist of various tasks, such as paging a systems programmer, sending an to a customer support center, displaying a banner, or running an executable program that automatically corrects a problem or performs some other action. It is recommended the DBA first set system limits and select the <Write to Log> action for each alert (see Table 87 on page 232). Next, view the log to determine which alerts are launching too frequently or not launching enough. Lastly, adjust the system limits accordingly before adding the actual actions. Follow this process to avoid sending false positive s and pages. Teradata Manager supports the following types of alerts, which are known as physical actions: Teradata Manager User Guide 231

232 Chapter 15: Using Alerts to Monitor Your System Defining Actions to the Policy Table 86: Physical Actions Action Send a Page Send an Run a program Run a BTEQ script Notify SNMP System Display a Banner Description Specify the pager number and numeric callback message To send an alphanumeric message, use the Send an action instead (see Alerts Examples on page 251) Specify an address and text message. Event information (date, time, event name, threshold and actual value) is automatically added to the body of the message. This action requires that a MAPI or SMTP-based client be configured on the Teradata Manager server PC. Execute a specified program (.exe). The executable file must reside in the secure subdirectory of the Teradata Manager folder. Execute a BTEQ command window, passing a file that is specified as input. The script file must reside in the secure subdirectory of the Teradata Manager folder. Generate an SNMP Trap This action requires that the Windows SNMP service be configured on the Teradata Manager PC. Display scrolling alert information on the Windows desktop The alert policy provides the following built-in actions: Table 87: Built-in Actions Action <Write to Log> <Abort Session> Description Record the event in the alert log. The alert log contains one entry for each alert the Alert Service executes. The files are in text format, and have a file name of alerts.log by default. To change the log file name or the size of the log, see Step 6 - Defining System Parameters on page 57. The log files are located in: \Documents and Settings\All Users\Application Data\NCR\Teradata Manager\Databases\<TDPID> Abort the Teradata Database session for which an alert condition was detected. This action is only available for Session events. 232 Teradata Manager User Guide

233 Chapter 15: Using Alerts to Monitor Your System Defining Actions - Sending a Page Table 87: Built-in Actions (continued) Action <Lower Priority> <No Action> Description Set the priority of the Teradata Database session for which an alert condition was detected to the one specified in the Lower Priority Action field on the System tab. If there is no entry in this field, the default $L is used. Any system defined priority like $M, or a user defined performance group name like $TESTGRP$ can be used. (A user performance group name has $ surrounding it and may be up to 18 characters, including the $). This action is only available for Session events. Do not raise an alert Logical Actions The physical actions themselves are just templates and cannot be assigned directly to events in alert policy. For example, the action Send a Page requires additional information: a pager number and a callback number (or message). Instantiate alert actions by creating Logical Actions, then assign the logical actions to specific Teradata Database events. Logical actions fall into two categories: Action Definition - associates a physical action with a user-defined name and any required execution parameters For example, the physical action Send a Page can be instantiated as a logical action by giving it a name such as Page DBA, and assigning the pager number and a callback number of the DBA. Action List - a named collection of action definitions. See Defining Actions - Action Lists on page 241. To define a logical action, run the Alert Policy Editor, which can be accessed from the Administer menu of Teradata Manager. Defining Actions - Sending a Page The Send a Page action supports numeric messages only. Alphanumeric messages are supported using the Send an action which is described in Defining Actions - Sending on page 234. An alphanumeric paging example is described in Sending a Text Page on page 251. To define an action that sends a numeric page 1 In the Alert Policy Editor, click a policy to activate the Actions tab, then click Add. The Add Action dialog box appears. Teradata Manager User Guide 233

234 Chapter 15: Using Alerts to Monitor Your System Defining Actions - Sending 2 Type in an Action Name. For this example, the name Page Admin is used. 3 Ensure Action Definition is selected. 4 Click OK to close the Add Action dialog; the Alert Policy Editor window appears. Your new action (Page Admin) is now displayed in the list of actions. 5 With Page Admin highlighted, select Send a Page from the Physical Action list. 6 In the Pager Number box, type in your Administrator's pager number. 7 In the Callback Number box, type in the callback number or other numeric message to be sent to the Administrator. 8 In the Do not repeat within box, enter the number of minutes that need to elapse between successive invocations of this action. For example, if 10 is entered, this tells Teradata Manager not to execute Page Admin alerts within 10 minutes of each other. Note: The Send a Page action requires a modem configured on the Windows system that hosts the Teradata Manager Service. Defining Actions - Sending The Send an action can be used for sending alphanumeric pages as well as normal e- mail. An alphanumeric paging example is described in Alerts Examples on page 251. To define an action that sends an 1 In the Alert Policy Editor, click the Actions tab to make it active, then click Add. The Add Action dialog box appears. 2 Type in an Action Name. For this example, the name Admin is used. 3 Ensure Action Definition is selected. 4 Click OK to dismiss the Add Action dialog; the Alert Policy Editor window appears. Your new action ( Admin) is now displayed in the list of actions. 5 With Admin highlighted, select Send an from the Physical Action list. 6 In the Address box, enter the address of the person to whom the alert is sent. To send to multiple addresses, use an Action List. See Defining Actions - Action Lists on page [Optional] In the Message box, enter a text message to be included in the alert. A description of the event is automatically included in the body of the message, as described below. Any text entered in the Message box is then appended to the body of the . 8 In the Do not repeat within box, enter the number of minutes that need to elapse between successive invocations of this action. For example, if 15 is entered, this tells Teradata Manager not to execute Admin alerts within 15 minutes of each other. 234 Teradata Manager User Guide

235 Chapter 15: Using Alerts to Monitor Your System Defining Actions - Sending 9 Enable the Teradata Manager Alert service to send notifications of events by following the procedure in Configuring the System to Send Alerts on page Alert Message An alert is a text message containing the following fields (one field per line): Table 88: Alert Message Field Date Time DBS (TDPID) Utility Description The Teradata Database date on which the event occurred The Teradata Database time at which the event occurred The TDPID of the Teradata Database The name of the utility that generated the event. The Alerts system contains the following pre-defined utility names: Performance pertains to events in the System, Node, Vproc, Session, and Combination categories Database Space pertains to events in the DB Space category Database Event Log pertains to events in the Database Events category alerts that are generated using the AlertRequest or MonitorRequest tables contain their own utility names: for AlertRequests, the utility name is taken from the JobName column; for MonitorRequests, the utility name is the MonitorId. Datapoint The name of the alert item. For example: System Average AMP CPU % Threshold Actual Value Message The threshold that was exceeded Note: This field does not appear for AlertRequest or MonitorRequest alerts. The actual event value The text that was entered into the Message field in the Alert Policy Editor, or the Message column of the AlertRequest or MonitorRequest table Alert Example This is a sample alert for average AMP CPU utilization on a Teradata Database named teradb : From: [email protected] Sent: Wednesday, May 23, :28 To: [email protected] Subject: Alert for Performance - System Average AMP CPU % Date: 2002/05/23 Time: 10:27:16 DBS: teradb Utility: Performance Datapoint: System Average AMP CPU % Threshold Value: 80 Actual Value: 84 Alert from Teradata Manager - this text comes from Teradata Manager User Guide 235

236 Chapter 15: Using Alerts to Monitor Your System Configuring the System to Send Alerts the Message field of the Alert Policy Editor s Actions tab. Configuring the System to Send Alerts Before Beginning Configuring Options The Teradata Manager Alert service can be enabled to send notifications of events. To send to multiple addresses, use an Action List. See Defining Actions - Action Lists on page 241. Teradata Manager uses MAPI or SMTP to send alerts. In the case of MAPI, an client is needed such as Microsoft Outlook configured on the Windows system hosting the Teradata Manager Service. Also, your mail server must be Microsoft Exchange Server. The MAPI client account must meet the following requirements: The account is designated for use only with the Teradata Manager Service, and must be configured on the machine where the service is running. The user must be a member of the Administrators group on the machine where the Teradata Manager Service is running. A default MAPI profile for this account must be created. The default delivery location of the profile must be the Exchange mailbox (not a.pst). This means the delivery location for your account profile is designated by setting the Deliver new mail to the following location box to the Exchange mailbox (for example, Mailbox - Jason Johnston). Do not set it to Personal Folders. Note: Repeat this procedure whenever the client logon information changes. To configure the Teradata Manager options (Step 1 of 2) 1 From the Teradata Manager menu bar, click Administer>Teradata Manager. 2 Click the System tab. 3 Select the appropriate system from the System (DBS) Name box. 4 Do one of the following: If using a Microsoft client such as Outlook, click Configure and input your settings as follows, and then click OK to save your settings: Username - the client user name Password - the password for the client user name Domain - the client domain name 236 Teradata Manager User Guide

237 Chapter 15: Using Alerts to Monitor Your System Configuring the System to Send Alerts To use SMTP mail, check the Use SMTP Mail box, then click Configure , and input your settings as follows: SMTP Server - name of the SMTP server SMTP Port - the port STMP is available on. The default is port 25. Server Timeout - the amount of time, in seconds, the connection is attempted before timing out. The default is 30 seconds. This server requires a secure connection (SSL) - select this check box if your server requires a Secure Socket Layer connection Reply Address - the address that appears in the reply field of the Authentication Method - click Anonymous Logon, Basic Authentication (requiring a Username and Password), or NTLM Test Recipient - entering an address here and then clicking Test allows testing of the SMTP mail server instantly. Do this to confirm that SMTP mail can be sent successfully. This step is strongly recommended before running the alert editor to configure mail alerts. Click Defaults to fill the fields with the default settings Click OK to save your settings To configure the Teradata Manager Service logon options (Step 2 of 2) 1 Go to the Services window. From the Windows 2000 desktop, click Start>Settings>Control Panel> Administrative Tools>Services). 2 If the Teradata Manager Service is running, right-click the Teradata Manager Service to display the shortcut menu. 3 Click Stop. 4 Right-click the Teradata Manager Service to display the shortcut menu. 5 Click Properties. 6 If using MAPI, do the following: a b c Click the Log On tab. Click This account and enter the same account information entered in To configure the Teradata Manager options (Step 1 of 2), (<domain name>\userid), Password, and Confirm password). Click Apply. 7 Click Local System account, and ensure the Allow service to interact with desktop check box is selected. 8 Click OK. 9 Right-click the Teradata Manager Service to display the shortcut menu. 10 Click Start to start the service. Teradata Manager User Guide 237

238 Chapter 15: Using Alerts to Monitor Your System Defining Actions - Running a Program Defining Actions - Running a Program The Run a Program action can be used to launch an application. This application might automatically correct the problem or take some additional action. A startup string containing information about the alert is passed to that application. Teradata Manager includes an SNMP agent that allows third party applications to monitor Teradata Database performance and to be notified of exceptions using SNMP traps. For more information, see Chapter 5 Configuring the SNMP Agent on page 85 and Defining Actions - Generating an SNMP Trap on page 240. To define an action that runs a program 1 In the Alert Policy Editor, click the Actions tab to make it active, then click Add. The Add Action dialog box appears. 2 Type in an Action Name. For this example, the name Make web page is used. 3 Ensure Action Definition is selected. Command Line Parameters 4 Click OK to dismiss the Add Action dialog; the Alert Policy Editor window appears. Your new action (Make web page) is now displayed in the list of actions. 5 With Make web page highlighted, select Run a program from the Physical Action list. 6 In the Program Name box, enter the name of the application (.EXE) file. For this example, a program called makehtml.exe is specified as the program to be executed when the Make web page alert is raised. The simple programmakehtml.exe reads alert information from the command line, parses and formats the information as HTML, and saves the HTML file in the directory the -d command line parameter specifies. Note: Put the executable file in the secure subdirectory of your Teradata Manager installation on the Teradata Manager server PC (the default path is \Program Files\NCR\Teradata Manager 12.0\secure.) 7 In the Parameters box, enter any command line parameters to be passed to the program. In this example, the -d command line parameter is specified, which tells makehtml.exe where to write the HTML file. 8 In the Do not repeat within box, enter the number of minutes that need to elapse between successive invocations of this action. For example, if 0 is entered here, this tells Teradata Manager to execute Make web page alerts every time an event which has been assigned this action is detected, regardless of how frequently it happens. For Run a Program actions, the sequence of the command line parameters is: Executable name. For example: c:\program files\ncr\teradata Manager 12.0\secure\ makehtml.exe Items specified in the Parameters box. For example: -d c:\inetpub\tdalert 238 Teradata Manager User Guide

239 Chapter 15: Using Alerts to Monitor Your System Defining Actions - Running a BTEQ Script Colon-delimited list of event data The list of event data items are as follows: Table 89: Event Data Items Item Threshold Actual Value TDPID Utility Description The threshold that was exceeded The actual event value The TDPID of the Teradata Database The name of the utility that generated the event Event The name of the event (for example, System Average AMP CPU % ) Date Time The Teradata Database date on which the event occurred The Teradata Database time at which the event occurred Using the Make web page action as an example, suppose this action was assigned to the System event Average AMP CPU % on the teradb Database. When an alert is raised, the following command line is executed (without line breaks): c:\program files\ncr\teradata Manager 12.0\secure\makehtml.exe -d c:\inetpub\tdalert 80:85:teradb:Performance:System Average AMP CPU %:2001/05/23:12:23:45. Defining Actions - Running a BTEQ Script Caution: Do not assign a BTEQ script action to the Response Time event from the System tab. If an alert is triggered for response time, this may indicate a heavily congested or hung system, in which case any BTEQ script would itself become blocked. To define an action that runs a BTEQ script 1 In the Alert Policy Editor, click the Actions tab to make it active, then click Add. The Add Action dialog box appears. 2 Type in an Action Name. For this example, the name Clean DB is used. 3 Ensure Action Definition is selected. 4 Click OK to dismiss the Add Action dialog; the Alert Policy Editor window appears. Your new action (Clean DB) is now displayed in the list of actions. 5 With Clean DB highlighted, select Run a BTEQ script from the Physical Action list. 6 In the Script File Name box, enter the name of the file. For this example, cleandb.txt is specified as the script to be executed when the Clean DB alert is raised; cleandb.txt contains SQL statements that delete rows from tables in a user's Teradata Manager User Guide 239

240 Chapter 15: Using Alerts to Monitor Your System Defining Actions - Generating an SNMP Trap Logon Information database. The Alerts system invokes this action whenever the perm space utilization for the user's database exceeds 90%. Note: Put the script file in the secure subdirectory of your Teradata Manager installation on the Teradata Manager server PC (the default path is \Program Files\NCR\Teradata Manager 12.0\secure.) 7 In the Do not repeat within box, enter the number of minutes that need to elapse between successive invocations of this action. For example, if 120 is entered here, this tells Teradata Manager not to execute Clean DB alerts within two hours of each other. The BTEQ session is executed on the Teradata Manager server PC and has access to the Teradata Manager profile data. This allows the use of the special.logon... shortcut in the SQL script and avoids placing a UserName and password in the script file. For example, if the current Teradata Manager profile specifies TDPID teradb, UserName tdmanager and password tdm, then the bteq command.logon... is equivalent to.logon teradb/tdmanager,tdm. Defining Actions - Generating an SNMP Trap To define an action that generates an SNMP trap 1 In the Alert Policy Editor, click the Actions tab to make it active, then click Add. The Add Action dialog box appears. 2 Type in an Action Name. For this example, the name SNMP Trap is used. 3 Ensure Action Definition is selected. 4 Click OK to dismiss the Add Action dialog; the Alert Policy Editor window appears. Your new action (SNMP Trap) is now displayed in the list of actions. 5 With SNMP Trap highlighted, select Notify SNMP System from the Physical Action list. 6 In the Do not repeat within box, enter the number of minutes that need to elapse between successive invocations of this action. For example, if 0 is entered, this tells Teradata Manager to execute SNMP Trap alerts every time an event that has been assigned this action is detected. Set Up the Windows SNMP Service The SNMP alert action requires Microsoft's SNMP service to be installed and configured on the Teradata Manager server PC. Consult the Windows documentation for information on setting up the SNMP service. 240 Teradata Manager User Guide

241 Chapter 15: Using Alerts to Monitor Your System Defining Actions - Action Lists Defining Actions - Action Lists To execute a combination of actions when an event occurs, create an Action List. For example, when the perm space utilization of a database exceeds 90%, Teradata Manager can page the DBA, generate a web page for the event, clean the database, and send to an unlimited number of people. To define an Action List 1 In the Alert Policy Editor, click the Actions tab to make it active, then click Add. The Add Action dialog box appears. 2 Type in an Action Name. For this example, the name Page Admin & Clean DB is used. 3 Select List of Actions. 4 Click OK to close the Add Action dialog; the Alert Policy Editor window. appears. Your new action (Page Admin & Clean DB) is now displayed in the list. Notice the empty box under the label List of Actions and the new Add and Delete buttons on the right side of the window. 5 With Page Admin & Clean DB highlighted, click Add under List of Actions (on the right side of the window). The Add Action(s) to List dialog box appears. 6 Hold down the <Ctrl> key and click each of the actions that are to be included in the Page Admin & Clean DB list. 7 Click OK to return to the Alert Policy Editor window. Now the List of Actions associated with Page Admin & Clean DB shows the set of actions selected. Defining Events to the Policy After the actions are defined, the events that trigger them can be defined. Events occur when a monitored system parameter crosses a threshold that has been defined. These events are defined based on data collected from the following areas: PM Physical Resource data PM Virtual Resource data Database Space information Session information Teradata Manager User Guide 241

242 Chapter 15: Using Alerts to Monitor Your System Defining Events - Database Space Teradata Database messages Event Combinations Defining Events - Database Space Database Space events are defined to raise an alert whenever the space used on any AMP exceeds the specified percentage. Define the appropriate actions before continuing. Monitoring databases impacts performance. Depending on your system, it is recommended the Collect Database Space rate be set to 15 minutes or higher. If your tables grow very quickly, use a higher rate to minimize performance impact. To add a Database Space event 1 In the Alert Policy Editor, click the DB Space tab to make it active, then click Add. The Add Database Rule dialog box appears. 2 Do one of the following: To apply the rule to a specific database, click Apply to Specific database, then enter the name of the database in the Database Name box. To apply the rule globally to all databases, click Apply to All databases. 3 Click OK to add the new database rule to the list. 4 Ensure the rule is highlighted, then enter the percentage limit in the % Space used is above field. 5 With the same rule highlighted, select from the list the action to be taken when the rule is exceeded. 6 Repeat Steps 1 through 5 to add as many rules as are required. Alternatively, to add alerts for many databases, directly insert rows onto the AlertLevel table. For example: Insert into dbcmngr.alertlevel Values (800, [dbname], [limit], 0, [action], <None>, <None>, 0) The three items in brackets are variables; the remaining values are literals. Defining Events - System Level Performance System Level Performance events are defined to raise an alert whenever the performance on your Teradata Database falls out of the specified thresholds. Define the appropriate actions before continuing. 242 Teradata Manager User Guide

243 Chapter 15: Using Alerts to Monitor Your System Defining Events - Node Level Performance For information on default settings, source data, and calculations on performance alerts at the system level, see Workload Management API: PM/API and Open API. See Additional Information on page 6 to locate this resource. To add a System level performance event 1 In the Alert Policy Editor, click the System tab to make it active. 2 Click to highlight the event in the pane, then use the Above box and Below box to set the system limits. Caution: Do not assign a BTEQ script action to the Response Time event. If an alert is triggered for response time, this may indicate a heavily congested or hung system, in which case any BTEQ script would itself become blocked. Note: For Parallel Efficiency events, the parallel efficiency = 100 * AvgCPU / MaxCPU. CPU is either node or AMP level depending on the chosen event. Averages are a simple average across all online nodes, AMPs, PEs, and so forth. 3 Use the drop-down lists to define the appropriate actions to take for the Above, Between, and Below conditions. 4 Enter the Duration (in minutes) for which this condition must exist before the alert action is taken. If the duration is 0, the action will be taken even if the condition exists only momentarily. It is recommended that Duration be set to greater than 0. 5 Repeat this procedure from Step 2 to set up as many System level events as required. Defining Events - Node Level Performance Node Level Performance events are defined to raise an alert whenever the performance on your Teradata Database falls out of the specified thresholds. Define the appropriate actions before continuing. For information on default settings, source data, and calculations on performance alerts at the node level, see Workload Management API: PM/API and Open API. See Additional Information on page 6 to locate this resource. To add a Node level performance event 1 In the Alert Policy Editor, click the Nodes tab to make it active. 2 Click to highlight the event in the pane, then use the Above box, Below box, or Non-TPA node count box to set the system limits. 3 Use the drop-down lists to define the appropriate actions to take for the Above, Between, and Below conditions. Teradata Manager User Guide 243

244 Chapter 15: Using Alerts to Monitor Your System Defining Events - Vproc Level Performance 4 Enter the Duration (in minutes) for which this condition must exist before the alert action is taken. If the duration is 0, the action will be taken even if the condition exists only momentarily. It is recommended that Duration be set to greater than 0. 5 Repeat this procedure from Step 2 to set up as many node level events as required. Node Alerts and Non-TPA Nodes In a situation where the Teradata Manager alerting service is started and the Teradata Database already has one or more DOWN TPA nodes, Teradata Manager does not have a sure way of distinguishing TPA nodes from non-tpa nodes. This is because all affected nodes appear to have gone into DOWN status simultaneously. In this case, Teradata Manager begins sending NODE DOWN alerts based on the order of node information it receives from the Teradata PM/API. Using the example above, if three nodes are DOWN when Teradata Manager Alerts is started, then Teradata Manager ignores the first two DOWN nodes received from PM/API and begins alerting on the third DOWN node, which may be a non-tpa node. This situation can be avoided by configuring non-tpa nodes without having PDE installed on them at all. This prevents the PM/API from reporting non-tpa nodes; the Teradata Manager non-tpa Node Count is set to zero. Any node with DOWN status is sure to be a TPA node. Recommendation Do not install PDE on non-tpa nodes. In Teradata Manager, set the non-tpa node count to 0. For Teradata Database systems already having PDE on non-tpa nodes: Set the non-tpa Node Count in the Teradata Manager Alert Policy appropriately If Teradata Manager reports NODE DOWN alerts for a non-tpa node, do check the Teradata Database; one (or more) TPA nodes are down Defining Events - Vproc Level Performance Vproc Level Performance events are defined to raise an alert whenever the performance on your Teradata Database falls out of the specified thresholds. Define the appropriate actions before continuing. For information on default settings, source data, and calculations on performance alerts at the Vproc level, see Workload Management API: PM/API and Open API. See Additional Information on page 6 to locate this resource. To add a Vproc level performance event 1 In the Alert Policy Editor, click the Vprocs tab to make it active. 2 Click to highlight the event in the pane, then use the Above box and Below box to set the system limits. 244 Teradata Manager User Guide

245 Chapter 15: Using Alerts to Monitor Your System Defining Events - Session Level Performance Note: The Vproc is Down event is a simple condition, and thus has no limit fields attached to it. 3 Use the drop-down lists to define the appropriate actions to take for the Above, Between, and Below conditions. 4 Enter the Duration (in minutes) for which this condition must exist before the alert action is taken. If the duration is 0, the action will be taken even if the condition exists only momentarily. It is recommended that Duration be set to greater than 0. 5 Repeat this procedure from Step 2 to set up as many vproc level events as are required. Defining Events - Session Level Performance Session Level Performance events are defined to raise an alert whenever the performance on your Teradata Database falls out of the specified thresholds. Define the appropriate actions before continuing. For information on default settings, source data, and calculations on performance alerts at the session level, see Workload Management API: PM/API and Open API. See Additional Information on page 6 to locate this resource. To add a session level performance event 1 In the Alert Policy Editor, click the Sessions tab to make it active. 2 Click to highlight the event in the pane, then use the Above box and Below box to set the system limits. Note: The Running at Rush priority and Logon to Monitor partition events are simple conditions, and thus have no limit fields attached to them. Note: For the CPU Skew % event, the amount of CPU usage to use on the most heavily used AMP must be specified before the event is triggered. By specifying a value greater than 0, an alert is avoided when a query uses indexed retrieval. Index retrievals use only 1 or 2 AMPs and, therefore, are inherently skewed operations. Setting this limit allows targeting of this alert to only those skewed queries that consume large amounts of CPU. 3 Use the drop-down lists to define the appropriate actions to take for the Above and Between conditions. 4 Click Exceptions to specify users who are exempt from all session level alerts except the Blocked for alert. 5 Repeat this procedure from Step 2 to set up as many session level events as are required. Teradata Manager User Guide 245

246 Chapter 15: Using Alerts to Monitor Your System Defining Data Collection Rates for the Policy Defining Data Collection Rates for the Policy Use this procedure to change the collection frequency for various types of data. The default rates are set when the policy is created using the Alert Policy Template. The rates are internal to the Alerts system; therefore, they do not affect Teradata Database values. It is recommended the Collect Session Data rate be set to match the rate set in the Teradata Database itself. To set this rate, use PMON, Session Information, or the Remote Console. To define data collection rates 1 In the Alert Policy Editor, click the Rates tab to make it active. 2 Highlight the appropriate collection type, then change the collection frequency by entering the new value in the Collection Interval box. The Refresh Policy Information rate is the frequency at which the Teradata Manager Service checks to see if the active policy has been updated, and if so, begins executing alerts to the new policy accordingly. The Teradata Manager Service generates an alert when it is unable to read policy information from the database. For information on defining this alert, see Alerting on Policy Refresh Time on page 250. The Process Alert Requests rate is the frequency at which Teradata Manager checks to see if alerts need to be raised for the user jobs. The criteria for alerts is based on the rows that have been inserted into the AlertRequest and MonitorRequest tables. For more information the AlertRequest table, see Using the AlertRequest Table on page 252 For more information on the MonitorRequest table, see Using the MonitorRequest Table on page Repeat Step 2 to set up as many rates as are required. Applying the Policy to the Database There are two modes for applying your alert policy to the Teradata Database: Interactive - applies the policy changes to the Database as was requested Batch - allows automatic alert policy changes to be scheduled To apply a policy to the Database in interactive mode 1 From the Alert Policy Editor menu bar, click Tools>Apply to Database. A list of systems currently in the active list appears. 2 Select the System from the list, then click OK to apply the policy to the selected system. 246 Teradata Manager User Guide

247 Chapter 15: Using Alerts to Monitor Your System Displaying the Performance Status of the Database To apply a policy to the system in batch mode In batch mode, start APE with command line parameters that specify the name of a saved alert policy file along with the name of the Teradata Manager system that contains appropriate Teradata Database logon information. APE uses this information to update the alert policy on the Teradata Database system without user interaction. Batch mode allows automatic alert policy changes to be scheduled. Example of Applying Policy in Batch Mode A local copy of an alert policy with the name NightShift is saved. To apply this policy to the Teradata Database system identified in the teradb profile, the command would be: ape.exe -a NightShift\teradb To set this batch update to run automatically every night at 8:00 p.m., do the following: 1 From the Teradata Manager menu bar, click Administer>Teradata Manager. 2 Click the Scheduler tab. 3 Fill in the Name and Description boxes. 4 In the Command box, enter the command line for NightShift as listed above. 5 Under Schedule Type, select At a Specific Date/Time. 6 Ensure the Enabled check box is selected. 7 In the Hour field, enter In the Minute field, enter 0. 9 Click Add. 10 Click OK. Displaying the Performance Status of the Database After setting up an Alert Policy, use the Alert Viewer to display the status of the Database. To start the Alert Viewer 1 Connect to the server and ensure the Teradata Manager Service is running. To change logon settings, see Changing Logon Settings on page 78. To check the status of the Teradata Manager Service, see Checking the Status of the Teradata Manager Server on page From the Teradata Manager menu bar, click Investigate>Alert Viewer. The Modify Active List dialog box appears. Teradata Manager User Guide 247

248 Chapter 15: Using Alerts to Monitor Your System Alerting on Teradata Event Messages From Teradata Database V2R6.x on Windows Move one or more systems from the Available Systems list to the Active Systems list by first highlighting the item (highlight multiple items by holding <Shift> while clicking), then clicking Add. 4 Click OK. 5 The Alert Viewer window shows a tree structure containing your active systems. Click + next to a system or group in the left pane to expand the view. Click - to collapse the view. Do the following: Click each system (displayed as a top-level item in the tree structure in the left pane) to display the related system level data in the panel to the right. Click the second or third-level group items below each system to show the actual item together with the associated detail data. 6 Create a chart from any of the data points by doing one of the following: Move your cursor across the value fields on the main window. When the cursor changes to a hand shape (meaning the field contains chartable data) double-click the field to create a chart. From the Alert Viewer menu bar, click View>Chart, and select one of the chartable commands from the Chart submenu to create a chart for that item. Note: If the data for this system is being charted for the first time, the Alert Viewer opens the graph window and draws the data. If the data is being charted for the second time (or more), the Alert Viewer displays a Select Chart dialog box. If there are several charts associated with the one system, group the data. Alerting on Teradata Event Messages From Teradata Database V2R6.x on Windows 2000 Caution: This topic applies to Teradata Database V2R6.x. Skip this topic for Teradata Database or later. Follow this procedure to read an alert on Teradata Database event messages from an SMP Teradata Database running on Windows Detailed steps follow: 1 Set the security permissions 2 Set up the message DLLs 3 Configure the hostname (TPA node) 4 Start the Teradata Manager Service Note: For Windows and Linux V2R6.x MPP systems, use the alert mechanisms in Teradata Administration Workstation (AWS). For more information, see Teradata AWS User Guide. See Additional Information on page 6 to locate this resource. 248 Teradata Manager User Guide

249 Chapter 15: Using Alerts to Monitor Your System Alerting on Teradata Event Messages From Teradata Database V2R6.x on Windows 2000 To set the security permissions (Step 1 of 4) The Teradata Manager Service must be allowed access to the Windows (Application) event log on the Teradata Database (TPA node). Be sure to configure system parameters as described in Step 6 - Defining System Parameters on page 57 Verify the permissions, run the Windows 2000 Event Viewer program by doing the following: 1 Logon to your Teradata Manager server PC using the same logon credentials that was entered on the Configure Windows OS/Network Logon screen (from the Teradata Manager menu bar, click Administer>Teradata Manager, then click the System tab.) 2 Start the Event Viewer program. On Windows 2000 Professional, from the Windows desktop, click Start>Settings>Control Panel>Administrative Tools>Event Viewer. 3 Connect Event Viewer to the Teradata Database server (TPA node). On Windows 2000 Professional, right-click the Event Viewer item that appears in the left pane to display the shortcut menu, then select Connect to another computer. Enter the name of the TPA node and click OK. 4 Verify the Application log can be read. On Windows 2000 Professional, click the Application entry that appears in the left pane. If unable to view the TPA node's Application event log, check the following: The Windows user on the Teradata Manager server PC needs to have remote logon rights on the TPA node. Furthermore, this user's password must be valid and must match on both the Teradata Manager PC and on the TPA node, OR the TPA node must be configured to allow guest access. The Windows user on the Teradata Manager server PC must have read permission on the Application event log file on the TPA node. By default, the Application event log is located in the %SystemRoot%\SYSTEM32\CONFIG directory, in a file named APPEVENT.EVT. The security permissions on this file must allow at least READ access to the user whose credentials were entered into the Configure Windows OS/Network Logon screen. To set up the message DLLs (Step 2 of 4) Teradata Database messages (text strings) are stored in various DLLs on the TPA node. For the Alert Viewer to display message text for Teradata Database events, copy the DLLs onto your Teradata Manager server PC. Put the DLLs into the Teradata Manager bin directory, or any directory that is in your PATH. Note: Because the Teradata Manager Alert Policy identifies messages by event id rather than text description, the message DLLs are not required for proper operation of the alerting facility. However, the Alert Viewer cannot display complete message text if the message DLLs are not available. Teradata Manager User Guide 249

250 Chapter 15: Using Alerts to Monitor Your System Alerting on Policy Refresh Time Teradata Manager attempts to open the following message files for Teradata Database and PDE events: Table 90: Event Message Files Event Source Message File Location on TPA Node (Windows 2000) Teradata Database emflib.dll \program files\ncr\tdat\pde\<version>\bin, where <version> is the current version of Teradata software (for example, for a Teradata Database system, <version> is ) Tdat Tools libnetpde.dll \program files\ncr\tdat\pde\<version>\bin To configure the hostname -- TPA node (Step 3 of 4) Teradata Manager uses the name of the Teradata Database (the TDPID) as the hostname of the Windows 2000 system whose Application event log is to be opened. If the Teradata Database has been configured with a TDPID that differs from the Windows hostname, then do the following on the Teradata Manager server PC: 1 Start Notepad and open a new (empty) file. 2 Type the hostname of the TPA node. 3 Save the file as tm_evthost_<tdpid>.txt in the Teradata Manager bin directory, where <TDPID> is the name of the Teradata Database for which the Teradata Manager Service is running. For example, if your Teradata Database system is named TdatTest, the file name would be: tm_evthost_tdattest.txt. Note: The default location of the Teradata Manager bin directory is: \Program Files\NCR\Teradata Manager <version>\bin, where <version> is the current version of Teradata Manager (for example, 12.0). 4 Exit Notepad. To start the Teradata Manager Service (Step 4 of 4) For instructions on starting the Teradata Manager Service, see Checking the Status of the Teradata Manager Server on page 78. Alerting on Policy Refresh Time The Teradata Manager Service periodically reads alert policy information from the Teradata Database. If the read operation is unsuccessful over an extended period of time, a Policy Refresh Failed alert can be raised. 250 Teradata Manager User Guide

251 Chapter 15: Using Alerts to Monitor Your System Alerts Examples To define a Policy Refresh Failed alert 1 In the Alert Policy Editor, click the System tab to make it active. 2 Click to highlight the event in the pane, then use the Above box to set the Policy Refresh Time threshold in minutes. Caution: Changing the Policy Refresh Time threshold from its default setting is not recommended. Defining the threshold too low may cause extraneous alerts if the policy refresh queries become delayed during periods of heavy database usage. 3 Use the drop-down list to define the appropriate action to take for the Above condition. Alerts Examples Sending a Text Page The Teradata Manager Send a Page action supports numeric pages only. However, if your paging service provider supports delivery, an Alert Action can be defined using an address specified by your service provider. The alert is then relayed to your alphanumeric pager using the service provider. For example, for action Notify DBA, use the following settings: Physical Action - Send an Address @skytel.com Message - Teradata Database alert When executed, this action sends an alphanumeric message to the DBA's pager using the SkyTel service. Using Alerts for Session Management The built-in actions <Abort Session> and <Lower Priority> can be used to perform automatic session management on your Teradata Database system. Example 1 For example, to abort sessions that sit idle for more than 30 minutes, do the following: 1 In the Alert Policy Editor, click the Sessions tab. 2 Select the Idle for (Minutes) event. 3 Change the Above value to 30, and select <Abort Session> from the list. These settings cause a session to be aborted when all of the following are true: The session has been idle for more than 30 minutes, and The session is running in the DBC/SQL partition, and The UserName of the session is not on the Exceptions list. Teradata Manager User Guide 251

252 Chapter 15: Using Alerts to Monitor Your System Alerts Examples Example 2 To automatically lower the priority of sessions that consume significant CPU time and exhibit a large amount of CPU skew, do the following: 1 In the Alert Policy Editor, click the Sessions tab. 2 Select the CPU Skew % event. 3 Change the Above value to 60, and select <Lower Priority> from the list. 4 Change the And the CPU used on the most heavily used AMP is at least value to 5. These settings cause a session's priority to be set to '$L' when all of the following are true: The session's CPU Skew exceeds 60% It has used at least five seconds of CPU time on the most active AMP The UserName of the session is not on the Exceptions list Excluding Users from Alerts Monitoring The Alerts system generally ignores sessions for users that are on the Excluded Users list. However, all sessions are evaluated for the Blocked for (Minutes) alert, whether or not the session s username is on the Excluded Users list. To see the list of excluded users, click the Sessions tab, and click Exceptions to open the Excluded Users dialog box. Note: By default, sessions owned by DBC, DBCManager, and SystemFe are excluded from alerts. To add a user to the Excluded Users list, type the name into the User name field, then click Add. Type * as a wildcard character to match any sequence of zero or more characters. For example, tera*123 matches usernames tera123, teradata123, terasales123, and so forth. To remove a user, select the name from the Excluded Users list and click Delete. Click OK when finished with viewing or modifying the list. Your changes take effect when the policy is applied to the Database. Note: For the control session associated with Teradata utilities, only the Blocked for (Minutes) alert is evaluated and raised. Using the AlertRequest Table Any Teradata Database utility or user program can request an alert by inserting a row into the AlertRequest table in the Teradata Manager dbcmngr database. The Teradata Manager Service running on your Teradata Manager server PC monitors the AlertRequest table and executes the requested alerts. Upon successful completion of an alert action, Teradata Manager removes the corresponding row from the table. If an action fails, the row is not removed, and the system attempts to execute the action after the next refresh interval. 252 Teradata Manager User Guide

253 Chapter 15: Using Alerts to Monitor Your System Alerts Examples The AlertRequest table is defined as: Table 91: Alert Request Table Column Descriptions Column Type Description ReqDate Date Request date generated on the Teradata Database ReqTime Integer Request time generated on the Teradata Database JobName Char(60) Name of the requesting job Description Char(120) Text description of the event (reason for the alert) Value Integer Event value (if appropriate) ActionCode Char(1) Type of action being requested. The action codes are: E send an L write a log entry P send a page R run a program S send an SNMP TRAP T run a BTEQ script B display a banner + execute a logical action RepeatPeriod Smallint Minimum time (in minutes) between alerts for this event. Zero means always execute the alert. This value is ignored if the ActionCode is +. Destination Char(120) Address to which the alert is sent (for example, pager number or address). If ActionCode is +, this is the name of the logical action to be executed. Message Varchar(600) Message to be sent for this alert (for example, message or numeric page and callback number.) Requesting an Alert The following insert statement causes an message to be sent to the user named dba at mysite.com : insert dbcmngr.alertrequest values (date, time, Job1, Load job completed, 0, e, 20, [email protected], This message indicates that the load job completed! ); This action does not repeat within 20 minutes. Teradata Manager User Guide 253

254 Chapter 15: Using Alerts to Monitor Your System Alerts Examples The delivered message header and body look similar to this: From: Sent: Wednesday, May 23, :30 To: Subject: Alert for Job1 - Load job completed Using the MonitorRequest Table Date: 2002/05/23 Time: 09:30:01 DBS: teradb Utility: Job1 Datapoint: Load job completed Actual Value: 0 This message indicates that the load job completed! Any Teradata Database utility or user program can request that Teradata Manager monitor its progress by inserting rows into the MonitorRequest table in the Teradata Manager dbcmngr database. Each row includes fields that indicate the date and time by which the next row is inserted. If a new row is not inserted before the specified date and time, the Teradata Manager Service executes the specified alert action. When the job finishes, it inserts a final row containing a 0 (zero) value in the ActionCode column; this indicates the end of the monitor request. The MonitorRequest table is defined as: Table 92: Monitor Request Table Column Definitions Column Type Description MonitorId Char(60) A unique ID for the job: Date, StartTime, Host ID, and session id is recommended ActionDate Date Date before which the next row for this job is inserted ActionTime Integer Time before which the next row for this job is inserted JobName Char(60) Name of the requesting job EventValue Integer Any value to be displayed in the Alert Viewer, or included in the alert action. For example, if monitoring a load job, this could be the number of rows inserted so far. 254 Teradata Manager User Guide

255 Chapter 15: Using Alerts to Monitor Your System Alerts Examples Table 92: Monitor Request Table Column Definitions (continued) Column Type Description ActionCode Char(1) Type of action being requested. The action codes are: E send an L write a log entry P send a page R run a program S send an SNMP TRAP T run a BTEQ script B display a banner + execute a logical action 0 the job has completed (no alert is to be executed). Destination Char(120) Address to which the alert is sent (for example, pager number or address). If ActionCode is +, this is the name of the logical action to be executed. Message Varchar(600) Message to be sent for this alert Monitoring a Five Minute Job If a job takes five minutes to complete, but sometimes hangs due to lock conflicts, two additional steps can be added as follows: 1 Before the job, execute the following: insert dbcmngr.monitorrequest values ( , date, time+1000, My Job, 0, +, Page Admin, ); 2 After the job, execute the following: insert dbcmngr.monitorrequest values ( , date, time, My Job, 0, 0,, ); This tells Teradata Manager to execute the logical action Page Admin if the job does not finish within 10 minutes. Monitoring a Long-Running Job The MonitorRequest feature can also be used to send updated status information on longrunning jobs. In this context, the job would simply use Date and Time when inserting into the MonitorRequest table, thus forcing the designated alert action to be executed. The EventValue or Message fields can be used to indicate current status. Teradata Manager User Guide 255

256 Chapter 15: Using Alerts to Monitor Your System Alerts Examples For example, a big load job can notify an administrator of its progress by executing the following at regular intervals: insert dbcmngr.monitorrequest values ( , date, time, Load Job, , e, [email protected], ); The value might represent the number of rows loaded so far. Each time the job inserts a row, it inserts the latest row count in the EventValue column. 256 Teradata Manager User Guide

257 CHAPTER 16 System Administration The following topics provide information on the various system administration options available with your Teradata Manager software: Administering Workloads with Priority Scheduler Administrator Administering Using the Database Console (Remote Console) Administering System Alarms Using Alerts (Alert Policy Editor) Administering Using the BTEQ Window Administering Using Database Statistics (Statistics Collection) Administering Workloads with Priority Scheduler Administrator Priority Scheduler Administrator is a resource-management tool that provides an easy-to-use graphical interface where priority scheduler profiles can be defined and schmon scripts can be generated to implement these profiles. To start Priority Scheduler From the Teradata Manager menu bar, click Administer>Workload Management>Priority Scheduler. Instructions for using this program are in Chapter 14: Using Teradata Priority Scheduler Administrator. Administering Using the Database Console (Remote Console) Remote Console allows many Teradata Database console utilities to be run from your Teradata Manager PC. For more information, see Remote Console on page 293. Teradata Manager User Guide 257

258 Chapter 16: System Administration Administering System Alarms Using Alerts (Alert Policy Editor) To start Remote Console From the Teradata Manager menu bar, click Administer>Database Console. Instructions for using this program are in the Remote Console online help. Administering System Alarms Using Alerts (Alert Policy Editor) The Alert Policy Editor allows the DBA to define the actions that take place when Performance or Database Space events occur on one or more Teradata Database machines. These events are defined based on data collected from the following areas: PM Physical Resource data PM Virtual Resource data Database Space information Session information Teradata Database messages Event Combinations The collection rates for each type of data can be set independently by data type and machine. For more information, see Alert Policy Editor on page 288. For complete information on setting up the Alerts System, see Chapter 15: Using Alerts to Monitor Your System. To start Alert Policy Editor From the Teradata Manager menu bar, click Administer>Alert Policies. Instructions for using this program are in the Alert Policy Editor online help. Administering Using the BTEQ Window BTEQ Window is a unicode application that allows multiple BTEQ sessions to be run and different databases to be accessed simultaneously under Teradata Manager. Use BTEQ Window to: Select the charset for Database communication Run multiple BTEQ and DMTEQ sessions simultaneously Access multiple Databases simultaneously under Teradata Manager Scroll back the window display Save all BTEQ Window output to a file 258 Teradata Manager User Guide

259 Chapter 16: System Administration Administering Using Database Statistics (Statistics Collection) Use editing functions to modify a BTEQ or a SQL statement Re-send a BTEQ or a SQL statement to the Teradata Database without retyping Run a BTEQ script using drag and drop functionality To start a BTEQWIN session, select the session character set, and click OK in Select Session Charset dialog. Since a BTEQWIN session is always initiated by selecting the session charset using the Select Session Charset dialog box, the charset_id value as defined in the clispb.dat file does not process. For more information, see BTEQ Window on page 289. To start BTEQ Window From the Teradata Manager menu bar, click Administer>BTEQ Window. Instructions for using this program are in the BTEQ Window online help. Administering Using Database Statistics (Statistics Collection) Collecting statistics on a column or key field assists the query optimizer in choosing an execution plan that minimizes query time. Because the optimizer bases the execution plan on the actual values in the table, statistics can be updated whenever there have been a significant number of row additions or deletions. Use Statistics Collection to: Determine which tables have statistics Create statistics for columns or indexes Drop statistics by column/index, or for the entire table Update statistics for column/index, table, database, or the entire Teradata Database Also, this application helps create SQL scripts to collect or drop statistics. For more information, see Statistics Collection on page 296. To start Statistics Collection From the Teradata Manager menu bar, click Administer>Statistics Collection. Instructions for using this program are in the Statistics Collection online help. Teradata Manager User Guide 259

260 Chapter 16: System Administration Administering Using Database Statistics (Statistics Collection) 260 Teradata Manager User Guide

261 CHAPTER 17 Using the Scheduler Use the Teradata Manager scheduler to create tasks that launch programs automatically at the dates and times specified. The following topics provide information on how to use the scheduler, including examples: Introduction to the Scheduler Scheduling Tasks That Launch Applications Example 1: Scheduling a Task To Run Once a Day Example 2: Specifying the Days and Times Example 3: Specifying Multiple Daily Runs Introduction to the Scheduler Using the Interval Option Using the Calendar Option The scheduler runs as part of the Teradata Manager Service. Any scheduled application is launched on the host where the service is running. The Teradata Manager scheduler can be used to launch an application at a specific time or interval. Using the interval option, applications may be scheduled to run at a specific interval such as every 10 minutes, every four hours, or once per day. The interval option does not allow control of the specific time that the application is launched. The application is launched at exact intervals. So if an application scheduled to run every four hours starts at 4:34:05 a.m., it starts next at 8:34:05 a.m. Scheduling with the calendar option provides more flexibility than scheduling with intervals. Schedule an application to run once at a specific time and date, or use wildcards to create a schedule that runs your application at 17 and 47 minutes after the hour on weekdays between 8:00 a.m. and 5:00 p.m. Teradata Manager User Guide 261

262 Chapter 17: Using the Scheduler Introduction to the Scheduler Frequently Asked Questions The following are answers to some questions regarding the scheduler: Does my application run under my user ID? No, the application runs under the user ID of the Teradata Manager Service (a restricted user called Local System Account ). Does my application run on my PC? The application runs on the host where the Teradata Manager Service is installed. This may or may not be your PC. To determine where the Service is running, go to the Teradata Manager menu bar, and click Options>Change Logon Settings. I disabled my scheduled application, but it ran one more time. Why? The Teradata Manager Service checks for new or modified tasks in the dbcmngr.tmgrschedule table every 10 minutes. Can I run a BTEQ script? Do I need to include a logon string in the script? Yes, use BTEQ (if it is installed) or DMTEQ (installed by Teradata Manager). If using BTEQ, your script must include a.logon directive with a valid username and password. If using DMTEQ, the script logs on with the username and password the Teradata Manager Service used (the username is displayed on the System tab when choosing Administer>Teradata Manager). To change the username, use a.logon directive in your script. To access online help for DMTEQ, go to the \bin directory where Teradata Manager is installed, and double-click DMTEQ_ENU.HLP. If I run the Teradata Manager Service on two hosts, does my application run twice? Yes, if both services are monitoring the database where the schedule is saved. I want to run the same script on two Teradata Databases, how do I do that? a b Enter the data twice by logging onto the first database from tdclient and enter the data by clicking Administer>Teradata Manager, and click the System tab. Click Options>Change Database to switch to the second database. c Enter the data into the System tab from Administer>Teradata Manager. The data entered previously does not appear because it was stored in the first database. What are the differences between the Teradata Manager 5.x scheduler and Teradata Manager 7.x scheduler? 5.x scheduler runs in the TMGR Executive (GUI); 7.x scheduler runs in the TMGR Service. 5.x scheduled applications run on your PC; 7.x scheduled applications run on TMGR Service PC. 5.x schedules are stored on your PC; 7.x schedules are stored in a Database table. 5.x scheduler interface has Run Minimized options. 262 Teradata Manager User Guide

263 Chapter 17: Using the Scheduler Scheduling Tasks That Launch Applications Scheduling Tasks That Launch Applications The scheduler creates tasks that launch applications at specific times or intervals. To create a scheduled task 1 From the Teradata Manager menu bar, click Administer>Teradata Manager. 2 Click the Scheduler tab. 3 Do one of the following: To modify an existing task schedule, select the name of the schedule from the Name list. The Description and Command boxes can be edited. To add a new task schedule, select an existing schedule from the Name list that has similar attributes to the one to be added, then edit the name in the Name box to that of the new schedule. The Description and Command boxes can be edited. To delete an existing task schedule, select the name of the schedule from the Name list, then click Delete. Skip the rest of this procedure. Note: When configuring the schedule for a Teradata Manager Service Data Collection task, the Name list is preset and cannot be modified. 4 For the task schedule to be available when a user starts Teradata Manager, select the Enabled check box. 5 Under Schedule Type: a b For the scheduled task to repeat at regular intervals: i Select Repeat at Fixed Interval. ii Under Define Schedule, type the length of the interval in the Interval box (a numeric value between 0 and ) and select the interval units (Days, Hours or Minutes). For example, if 8 hours is entered, the task runs every eight hours. See Example 1: Scheduling a Task To Run Once a Day on page 264. To specify the dates and times the scheduled task is to execute, select At a Specific Date/ Time and enter the date and time parameters under Define Schedule. Type * in a box as a wildcard character to select all values for that period. For example, type * in the Year box to indicate that the task is eligible for execution every year. Input comma-separated values into the fields so the task executes at multiple dates and times. Click Choose next to a box to select specific values instead of entering them manually. See Example 2: Specifying the Days and Times on page 265 and Example 3: Specifying Multiple Daily Runs on page 265. Teradata Manager User Guide 263

264 Chapter 17: Using the Scheduler Example 1: Scheduling a Task To Run Once a Day 6 To limit the number of times the task can be started, type a number in the Lifetime number of starts box (a numeric value between 0 and 1000). To not set a start limit, enter 0. 7 Do one of the following: To modify an existing task, click Modify. To add a new task, click Add. 8 To run the scheduled task now, click Run Now. To run the task in the background while other things are being done, select the Minimized check box. To run the scheduled task later, click Close. Example 1: Scheduling a Task To Run Once a Day This example launches DMTEQ (the Teradata Manager version of BTEQ) to process the script daily.sql once per day. From the Teradata Manager menu bar, click Administer>Teradata Manager, then click the Scheduler tab, and fill in the dialog box as follows: Figure 8: Scheduling a task to run once a day 264 Teradata Manager User Guide

265 Chapter 17: Using the Scheduler Example 2: Specifying the Days and Times Example 2: Specifying the Days and Times This is the same script from Example 1: Scheduling a Task To Run Once a Day on page 264, but now the settings in Figure 9 show the script is only running on weekdays and at 15 minutes before midnight. Specify a range of days using a hyphen (for example, 2-6 represents Monday through Friday). From the Teradata Manager menu bar, click Administer>Teradata Manager, then click the Scheduler tab, and fill in the dialog box as follows: Figure 9: Scheduling a task to run once a day specifying the days and time Example 3: Specifying Multiple Daily Runs In this example, an application named sessions.exe is run every 15 minutes between the hours of 8AM and 5PM only on Mondays that are the first day of the month. Note: The use of a comma to separate multiple minute values. Also, the required full pathname for applications that are not located in the Teradata Manager bin directory. Teradata Manager User Guide 265

266 Chapter 17: Using the Scheduler Example 3: Specifying Multiple Daily Runs From the Teradata Manager menu bar, click Administer>Teradata Manager, then click the Scheduler tab, and fill in the dialog box as follows: Figure 10: Scheduling a task to run many times on a specified day 266 Teradata Manager User Guide

267 CHAPTER 18 Using the Performance Monitor Object This chapter describes how to use the Teradata Performance Monitor Object which is an ActiveX (COM) object that exposes methods to allow retrieval of PMPC data. Each method returns a collection of objects, each of which encapsulates the performance data for that object. It also provides for execution of the production control (action) functions of PMPC. The following topics provide information on how to use the Performance Monitor Object: Prerequisite Knowledge Application Distribution Requirements The Object Model Object Model Error Messages Prerequisite Knowledge The Performance Monitor object runs in both Visual Basic (VB) and C++ environments. To use this object in a new VB program From the VB menu bar, click Project>References to add a reference to it. It is located in the listbox under TeradataPerformance6. For more information on using the Monitor Object with VB, refer to the sample code in \<install_directory>\samples\vb\simplemon. To use this object in C++ 1 Include the files TDMon.h and TDMon_i.c in your source code. These files can be found in \<install_directory>\samples\vc\simpmon. Your code must call the function CoInitialize() to prepare for the use of COM objects. For more information, refer to the sample application in the directory mentioned above. 2 If all components will be executed from this directory, add the \<install_directory>\bin directory to your path (this also applies during debugging). This allows the object to find its required support files. Teradata Manager User Guide 267

268 Chapter 18: Using the Performance Monitor Object Application Distribution Requirements Object Modes Object Scope The Monitor object can be used in two modes. Control the mode by setting the UseClient property. The default setting is set to False. Direct mode In direct mode all data is fetched directly from the Teradata Database. A session must be established using the Connect method before calling any of the data retrieval or action methods. Client mode Initially in Client mode, a Database session is temporarily established to retrieve some control information. After this information is obtained, the session is disconnected and all future data is retrieved from a Teradata Manager server. A session does not need to be established on the Teradata Database. Start client mode by setting UseClient to True. To ensure communication is established and that data entered is retrieved from the Teradata Manager server, check the value of the UseClient property after setting it to ensure it is set to True. In general, create a Monitor object at application startup and destroy it (in VB set the object = Nothing) at program termination. The GetSessionData function uses an internal cache that allows the object to calculate CurrentCPU, Time Blocked, and Time Idle. If the object is destroyed and re-created, these values reset to zero. This internal cache applies only when running in direct mode. Although the object itself issues the DisConnect and Client Shutdown if necessary, it is good practice to specifically call Disconnect, or to set UseClient to False. Sample Files There are sample files included with the Teradata Manager installation to help with the Object Model. These samples are in: \<install_directory>\samples. Application Distribution Requirements Required Files The object model can be run in both client and direct modes on any machine that has Teradata Manager installed. To run the application on a machine that does not have Teradata Manager installed, ensure the following files are installed on your machine. 268 Teradata Manager User Guide

269 Chapter 18: Using the Performance Monitor Object Application Distribution Requirements Required Microsoft Support Files asycfilt.dll comcat.dll comctl32.ocx comdlg32.ocx mfc42u.dll mfc71u.dll msvbvm60.dll msvcrt.dll msvcr71.dll msvcr80.dll oleaut32.dll olepro32.dll stdole2.tlb Note: The required versions of these support files are distributed with the current release of Teradata Manager. Table 93: Required Teradata Manager Support Files Required Teradata Manager Support Files tdapp.dll tdis.dll tdmfcis.dll tdwmutil.dll ncrtmgr.dll mgrcli.dll monpm.dll Table 94: Required Third Party Support Files Required Third Party Support Files gsprop32.dll gswag32.dll gswdll32.dll fpspru70.ocx File Registration Ensure the files in Table 93 and Table 94 are on your machine and register TDMon6.dll. Note: The following files also need to be registered if they were added to the target system: COMCTL32.OCX COMDLG32.OCX FPSPRU70.OCX MFC42U.DLL Teradata Manager User Guide 269

270 Chapter 18: Using the Performance Monitor Object The Object Model MFC71U.DLL MSVBVM60.DLL OLEAUT32.DLL OLEPRO32.DLL To register TDMon6.dll Execute the following command to register TDMon6.dll: regsvr32 TDMon6.dll Note: The application regsvr32.exe is a Microsoft application. The file TDMon6.dll must be prefixed by its full path if the command is not executed from within the directory that contains the file. The Object Model This section describes the makeup of the Object Model. When reading the model descriptions, note that the fonts have these meanings: Font Plain Italic Bold Meaning Property Read Only Property (optional parameter) Method Table 95: Monitor (Object) Descriptions Monitor (Object) AppName IdNames Password Server System UserID UseClient Description The name of your application (no blanks). If True, Table and Database names are reported for blocked sessions. If False, Table and Database Ids are displayed. The password used to establish the connection. The name of the Teradata Manager server from where your data is fetched. Used in Client mode only. The system to connect to or are connected to. The User ID used to establish the connection. If True, the data is fetched from a Teradata Manager server. If False, the data is fetched directly from the Teradata Database. 270 Teradata Manager User Guide

271 Chapter 18: Using the Performance Monitor Object The Object Model Table 95: Monitor (Object) Descriptions (continued) Monitor (Object) Connected MonitorVersion Profile Connect (System, UserName, Password, Account, Authentication Mechanism, Mechanism Data) Disconnect () GetQueryBands (Host, Session, PE) GetVprocSummary () GetNodeSummary () GetVprocDetail (PEs) GetNodeDetail () GetSessionData (Host) GetSessionSQL (Host, Session, RunVproc, CurStep1 CurStep2, Steps) GetWorkloads () AbortSession (Host, SessionOrUserName) Description Indicates if this monitor object is currently connected to a Teradata system. Highest Teradata PM/API version available on the connected system. Name of the Teradata Manager profile that launched this application. A null string if launched independently. This method connects to a Teradata Database with optional parameters for System, User Name, Password, Account, Authentication Mechanism, and Mechanism Data. For more information, see Setting the Security Mechanism and Character Set on page 83. This method disconnects from a Teradata Database. This method returns the query band information set for a session, including those set at both the session and transaction levels. This method returns a VprocSummary object. This method returns a NodeSummary object. This method returns an AMPs collection. Passing in a reference to a PEs collection is required. The method populates this collection. This method returns a Nodes collection. This method returns a Sessions collection. The Host parameter is optional. If specified, it returns only those sessions connected from that Host Id. Specify -1 to return all sessions. This method returns the SQL for a specific session. It also returns the Explain Step information and tells which step(s) are currently executing. Note: This only works for relatively long running queries since the query must still be running when the GetSessionSQL() function is called. This is real-time data. To improve performance, specify the RunVproc as the third parameter. That is the ID of the PE that is controlling the session. If this information is unavailable, specify zero. This method returns a Workloads collection that contains all the currently-enabled workloads. Note: The collection may be empty. This method aborts and logs off a session. Teradata Manager User Guide 271

272 Chapter 18: Using the Performance Monitor Object The Object Model Table 95: Monitor (Object) Descriptions (continued) Monitor (Object) ModifyAccount (Host, Session, NewAccount, CurrentRequestOnly) ModifyWorkload (Host, Session, RunVproc, NewID, CurrentRequestOnly) ReleaseSession (Host, Session, RequestID, WorkloadID, CurrentRequestOnly) SetNodeMonitorRate (Rate) SetVprocLoggingRate (Rate) SetVprocMonitorRate (Rate) SetNodeLoggingRate (Rate) SetSessionRate (Rate, SetLocalRate) Description This method modifies an account. This can be used to change the priority of a session. Method that moves a session into a different workload if the database is classifying sessions by workload. Method that releases a session from the delay queue. Method that sets the monitor rate of the node. Method that sets the logging rate of the vproc. Method that sets the monitor rate of the vproc. Method that sets the logging rate of the node. Method that sets the session rate with an optional parameter to set the local rate. Table 96: VprocSummary Descriptions VprocSummary (Not Creatable) Description AvgAMPUse The average CPU usage across all AMPs (%). AvgPEUse The average CPU usage across all PEs (%). AvgDiskUse The average Disk usage across all AMPs (%). AvgDiskIOs The average number of disk I/Os on each AMP. HiAmpUse The highest CPU usage on any AMP (%). HiAmpNode HiAmp The node running the AMP with the highest CPU usage. The AMP with the highest CPU usage. LoAmpUse The lowest CPU usage on any AMP (%). LoAmpNode LoAmp The node running the AMP with the lowest CPU usage. The AMP with the lowest CPU usage. HiPeUse The highest CPU usage on any PE (%). HiPeNode HiPe The node running the PE with the highest CPU usage. The PE with the highest CPU usage. LoPeUse The lowest CPU usage on any PE (%). LoPeNode The node running the PE with the lowest CPU usage. 272 Teradata Manager User Guide

273 Chapter 18: Using the Performance Monitor Object The Object Model Table 96: VprocSummary Descriptions (continued) VprocSummary (Not Creatable) LoPe Description The PE with the lowest CPU usage. HiDiskUse The highest disk usage on any AMP (%). HiDiskNode HiDiskAmp The node running the AMP with the highest disk usage. The AMP with the highest disk usage. LoDiskUse The lowest disk usage on any AMP (%). LoDiskNode LoDiskAmp HiDiskIOs HiDiskIONode HiDiskIOAmp LoDiskIOs LoDiskIONode LoDiskIOAmp SessionCount SessionRateLocal SessionRateSystem VprocLoggingRate VprocMonitorRate Version TDRelease The node running the AMP with the lowest disk usage. The AMP with the lowest disk usage. The highest number of disk IOs on any AMP. The node running the AMP with the highest number of disk IOs. The AMP with the highest number of disk IOs. The lowest number of disk IOs on any AMP. The node running the AMP with the lowest number of disk IOs. The AMP with the lowest number of disk IOs. The number of sessions currently logged onto the system. The frequency (in seconds) at which session data is collected (by this monitor session only). The frequency (in seconds) at which session data is collected (system wide). The frequency (in seconds) at which AMP and PE data is written to the ResUsage tables. The frequency (in seconds) at which AMP and PE data is collected. The Teradata PDE software version. The Teradata Database software release number. Table 97: Node Summary Descriptions NodeSummary (Not Creatable) Description AvgCpuUse The average CPU usage across all nodes (%). AvgDiskUse The average disk usage across all nodes (%). AvgDiskIOs The average number of disk I/Os on each node. HiCPUUse The highest CPU usage on any node (%). Teradata Manager User Guide 273

274 Chapter 18: Using the Performance Monitor Object The Object Model Table 97: Node Summary Descriptions (continued) NodeSummary (Not Creatable) HiCPUNode Description The node with the highest CPU usage. LoCPUUse The lowest CPU usage on any node (%). LoCPUNode The node with the lowest CPU usage. HiDiskUse The highest disk usage on any node (%). HiDiskNode The node with the highest disk usage. LoDiskUse The lowest disk usage on any node (%). LoDiskNode HiDiskIOs HiDiskIONode LoDiskIOs LoDiskIONode The node with the lowest disk usage. The highest number of disk IOs on any node. The node with the highest number of disk IOs. The lowest number of disk IOs on any node. The node with the lowest number of disk IOs. AvgBynetUse The average Bynet usage across the nodes (%). BynetCount BynetsActive NodeLoggingRate NodeMonitorRate Version TDRelease The total number of Bynets defined in the system. The number of Bynets that are active. The frequency (in seconds) at which node data is written to the ResUsage tables. The frequency (in seconds) at which node data is collected. The Teradata PDE software version. The Teradata Database software release number. Table 98: AMPs Descriptions AMPs (Collection / Not Creatable) AvgCpuUse MaxCpuUse ParallelEfficiency BynetCount BynetsActive MonitorRate Count Description The average CPU use across all AMPs in the system. The highest CPU use on any AMP in the system. The parallel efficiency across all AMPs in the system. 100 is perfect parallelism. The total number of Bynets defined in the system. The number of Bynets that are active. The interval (in seconds) over which this data was collected. The number of items in the collection. 274 Teradata Manager User Guide

275 Chapter 18: Using the Performance Monitor Object The Object Model Table 98: AMPs Descriptions (continued) AMPs (Collection / Not Creatable) Item Description The item in the collection. Note: This property is not directly used. Table 99: AMP (Object) Descriptions AMP (Object) Key (AMP Number) NodeId Status Description The vproc ID of this AMP. The ID of the node this AMP is running on. The status of this AMP: U means the AMP is up. D means the AMP is down. CpuUse The percentage of CPU used by this AMP. It may exceed 100%. AmpWorkerUse SystemUse DiskUse DiskReads DiskWrites AvgDiskRequests MemSegsAllocated MemKBAllocated NetReads NetWrites Cluster RunCount BackupSegsAllocated The percentage of CPU time the AMP worker tasks use. It may exceed 100%. The percentage of CPU time used performing system tasks. It may exceed 100%. The percentage of time this AMP had outstanding disk requests. The number of disk reads the AMP issues during the sample period. The number of disk writes the AMP issues during the sample period. The average number of outstanding disks requests for this AMP. The number of memory segments allocated for this AMP during the sample interval. The number of kilobytes of memory allocated for this AMP. The number of messages read from the Bynet during the sample interval. The number of messages written to the Bynet during the sample interval. The cluster this AMP s disks have been assigned to. The number of sessions initiating requests to this AMP. The number of disk segments written to backup storage. Teradata Manager User Guide 275

276 Chapter 18: Using the Performance Monitor Object The Object Model Table 100: PEs Descriptions PEs (Collection / Not Creatable) AvgCpuUse MaxCpuUse Count Item Description The average CPU use across all PEs in the system. The highest CPU use across all PEs in the system. The number of items in the collection. The item in the collection. Note: This property is not directly used. Table 101: PE Object Descriptions PE Object Key (PE Number) NodeId Status HostId LogonCount RunCount Description The vproc ID of this PE. The ID of the node that this PE is running on. The status of this PE: U means the PE is up. D means the PE is down. The logical Host Id associated with this PE. The number of sessions logged on to this PE. The number of sessions initiating requests to this PE. CpuUse The percentage of CPU used by this PE. It may exceed 100%. SystemUse The percentage of CPU time used performing system tasks. It may exceed 100%. ParserUse The percentage of CPU time the parser uses. It may exceed 100%. DispatcherUse CICUse HostReads HostWrites MemSegsAllocated MemKBAllocated NetReads NetWrites The percentage of CPU time the dispatcher uses. It may exceed 100%. The percentage of the Channel Interface Controller used by this PE. The number of Host Message Blocks the PE reads during the sample period. The number of Host Message Blocks the PE writes during the sample period. The number of memory segments allocated for this PE. The number of kilobytes of memory allocated for this PE. The number of messages read from the Bynet during the sample interval. The number of messages written to the Bynet during the sample interval. 276 Teradata Manager User Guide

277 Chapter 18: Using the Performance Monitor Object The Object Model Table 102: Nodes Descriptions Nodes (Collections / Not Creatable) AvgCpuUse MaxCpuUse AvgDisk Use MaxDiskUse AvgBynetUse ParallelEfficiency BynetCount BynetsActive MonitorRate Count Item Description The average CPU use across all nodes in the system. The highest CPU use on any node in the system. The average disk use across all nodes in the system. The highest disk use on any node in the system. The average Bynet use across all nodes in the system. The parallel efficiency across all nodes in the system. 100 is perfect parallelism. The total number of Bynets defined in the system. The number of Bynets that are active. The interval (in seconds) over which this data was collected. The number of items in the collection. The item in the collection. Note: This property is not directly used. Table 103: Node (Object) Descriptions Node (Object) Key (Node Id) AmpCount PeCount Status CpuUse IOWaitUse SystemUse UserUse BynetUse DiskUse CICUse Description The Node Id of this node. Format ccc-nn where ccc is the cabinet number. The number of AMPs executing on this node. The number of PEs executing on this node. The status of this node: U means the node is up. D means the node is down. The percentage of CPU used on this node. The percentage of CPU time spent waiting for IO to complete while the CPU is idle. The percentage of CPU time used in performing system tasks. The percentage of CPU time in executing user code. The percentage of time the Bynets are busy. The percentage of time this node had outstanding disk requests. The percentage of the Channel Interface Controller used by this node. Teradata Manager User Guide 277

278 Chapter 18: Using the Performance Monitor Object The Object Model Table 103: Node (Object) Descriptions (continued) Node (Object) DiskReads DiskWrites AvgDiskRequests HostReads HostWrites SwapReads SwapWrites SwapDrops MemSegsAllocated MemKBAllocated MemAllocateFailed MemSegsAged NetReads NetWrites BackupSegs Allocated BackupKBAllocated BackupSegsAged Description The number of disk reads the AMPs issue on this node during the sample period. The number of disk writes the AMPs issue on this node during the sample period. The average number of outstanding disk requests for the AMPs on this node. The number of Host Message Blocks the PEs read during the sample period. The number of Host Message Blocks the PEs write during the sample period. The number of pages read from the swap area during the sample interval. The number of pages written to the swap area during the sample interval. The number of swap pages dropped from memory during the sample interval. The number of memory segments allocated on this node during the sample interval. The number of kilobytes of memory allocated on this node. The number of memory allocation attempts that failed during the sample interval. These are temporary failures. The number of memory segments that were flushed from memory during the sample interval. The number of messages read from the Bynet during the sample interval. The number of messages written to the Bynet during the sample interval. The number of disk segments read for backup storage during the sample interval. The number of kilobytes read for backup storage during the sample interval. The number of backup disk segments flushed from memory during the sample interval. 278 Teradata Manager User Guide

279 Chapter 18: Using the Performance Monitor Object The Object Model Table 104: Sessions Descriptions Sessions (Collection / Not Creatable) MonitorRate Count Item Description The interval (in seconds) over which this data was collected. The number of items in the collection. The item in the collection. Note: This property is not directly used. Table 105: Session (Object) Descriptions Session (Object) Key (HostId/Session) SessionNum HostId UserName Partition Priority Account LogonPE RunVproc LogonDateTime LogonSequence LogonSource PEState AMPState TotalPeCpu TotalAmpCpu TotalAmpIO CurrentAmpCpu SpoolSpace Description The host or session that uniquely identifies this session. The Teradata session number for this session. The Host Id from which this session was initiated. The name of the Teradata user who initiated this session. The partition in which this session is executing (DBC/SQL, Monitor, FastLoad, and so forth). The priority at which this session is currently executing. The account under which this session is executing. The ID of the PE that this session logged on to. The ID of the PE/AMP to which this session is sending requests. The date and time at which this session logged on. The logon sequence number of this session. This value is used to relate a set of sessions that were logged on for a single job. It is zero if only one session was logged on. This string identifies the origin of the session. The available data varies by host and connection interface. The current state of the session from the PE. The current state of the session from the AMP. The total CPU time used on the PE by this session. The total CPU time used on the AMPs by this session. The total number of disk IOs the AMPs perform for this session. The CPU time used on the AMPs during the current collection interval by this session. The spool space allocated for this session. Teradata Manager User Guide 279

280 Chapter 18: Using the Performance Monitor Object The Object Model Table 105: Session (Object) Descriptions (continued) Session (Object) TempSpace TransactionCount RequestCacheHits RequestCount RequestCpu RequestID RequestIO RequestStart TimeIdle TimeBlocked Blocks MoreBlockers AmpCount AmpSkew DiskSkew AvgAmpCpu AvgAmpIO HighAmpCpu1 HighAmpCpu2 HighAmpCpu3 Description The total temporary space allocated for this session. The total number of transactions processed by this session. The number of times a request was found already in the cache of the parser. The total number of requests processed by this session. The CPU time used on the AMPs during processing of the current request. The ID of the request that is currently executing in this session. The number of disk IOs the AMPs perform for the current request. The date and time at which the current request started processing. The length of time that this session has remained in an idle state (in seconds). The length of time that this session has been blocked (in seconds). A collection containing zero to three Block objects. Each Block contains information about a session that is blocking this session. If True, more than three sessions are blocking this session. The Teradata Database only reports the first three. The number of AMPs involved in processing requests from this session during the current collection interval. The CPU skew factor (non-parallelism) across the AMPs during the current collection interval. The range is from 0 to 100. Calculated as 100 * (1 - (AvgAMPCpu / HighAMPCpu). The disk skew factor (non-parallelism) across the disks during the current collection interval. The range is from 0 to 100. Calculated as 100 * (1 - (AvgAMPIO / HighDiskIO). The average CPU usage across all participating AMPs for this session during the current collection interval. The average number of diskios across all participating AMPs for this session during the current collection interval. The CPU usage of the AMP that performed the most work for this session during the current collection interval. The CPU usage of the AMP that performed the second most work for this session during the current collection interval. The CPU usage of the AMP that performed the third most work for this session during the current collection interval. 280 Teradata Manager User Guide

281 Chapter 18: Using the Performance Monitor Object The Object Model Table 105: Session (Object) Descriptions (continued) Session (Object) LowAmpCpu1 LowAmpCpu2 LowAmpCpu3 HighAmp1 HighAmp2 HighAmp3 LowAmp1 LowAmp2 LowAmp3 HighDiskIO1 HighDiskIO2 HighDiskIO3 LowDiskIO1 LowDiskIO2 LowDiskIO3 HighDiskAmp1 HighDiskAmp2 HighDiskAmp3 LowDiskAmp1 Description The CPU usage of the AMP that performed the least work for this session during the current collection interval. The CPU usage of the AMP that performed the second least work for this session during the current collection interval The CPU usage of the AMP that performed the third least work for this session during the current collection interval The AMP that performed the most work for this session during the current collection interval. The AMP that performed the second most work for this session during the current collection interval. The AMP that performed the third most work for this session during the current collection interval. The AMP that performed the least work for this session during the current collection interval. The AMP that performed the second least work for this session during the current collection interval. The AMP that performed the third least work for this session during the current collection interval. The number of IOs the AMP issues that perform the most disk access for this session during the current collection interval. The number of IOs the AMP issues that perform the second most disk access for this session during the current collection interval. The number of IOs the AMP issues that perform the third most disk access for this session during the current collection interval. The number of IOs the AMP issues that perform the least disk access for this session during the current collection interval. The number of IOs the AMP issues that perform the second least disk access for this session during the current collection interval. The number of IOs the AMP issues that perform the third least disk access for this session during the current collection interval. The AMP that performed the most disk access for this session during the current collection interval. The AMP that performed the second most disk access for this session during the current collection interval. The AMP that performed the third most disk access for this session during the current collection interval. The AMP that performed the least disk access for this session during the current collection interval. Teradata Manager User Guide 281

282 Chapter 18: Using the Performance Monitor Object The Object Model Table 105: Session (Object) Descriptions (continued) Session (Object) LowDiskAmp2 LowDiskAmp3 Workload WorkloadID ClassifiedBy AbortSession (AllUserSessions) GetQueryBands () GetSQL (CurStep1, CurStep2, PlanSteps) ModifyAccount (NewAccount, CurrentOnly) ModifyWorkload (NewWorkId, CurrentOnly) ReleaseSession () ShowQueryBands () ShowSkew () ShowSQL () Description The AMP that performed the second least disk access for this session during the current collection interval. The AMP that performed the third least disk access for this session during the current collection interval. The name of the workload that this session is running under. Null if workload classification is not in effect. The ID of the workload that this session is running under. Who classified the session into this workload. 0 means the system classified the session. 1 means the DBA re-classified this request and all future requests. 2 means the DBA re-classified this request only. Method that aborts and logs off this session. If AllUserSessions is True, it deletes all the sessions owned by the user that this session belongs to. Method that returns the query band information set for this session or transaction. Method that returns the SQL for this session. It also returns the Explain Step information and tells which step(s) are currently executing. Note: This only works for relatively long running queries since the query must still be running when the GetSQL() function is called. This is real-time data. Method that modifies the account. This can be used to change the priority of the session. If CurrentOnly is True, it changes the account for the current request only. If it is False or omitted, it changes the account for all future requests also. Method that moves the session into a different workload if the database is classifying sessions by workload. If CurrentOnly is True, it changes the workload for the current request only. If it is False or omitted, it changes the workload for all future requests also. Method that releases this session from the delay queue. Method that displays the query bands currently set for this session or transaction. Method that shows skew (workload imbalance) for this session. Method that shows the SQL and Explain text for this session. 282 Teradata Manager User Guide

283 Chapter 18: Using the Performance Monitor Object The Object Model Table 106: Blocks Descriptions Blocks (Collection / Not Creatable) Count Item Description The number of items in the collection. The item in the collection. Note: This property is not directly used. Table 107: Block (Object) Descriptions Block (Object) SessionNum HostId Severity LockType Granted UserName DbName TableName Description The session number that is causing this block. The Host Id from which the blocking session connected. The severity of the lock - Access, Read, Write, Exclusive. The scope of the lock - Database, Table, RowHash. If True, this session holds the lock. If False, it is waiting for the lock, but is ahead of the parent session in the lock queue. The name of the user causing this block. The database in which the lock has been requested. The table in which the lock has been requested. The value is null if it is a database level lock. Table 108: Steps Descriptions Steps (Collection / Not Creatable) Count Item Description The number of items in the collection. The item in the collection. Note: This property is not directly used. Table 109: Step (Object) Descriptions Step (Object) StepNum EstimatedTime ActualTime Description The parallel step number. The estimated time (in seconds) that this step will take. The actual time (in seconds) that this step took. It states -1 if the step has not completed. Teradata Manager User Guide 283

284 Chapter 18: Using the Performance Monitor Object The Object Model Table 109: Step (Object) Descriptions (continued) Step (Object) EstimatedIOs ActualIOs Confidence StepText Description The estimated number of IOs that this step will perform. The actual number of IOs that this step performed. It states -1 if the step has not completed. 0 means no confidence in the estimates. 1 means some confidence. 2 means high confidence. A description of the work performed by this step. Table 110: Workloads Descriptions Workloads (Collection / Not Creatable) Count Item Description The number of items in the collection. The item in the collection. Note: This property is not directly used. Table 111: Workload (Object) Descriptions Workload (Object) ID Name Description The ID number of the workload. The name of the workload. Table 112: Query Bands Descriptions Query Bands (Collection/Not Creatable) Count Item Description The number of items in the collection. The item in the collection. Note: This property is not directly used. 284 Teradata Manager User Guide

285 Chapter 18: Using the Performance Monitor Object Object Model Error Messages Table 113: Query Band (Object) Descriptions Query Band (Object) Level Name Value Description The query band level. S means session. T means transaction. The query band pair name. The query band pair value. Object Model Error Messages The following table describes the possible error messages that may be generated by running the Performance Monitor. Table 114: Object Model Error Messages Error Code Message CLI runtime not found Already connected System, UserId or Password is not set Error returned from Teradata Manager server Invalid server name - DNS lookup failed The Teradata Manager Service is not running on this server Not authorized to use this Teradata Manager Service The system can not be changed when running under a Teradata Manager profile No request is currently active on this session Parameter 2 must be the session number (Long) or UserName (String) Invalid parameter passed to <Method Name> The session rate must be in the range 6 to 3600, or The resource rate must be an integer divisor of 3600, or Data in unavailable due to a rate change or restart Not connected to a Teradata Database system, or using client mode This server is not currently monitoring database <name> Teradata Manager User Guide 285

286 Chapter 18: Using the Performance Monitor Object Object Model Error Messages Note: Messages between and are four-digit Teradata Database error codes with a 1 appended at the start. For example, Message would be returned for Teradata Database error code Teradata Manager User Guide

287 CHAPTER 19 Teradata Manager Applications This chapter lists the applications that are included with Teradata Manager. The following is a list of topics with a brief description of each application: Alert Policy Editor Define the actions that take place when specific events occur on your Teradata Database machines. Alert Viewer View the overall system performance of your Teradata Database systems from a single view point. BTEQ Window Load and extract data from the Teradata Database using BTEQ with a windows interface. Configuration Check Collect configuration information related to an associated Teradata Database and stores it on the client PC. Error Log Analyzer Investigate the Teradata Database error log. Locking Logger Determine whether system performance has degraded by an inappropriate mix of SQL statements using a table of information extracted from the transaction logs. LogOnOff Usage View daily, weekly, and monthly logon statistics based on information in the DBC LOGONOFF view on the Teradata Database. Database Setup Set up the Database to run Teradata Manager. Priority Scheduler Administrator Control the allocation and consumption of resources available to the Teradata Database. Remote Console Run many of the Teradata Database console utilities from your Teradata Manager PC. Session Information Get information on session status, modify session priority, view blocking or blocked sessions, change session priority. Statistics Collection Create, drop and update statistics for the Teradata Database. Teradata Performance Monitor Analyze the performance of a Teradata Database machine and to perform related control functions on that machine. Teradata Manager User Guide 287

288 Chapter 19: Teradata Manager Applications Alert Policy Editor Alert Policy Editor Start Alert Policy Editor The Alert Policy Editor allows the DBA to define the actions that take place when Performance or Database Space events occur on one or more Teradata Database machines. These events are defined based on data collected from the following areas: PM Physical Resource data PM Virtual Resource data Database Space information Session information Teradata Database messages Event Combinations The collection rates for each type of data can be set independently by data type and machine. Note: Alert Policy Editor does not connect to the Teradata Database by logging into the Teradata Manager server. Even if the Teradata Manager client is in client-server mode, the Alert Policy Editor always connects in direct mode. The Alert Policy Editor does not operate from outside a firewall. To start Alert Policy Editor From the Teradata Manager menu bar, click Administer>Alert Policies. Alert Viewer How It Works The Alert Viewer provides the user with a single view point on the overall system performance of a Teradata Database system. Through the easy to use graphical user interface and colored icons, users can easily drill down from an overall picture to identify the problem area, possibly preventing a hazardous situation. The Alert Viewer also provides a graphing function, enabling a graph to display for any data point value by simply clicking on it. Each profile is displayed as a top-level item in a tree structure, with the related system level data displayed in the panel to the right. Below each profile are the group items for Nodes, Vprocs, Sessions, Database Events, Monitor Alerts, and Alert Requests. These second level items display a List View of third level items consisting of Nodes, Vprocs or Sessions. For example, the Nodes group item displays the number of Node records below it. The third level shows the actual node, vproc or session together with the associated detail data. 288 Teradata Manager User Guide

289 Chapter 19: Teradata Manager Applications BTEQ Window Start Alert Viewer To start Alert Viewer From the Teradata Manager menu bar, click Investigate>Alert Viewer. BTEQ Window Start BTEQ Window BTEQ Window is a Unicode application giving the ability to run multiple BTEQ sessions and access different databases simultaneously under Teradata Manager. Use BTEQ Window to: Select the charset for Database communication Run multiple BTEQ and DMTEQ sessions simultaneously Access multiple Databases simultaneously under Teradata Manager Scroll back the window display Save all BTEQ Window output to a file Use editing functions to modify a BTEQ or a SQL statement Re-send a BTEQ or a SQL statement to the Teradata Database without retyping Run a BTEQ script using drag and drop functionality Note: The session character set cannot be changed to or from UTF-16. Use the character set name when executing.set SESSION CHARSET from BTEQWIN. Do not use a numeric code. Note: BTEQ Window does not connect to the Teradata Database by logging into the Teradata Manager server. Even if the Teradata Manager client is in client-server mode, the BTEQ Window always connects in direct mode. The BTEQ Window does not operate from outside a firewall. To start BTEQ Window 1 From the Teradata Manager menu bar, click Administer>BTEQ Window. 2 Select the session character set, and click OK. Since a BTEQWIN session is always initiated by selecting the session charset, the charset_id value as defined in the clispb.dat file does not process. Teradata Manager User Guide 289

290 Chapter 19: Teradata Manager Applications Configuration Check Configuration Check Start Configuration Check Configuration Check is a Teradata Manager utility that collects configuration information related to an associated Teradata Database and stores it on the client PC. Locking Logger runs Configuration Check automatically to create the dbconfig.dat file. If the number of nodes, AMPs, or PE vprocs changes on the database server, delete the dbconfig.dat file so it can automatically regenerate with the correct configuration specifications. Note: Configuration Check does not connect to the Teradata Database by logging into the Teradata Manager server. Even if the Teradata Manager client is in client-server mode, Configuration Check always connects in direct mode. Configuration Check does not operate from outside a firewall. To start Configuration Check This program does not appear on any of the Teradata Manager menus. Before starting Configuration Check, add the application to the Teradata Manager menu using the procedure, Adding Additional Applications to the Teradata Manager Menu Bar on page 81. From your local menu, click cchk.exe. Error Log Analyzer Use Error Log Analyzer (ELA) to view the error log system tables on the Teradata Database. The log tables can be viewed by Category, Message Screen, and Reports. The Teradata Database monitors software error events and logs error messages into the dbc.software_event_log. The ELA macros included with the Teradata Manager include AllRestarts, BynetEvents, DiskEvents, EventCount, LogHistory, MemEvents, MiniCylPacks, PackDisk and RestartLogonEvents. Error Log Analyzer only works with a Teradata Database running on Unix MPRAS. Note: ELA does not connect to the Teradata Database by logging into the Teradata Manager server. Even if the Teradata Manager client is in client-server mode, ELA always connects in direct mode. ELA does not operate from outside a firewall. 290 Teradata Manager User Guide

291 Chapter 19: Teradata Manager Applications Locking Logger Start Error Log Analyzer To start Error Log Analyzer From the Teradata Manager menu bar, click Investigate>Error Log. Locking Logger The Teradata Manager Locking Logger application is a graphical user interface to the Locking Logger console utility of the Teradata Database software. When Locking Logger is enabled, the Teradata Database maintains ongoing logs of: Transaction identifiers Session identifiers Lock object identifier Lock levels associated with executing SQL statements which have been delayed because of database lock contention Application The Locking Logger application runs the Locking Logger console utility which creates a table of information extracted from the transaction logs. The Locking Logger application can then use this table to create a report that helps determine whether system performance has been degraded by an inappropriate mix of SQL statements. Note: Locking Logger does not connect to the Teradata Database by logging into the Teradata Manager server. Even if the Teradata Manager client is in client-server mode, Locking Logger always connects in direct mode. Locking Logger does not operate from outside a firewall. Enabling Locking Logger Enable the Locking Logger option before using the Teradata Manager Locking Logger application. Modify the Database Control Record by running the dbscontrol console utility using Remote Console, and then restart the system. Warning: To use Locking Logger, the database user must have the necessary database privileges. Ensure the user was created using the Teradata Manager Database Setup utility. Start Locking Logger To start Locking Logger From the Teradata Manager menu bar, click Investigate>Locking Logger Teradata Manager User Guide 291

292 Chapter 19: Teradata Manager Applications LogOnOff Usage LogOnOff Usage LogOnOff Usage presents daily, weekly, and monthly logon statistics based on information in the DBC LOGONOFF view on the associated Teradata Database. Three macros are included with LogOnOff Usage to help retrieve this information: Table 115: LogOnOff Usage Report Descriptions Report Name DailyReport WeeklyReport MonthlyReport Description The number of logons across several days, either in 10 minute or one hour intervals, grouped by time interval and user. A summary of all logons for the last ten weeks, grouped by week. A summary of all logons over the last month (from 30 days previous to the current date) grouped by date. Application Use LogOnOff Usage to create and execute macros on the associated Teradata Database and to display the results in a scrollable window. Note: LogOnOff Usage does not connect to the Teradata Database by logging into the Teradata Manager server. Even if the Teradata Manager client is in client-server mode, LogOnOff Usage always connects in direct mode. LogOnOff Usage does not operate from outside a firewall. Start Logon/Logoff Usage To start Logon / Logoff Usage From the Teradata Manager menu bar, click Investigate>Logon / Logoff History. Database Setup How It Works Database Setup is a tool for setting up the Teradata Database with the databases, tables, macros and users necessary to run Teradata Manager. Database Setup uses your parameters to generate SQL statements for creating and modifying databases, tables, macros, and users on the specified database. Each SQL statement and whether it was submitted successfully or unsuccessfully is logged in the main window of the application. 292 Teradata Manager User Guide

293 Chapter 19: Teradata Manager Applications Priority Scheduler Administrator Start Database Setup Note: Database Setup does not connect to the Teradata Database by logging into the Teradata Manager server. Even if the Teradata Manager client is in client-server mode, Database Setup always connects in direct mode. Database Setup does not operate from outside a firewall. To start Database Setup From the Teradata Manager menu bar, click Administer>Teradata Database Setup. Priority Scheduler Administrator Start Teradata PSA The Teradata Priority Scheduler Administrator (Teradata PSA) is a resource-management tool that provides an easy-to-use graphical interface enabling Priority Definition Sets to be defined and schmon scripts to be generated to implement these sets. For more information and instructions on using Priority Scheduler, see Chapter 14: Using Teradata Priority Scheduler Administrator. Priority Scheduler Administrator is not supported under the Teradata Database running on HPUX. Note: Teradata PSA does not connect to the Teradata Database by logging into the Teradata Manager server. Even if the Teradata Manager client is in client-server mode, Teradata PSA always connects in direct mode. Teradata PSA does not operate from outside a firewall. To start Teradata PSA From the Teradata Manager menu bar, click Administer>Workload Management> Priority Scheduler. Remote Console Use Remote Console to run many of the Teradata Database console utilities from your Teradata Manager PC. Supported utilities include: Table 116: Remote Console Utility Descriptions Use this utility... Abort Host To... Cancel all outstanding transactions running on a host that is no longer operating Teradata Manager User Guide 293

294 Chapter 19: Teradata Manager Applications Remote Console Table 116: Remote Console Utility Descriptions (continued) Use this utility... CheckTable Configure DBS Control Ferret Gateway Global Lock Display (V2R4) Operator Console Priority Scheduler (V2R4.1) Query Configuration Query Session Recovery Manager Show Locks Vproc Manager Teradata DWM Dump (V2R6.0) To... Check for inconsistencies in internal data structures and for corruption Review and update the configuration of the Teradata Database Display the values of the DBS Control Record fields. Modify the values, if the field is writable Display and set various disk space utilization attributes, and dynamically reconfigure the data on the disks to correspond with the selections Inspect and modify the gateway operating parameters for any network attached to the associated Teradata Database See a snapshot capture of all real-time database locks Run supervisor commands to manage the programs that perform Teradata Database operations Control resource allocation for Database sessions based on either sessionrelated priority designations or system-level scheduling parameters Display the current Teradata Database configuration Monitor the state of database sessions on logical host IDs attached to the Teradata Database Monitor the progress of a Teradata Database recovery Provide information about hosts utility locks Obtain the status of vprocs, change vproc states, initialize and boot a specific vproc, initialize the vdisk associated with a specific vproc, or force a database restart View information about Teradata Dynamic Workload Manager (Teradata DWM) rules active on your Teradata Database system Application The Remote Console log contains the input and output for all console utilities started. One log file is used by each instance of Remote Console, and there may be up to four instances running against the same database on a given PC. When a utility is run, the output for the utility appears on the main window. The script feature of Remote Console allows the recording of commands associated with starting, running, and stopping console utilities. The commands entered are saved as scripts and can be played back at a later time. Scripts may be run interactively from the main menu by clicking Scripts>Run, or in batch mode by using the Teradata Manager Scheduler. Note: Remote Console does not connect to the Teradata Database by logging into the Teradata Manager server. Even if the Teradata Manager client is in client-server mode, Remote Console always connects in direct mode. Remote Console does not operate from outside a firewall. 294 Teradata Manager User Guide

295 Chapter 19: Teradata Manager Applications Session Information Start Remote Console To start Remote Console From the Teradata Manager menu bar, click Administer>Database Console. Session Information Session Information (SI) uses the Teradata Database Performance Monitor to collect the session PM data from the Teradata Database. It then formats and shows key information about each session, based on the current collection rate. SI shows logon sessions in different categories, and helps identify blocked and long idle sessions and abort sessions on the Teradata Database. Reports Most of the SI reports are categorized based on the status of the session. These reports can be used in many different ways. Open the reports based on your needs, and set up the Collection Frequency. After this is done, SI updates the reports automatically. The reports listed in Table 117 provide very useful information, and can be left open all the time. Table 117: Session Information Report Descriptions Report Name Summary Report Blocked Report Idle Report Description A single row for each user, with a count of sessions for each state (Idle, Active, Blocked, Responding, Parsing, Aborting, Other, and Delayed). Blocked sessions on the system. Double-click the blocked session in the report. The Host/Session detail dialog box shows who is blocking the session and how many sessions are being blocked. To abort the session, use the Host/Session dialog box. Idle sessions on the system. Define thresholds for the Idle Report so all long idle sessions are displayed in this report. The Auto Abort Threshold can be defined so the long idle sessions automatically abort. Caution: To avoid aborting critical sessions or users, define a local filter with this report. Connection Options The type of connection can be changed. Log on directly to the Teradata Database by disconnecting from the Server. Teradata Manager User Guide 295

296 Chapter 19: Teradata Manager Applications Statistics Collection Start SI SI can either: Log on to the Database to get the PMPC session data from the system directly. Connect to another Teradata Manager PC that is running the Teradata Manager Service, and get the PMPC data from the server PC. To start SI From the Teradata Manager menu bar, click Monitor>Session Information. Statistics Collection How It Works Collecting statistics on a column or key field assists the query optimizer in choosing an execution plan that minimizes query time. Because the optimizer bases the execution plan on the actual values in the table, statistics can be updated whenever there have been a significant number of row additions or deletions. Use Statistics Collection to: Start Statistics Collection Determine which tables have statistics Create statistics for columns or indexes Drop statistics by column/index, or for the entire table Update statistics for column/index, table, database, or the entire Teradata Database Create SQL scripts to collect or drop statistics Statistics Collection shows Teradata Database statistics in three windows: The Database window showing a tree view of the databases. The Table window showing the tables in the selected database. The Statistics window showing the columns/indices for the selected table. Note: Statistics Collection does not connect to the Teradata Database by logging into the Teradata Manager server. Even if the Teradata Manager client is in client-server mode, Statistics Collection always connects in direct mode. Statistics Collection does not operate from outside a firewall. To start Statistics Collection From the Teradata Manager menu bar, click Administer>Statistics Collection. 296 Teradata Manager User Guide

297 Chapter 19: Teradata Manager Applications Teradata Performance Monitor Teradata Performance Monitor How It Works General Notes Use Teradata Performance Monitor to monitor the general health of a Teradata Database. Analyze current performance as well as current and historical session information. Abort sessions if they are causing system problems. Teradata Performance Monitor uses the Teradata Database Performance Monitor to collect near real-time system configuration, Resource usage, and Session information from the Teradata Database. It then formats and shows this information as requested. Teradata Performance Monitor shows this performance data on four sets of screens, one for each of the following types of data: General health information (configuration and summary) This data is displayed on the main screen and is refreshed automatically at a user defined interval. This data can also be displayed as a chart of summary values over time by clicking Chart. Resource information (nodes and vprocs) This data is collected and displayed only when the user requests it. Graphs showing a user selected data point for each node (or vproc) may be displayed by double-clicking the required data point. Session Information (statistics and lock information) This data is collected and displayed only when the user requests it. The session summary screen shows all the sessions currently logged onto the system and allows the user to filter these sessions and to sort them in various ways. It also shows which sessions are currently blocked. Detail session information, for a specific session may be seen by double-clicking on that session. Graphs showing a user selected data point for each Session may be displayed by double-clicking the required data point. Graphs showing data point A by data point B may be displayed by clicking on one data point and dragging it to the other. Detail lock information may be displayed by double-clicking on any session that is shown to be blocking, or blocked by, another session. Display session skew information and SQL text and Explain steps. Historical session information A list of historical session files is displayed. By choosing from this list, the user may analyze a problem after the fact. The data itself is displayed on the regular Session Information screens. The Main Teradata Performance Monitor screen must remain open. Closing it ends your Teradata Performance Monitor session. Teradata Manager User Guide 297

298 Chapter 19: Teradata Manager Applications Teradata Performance Monitor Prerequisites Resusage Tables In general, each screen is displayed maximized within the parent frame. This may be required to see the entire screen contents. To use all of the functions in Teradata Performance Monitor, the following user privileges are required on the Teradata Database: SETSESSRATE SETRESRATE MONSESSION MONRESOURCE ABORTSESSION Before Teradata Performance Monitor can return any data, use the xctl utility to enable the following Resusage tables on the Teradata Database system(s) that are being monitored: SVPR SPMA IPMA SLDV SHST After enabling these tables, use Teradata Performance Monitor or the Operator commands to set the session and resource collection rates to non-zero values. Start Teradata Performance Monitor To start Teradata Performance Monitor From the Teradata Manager menu bar, click Monitor>Performance Monitor. 298 Teradata Manager User Guide

299 Glossary A action definition A logical action consisting of a single physical action and related attributes such as a user-defined name and any required execution parameters. action list A logical action consisting of one or more action definitions. Alert Policy Editor See APE. Alert Viewer A component of the Alerts Facility used to easily view system status for one or more Teradata Databases. Alerts Facility Facilitates the monitoring of performance characteristics and faults on the Teradata Database. The Alerts Facility can automatically activate actions, such as sending a page, sending , or sending a message to an SNMP system. Other applications and utility programs can also make use of the Alert function by using a built-in request interface. allocation group Establishes how resources are allocated to processes. An allocation group has parameters that determine the amount of resources available to the sessions assigned to the performance group that references the allocation group. An allocation group determines the scheduling policy and set type. See the Priority Scheduler chapter of the Teradata Database Utilities - Volume 2 documentation. American National Standard Code for Information Interchange See ASCII. APE Alert Policy Editor. The interface that defines the actions that take place when performance or database space events occur on one or more Teradata Database machines. Use it to define alert policies: create actions, set event thresholds, assign actions to events, and apply the policy to the Teradata Database. API Application Programming Interface. A language and message format used by an application program to communicate with the operating system or some other control program such as a database management system or communications protocol. application programming interface See API. ASCII American National Standard Code for Information Interchange. The basis of character sets used in almost all present-day computers. B Basic Teradata Query See BTEQ. BTEQ Basic Teradata Query. A command-based application that enables users on a workstation to communicate with one or more Teradata Database systems. Teradata Manager User Guide 299

300 Glossary C Call-Level Interface, Version 2 See CLIv2. central processing unit See CPU. CLIv2 Call-Level Interface, Version 2. A library of routines that enable an application program to access data stored in Teradata Database. coexistence system A system that contains a mixture of node and storage generations that operate as a single MPP system running the same software. The Teradata Administration Workstation (AWS) manages the coexistence system. CPU Central Processing Unit. The part of a computer which controls all the other parts. Designs vary widely but, in general, the CPU consists of the control unit, the arithmetic and logic unit (ALU) and memory (registers, cache, RAM and ROM) as well as various temporary buffers and other logic. D Dashboard A feature of Teradata Manager that provides a summary of the current state of the system on a single page where current performance and workload information can be viewed, as well as recent trends, enabling rapid problem resolution. database administrator See DBA. DBA Database Administrator. Generally, a person responsible for the design and management of one or more databases and for the evaluation, selection and implementation of database management systems. Delay Queue Statistics Report Shows details on the objects in the Workload Delay Queue. DLL Dynamic Link Library. A.dll file contains a library of functions and other information that can be accessed by a Windows program. When a program is launched, links to the necessary.dll files are created. If a static link is created, the.dll files are in use as long as the program is active. If a dynamic link is created, the.dll files are only used when needed. Dynamic links help programs use resources, such as memory and hard drive space, more efficiently. dynamic link library See DLL. E event sequence number The agent generates this number to uniquely identify each trap. H HTML HyperText Markup Language. The coding language used to create hypertext documents for the World Wide Web. HyperText Markup Language See HTML. 300 Teradata Manager User Guide

301 Glossary L logical action A named action that is defined from the Actions tab in the Alert Policy Editor. Logical actions can be assigned to events in the alert policy. M Management Information Base See MIB. MAPI Messaging Application Programming Interface. A set of Microsoft-defined functions and interfaces that support capabilities. Messaging Application Programming Interface See MAPI. MIB Management Information Base. A naming convention used to access network data by way of a network management protocol such as SNMP. N Node Utilization Report on individual nodes. Shows information on node use including detailed information O object identifiers See OIDs. Object Logon Statistics Report Shows details on object logon statistics. ODBC Open Database Connectivity. Type of driver used to connect applications with databases. The ODBC driver processes ODBC calls from an application, but passes SQL requests to the Teradata Database for processing. OIDs Object Identifiers. Generally an implementation-specific integer or pointer that uniquely identifies an object. Open Database Connectivity See ODBC. P PD set Priority Definition Set. The collection of data, including the resource partition, performance group, allocation group, performance period type, and other definitions that control how the Priority Scheduler manages and schedules session execution. performance group A collection of parameters used to control and prioritize resource allocation for a particular set of Teradata Database sessions. See the Priority Scheduler chapter of the Teradata Database Utilities - Volume 2 documentation. performance period Links a performance group to an allocation group. Use a performance period to change allocation group assignments based on time-of-day or resource usage. See the Priority Scheduler chapter of the Teradata Database Utilities - Volume 2 documentation. Teradata Manager User Guide 301

302 Glossary performance period type performance group. A type of threshold used to change performance periods for a performance monitor and production controls See PMPC. Performance Monitor See PMON. Performance Monitor API See PM/API. physical action A basic action type, such as <Send a Page> or <Send an >. Physical actions must be encapsulated by logical actions to be used in the alert policy. Physical actions themselves are just templates and cannot be assigned directly to events in the alert policy. PM/API Performance Monitor API. An application programming interface that allows clients to retrieve performance data from the Teradata Database and to issue certain control statements such as Abort Session. PMON Performance Monitor. Provides the system status at a glance with seven functional areas for monitoring system activity including Configuration Summary, Performance Summary and Resource Usage (both physical and virtual), Session and Lock information, Session History, Control functions and graphic displays of Resource and Session data. PMPC Performance Monitor and Production Controls. The Performance Monitor Object is an ActiveX (COM) object that exposes methods to allow retrieval of PMPC data. Each method returns a collection of objects, each of which encapsulates the performance data for that object. It also provides for execution of the production control (action) functions of PMPC. priority definition set See PD set. Priority Scheduler Administrator See PSA. PSA Priority Scheduler Administrator. A resource management tool used to monitor and control the Priority Scheduler environment, where the different types of work can be prioritized in a mixed workload. Ensures queries requiring immediate handling are prioritized by moving the jobs in front of lower priority work. R resource partition See RP. Resource Sampling Subsystem See RSS. response time The time it takes to get the first response parcel for a single request from the Teradata Database. RP Resource Partition. In Priority Scheduler, one of three control structures to group user sessions for scheduling purposes. The other two are performance group and allocation group. A resource partition is a set of performance groups and associated components. See the Priority Scheduler chapter of Teradata Database Utilities - Volume Teradata Manager User Guide

303 Glossary RSS Resource Sampling Subsystem. Collects a wide-range of resource usage data. The RSS and the Parallel Data Extensions (PDE) are two Teradata Database subsystems that work in conjunction with other subsystems to gather resource usage data. During the data collection phase, both PDE and RSS gather information from the operating system and from the Teradata Database. This data is temporarily stored in shared data collection buffers. Data collection continues for a user-specified period of time, called the collection interval. S service level goal See SLG. Session Information See SI. Session Status Report Shows information on sessions including detailed information on any displayed session. From this report, the priority of the session can be modified, sessions can be aborted, view what sessions the selected session is blocking, and what the selected session is blocked by. SI Session Information. Uses the Performance Monitor to collect the session PM data from the Teradata Database. It then formats and shows key information about each session, based on the current collection rate. SI shows logon sessions in different categories, and helps to identify blocked and long idle sessions and abort sessions on the Teradata Database. Simple Network Management Protocol See SNMP. Single Sign On See SSO skew This value is calculated based on a single database collection interval. If the Session Collection rate is 60, then the skew is calculated for a 60 second period. The value is calculated using current data values. For example, the Max CPU used during the past 60 seconds relative to the Average used over that same 60 seconds: skew = 100 * (1 - avg / max) SLG Service Level Goal. The measure of whether the queries in a workload class are meeting the performance objectives. The performance objectives can be stated either in terms of throughput, or a percentage of queries meeting a response time objective. SMP Symmetric Multi Processing. The NCR SMP platform node is an entry-level, standalone data warehousing system server. SNMP Simple Network Management Protocol. Generally used with TCP/IP networks, it is a protocol used by network hosts to exchange information used in the management of networks. SNMP provides a means to monitor and control network devices, and to manage configurations, statistics collection, performance, and security. SNMP trap One of three main areas for grouping Teradata Manager MIB objects. An SNMP trap is known as an event. Teradata Manager Alerts system generates SNMP events. SQL Structured Query Language. A standardized query language for requesting information from a database. SQL consists of a set of facilities for defining, manipulating, and controlling data in a relational database. The initialism, SQL, is pronounced either see-kwell or as separate letters. Teradata Manager User Guide 303

304 Glossary SSO Single Sign On. Allows users on Windows 2000 systems to access the Teradata Database based on their authorized network usernames and passwords. When using SSO, there is no need to enter an additional username and password when logging on to a Teradata Database through client applications. Structured Query Language See SQL. Summary graph Shows trend data over time and additional data not visible on the top level Dashboard window. Investigate problems by correlating your choice of many types of data. Symmetric Multi Processing See SMP. T TCP/IP Transmission Control Protocol/Internet Protocol. A protocol for communication between computers, used as a standard for transmitting data over networks and as the basis for standard Internet protocols. TDPID Teradata Director Program Identifier. The name of the Teradata Database being accessed or monitored. Teradata Director Program Identifier See TDPID. Teradata Manager A fully-featured suite of specialized tools and applications to centrally monitor and control the Teradata Database. It collects, analyzes, and shows database performance and utilization information in either report or graphic format without impacting database users. Teradata Manager Service Teradata Manager Service runs on your Teradata Manager server PC and is installed if Server setup type is selected during the installation process. Teradata Manager Service is required to use alerts, the Dashboard, workload analysis and trends, the scheduler, or client/server mode connections. Teradata Tools and Utilities See TTU. TPM Transactions Per Minute. The number of requests processed per minute. transactions per minute See TPM. Transmission Control Protocol/Internet Protocol See TCP/IP. TTU Teradata Tools and Utilities. A group of products designed to work with the Teradata Database. V Vproc Utilization Report on individual vprocs. Shows information on vproc use including detailed information 304 Teradata Manager User Guide

305 Index Symbols # Proc Swap 178 % Brd 177 % in Use 191 % Mem Free 178 % PtP 177 % Retries 177 A A+R % of IOs 174 Abort Query % 149 Abort Query Count 149 Abort Session Report 109 aborting sessions 108 Aborts 160 access authorizing for profiles 57 restricting with profiles 56 access denials, audit log report 204 access log, creating 199 access logging, initiating 199 Access Type 201, 203, 204 Account 104, 137, 139 account options 236 action list, defining 241 action, creating a user-defined 231 Active 93 Active Count 149 Active Sessions 91, 92, 93 ActiveX (COM) object application distribution requirements 268 Performance Monitor Object 267 Administer menu 41 Advanced dialog box 83 Ages/Sec 178 Alert Action log file location 44 log name, changing 58 log size, changing 58 alert events, defining database space 242 node level performance 243 session level performance 245 system level performance 242 Vproc level performance 244 alert policy Alert Policy Template 231, 246 applying to the database 246 creating 231 data collection rates, defining 246 events, adding 242 false positive s and pages, avoiding 231 Alert Policy Editor description 258 log file 231 log file location 44 starting 258 Alert Viewer description 197 overview 33 starting 247 system performance, investigating 197 alerts facility action definition 233 action lists 233, 241 actions, defining 231 alert policy, creating 230 BTEQ script, running a 239 collecting rates, setting 60 configuring 236 sending 234 introduction 230 log name, changing 58 log size, changing 58 overview 32 page, sending a 233 program, running a 238 SNMP MIB objects 85 SNMP trap, generating an 240 system parameters, defining 57 usage examples 251 alerts.log 44 allocation groups See Teradata PSA Aloc Fail % 178 AMP Count 99 AMP Count Exception 161 AMP CPU 102 AMP CPU Skew Exception 160 historical resource utilization, analyzing 169 Utilization Report 170 AMP Disk Use 96 AMP I/O 102, 106 Teradata Manager User Guide 305

306 Index AMP I/O Count Exceptions 161 AMP I/O Skew Exceptions 161 AMP object 275 AMP Parallelism 91 AMP State 101, 105 AMP usage data collection parameters, configuring 70 data collection tables 64 historical data, storing 64 AMP Utilization % 91 AMP Worker Task 95, 96 AMP/CPU Skew (%) 162 AMP/IO Skew (%) 162 AMP/PE Exceptions 160 Analyze menu 39 ape.log 44 application descriptions Alert Policy Editor 258, 288 Alert Viewer 197, 288 BTEQ Window 258, 289 Configuration Check 290 Database Setup 292 Error Log Analyzer 195, 290 Locking Logger 196, 291 LogOnOff Usage 196, 292 Priority Scheduler Administrator 293 Remote Console 293 Session Information 295 Statistics Collection 259, 296 Teradata Performance Monitor 297 Application ID CPU Utilization Report 137 Disk I/O Utilization Report 139 applications, adding to the menu bar 81 Arrival Rate 149 Audit Checkpoint, Dump and Restore Activity Report 203 Audit Database and Users Activity Report 200 Audit Denials Report 204 Audit Grant and Revoke Activity Report 202 Audit Index Activity Report 202 audit log reports access denials 204 checkpoint, dump and restore activity 203 custom report, creating 205 database and user activity 200 filter parameters, setting 200 index activity 202 setting up 199 summary report, creating 204 table, view and macro activity 201 Audit Summary Report 205 Audit Table, View, Macro Activity Report 201 authentication mechanism, setting client (session) 83 Teradata Manager Service 83 authentication string, setting client (session) 83 Teradata Manager Service 84 Available Perm 192 Ave Free Mem MB 157 Ave I/O Size 157 Average CPU (%) 137 Average CPU Use 100 Average Disk I/O 139 Average Disk Req 100 Average I/O per Transaction 91 Average Node CPU % 92 Average Response Time 91 Average Row Size 141 Average Transaction Rate (TPM) 91 Average Vprocs CPU% 92 Avg Disk Req 96 Avg I/O Resp 176 AvgReqQLen 180 Awt User Exec % 170 Awt User Serv % 170 B Backup KB Allocated 100 Backup Seg Agings 100 Backup Segs Alloc 97 Backup Segs Allocated 100 Bad Cyls # Cyls 193 % of Total Avail Cyls 193 batch reports, creating 46 BIN directory 44 Bkup Rds /Sec 174 Blks Read Fail% 180 Blks Read/Sec 180 Blks Write Fail% 180 Blks Write/Sec 180 Block (Object) 283 Block Count 106 Blocked By Report 111, 112 Blocked Sessions Dashboard 91, 92 Summary Graph Data Points 93 viewing 110 Blocked Time 103 Blocked Time Exception 161 Blocking Duration (secs) 146 Blocking Sessions Report 110 BTEQ scripts file location 44 running using alert action 239 BTEQ Window 306 Teradata Manager User Guide

307 Index description 258, 289 running the setup script 53 starting 259 Bucket 166 Bynet historical resource utilization, analyzing 176 Summary Graph data points 93 Bynet Use 99 Bynet Use % 98 Bynet Utilization % 91 C Cache Hit Ratio 174 Cached 160 Channel Use % 94, 98 character set, setting client (session) 83 Teradata Manager Service 84 checkpoint activity, audit log report 203 CIC Use 96, 99 client mode 268 client/server mode, defining system parameters for 57 coexistence systems, setting up 49 collecting statistics 259 collection of data, enabling 61 collection rates, setting 60 color options, configuring 77 command line parameters, Teradata PSA 228 Completed Query % 149 Completed Query Count 149 Completed Query List Report 154 Concurrency 146, 162 Configuration Check, description 290 configuring Alerts 57 client/server mode 57 color display options 77 Dashboard 57 data collection AMP usage 70 DBQL 71 heartbeat query 72 Priority Scheduler 73 resource usage 74 spool space 75 table space 76 Teradata DWM 72 alerts 236 firewall 82 installation, new 47 Teradata Manager Service to monitor a system 57 workload trend analysis 57 console See Remote Console CPU Busy 173 CPU Busy + WIO % 174 CPU Skew 102, 106 CPU Time 149, 162, 166 CPU usage, comparing 226 CPU Use 96, 99 CPU Use % 94, 98 CPU Utilization Report 137 CPU utilization, analyzing workload trends 135 CPU/Disk Ratio 158, 162, 166 create statement (ddl), table 189 Current Perm 186, 188, 189, 191 Current Perm % 186 Current Perm Usage 141 Current Request CPU 105 Current Request IOs 105 Current Request Start 105 Current Spool 106 Current Spool Usage 143 Current Temp 187 Current Temp % 187 Current Temp Usage 144 Cylinder Count 141 Cylinder Space by Vproc Report 192 cylinder space usage, viewing by Vproc 192 D Dashboard collection rates, setting 60 history data displayed 92 monitoring activity with 90 overview 29 starting 90 system parameters, defining 57 viewing 90 data collection Data Collection tab 61 enabling 61 external DBQL, specifying an 66 logon credentials for tasks, assigning 65 perm space requirements for historical trends 63 rates for alert policy, defining 246 data collection parameter configuration DBQL 71 for AMP usage 70 heartbeat query 72 Priority Scheduler 73 resource usage 74 spool space 75 table space 76 Teradata DWM 72 data directory 44 database activity, audit log report 200 Teradata Manager User Guide 307

308 Index Database Administration documentation 7, 151 database console See Remote Console database objects, viewing 189 database ownership, transferring 185 database performance status, displaying 247 Database Setup alternate script, running 52 database, setting up 52 databases, tables and macros 48 description 292 Teradata Manager, setting up 48 users, adding 50 database space event, defining 242 database space usage, viewing 186, 187 databases changing 78 creating 48 initial setup 48 performance status, displaying 247 Datablock Count 141 Datablock Size 141 dbcmngr.logampusage 64 dbcmngr.logdbql 64 dbcmngr.logdbqlstep 64 dbcmngr.logheartbeat 64 dbcmngr.logperm 65 dbcmngr.logresusagehost 65 dbcmngr.logresusagenode 65 dbcmngr.logresusagevproc 65 dbcmngr.logschmondag 64 dbcmngr.logschmonnode 64 dbcmngr.logschmonpg 64 dbcmngr.logschmonrp 64 dbcmngr.logschmonsystem 64 dbcmngr.logspool 65 dbcmngr.logsystemactivity 65 dbcmngr.logwdsummary 65 DBQL data collection parameters, configuring 71 data collection tables 64 external DBQL, specifying an 66 historical data, storing 64 DBQL Step Usage Report 164 DBQL Summary Histogram 166 DBQL Summary Histogram Report 166 DBQL Usage Report Condition Indicator Count 160 Parallelism 162 Resource Usage 162 Response Time 161 ddl, viewing for selected table 189 default preferences, tables and graphs 79 defining actions generate an SNMP trap 240 run a BTEQ script 239 run a program 238 send a page 233 send an 234 to the policy 231 allocation group parameters 214 an Action List 241 data collection rates 246 events to the policy 241 PD Set parameters 209 performance group parameters 212 resource partition parameters 209 system parameters 57 user access to profiles 57 Delay Queue Statistics Report 113 Delay Time 152, 161 Delayed Query % 149 Delayed Query Count 149 Delayed Query List Report 151 deleting allocation groups 215 performance groups 214 performance periods 214 Priority Definition Set information 217 resource partitions 211 Delta AMP CPU Seconds 105 Delta CPU 102 Delta I/O 102 Depot Cyls # Cyls 192 Av Util per Cyl 192 details, displaying history data 92 node utilization 99 physical utilization 99 session data 103 Teradata DWM workload definition 128 virtual utilization 95, 112 Vproc utilization 95, 112 dialog box help, viewing 26 DIPACC DBCSQL script 199 direct mode object model 268 Performance Monitor object 268 setting 55, 79 directories BIN 44 data 44 help 44 profiles 44 samples 44 secure 44 SQL Teradata Manager User Guide

309 Index directory structure 43 Disk 93 Disk I/O Utilization Report 139 disk i/o utilization, analyzing 138 Disk Q Len 95, 98 Disk Reads 95, 96, 98, 100 Disk Skew 106 disk space, reallocating 183 Disk to CPU Exception 161 Disk Use % 94, 98 Disk Utilization % 91 Disk Utilization Report 175 disk utilization, analyzing historical resource 174 Disk Writes 95, 96, 98, 100 Disp User Exec % 172 Disp User Serv % 172 documentation CD-ROM, downloading 7 how to order 7 installation 7, 27 Release Definition 6, 27 dump activity, audit log report 203 E Edit menu 36 Elapsed Time 103, 106 actions to the policy, defining 231 actions, defining 234 configuring 236 alert message contents 235 Microsoft Outlook, configuring 58 sample alert 235 sending using alerts 234 SMTP mail configuring 58 testing 59 Error Log Analyzer (ELA) description 195 starting 290 error log, viewing 195 error messages ODBC error, SQL Assistant 41 on SMP systems 59 PDSet mismatch errors, correcting 219 Performance Model object 285 resource partition errors, correcting 219 Error Query % 149 Error Query Count 149 Estimated Processing Time 164 Estimated Row Count 164 events database space, adding 242 defining 241 node level performance, adding 243 session level performance, adding 245 SNMP 86 system level performance, adding 242 Vproc level performance, adding 244 Exceeded SLG Query % 149 Exceeded SLG Query Count 149 Exceeded SLG Query List Report 153 Exception Action 153 Exception Code 151, 153 Exception Query % 149 Exception Query Count 149 Exception Query List Report 152 Exception Type (Limit Exceeded) 153 Excluded Users dialog box 252 external DBQL, specifying an 66 F Fallback 190 File menu 36 files, location of 43 filter parameters, setting audit log reports 200 First Response Time 161 Free Cyls # Cyls 193 % of Total Avail Cyls 193 Free Mem % 174 FSG Cache Miss 158 G Graph menu 42 graphs color display, changing 77 graph legend 121 disabling 121 enabling 121 preferences, restoring 79 printing 45 saving 45 H heartbeat query data collection parameters, configuring 72 data collection tables 64 historical data, storing 64 logon credentials, assigning 65 response time, analyzing 144 Help Database Report 190 help file directory 44 Help menu 43 Hide Options link 112, 124, 128, 131, 136, 138, 140, 143, 144, Teradata Manager User Guide 309

310 Index 147, 156, 168, 170, 171, 173, 175, 177, 178, 180, 181 hierarchical space usage, viewing 190 Hierarchy Report 191 High Vprocs CPU% 92 historical resource utilization, analyzing AMP CPU 169 collection rates, setting 60 disk 174 host 179, 181 memory 177 network (Bynet) 176 node 172 node CPU 167 PE CPU 171 historical trends CPU utilization 39 data collection, perm space requirements for 63 DBQL step usage 40 DBQL usage 40 disk I/O utilization 39 resource usage 40 response time 40 space usage 39 table growth 39 user count 40 history data details, displaying 92 Host 102 Host Block Reads 97, 100 Host Block Writes 97, 100 Host Id 109, 111 Host ID/Cluster 96 Host Reads 95, 98 Host Utilization Report 180 host utilization, analyzing 179 Host Writes 95, 98 HSpace 191 I I/O Count 162, 164, 166 I/O per Tx 93 I/O Wait 99 Idle Time 103 index activity, audit log report 202 Index Count 141 Index Ratio 158 initial setup 48 installation directory structure 43 getting help with 27 Investigate menu 38 IOs/Sec 177 J Jrnl Cyls # Cyls 193 % of Total Avail Cyls 193 Av Util per Cyl 193 K KB/IO 177 KB/Swp Drp 179 KB/Swp Rd 179 KB/VPR Aloc 178 KBs Read/Sec 180 KBs Write/Sec 180 KBs/Blk Read 180 KBs/Blk Write 180 Kernel CPU % 98 L Last Response Time 161 Ldv IOs /Sec 174 Ldv KB / IO 174 LDV MB/sec 174 legend, graph 121 Level 112 location of log files 44 lock contentions, investigating 196 Lock Mode 110 Lock Scope 110 Lock Status 110 Locked Object 110 Locking Logger description 196, 291 using 196 Log Date 200, 201, 202, 203, 204 log files Alert Policy Editor 231 alerts.log 44, 232 ape.log 44 locations 43, 44 log name, changing Alert Action 58 log size, changing Alert Action 58 Teradata Manager log 44 tmgr.log 44 Log Time 201, 202, 203, 204 logical alert actions, defining 233 Logical MB/Sec 157 logon activity, investigating 196, 264, 265 logon credentials data collection, assigning 65 heartbeat queries 65 Teradata Manager Service 59 Logon PE Number Teradata Manager User Guide

311 Index Logon Sequence 105 logon settings, changing 78 Logon Source 103, 106 Logon Time 103 Logon Time/Date 105 LogOnOff Usage description 196, 292 using 196, 264, 265 Long I/O per Tx 94 Long Resp Time 94 Long TPM 94 Low Vprocs CPU% 92 M macro activity, audit log report 201 macros, creating 48 Max Concur Rqsts 176 Max Perm 186, 191 Max Row Count for Steps Exception 161 Max Spool 186 Max Steps in Parallelism 162 Max Temp 187 Maximum CPU (%) 137 Maximum Current Spool 143 Maximum Current Temp 144 Maximum Disk I/O 139 Maximum Node CPU % 92 Maximum Peak Spool 143 Maximum Peak Temp 144 Maximum Row Size 141 MaxReqQLen 180 Medium CPT 94 Medium I/O per Tx 93 Medium Resp Time 93 Medium TPM 93 Mem Aloc/Sec 174 Mem Fail % 174 Mem Failures 100 Mem KB Allocated 97, 100 Mem Segs Agings 100 Mem Segs Allocated 97, 100 Memory Allocation Failures 98 Memory Utilization Report 178 memory utilization, analyzing 177 menu bar adding applications to 81 Administer menu 41 Analyze menu 39 description 35 Edit menu 36 File menu 36 Graph menu 42 Help menu 43 Investigate menu 38 Monitor menu 37 Options menu 37 Window menu 43 MIB objects 85 Microsoft support files 268 migrating tdwm database 49 Unicode 53 Min Free Mem MB 157 Minimum CPU (%) 137 Minimum Current Spool 143 Minimum Current Temp 144 Minimum Disk I/O 139 Minimum Node CPU % 92 Minimum Peak Spool 143 Minimum Peak Temp 144 Minimum Row Size 141 Misc User Exec % 170, 172 Misc User Serv % 170, 172 Mode 111 Monitor menu 37 Monitor object 270 moving permanent disk space 183 ms/blk 174 Msg Queue Length 95 MsgBrdRead 157 MsgBrdReadKB 157 MsgBrdWriteKB 158 MsgBrdWrites 157 MsgPtPReadKB 157 MsgPtpReads 157 MsgPtPWriteKB 157 MsgPtPWrites 157 Msgs/Blk Read 180 Msgs/Blk Write 180 N Net Reads 97, 100 Net Rtry % 174 Net Writes 97, 100 NetMsgFCBlock 158 NetMsgGroupBlock 158 NetMsgResourceBlock 158 NetMsgRxBlock 158 network (Bynet), analyzing utilization 176 Network Utilization Report 177 No Classifications 160 Node Ave 93 Node CPU Utilization Report Contents 168 node CPU, analyzing utilization 167 Node Disk Use 99 node level performance event, defining 243 Teradata Manager User Guide 311

312 Index Node Max 93 Node Min 93 Node object 277 Node Parallelism 91 Node Utilization % 91 Node Utilization Detail Report 99 node utilization details, displaying 99 Node Utilization Report 98, 173 node utilization, monitoring 97 node, analyzing utilization 172 NodeSummary object 273 Non-Grouped Report 181 Number of Active Amps 162 Number of Concurrent Users 147, 164, 166 Number of Distinct Users 147, 162 Number of Steps 162 Number of Steps with Parallelism 162 O Object 111 object collection, returning 267 Object Delay Queue List Report 116 Object Logon Statistics Report 114 Object Query Statistics Report 115 Object Utility Statistics Report 117 objects AMP object 275 Block object 283 monitor object 270 Node object 277 NodeSummary object 273 PE object 276 SNMP MIB 85 Step object 283 viewing database 189 VprocSummary object 272 Workload object 284 ODBC error 41 online help, viewing 26 Options menu 37 Out Rqst Time % 176 ownership, transferring database 185 P P+S % of IOs 174 P+S Drps/Sec 179 P+S IO % 179 P+S Rds/Sec 179 P+S Wrts/Sec 179 page, sending using alerts 233 Parallel Efficiency 97, 100 Parallelism % 156 parameters, defining system parameters 57 Pars User Exec % 172 Pars User Serv % 172 Partition 103, 104 PD Set/Resource Partitions panel 209 PDE User Service 99 PDE User Service % 96 PE Count 99 PE CPU 93 PE CPU Seconds 105 PE CPU Utilization Report 172 PE CPU utilization, analyzing 171 PE Dispatcher 96 PE object 276 PE Parser 96 PE State 101, 105 PE Utilization % 91 Peak Perm 186, 188, 189 Peak Perm % 186 Peak Spool 187 Peak Spool % 187 Peak Spool Usage 143 Peak Temp 187 Peak Temp % 187 Peak Temp Usage 144 performance data data items 223 priority scheduler groups 222 report type and time 220 viewing 219 performance groups See Teradata PSA Performance Monitor collection rates, setting 60 overview 31 PM/API documentation 7 starting 120 Performance Monitor object 267, 268 AMP object 275 application distribution requirements 268 Block object 283 client mode 268 direct mode 268 error messages 285 Microsoft support files 268 monitor object 270 Node object 277 NodeSummary object 273 PE object 276 query bands 284, 285 registering files 269 sample files 268 Step object 283 Teradata Manager support files 269 VprocSummary object 272 Workload object Teradata Manager User Guide

313 Index Workloads (Collection/Not Creatable) 284 Performance Object Model, sample files 44 performance periods See Teradata PSA performance status, displaying 247 Perm Data Cyls # Cyls 192 % of Total Avail Cyls 192 Av Util per Cyl 192 perm space new database, allocating 48 new user, allocating 51 reallocating 183 requirements for historical trend data collection 63 tdwm database, setting for 49 permanent disk space, moving 183 Pg Drps/Sec 178 Pg Rds/Sec 178 Pg Wrts/Sec 178 physical alert actions, defining 231 physical utilization details, displaying 99 monitoring 97 PM/API documentation 7 PMON See Performance Monitor PMPC data, retrieving connection options 296 using Performance Monitor Object 267 policy See alert policy port number, setting 82 Prc Blks/Sec 174 preferences, tables and graphs 79 previewing reports or graphs before printing 45 Primary Table Size (MB) 141 printing previewing output 45 reports and graphs 45 Priority 102, 105 Priority Definition Set creating 219 defining advanced parameters 227 defining parameters 209 deleting 218 errors, correcting 219 printing text 216 saving information 217 scheduling 224 viewing description 216 Priority Group 137, 139 Priority Scheduler data collection parameters, configuring 73 data collection tables 64 historical data, storing 64 starting 257 Priority Scheduler Administrator See Teradata PSA Processing Time Differential 164 Processing User Code 99 product version numbers 3 Teradata Manager 43 profiles authorizing user access to 57 restricting user access with 56 setting up 56 Profiles directory 44 program fixes 27 programs, defining an action that runs a program 238 Q queries aborted queries 160 queries in step cache 160 queries with warnings 160 query band data collection parameters, configuring 74 Delayed Query List Report 152 Exception Query List Report 152 method for monitor (object) 271 method for session (object) 282 Performance Monitor object 284, 285 query band pairs, viewing 111 Query Bands Report 111 Query Count 161, 166 Query Log See DBQL Query Name 145 Query Seconds 161, 166 Query Text 151, 152 R Rd KB / I/O 176 Read % of I/O 157 Read % of IOs 174 Reads/Sec 176, 177 Refresh Workload List command 37 Rejected Query % 149 Rejected Query Count 149 Rejected Query List Report 151 release definition 27 Remote Console description 293 starting 258 reports creating batch version of 46 overview 34 printing 45 saving 45 space usage, changing options 185 Request Cache Hits 106 Request Count 102, 106 Teradata Manager User Guide 313

314 Index resource partitions See Teradata PSA resource usage collection rates, setting 60 data collection parameters, configuring 74 data collection tables 65 historical data, storing 65 Resource Usage Report Bynet Usage 157 CPU Usage 156 Disk Usage 157 Memory Usage 157 System Utilization 158 resource utilization, historical AMP CPU 169 disk 174 host 179, 181 memory 177 network (Bynet) 176 node 172 node CPU 167 PE CPU 171 Resp Time 149 Response Time 93 Response Time (ms) 146 Response Time Report 145 restore activity, audit log report 203 Result 201, 202, 203, 204 Retrieve Time (ms) 146 retrieving PMPC data 267, 296 Row Count 141, 161 Row Count Differential 164 Row Count Exception 161 Run VProc Number 105 S sample files Performance Monitor object 268 performance object model 44 SQL scripts 44 samples directory 44 saving Priority Definition Set to a file 217 Priority Definition Set to or from the Database 218 reports and graphs 45 schmon commands 217 schmon commands printing 216 saving 217 viewing 216 secure directory 44 security mechanism, setting 83 server changing to a different one 79 checking the status of 78 Ses User Exec % 172 Ses User Serv % 172 session character set, setting 83 Session Detail Report 104 session details, displaying 103 Session Id 111 Session Information collection rates, setting 60 description 295 overview 31 using 120 viewing 223 session level performance event, defining 245 Session Log Count 96 Session Number 102, 109 Session Priority Attributes 107 session priority, modifying 107 Session Report, viewing 224 Session Run Count 96 Session Status Report 102 session status, monitoring 101 sessions aborting 108 blocked 110 blocking 109 Sessions (for each AMP and PE) 95 setting up Alerts Facility on Windows coexistence systems 49 data collection 61 databases tables and macros 48 TCP/IP communications 82 the Teradata Database 292 users 50, 52 setup script, running 52 Short I/O per Tx 93 Short Resp Time 93 Short TPM 93 Show Options link 112, 124, 128, 131, 136, 138, 140, 143, 144, 147, 156, 168, 170, 171, 173, 175, 177, 178, 180, 181 Skew 186, 188, 189 Skew % 192 SLG Met 160 SNMP agent, configuring 85 MIB objects 85 trap, generating using alert action 240 troubleshooting tips 87 software releases, supported 3 Space By Database Report 186 Space By Vproc Report 191 space usage report options, changing Teradata Manager User Guide

315 Index viewing by table 187 by vproc 191 cylinder space by Vproc 192 database 186 hierarchical 190 table space by vproc 188 Spool 102 Spool Cyls # Cyls 192 % of Total Avail Cyls 192 Av Util per Cyl 192 spool space data collection parameters, configuring 75 data collection tables 65 historical data, storing 65 new database, allocating 49 new user, allocating 51 space usage, viewing 142 tdwm database, setting for 49 Spool Space Exception 161 Spool Space Limit 143 Spool Usage 162 Spool/Temp Space Usage Report 143 spool/temp space usage, analyzing workload trends 142 SQL Assistant ODBC error 41 starting 41 SQL directory 44 SQL scripts, sample files 44 starting Alert Policy Editor 258 BTEQ Window 259 Performance Monitor 120 Priority Scheduler 257 Remote Console 258 Statistics Collection 259 Teradata Manager 55 Teradata Manager Service 78 Teradata PSA 209 State 102 Statistics Collection description 259, 296 starting 259 Status 111 status of Database, displaying 247 Step Count 164 Step object 283 Swap Drops 100 Swap Reads 98, 100, 157 Swap Writes 98, 100 Swp Drps/Sec 179 Swp Rds/Sec 179 system alarms, administering using Alerts 258 system level performance events, defining 242 system parameters, defining 57 system performance parameters, investigating 197 T table activity, audit log report 201 table create statement (ddl), viewing 189 Table Growth Report 141 table growth, analyzing workload trends 140 Table Size (MB) 141 table space data collection parameters, configuring 76 data collection tables 65 historical data, storing 65 Table Space by Vproc Report 189 Table Space Report 188 table space usage, viewing by vproc 188 Table, View, Macro Name 201, 202, 203, 204 tables creating for Teradata Manager 48 initial setup 48 preferences, restoring 79 TCP/IP communications 82 tdatmgreventinfo 86 tdatmgrmonitorinfo tdratephysicalresource 86 tdratetable 86 tdratevirtualresource 86 tdatmgrsysteminfo tdnodetable 86 tdsessiontable 86 tdsystemcount 85 tdsystemtable 86 tdvproctable 86 tdeventmaxpersystem 86 tdmonitor.dll, registering 269 tdwm database, migrating 49 TDWM See Teradata DWM Temp Cyls # Cyls 193 % of Total Avail Cyls 193 Av Util per Cyl 193 Temp Space Limit 143 temp space, viewing space usage 142 Temporary Space 106 Teradata Administrator User Guide 7, 41 Teradata AWS User Guide 7 Teradata Database Utilities documentation See Utilities documentation Teradata DWM 49 configuring data collection parameters 72 data collection tables 65 historical data, storing 65 Teradata Manager User Guide 315

316 Index tdwm database perm space, setting 49 spool space, setting 49 Teradata DWM Dump, running 294 Workload Definition Summary Report 129 workload definition summary, displaying 128 Teradata Dynamic Workload Manager User Guide 7, 37, 42, 123, 127 Teradata Manager database, changing 78 initial setup 48 log file (tmgr.log) 44 overview 29 support files for PMON object 269 users, initial setup 50, 52 Teradata Manager Installation Guide 7, 27 Teradata Manager Performance Object Model, sample files 44 Teradata Manager Service character set, setting 84 COM object registration 78 connecting 55 data collection, enabling 61 account options, configuring 236 log files 44 logon credentials 59, 65 logon settings, changing 79 port number, setting 82 status, checking the 78 Teradata Performance Monitor description 297 overview 31 starting 120 Teradata PSA active time, setting 210 age time, setting 209 allocation groups adding 215 allocation groups panel 214 CPU limit, setting 215 defining new 213 defining parameters 214 deleting unused 216 relative CPU use, comparing 226 relative weights, comparing 225 session information, viewing 223 Session Report, viewing 224 command line parameters 228 CPU limit allocation group panel parameter 215 resource partition parameter 211 setting 210 CPU usage, comparing 226 dispatch queue wait 227 display, configuring the 228 I/O concurrency 227 I/O prioritization 227 limit AWT, setting 211 milestone limits 213 PD Set 209 performance data data items 223 priority scheduler groups 222 report type and time 220 viewing 219 performance groups adding 214 defining parameters 212 deleting 214 performance groups panel 212 performance period type 213 performance periods adding 214 deleting 214 Priority Definition Set creating 219 defining advanced parameters 227 defining parameters 209 deleting 218 printing text 216 saving information 217 scheduling 224 viewing description 216 relative weight changing 211 comparing 225 reserved AWT, setting 210 resource partitions creating 211 defining advanced parameters 227 defining parameters 209 deleting 211 errors in a PDSet, correcting 219 schmon commands printing 216 viewing 216 session information, viewing 223 session report, viewing 224 set type 214, 215 starting 209 used by performance group 215 weight, changing 214 Teradata Query Scheduler Administrator Guide 7, 42 Teradata Query Scheduler User Guide 7, 42 Teradata SQL Assistant User Guide 7, 41 Teradata Tools and Utilities Installation Guide for Microsoft Windows 7, 27 Teradata Tools and Utilities Release Definition Teradata Manager User Guide

317 Index Text Alocs/Sec 178 Time Blocked 106 Time Idle 106 Time Limit Exception 160 tmgr.log 44 TMlt IOs / Sec 174 Total AMP CPU % 156 Total AMP CPU Seconds 105 Total Avail Cyls 192 Total Busy % 168, 170, 172 Total Node CPU % 156 Total Processing Time 164 Total Row Count 164 Total Sessions 91, 92, 93 Total Time (ms) 146 Total User Exec % 168, 170, 172 Total User Serv % 168, 170, 172 TPM 93 TPtP IOs /Sec 174 Transaction Count 106 transferring database ownership 185 trends, workload analyzing CPU utilization 135 analyzing disk i/o utilization 138 analyzing heartbeat query response time 144 analyzing spool/temp space usage 142 analyzing table growth 140 analyzing user count 146, 147, 150, 155, 158, 163, 164 troubleshooting, SNMP 87 Type 111 U Unicode, migrating 53 Unused Perm 186 Unused Perm% 186 User 111 user access authorizing for profiles 57 restricting with profiles 56 user activity, audit log report 200 user applications 44 user count DBQL Step Usage Report, creating 163 DBQL Summary Histogram Report, creating 164 DBQL Usage Report 158 Resource Usage Trend Analysis feature 155 User Count Report, creating 146 Workload Definition Query List Report, creating 150 Workload Definition Usage Report, creating 147 User Count Report 147 User CPU % 98 user-defined action, creating 231 users adding 50 initial setup 50, 52 Utilities documentation 7, 208, 211, 216 V version numbers Teradata Database 3 Teradata Manager 3, 43 Teradata Tools and Utilities 3 view activity, audit log report 201 virtual utilization See Vproc utilization Visual Basic 268 VPR Alocs/Sec 178 Vproc Ave 93 Vproc level performance event, defining 244 Vproc Max 93 Vproc Min 93 Vproc utilization details, displaying 95, 112 monitoring 94 Vproc Utilization Detail Report 95 Vproc Utilization Report 94 VprocSummary object 272 W Wait I/O CPU % 98, 156 Wal Cyls # Cyls 192 % of Total Avail Cyls 192 WD Override 160 Window menu 43 WIO % 168, 173 Workload Definition Detail Report 130 workload definition details, displaying 128 Workload Definition Summary History Report 132 Workload Definition Summary Report 129 Workload Definition Usage Report 149 Workload Delay Queue Detail Report 124 Workload Delay Queue History Report 125 Workload Delay Queue List Report 113 Workload Delay Queue Session List 126 workload list, refreshing 37 Workload Management API documentation 7 Workload object 284 workload trends, analyzing CPU utilization 135 defining system parameters for 57 disk i/o utilization 138 heartbeat query response time 144 spool/temp space usage 142 table growth 140 user count 146, 147, 150, 155, 158, 163, 164 Workloads 284 Teradata Manager User Guide 317

318 Index Writes/Sec 176, 177 Wt KB / I/O Teradata Manager User Guide