Teradata RDBMS Utilities Volume 2 G-S - …dbmanagement.info/Books/MIX/Teradata_Vol_2_V2R4... ·...

Teradata® RDBMSUtilities - Volume 2G-S

V2R5.0

B035-1102-122ADecember 2002

The product described in this book is a licensed product of NCR Corporation.

BYNET is an NCR trademark registered in the U.S. Patent and Trademark Office.CICS, CICS/400, CICS/600, CICS/ESA, CICS/MVS, CICSPLEX, CICSVIEW, CICS/VSE, DB2, DFSMS/MVS, DFSMS/VM, IBM, NQS/MVS, OPERATING SYSTEM/2, OS/2, PS/2, MVS, QMS, RACF, SQL/400, VM/ESA, and VTAM are trademarks or registered trademarks of International Business Machines Corporation in the U. S. and other countries.DEC, DECNET, MICROVAX, VAX and VMS are registered trademarks of Digital Equipment Corporation.HEWLETT-PACKARD, HP, HP BRIO, HP BRIO PC, and HP-UX are registered trademarks of Hewlett-Packard Co.KBMS is a trademark of Trinzic Corporation.INTERTEST is a registered trademark of Computer Associates International, Inc.MICROSOFT, MS-DOS, MSN, The Microsoft Network, MULTIPLAN, SQLWINDOWS, WIN32, WINDOWS, WINDOWS 2000, and WINDOWS NT are trademarks or registered trademarks of Microsoft Corporation.SAS, SAS/C, SAS/CALC, SAS/CONNECT, and SAS/CPE are registered trademarks of SAS Institute Inc.SOLARIS, SPARC, SUN and SUN OS are trademarks of Sun Microsystems, Inc.TCP/IP protocol is a United States Department of Defense Standard ARPANET protocol.TERADATA and DBC/1012 are registered trademarks of NCR International, Inc.UNICODE is a trademark of Unicode, Inc.UNIX is a registered trademark of The Open Group.X and X/OPEN are registered trademarks of X/Open Company Limited.YNET is a trademark of NCR Corporation.

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 NCR CORPORATION (NCR) 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 NCR intends to announce such features, functions, products, or services in your country. Please consult your local NCR 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. NCR 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 e-mail: [email protected]

or write:

Information EngineeringNCR Corporation100 North Sepulveda BoulevardEl Segundo, CA 90245-4361U.S.A.

Any comments or materials (collectively referred to as “Feedback”) sent to NCR will be deemed non-confidential. NCR 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, NCR 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 © 1996-2002, NCR CorporationAll Rights Reserved

mailto:[email protected]

Preface

Supported Software Release

This book supports Teradata RDBMS V2R5.0.

Changes to This Book

This book, Teradata RDBMS Utilities, consists of three volumes:

• Volume 1 includes utilities A-F.• Volume 2 includes utilities G-S.• Volume 3 includes utilities T-Z.

Some utilities are platform specific. Those are identified as either “NCR UNIX MP-RAS Only” or “Microsoft Windows 2000 Only.” If a utility runs on both platforms, no differentiation appears.

This volume includes the following changes to support the current release:

Date Utility Description

December 2002 Gateway Control

• On Windows 2000, the valid range for fLogfilesize is 1000 through 2147483647.

• On Windows 2000, the default for sSessions is 600. The valid range is 0 through 21474836347.

• If you change the maximum sessions per node, the following occurs:– On Windows 2000, the limit is effective immediately.– On UNIX MP-RAS, the limit is effective immediately or after a tpareset,

depending on the size of the limit at the last tpareset.

Locking Logger • In the "Producing a Lock Log Report" example, a locking modifier is added.

• A Messages section is added.

• A new session number added to the BLKINGSESSNO column in the Lock Log Report: 3 - Archive/Restore

• *63127 - The CREATE TABLE statement examples have been changed to reflect the following:

– column begdatetime has a format of 'zzz,zzz,zzz,zzz.zzz' instead of 'zzz,zzz,zzz,zzz.zz9'.

– column logondatetime to have a format of 'z,zzz,zzz,zzz,zzz.zzz' instead of 'z,zzz,zzz,zzz,zzz.zz9'.

modmpplist • An error in the WRITE command syntax diagram is corrected.

Teradata RDBMS Utilities - G-S i

Preface

December 2002 (cont.)

pdeconfig • This chapter is completely redesigned, including the following:– Planning PDE configuration– In-depth procedures and screens– Example setup

• The new command line feature has the following options:– Moves AMP and or PE vprocs.– Runs in non-PDE environment.– Runs in Multimedia environment, such as for Prospector.– Reconstructs the vconfig.out file from the VCONFIG GDO and

distributes the file to all nodes.– Updates with current information from mpplist file.

• EMC disk arrays are supported.

• You must start pdeconfig on the PDN node of the existing system. If you run pdeconfig on any new nodes, you could lose all user data on the existing system.

Priority Scheduler

• The new Priority Scheduler Simulator (PSS), a Microsoft Excel spreadsheet, allows you to generate “what-if” situations with different priority attributes. PSS allows you to emulate Priority Scheduler weighting configurations to determine expected relative weights for various activity situations.

• Performance Period milestone type Resource Usage is broken into two components:

– Session resource usage (S or R) milestone limits are specified in seconds and define an amount of session CPU resource consumption per node.

– Query resource usage (Q) milestone limit is specified in seconds and define an amount of query CPU resource consumption per node.

• In schmon -m and -M command displays, the % Use column is replaced with % Avg CPU and % Avg I/O columns:

– The CPU data is shown in two columns: % and msec.– The I/O data is shown in two columns: % and sblks.

• The following options are added to the schmon -a command:– -s displays Priority Scheduler data for all sessions controlled by the

allocation group on the current node.– -S displays Priority Scheduler data for all sessions controlled by the

allocation group on all nodes of the system. – X means that the allocation group is expected to process expedited

work.


Teradata RDBMS Utilities - G-Sii

Preface


Priority Scheduler (cont.)

• The following options are added to the schmon -b command:– -s displays Priority Scheduler data for all sessions controlled by the

resource partition on the current node.– -S displays Priority Scheduler data for all sessions controlled by the

resource partition on all nodes of the system. – Limit is a percentage weight limit on total CPU usage by all processes

controlled by a resource partition.

• The new -f command reads schmon commands from a file or standard input device.

• The new -l command sets the system CPU usage limit.

• The following options are added to the schmon -p command:– -s displays Priority Scheduler data for all sessions controlled by the

performance group on the current node.– -S displays Priority Scheduler data for all sessions controlled by the

performance group on all nodes of the system.

• The new -s command displays information about each session or request that is active on the node where you invoked the command as well as Priority Scheduler data for the specified sessions from the current node or all nodes in the system.

• The new -w command sets or displays the number of processes available on each vproc for use by work requests assigned to allocation groups having the Expedite attribute.

Query Session • You can exit Query Session by entering the quit; command.

• Query Session reports the index analysis state pertaining to the Teradata Index Wizard. If a workload is being analyzed for indexes, session state information is displayed.

Reconfiguration • The following options are added to the RECONFIG command:– DISPLAY enables or disables output of Reconfiguration status.– n TASKS limits the number of Reconfiguration sessions running in

parallel.– PRIORITY p is the priority string determined by Priority Scheduler. – STATISTICS enables or disables output of Reconfiguration statistics.

• The new STATUS command allows you to determine the status of Reconfiguration at any time.

• Sample output for RECONFIG and STATUS commands is added.


Teradata RDBMS Utilities - G-S iii

Preface


Reconfiguration Estimator

The new Reconfiguration Estimator utility estimates an elapsed time for reconfiguration based upon the number and size of tables on your current system and provides estimates for the following phases:

• Redistribution• Deletion• NUSI building

Resource Check Tools

• The following changes are made to options of the nodecheck command:

– -D displays threshold values for -nodeonly and -timercontrol tunables in syscheckrc format.

– -f log overrides the default log file location as specified in the -L option.– -I lists threshold values for -nodeonly and -timercontrol tunables.– -L logs the output to a file in the /tpi-data directory on the node where

nodecheck is run. – -r rscfile specifies an additional syscheckrc file to be read and processed

that will override the values processed in the default syscheckrc file. – -s is removed.– -t directs nodecheck to read node-level resource data from a previously

created log file.

• The following new sections are added to nodecheck:– Creating a Log File – Messages

• The following changes are made to options of the syscheck command:– -D displays threshold values for -nodeonly and -timercontrol tunables

in syscheckrc format.– -f log overrides the default log file location as specified in the -L option.– -I lists threshold values for -nodeonly and -timercontrol tunables.– -L logs the output to a file in the /tpi-data directory on the node where

nodecheck is run. – -r rscfile specifies an additional syscheckrc file to be read and processed

that will override the values processed in the default syscheckrc file. – -t n directs nodecheck to read node-level resource data from a

previously created log file (with a default name) on each node. – -t logfilename is removed.– -v displays all the resource values for each node, evaluates the resource

values, and notifies you of the status of all tunable resources, regardless of level.


Teradata RDBMS Utilities - G-Siv

Preface


Resource Check Tools (cont.)

• The following new sections are added to syscheckrc:– The Default syscheckrc File– Creating an Optional syscheckrc File– Default syscheckrc File Example– Testdriver Section– Nodeonly Section– Timercontrol Section– Modified syscheckrc File Example

• nodecheck, syscheck, and syscheckrc have been completely updated with new examples.

RSSMon The RSSMon utility now comes with seven standard configuration files.

sysinit This chapter is completely reorganized into procedure format.

Appendix B A Frequently Asked Questions appendix for Priority Scheduler is added.

Appendix C This new appendix lists links to starting and exiting information for each utility.

June 2001 Locking Logger Locking Logger has the following modifications:

• If the ratio of AMPs to IFPs is six to one or higher, Locking Logger cannot run in continuous mode.

• Information on how to enable Locking Logger using the DBS Control utility is included.

• To create a lock log table, you must have CREATE TABLE privileges.• A new sample input is included.

modmpplist The new utility modmpplist allows you to modify the node list file (mpplist).

pdeconfig A new example is added for the RSG Vproc Mapping Screen.

Priority Scheduler

Priority Scheduler has the following modifications:

• The utility is available on Windows 2000.• Additional examples, procedures, and expanded text are included. • An overview of components and the default settings are added.

Query Session Query Session now exits on Windows 2000 by pressing the Enter key.


The new Resource Check Tools utility identifies a slow down or hang of the Teradata RDBMS and provides system statistics that could lead to the causes.

Teradata MultiTool

Teradata Utility has been renamed Teradata MultiTool and the graphical user interface and functionality is improved.


Teradata RDBMS Utilities - G-S v

Preface

June 2001 (cont.)

Update DBC The new Update DBC utility recalculates the following:

• The PermSpace and SpoolSpace values in the DBASE table for the user DBC

• The MaxPermSpace and MaxSpoolSpace values of the DATABASESPACE table for all databases based on the values in the DBASE table.

Update Space The new Update Space utility recalculates the permanent, temporary, or spool space used by a single database or by all databases in a system.

vpacd Now you can start vpacd using the new vpacadm script.

xctl • Information on using xctl in the non-windowing mode is added.• In the DBS Settings window and Screen DBS command, the Minimum

Nodes Per Clique is automatically calculated by PDE during initial system installation and each time the system is started. Manually revised values remain in effect until the system restarts.

• The DBS Settings window and Screen DBS command contain the new Battery Status field that allows you to set the battery status for the system.

• The RSS Settings window and Screen RSS command contain the new RSS Sub Table Enable section that allows you to enable or disable logging of SCSI or PDISK data to the ResUsageSldv table.

• The Screen Version command contains the Running RSG field and the Desired RSG fields to display the running versions.

September 2000 Added Windows NT/Windows 2000 information to applicable utilities.

June 2000 • The Lock Display utility has been added.• The Locking Logger utility processor query has changed.• The pdeconfig utility automatically creates the alias

SYSTEMNAMEbynetc for all the nodes in the configuration. (UNIX MP-RAS-only)

• The Query Session utility now displays the date as YY/MM/DD.• The Reconfiguration utility has improved base performance and

contains new stored procedures information.• The Recovery Manager utility provides a method to measure and

predict down AMP recovery time. • The Table Rebuild utility contains new stored procedures information.• The Teradata Utility has been added to access the ctl, Database

Initialization Program, DBS Control, and Vproc Manager utilities.• The xctl utility improvements include the following:– Allows you to specify whether a snapshot dump will cause the

Teradata RDBMS to crash or not.– Notifies you when a change to a tunable value requires a reset or reboot

to be effective.


Teradata RDBMS Utilities - G-Svi

Preface

June 1999 • The ctl utility has been added. • The xctl utility has been revised for clarification. Added screen captures

and menu bar information for windows and revised text for clarity.

April 1999 • The Ferret utility has been revised to clarify general command syntax and usage. In addition, much of the information in the PACKDISK and SCOPE commands has been expanded and revised.

• The Gateway Control utility has been revised into two separate chapters for clarification:

– Gateway Control utility– Gateway Global Control Utility• The PDE Priority Scheduler has been revised and updated.

December 1998 • The SCOPE command in the Ferret Utility has been updated. • The Priority Scheduler is a new utility.


Teradata RDBMS Utilities - G-S vii

PrefaceAbout This Book

About This Book

Purpose

This book describes the utility programs that support the Teradata Relational Database Management System (RDBMS). The subjects covered in this book include utilities G through T. Use this book in conjunction with Teradata® RDBMS Utilities, Volume 1 and Teradata® RDBMS Utilities, Volume 3.

Audience

The utilities described in this book are used primarily by Teradata Support Center (TSC) field engineers, RDBMS developers, System Test and Verification, and system administrators. For example, these utilities are used to display control parameters, display DBS control record fields, find and correct problems within the file system, initialize the Teradata RDBMS, rebuild tables in the database, and manage the virtual processors (vprocs). These utilities are used to abort transactions and processes; monitor system performance, resources, and status, perform internal system checking, and perform system configuration, initialization, recovery, and tuning.

Users should also be familiar with the RDBMS console running the Database Window (DBW) and your client (host) system.

Experienced utilities users can also refer to the simplified command descriptions in the Teradata RDBMS Utilities Quick Reference. This book provides the syntax diagrams and a brief description of the syntax variables for each Teradata RDBMS utility.

How This Book Is Organized

This document contains 16 chapters, three appendixes, and an index:

Chapter 1: “Gateway Control Utility” describes how to modify default values in the fields of the gateway control globally distributed object (GDO).

Chapter 2: “Gateway Global Utility” describes how to monitor and control the sessions of Teradata LAN-connected users.

Chapter 3: “Lock Display Utility” provides a snapshot capture of all real-time database locks and their associated currently running jobs.

Chapter 4: “Locking Logger Utility” describes how to create a table of information extracted from RDBMS transaction logs.

Chapter 5: “modmpplist Utility (Microsoft Windows 2000 Only)” allows you to modify the node list file (mpplist).

Chapter 6: “pdeconfig Utility (NCR UNIX MP-RAS Only)” describes how to configure the Parallel Database Extensions (PDE) on a system.

Teradata RDBMS Utilities - G-Sviii


Chapter 7: “Priority Scheduler” describes how to prioritize process scheduling through the use of resource partitions for groups of processes or users.

Chapter 8: “Query Configuration Utility” describes how to display configuration information about a node in the RDBMS.

Chapter 9: “Query Session Utility” describes how to monitor the states of all or selected database sessions on all or selected logical host IDs attached to the Teradata RDBMS.

Chapter 10: “Reconfiguration Utility” describes how to define or modify an RDBMS.

Chapter 11: “Reconfiguration Estimator Utility” estimates an elapsed time for reconfiguration based upon the number and size of tables on your current system.

Chapter 12: “Recovery Manager Utility” describes how to monitor the progress of a system in recovery.

Chapter 13: “Resource Check Tools” identifies a slow down or hang of the Teradata RDBMS and provides system statistics that could lead to the cause of the slow down or hang.

Chapter 14: “RSSmon Utility (NCR UNIX MP-RAS Only)” describes how to collect data using the Resource Sampling System (RSS) of PDE.

Chapter 15: “Showlocks Utility” describes how to display information about host utility locks placed on databases and tables by the Archive and Recovery utility during database operations.

Chapter 16: “System Initializer Utility” describes how to initialize the Teradata RDBMS.

Appendix A: “How to Read Syntax Diagrams” describes the conventions that apply to reading the syntax diagrams used in this book.

Appendix B: “Priority Scheduler Frequently Asked Questions (FAQ)” contains frequently asked questions and answers about Priority Scheduler.

Appendix C: “Starting and Exiting Utilities” includes links to starting and exiting information for each utility.

Prerequisites

You should be familiar with the following operations:

• Using a command line to run the pdeconfig utility on the Package Distribution Node (PDN).

• Using the Database Window (DBW) to run the other utilities.

Teradata RDBMS Utilities - G-S ix


In addition, you might want to review the following related books:

• Teradata RDBMS Database Window• Teradata RDBMS Performance Optimization• Teradata RDBMS Resource Usage Macros and Tables• Platform-dependent Teradata RDBMS Installation/Upgrade/Migration

documents

For detailed information about Archive/Recovery, FastExport, FastLoad, MultiLoad, and TPump utilities, refer to the appropriate client utilities books.

Teradata RDBMS Utilities - G-Sx

PrefaceList of Acronyms

List of Acronyms

The following acronyms, which the following table lists in alphabetical order:

AMP Access Module Processor

AWT AMP Work Task

CPU Central Processing Unit

DB Data Block

DBW Database Window

DIP Data Initialization Program

DML Data Manipulation Language

DUL Dump Unload/Load

FSG Three-character functional code group name for a PDE code subsystem.

GDO Globally Distributed Objects

GRAW Group Resource Allocation Group

LAN Local Area Network

MLOAD MultiLoad

MPP Massively Parallel Processing

ODS Operational Data Store

PDE Parallel Database Extensions

PDN Package Distribution Node

PE Parsing Engine

PJ Permanent Journal

PROC Procedural Management Subsystem

QFC Query Capture Feature

RDBMS Relational Database Management System

RSS Resource Subsystem

SMP Symmetric Multi-Processing

SQL Structured Query Language

TDP Teradata Director Program

TLE Target Level Emulation

Teradata RDBMS Utilities - G-S xi

PrefaceList of Acronyms

TPA Trusted Parallel Application

TSC Teradata Support Center

TUVT Teradata Utilities Verification Tool

UTC Universal Coordinated Time

vpacd Virtual Process Controller

vproc virtual processor

xpsh Parallel Shell Tool

xpt Cross Package Tools

Teradata RDBMS Utilities - G-Sxii

PrefaceTechnical Information on the Web

Technical Information on the Web

The NCR home page (http://www.ncr.com) provides links to numerous sources of information about Teradata. Among the links provided are sites that deal with the following subjects:

• Contacting technical support• Enrolling in customer education courses• Ordering and downloading product documentation• Accessing case studies of customer experiences with Teradata• Accessing third party industry analyses of Teradata data warehousing

products• Accessing white papers• Viewing or subscribing to various online periodicals

Teradata RDBMS Utilities - G-S xiii

http://www.ncr.com

PrefaceTechnical Information on the Web

Teradata RDBMS Utilities - G-Sxiv

Contents

Preface

Supported Software Release ............................................................................................ iChanges to This Book ....................................................................................................... i

About This Book .............................................................................................................. viiiList of Acronyms ................................................................................................................ xiTechnical Information on the Web.................................................................................xiii

Chapter 1: Gateway Control UtilityStarting and Exiting Gateway Control on UNIX MP-RAS........................................ 1–2Starting and Exiting Gateway Control on Microsoft Windows 2000 ...................... 1–3Gateway Log Files ........................................................................................................... 1–4Inputting Gateway Control Options ............................................................................ 1–5Gateway Control Options .............................................................................................. 1–6Changing Maximum Sessions Per Node ................................................................... 1–10

Chapter 2: Gateway Global UtilityStarting and Exiting Gateway Global on UNIX MP-RAS ......................................... 2–3

From the Database Window ....................................................................................... 2–3From the Command Line ............................................................................................ 2–4From the X Windows Interface Command Line...................................................... 2–4

Starting and Exiting Gateway Global on Microsoft Windows 2000 ........................ 2–5From the Database Window ....................................................................................... 2–5From Teradata Command Prompt ............................................................................ 2–6From Teradata MultiTool ............................................................................................ 2–7

Gateway Global User Interfaces.................................................................................... 2–8Gateway Global Command Line Functions ................................................................ 2–9Specifying a Host........................................................................................................... 2–10Displaying Network and Session Information ......................................................... 2–11Administering Users and Sessions ............................................................................. 2–12Performing Special Diagnostics .................................................................................. 2–13Logging Sessions Off Using KILL............................................................................... 2–14Getting Help................................................................................................................... 2–15

Teradata RDBMS Utililties - G-S xv

Contents

DISABLE EXLOGON (UNIX MP-RAS Only) ........................................................... 2–16DISABLE LOGONS....................................................................................................... 2–17DISABLE TRACE .......................................................................................................... 2–18DISCONNECT SESSION (UNIX MP-RAS Only) ..................................................... 2–19DISCONNECT USER (UNIX MP-RAS Only) ........................................................... 2–20DISPLAY DISCONNECT............................................................................................. 2–22DISPLAY FORCE (Windows 2000 Only)................................................................... 2–23DISPLAY GTW .............................................................................................................. 2–24DISPLAY NETWORK................................................................................................... 2–27DISPLAY SESSION ....................................................................................................... 2–30DISPLAY STATS (Windows 2000 Only) .................................................................... 2–34DISPLAY TIMEOUT ..................................................................................................... 2–36DISPLAY USER ............................................................................................................. 2–37ENABLE EXLOGON (UNIX MP-RAS Only) ............................................................ 2–39ENABLE LOGONS........................................................................................................ 2–40ENABLE TRACE ........................................................................................................... 2–41FLUSH TRACE .............................................................................................................. 2–43HELP ............................................................................................................................... 2–44KILL SESSION ............................................................................................................... 2–46KILL USER...................................................................................................................... 2–47SELECT HOST ............................................................................................................... 2–49SET TIMEOUT ............................................................................................................... 2–50X Window Interface Gateway Global Functions (UNIX MP-RAS Only) .............. 2–51

Starting the Gateway Global Graphical Interface .................................................. 2–51Exiting the Gateway Global Graphical Interface .................................................. 2–51

Gateway Global Main Window................................................................................... 2–52Menu Bar......................................................................................................................... 2–54Display ............................................................................................................................ 2–55Summary and Session................................................................................................... 2–56Mode................................................................................................................................ 2–57Messages ......................................................................................................................... 2–59Session Window ............................................................................................................ 2–60

Chapter 3: Lock Display UtilityStarting and Exiting Lock Display on NCR UNIX MP-RAS..................................... 3–2Starting and Exiting Lock Display on Microsoft Windows 2000 ............................. 3–3

From the Database Window ....................................................................................... 3–3From Teradata Command Prompt............................................................................. 3–4From Teradata MultiTool ............................................................................................ 3–5

Lock Modes ...................................................................................................................... 3–6Lock-Mode Contention................................................................................................... 3–7

Teradata RDBMS Utililties - G-Sxvi

Contents

Explicit and Implicit Lock Modes ................................................................................. 3–8Lock Request Status ........................................................................................................ 3–9Lock Display Utility Commands................................................................................. 3–10BLOCKERS..................................................................................................................... 3–11DB .................................................................................................................................... 3–15HELP ............................................................................................................................... 3–18QUIT................................................................................................................................ 3–19ROWHASH .................................................................................................................... 3–20ROWRANGE ................................................................................................................. 3–23TABLE ............................................................................................................................. 3–25TRAN .............................................................................................................................. 3–27

Chapter 4: Locking Logger UtilityStarting and Exiting Locking Logger on NCR UNIX MP-RAS ................................ 4–2Starting and Exiting Locking Logger on Microsoft Windows 2000......................... 4–3

From the Database Window ....................................................................................... 4–3From Teradata Command Prompt ............................................................................ 4–4From Teradata MultiTool ............................................................................................ 4–5

Transaction Lock Log Information ............................................................................... 4–6Enabling the LockLogger Field in DBS Control Utility ............................................. 4–7Lock Logger Table Requirements ................................................................................. 4–8Lock Log Tables ............................................................................................................. 4–10Messages ......................................................................................................................... 4–15Producing a Lock Log Report...................................................................................... 4–16Example Log Files ......................................................................................................... 4–19Reducing the Size of the Tables................................................................................... 4–20Reducing the Size of the Lock Log Table .................................................................. 4–22Reducing the Size of the DBC.EventLog Table ........................................................ 4–23Inserting Rows ............................................................................................................... 4–24Determining the Blocked User .................................................................................... 4–27Hexadecimal and Non-Standard Names Support.................................................... 4–30

Chapter 5: modmpplist Utility (Microsoft Windows 2000 Only)Starting modmpplist ....................................................................................................... 5–2Editing the Default mpplist ........................................................................................... 5–3Editing a User-Specified mpplist .................................................................................. 5–4Using modmpplist........................................................................................................... 5–5DISPLAY .......................................................................................................................... 5–6LIST.................................................................................................................................... 5–7

Teradata RDBMS Utililties - G-S xvii

Contents

OFF id_list ......................................................................................................................... 5–8ON id_list .......................................................................................................................... 5–9QUIT................................................................................................................................ 5–10WRITE ............................................................................................................................. 5–11!COMMAND .................................................................................................................. 5–12

Chapter 6: pdeconfig Utility (NCR UNIX MP-RAS Only)About pdeconfig .............................................................................................................. 6–2Planning PDE Configuration ......................................................................................... 6–3Definitions of Terms Used in pdeconfig ...................................................................... 6–5Starting and Exiting pdeconfig...................................................................................... 6–7

Applying Changes and Exiting pdeconfig ............................................................... 6–8Discarding Changes and Exiting pdeconfig ........................................................... 6–10

Error Messages............................................................................................................... 6–12Configuring PDE ........................................................................................................... 6–13Task 1: Setting PDE to the NULL State ...................................................................... 6–14Task 2: Running pdeconfig .......................................................................................... 6–15pdeconfig Screens.......................................................................................................... 6–16Moving Between Screen Types.................................................................................... 6–17Jump Command ............................................................................................................ 6–18Continue Command...................................................................................................... 6–19Screen 1: TPA Summary ............................................................................................... 6–20Screen 2: Disk Array Summary ................................................................................... 6–22Screen 3: Disk Slicing Summary.................................................................................. 6–28Screen 4: Pdisk Mapping Summary............................................................................ 6–32Screen 5: LAN Summary .............................................................................................. 6–38Screen 6: Host Channel Summary............................................................................... 6–45Screen 7: Relay Services Gateway (RSG) TPA Mapping Summary ...................... 6–52Screen 8: Apply Changes.............................................................................................. 6–54Screen 9: Exit With No Changes to the System......................................................... 6–56Example Setup ............................................................................................................... 6–58Task 1: Gathering System Information....................................................................... 6–59Task 2: Configuring the Disk Array............................................................................ 6–61Task 3: Configuring Disk Slicing................................................................................. 6–63Task 4: Mapping Pdisks................................................................................................ 6–65Task 5: Mapping a LAN ............................................................................................... 6–67Task 6: Assigning Host Channels................................................................................ 6–69Task 7: Applying Changes ........................................................................................... 6–716210 Disk Array Special Procedure............................................................................. 6–74

Teradata RDBMS Utililties - G-Sxviii

Contents

Chapter 7: Priority Scheduler About Priority Scheduler ............................................................................................... 7–3

About Resource Partitions .......................................................................................... 7–3About Performance Groups and Allocation Groups .............................................. 7–3

Overview of Priority Scheduler Components............................................................. 7–5Priority Scheduler Default Settings .............................................................................. 7–7Using the Priority Scheduler.......................................................................................... 7–8Resource Partitions.......................................................................................................... 7–9

Resource Partition Parameters ................................................................................. 7–10Determining the Relative Weight of a Resource Partition ................................... 7–10Limiting Resource Partition CPU Usage................................................................. 7–11Suggestions for Using Resource Partitions............................................................. 7–11

Performance Groups ..................................................................................................... 7–13Performance Groups and Allocation Groups......................................................... 7–13Performance Group and Weight Defaults for Resource Partition 0 ................... 7–14

Performance Group Name........................................................................................... 7–15Recording the Performance Group Name in a User Record................................ 7–15Alternative Formatting for Default Resource Partition 0

Performance Group Names ................................................................................... 7–16Associating a Performance Group Name to a User............................................... 7–16Supplying Performance Group Names During an RDBMS

Session Logon........................................................................................................... 7–16Performance Group Value ........................................................................................... 7–17

Performance Group Values in Default Resource Partition 0 ............................... 7–17Performance Periods ..................................................................................................... 7–19

Performance Period Components ............................................................................ 7–20Performance Period Types and Limits....................................................................... 7–21

Time-of-day ................................................................................................................. 7–21Resource Usage........................................................................................................... 7–22

Allocation Groups ......................................................................................................... 7–23Allocation Group Parameters ................................................................................... 7–24Associating Allocation Groups to Performance Groups ...................................... 7–24

Set Division Type........................................................................................................... 7–25Expedite Attribute......................................................................................................... 7–26Allocation Group Weight ............................................................................................. 7–27

Determining Allocation Group Relative Weight ................................................... 7–27Number of Active Users Assigned to an Allocation Group

Affects Query Response Time ............................................................................... 7–29Scheduling Policy .......................................................................................................... 7–31

Using Scheduling Policies ......................................................................................... 7–34

Teradata RDBMS Utililties - G-S xix

Contents

Allocating Resources Using the ABSOLUTE Scheduling Policy......................... 7–34Allocating Resources Using the RELATIVE Scheduling Policy .......................... 7–36

Resource Accounting .................................................................................................... 7–37Set Age Time ............................................................................................................... 7–37Set Active Time ........................................................................................................... 7–37I/O Concurrency Level (Windows 2000 Only)...................................................... 7–38System CPU Usage Limit .......................................................................................... 7–38

AMP Work Task (AWT) Reservations and Limits ................................................... 7–39AWT Resource Allocation ......................................................................................... 7–39AWTs Reservation for Expedited Allocation Groups........................................... 7–40

schmon Utility................................................................................................................ 7–45schmon -a........................................................................................................................ 7–46schmon -b........................................................................................................................ 7–49schmon -d ....................................................................................................................... 7–51schmon -e ........................................................................................................................ 7–56schmon -E ....................................................................................................................... 7–57schmon -f ........................................................................................................................ 7–58schmon -h ....................................................................................................................... 7–59schmon -i......................................................................................................................... 7–60schmon -I ........................................................................................................................ 7–61schmon -l......................................................................................................................... 7–62schmon -m ...................................................................................................................... 7–64schmon -M ...................................................................................................................... 7–70schmon -p ....................................................................................................................... 7–78schmon -r ........................................................................................................................ 7–81schmon -R ....................................................................................................................... 7–82schmon -s ........................................................................................................................ 7–83schmon -t......................................................................................................................... 7–85schmon -w ...................................................................................................................... 7–87xschmon Utility.............................................................................................................. 7–89xschmon Main Window ............................................................................................... 7–90Main Window Menus ................................................................................................... 7–92File Menu ........................................................................................................................ 7–93Edit Menu ....................................................................................................................... 7–95View Menu ................................................................................................................... 7–101Getting Help................................................................................................................. 7–103

Chapter 8: Query Configuration UtilityStarting and Exiting Query Configuration on NCR UNIX MP-RAS....................... 8–2

From the Database Window ....................................................................................... 8–2From the Remote Console ........................................................................................... 8–3

Teradata RDBMS Utililties - G-Sxx

Contents

Starting and Exiting Query Configuration on Microsoft Windows 2000 ............... 8–5From the Database Window ....................................................................................... 8–5From Teradata MultiTool ............................................................................................ 8–6

About Query Configuration .......................................................................................... 8–8Vprocs and Physical Processors ................................................................................. 8–8Display Options ............................................................................................................ 8–8

Query Configuration Options ....................................................................................... 8–9ALL Option .................................................................................................................... 8–10Processors Option.......................................................................................................... 8–11Online Processors or Offline Processors Options ..................................................... 8–12AMPs Option ................................................................................................................. 8–13Online AMPS or Offline AMPs Options .................................................................... 8–14PEs Option...................................................................................................................... 8–15Online PEs and Offline PEs Options .......................................................................... 8–16Getting HELP ................................................................................................................ 8–17

Chapter 9: Query Session UtilityStarting and Exiting Query Session on NCR UNIX MP-RAS................................... 9–2

From the Database Window ....................................................................................... 9–2From the Remote Console ........................................................................................... 9–3

Starting and Exiting Query Session on Microsoft Windows 2000 ........................... 9–5From the Database Window ....................................................................................... 9–5From Teradata MultiTool ............................................................................................ 9–6

Query Session States ....................................................................................................... 9–8Parent and Child Sessions.............................................................................................. 9–9Query Session Displays ................................................................................................ 9–10Session State Display .................................................................................................... 9–12

Session State Details During Stored Procedure Execution................................... 9–13Session State Details Pertaining to the Teradata Index Wizard .......................... 9–13

State Information Displays........................................................................................... 9–14ABORTING State........................................................................................................... 9–15ACTIVE State ................................................................................................................. 9–16BLOCKED State ............................................................................................................. 9–17IDLE State ....................................................................................................................... 9–18INDOUBT State ............................................................................................................. 9–19INDOUBT PARSING State .......................................................................................... 9–20PARSING State ............................................................................................................. 9–21QUIESCED ABORT State ............................................................................................ 9–22QUIESCED ABORT WITH LOGOFF State ............................................................... 9–23QUIESCED INDOUBT State ....................................................................................... 9–24RESPONSE State............................................................................................................ 9–25

Teradata RDBMS Utililties - G-S xxi

Contents

Archive and Recovery Sessions State Displays......................................................... 9–26Active Parent Session with Regular Request Display.............................................. 9–27Active Parent Session with Directed Request Display............................................. 9–28Inactive Parent Session Display................................................................................... 9–29Child Session Display ................................................................................................... 9–30FastLoad Sessions State Displays................................................................................ 9–31Active Parent Session in a Loading Phase Display .................................................. 9–32Active Parent Session in a Nonloading Phase Display............................................ 9–33Inactive Parent Session in a Loading Phase Display................................................ 9–34Inactive Parent Session in a Nonloading Phase Display ......................................... 9–35Child Sessions Display.................................................................................................. 9–36MultiLoad Sessions State Displays ............................................................................. 9–37Preliminary Phase Session Display............................................................................. 9–38Application Phase Session for Apply Task Display ................................................. 9–39Application Phase Session for Delete Task Display ................................................. 9–41Active Parent Session in an Acquisition Phase Display .......................................... 9–42Inactive Parent Session in an Acquisition Phase Display........................................ 9–43Child Session in an Acquisition Phase Display ........................................................ 9–44FastExport Sessions State Displays ............................................................................. 9–45

Chapter 10: Reconfiguration UtilityBefore Starting Reconfiguration .................................................................................. 10–2

Disabling Logons ........................................................................................................ 10–2Enabling Logons ......................................................................................................... 10–3

Starting and Exiting Reconfiguration on NCR UNIX MP-RAS.............................. 10–4Starting and Exiting Reconfiguration on Microsoft Windows 2000 ...................... 10–6

From the Database Window ..................................................................................... 10–6From Teradata MultiTool .......................................................................................... 10–7

About Reconfiguration ................................................................................................. 10–9Vprocs........................................................................................................................... 10–9Physical Processors..................................................................................................... 10–9Configuration Utility Activities................................................................................ 10–9New Configuration Map ......................................................................................... 10–10Reconfiguration Utility Activities .......................................................................... 10–10Effects on Journal Tables ......................................................................................... 10–11Timestamps ............................................................................................................... 10–11

Reconfiguration Utility Commands ......................................................................... 10–12Reconfiguration Utility Process................................................................................. 10–13RECONFIG................................................................................................................... 10–21STATUS......................................................................................................................... 10–24STOP.............................................................................................................................. 10–27

Teradata RDBMS Utililties - G-Sxxii

Contents

Error Messages............................................................................................................. 10–28Reconfiguration Example........................................................................................... 10–29

Chapter 11: Reconfiguration Estimator UtilityStarting and Exiting Reconfiguration Estimator on NCR UNIX MP-RAS ........... 11–2Starting and Exiting Reconfiguration Estimator on Microsoft Windows

2000 ............................................................................................................................... 11–4From the Database Window ..................................................................................... 11–4From Teradata MultiTool .......................................................................................... 11–5

Chapter 12: Recovery Manager UtilityStarting and Exiting Recovery Manager .................................................................... 12–2Starting and Exiting Recovery Manager on NCR UNIX MP-RAS......................... 12–3

From the Database Window ..................................................................................... 12–3From the Remote Console ......................................................................................... 12–4

Starting and Exiting Recovery Manager on Microsoft Windows 2000 ................. 12–6From the Database Window ..................................................................................... 12–6From Teradata MultiTool .......................................................................................... 12–7

Priority Levels................................................................................................................ 12–9Online Transaction Recovery .................................................................................... 12–11Transaction Recovery Sequence ................................................................................ 12–12Multiple Recovery Sessions ...................................................................................... 12–13Deferred Transaction Recovery ................................................................................ 12–14Down AMP Recovery ................................................................................................. 12–15

Down AMP Recovery Operations Display........................................................... 12–15Recovering Down AMPs............................................................................................ 12–17Recovery Journal ........................................................................................................ 12–18Types of Recovery Journal Records.......................................................................... 12–19Changed Row Journal ................................................................................................ 12–20Ordered System Change Journal ............................................................................. 12–21Deferred Down AMP Recovery ............................................................................... 12–22Offline Catchup ........................................................................................................... 12–23Setting a Down AMP to Offline Catchup Mode ..................................................... 12–24Verifying if an Offline AMP is in Catchup Mode................................................... 12–26Online Catchup Mode ................................................................................................ 12–27Startup/Restart Messages .......................................................................................... 12–28Restarts.......................................................................................................................... 12–30

Automatic Restarts ................................................................................................... 12–30User-Initiated Restarts ............................................................................................. 12–30

Teradata RDBMS Utililties - G-S xxiii

Contents

Recovery Manager Commands ................................................................................. 12–31HELP ............................................................................................................................. 12–33LIST................................................................................................................................ 12–34

LIST STATUS ............................................................................................................ 12–35LIST STATUS proc-id............................................................................................... 12–39LIST LOCKS .............................................................................................................. 12–42

QUIT.............................................................................................................................. 12–43REBUILD/RECOVERY PRIORITY........................................................................... 12–44

Chapter 13: Resource Check Toolsdbschk ............................................................................................................................. 13–2nodecheck ....................................................................................................................... 13–6

Creating a Log File ..................................................................................................... 13–8syscheck ........................................................................................................................ 13–23The Default syscheckrc File........................................................................................ 13–30Creating an Optional syscheckrc File ....................................................................... 13–33

Chapter 14: RSSmon Utility (NCR UNIX MP-RAS Only)Starting and Exiting RSSmon....................................................................................... 14–2The Monitoring Configuration File............................................................................. 14–4Standard Configuration Files....................................................................................... 14–5Customized Configuration Files ................................................................................. 14–6Customizing a Configuration File............................................................................... 14–7Displaying ResUsage Data........................................................................................... 14–9

Chapter 15: Showlocks UtilityStarting and Exiting Showlocks on NCR UNIX MP-RAS ....................................... 15–2

From the Database Window ..................................................................................... 15–2From the Remote Console ......................................................................................... 15–3

Starting and Exiting Showlocks on Microsoft Windows 2000................................ 15–5From the Database Window ..................................................................................... 15–5From Teradata MultiTool .......................................................................................... 15–6

Host Utility Locks.......................................................................................................... 15–7Interpreting the Showlocks Display ........................................................................... 15–8

Conflicts ....................................................................................................................... 15–9

Teradata RDBMS Utililties - G-Sxxiv

Contents

Chapter 16: System Initializer UtilityStarting and Exiting SYSINIT on NCR UNIX MP-RAS........................................... 16–2Starting and Exiting SYSINIT on Microsoft Windows 2000 ................................... 16–3

From the Database Window ..................................................................................... 16–3From Teradata MultiTool .......................................................................................... 16–4

About System Initializer............................................................................................... 16–5Initializing the Teradata RDBMS ............................................................................. 16–5Setting a New System ................................................................................................ 16–5Setting a Previously Initialized System................................................................... 16–5Globally Distributed Objects..................................................................................... 16–5Configuration Maps ................................................................................................... 16–6Configuration and Reconfiguration Utilities.......................................................... 16–6

Using System Initializer ............................................................................................... 16–7

Appendix A: How to Read Syntax DiagramsSyntax Diagram Conventions........................................................................................A-2

Appendix B: Priority Scheduler Frequently Asked Questions (FAQ)Basic Concepts ................................................................................................................. B-2Priority Weighting & Resource Allocation .................................................................. B-8Performance Periods & Allocation Groups ............................................................... B-11

Appendix C: Starting and Exiting Utilities

Index ......................................................................................................................... Index–1

Teradata RDBMS Utililties - G-S xxv

Contents

Teradata RDBMS Utililties - G-Sxxvi

Chapter 1:

Gateway Control Utility

The Gateway Control Utility is a tool that you use to modify default values in the fields of the gateway control Globally Distributed Object (GDO).

For Teradata RDBMS for NCR UNIX MP-RAS and Teradata RDBMS 2.0.1 for Windows NT, gateways are limited to one per node.

For Teradata RDBMS 3.0.1 for Microsoft Windows NT, multiple gateways per node are supported, as long as the gateways belong to different host groups and have different IP addresses to listen on.

Each gateway can support up to 1200 sessions, depending on available system resources and the number of allotted Parser Engines (PEs).

Audience

Users of Gateway Control include the following:

• System engineers

Users should be familiar with the configuration of the Teradata RDBMS and performance of the gateway.

Teradata RDBMS Utilities - G-S 1 – 1

Chapter 1: Gateway Control UtilityStarting and Exiting Gateway Control on UNIX MP-RAS

Starting and Exiting Gateway Control on UNIX MP-RAS

You can start Gateway Control from the command line.

To start Gateway Control, do the following:

Step Action

1 Change to the /tgtw/bin directory.

2 At the command line, type the following:

gtwcontrol -option

Note: You must type an option when using Gateway Control. For a list of options, see “Gateway Control Options” on page 1-6.

3 Press Enter.

Teradata RDBMS Utilities - G-S1 – 2

Chapter 1: Gateway Control UtilityStarting and Exiting Gateway Control on Microsoft Windows 2000

Starting and Exiting Gateway Control on Microsoft Windows 2000

You can start Gateway Control from the Teradata Command Prompt.

To start Gateway Control, do the following:

Step Action

1 Select Start ->Programs ->Teradata RDBMS -> Teradata Command Prompt.

2 At the Teradata Command Prompt, type the following:

gtwcontrol -option

Note: You must type an option when using Gateway Control. For a list of options, see “Gateway Control Options” on page 1-6.


Chapter 1: Gateway Control UtilityGateway Log Files

Gateway Log Files

Function

The gateway log files include the assign and connect files. On Windows 2000, the assign and connect files are combined into a single file. The default location for these files is /tmp for the UNIX MP-RAS PDE. The default location for these files for Teradata for Windows 2000 is the temporary directory you specified for PDE at installation time. These log files are represented by the following format:

UNIX MP-RAS Syntax

TNT 2.0.1 Syntaxgtwyyyymmddhhmmss.log

TNT 3.0.1/Windows 2000 SyntaxGtw_vvvvv_yyyymmddhhmmss.log

where:

Syntax element … Is the …

g gateway.

a assign process.

c connect process.

y last digit of the four-digit year.

ddd day of the year (365 days).

hh hour (24-hour clock).

mm minutes.

ss seconds.

log log files.

yyyy four-digit year.

vvvvv vproc number.

ydddhhmmsslog

GT07A028

g

a

c


Chapter 1: Gateway Control UtilityInputting Gateway Control Options

Inputting Gateway Control Options

Gateway Control options are case sensitive and must include a dash before the option letters when using either the UNIX MP-RAS or Windows 2000 operating system.

The following example gives the syntax for the help option that you use to list the syntax for all gateway control options.

gtwcontrol -h

When a gateway option requires a field value, that option includes a field name where you define the value.

For example, to select the host group number 1 on which to perform an action, you would use the option gHostnumber as shown in the example below:

gtwcontrol -g1

where the Hostnumber for the option is 1.

You can combine options by entering them, separated by a space. Using the above example, you can set the maximum number of sessions for host group 1 to 600 by entering the following command:

gtwcontrol -g1 -s600


Chapter 1: Gateway Control UtilityGateway Control Options

Gateway Control Options

The following table describes these options:

• Gateway Control options that run only on Teradata RDBMS for Windows 2000.

• gtwcontrol control options that run only on Teradata RDBMS for UNIX MP-RAS

• Gateway Control options that run on both Teradata RDBMS for Windows 2000 and UNIX MP-RAS.

Option DescriptionWindows 2000/UNIX MP-

RAS

aSSO Enables or disables permission of single sign on by a host group. You can set each value individually on each host group. The setting are as follows:

• On or ON allows single sign on if the RDBMS allows single sign on.

• Off or OFF does not allow single sign on even if the RDBMS allows single sign on.

• Only or ONLY allows only single sign on only if the RDBMS allows only single sign on.

Note: By default, the gateway single sign on option defaults to off when V4.1 of the gateway software is installed. If you set the RDBMS setting to Only or Off, that setting overrides the gateway setting.

Windows 2000

d Displays current GDO. Both

eEventcnt Specifies the number of event trace entries. Both

fLogfilesize Specifies the maximum log file size.

On Windows 2000, the valid range is 1000 through 2147483647.

The default is 5000000.

Both

gHostnumber Selects the host group.

When you do not specify this option in combination with another option, all hosts are selected.

Both

h Displays gtwcontrol options. Both



iInitialIothreads Initially starts up the number of threads specified by this option for the processing of LAN messages.

Two types of threads exist:

• One handles traffic from the client (that is, TCP/IP connections).

• One handles traffic from the database (that is, the PDE msgsystem).

The default is 5.

Windows 2000

lLogonname For remote gateway global access. (Not implemented in V2R4.1.)

Windows 2000

mMaximumIothreads Specifies maximum number of threads per type.




The default is 50.

Windows 2000

pPathname Specifies path to gateway log files. UNIX MP-RAS

rIoThreadCheck Determines the frequency in minutes that the gateway checks to see if all the threads are busy.

If they are all busy, a new thread of the appropriate type is started.

If more than one thread has not run during the rIoThreadCheck period, the gateway stops a thread.




The default is 10 minutes.

Windows 2000

sSessions Specifies maximum sessions for host group.

Limited to system resources.

UNIX MP-RAS

Specifies maximum sessions per vproc.

The valid range is 0 through 2147483647.

The default is 600.

Note: NCR recommends that you do not set the session number to 0 because you will be unable to logon.

Windows 2000


RAS



tTimeoutvalue Determines how long a disconnected session has to reconnect. If the client has not reconnected within the specified time period, the client is logged off automatically.

Note: During this time period, the session still counts against the number of sessions allocated to a PE.

The default is 20 minutes.

Both

vVprocnumber Selects a vproc.

When this option is not specified, all vprocs are selected.

Both

A Toggles assign tracing. Both

C Toggles connect wait.

Unnecessary for Windows 2000 because there is an assign task that runs as part of the connect task. Therefore, the W option is sufficient for both.

UNIX MP-RAS

Toggles connection tracing. Windows 2000

D Toggles no gtwdie. Both

E Toggles event trace. Windows 2000

F Toggles fast logon.

Toggling fast logon for Windows 2000 is unnecessary because fast logon is always enabled.

UNIX MP-RAS

Toggles append domain names on single sign on logon. Windows 2000

H Toggles connect heap trace. Both

I Toggles interactive mode. Windows 2000

J Toggles log LAN errors.

Logs any LAN-related errors even when properly handled by the gateway.

Windows 2000

K Toggles session ctx lock trace.

This option shows the session locking to make the session context multiprocessor safe.

Windows 2000

L Toggles enable logons. Both

M Toggles message tracing. Both

O Toggles output LAN header on errors.

Causes an error message to be written to the gateway log file.

Windows 2000

P Toggles assign heap trace. Both


RAS



Caution: The following options are only useful for debugging gateway problems and, in general, should not be specified: lGtwGlobal logon name, A, C, D, E, F, H, I, J, K, L, M, O, P, R, S, T, W, X, Y. Turning these options on results in slower gateway performance and in a potentially large amount of disk space consumption by the gateway control log files. Options lGtwGlobal logon name, L, and Z are the only options not specifically related to debugging.

R Toggles xport log all.

By default, the Xport trace does not log every LAN operation. The xport log all options causes all LAN operations to be logged.

This option only takes effect if the Y trace is on.

Windows 2000

S Toggles assign wait. UNIX MP-RAS

Toggles the action log.

The E event trace does not log the actions.

The S option turns on the action trace. It only takes effect if the E trace is on.

Windows 2000

T Toggles connect trace. UNIX MP-RAS

Toggles allow gateway testing. Windows 2000

W Toggles connect and assign wait. UNIX MP-RAS

Toggles wait for debugger to attach. Windows 2000

X Toggles xport trace. Both

Y Toggles handle trace. Windows 2000

Z Resets GDO to defaults. Windows 2000


RAS


Chapter 1: Gateway Control UtilityChanging Maximum Sessions Per Node

Changing Maximum Sessions Per Node

If your site runs jobs that are CPU or I/O intensive, you might find that a lower session limit gives better performance. To view the current maximum sessions per node, type the following:

gtwcontrol -d

On Windows 2000, the valid range for maximum sessions is 0 through 2147483647. NCR recommends that you do not set the session number to 0 because you will be unable to logon. Also, you cannot set the maximum sessions to a negative number.

To set the maximum sessions to 1000, type the following:

gtwcontrol -g1 -s1000

where 1 is the number of the host group and 1000 is the maximum sessions you want.

On Windows 2000, the new limit is effective immediately.

On UNIX MP-RAS, the following table describes when the new limit takes effect.

gtwcontrol notifies you of the following:

• Whether a tpareset is required for the new maximum session limit to become effective

• The current maximum sessions limit and the new maximum sessions limit if you did not restart the Teradata RDBMS after a change.

If more sessions are active than the new maximum sessions limit allows, then no new sessions are started. No new sessions can log on until the number of sessions is below the maximum sessions limit.

IF the new maximum session limit is … THEN the new limit takes effect …

less than 600 or less than the limit at the last tpareset (whichever is bigger)

immediately.

more than 600 and more than the limit at the last tpareset

after the next tpareset.

The current maximum session limit will default to the value at the last tpareset.


Chapter 2:

Gateway Global Utility

The Gateway Global utility allows you to monitor and control the sessions of Teradata database LAN-connected users. The gateway software runs as a separate operating system task and is the interface between the network and the Teradata RDBMS.

Client programs that communicate through the gateway to the Teradata RDBMS may be resident on the system, or they may be installed and running on network-attached workstations. Client programs that run on a channel-attached host bypass the gateway completely.

For Teradata RDBMS for NCR UNIX MP-RAS and Teradata RDBMS 2.0.1 for Microsoft Windows NT, gateways are limited to one per node.

For Teradata RDBMS 3.0.1 for Windows NT, multiple gateways per node are supported, as long as the gateways belong to different host groups and have different IP addresses to listen on.

Each gateway can support up to 1200 sessions, depending on available system resources and the number of allotted Parsing Engines (PEs). At least one PE that can support up to 120 sessions is required for each logical network attachment.

Note: When all the PEs in the DBS configuration are offline, Gateway Global exits, and the following message appears:

xgtwglobal cannot proceed as no PEs are online.

When all of the PEs in some of the host groups in the DBS configuration are offline, then Gateway Global displays the following notice and continues to process information for the host groups with at least one PE online:

NOTICE: xgtwglobal cannot process all the host groups as all the PEs on one or more of the host groups are offline.

The number of sessions per gateway is defined using the gtwcontrol utility. For information on configuring gateway options, see Chapter 1: “Gateway Control Utility.”

For information about configuring the gateway, see platform-dependent Teradata RDBMS Installation/Migration/Upgrade documents.

Note: Gateway errors are handled in the same manner as other RDBMS errors.


Chapter 2: Gateway Global Utility

Audience

Users of Gateway Global include the following:

• Field service representatives• Network administrators• System administrators

Users should be familiar with the administration of their network environment and the Teradata database software.


Chapter 2: Gateway Global UtilityStarting and Exiting Gateway Global on UNIX MP-RAS

Starting and Exiting Gateway Global on UNIX MP-RAS

You can type the command in uppercase letters, lowercase letters, or any combination of uppercase and lowercase letters.

Gateway Global is located in the tgtw/bin directory.

You can start and exit Gateway Global from the following:

• Database Window• Command Line• X Windows Interface Command Line

From the Database Window

To start Gateway Global, do the following:

Note: For details on the Database and Supervisor windows, see Teradata RDBMS Database Window.

Step Action

1 In the Database Window, select the Supervisor (Supvr) icon.

The Supervisor window appears.

2 In the Enter a command input subwindow of the Supervisor window, type the following:

start xgtwglobal -nw

3 Press Enter.

The Supervisor window displays the following:

Started 'xgtwglobal' in window 4.

The number represents the application window in which Gateway Global is running. The Gateway Global window appears.


Chapter 2: Gateway Global UtilityStarting and Exiting Gateway Global on UNIX MP-RAS

To exit Gateway Global, do the following:

From the Command Line


From the X Windows Interface Command Line


Step Action

1 In the Enter a command subwindow of the Gateway Global window, type one of the following:

quit

2 Press Enter.

The following message appears:

gtwglobal exiting. . .

3 In the Gateway Global window, select File -> Close.

4 In the Supervisor window, select File -> Close.

Step Action

1 Change to the tgtw/bin directory.

2 At the command line, type the following:

xgtwglobal -nw

3 Press Enter.

The Gateway Global window appears.

Step Action


2 At the X Windows interface command line, type the following:

xgtwglobal

3 Press Enter.



Chapter 2: Gateway Global UtilityStarting and Exiting Gateway Global on Microsoft Windows 2000

Starting and Exiting Gateway Global on Microsoft Windows 2000


Gateway Global is located in the tgtw/bin directory.

You can start and exit Gateway Global from the following:

• Database Window• Teradata Command Prompt• Teradata MultiTool



Note: For detailed information on the Database and Supervisor Windows, see Teradata RDBMS Database Window.

Step Action

1 Select Start -> Programs -> Teradata RDBMS -> Database Window.

The Database Window appears.



3 In the Enter a command subwindow of the Supervisor window, type one of the following:

• start gtwglobal

• start xgtwglobal

4 Press Enter.


Started 'gtwglobal' in window 4.

The number represents the application window in which Gateway Global is running. The Gateway Global window appears.




From Teradata Command Prompt



Step Action

1 In the Enter a command subwindow of the Gateway Global, type the following:

quit

2 Press Enter.



3 In the Gateway Global window, select File -> Close.


Step Action

1 Select Start -> Programs -> Teradata RDBMS -> Teradata Command Prompt.

The Teradata Command Prompt window appears.

2 In the Teradata Command Prompt window, type one of the following:

start gtwglobal

or

start xgtwglobal

3 Press Enter.


Step Action

1 In the Gateway Control window, type the following:

quit

2 Press Enter.





From Teradata MultiTool



Step Action

1 Select Start -> Programs -> Teradata RDBMS -> Teradata MultiTool.

The Teradata MultiTool main window appears.

2 In the Teradata MultiTool main window, select Tools -> Database Window (DBW).

The DBW appears.

3 Select the Supervisor tab.

4 In the Command field, type one of the following:

• start gtwglobal

• start xgtwglobal

5 Press Enter.

The Supervisor window displays the following message:

Started ‘gtwglobal’ in window 1.

The number represents the application window in which Gateway Global is running. The tab that previously said Application 1 now says Gateway Global and is the active window.

Step Action

1 In the DBW, select the Gateway Global tab.

2 In the Command field, type the following:

quit

3 Press Enter.


Gtwglobal exiting.

4 In the DBW, select File -> Exit.


Chapter 2: Gateway Global UtilityGateway Global User Interfaces

Gateway Global User Interfaces

You can use either Teradata Command prompt on Windows 2000, the UNIX command line, or X Window interface to monitor and control your network using Gateway Global. You can access most Gateway Global commands using the Windows 2000 environment. The X Window interface is available only with UNIX systems. Although the functions of the two interfaces are the same, the X Window interface does include some additional features.

This chapter is divided into two sections that explain the commands and syntax of the following two interfaces:

• Gateway Global UNIX MP-RAS/Windows 2000 Functions • Gateway Global X Window Interface

If the command is just for Windows 2000 or just for UNIX MP-RAS, the word “Only” appears after the heading. If the command is for Windows 2000 and UNIX MP-RAS, nothing is specified in the heading.


Chapter 2: Gateway Global UtilityGateway Global Command Line Functions

Gateway Global Command Line Functions

You use Gateway Global commands to perform the following functions:

• Display network and session information• Administer users and sessions• Perform routine and special diagnostics

The following sections summarize the functions of each command line command, including whether the command requires the use of SELECT HOST and if the command is available on UNIX MP-RAS, Windows 2000, or on both.

Following this section, each command is discussed separately in detail in alphabetical order.


Chapter 2: Gateway Global UtilitySpecifying a Host

Specifying a Host

Some commands require you to specify a host before you can initiate the command action. To specify a host, use the SELECT HOST command.

Command Function Windows 2000/UNIX MP-RAS

SELECT HOST Allows input of a specific host number to define the scope used by a subsequent command function.

Note: Selecting host 0 resets the host selection.

Both


Chapter 2: Gateway Global UtilityDisplaying Network and Session Information

Displaying Network and Session Information

DISPLAY commands allow you to display your network configuration, sessions, and vprocs associated with the gateway, plus information about specific sessions.

The following table lists the Display commands:

Command FunctionWindows 2000/UNIX MP-RAS

DISPLAY DISCONNECT

Displays a list of sessions that have disconnected.

Requires using the SELECT HOST command.

Both

DISPLAY FORCE Displays sessions that have been successfully killed or aborted using Performance Monitoring and Production Control (PMPC) abort process.

Windows 2000

DISPLAY GTW Displays all sessions connected to the gateway.

Both

DISPLAY NETWORK Displays network configuration information.

Both

DISPLAY SESSION Displays the following information on a specific session: User name, IP address, TCP socket number, state, event, action, partition, and RDBMS mailbox.


Both

DISPLAY STATS Displays the RSS statistics for the gateway vproc.

Windows 2000

DISPLAY TIMEOUT Displays the timeout value.


Both

DISPLAY USER Displays the session number, PE number, User name, IP address, and current connection status.


Both


Chapter 2: Gateway Global UtilityAdministering Users and Sessions

Administering Users and Sessions

You use the commands listed in the following table to control gateway traffic and access to the Teradata RDBMS:


DISABLE LOGONS Disables all logons to the Teradata RDBMS through the gateway.


Both

DISABLE EXLOGON Disables the EXLOGON option and reverses logons back to the normal path.

UNIX MP-RAS

ENABLE LOGONS Enables logons to the Teradata RDBMS through the gateway.


Both

ENABLE EXLOGON Enables and allows the gateway to choose the fast path when logging users onto the RDBMS.

This command greatly improves the logon response time.

UNIX MP-RAS

DISCONNECT USER Disconnects all sessions owned by a user.


UNIX MP-RAS

DISCONNECT SESSION

Disconnects a specific session.


UNIX MP-RAS

KILL SESSION Terminates a specific session.


Both

KILL USER Terminates all sessions of a specific user.


Both

SET TIMEOUT Sets a timeout value.


Both


Chapter 2: Gateway Global UtilityPerforming Special Diagnostics

Performing Special Diagnostics

Use the following trace commands to debug internal gateway errors or anomalies:


ENABLE TRACE Records internal gateway events.


Both

DISABLE TRACE Turns off the recording of event tracing and writing to the event log file on UNIX MP-RAS and to the gateway log file on Windows 2000.


Both

FLUSH TRACE Directs the gateway to write the contents of its internal trace buffers to the event log file on UNIX MP-RAS and to the gateway log file on Windows 2000.


Both


Chapter 2: Gateway Global UtilityLogging Sessions Off Using KILL

Logging Sessions Off Using KILL

When you issue a KILL command, any outstanding requests are first aborted. Then you are logged off. The following table describes the KILL command behavior.

Note: Aborting an outstanding request could take a significant amount of time. Therefore, killing a user does not necessarily free up the resources of a session immediately.

IF the session is currently … THEN …

disconnected the assign task attempts a log off by setting the KILL flag to indicate that an attempt has been made to log off.

logged on a kill message is sent to the connect task to abort any outstanding requests and then log off.


Chapter 2: Gateway Global UtilityGetting Help

Getting Help

To list all the Gateway Global commands, type help at the command line.


HELP Displays a menu of all the gtwglobal commands alphabetically, including the syntax for each command.

Both


Chapter 2: Gateway Global UtilityDISABLE EXLOGON (UNIX MP-RAS Only)

DISABLE EXLOGON (UNIX MP-RAS Only)

Function

The DISABLE EXLOGON command disables the EXLOGON option, and allows the gateway to choose the fast path when logging on users to the RDBMS.

For more information on EXLOGON, see the “ENABLE EXLOGON (UNIX MP-RAS Only)” on page 2-39.

Syntax

Usage Notes

You use the DISABLE EXLOGON function to disable a single host group or all host groups. To disable this option for a single host group, you must specify a host using the syntax SEL HOSTS hostid before issuing the DISABLE EXLOGON command.

If you fail to specify a host, the DISABLE EXLOGON command option affects all host groups. Once disabled, the option remains in effect until you change it.

Example

To disable the EXLOGON option, type the following:

disable exlogon

GT07B031

DISABLE

DISA

EXLOGON

EX


Chapter 2: Gateway Global UtilityDISABLE LOGONS

DISABLE LOGONS

Function

The DISABLE LOGON command prevents users from logging on to the Teradata RDBMS on the network using the gateway for the selected host.

Syntax

Usage Notes

The default setting of the logon flag is enabled. However, after a system restart, all host groups that were disabled remain disabled.

Any application that attempts to log on after DISABLE LOGONS is enabled results in the error message:

8033: Logon is disabled.

Note: Sessions already logged on are not affected by the DISABLE LOGONS command.

Before using the DISABLE LOGONS command, you must select the host from which the session is running using the SELECT HOST command. For information, see “SELECT HOST” on page 2-49.

For additional information, see “ENABLE LOGONS” on page 2-40.

Example

To prevent network users from logging on through the gateway to the Teradata RDBMS, type the following:

disable logons

GT07B003

DISABLE

DISA

LOGONS

LOGO


Chapter 2: Gateway Global UtilityDISABLE TRACE

DISABLE TRACE

Function

The DISABLE TRACE command turns off the recording of event tracing and writing to the event log file on UNIX MP-RAS and to the gateway log file on Windows 2000.

Syntax

Usage Notes

The default setting of the trace flag is disabled.

Note: If tracing has been enabled and you do not use the DISABLE TRACE command to turn it Off, the file system may become full.

Before using the DISABLE TRACE command, you must select the host from which the session is running using the SELECT HOST command. For information, see “SELECT HOST” on page 2-49.

For additional information, see “ENABLE TRACE” on page 2-41.

For information on the event and gateway log files, see Chapter 1: “Gateway Control Utility.”

Example

To turn Off the recording of event tracing and writing to the event log file or gateway log file, type the following:

disable trace

No report is generated.

GT07B004

DISABLE

DISA

TRACE

TRAC


Chapter 2: Gateway Global UtilityDISCONNECT SESSION (UNIX MP-RAS Only)

DISCONNECT SESSION (UNIX MP-RAS Only)

Function

The DISCONNECT SESSION command disconnects a specific session from the gateway utility.

Syntax

where:

Note: To list the possible values for ses_no, use the DISPLAY GTW or DISPLAY NETWORK command.

Usage Notes

Before using the DISCONNECT SESSION command, you must select the host from which the session is running using the SELECT HOST command. For information, see “SELECT HOST” on page 2-49.

The DISCONNECT SESSION command disconnects only the session identified by ses_no. This command does not require the actual processor number containing the session to be entered. After 20 minutes, the session is logged off, if the client has not reconnected during the timeout period.

Note: The 20-minute value is only a default. You can change the value using gtwcontrol or gtwglobal.

The DISCONNECT SESSION command is useful for testing application recovery when reconnecting is required.

Example

To disconnect session 1000 from the gateway control utility, type the following:

disconnect session 1000

The following statement displays:

Session 1000 scheduled to be disconnected.


ses_no session number (in decimal).

GT07C006

DISCONNECT

DISC

SESSION

SE

ses_no


Chapter 2: Gateway Global UtilityDISCONNECT USER (UNIX MP-RAS Only)

DISCONNECT USER (UNIX MP-RAS Only)

Function

The DISCONNECT USER command disconnects all sessions owned by a specific user originating from a specific host.

Syntax

where:

Note: To list the valid users for user_name, use “DISPLAY GTW” on page 2-24 or “DISPLAY SESSION” on page 2-30.

Usage Notes

Before using the DISCONNECT USER command, you must select the host from which the session is running using the SELECT HOST command. For information, see “SELECT HOST” on page 2-49.

The DISCONNECT USER command forces all sessions owned by the user_name to disconnect. This command does not require the actual processor number containing the sessions to be entered, just the user_name. After 20 minutes, the session is logged off, if the client has not reconnected during the timeout period.

Note: The 20-minute value is only a default. You can change the value using gtwcontrol or gtwglobal.

The DISCONNECT USER command is useful for testing application recovery when reconnecting is required.


user_name name of the user.

GT07C007

DISCONNECT

DISC

USER

US

user_name


Chapter 2: Gateway Global UtilityDISCONNECT USER (UNIX MP-RAS Only)

Example

To disconnect all sessions owned by a specific user, first specify the host using the SELECT HOST command, then type the following:

disconnect user systemfe

The following report displays:

User Systemfe has 2 sessions disconnected SessionNo---------10001001


Chapter 2: Gateway Global UtilityDISPLAY DISCONNECT

DISPLAY DISCONNECT

Function

The DISPLAY DISCONNECT command returns a list of sessions that have disconnected and not yet reconnected.

Syntax

Usages Notes

The context for these sessions is maintained in the gateway control assign task. If the client associated with the session fails to reconnect in the time allotted, the session is logged off.

Before using the DISPLAY DISCONNECT command, you must select the host from which the session is running using the SELECT HOST command. For information, see “SELECT HOST” on page 2-49.

Example

To display disconnected sessions, type the following:

di disc

Host Group 52 has 5 disconnected sessions:

Session PE User TimeToLive 1050 16383 DBC 1185 secs 1051 16383 DBC 1185 secs 1052 16383 DBC 1185 secs 1053 16383 DBC 1185 secs1054 16383 DBC 1185 secs

GT07B022

DISPLAY

DI

DISCONNECT

DISC


Chapter 2: Gateway Global UtilityDISPLAY FORCE (Windows 2000 Only)

DISPLAY FORCE (Windows 2000 Only)

Function

The DISPLAY FORCE command displays sessions that have been forced off because of a KILL command or a Performance Monitoring and Production Control (PMPC) abort command.

Syntax

Usage Notes

The system displays this information:

• Host number• Number of sessions • Session ID number• User name associated with the session• The length of time before the session information is discarded

The gateway retains the session information for the standard timeout period after the client has been logged off. The gateway returns an 8055 error when the client reconnects:

Session forced off by PMPC or gtwglobal

After the timeout period expires, the gateway discards the session information.

Example

To display a session that has been killed or aborted, type the following:

disp force

Host Group 1 has 2 forced sessions

Session User TimeToLive1002 DBC 916 secs1004 DBC 922 secs

FF07D356

DISPLAY FORCE

FODI


Chapter 2: Gateway Global UtilityDISPLAY GTW

DISPLAY GTW

Function

The DISPLAY GTW command displays all sessions connected to the gateway.

Syntax

where:

Note: To list all possible values for gtwid, use “DISPLAY NETWORK” on page 2-27.

Usage Notes

For the selected gateway, the system displays this information:

• Gateway vproc number• Host number• Number of sessions on the gateway• Session ID number• Internet address• User name associated with the session


gtwid number of the GTW processor containing the sessions you want to display.

ALL keyword that displays all sessions regardless of selected Host Group.

GT07C023

DISPLAY

DI

GTW

ALL

gtwid



Example 1

On Windows 2000, to display a gateway (for example, gateway 8192), type the following:

display gtw 8192

GTW 8192 has 18 sessions

Session PE User IP Adr Status1001 16383 DBC 141.206.35.30 CONNECTED1003 16383 DBC 141.206.35.30 CONNECTED1005 16383 DBC 141.206.35.30 CONNECTED1006 16382 DBC 141.206.35.30 CONNECTED1007 16383 DBC 141.206.35.30 CONNECTED1008 16382 DBC 141.206.35.30 CONNECTED1009 16383 DBC 141.206.35.30 CONNECTED1010 16382 DBC 141.206.35.30 CONNECTED1011 16383 DBC 141.206.35.30 CONNECTED1012 16382 DBC 141.206.35.30 CONNECTED1013 16383 DBC 141.206.35.30 CONNECTED1014 16382 DBC 141.206.35.30 CONNECTED1015 16383 DBC 141.206.35.30 CONNECTED1016 16382 DBC 141.206.35.30 CONNECTED1017 16383 DBC 141.206.35.30 CONNECTED1018 16382 DBC 141.206.35.30 CONNECTED1019 16383 DBC 141.206.35.30 CONNECTED1020 16382 DBC 141.206.35.30 CONNECTED



Example 2

To display all of the gateway sessions, type the following:

display gtw all

System pc316 has 20 connected sessions

HGID GTW Session PE User IP Adr 52 16384 1000 16383 DBC 128.0.0.1 52 16384 1001 16383 DBC 128.0.0.1 52 16384 1002 16383 DBC 128.0.0.1 52 16384 1004 16383 DBC 128.0.0.1 52 16384 1005 16383 DBC 128.0.0.1 52 16384 1006 16383 DBC 128.0.0.1 52 16384 1007 16383 DBC 128.0.0.1 52 16384 1008 16383 DBC 128.0.0.1 52 16384 1009 16383 DBC 128.0.0.1 52 16384 1010 16383 DBC 128.0.0.1 52 16384 1011 16383 DBC 128.0.0.1 52 16384 1012 16383 DBC 128.0.0.1 52 16384 1013 16383 DBC 128.0.0.1 52 16384 1014 16383 DBC 128.0.0.1 52 16384 1015 16383 DBC 128.0.0.1 52 16384 1016 16383 DBC 128.0.0.1 52 16384 1017 16383 DBC 128.0.0.1 52 16384 1018 16383 DBC 128.0.0.1 52 16384 1019 16383 DBC 128.0.0.1


Chapter 2: Gateway Global UtilityDISPLAY NETWORK

DISPLAY NETWORK

Function

The DISPLAY NETWORK command displays information about your network configuration and its associated gateway.

Syntax

where:

Usage Notes

The default setting for the DISPLAY NETWORK command is the short form report, which gives this information:

• Host number(s)• Total number of PEs assigned to host• Total number of gateways assigned to host• Total number of active sessions on the host• Total number of disconnected sessions• Tracing information (either Enabled or Disabled)• Logon event information (either Enabled or Disabled)

The long form displays the following information in addition to the information displayed in the short form report for the network:

• Vproc number in a group (gateway)• Total number of sessions connected to the listed vproc• Total number of sessions connected to the listed PE

If host_no is used to request a specific host number, the long form cannot be requested.


host_no host number (in decimal).

LONG display of the gateway statistics for the particular network.

GT07C009

DISPLAY

DI

NETWORK

NE LONG

LONhost_no

;



Example 1

To display information about your network configuration and its associated gateway in the short form on UNIX MP-RAS, type the following:

display network

Host 1 has 0 session(s) over 2 GTW(s) and 4 PE(s)( 0 Active / 0 Disconnected )

Gateway Sessions Logon EXlogon Trace ------- -------- -------- -------- --------16384 0 Enable Enable Disable 16385 0 Enable Enable Disable

Example 2

To display information about your network configuration and its associated gateway in the short form on Windows 2000, type the following:

display network

Host 2 has 0 session(s) over 1 GTW(s) and 1 PE(s)( 0 Active / 0 Disconnected / 0 Forced)

Gateway Sessions Logon Trace8193 0 Enable Disable

Host 1 has 20 session(s) over 1 GTW(s) and 2 PE(s)( 18 Active / 0 Disconnected / 2 Forced)

Gateway Sessions Logon Trace8192 18 Enable Disable

Example 3

To display information about your network configuration and its associated gateway in the long form on UNIX MP-RAS, type the following:

display network long


PE Sessions-------- --------16380 0 16383 0 16382 0 16381 0



Gateway Sessions Logon EXlogon Trace ------- -------- -------- -------- --------16384 0 Enable Enable Disable 16385 0 Enable Enable Disable

Example 4

To display information about your network configuration and its associated gateway in the long form on Windows 2000, type the following:

display network long


PE Sessions16382 5 16383 5

Gateway Sessions Logon Trace 16384 20 Enabled Enabled


Chapter 2: Gateway Global UtilityDISPLAY SESSION

DISPLAY SESSION

Function

The DISPLAY SESSION command returns a complete list of connected sessions regardless of the selected host group.

Syntax

where:

Note: To list the possible values for ses_no, use “DISPLAY GTW” on page 2-24.

Usage Notes

Before using the DISPLAY SESSION command, you must select the host from which the session is running using the SELECT HOST command. For information, see “SELECT HOST” on page 2-49.

The DISPLAY SESSION command displays only the session identified by ses_no.

By default, the system displays the short-form report containing the following information:

• User Name• IP address• Port• State• Event• Action• Partition (Windows 2000 only)• Authentication (Windows 2000 only)



LONG display of the gateway statistics for the particular session.

GT07C024

DISPLAY

DI

SESSION

SE

ses_no

LONG

LON



The Authentication field has four values, as shown in the following table.

The long-form report gives a detailed connect display for a selected session. The following is provided:

• RDBMS mailbox information.• The session number in the user information is shown in decimal.• All other values are shown in hexadecimal.

This information is useful for field service personnel when diagnosing gateway problems.

Procedure for Displaying a Session

To display a session, do the following:

The value … Indicates …

Database that the database provided the authentication method.

Note: This was the normal logon method before the implementation of single sign on.

Negotiate a single sign on using the Windows Negotiate authentication method.

NTLM a single sign on using the Windows NTLM authentication method.

KERBEROS a single sign on using the Windows KERBEROS authentication method.

Step Action

1 To select a host (for example, host 52), type the following:

se host 52

The system displays the following:

52>

2 To display a session (for example, session 1000), type the following:

display sess 1000



Example 1

To display the session in the default (or short) form on Windows 2000, type the following:

display 1001

Session 1001 connected to GTW 8192 is assigned to PE 16383 of host 1

User Name IP Addr Port--------------------- ---------------------- -------------ABC 141.206.7.56 30477

State Event Action --------------------- ---------------------- -------------CS_CLIENTWAITNOTRAN CE_STARTMSGRSPNOTRAN CA_SENDDBSRSP

Partition Authentication --------------------- -----------------DBC/SQL NTLM



Example 2

To display the session in the long form on Windows 2000, type the following:

di se 1001 long

Session 1001 connected to GTW 8192 is assigned to PE 16383 of host 1

User Name Account IP Addr Port--------------------- ---------------- ---------------- -------DBC DBC 141.206.7.56 30477

State Event Action --------------------- ---------------------------------- -------------CS_CLIENTWAITNOTRAN CE_STARTMSGRSPNOTRAN CA_SENDDBSRSP

Partition Authentication --------------------- -----------------DBC/SQL NTLM

StrMbx: 02 00 3fff 00000000 030e 02 00CntMbx: 02 00 3fff 00000000 040d 02 00AbtMbx: 02 00 3fff 00000000 030d 43 53

HostMessageReads: 2208HostBlockReads: 1104HostReadBytes: 92763DbsMessageReads: 1103HostMessageWrites: 1104HostBlockWrites: 1104HostWriteBytes: 3949759DbsMessageWrites: 1103


Chapter 2: Gateway Global UtilityDISPLAY STATS (Windows 2000 Only)

DISPLAY STATS (Windows 2000 Only)

Function

The DISPLAY STATS command allows you to display the statistics for the gateway vproc.

Syntax

where:


gtwid specified gateway vproc whose statistics are displayed.

ALL selected host group.

If you select a host group, gtwglobal returns the statistics for all the gateway vprocs in the selected host group.

If you do not select a host group, gtwglobal returns the statistics for all gateway vprocs.

GS02A013

DISPLAY STATS gtwid

DI ST ALL


Chapter 2: Gateway Global UtilityDISPLAY STATS (Windows 2000 Only)

Example 1

To display the statistics for the gateway vproc, type the following:

di st all

Gtw Vprocid: 8193HostMessageReads: 382HostBlockReads: 125HostReadBytes: 3829382DbsMessageReads: 108HostMessageWrites: 125HostBlockWrites: 125HostWriteBytes: 1167DbsMessageWrites: 104Gtw Vprocid: 8192HostMessageReads: 2220HostBlockReads: 1107HostReadBytes: 92919DbsMessageReads: 1103HostMessageWrites: 1107HostBlockWrites: 1107HostWriteBytes: 3950263DbsMessageWrites: 1103

Example 2

To display the statistics for gateway vproc 8192, type the following:

disp stats 8192

Gtw Vprocid: 8192HostMessageReads: 2220HostBlockReads: 1107HostReadBytes: 92919DbsMessageReads: 1103HostMessageWrites: 1107HostBlockWrites: 1107HostWriteBytes: 3950263DbsMessageWrites: 1103


Chapter 2: Gateway Global UtilityDISPLAY TIMEOUT

DISPLAY TIMEOUT

Function

The DISPLAY TIMEOUT command allows you to display the logoff delay in minutes for disconnected sessions.

Syntax

Example

Before using the DISPLAY TIMEOUT command, you must select the host from which the session is running using the SELECT HOST command. For information, see “SELECT HOST” on page 2-49.

To display the timeout logoff delay, type the following:

DI TI

Host 1 Timeout Value: 20 minutes

GT07C028

DISPLAY TIMEOUT

TIDI


Chapter 2: Gateway Global UtilityDISPLAY USER

DISPLAY USER

Function

The DISPLAY USER command returns a list of connected sessions whose names match userid.

Syntax

where:

Usage Notes

Before using the DISPLAY USER command, you must select the host from which the session is running using the SELECT HOST command. For information, see “SELECT HOST” on page 2-49.

The DISPLAY USER command displays this information:

• Session number• Parsing Engine that the session is assigned to• User name• IP address• Status indicating the following (Windows 2000 only):

– Connected– Forced– Gone– Killed



GT07C025

DISPLAY

DI

USER user_name

US


Chapter 2: Gateway Global UtilityDISPLAY USER

Example

On Windows 2000, to display a user (for example, user dbc), type the following:

disp user dbc

User DBC has 20 sessions

Session PE User IP Adr Status1001 16383 DBC 141.206.35.30 CONNECTED1002 0 DBC 141.206.35.30 FORCED1003 16383 DBC 141.206.35.30 CONNECTED1004 0 DBC 141.206.35.30 FORCED1005 16383 DBC 141.206.35.30 CONNECTED1006 0 DBC 141.206.35.30 GONE1007 16383 DBC 141.206.35.30 CONNECTED1008 16382 DBC 141.206.35.30 CONNECTED1009 16383 DBC 141.206.35.30 CONNECTED1010 16382 DBC 141.206.35.30 CONNECTED1011 16383 DBC 141.206.35.30 CONNECTED1012 16382 DBC 141.206.35.30 CONNECTED1013 16383 DBC 141.206.35.30 CONNECTED1014 16382 DBC 141.206.35.30 CONNECTED1015 16383 DBC 141.206.35.30 CONNECTED1016 16382 DBC 141.206.35.30 CONNECTED1017 16383 DBC 141.206.35.30 CONNECTED1018 16382 DBC 141.206.35.30 CONNECTED1019 16383 DBC 141.206.35.30 CONNECTED1020 16382 DBC 141.206.35.30 CONNECTED


Chapter 2: Gateway Global UtilityENABLE EXLOGON (UNIX MP-RAS Only)

ENABLE EXLOGON (UNIX MP-RAS Only)

Function

The ENABLE EXLOGON option defines the fast logon path to the Teradata RDBMS.

The ENABLE EXLOGON command allows the gateway to choose the fast path when logging users onto the Teradata RDBMS. This results in faster logon response time.

Syntax

Usage Notes

To enable this option for a single host group, you must specify a host using the syntax SEL HOSTS hostid before issuing the ENABLE EXLOGON command.

If you do not specify a host, the option is enabled for all host groups. After you enable the option, the option remains in effect until you change it.

For additional information, see “ENABLE LOGONS” on page 2-40.

Example

To choose the fast path logon option, type the following:

enable exlogon

GT07B030

ENABLE

EN

EXLOGON

EX


Chapter 2: Gateway Global UtilityENABLE LOGONS

ENABLE LOGONS

Function

The ENABLE LOGONS command allows users to log on to the Teradata RDBMS using the network through the gateway for the selected host.

Syntax

Usage Notes

The default setting of the logons flag is enabled.

Before using the ENABLE LOGONS command, you must select the host from which the session is running using the SELECT HOST command. For information, see “SELECT HOST” on page 2-49.

For additional information, see “SELECT HOST” on page 2-49 and “DISABLE LOGONS” on page 2-17.

Example

To allow users to log on to the Teradata RDBMS using the network through the gateway, type the following:

enable logons

GT07B012

ENABLE

EN

LOGONS

LOGO


Chapter 2: Gateway Global UtilityENABLE TRACE

ENABLE TRACE

Function

The ENABLE TRACE command turns on session tracing. The command records internal gateway events.

Syntax

Usage Notes

When ENABLE TRACE is enabled, the session tracing may contain some of these elements:

Note: Entries vary depending on the events and action taken.

• Session number (if available)• Associated file description (if available)• Event• One or more of these events:

– Assigned– Logged on– Logged off– Logoff forced (RDBMS killed session)– Logon failed (usually caused by invalid password)– Disconnected– Reassigned– Reconnected

• Network address of the originating network-attached host

By default, tracing is disabled. After a system restart, tracing enabled earlier using the ENABLE TRACE command is continued.

Caution: If tracing has been enabled and you do not use the DISABLE TRACE command to turn it off, the file system may become full.

Before using the ENABLE TRACE command, you must select the host from which the session is running using the SELECT HOST command. For information, see “SELECT HOST” on page 2-49.

GT07B013

ENABLE

EN

TRACE

TRAC


Chapter 2: Gateway Global UtilityENABLE TRACE

For additional information, see “DISABLE TRACE” on page 2-18. For information on the event and gateway log files, see Chapter 1: “Gateway Control Utility.”

Example

To turn on session event tracing, type the following:

enable trace


Chapter 2: Gateway Global UtilityFLUSH TRACE

FLUSH TRACE

Function

The FLUSH TRACE command directs the gateway to write the contents of its internal trace buffers to the gateway log file. Usually, these transitions are buffered before being recorded in gateway log files.

For the gateway log to accurately reflect all of the events processed by the gateway, you must issue a FLUSH TRACE command.

Syntax

Usage Notes

The FLUSH TRACE command can be used when diagnosing gateway anomalies.

For additional information, see “ENABLE TRACE” on page 2-41 and “DISABLE TRACE” on page 2-18.

Before using the FLUSH TRACE command, you must select the host from which the session is running using the SELECT HOST command. For information, see “SELECT HOST” on page 2-49.

For information on the event and gateway log files, see Chapter 1: “Gateway Control Utility.”

Example

To direct the gateway to write the contents of its internal trace buffers to the gateway log file, type the following:

flush trace

GT07B015

FLUSH

FL

TRACE

TRCE


Chapter 2: Gateway Global UtilityHELP

HELP

Function

The HELP command allows you to get help when using the xgtwglobal or gtwglobal commands.

Syntax

where:

Example

The following is an example of the Help commands for Gateway Global on UNIX MP-RAS:


help displays syntax for all the gtwglobal or xgtwglobal commands.

DISAble LOGOns ( disa logo * host must be selected)

DISAble EXlogon ( disa ex * host must be selected)

DISAble TRACe ( disa trac * host must be selected)

DISConnect SEssion ses_no ( disc se 1010 * host must be selected)

DISConnect USer user_name ( disc us joe * host must be selected)

DIsplay DISConnect ( di disc * host must be selected)

DIsplay GTW gtwid | ALL ( di gtw 16384 | ALL )

DIsplay NEtwork LONg | host_no ( di ne lon | 52 )

DIsplay SEssion ses_no [LONg] ( di se 1020 lon )

DIsplay TImeout ( di ti * host must be selected)

DIsplay USer user_name ( di us joe * host must be selected)

ENable LOGOns ( en logo * host must be selected)

ENable EXlogon ( en ex * host must be selected)

ENable TRACe ( en trac * host must be selected)

FLush TRACe ( fl trac * host must be selected)

GS07A022

HELP


Chapter 2: Gateway Global UtilityHELP

KIll SEssion ses_no ( ki se 1010 * host must be selected)

KIll USer user_name ( ki us joe * host must be selected)

SElect HOst host_no ( se ho 52 (select ho 0 to reset)

SET TImeout time_value ( set ti 30 * value in minutes )

QUIT

Enter gateway command or type h for Help:


Chapter 2: Gateway Global UtilityKILL SESSION

KILL SESSION

Function

The KILL SESSION command terminates the specified session on the Teradata RDBMS by aborting any active request on that session and logging the session off.

Syntax

where:

Note: To list the possible values for ses_no, use the “DISPLAY GTW” on page 2-24 or “DISPLAY NETWORK” on page 2-27.

Usage Notes

Before using the KILL SESSION command, you must select the host from which the session is running using the SELECT HOST command. For information, see “SELECT HOST” on page 2-49.

The KILL SESSION command specifies that the session identified by ses_no be terminated. This command leaves an audit trail in the error log.

Example

To terminate session 1000 on the network through the gateway, type the following:

kill session 1000

Session 1000 scheduled to be killed.



GT07C016

KILL

KI

SESSION

SE

ses_no


Chapter 2: Gateway Global UtilityKILL USER

KILL USER

Function

The KILL USER command terminates all sessions logged on to the Teradata RDBMS for the specified userid by aborting any active requests on those sessions and logging the sessions off.

Syntax

where:

Note: To list the possible values for user_name, use the “DISPLAY GTW” on page 2-24 or “DISPLAY SESSION” on page 2-30.

Usage Notes

Before using the KILL USER command, you must select the host from which the session is running using the SELECT HOST command. For information, see “SELECT HOST” on page 2-49.

The KILL USER command leaves an audit trail in the Windows 2000 event log or the RDBMS software event log, which shows the vproc that the kill was issued on and the session number of the user being killed.

An example is shown below.

Gtwglobal issued kill command: gtwassign.c @3205 (867): Fri Apr 14 13:39:01 2000 VprocId: 8193 Session Number: 1009

Note: Only the attempt to logoff the user is recorded, since the DBS might deny the logoff attempt.



GT07C017

KILL

KI

USER

US

user_name


Chapter 2: Gateway Global UtilityKILL USER

Example

To terminate all sessions logged on the network through the gateway by a specific user, type the following:

kill user systemfe

User Systemfe has 2 sessions killed: SessionNo---------10001001


Chapter 2: Gateway Global UtilitySELECT HOST

SELECT HOST

Function

The SELECT HOST command displays network information and is used in conjunction with subsequent Gateway Control command functions.

Syntax

where:

Usage Notes

The SELECT HOST command allows you to specify the host number of a network-attached host that will be affected by the subsequent Gateway Control command function that you type next.

Example

To select host 1, type the following:

select host 1

To deselect a host, type the following:

select host 0


host_no host number.

IF the Host number is… THEN the following message displays …

found Host 1 has been selected.

not found Invalid Host 1 is entered. Please try again!

GT07C026

SELECT

SE

HOST

HO

host_no


Chapter 2: Gateway Global UtilitySET TIMEOUT

SET TIMEOUT

Function

The SET TIMEOUT command allows you to set the time in minutes to delay a logoff for disconnected sessions.

Syntax

where:

Usage Notes

The SET TIMEOUT command can be used to delay logoff for disconnected sessions when working on network or database problems.

Before using the SET TIMEOUT command, you must select the host from which the session is running using the SELECT HOST command. For information, see “SELECT HOST” on page 2-49.

Example

To set a timeout delay for one hour, type the following:

SET TI 60

Timeout value on host 1 set to 60


time_value amount of time to delay logoff in minutes.

GT07C027

SET TIMEOUT

TI

time_value


Chapter 2: Gateway Global UtilityX Window Interface Gateway Global Functions (UNIX MP-RAS Only)

X Window Interface Gateway Global Functions (UNIX MP-RAS Only)

The X Window interface for Gateway Global provides much the same functionality as the command line version using various menus and windows.

Starting the Gateway Global Graphical Interface

To start the graphical interface, do the following:

Exiting the Gateway Global Graphical Interface


Step Action


2 Enter the following and press Enter:

Note: If you do not specify the optional parameter DISPLAY, you must set the system environment variable DISPLAY to the name of the desired X host.

The Gateway Global main window appears.

Step Action

1 In the Gateway Global window, select File -> Exit.

GX03A004

XGTWGLOBALDISPLAY


Chapter 2: Gateway Global UtilityGateway Global Main Window

Gateway Global Main Window

The Gateway Global Main window is shown below.

The Gateway Global Main window consists of six sections differentiated by function. The sections of the Main window are described in the following table.

Subsection Function

Menu Bar Displays the menu items.

Display Displays information relating to the system configuration or current utilization.

Summary Shows the sessions grouping based on the Display mode toggle button setting.

The button setting also changes the list column.

Session Shows all sessions that are grouped under an item you select in the Summary list.

Menu Bar

Display

Summary

Session

Mode

Messages


Chapter 2: Gateway Global UtilityGateway Global Main Window

Note: Press F1 with the cursor placed on a specific topic to display information about that topic.

Mode Allows you to disconnect or kill specified sessions or users.

Messages Contains various information related to the xgtwglobal operations.

Usually, the actions from the Mode buttons initiate these messages.

Subsection Function


Chapter 2: Gateway Global UtilityMenu Bar

Menu Bar

The following table explains the menu bar items available in the Display section of the main window.

Menu bar item Submenu item Description

File Save Messages Saves the capture buffer to a disk.

Clear Messages Deletes the contents of the capture buffer.

Exit Closes the main window display.

Sort User Sorts the current display by user name.

Filter IP Address Filters output by specified IP address.

If you activate this option, a message indicating this displays in the status window every time the display is updated.

System Logon Toggles network-connected client (gateway) logons.

Trace Toggles trace facilities in the gateway connect and assign tasks.

Timeout Indicates the time in minutes, which the gateway delays logoff processing for a disconnected session because of network or database problems.

Autorefresh Toggles autorefresh for xgtwglobal displays.

When you set the autorefresh On, xgtwglobal polls the connect and assign tasks in the system for information related to session status changes.

Help About xgtwglobal Displays help options.


Chapter 2: Gateway Global UtilityDisplay

Display

The box beneath the main menu bar contains display options. When you select one of the display options, information about that option displays in the box below and in the summary window. The following table explains the function of each of the options.

Option Function

HGID Displays the active host group identifiers.

When you select the HGID option, the system updates the summary window to reflect the current status of all the connected host groups.

If you select a host group from the summary window, the system updates the session detail window with a list of sessions connecting to the select host group.

By selecting one or more of the sessions listed in the detail window, you can issue an action command against a subset of the sessions.

GTW Displays the active gateway vprocs.

If you select the GTW option, the system updates the summary window with the current active gateway vprocs.

If you select a vproc in the summary window, the system updates the detail with a scrolling selection list of sessions connected to that vproc.

PE Displays the active gateway parsing engines.

Like the HGID and GTW options, the PE option shows only the Communications Processor (COP)-type parsing engines.

USER Displays the summary of the currently logged on users.

If you select the Users option, the system updates the summary window with a list of Users. The list is sorted by host group and then by userid.

If you select an entry in the summary window, the system updates the detail window with a list of sessions.

DISC Displays summary information for the currently disconnected users.

“Disconnected sessions” refers to those sessions that were logged off of the database by a reset or a system panic. The system gives these sessions a fixed period of time to reconnect.

If the reconnect time expires without the client reconnecting, the gateway simulates a logoff.

FORC Kills or Aborts using PM & PC off sessions grouped by the Host Group.


Chapter 2: Gateway Global UtilitySummary and Session

Summary and Session

The Summary section shows the sessions grouping based on the Display mode toggle button setting.

The Session section shows all sessions that are grouped under an item you select in the Summary list.

The HGID display selection in the figure below shows the following:

• The host groups• The number of sessions connected• The number of sessions forced off• Other information about the sessions

128.0.0.1123.0.0.1128.0.0.1128.0.0.1128.0.0.1128.0.0.1128.0.0.1128.0.0.1128.0.0.1128.0.0.1

1042104410451046104710481049105010511052

DBCDBCDBCDBCDBCDBCDBCDBCDBCDBC

16384163841638416384163841638416384163841638416384


Chapter 2: Gateway Global UtilityMode

Mode

The Mode options work in conjunction with the Session section of the Main window. The following table describes the Mode options.

Option Function

Session Indicates that each session will have a KILL or DISCONNECT command issued.

Session offers these options:

Option Function

Disc Sends a message to the gateway indicating the session or user is to be disconnected.

A session disconnected using the Disconnect command is allowed to reconnect. The Kill command, however, removes the session information about the user from the database entirely, and if the client wants to reconnect, the gateway denies it.

If you choose the Disconnect command, a pop-up verification window appears, giving you a chance to select the OK, Cancel, or Help option before the system proceeds.

Kill Sends a message to the gateway indicating the session or user to be acted upon.

The Kill command immediately forces the user off the system.

If you choose the Kill command, a pop-up verification window appears, giving you a chance to select the OK, Cancel, or Help option before the system proceeds.

Dsply Sess Sends a message to the gateway requesting detail information about the status of the selected sessions.

For an sample of the Display session, see “Session Window” on page 2-60.

Sel/Clr All Selects or deselects all of the sessions in the Session window.

User Has the effect of sending a single command (per host group), forcing the gateway to determine which sessions should be killed.


Chapter 2: Gateway Global UtilityMode

To use a Mode option, do the following:

Step Action

1 Highlight a session in the Mode area of the Main window.

2 Select an option.


Chapter 2: Gateway Global UtilityMessages

Messages

The Messages section is located at the bottom of the Main window. Messages generated by the system that are the result of a specified Mode option for a specific session display here.

For example, if you initiate a kill or disconnect option in the Mode window, you might see the following messages:

• User DBC killed

• Session xxx not found


Chapter 2: Gateway Global UtilitySession Window

Session Window

The Session window provides detailed information about a selected session.

To display the Session window, do the following:

Step Action

1 In the Summary section of the Main window, select a session by clicking on it.

The session is highlighted.

2 In the Mode section of the Main window, select the Session push button.

3 In the Mode section of the Main window, select the Dsply Sess button.

The Session window appears. The example session window below shows user and configuration information for session number 1042.

The session window displays a list of the users that are connected to that particular session, plus detailed configuration information.


Chapter 3:

Lock Display Utility

The Lock Display utility provides a snapshot capture of all real-time database locks.

The database software uses locks for concurrency control. The Lock Display utility displays locks used for concurrency. A lock can be applied to a database object based on the following lock granularity:

• Database• Table• Rowhash Range• Rowhash

Optionally, you can specify the lock to be applied to a database object using the SQL Locking Modifier.

Lock Display can obtain lock information from the following:

• A specific AMP• A group of AMPs• All AMPs

Note: For a system with many AMPs and a heavy load, be careful when selecting the number of AMPs from which to obtain information. The fewer the AMPs selected, the lower the volume of lock information generated, and the more manageable the output. NCR recommends obtaining information from all AMPs only when the lock information for a specific transaction is needed.

For detailed examples of returned data, see “DB” on page 3-15 and “TABLE” on page 3-25.

Audience

Users of the Lock Display utility include the following:

• Database administrators• System programmers• System engineers• Support engineers


Chapter 3: Lock Display UtilityStarting and Exiting Lock Display on NCR UNIX MP-RAS

Starting and Exiting Lock Display on NCR UNIX MP-RAS


You can start and exit Lock Display from the Database Window.

To start Lock Display, do the following:

Note: For details on the Database and Supervisor Windows, see Teradata RDBMS Database Window.

To exit Lock Display, do the following:

Step Action



2 In the Enter a command subwindow of the Supervisor window, type the following:

start lokdisp

3 Press Enter.


Started ‘lokdisp’ in window 1.

The number represents the application window in which Lock Display is running. The Lock Display window appears.

Step Action

1 In the Enter a command subwindow of the Lock Display window, type the following:

quit

2 Press Enter.

The following message displays:

LOCK DISPLAY UTILITY terminates.

3 In the Lock Display window, select File -> Close.



Chapter 3: Lock Display UtilityStarting and Exiting Lock Display on Microsoft Windows 2000

Starting and Exiting Lock Display on Microsoft Windows 2000


You can start and exit Lock Display from the following:





Step Action






start lokdisp

4 Press Enter.


Started 'lokdisp' in window 4.

The number represents the application window in which Lock Display is running. The Lock Display window appears.







Step Action

1 In the Enter a command subwindow of the Lock Display window, type the following:

quit

2 Press Enter.



3 In the Lock Display window, select File -> Close.


Step Action



2 In the Teradata Command Prompt window, type the following:

start lokdisp

3 Press Enter.

The Lock Display window appears.

Step Action

1 In the Lock Display window, type the following:

quit

2 Press Enter.






Step Action




The DBW appears.



start lokdisp

5 Press Enter.


Started ‘lokdisp’ in window 1.

The number represents the application window in which Lock Display is running. The tab that previously said Application 1 now says Lock Display and is the active window.

Step Action

1 In the DBW, select the Abort Host tab.


quit

3 Press Enter.





Chapter 3: Lock Display UtilityLock Modes

Lock Modes

You can specify the following lock modes to a database object:

• Access• Read• Write• Exclusive


Chapter 3: Lock Display UtilityLock-Mode Contention

Lock-Mode Contention

The lock-mode contention among all outstanding lock requests determines which lock requests can be applied concurrently against a database object. This is illustrated by the contention matrix shown below.

Lock ModeImplicitAccess

Implicit Read

Implicit Write

Implicit Exclusive

Access Read Write Exclusive

Implicit Access

X X X X X X X

Implicit Read

X X X X X X

Implicit Write

X X X X X

Implicit Exclusive

X X X X

Access X X X X X X

Read X X X X

Write X X

Exclusive


Chapter 3: Lock Display UtilityExplicit and Implicit Lock Modes

Explicit and Implicit Lock Modes

Explicit lock modes are the actual locks that secure access to a database object. Usually, they are acquired at the onset of the actual transaction processing.

Implicit lock modes are pre-emptive locks used by the Lock Manager in the process of acquiring an explicit lock. Use of pre-emptive locks suggests that an explicit lock is not acquired in a single step but rather in a sequence of steps.

For example, consider acquiring an explicit table-level lock. Prior to acquiring the explicit table-level lock, an implicit database-level lock and an implicit table-level lock must be acquired first. Upon acquiring an explicit lock, any implicit lock acquired in the process is released.

The lock mode is noted in the mode field of the lock display output. An implicit lock is identified by the appearance of an asterisk (*). An explicit lock is implied when an asterisk is absent.


Chapter 3: Lock Display UtilityLock Request Status

Lock Request Status

A lock request against a database object can be granted or blocked depending on the following:

• The lock mode contention of all outstanding lock requests• The success of acquiring all locks implied by the lock granularity of the

request

Lock Display output shows separate sections for Granted and Blocked lock requests. In the case of a blocked request, the level of the database object is shown by marking the associated field in the output with the # symbol. For example, if the blocked request involves a table, then the table field is marked with the # symbol.


Chapter 3: Lock Display UtilityLock Display Utility Commands

Lock Display Utility Commands

The following table lists the Lock Display commands.

The commands are discussed in detail in the following sections.

Note: Lock Display displays 30 question mark (?) characters if it does not find user, database, or table names in the cache or user, database, or table IDs in the Data Dictionary in the case of DDL statements. To view output examples, see “DB” on page 3-15 and “TABLE” on page 3-25.

Command Description

BLOCKERS Identifies the blocked transactions as well as their blocker transactions.

DB Identifies the databases that have a database-level lock request.

HELP Provides general help for the Lock Display utility.

QUIT Exits the Lock Display utility.

ROWHASH Identifies a rowhash-level lock request. Rowhash lock information is provided also.

ROWRANGE Identifies a rowrange-level lock request. Rowrange lock information is provided also.

TABLE Identifies a table-level lock request.

TRAN Identifies currently running transactions with locks being applied.


Chapter 3: Lock Display UtilityBLOCKERS

BLOCKERS

Function

The BLOCKERS command identifies the blocked transactions as well as their blocker transactions.

Syntax

where:

Note: Together, ProcId, Uniq1, and Uniq2 identify a transaction ID.

Syntax element … Specifies …

ProcId the virtual processor number of the parsing engine processor handling the transaction.

Since virtual processor numbers are designated as integer numbers, the corresponding value for this option normally is specified in decimal notation.

This number is the first component of a transaction ID.

Uniq1 a value that is normally specified as four hexadecimal digits.

This value is the second component of a transaction ID.


This value is the third component of a transaction ID.

ALL that all blocked transactions and their corresponding blocker transactions will be considered.

ALL is the default if you do not specify a transaction ID.

LIMIT the number of blocker transactions to consider for a blocked transaction.

NUMBER the desired limiting value.

NONE that all blocker transactions for a blocked transaction are considered.

Specifying NONE corresponds to specifying zero for Number.

KY01A098

BLOCKERS

LIMIT

NUMBER

NONE

B ProcId

ALL

Uniq1 Uniq2

TRAN



Usage Notes

A transaction is an internal database concept. A transaction can have more than one blocking transaction. For example, a transaction can have five lock requests, and five transactions can block those same lock requests. In other words, if you have five tables, then conceivably, five other transactions can have the locks on those same five tables.

The following table shows the components of BLOCKERS command output in the example that follows.

Component … Includes the …

Number of Blocked Trans displayed

total number of both blocked and blocker transactions.

Blocked Trans number of the blocked transaction and the following information:

Component … Specifies …

Number of blockers displays

blocker entry count.

Number of blockers exists actual blocker count.



Note: If the lock objectType is Rowhash, only RowHashS is displayed; if the Lock objectType is RowRange, both RowHashS and RowHashE is displayed. RowHashS and RowHashE are the lower- and upper-bound levels of the RowHash range, respectively.

Blocker Trans number of blocking transactions and the following information:


lock mode a type of lock mode:


lock status a type of status of the lock request:

• Granted

lock objectType a type of object that is locked:

• Database• Table• Rowrange• Rowhash

lock objectID an ID of the locked object and might include the following:

• Database ID• Database Name• Table ID• Table Name• RowHashS• RowHashE

Component … Includes the …



Example

The following example shows one lock entry on AMP 0:


Chapter 3: Lock Display UtilityDB

DB

Function

The DB command identifies the databases that have a database-level lock request.

Syntax

where:

Usage Notes

The following table shows the components of DB command output in the example that follows.


DBname the name of a database.

ALL that all databases that have a database-level lock request will be considered.

ALL is the default if you do not specify a database name.


Tran currently running transactions with locks being applied.

Host the logical host ID (the origin of the transaction).

Session the session number for the transaction.

Mode the lock mode:


User the logon-ID for whom the lock is being requested.

Database the name of the database being locked.

KY01A096

DB

DBname

ALL

D



Example 1

The following example shows locks on a sampling of AMPs for the STAFF database:



Example 2

The following example tries to display database-level locks while trying to create database USER1. The first lock is an Intentional Write Lock on database DBC (user DBC), and the second lock is an Intentional Exclusive Lock on database USER1 (user DBC).

LOKDISP >>

DB ALL

- The following amps are available:

0

-> Which amp(s) do you want to request on (S=Sampling/A=all/C=cancel/Q=quit):A

---------------- AMP 0 REPORTS 2 LOCK ENTRIES -------------

GRANTED LOCK REQUEST(S):

Tran: 16383 000008B8Host: 7169 Session: 0, 1010 Mode: WR* User: ??????????????????????????????

Database: ??????????????????????????????

Host: 7169 Session: 0, 1010 Mode: EX* User: ??????????????????????????????

Database: ??????????????????????????????


Chapter 3: Lock Display UtilityHELP

HELP

Function

The HELP command provides general help for Lock Display.

Syntax

where:

Example

The following example shows basic Lock Display Help:

Enter a command:HELP

LOCK DISPLAY UTILITY

An optional command string may be used to limit the display to specific requests; otherwise, all requests are displayed except for BLOCKERS.

Commands are case-insensitive and may be abbreviated. The default radix for numeric entries is hex, but may be forced to decimal by terminating with a period. For example, ten decimal must be entered as "10.", since an unmodified "10" is interpreted in hex as 0x10 or sixteen decimal.

For the TRAN command, a set of lines displayed represents one lock request.Only object names relevant to a given lock request are displayed: for example, only database name is displayed for a database lock, whereas both database name and table name are displayed for a table lock. A "#" after an object name means the lock has not yet been granted for that level. For example, "Databasename Tablename# Rowhash1#" means the lock has been granted at database level, but not yet at table or rowhash level.


Help or ? general help for the Lock Display utility.

KY01A097

HELP

H

?


Chapter 3: Lock Display UtilityQUIT

QUIT

Function

The QUIT command exits Lock Display.

Syntax

where:


QUIT that Lock Display should exit.

KY01A099

QUIT

Q


Chapter 3: Lock Display UtilityROWHASH

ROWHASH

Function

The ROWHASH command identifies a rowhash-level lock request.

Syntax

where:


DBname.Tablename the name of a database and the name of a table separated by a required period (.).

TypeAndIndex a subtable identifier.

A table is comprised logically of one or more subtables. For example:

• 0 is a table header. • 1024 is a primary subtable. • 1028, 1032, 1036, and other +4 incremental values are

secondary index subtables. • 2048, 3072, 4096, and other multiples of 1024 are the

fallback subtables.

RowHash1 a system-assigned rowhash value used to acquire a rowhash lock.

Normally, this value is specified in decimal notation.

RowHash2 a system-assigned rowhash value used to acquire a rowhash lock.

Normally, this value is specified in decimal notation.

ALL that all tables that have a rowhash-level lock applied are considered.

ALL is the default if you do not specify an object name.

KY01A094

ROWHASH

ROWH DBname.Tablename

ALL

TypeAndIndex RowHash1 RowHash2



Usage Notes

The following table shows the components of ROWHASH command output in the example that follows.

Note: The rowhash lock information is provided also.


Tran currently running transactions with locks being applied.

Host the logical host ID (origin of the transaction).


Mode the type of lock mode:




Table the name of the locked table.

Row Hash the locked row hash.



Example

The following example shows locks on AMP 0 on Database STAFF and Table MANAGEMENT:

> rowhash staff.management 0 0 1rowhash staff.management 0 0 1- The following amps are available:

0 1 2

-> Which amp(s) do you want to request on (S=Sampling/A=all/C=cancel/Q=quit): > aa


BLOCKED LOCK REQUEST(S):

Tran: 16383 00001354Host: 0 Session: 0, 2053 Mode: Ac User: NCR Database: STAFF Table: MANAGEMENT Row Hash1: 0, 1 #


Chapter 3: Lock Display UtilityROWRANGE

ROWRANGE

Function

The ROWRANGE command identifies a rowrange-level lock request.

Syntax

where:

Usage Notes

The following table shows the components of ROWRANGE command output in the example that follows.



TypeAndIndex a subtable identifier.

A table is comprised logically of one or more subtables. For example:

• 0 is a table header. • 1024 is a primary subtable. • 1028, 1032, 1036, and other +4 incremental values are

secondary index subtables. • 2048, 3072, 4096, and other multiples of 1024 are the

fallback subtables.

ALL that all tables that have a rowrange-level lock request are considered.

ALL is the default if you do not specify the command parameters.


Tran the currently running transactions with locks being applied.



KY01A095

ROWRANGE

ROWR DBname.Tablename

ALL

TypeAndIndex


Chapter 3: Lock Display UtilityROWRANGE

Example

The following example shows locks on AMP 0 on Database STAFF and Table MANAGEMENT:

> rowhash staff.management 0rowhash staff.management 0- The following amps are available:

0 1 2

-> Which amp(s) do you want to request on (S=Sampling/A=all/C=cancel/Q=quit): > aa


BLOCKED LOCK REQUEST(S):

Tran: 16383 00001354Host: 0 Session: 0, 2053 Mode: Ac User: NCR Database: STAFF Table: MANAGEMENT Row Hash1: 0, 1 Row Hash2: 0, 2 #





Table the name of the table being locked.

Row Range the range of rows being locked.



Chapter 3: Lock Display UtilityTABLE

TABLE

Function

The TABLE command identifies a table-level lock request.

Syntax

where:

Usage Notes

The following table shows the components of TABLE command output in the example that follows.



ALL that all tables (from all databases) that have a table-level lock request are considered.

ALL is the default if you do not specify an object name.










KY01A093

TABLE

TA DBname.Tablename

ALL


Chapter 3: Lock Display UtilityTABLE

Example 1

The following example shows the locks on AMP 0 on the database STAFF and table MANAGEMENT:


GRANTED LOCK REQUEST(S):

Tran: 16383 00001372Host: 2100 Session: 0, 1267 Mode: EX User: NCR Database: STAFF Table: MANAGEMENT

Example 2

The following is an example of trying to display table-level locks on a table while trying to create the table.

lokdisp>>

table all

- The following amps are available:

0

-> Which amp(s) do you want to request on (S=Sampling/A=all/C=cancel/Q=quit):

A

Host: 7169 Session: 0, 1441 Mode: EX User: DBC

Database: STAFF Table: ??????????????????????????????

Table name is not printed.


Chapter 3: Lock Display UtilityTRAN

TRAN

Function

The TRAN command identifies currently running transactions with locks being applied.

Syntax

where:

Note: Together, ProcId, Uniq1, and Uniq2 identify a transaction ID.

Usage Notes

A transaction is an internal database concept. A transaction can have more than one blocking transaction. For example, a transaction can have five lock requests, and five transactions can block those same lock requests. In other words, if you have five tables, then conceivably, five other transactions can have the locks on those same five tables.

Each logically grouped display represents one lock request. Only object names relevant to a given lock request are displayed.


ProcId the virtual processor number of the parsing engine processor handling the transaction.

Since virtual processor numbers are designated as integer numbers, the corresponding value for this option normally is specified in decimal notation.

This number is the first component of a transaction ID.


This value is the second component of a transaction ID.


This value is the third component of a transaction ID.

ALL that all blocked transactions and their corresponding blocker transactions that will be considered.

ALL is the default if you do not specify an ProcId.

KY01A092

TRAN

TR ProcId

ALL

Uniq1 Uniq2



For example, only the database name is displayed for a database lock, whereas both a database name and a table name are displayed for a table lock.

The following table shows the components of TRAN command output in the example that follows.










DUMMY LOCK

the specific row has lock applied on a distinct pseudo dictionary table when applicable to facilitate concurrency control. The pseudo dictionary table does not exist. The table ID is used as the value of the row hash.



Example

The following example shows the transactions on AMP 2 with locked entries:


Chapter 4:

Locking Logger Utility

Also called the Dumplocklog, Locking Logger is an optional utility. When you enable the locklogger option in DBS Control, the Teradata RDBMS maintains ongoing logs of the following:

• Transaction identifiers• Session identifiers• Lock object identifiers• Lock levels associated with executing SQL statements that have been

delayed because of database lock contention

Locking Logger creates a table of information extracted from the transaction logs. You can use this table to determine whether system performance has been degraded by an inappropriate mix of SQL statements.

You must enable the locklogger field in DBS Control before you can use Locking Logger.

For more information, see “DBS Control Utility” in Teradata RDBMS Utilities.

Audience

Users of Locking Logger include the following:

• Database administrators• System programmers• System engineers


Chapter 4: Locking Logger UtilityStarting and Exiting Locking Logger on NCR UNIX MP-RAS

Starting and Exiting Locking Logger on NCR UNIX MP-RAS


You can start and exit Locking Logger from the Database Window.

To start Locking Logger, do the following:


To exit Locking Logger, do the following:

Step Action




start dumplocklog

3 Press Enter.


Started ‘dumplocklog’ in window 1.

The number represents the application window in which Locking Logger is running. The Locking Logger window appears.

Step Action

1 In the Enter a command subwindow of the Locking Logger window, type the following:

quit

2 Press Enter.


DumpLockLog is terminated.

3 In the Locking Logger window, select File -> Close.



Chapter 4: Locking Logger UtilityStarting and Exiting Locking Logger on Microsoft Windows 2000

Starting and Exiting Locking Logger on Microsoft Windows 2000


You can start and exit Locking Logger from the following:





Step Action






start dumplocklog

4 Press Enter.



The number represents the application window in which Locking Logger is running. The Locking Logger window appears.







Step Action

1 In the Enter a Command subwindow of the Locking Logger window, type the following:

q

2 Press Enter.



3 In the Locking Logger window, select File -> Close.


Step Action



2 In the Teradata Command Prompt window, type the following:

start dumplocklog

3 Press Enter.

The Locking Logger window appears.

Step Action

1 In the Locking Logger window, type the following:

q

2 Press Enter.






Step Action




The DBW appears.



start dumplocklog


5 Press Enter.



The number represents the application window in which Locking Logger is running. The tab that previously said Application 1 now says Locking Logger and is the active window.

Step Action

1 In the DBW, select the Locking Logger tab.


q

3 Press Enter.





Chapter 4: Locking Logger UtilityTransaction Lock Log Information

Transaction Lock Log Information

When Locking Logger is enabled, each system AMP creates a 32 KB circular memory buffer for saving transaction lock log information.

The lock log buffers hold approximately 810 entries. When the buffer is full, the next entry overwrites the first. This provides a continuously updated log of the last 810 transaction locks encountered by each AMP.

When a transaction encounters a lock contention delay, the AMP writes an entry in the lock log buffer that includes object identifiers containing the following information concerning the delayed transaction:

• The date and time the transaction lock was requested• The length of time the blocked transaction was blocked• The database and table identifiers of the table upon which the lock was

requested• The host ID and session number of the transaction request that was locked• The host ID and session number of the transaction that imposed the lock • The processor ID of the AMP where the lock was requested• The lock level (database, table, row, or range of rows), and mode (read,

write, exclusive), of the lock request• The type of executing statement associated with the transaction (INSERT,

UPDATE, SELECT, and so forth)• Whether the lock request caused a deadlock


Chapter 4: Locking Logger UtilityEnabling the LockLogger Field in DBS Control Utility

Enabling the LockLogger Field in DBS Control Utility

The DBS Control utility LockLogger field defines the system default for Locking Logger. This field allows you to log the delays caused by database locks to help identify lock conflicts.

The new setting becomes effective after the next RDBMS restart.

For more information, see “DBS Control Utility” in Teradata RDBMS Utilities.

To … Set the field to …

enable this feature TRUE.

disable this feature FALSE (Default).


Chapter 4: Locking Logger UtilityLock Logger Table Requirements

Lock Logger Table Requirements

Lock log tables allow you to define the information that you want to retrieve from the lock log buffers. When using Locking Logger to create a lock log table, you must provide the following information.

Required Information Description

User name and password

Since Locking Logger uses standard Teradata SQL statements to create the lock log table and insert the information from the lock log buffers, you must have appropriate database access privileges.

IF the table is … THEN you must have …

new CREATE TABLE privileges.

existing table or database INSERT privileges.

Number of SQL sessions Locking Logger will use to perform the INSERT operation

The minimum is one session; the maximum is one session for each online AMP.

The following restrictions affect the performance and ability of Locking Logger to run.

IF Locking Logger runs in … THEN there …

continuous mode should be at least one or more free console sessions per PE. If the ratio of AMPs to PEs is at least three to one, Locking Logger should have no problem running. But if the ratio is six to one or higher, Locking Logger cannot run in continuous mode.

snapshot mode must be one or more free console session per PE (no matter what the ratio of AMPs to PEs) for Locking Logger to run.

Note: The maximum number of sessions is limited by the number of PEs.


Chapter 4: Locking Logger UtilityLock Logger Table Requirements

Type of mode of Locking Logger

Locking Logger has the following types of modes.

IF the type of mode is … THEN Locking Logger creates …

single-snapshot lock log table entries from a single copy of the current contents of the lock log buffer for each AMP.

continuous table entries from the first copy of the contents of the lock log buffer for each AMP, then gets additional buffer entries, as they are created, translating them into additional lock log table rows.

Character set of the table name

This parameter dictates how the input is to be interpreted internally by the Locking Logger and the RDBMS.

Name of the lock log table to be created

You can specify either an existing table or a new table.

For detailed information on naming a table, see “SQL Lexicon” in Teradata RDBMS SQL Reference, Volume 1.

Time constraints that you want to use for selecting entries from the lock log buffers

You can select lock log entries that were created for the following:

• Within a specified time range• At or after a specified time• At or before a specified time

The default is no time constraint.

Names of any specific database objects whose lock log entries you want to select.

You can select the following objects:

• A specific database and a specific table• A specific database and all of the tables • A specific table under the default database for your user

name

You can select up to 10 objects. If you do not specify any objects, the default specification selects all tables from all databases.

Required Information Description


Chapter 4: Locking Logger UtilityLock Log Tables

Lock Log Tables

To create Lock Log tables after starting Locking Logger, do the following:

Step Action

1 Enter your logon string: <username,password> (Q/q to quit)

• To create a lock log table, you must have CREATE TABLE privileges.• To update an existing table, you must have INSERT privileges for the table or database.

2 Do you want this utility to run continuously? (Y/N):

IF you answer … THEN you specify the …

Y continuous run mode whereby rows are added to your table as additional lock log buffer entries are created. This continues until you terminate the utility, or until the size of the table consumes all available system storage.

• If your username and password are validated, you go directly to Step 4. • If the username and password cannot be validated, the utility terminates at

this point.

N single-snapshot mode whereby the utility creates or updates your lock log table from a single copy of the lock log buffer for each system AMP.

• If you answer N, and specify the single-snapshot mode, the number of sessions prompt displays.

3 Enter number of sessions (? For Help, Q/q to Quit):

Number of sessions Description

Minimum The minimum number of sessions is one.

Maximum Based on the following:

• Because of a limit of four console sessions per PE, the maximum number of sessions is whichever is lower:

– The number of online AMPs– The number of PEs

The default is the maximum: one session per online AMP:

• To select the default, type an asterisk (*). • If you type an invalid number, the utility displays an error message and

repeats the number of sessions prompt.



4 Enter the Character Set (? for Help, Q/q to Quit):

• STRING - Interpreted as a CHARACTERSET NAME.• NUMBER - Interpreted as a CHARACTERSET CODE.

Note: The first character of the input dictates this rule. Example: “123ascii” is read as “123.” • * (asterisk) - The default character set, which is usually ASCII for a network-attached machine and

EBCDIC for a channel-connected system.• ? (question mark)- Lists the character sets installed on your system.

Note: Depending on the particular host connection of your machine, such as IBM channel, you might not be able to use all of the following available character sets:

Code Character Set Name

127 ASCII

64 EBCDIC

65 - 126 User-defined

5 Enter the table name where the lock log entries will be written (? for Help, Q/q to Quit):

• Specify a new table or an existing table. You must have the appropriate database access privileges.

Note: Table name entries on a Kanji machine must be in hex format, such as '82eb82ae'xn, an even number of hex characters contained in single quotes immediately followed by the letters xn.

To specify a table … Enter …

for a database other than the default database of your logon username

both the database name and the table name as follows:

<name1>.<name2>

where:

<name1> specifies the database name.

<name2> specifies the table name.

that is under the default database of your logon username

only the table name as follows:

<name1>

where:


6 Do you want this utility to create table <tablename> (Y/N):

• Y - If you specified an existing table name• N - If you specified a new table name

Step Action



7 Enter the time constraint to control selection of lock log entries that were generated AT or LATER than this time YYYYMMDD HHMMSS (? For Help, Q/q to Quit):

Note: This is the first of two time constraint prompts that ask you to specify a time period for selecting lock log entries.

• To specify all entries that were created within a range of times, specify both an AT or LATER and an AT or PRIOR time constraint.

• To select all entries from the lock log buffers, regardless of time, type an asterisk (*).

Time constraints are specified using the following format:

YYYYMMDD HHMMSS

where:

YYYY=Year Range = 1901 to 9999

MM = Month Range = 01 to 12

DD = Day Range = 01 to 31

HH = Hour Range = 00 to 23

MM = Minute Range = 00 to 59

SS = Second Range = 00 to 59

Note: If you answered Y at Step 2 to specify the continuous run mode, skip to Step 8 and specify the database object constraints for selecting lock log entries. If you entered N at Step 2 to specify the single-snapshot mode, you are prompted to type the latest time of the range of lock log entries that you want to select.

8 Enter the time constraint to control selection of lock log entries that were generated AT or PRIOR TO this time YYYYMMDD HHMMSS (? For Help, Q/q to quit):

• If entries were created for a specified range of times, type the AT or PRIOR time of the range using the same format as in Step 7.

Step Action



9 Enter the object constraint to select lock log entries <database.table> (? For Help, Q/q to quit):

You can specify up to 10 database objects for selecting lock log entries.

• If you do not want to specify any database objects, type an asterisk (*) and skip to Step 11.

After you type the first object constraint, the utility prompts you to type another object.

To specify a … Enter …

table for a database other than the default database of your logon username

both the database name and the table name as follows:

<name1>.<name2>

where:

<name1> specifies the database name.


table that is under the default database of your logon username

only the table name as follows:

<name1>

where:


database and all of the tables under it

the database name and an asterisk (*) as follows:

<name>.*

where:

<name> specifies the database name.

* specifies all of the tables under the database.

10 more? <database.table> (? For Help, <Ret> for Done):

The utility will redisplay the more? prompt until you have specified ten object constraints, or until you press the carriage return key without specifying another object.

Step Action



For a description of the structure of the lock log table that Locking Logger creates and example SQL procedures for joining your table with the system DBase, TVM, and EventLog tables to produce a meaningful output report, see “Producing a Lock Log Report” on page 4-16.

11 After you specify the database object constraints, the utility initiates the table CREATE and INSERT tasks and displays the following statement and prompt:

Writing lock log entries to table <tablename>

Press <F2> anytime to stop the utility

• If you specified the single-snapshot mode in Step 2, or if you entered a prior-to time constraint in Step 7, the utility stops when it completes the single-snapshot operation.

• If you specified the continuous run mode in Step 1 with no prior-to time constraint in Step 7, the utility runs continuously until you stop it by pressing the F2 function key, or until the size of your table grows to consume all available system storage.

12 The final display indicates the total number of rows that were inserted in the table that you specified in Step 5:

<positive integer> rows have been inserted to table <tablename>

*** DumpLockLog is terminated ***

Step Action


Chapter 4: Locking Logger UtilityMessages

Messages

The following table contains Locking Logger messages and their descriptions.

Message Description

"x rows have been inserted..." In CONTINUOUS mode, 1,000 additional rows have been generated and inserted into the target table.

"*** Warning - some lock log entries have been lost from processor due to buffer overflow."

In CONTINUOUS mode, some vprocs failed to insert all rows into the table because the holding buffer overflowed.

"No rows inserted." In SNAPSHOT mode, the user has decided to terminate before entering all the data that Locking Logger requires to run, or Locking Logger terminated abnormally.

"No rows have been inserted to table " In SNAPSHOT mode, this means a normal termination of the Locking Logger in which no rows were observed, that is, no locking contention within given parameters of the user.

"1 row has been inserted to table " In SNAPSHOT mode, one single row was found and inserted successfully into the table.

"%s rows have been inserted to table " In SNAPSHOT mode, more than one row was found and inserted successfully to the table.

"*** DumpLockLog is terminated *** " In SNAPSHOT mode, this appears preceding a normal termination.

"Utility is about to be terminated ..." In CONTINUOUS mode, this appears after the user presses <F2> to terminate Locking Logger.

"Utility resumes ..." In CONTINUOUS mode, this appears after the user presses any key (usually the CTRL key) other than F2.


Chapter 4: Locking Logger UtilityProducing a Lock Log Report

Producing a Lock Log Report

The lock log table that is created by Locking Logger uses the following structure:

CREATE SET TABLE DHV.LL ,FALLBACK , NO BEFORE JOURNAL, NO AFTER JOURNAL ( BEGDATE DATE FORMAT 'YY/MM/DD' NOT NULL, BEGTIME FLOAT FORMAT '99:99:99.999' NOT NULL, DELAY FLOAT FORMAT '99:99:99.999' NOT NULL, DBID BYTE(4) NOT NULL, TID BYTE(6) NOT NULL, BLKDLOGHOST SMALLINT NOT NULL, BLKDSESSNO INTEGER NOT NULL, BLKDLEVEL CHAR(8) CHARACTER SET UNICODE NOT CASESPECIFIC NOT NULL, BLKDMODE CHAR(2) CHARACTER SET UNICODE NOT CASESPECIFIC NOT NULL, BLKINGLOGHOST SMALLINT NOT NULL, BLKINGSESSNO INTEGER NOT NULL, BLKINGLEVEL CHAR(8) CHARACTER SET UNICODE NOT CASESPECIFIC NOT NULL, BLKINGMODE CHAR(2) CHARACTER SET UNICODE NOT CASESPECIFIC NOT NULL, PROCESSOR SMALLINT FORMAT 'ZZZZ9' NOT NULL, DEADLOCK CHAR(1) CHARACTER SET UNICODE NOT CASESPECIFIC NOT NULL, MULTIPLEBLOCKER CHAR(1) CHARACTER SET UNICODE NOT CASESPECIFIC NOT NULL, STMTTYPE VARCHAR(20) CHARACTER SET UNICODE NOT CASESPECIFIC NOT NULL)PRIMARY INDEX ( BEGDATE ,BEGTIME );

The following table describes the structure.

Column Description Format and Data Type

BEGDATE The date the transaction was blocked.

DATE NOT NULL

BEGTIME The time that the transaction became blocked.

FLOAT '99:99:99.999' NOT NULL

BLKDLEVEL The lock level of the transaction that was waiting for the lock—LokDB, LokTable, LokRowRg, or LokRow.

CHAR(8) NOT NULL

BLKDLOGHOST The logical host ID of the transaction that was waiting for the lock.

SMALLINT NOT NULL



BLKDMODE The lock mode of the transaction that was waiting for the lock—Access, Read, Write, or Excl.

CHAR(2) NOT NULL

BLKDSESSNO The session number of the transaction that was waiting for the lock.

The following session numbers are used to indicate DBS internal sessions:

0 - System User

1 - System Accounting

2 - System Recovery

INTEGER NOT NULL

BLKINGLOGHOST The logical host ID of the transaction that imposed the lock.

SMALLINT NOT NULL

BLKINGLEVEL The lock level of the transaction that imposed the lock—LokDB, LokTable, LokRowRg, or LokRow.

CHAR(8) NOT NULL

BLKINGMODE The lock mode of the transaction that imposed the lock.

CHAR(2) NOT NULL

BLKINGSESSNO The session number of the transaction that imposed the lock.

The following session numbers are used to indicate DBS internal sessions:

0 - System User

1 - System Accounting

2 - System Recovery

3 - Archive/Restore

INTEGER NOT NULL

DBID The database ID of the table on which the lock was requested.

BYTE(4) NOT NULL




The rows in the table also contain the following information:

• Internal identifiers for the object on which the lock was requested• Holder of the lock• Requestor of the lock

DEADLOCK Indicates whether the lock contentions resulted in a deadlock.

Note: Records local deadlocks only, or those deadlocks for a single AMP, not deadlocks across the entire system.

CHAR(1) NOT NULL

DELAY The total time the transaction waited for the block, to the hundredth of a second.

FLOAT '99:99:99.999' NOT NULL

MULTIPLEBLOCKER Indicates whether more than one transaction encountered the same lock contention.

CHAR(1) NOT NULL

PROCESSOR The identifier of the AMP where the lock was requested.

SMALLINT 'ZZZZ9' NOT NULL)

STMTTYPE The type of executing statement for the transaction that produced the lock.

VARCHAR (20) NOT NULL

TID The table ID of the table on which the lock was requested—Access, Read, Write, or Excl.

BYTE(6) NOT NULL



Chapter 4: Locking Logger UtilityExample Log Files

Example Log Files

The example lock log files are similar in the following respects:

• Since the EventLog table usually is very large, the examples first try to reduce the size of this table to minimize the execution time of the join operation.

• Temporary tables are assigned names using nonalphabetic characters to avoid possible conflicts with existing permanent tables.

• MyLog represents the lock log table that was created by Locking Logger.


Chapter 4: Locking Logger UtilityReducing the Size of the Tables

Reducing the Size of the Tables

When a lock log table is joined with DBC.EventLog, determining the blocked user from the blocking user can be difficult. Usually, this is because of a large number of rows in DBC.EventLog with the same session number, since the session number is reused whenever TDP restarts.

To determine the blocked user from the blocking user, use the following:

• The begdate and begtime values from the lock log table• The logondate and logontime values from DBC.EventLog

For example, suppose that your lock log table (MyLog) and the DBC.EventLog table contain the following rows.

To identify the user from DBC.EventLog for each row in MyLog, note the following:

• The first row of MyLog is <T2,S1> and that there are four rows from DBC.EventLog with session number S1:– <T1,S1,A>– <T3,S1,C>– <T5,S1,D>– <T11,S1,F>

MyLog Table DBC.EventLog Table

begdatetime blkdsessno logondatetime sessionno user

T2 S1 T1 S1 A

T4 S2 T2 S2 B

T10 S1 T3 S1 C

T30 S2 T5 S1 D

T9 S2 E

T11 S1 F

T20 S2 G


Chapter 4: Locking Logger UtilityReducing the Size of the Tables

Since S1 was blocked at time T2, S1 must have been logged on before T2. Therefore, user A was blocked at T2.

• Similarly, the second row of MyLog, <T4,S2>, identifies user B.• The third row of MyLog, <T10,S1>, has four rows from EventLog with

session number S1, and three of them have a logondatetime before T10– <T1,S1,A>– <T3,S1,C>– <T5,S1,D>

In this case, user D was blocked at T10, since the last logon time for S1 before T10 was at T5. Using the same process as before, the fourth row of MyLog identifies user G.

The following example SQL queries use two temporary tables:

• Table “MYTEMPLOG_ONE” to reduce the size of DBC.EventLog• Table “MYTEMPLOG_TWO“ to reduce the size of MyLog

Using unusual table names avoids conflicts with permanent tables.


Chapter 4: Locking Logger UtilityReducing the Size of the Lock Log Table

Reducing the Size of the Lock Log Table

The following SQL statements create a temporary table that contains a portion of MyLog.

The temporary table has databasename and tablename instead of internal IDs.

In the following example, begtime is the combination of begdate and begtime from MyLog. This simplifies the comparison on date/time columns.

drop table "MYTEMPLOG_TWO";ct "MYTEMPLOG_TWO", fallback(begdatetime float format 'zzz,zzz,zzz,zzz.zzz' not null,begdate date not null,begtime float format '99:99:99.999' not null,delay float format '99:99:99.999' not null,databasename char(30) not null,tablename char(30) not null,blkdloghost smallint not null,blkdsessno integer not null,blkdlevel char(8) not null,blkdmode char(2) not null,blkingloghost smallint not null,blkingsessno integer not null,blkinglevel char(8) not null,blkingmode char(2) not null,processor smallint format 'zzzz9' not null,deadlock char(1) not null,multipleblocker char(1) not null,stmttype varchar(20) not null)

primary index (begdate,begtime);


Chapter 4: Locking Logger UtilityReducing the Size of the DBC.EventLog Table

Reducing the Size of the DBC.EventLog Table

Similarly, the following SQL statements create a temporary table that contains a portion of DBC.EventLog:

drop table "MYTEMPLOG_ONE";ct "MYTEMPLOG_ONE", fallback(datefld date not null,timefld float format '99:99:99.99' not null,logondatetime float format 'z,zzz,zzz,zzz,zzz.zzz' not null,sessionno integer not null,logicalhostid smallint format 'zzz9' not null,username char(30) not null,accountname char(30) not null,logonsource varchar(128))

primary index (datefld,timefld);


Chapter 4: Locking Logger UtilityInserting Rows

Inserting Rows

The following SQL statements define a macro that inserts rows into the temporary tables. The macro uses four parameters:

• t1date, t1time specifies that only the users logged on AFTER this time should be selected from DBC.EventLog.

• t2date, t2time specifies that only the blockages occurring BEFORE this time should be selected from MyLog.

Limiting the number of rows from DBC.EventLog before performing a join operation is very important because DBC.EventLog could contain millions of rows if it is not purged frequently.

Also, you could add other parameters to this macro to further limit the analysis. If, for example, you are only interested in lock log table rows involving user Joe with account Joe1 in some time range, you could add the following:

• Parameters UserA Char(30) and AccountA Char(30) to the macro• Conditions (UserName = :UserA) and (AccountName = :AccountA) to the

Insert-Select statement for table “MYTEMPLOG_ONE”.drop macro LockBldTmp;cm LockBldTmp (t1date date,

t1time float,t2date date,t2time float) as

(/*******************************************************//* To get all of the rows from MyLog whose blocked *//* begin time is less than t2date/time, join with *//* DBC.TVM to get the table name from the table ID *//* and with DBC.Dbase to get the database name from *//* the database ID. A database level lock row has *//* table name of “ALL”. *//*******************************************************/del from "MYTEMPLOG_TWO";locking MyLog for accessins into "MYTEMPLOG_TWO"sel (begdate*1000000+begtime),

begdate, begtime, delay, dbase.databasename, tvm.tvmname, blkdloghost, blkdsessno, blkdlevel,



blkdmode, blkingloghost, blkingsessno, blkinglevel, blkingmode, processor, deadlock, multipleblocker, stmttype

from dbc.tvm, dbc.dbase, MyLog

where (tid = tvm.tvmid) and (dbid = dbase.databaseid) and (begdate*1000000+begtime) <= (:t2date*1000000 +

:t2time);/********************************************************/

/* Because DBC.EventLog may contain millions of rows, *//* reduce it by getting only the rows that satisfy *//* these conditions: *//* *//* 1. Event is logon. *//* 2. Logon date/time is greater than t1date/time. *//********************************************************/del from "MYTEMPLOG_ONE";

ins into "MYTEMPLOG_ONE"sel datefld,

timefld, (logondate*1000000+logontime), sessionno, logicalhostid, username, accountname, logonsource

from dbc.eventlogwhere (event = 'logon') and

(logondate*1000000+logontime) >=(:t1date*1000000 +:t1time);

/********************************************************//* Insert dummy rows for those sessions that are used *//* by internal DBC system activities, such as cache *//* management, space accounting, recovery, and so on. *//********************************************************/

ins into "MYTEMPLOG_ONE" ('90/01/01',0,0,0,0,'SystemUser','SystemUser', 'SystemUser');

ins into "MYTEMPLOG_ONE"



('90/01/01',0,0,1,0,'SystemAccounting', 'SystemAccounting','SystemAccounting');

ins into "MYTEMPLOG_ONE" ('90/01/01',0,0,2,0,'SystemRecovery', 'SystemRecovery','SystemRecovery');

/************************************************************//* Eliminate rows from "MYTEMPLOG_ONE" by joining it with *//* "MYTEMPLOG_TWO". Note that you could combine this *//* statement with the previous Select-Insert statement, *//* but that would require joining DBC.EventLog, which *//* is a very large table, with MyLog. Doing so would *//* require a large spool space, and would take a long *//* time to complete. *//************************************************************/

del from "MYTEMPLOG_ONE"where logondatetime > (sel max(begdatetime)

from "MYTEMPLOG_TWO") or (NOT ((sessionno,logicalhostid)

= any (sel blkdsessno,blkdloghost from "MYTEMPLOG_TWO")) and

NOT ((sessionno,logicalhostid) = any (sel blkingsessno,blkingloghost

from "MYTEMPLOG_TWO")) );

);


Chapter 4: Locking Logger UtilityDetermining the Blocked User

Determining the Blocked User

At this point, the number of rows in temporary tables "MYTEMPLOG_ONE" and "MYTEMPLOG_TWO" should be small enough for the final statements to complete in a reasonable time.

The remaining SQL query example uses "MYTEMPLOG_ONE" to determine the blocked user and its alias temp to determine the blocking user.

The following condition selects the maximum logondatetime from "MYTEMPLOG_ONE" and begdatetime from "MYTEMPLOG_TWO" for each logical host ID/session number from "MYTEMPLOG_TWO":

(("MYTEMPLOG_ONE".logondatetime,"MYTEMPLOG_TWO".begdatetime)in (sel max(logondatetime),begdatetime...

Using the sample rows described earlier:

("MYTEMPLOG_ONE".logicalhostid = "MYTEMPLOG_TWO".blkdloghost) and ("MYTEMPLOG_ONE".sessionno = "MYTEMPLOG_TWO".blkdsessno )

returns:

"MYTEMPLOG_TWO" "MYTEMPLOG_ONE" <T2,S1> X <T1,S1,A>, <T3,S1,C>, <T5,S1,D>, <T11,S1,F>

^^ ^^ ^^ ^^ ^^ <T4,S2> X <T2,S2,B>, <T9,S2,E>, <T20,S2,G>

^^ ^^ ^^ ^^ <T10,S1> X <T1,S1,A>, <T3,S1,C>, <T5,S1,D>, <T11,S1,F>

^^ ^^ ^^ ^^ ^^ <T30,S2> X <T2,S2,B>, <T9,S2,E>, <T20,S2,G>

^^ ^^ ^^ ^^

and:

(sel begdatetime,max(logondatetime)

from:

"MYTEMPLOG_ONE","MYTEMPLOG_TWO"



where:

(logondatetime < begdatetime) and(logicalhostid = blkdloghost) and (sessionno = blkdsessno)group by begdatetime,processor)

returns:

<T2,T1>, <T4,T2>, <T10,T5>, <T30,T20>

Hence, using the result from 1:

("MYTEMPLOG_TWO".begdatetime,"MYTEMPLOG_ONE".logondatetime) in ...

returns:

<A> : <T2,S1><T1,S1,A> in <T2,T1> ^^ ^^ ^^ ^^ <B> : <T4,S2><T2,S2,B> in <T4,T2> ^^ ^^ ^^ ^^ <D> : <T10,S1><T5,S1,D> in <T10,T5> ^^^ ^^ ^^^ ^^ <G> : <T30,S2><T20,S2,G> in <T30,T20> ^^^ ^^^ ^^^ ^^^

The remainder of the SQL example is as follows:

drop macro LockDisplay;cm LockDisplay as(sel "MYTEMPLOG_TWO".begdate (named RequestedDate),

"MYTEMPLOG_TWO".begtime (named RequestedTime), "MYTEMPLOG_TWO".delay (named Delay), "MYTEMPLOG_TWO".databasename (named DataBaseName), "MYTEMPLOG_TWO".tablename (named TableName), "MYTEMPLOG_TWO".blkdlevel (named BlockedLockLevel), "MYTEMPLOG_TWO".blkdmode (named BlockedLockMode), "MYTEMPLOG_ONE".logicalhostid (named BlockedHostId), "MYTEMPLOG_ONE".username (named BlockedUser), "MYTEMPLOG_ONE".accountname (named BlockedAccount), "MYTEMPLOG_ONE".logonsource (named BlockedLogonSource),"MYTEMPLOG_TWO".blkinglevel (named BlockingLockLevel),

"MYTEMPLOG_TWO".blkingmode (named BlockingLockMode), temp.logicalhostid (named BlockingHostId), temp.username (named BlockingUser), temp.accountname (named BlockingAccount), temp.logonsource (named BlockingLogonSource), "MYTEMPLOG_TWO".processor (named AMPvproc), "MYTEMPLOG_TWO".deadlock (named DeadLock), "MYTEMPLOG_TWO".multipleblocker (named MultipleBlockers), "MYTEMPLOG_TWO".stmttype (named Statement) "MYTEMPLOG_TWO".stmttype (named Statement)



from "MYTEMPLOG_ONE" temp, "MYTEMPLOG_TWO"

where ("MYTEMPLOG_ONE".logicalhostid = "MYTEMPLOG_TWO".blkdloghost ) and ("MYTEMPLOG_ONE".sessionno = "MYTEMPLOG_TWO".blkdsessno ) and (Temp.logicalhostid = "MYTEMPLOG_TWO".blkingloghost ) and (Temp.sessionno = "MYTEMPLOG_TWO".blkingsessno ) and (("MYTEMPLOG_TWO".begdatetime, "MYTEMPLOG_ONE".logondatetime) in

(sel begdatetime,max(logondatetime) from "MYTEMPLOG_ONE",

"MYTEMPLOG_TWO" where (logondatetime < begdatetime) and

(logicalhostid = blkdloghost) and (sessionno = blkdsessno)

group by begdatetime,processor) ) and (("MYTEMPLOG_TWO".begdatetime, Temp.logondatetime) in

(sel begdatetime,max(logondatetime) from "MYTEMPLOG_ONE",

"MYTEMPLOG_TWO" where (logondatetime < begdatetime) and

(logicalhostid = blkingloghost) and (sessionno = blkingsessno)

group by begdatetime,processor) ) order by 1,2;

);

/********************************************************//* To analyze the lock rows for users logged on after *//* 6:30 a.m. on 92/01/02 and delays that occurred *//* before 12:00 p.m. on 92/01/03: *//* *//* > EXEC LockBldTmp(920102,063000,920103,120000); *//* *//* > EXEC LockDisplay; *//* *//* To clean up the temporary tables: *//* *//* > Drop table "MYTEMPLOG_TWO"; *//* *//* > Drop table "MYTEMPLOG_ONE"; *//* *//********************************************************/


Chapter 4: Locking Logger UtilityHexadecimal and Non-Standard Names Support

Hexadecimal and Non-Standard Names Support

For hexadecimal name support, Locking Logger allows users to type log table names and lock object names in hexadecimal format and in non-standard format (names are surrounded by double quotes).

Hexadecimal Syntax

The hexadecimal format is as follows:

'...'xn.'...'xn

where:

Sample Output

The following shows a sample output:

This utility writes lock log entries in memory to an user specified table.

Enter your logon string: <username,password> (Q/q to quit)

dbc,dbc

Do you want this utility to run continuously? (Y/N)

n

Enter number of sessions (? For Help, Q/q to Quit):

22 sessions will be logged on.

Enter the table name where the lock log entries will be written (? For Help, Q/q to Quit):

dmo.locklog

Do you want this utility to create table DMO.LOCKLOG? (Y/N)

Syntax element … Is …

. . . the string of hexadecimal number.

Digit 0, . . . ,9.

Char ‘a’, . . . , ‘z’, ’A’, . . . , ’Z’.



yTable DMO.LOCKLOG has been created.

Enter the time constraint to control selection of lock log entriesthat were generated AT or LATER than this time YYMMDD HHMMSS(? For Help, Q/q to Quit):

970701 130000

Enter the time constraint to control selection of lock log entriesthat were generated AT or PRIOR to this time YYMMDD HHMMSS(? For Help, Q/q to Quit):

970701 140000

Enter the object constraint for selection oflock log entries (? For Help, Q/q to Quit):

?

Specify the database objects for which lock delayshould be selected. Up to 10 objects can be entered.Input ceases when an empty line or 10 objects havebeen entered.

- <name1>.<name2> - name1 specifies a database and name2 specifies a table.

- <name>.* - name specifies a database and all tables under it.

- <name1> - name specifies a table under the user name specified in the logon.

- * - All databases and tables.

- <Return> - Done.

- Q - Terminate the utility.

Note that if database or table name is specified, ithas to exist or an error will be returned.

Enter the object constraint for selection oflock log entries (? For Help, Q/q to Quit):

dmo.*



more? (? For Help, <Ret> for Done):

Writing lock log entries to table DMO.LOCKLOG.

Press <F1> to interrupt the utility.0 row has been inserted to table DMO.LOCKLOG.

*** DumpLockLog is terminated ***Ready;


Chapter 5:

modmpplist Utility (Microsoft Windows 2000 Only)

The interactive modmpplist utility allows you to modify the node list file (mpplist).

modmpplist can read the real mpplist from the Teradata Configuration directory (for example, D:\Program Files\NCR\TDAT\tdConfig) or can modify a copy of the of mpplist in another location.

When you must down a node for hardware maintenance, you can run the modmpplist file to make the downed node in an offline state and to distribute the revised mpplist file on the system. If you use modmpplist to take a node offline, you must use modmpplist to bring the node back online.

Audience

Users of modmpplist include the following:

• Teradata Support Center (TSC) personnel• Test personnel• Developers


Chapter 5: modmpplist Utility (Microsoft Windows 2000 Only)Starting modmpplist

Starting modmpplist

You can start modmpplist from the Teradata Command Prompt.

To start modmpplist, do the following:

where:

After you have started modmpplist, the mpp prompt appears, as shown below:

mpp>

At the mpp prompt, you type the commands. For information on entering commands, see “Using modmpplist” on page 5-5.

Step Action


2 At the Teradata Command Prompt, type the following:


-h general help for modmpplist.

-m mpplist_path an mpplist in a location other than the default Program Files\NCR\TDAT\tdConfig directory.

1102A001

-h

modmpplist

-m mpplist_path


Chapter 5: modmpplist Utility (Microsoft Windows 2000 Only)Editing the Default mpplist

Editing the Default mpplist

The following example shows how to start modmpplist to edit the default mpplist:

D:\WINNT\Profiles\Administrator>modmpplist reading default mpplist, C:\Program Files\NCR\TDAT\tdConfig\mpplist ...

0:pdetnt5_bynet 1:pdetnt6_bynet 2:pdetnt7_bynet 3:pdetnt8_bynet

all 4 nodes are online.


Chapter 5: modmpplist Utility (Microsoft Windows 2000 Only)Editing a User-Specified mpplist

Editing a User-Specified mpplist

The following example show how to start modmpplist to edit a user-specified mpplist.

>modmpplist -m c:\temp\tempmpplist reading user’s mpplist, C:\temp\tempmpplist ...




Chapter 5: modmpplist Utility (Microsoft Windows 2000 Only)Using modmpplist

Using modmpplist

The following table lists the commands available from within the modmpplist session (that is, from the mpp> prompt).

The modmpplist commands are discussed in detail in the following sections.

Command Description

DISPLAY Outputs the current mpplist buffer as it would appear in file format to the STDOUT file.

LIST Outputs the list of node names, their unique node IDs, and the status of nodes in the current mpplist buffer to the STDOUT file.

OFF id_list Changes the status of the IDs in the space-separated list to NO (offline).

ON id_list Changes the status of the IDs in the space-separated list to YES (online).

QUIT Causes modmpplist to quit the interactive session.

WRITE Forces the mpplist file to be written out to all nodes in the MPP system.

!COMMAND Runs a system command, prefixed with an exclamation point (!), within the modmpplist session.


Chapter 5: modmpplist Utility (Microsoft Windows 2000 Only)DISPLAY

DISPLAY

Function

The DISPLAY command outputs the current mpplist buffer as it would appear in file format to the STDOUT file.

Syntax

Example

The following example displays the mpplist contents:

mpp> d# This file is generated by PDEConfig. Please do not# edit it manually. Note a # or a space character in# the first column on a line causes the entire line to# be ignored. Field delimiter must be space character.# node type nodeid status#-----------------------------------------------------pdetnt5_bynet yes 33 yespdetnt6_bynet yes 34 yespdetnt7_bynet yes 35 yespdetnt8_bynet yes 36 yes

1102A026

D

DISPLAY


Chapter 5: modmpplist Utility (Microsoft Windows 2000 Only)LIST

LIST

Function

The LIST command outputs the list of node names, their unique node IDs, and the status of nodes in the current mpplist buffer to the STDOUT file.

Syntax

Usage Notes

The list shows the nodes in the following format:

IndexId:nodename

where:

If a node is offline, the node appears as follows in the mpplist:

-IndexId:nodename

Example

The following example lists the status and ID of the nodes.

mpp> l




dash (-) a prefix to IndexId and indicates that the node is offline.

If a node is online, the dash does not appear.

IndexId an arbitrary index number starting from 0 to N-1, where N is the number of nodes in the mpplist file.

nodename the name of a node.

1102A027

L

LIST


Chapter 5: modmpplist Utility (Microsoft Windows 2000 Only)OFF id_list

OFF id_list

Function

The OFF id_list command changes the status of the IDs in the space-separated list to NO (offline).

Syntax

where:

Example

The following example changes node 2 to offline:

mpp> off 2

1 node is offline.

(Buffer has been Modified since last read)


id_list list of node IDs.

1102A028

OFF id_list


Chapter 5: modmpplist Utility (Microsoft Windows 2000 Only)ON id_list

ON id_list

Function

The ON id_list command changes the status of the IDs in the space-separated list to YES (online).

Syntax

where:

Example

The following example changes node 3 to online:

mpp> on 3



id_list list of node IDs.

1102A029

ON id_list


Chapter 5: modmpplist Utility (Microsoft Windows 2000 Only)QUIT

QUIT

Function

The QUIT command causes modmpplist to quit the interactive session.

Syntax

Usage Notes

If you modify the mpplist file, but you did not issue a WRITE command, you are asked if you want to write the current mpplist buffer to all available nodes. The default is NO.

• If you just press RETURN, the session exits. • If you type Y (YES) at the prompt, the current mpplist buffer is written, and

then the session exits.

Example 1

The following example quits modmpplist if you just press RETURN:

mpp> quit

You have changed a value. Do you wish to save the mpplist file? (yes|no) [no]

Example 2

The following example quits modmpplist if you type Y (YES) to the prompt:

mpp> quitYou have changed a value. Do you wish to save the mpplist file? (yes|no) [no]yAll 1 node(s) have connectedMODE SIZE INODE USER GROUP FILE-rw-r--r-- 375 54206 <anon> <anon> C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\mpplistlocalhost:1043: send completed: 444 bytes received (1 files/0 directories)

Wrote and distributed mpplist to 1 node successfully.

QUIT

GS03C022Q


Chapter 5: modmpplist Utility (Microsoft Windows 2000 Only)WRITE

WRITE

Function

The WRITE command forces the mpplist file to be written out to all nodes in the MPP system.

Syntax

where:

Example 1

The following example bypasses the prompt and writes the mpplist file to all live nodes:


-y to skip the confirmation message.

-w file_path to write the modified mpplist file to a file on the local node only.

This option allows you to save changes to the local node when a remote copy fails.

• If you specify a directory, then the file mpplist is written to that directory.

• If you specify a path/file, then that file is written.

Note: If using -y, the correct format is as follows:

write -y -w filename

1102A030

-y

WRITE

-w file_path

-y -w filename

W


Chapter 5: modmpplist Utility (Microsoft Windows 2000 Only)!COMMAND

!COMMAND

Function

The !COMMAND runs a system command, prefixed with an exclamation point (!), within the modmpplist session.

Syntax

where:


COMMAND system command you want to run.

1102A031

!COMMAND



Example

The following example runs a system command to verify the contents of the mpplist file on all nodes. All four nodes will connect using pcl, since all nodes are online.

mpp >!pcl -force -group all -shell cmd /c type “c:\Program Files\NCR\TDAT\tdConfig\mpplist-


Chapter 6:

pdeconfig Utility (NCR UNIX MP-RAS Only)

The pdeconfig utility is used to configure the Parallel Database Extensions (PDE) on a system, such as configuring the disk arrays and disks, and mapping virtual elements (AMPs and PEs) to physical elements (disks, Ethernet controllers, or host channel controllers).

Note: For Teradata RDBMS for Microsoft Windows 2000, pdeconfig is incorporated into the Parallel Upgrade Tool (PUT). For more information, please see Parallel Upgrade Tool (PUT) for Windows NT and Windows 2000 User Guide.

Audience

Users of pdeconfig include the following:

• Staging engineers• RDBMS developers• System test and verification• Field engineers• System administrators


Chapter 6: pdeconfig Utility (NCR UNIX MP-RAS Only)About pdeconfig

About pdeconfig

pdeconfig defines all of the following RDBMS elements as follows:

• Creates LUNs and slices on disk storage systems. (LUNs and slices house customer data.)

• Adds AMPs and PEs. (These processes manage the data on the disks (AMPs) and handle the traffic via the LANs and channel connections (PEs).)

• Assigns pdisks to AMPs. (Slices of LUNs are grouped into vdisks. An AMP manages the data on one vdisk.)

• Defines PDE host (client) groups. (A relationship among a group of processes (PE) and a group of communications connections (LAN or channel) is defined.)

Whenever the Teradata RDBMS configuration (that is, vprocs, disk storage, or clients) changes, use pdeconfig to make these changes. pdeconfig saves all the configuration information into the vconfig.gdo file.


Chapter 6: pdeconfig Utility (NCR UNIX MP-RAS Only)Planning PDE Configuration

Planning PDE Configuration

You should have a clear plan for the PDE system configuration. pdeconfig requires specific input which needs to be planned ahead of time. To prepare, write your answers to the following questions before PDE configuration:

Question Factors

What is the RDBMS System name? Site specific.

Which type of Disk Array to use? Symbios or EMC or mix of both.

EMC configuration is done at the EMC factory, so configuration must be planned well ahead of time.

What RAID storage type can be used with Symbios arrays?

Three types of Symbios storage exists:

• RAID5 (default): Four LUNs placed on a rank (5 drives)

• RAID 1 with striping: Eight LUNs placed on two ranks

• RAID 1 without striping: Five LUNs placed on two ranks

What RAID storage type can be used with EMC arrays?

Two types of EMC storage exist:

• RAID 1 • RAID S

What are the possible Disk/LUN slicing patterns?

Default but you can specify your own pattern.

pdeconfig automatically senses the arrays and sets up the optimum configuration.

NCR recommends the default.

How many AMPs to create? Typically one AMP per CPU, or

Symbios:

• One AMP per RAID5 rank, or• One AMP per two RAID1 ranks.

What LAN connections exist in what PCI slots?

pdeconfig will generally find these, but sometimes you need to add new or unusual types manually.

Which LAN connections should be grouped together?

Typically, all are placed in a single host group, which is accessible by several PEs.

Should BYNET LAN connections be assigned to a PE vproc?

Site specific.


Chapter 6: pdeconfig Utility (NCR UNIX MP-RAS Only)Planning PDE Configuration

How many and which PE vprocs should service each Host Group?

Site specific.

Which Host Channels should be mapped to Host Groups?

Site specific, but generally recommend one HGID per channel statement (host channel CUA). For example, each port on a PBSA is assigned its own unique HGID).

Which PE vproc should service each Host Channel connection?

pdeconfig defaults recommended.

What are the Host Channel parameters?

• Type (IBMMUX, BULLHN, and so on)• Channel Unit Address or CUA (0-FF)• Speed (DCI, 4MB, and so on)

Question Factors


Chapter 6: pdeconfig Utility (NCR UNIX MP-RAS Only)Definitions of Terms Used in pdeconfig

Definitions of Terms Used in pdeconfig

The following table defines the terms that specifically apply to pdeconfig operations.

Term Definition

adapter card

Used for host (client) channel connection.

AMP Access Module Processor virtual processor. Its components are Relational Database Management and File System Data Management.

BYNET A high-speed, bi-directional node interconnect, which provides a hardware interconnect between nodes and a software interconnect within a node for MPP systems.

clique One or more physical processing nodes that are cross-connected to one or more disk arrays.

CPU Central Processing Unit.

RDBMS Relational Database Management System.

disk array A matrix of independent but interconnected physical disk storage units.

GDOs Globally Distributed Objects. (Used by PDE and RDBMS)

HGID Host Group Identifier.

JBOD Just a Bunch Of Disks. One or more disk drives not organized as a disk array.

LAN Local Area Network.

LUN Logical Unit. The logical disk storage area presented by the disk array.

MCA bay Micro-Channel Assembly bay. Used to insert the adapter cards for host (client) channel connection and other types of cards.

MPP Massively Parallel Processing. A system with two or more SMP nodes. NCR uses a loosely coupled system configuration.

node A set of boards that makes up a physical processor, which might include multiple, tightly coupled CPUs.

PDE Parallel Database Extensions. A package that serves as an interface layer on top of the standard operating system. This interface layer runs on the SMP or MPP platform to support the execution of the Teradata RDBMS.

pdisk A slice of a LUN, uniquely identified and independently addressable. The area used for storing the Teradata RDBMS data.


Chapter 6: pdeconfig Utility (NCR UNIX MP-RAS Only)Definitions of Terms Used in pdeconfig

PE Parsing Engine virtual processor. Its components are Session Control, Optimizer, Parser/Dispatcher.

RAID5 Redundant Array of Independent Disks data protection Level 5, where data is striped across the drives in the rank. Using parity technology, every fifth block is a parity block that is used to recreate data if a disk fails.

RSG Replication Services Gateway (not used).

slicing After defining the LUNs, each LUN is divided into slices. The sum of all slices (that is, all pdisks) associated with an AMP is called a vdisk (virtual disk). The Teradata RDBMS treats the vdisk like a single disk.

SMP Symmetric Multiprocessing. A system with a single processing node that is connected to one or more disk arrays. All processors access shared memory through a common bus. A tightly coupled system configuration.

System Name

Represents the RDBMS System Name that must be entered only for the initial installation.

TPA Trusted Parallel Application. A special class of tasks, to which PDE provides a series of parallel operating system services. An example of a TPA is the Teradata RDBMS.

vdisk One or more pdisks are grouped into one vdisk, which is associated with one particular AMP.

vproc Virtual processor.

Term Definition


Chapter 6: pdeconfig Utility (NCR UNIX MP-RAS Only)Starting and Exiting pdeconfig

Starting and Exiting pdeconfig

Before you start pdeconfig, do the following:

• Determine which node is the Package Distribution Node (PDN) because pdeconfig can run only on the PDN.

Warning: You must start pdeconfig on the PDN node of the existing system. If you run pdeconfig on any new nodes, you could lose all user data on the existing system. If you have any questions, contact the PDE team of the Teradata Support Center (TSC).

Note: The PDN is applicable to both SMP and MPP systems and is often the lowest-numbered node in the system.

• Make sure the PDE and all nodes are in the NULL state.

You can start pdeconfig from a PDN console window.

To start pdeconfig, type the following:

where:

Syntax element … Specifies to …

-h display command line help for pdeconfig.

-m move AMP and/or PE vprocs.

-n run in non-PDE environment.

-p run in Multimedia environment, such as for Prospector.

-r reconstruct the vconfig.out file from the VCONFIG GDO and distributes the file to all nodes.

-u update with current information from mpplist file.

-? display command line help for pdeconfig.

pdeconfig

1102A037

-h

-m

-n

-p

-r

-u

-?



You can exit pdeconfig using one of the following:

• “Applying Changes and Exiting pdeconfig” on page 6-8• “Discarding Changes and Exiting pdeconfig” on page 6-10

Applying Changes and Exiting pdeconfig

Before you apply changes and exit pdeconfig, first you must do the following:

• Configure the disk arrays• Slice the LUNs• Create the AMPs• Assign storage to the AMPs• Configure in the LAN cards• Configure in the adapter cards• Create PEs• Assign LAN cards and PEs to host groups

The following is an example of the Apply Changes and Exit pdeconfig screen.

The following table lists the commands available for the Apply Changes screen.

APPLY CHANGES

No changes have been made to the system so far.You can do one of the following:

Apply the changes that you have specified. Jump back to the Main Menu.

a=Apply changes/j=JumpEnter command (a/e/h/j)?



Command Function

a (Applies changes.) Applies the changes that you have specified.

When this command is entered, the following question is displayed:

Are you sure you want to configure the system (y/n)?

If you type n, the system returns to the first Apply Changes screen.

If you type y, pdeconfig asks if reassigning AMPs to specific nodes is acceptable. The following appears only if one or more AMPs do not have a node assignment of -1:

27 AMP vprocs are assigned to specific nodes and 0 are not.

pdeconfig will either reassign all AMP

vprocs to specific nodes, or will leave

all AMP vproc assignments as they are.

Can pdeconfig reassign all AMPs to

specific nodes (y/n)?

Note: For systems at the level of V2R1.1.2 or above, NCR recommends you answer y. For existing systems, NCR highly recommends that AMPs be assigned to specific nodes to improve fault-tolerance.

After you type y, the system displays this message:

Configuring the system.

This may take a while . . .

Note: If you are configuring disk arrays, configuring the system takes up to about two hours.

No errors reported during configuration.

Moving current /ntos/vconfig.out to

/ntos/vconfig.out.old.

Writing /ntos/vconfig.out.

Running vconfig.

***vcf: Reading/Processing vconfig.out file***

vconfig.gdo successfully written.

vconfig finished.

Generating configuration information file:

/ntos/config.info

Restarting Array Monitor Daemon(s) (amd).

System configuration completed.

For explanations of other messages that might display, see Teradata RDBMS Messages.



Discarding Changes and Exiting pdeconfig

Use the Exit With No Changes to the System pdeconfig screen when you do not want to implement the changes you have specified. pdeconfig exits immediately. All work from this current session of pdeconfig is lost.

The following is an example of the Exit With No Changes to the System pdeconfig screen.

The following table lists the commands available for the Exit With No Changes to the System pdeconfig screen.

Example

The following is an example of starting pdeconfig without any options:

pdeconfig

*****CONFIGURING SYSTEM ipp*****

2 nodes read from /ntos/mpplist.

Requesting configuration information from all nodes.This may take several minutes...This system consists of 2 node(s) and 1 clique(s).

The following disk array ranks have no disk drives: Node: byn001-4 Array: c0t0 Rank 1 Node: byn001-4 Array: c0t0 Rank 2 Node: byn001-4 Array: c0t0 Rank 3

Command Function

e (Exit with no changes.) Exits pdeconfig without making any changes.

j (Jump) Jumps back to the Main Menu, which lists the top-level screen options (that is, Screens 1 through 9).

EXIT WITH NO CHANGES TO THE SYSTEM


Exit the program without making any changes. Jump back to a previous screen.

e=Exit with no changes/j=JumpEnter command (e/j)?



Node: byn001-4 Array: c1t0 Rank 1 Node: byn001-4 Array: c1t0 Rank 2 Node: byn001-4 Array: c1t0 Rank 3

The ranks listed above cannot be configured for PDE use.To use these ranks, you must exit pdeconfig, correct the condition(s)and then rerun pdeconfig.Press the Return key to continue...

-------------------------------------------------------------------------------TPA SUMMARY

This system has been configured for a TPA.The components associated with the following vprocs are not available forPDE Configuration until the following vprocs are removed with config/reconfig:

0 1 2 3 4 5 6 7 16380 16381 16382 16383

All other components are available for PDE Configuration.

Number of disk blocks per cylinder is 3872.

ipp currently consists of: 1 Clique(s) 2 Node(s) 8 AMP vproc(s) 4 PE vproc(s)

e=Examine or modify system info c=Continue/h=Help/j=JumpEnter command (e/c/h/j)? >>e

Note: If your system has EMC disk arrays, the following prompt appears after the nodes are read from /ntos/mpplist:

This system has EMC disk arrays and EMPATH capability.

Do you want to use EMPATH devices for EMC pdisks (y/n)? >>


Chapter 6: pdeconfig Utility (NCR UNIX MP-RAS Only)Error Messages

Error Messages

The following error messages might appear.

IF you type an invalid entry for … THEN the following message might appear …

a clique, an AMP, or a PE • Maximum allowable value is X.• Minimum allowable value is X.

a source AMP WARNING: Some of the specified source AMP vprocs are not found in current configuration.

a destination AMP WARNING: Some of the specified destination AMP vprocs are not found in current configuration.

a source PE or range of source PEs WARNING: Some of the specified source PE vprocs are not found in current configuration.

a destination PE or range of destination PEs

WARNING: Some of the specified destination PE vprocs are not found in current configuration.

vproc entries that overlap WARNING: The source and destination AMP vproc ranges overlap. Retry.

a range of source values that are not equal to a range of destination values

WARNING: The number of source AMP vprocs to be moved must be equal to the number of destination AMP vprocs.


Chapter 6: pdeconfig Utility (NCR UNIX MP-RAS Only)Configuring PDE

Configuring PDE

This entire chapter applies to SMP systems. The examples shown are from MPP systems, but similar actions must be done on all SMP systems.

Configuring PDE is a complex process. pdeconfig makes the work easier. Defaults are given to lead you through the process and result in an efficient system. NCR strongly recommends that you select the defaults.

Displays from a 5100M system show samples during a pdeconfig session. Other hardware shows minor differences (such as device names) from these examples.

To configure PDE, perform the following tasks:

Task Action See

1 Set PDE to NULL State “Task 1: Setting PDE to the NULL State”

2 Run pdeconfig “Task 2: Running pdeconfig”


Chapter 6: pdeconfig Utility (NCR UNIX MP-RAS Only)Task 1: Setting PDE to the NULL State

Task 1: Setting PDE to the NULL State

PDE starts when the system is booted, even if PDE is not yet fully configured. To run pdeconfig, PDE must not be running, meaning PDE must be in the NULL state.

PDE startup normally fails on an unconfigured system, leaving the system in the NULL state automatically. However, if PDE had been partially configured on the node, the system might not automatically go to the NULL state.

To set PDE to the NULL state, do the following:

Step Action

1 To verify if PDE is in the NULL state, type the following:

/usr/ntos/bin/pdestate

The output should show that PDE is in the NULL or NULL/STOPPED state.

2 If the PDE state is not NULL, go to a console window on a node where the state is not NULL.

3 To stop PDE, type the following and press Enter:

# /usr/ntos/bin/tpareset -x comment

where comment is the reason you are stopping PDE.


You are about to restart the database

on the system

ipp

Do you wish to continue (yes/no) [no]:

4 To continue, type the following:

y


/usr/ntos/bin/tpareset: TPA shutdown submitted.

5 To verify whether PDE is in the NULL state, type the following:

/usr/ntos/bin/pdestate


PDE: Parallel Database Extension state is NULL/STOPPED.


Chapter 6: pdeconfig Utility (NCR UNIX MP-RAS Only)Task 2: Running pdeconfig

Task 2: Running pdeconfig

pdeconfig configures PDE on the system and provides you with an opportunity to do the following:

• Configure disk arrays and disks• Map virtual elements to physical elements (that is, disks, Ethernet

controllers, or Host Channel controllers)

pdeconfig is run only on the Package Distribution Node (PDN).

The first presentation is more tutorial than strictly procedural. It shows how pdeconfig works. You can use this task as reference material for other maintenance actions.

The second presentation is a straight-through example setup for a four-node, two-clique MPP system. Every command choice is shown, in sequence.


Chapter 6: pdeconfig Utility (NCR UNIX MP-RAS Only)pdeconfig Screens

pdeconfig Screens

pdeconfig consists of nine main screens.

Top-Level Screen Description

1 = TPA summary - System information

Changes system parameters

2 = Disk Array Configuration Formats Symbios logic disk array LUNs

3 = Disk Configuration Slices LUNs into pdisks

4 = Pdisk Mapping • Creates AMP vprocs• Groups pdisks into vdisks• Assigns vdisk storage to AMPs

5 = LAN Mapping Creates PE vprocs and assigns to LAN host groups

6 = Host Channel Mapping Creates PE vprocs and assigns to channel host groups

7 = RSG Vproc Mapping This screen is not functional.

8 = Apply Changes and Exit pdeconfig

• Configures disk arrays• Saves changes • Performs sanity checking• Runs vconfig

9 = Discard Changes and Exit pdeconfig

• Discards changes• Exits pdeconfig


Chapter 6: pdeconfig Utility (NCR UNIX MP-RAS Only)Moving Between Screen Types

Moving Between Screen Types

The top-level screen is a summary. Within each top-level screen, one or two additional levels exist. The additional levels provide greater detail. The top level of a given screen type always presents an option to move to the second level for that screen type. In the same way, the second-level screen presents an option to move to the third level for that screen type.


Chapter 6: pdeconfig Utility (NCR UNIX MP-RAS Only)Jump Command

Jump Command

From the Jump Menu, you can jump from any pdeconfig screen (task) to another.

Available on most levels of each screen type, the Jump command presents a list of the nine screen types and prompts you to select one. When you select a screen type, the top level for that screen displays.

The following is a sample Jump screen:

1 = TPA Summary - System Information2 = Disk Array Configuration3 = Disk Configuration4 = Pdisk Mapping5 = LAN Mapping6 = Host Channel Mapping7 = RSG Vproc Mapping8 = Apply Changes and Exit pdeconfig9 = Discard Changes and Exit pdeconfig

Enter option(1-9) >>1


Chapter 6: pdeconfig Utility (NCR UNIX MP-RAS Only)Continue Command

Continue Command

The following occurs when you type the Continue command option:

When running pdeconfig, nothing changes the system configuration until you answer the last Yes in “Screen 8: Apply Changes” on page 6-54.

Note: The following screen examples show how pdeconfig works. Your screens might differ. Even if your screens differ, NCR still recommends using the defaults.

IF you type the Continue command at a … THEN pdeconfig …

top-level or second-level screen moves to the next top-level screen.

third-level screen returns to the current top-level screen.

This occurs because you use third-level screens to configure a single clique. So normally when you finish with one clique, you want to go to the next clique rather than skip ahead to the next task.


Chapter 6: pdeconfig Utility (NCR UNIX MP-RAS Only)Screen 1: TPA Summary

Screen 1: TPA Summary

The TPA Summary screen summarizes the current system configuration:

• Number of disk blocks per logical cylinder• Number of cliques, nodes, AMPs, and PEs

The TPA Summary screen allows you examine or modify the following system information:

• System name• Number of blocks per cylinder

The TPA Summary screen is shown below.

TPA SUMMARYNumber of disk blocks per cylinder is 1488.<System-name> currently consists of: 2 clique(s) 4 node(s) 0 AMP vproc(s) 0 PE vprocs e=Examine or modify system infoh=Help/j=Jump/c=continueEnter command (e/h/j/c)? >>


Chapter 6: pdeconfig Utility (NCR UNIX MP-RAS Only)Screen 1: TPA Summary

In the TPA Summary screen, do the following:

Step Action

1 To modify the system information, type the following:

e

The TPA Detailed Display appears:

TPA DETAILED DISPLAYSystem Name: ippNumber of disk blocks per cylinder: 3872Total vprocs: 12State of vprocs:

8 AMP vproc(s) = ONLINE 4 PE vproc(s) = ONLINE

b=modify number of Blocks per cylinder/s=modify System namec=Continue/h=Help/j=JumpEnter command (b/s/c/h/j)? >>

2 To modify the System Name, type the following:

s

The following appears:

Enter new system name:

3 Type the new RDBMS System Name, which is the name of the entire RDBMS system. For example: Customer1.

Customer1

4 Verify whether the number of disk blocks per cylinder shown is 3872.

5 To modify the number of blocks per cylinder to 3872, type the following:

b = 3872


c

The Disk Array Summary screen appears.


Chapter 6: pdeconfig Utility (NCR UNIX MP-RAS Only)Screen 2: Disk Array Summary

Screen 2: Disk Array Summary

The Disk Array Summary screen summarizes the following:

• Number of cliques in the system• Number of disk array ranks in the system• Status of the disk array ranks

While gathering information about the system, pdeconfig determines how many ranks are in the system and the condition of the LUNs on the ranks.

Disk array configuration using pdeconfig can be used with Symbios Logic and EMC disk array units.

The Disk Array Summary screen allows you to do the following:

• Use the default disk array setup• Examine or modify a disk array

The Disk Array Summary screen is shown below.

DISK ARRAY SUMMARYCurrent system consists of: 2 Cliques 16 Disk Array RanksCliques with 2 nodes, 8 ranks are: 0 1

d=Default disk array setup for clique/e=Examine or modify disk array /c=Continue/h=Help/j=JumpEnter command (d/e/c/h/j)? >>



In the Disk Array Summary screen, do the following:

Step Action

1 To examine or modify the disk array, type the following:

e

The system prompts for the clique number you want to examine or modify.

Enter a clique number to examine/modify, or q to quit (xx/q) >>0

2 Type the appropriate clique number (for example: 0).

The Clique Disk Array Summary screen appears:

CLIQUE 0 DISK ARRAY SUMMARY

2 Nodes8 Ranks

2 RAID5 rank(s)2 RAID1 rank(s)4 unconfigured rank(s)

Examine or modify disk array (y/n)? >>y

Note: If your system is connected to an EMC disk array, your Clique Disk Array Summary screen might look like this:

CLIQUE 0 DISK ARRAY SUMMARY

1 Node 0 Ranks




3 To modify the disk array, type the following and press Enter:

y

A list of the ranks from clique 0 appears:

CLIQUE 0 DISK ARRAY DETAILS

RANK LUNS STATUS RANK LUNS STATUS(00) *C111t5:0 0-7 RAID1-STRIPE (04) *c20t5:0 0-3 RAID5(01) *c111t5:1 RAID1-STRIPE (05) *c20t5:1 4-7 RAID5(02) c111t5:2 NOT_CONFIGURED (06) c20t5:2 NOT_CONFIGURED(03) c111t5:3 NOT_CONFIGURED (07) c20t5:3 NOT_CONFIGURED

*=previously configured, must remove all LUNs from this array to reconfigured=Default rank configuration/m=Make LUNs from on rank/r=Remove all LUNs from arrayc=Continue/h=help/j=JumpEnter command (d/m/r/c/h/j)?

Note: This example was taken from a working system that had already been configured. On an initial installation, the *previously configured message would not appear.

Note: If your system is connected to an EMC disk array, your CLIQUE 0 DISK ARRAY DETAILS screen might look like this:


RANK LUNS STATUS RANK LUNS STATUS

*=previously configured, must remove all LUNs from this array to reconfigure

d=Default rank configuration/m=Make LUNs on rank/r=Remove all LUNs from arrayc=Continue/h=Help/j=JumpEnter command (d/m/r/c/h/j)? >>

At this point, you can do one of the following:

• Use the default configuration (RAID5).• Use a non-RAID5 configuration.• Remove all existing LUNs from a specified array.

Step Action



IF you want to … THEN …

use the default configuration (RAID 5)

a In the Clique Disk Array Details screen, type the following:d

The system prompts for the rank ID:Enter rank id for default configuration, or q to quit (xx/q) >>6

b Type the appropriate rank id number (for example: 6).The status for rank 6 changes to RAID5, and the LUNS are 8-b. The following refreshed screen appears:


RANK LUNS STATUS(00) *C111t5:0 0-7 RAID1-STRIPE(01) *c111t5:1 RAID1-STRIPE(02) c111t5:2 NOT_CONFIGURED(03) c111t5:3 NOT_CONFIGURED(04) *c20t5:0 0-3 RAID5(05) *c20t5:1 4-7 RAID5(06) c20t5:2 8-b RAID5(07) c20t5:3 NOT_CONFIGURED

d=Default rank configuration/m=Make LUNs from one rank/r=Remove all LUNs from arrayc=Continue/h=help/j=JumpEnter command (d/m/r/c/h/j)? >>

c Repeat the above steps to configure other ranks.

Step Action




use a non-RAID5 configuration

a In the Clique Disk Array Details screen, type the following:m

The system prompts for the rank to configure:Enter rank to configure, or q to quit (xx/q) >>0

b Type the appropriate rank id number (for example: 0). The following screen appears: 1. RAID5

2. RAID1-STRIPE (not allowed for 6282)3. RAID1-NOSTRIPE

Enter new rank configuration type, or q to quit (xx/q) >>2

c Type the appropriate number for the new rank configuration type (for example: 2).The status for rank 0 changes to RAID1-STRIPE. The Clique Disk Array Details screen appears:


RANK LUNS STATUS(00) *C111t5:0 0-7 RAID1-STRIPE(01) *c111t5:1 RAID1-STRIPE(02) c111t5:2 8-b RAID5(03) c111t5:3 NOT_CONFIGURED(04) *c20t5:0 0-3 RAID5(05) *c20t5:1 4-7 RAID5(06) c20t5:2 8-b RAID5(07) c20t5:3 NOT_CONFIGURED

d=Default rank configuration/m=Make LUNs from on rank/r=Remove all LUNs from arrayc=Continue/h=help/j=JumpEnter command (d/m/r/c/h/j)? >>

d Repeat the above steps to configure other ranks.

Step Action




remove all existing LUNs from a specified array

a In the Clique Disk Array Details screen, type the following:r

The system prompts for the rank ID:Enter any rank from array, or q to quit (xx/q) >>

b Type the appropriate rank ID number (for example: 0), which can be for any rank on the disk array.The status for all ranks on disk array c111t5 changes to not_configured. The following screen appears:


RANK LUNS STATUS(00) c111t5:0 NOT_CONFIGURED(01) c111t5:1 NOT_CONFIGURED(02) c111t5:2 NOT_CONFIGURED(03) c111t5:3 NOT_CONFIGURED(04) *c20t5:0 0-3 RAID5(05) *c20t5:1 4-7 RAID5(06) c20t5:2 8-b RAID5(07) c20t5:3 NOT_CONFIGURED

d=Default rank configuration/m=Make LUNs from on rank/r=Remove all LUNs from arrayc=Continue/h=help/j=JumpEnter command (d/m/r/c/h/j)? >>

4 To return to the Disk Array Summary screen, type the following:

c

5 Repeat the steps from the Disk Array Summary screen until all the other cliques are examined or modified.

6 To continue after you are finished modifying all the cliques, type the following:

c

The Disk Slicing Summary screen appears.

Step Action


Chapter 6: pdeconfig Utility (NCR UNIX MP-RAS Only)Screen 3: Disk Slicing Summary

Screen 3: Disk Slicing Summary

The Disk Slicing Summary screen summarizes the following:

• Number of cliques in the system• Number of disk array ranks in the system• Status of the disks

The Disk Slicing Summary screen allows you to do the following:

• Use default disk slicing• Examine or modify disk slicing• Copy disk slicing

Optimized slicing schemes are available as defaults for Symbios Logic, EMC, and NSC disk array units. pdeconfig recognizes these array types but does not recognize any other vendor disk. pdeconfig uses a generic slicing scheme.

NCR strongly recommends using the default slicing schemes of pdeconfig, although this is not mandatory.

NCR UNIX MP-RAS release 3.0.1 allows much larger disk slices, to the point that a slice can occupy a whole LUN. This is the new default slicing pattern.

If you are adding new disk arrays to an existing system, you probably want to use the slicing method already on the existing disk arrays. You can use the copy option to copy the existing slicing pattern from the old disk arrays to the new disk arrays.

The Disk Slicing Configuration screen is shown below.

DISK SLICING SUMMARY

Current system consists of:2 cliques

64 disks

Cliques with 2 nodes, 32 disks are:0 1

d=Default disk slicing for clique/e=Examine or modify disk slicing for clique/p=coPy disk slicing for cliquec=Continue/h=Help/j=Jump/c=Continue



SMP Systems

SMP systems do not use cliques. If you are installing an SMP system, pdeconfig shows one clique, numbered clique 0.

In the Disk Slicing Summary screen, do the following:

Step Action

1 To modify disk slicing, type the following:

e

Note: Optionally, if you are adding disk arrays to an existing system and want to use the existing slicings on the new disk array, then use the p (coPy) option at this point and follow the screen prompts.

The system prompts you for the clique number:

Enter a clique number to examine or modify, or q to quit (##/q)? >>0

2 Enter the appropriate clique number (for example: 0).

Note: If you have an SMP system, then the system calls the disk array clique 0. Therefore, enter 0.

The following screen appears:

CLIQUE 0 DISK SLICING SUMMARY

2 Nodes

32 Disks which consisting of:

0 System Disk0 Data Disks (Default Slices)0 Data Disks (Non-Default Slices)

32 Unformatted or Unsliced Disks

Examine or modify disk slicing (y/n) >>y



3 To modify disk slicing, type the following:

y

A list of the physical disks and LUNs appears:

CLIQUE 0 DISK SLICING DETAILS

System Disks:(none)

Data Disks (Default Slices):(none)

Data Disks (Non-Default Slices):(none)

Unformatted or Unsliced Disks:(00)c111t5d0s0 (01)c111t5d1s0 (02)c111t5d2s0 (03)c111t5d3s0 (04)c111t5d4s0 (05)c111t5d5s0 (06)c111t5d6s0 (07)c111t5d7s0 (08)c111t5d8s0 (09)c111t5d9s0 (10)c111t5das0 (11)c111t5dbs0 (12)c111t5dcs0 (13)c111t5dds0 (14)c111t5des0(15)c111t5dfs0 (16)c20t5d0s0 (17)c20t5d1s0 (18)c20t5d2s0 (19)c20t5d3s0 (20)c20t5d4s0 (21)c20t5d5s0 (22)c20t5d6s0 (23)c20t5d7s0 (24)c20t5d8s0 (25)c20t5d9s0 (26)c20t5das0 (27)c20t5dbs0 (28)c20t5dcs0 (29)c20t5dds0(30)c20t5des0 (31)c20t5dfs0

d=Default slices/e=Edit slices/p=coPy slices/v=View Slices/h=Help/j=Jump/c=ContinueEnter command (d/e/p/v/a/h/j/c)? >>d

Step Action



4 a To select default slices, type the following:d

The system prompts you for the disk number:Enter a disk number or range of numbers, or q to quit (xx/xx-xx/q) >>0-31

b Type the appropriate range of numbers or press Enter for the default range: 0-31.The following appears:CLIQUE 0 DISK SLICING DETAILS

System Disks:(none)

Data Disks (Default Slices):(00)c111t5d0s0 (01)c111t5d1s0 (02)c111t5d2s0 (03)c111t5d3s0 (04)c111t5d4s0 (05)c111t5d5s0 (06)c111t5d6s0 (07)c111t5d7s0 (08)c111t5d8s0 (09)c111t5d9s0 (10)c111t5das0 (11)c111t5dbs0 (12)c111t5dcs0 (13)c111t5dds0 (14)c111t5des0(15)c111t5dfs0 (16)c20t5d0s0 (17)c20t5d1s0 (18)c20t5d2s0 (19)c20t5d3s0 (20)c20t5d4s0 (21)c20t5d5s0 (22)c20t5d6s0 (23)c20t5d7s0 (24)c20t5d8s0 (25)c20t5d9s0 (26)c20t5das0 (27)c20t5dbs0 (28)c20t5dcs0 (29)c20t5dds0(30)c20t5des0 (31)c20t5dfs0

Data Disks (Non-Default Slices):(none)

Unformatted or Unsliced Disks:(none)

d=Default slices/e=Edit slices/p=coPy slices/v=View slices/h=Help/j=Jump/c=ContinueEnter command (d/e/p/v/a/h/j/c)? >>

5 To return to the Disk Slicing Summary screen, type the following:

c

6 Repeat the steps from the Disk Slicing Summary screen until you have examined or modified all the other cliques.

Note: This step is for MPP systems only.

7 After you are finished modifying all the cliques, type the following:

c

The Pdisk Mapping Summary screen appears.

Step Action


Chapter 6: pdeconfig Utility (NCR UNIX MP-RAS Only)Screen 4: Pdisk Mapping Summary

Screen 4: Pdisk Mapping Summary

The Pdisk Mapping Summary screen summarizes the following:

• Number of cliques in the system• Number of pdisks in the system

The Pdisk Mapping Summary screen allows you to do the following:

• Use the default pdisk mapping• Examine or modify pdisk mappings• Copy pdisk mappings

To do this, you need to know the following:

• How many pdisks to assign to each AMP• Which pdisks to assign to which AMP

You must provide this information to the site team before the system is installed. These decisions are based on a set of guidelines provided by NCR to best fit the your specific environment.

In general, the following rules apply:

• You must assign at least one pdisk to each AMP.• Only slices tagged as USR are available for use as pdisks.

Beginning with Teradata V2R3.0, the AMP vproc numbering has been increased to the range 0 through 16199.

The Pdisk Mapping Summary screen is shown below.

PDISK MAPPING SUMMARY

Current system consists of:

2 cliques 64 pdisks

d=Default pdisk mapping for clique/e=Examine or modify pdisk mappings for clique/p=coPy pdisk mappings for cliquec=Continue/h=Help/j=Jump/



In the Pdisk Mapping Summary screen, do the following:

Step Action

1 To examine or modify pdisk mapping, type the following:

e

The system prompts you for a clique number:

Enter a clique number to examine or modify, or q to quit (##/q)? >>0

2 Enter the appropriate clique number (for example: 0).

Note: SMP systems call the disk array clique 0. For SMP systems, enter 0.

A summary screen of the existing AMP vproc to pdisk mapping appears:

CLIQUE 0 PDISK MAPPING SUMMARY

No AMP vprocs mapped to storage.

Unassigned slices: 64

Examine or modify Pdisk mappings(y/n)? >>y

Note: If your system is connected to an EMC disk array, your Pdisk Mapping Summary screen might look like this:

CLIQUE 0 PDISK MAPPING SUMMARY

NO AMP vprocs mapped to storage.

Unassigned slices: 1 (00) c2t9d0s1




3 To examine or modify pdisk mappings, type the following:

y

The Clique 0 pdisk to AMP vproc assignment appears:

CLIQUE 0 PDISK TO AMP VPROC ASSIGNMENTS

Unassigned slices:

(00)c111t5d0s8 (01)c111t5d0s9 (02)c111t5d1s8

(03)c111t5d1s9 (04)c111t5d2s8 (05)c111t5d2s9

(06)c111t5d3s8 (07)c111t5d3s9 (08)c111t5d4s8

.. .. ..

.. .. ..

.. .. ..

(57)c20t5dcs9 (58)c20t5dds8 (59)c20t5dds9

(60)c20t5des8 (61)c20t5des9 (62)c20t5dfs8

(63)c20t5dfs9

No AMP vprocs mapped to storage

d=Assign defaults/a=Assign storage/r=Remove storage/h=Help/j=Jump/c=Continue

Enter command (d/a/r/h/j/c)? >>

At this point, you can do one of the following:

• Use the default storage assignments• Manually assign storage• Remove storage

CAUTION: Inspect the list of slices for any node system disks. If any are node system disks, use extreme caution, especially when using the default assign option. Under most circumstances, you should not use system disks as RDBMS data disks.

Step Action




use the default storage

a Type the following:d

The following message appears:There are 64 unassigned pdisks.There are currently 0 AMP vprocs managing 0 pdisks.Up to 16 AMP vprocs can be added, depending on the number of pdisks per AMP vproc.Enter number of AMP vprocs to add or q to quit (##/q)? >>16

b Enter the appropriate number of AMP vprocs you want to add (for example: 16).The utility requests the number of pdisks per AMP.There can be up to 4 pdisks per AMP vproc.Enter number of pdisks per AMP vproc or q to quit (##/q)? >>4

c Enter the appropriate number of pdisks per AMP vproc (for example: 0).pdeconfig checks the limitation of 61,000 cylinders maximum per AMP vproc, and limits the number of pdisks to fit the maximum.The pdisk to AMP default assignments screen appears:CLIQUE 0 PDISK TO AMP VPROC ASSIGNMENTS

Unassigned slices: 0AMP vprocs mapped to storage (17570304 blocks):0: (00)c111t5d0s0 (01)c111t5d1s0 (02)c111t5d2s0

(03)c111t5d3s0 1: (04)c111t5d4s0 (05)c111t5d5s0 (06)c111t5d6s0

(07)c111t5d7s0 .. .. .... .. .... .. ..

16: (60)c20t5des8 (61)c20t5des9 (62)c20t5dfs8(63)c20t5dfs9

d=Assign Defaults/a=Assign storage/r=Remove storage/h=Help/j=Jump/c=Continue

Step Action




manually assign storage

a Type the following:a

The system prompts for an AMP vproc number.Enter an AMP vproc (##)? >>0

Note: If your system is connected to an EMC disk array, the system might show the following prompt:

Enter AMP vproc id to add slice to, or q to quit (##/q)? >>

As a general rule, AMP vprocs are numbered starting from 0, incrementing by 1 for each additional AMP.

b Enter AMP vproc ID (for example: 0).The system prompts you for slice numbers:Enter slice number to assign or q to quit (##/q)? >>0Enter slice number to assign or q to quit (##/q)? >>1Enter slice number to assign or q to quit (##/q)? >>2Enter slice number to assign or q to quit (##/q)? >>3Enter slice number to assign or q to quit (##/q)? >>q

c Enter 0, 1, 2, 3, 4, 5, 6, 7 or whatever for the slice number (index number on the screen).

d When finished, type the following:q

The following screen appears:CLIQUE 0 PDISK TO AMP VPROC ASSIGNMENTS

Unassigned slices: 0AMP vprocs mapped to storage (17570304 blocks):

0: (00)c111t5d0s0 (01)c111t5d1s0 (02)c111t5d2s0(03)c111t5d3s0


.. .. ..

.. .. ..

.. .. ..16: (60)c20t5des8 (61)c20t5des9 (62)c20t5dfs8

(63)c20t5dfs9d=Assign Defaults/a=Assign storage/r=Remove storage/h=Help/j=Jump/c=Continue

Step Action




remove (unassign) storage

a Type the following:r The systems prompts for the ID of the AMP vproc to be removed.

b Type the appropriate AMP vproc id to be removed (for example: 0).The following refreshed screen appears:CLIQUE 0 PDISK TO AMP VPROC ASSIGNMENTS

Unassigned slices:(00)c111t5d0s8 (01)c111t5d0s9 (02)c111t5d1s8(03)c111t5d1s9 AMP vprocs mapped to storage (17570304 blocks)


d=Assign Defaults/a=Assign storage/r=Remove storage/h=Help/j=Jump/c=Continue

4 To return to the Pdisk Mapping Summary screen, type the following:

c

5 On MPP systems only, repeat the steps from the Pdisk Mapping Summary screen until all the other cliques are examined or modified.

6 To continue after you are finished modifying all the cliques, type the following:

c

The LAN Summary screen appears.

Step Action


Chapter 6: pdeconfig Utility (NCR UNIX MP-RAS Only)Screen 5: LAN Summary

Screen 5: LAN Summary

The LAN Summary screen allows you to examine or modify LAN mappings.

In LAN Mapping, LAN and BYNET connections are mapped to PEs. The pdeconfig utility identifies most LANs automatically.

Note: For an SMP system, if no Local Area Network (LAN) connections exist, you can skip this screen.

Beginning with Teradata V2R3.0, the number of Host Group IDs has been increased to the range 1 through 1023. The range of PE vproc numbers has been increased to the range 15,360 to 16,385.

The LAN Summary screen is shown below.

LAN SUMMARY

4 LANs, consisting of: Unassigned LANs: 4

e=Examine or modify LAN mappingsc=Continue/h=Help/j=JumpEnter command (e/c/h/j)? >>e



In the LAN Summary screen, do the following:

Step Action

1 To examine or modify LAN mapping, type the following:

e


LAN TO PE VPROC ASSIGNMENTS

HGID -1 (Unassigned)

LANs: (00) node:001-01 bus:1 slot:4 kind:ETHERNET description: WD EtherCard PLUS/A (WD8013EP/A)

(01) node:001-01 bus:-1 slot:-1 kind:BYNETdescription: Bynet

(02) node:001-10 bus:1 slot:4 kind:ETHERNETdescription: WD EtherCard PLUS/A (WD8013EP/A)

(03) node:001-10 bus:-1 slot:-1 kind:BYNET description: Bynet

a=Add LAN/d=Default assign/l=LAN assign/m=Modify LAN/v=PE Vproc assign/r=PE Vproc Remove/P=Add Bynet LAN(s)/c=Continue/h=Help/j=JumpEnter command (a/d/l/m/v/r/p/c/h/j)? >>

At this point, you have several options:

• Manually add a LAN• Use default LAN assignments• Manually assign a LAN• Modify an existing LAN assignment• Manually assign a PE vproc• Remove a PE vproc• Add a BYNET adaptor board




manually add a LAN

using the following procedure is more reliable than manually editing the vconfig.out file, if pdeconfig is unable to read some brands of network boards.

a In the LAN to PE VPROC assignments screen, type the following:a

The system prompts for a node ID:Enter the associated Node ID of the added LAN or q to quit (CCC-MM/q)? >>001-04

b Type the node ID of the added LAN (for example: 001-04).The system prompts for a new bus number:Enter the new bus number or q to quit (##/q)? >>2

c Type the new bus number (for example: 2).The system prompts for a new slot number:Enter the new slot number or q to quit (default: -1) (##/q/)? >> 4

The system prompts for a new LAN type:LAN types: 0=UNKNOWN 4=BYNET

1=ETHERNET TCPIP 5=SCSI ETHERNET

2=X25 6=SCSI X25

3=TOKEN RING 7=SCSI TOKEN RING

Enter the new LAN type or q to quit (##/q)? >>

d Type the new LAN type (for example: 1).The LAN to PE VPROC assignments screen appears showing the new LAN.

use default LAN assignments

a In the LAN to PE VPROC assignments screen, type the following:d

The defaults appear:LAN TO PE VPROC ASSIGNMENTSHGID -1 (Unassigned)PE vprocs:HGID 1LANs: (00) node:001-01 bus:1 slot:4 kind:ETHERNET

description: WD EtherCard PLUS/A (WD8013EP/A)(01) node:001-01 bus:-1 slot:-1 kind:BYNET

description: Bynet(02) node:001-10 bus:1 slot:4 kind:ETHERNET

description: WD EtherCard PLUS/A (WD8013EP/A)(03) node:001-10 bus:-1 slot:-1 kind:BYNET

description: BynetPE vprocs: 16383 16382 16381 16380

a=Add LAN/d=Default assign/l=LAN assign/m=Modify LAN/v=PE Vproc assign/r=PE Vproc Remove/P=Add Bynet LAN(s)/c=Continue/h=Help/j=JumpEnter command (a/d/l/m/v/r/p/c/h/j)? >>

Step Action




manually assign a LAN

a In the LAN to PE VPROC assignments screen, type the following:l

The system prompts for a LAN number:Enter the LAN number to be assigned or q to quit (##/q)? >>1

b Type the appropriate number for the LAN device index number (for example: 1).The system prompts for a Host Group ID (HGID):Enter HGID to assign it to or q to quit (##/q)? >>1

Note: NCR recommends that you assign all LAN and PE vprocs to the same Host Group ID (HGID).

c Type the appropriate number for the HGID to receive the LAN device (for example: 1). A LAN is assigned to the specified PE vproc.

modify an existing LAN assignment

a In the LAN to PE VPROC assignments screen, type the following:m

The system prompts for the LAN number:Enter the LAN number to be modified or q to quit (##/q)? >>03

b Type the number of the LAN to be modified (for example: 03).The system prompts for the bus number:Enter the bus number to be modified or q to quit (##/q)? >>1

c Type the new bus number (for example: 1).Note: Be careful when you change bus numbers. pdeconfig scans the system for devices. Usually, changing device bus numbers is unnecessary.The system prompts for the slot number:Enter the new slot number to be modified or q to quit (##/q)? >>4

d Type the appropriate number for the new slot number (for example: 4).Note: Be careful when you change slot numbers. pdeconfig scans the system for devices. Usually, changing device slot numbers is unnecessary.The system prompts for the LAN type:LAN types: 0=UNKOWN, 1=ETHERNET TCPIP, 2=X25

3=TOKEN RING, 4=BYNET, 5=SCSI ETHERNET

6=SCSI X25, 7=SCSI TOKEN RING

Enter to the new LAN type or q to quit (##/q)? >>1

e Type the appropriate LAN type (for example: 1).

Step Action




manually assign a PE vproc

a In the LAN to PE VPROC assignments screen, type the following:v

The system prompts for a PE number.Enter the PE vproc id to be assigned or q to quit (##/q)? >>16379

b Type the appropriate PE vproc number (for example: 16379). Note: PE vproc numbering starts at 16383 and counts down to 15360. If a PE vproc number does not exist, pdeconfig creates the number.The system prompts for the Host Group ID (HGID):Enter HGID to assign it to or q to quit (##/q)? >>1

c Type the appropriate number for the HGID to receive the PE vproc number (for example: 1). Host group IDs can range from 1 to 1023.The system prompts for a Node ID:Enter the Node ID to assign it to or q to quit (CCC-MM/q)? >>001-04

d Type the Node ID where the LAN board resides (for example: 001-04).Note: Node ID format for 5100M systems differs from the general node naming convention. Within a cabinet, bottom nodes generally identified as 00x-10 are named here 00x-02. On a multi-node system, none of the nodes can have a Node ID of 0.The LAN to PE VPROC assignments screen appears.

remove a PE vproc a In the LAN to PE VPROC assignments screen, type the following:r

The system prompts for a PE number.Enter the PE vproc id to be removed or q to quit (##/q)? >>16379

b Type the appropriate PE vproc number (for example: 16379). The LAN to PE VPROC assignments screen appears showing that the PE vproc number is removed.

Step Action




modify an existing BYNET adapter board (MPP Systems Only)

a On an MPP system, in the LAN to PE VPROC assignments screen, verify that each node has an associated BYNET LAN.Note: NCR recommends that you group all BYNET LANs and associated PE vprocs into one HGID.

b In the LAN to PE VPROC assignments screen, type the following:m

The system prompts for the LAN number to be modified:Enter the LAN number to be modified or q to quit (##/q)? >> 00

c Type the appropriate LAN number (for example: 00).The system prompts for the bus number to be modified:Enter the bus number to be modified or q to quit (##/q)?1

d Type the bus number (for example: 1).The system prompts for the new slot number:Enter the new slot number or q to quit (default: -1) (##/q/)? >> 2

e Type the new slot number (for example: 2).The following screen appears:LAN types: 0=UNKNOWN 4=BYNET


2=X25 6=SCSI X25


Enter the new LAN type or q to quit (default: 4) (##/q)? >> 5

f Type the new LAN type (for example: 5).The LAN to PE VPROC assignments screen reappears showing the changes.

Step Action




add a BYNET adapter board (MPP Systems Only)

a In the LAN to PE VPROC assignments screen, type the following:a

Note: NCR recommends that you group all BYNET LANs and associated PE vprocs into one HGID.The system prompts for the associated node ID of the added LAN:Enter the associated Node ID of the added LAN or q to quit (CCC-MM/q)? >>001-05

b Type the appropriate LAN number (for example: 001-05).

The system prompts for the new bus number:Enter the new bus number or q to quit (##/q)? >>1

c Type the bus number (for example: 1).The system prompts for the new slot number:Enter the new slot number or q to quit (default: -1) (##/q/)? >> 3

d Type the new slot number (for example: 3).The following screen appears:LAN types: 0=UNKNOWN 4=BYNET


2=X25 6=SCSI X25


Enter the new LAN type or q to quit (##/q)? >> 4

e Type the new LAN type (for example: 4).The LAN to PE VPROC assignments screen appears showing the new BYNET board.

2 To continue after you are finished modifying LAN mapping, type the following:

c

The HOST Channel Mapping screen appears.

Step Action


Chapter 6: pdeconfig Utility (NCR UNIX MP-RAS Only)Screen 6: Host Channel Summary

Screen 6: Host Channel Summary

Note: If no host channel connections to the system exist, you can skip this screen.

The Host Channel Summary screen summarizes the relationship of PE vprocs to Host Channel controller boards.

In order to handle RDBMS session traffic, the initial configuration plan for your system determined the following:

• How many channel connections would be installed• How many PE vprocs would be assigned to which channels

Be sure you configure the channel and PE assignments according to this plan. To make corrections later is very time consuming.

The Host Channel Summary screen is shown below.

HOST CHANNEL SUMMARY0 Host Channels, consisting of:HGID 1: 0 Host Channel(s) mapped to 0 PE vproc(s)

Unassigned Channels: 2

e=Examine or modify Host Channel mappingsc=Continue/h=Help/j=JumpEnter command (e/c/h/j)? >>e

The procedure for host channel mapping is similar to LAN mapping.



In the Host Channel Summary screen, do the following:

Step Action

1 To examine or modify host channel mappings, type the following:

e

The Host Channel to PE Vproc Assignments screen appears:

HOST CHANNEL TO PE VPROC ASSIGNMENTS

HGID -1 (UNASSIGNED)

Channels: (00)node:001-00 bus:1 slot:5 port=0 kind:IBMMUX

speed:DCI cua:00

Channels: (01)node:001-02 bus:1 slot:5 port=0 kind:IBMMUX

speed:DCI cua:00

PE vprocs:

HGID 1 (Not assigned to a Host Channel)

Channels:

PE vprocs:

a=Add chan/d=Default assign/m=Modify chan/n=chaN assign/v=PE Vproc assign/r=PE Vproc Remove

c=Continue/h=Help/j=Jump

Enter command (a/d/m/n/v/c/h/j)? >>d

At this point, you have several options:

• Add a host channel• Use default host channel assignments• Modify an existing host channel assignment• Manually assign a host channel• Manually assign a PE VPROC• Manually remove a PE VPROC

The default option is a one-to-one, PE-to-channel assignment. The default creates a new PE vproc and HGID for each channel and ensures no conflicting values occur with existing AMP or PE vprocs.


manually add a host channel

a In the Host Channel to PE Vproc Assignments screen, type the following:a

The system prompts for the node ID of the added channel:Enter the associated Node ID of the added Channel or q to quit (CCC-MM/q)? >>

b Type the node ID of the added channel (for example: 001-05).The system prompts for the new bus number:Enter the new bus number or q to quit (##/q)? >> 01




manually add a host channel (cont)

c Type the new bus number (for example: 01).The system prompts for the new slot number:Enter the new slot number or q to quit (default: -1) (##/q/)? >> 3

d Type the new slot number (for example: 3).The system prompts for the new port number:Enter the new port number or q to quit (default: -1) (##/q/)? >> 3

e Type the new port number (for example: 3).The system prompts for the new channel type:Host Channel types: 0=UNKNOWN 3=ATT3B 6=FICON

1=IBMMUX 4=BULL/HONEYWELL

2=ESCON 5=OS1100

Enter the new Channel type or q to quit (##/q)? >>

f Type the new channel type (for example: 6).The system prompts for the Logical Control Unit address:Enter the Logical Control Unit Address (IN HEX) or q to quit(##/q)? >> 7f

g Type the logical control unit address (for example: 7f).The system prompts for the Logical Channel Number:Enter the Logical Channel Number or LPAR value (IN HEX) or q to quit(##/q)? >> 8g

h Type the logical channel number (for example: 8g).The system prompts for link address:Enter the Link Address(port number) on the director (IN HEX) or q to quit(##/q)? >> 5b

i Type the link address (for example: 5b).The system prompts for the new channel unit address:Enter the new Channel Unit Address (IN HEX) or q to quit (##/q)? >> 2a

j Type the new channel unit address (for example: 2a).The system prompts for a new channel speed:Channel speeds: 0=DCI 3=3MB

1=4MB 4=FIBER OPTIC

2=UNKNOWN

Enter the new Channel speed or q to quit (##/q)? >> 4

Step Action




manually add a host channel (cont.)

k Type the new channel speed (for example: 4).The Host Channel to PE VPROCS Assignments screen displays the new host channel configuration.

use the default host channel assignments

a In the Host Channel to PE Vproc Assignments screen, type the following:d

The following screen appears:HOST CHANNEL TO PE VPROC ASSIGNMENTSHGID 2Channels: (00)node:001-00 bus:1 slot:5 port=0 kind:IBMMUX speed:DCI cua:00PE vprocs: 16379

HGID 3Channels: (01)node:001-02 bus:1 slot:5 port=0 kind:IBMMUX speed:DCI cua:00PE vprocs: 16378

a=Add chan/d=Default assign/m=Modify chan/n=chaN assign/v=PE Vproc assignc=Continue/h=Help/j=JumpEnter command (a/d/m/n/v/c/h/j)?

The default Host Channel assignments might not set the Channel Unit Addresses (cua), speed, and/or protocol type (kind) correctly.To modify the cua, speed, kind, bus, or slot in the Host Channel Summary, you will have to modify the host channel assignment.

modify an existing host channel assignment

a In the Host Channel to PE Vproc Assignments screen, type the following:m

The system prompts for the channel number:Enter the channel number to be modified or q to quit (##/q)? >>00

b Type the appropriate number for the channel number (for example: 00).The system prompts for the bus number:Enter the bus number to be modified or q to quit (##/q)? >>1

c Type the new bus number (for example: 1).The system prompts for the slot number:Enter the new slot number or q to quit (##/q)? >>5

Step Action




modify an existing host channel assignment (cont)

d Type the appropriate new slot number (for example: 5).Note: Use caution when changing slot numbers. pdeconfig scans the system for installed devices, and it is not usually necessary to change device slot numbers.The system prompts for the new port number:Enter the new port number or q to quit (##/q)? >>0

e Type the new port number (for example: 0).If necessary, look at the adapter board to see which port is connected to the LAN. The system prompts for the host channel type:Host Channel types: 0=UNKNOWN 3=ATT3B 6=FICON

1=IBMMUX 4=BULL/HONEYWELL

2=ESCON 5=OS1100

Enter the new channel type or q to quit (default: 6) (##/q)? >> 4

f Type the new channel type (for example: 4).The system prompts for the Channel Unit Address (cua):Enter the new Channel Unit Address (IN HEX) or q to quit (##/q)? >>7f

g Type the logical control unit address (for example: 7f).The system prompts for the Logical Channel Number:Enter the Logical Channel Number or LPAR value (IN HEX) or q to quit(##/q)? >> 8g

h Type the logical channel number (for example: 8g).The system prompts for link address:Enter the Link Address(port number) on the director (IN HEX) or q to quit(##/q)? >> 5b

i Type the link address (for example: 5b).The system prompts for the new channel unit address:Enter the new Channel Unit Address (IN HEX) or q to quit (##/q)? >> 2a

j Type the Channel Unit Address (in Hex) (for example: 2a).The system prompts for the channel speed:Channel speeds:0=DCI 3=3MB

1=4MB 4=FIBER OPTIC

2=UNKOWN

Enter the new channel speed or q to quit (##/q)? >>4

Step Action




modify an existing host channel assignment (cont)

k Type the new channel speed (for example: 4).The Host Channel to PE VPROC Assignments screen reappears with the new configuration.

manually assign a host channel

a In the Host Channel to PE Vproc Assignments screen, type the following:n

The system prompts for the host channel number:Enter the host channel number to be assigned or q to quit (##/q)? >>00

b Type the appropriate number for the host channel number (for example: 00).The system prompts for the bus number:Enter HGID to assign it to or q to quit (##/q)? >> 3

c Type the new bus number (for example: 3).The Host Channel to PE VPROC Assignments screen reappears with the new configuration.

manually assign a PE VPROC

a In the Host Channel to PE Vproc Assignments screen, type the following:v

The system prompts for the PE VPROC ID:Enter the PE vproc id to be assigned or q to quit (##/q)? >> 16378

b Type the PE VPROC ID (for example: 16378).The system prompts for the HGID number:Enter HGID to assign it to or q to quit (##/q)? >>1

c Type the HGID number (for example: 1).The system prompts for the node ID:Enter the Node ID to assign it to or q to quit (CCC-MM/q)? >>

d Type the node ID (for example: 001-05).The Host Channel to PE VPROC Assignments screen reappears with the new configuration.

Step Action




manually remove a PE VPROC

a In the Host Channel to PE Vproc Assignments screen, type the following:r

The system prompts for the PE VPROC ID:Enter the PE vproc id to be removed or q to quit (##/q)? >> 16378

b Type the PE VPROC ID (for example: 16378).The Host Channel to PE VPROC Assignments screen reappears with the new configuration.

2 If the Host Channel mappings are satisfactory, type the following to skip past the next RSG Vproc Mapping screen and continue with the Apply Changes screen:

j 8

Make sure to type a space between the j and the 8.

The Apply Changes screen appears.

Step Action


Chapter 6: pdeconfig Utility (NCR UNIX MP-RAS Only)Screen 7: Relay Services Gateway (RSG) TPA Mapping Summary

Screen 7: Relay Services Gateway (RSG) TPA Mapping Summary

The RSG Vproc Mapping examples are from an SMP system named dbsa.

The RSG TPA Mapping Summary screen is shown below:

RSG TPA MAPPING SUMMARY

Total 1 TPA nodes0 have RSG vprocs associated with them

e=Examine or modify TPA node mappingsc=Continue/h=Help/j=JumpEnter command (e/c/h/j)? >>e

The following options are available:

IF you want to … THEN in the …

examine the system configuration and display which RSG vprocs are mapped to which nodes

RSG TPA Mapping Summary screen, type the following:

e


RSG VPROCS to TERADATA NODE ASSIGNMENTS

No RSG vproc mapped to node 0(dbsa)

a=Add RSG vprocs/d=Delete RSG vprocs/m=Modify mapping


Enter command (a/d/m/c/h/j)? >>

In the RSG Vprocs to Teradata Node Assignments screen, you can do the following:

• Add an RSG vproc• Delete an RSG vproc• Modify mapping

add an RSG vproc RSG Vprocs to Teradata Node Assignments screen, type the following:

a

The following screen appears, showing that one RSG vproc, numbered 9215, has been added to the SMP node:


RSG vproc 9215 mapped to node 33(dbsa)



Enter command (a/d/m/c/h/j)? >>


Chapter 6: pdeconfig Utility (NCR UNIX MP-RAS Only)Screen 7: Relay Services Gateway (RSG) TPA Mapping Summary

delete an RSG vproc RSG Vprocs to Teradata Node Assignments screen, type the following:

d



No RSG vproc mapped to node 33(dbsa)



Enter command (a/d/m/c/h/j)? >>c

continue to the next screen

RSG Vprocs to Teradata Node Assignments screen, type the following:

c

The Apply Changes screen appears.

IF you want to … THEN in the …


Chapter 6: pdeconfig Utility (NCR UNIX MP-RAS Only)Screen 8: Apply Changes

Screen 8: Apply Changes

The Apply Changes screen allows you to apply all your requested configuration changes.

When you approve the changes, pdeconfig writes a new /ntos/vconfig.out file and saves the previous vconfig file in /ntos/vconfig.out.old.

The vconfig utility converts the ASCII /ntos/vconfig.out file to the binary vconfig.gdo (Globally Distributed Object), with extensive sanity checking.

The Apply Changes screen is shown below.

APPLY CHANGESNo changes have been made to the system so far.You can do one of the following: Apply the changes that you have specified. Jump back to the Main Menu.a=Apply changes/j=JumpEnter command (a/j)? >>a

In the Apply Changes screen, do the following:

Step Action

1 To apply the changes you have made to the configuration, type the following:

a

The system prompts you:

Are you sure you want to configure the system (y/n)? >>y

2 Type one of the following:

• To accept changes, type Y.• To cancel changes, type N.

On MPP systems, the system prompts if reassigning AMPs to specific nodes is acceptable. The following example appears only if one or more AMPs do not have a node assignment of -1:


pdeconfig will either reassign all AMP vprocs to specific nodes, or will leave all AMP vproc assignments as they are.

Can pdeconfig reassign all AMPs to specific nodes (y/n)?>>y

• For new systems, NCR recommends that you answer Y. • For existing systems, NCR recommends that you assign AMPs to specific nodes to improve fault-

tolerance.


Chapter 6: pdeconfig Utility (NCR UNIX MP-RAS Only)Screen 8: Apply Changes

3 On MPP systems, if any of the assignments violate the general rules of fault tolerance, pdeconfig displays a warning.

Note: The following example only appears if pdeconfig is not able to place one node per disk array.

WARNING: One or more Disk Arrays are accessed by more than one node. This is not a recommended mapping of AMP vprocs to nodes.

After pdeconfig completes this should be reviewed.

See the /ntos/config.info file for the AMP to vproc assignment details.

Press the Return key to continue...

4 To continue, press Enter.

The following message is displayed:


This may take a while . . .

Note: Configuring the system takes up to about two hours if you are configuring disk arrays.

Upon completion, the following message is displayed:

No errors reported during configuration.

Moving current /ntos/vconfig.out to /ntos/vconfig.out.old.


Running vconfig.

***vcf: Reading/Processing vconfig.out file***

vconfig.gdo successfully written

vconfig finished.

Generating configuration information file:

ntos/config.info

Restarting array monitor daemon(s) (amd)

System configuration completed

This completes configuring PDE.

Step Action


Chapter 6: pdeconfig Utility (NCR UNIX MP-RAS Only)Screen 9: Exit With No Changes to the System

Screen 9: Exit With No Changes to the System

The Exit with No Changes to the System screen allows you to exit pdeconfig without changing your system in any way. When you exit through this screen, your system will be exactly the same as it was before you started pdeconfig.

The Exit With No Changes to the System screen is shown below:



Exit the program without making any changes. Jump back to a previous screen.

e=Exit with no changes/j=JumpEnter command (e/j)? >>e


Chapter 6: pdeconfig Utility (NCR UNIX MP-RAS Only)Screen 9: Exit With No Changes to the System

To access the Exit With No Changes to the System screen, do the following:

Step Action

1 To jump from any numbered screen to the Exit With No Changes to the System screen, type the following:

J 9

Make sure to type a space between the J and the 9.



No changes have been made to the system so far.

You can do one of the following:

Exit the program without making any changes.

Jump back to a previous screen.

e=Exit with no changes/j=Jump

Enter command (e/j)? >>e

2 To exit pdeconfig, type the following:

e


Restarting Array Monitor Daemon(s) (amd)... this will take several minutes.

No changes to configuration were made.

pdeconfig gracefully closes down and returns you to the command prompt.


Chapter 6: pdeconfig Utility (NCR UNIX MP-RAS Only)Example Setup

Example Setup

The following example shows how to configure a four-node, two-clique MPP system. Also, the example is a useful guide for setting up an SMP system.

The example is broken up into the following tasks:

Task Description

1 “Task 1: Gathering System Information” on page 6-59.

2 “Task 2: Configuring the Disk Array” on page 6-61.

3 “Task 3: Configuring Disk Slicing” on page 6-63.

4 “Task 4: Mapping Pdisks” on page 6-65.

5 “Task 5: Mapping a LAN” on page 6-67.

6 “Task 6: Assigning Host Channels” on page 6-69.

7 “Task 7: Applying Changes” on page 6-71.


Chapter 6: pdeconfig Utility (NCR UNIX MP-RAS Only)Task 1: Gathering System Information

Task 1: Gathering System Information

To gather system information, do the following:

Step Action

1 On the PDN, enter the following:

# /sbin/pdeconfig

The following messages are displayed:

*****CONFIGURING SYSTEM DEFAULT_VCONFIG*****

Warning: The VPROCCONFIG GDO does not exist.

4 nodes read from /ntos/mpplist.

Requesting configuration information from all nodes.

This may take several minutes...

(about 5 minutes for this system)

This system consists of 4 node(s) and 2 clique(s).

2 Since no system name has been assigned, pdeconfig assigns the system name of DEFAULT_VCONFIG.

The file VPROCCONFIG.GDO is not yet present on the initial installation.

3 Since this is an MPP, pdeconfig looks at the list of nodes (/ntos/mpplist found on all nodes) that xmppconfig utility created.

4 Using the node names, pdeconfig queries each node for its configuration information.

pdeconfig finds all the nodes and recognizes two cliques. (No cliques exist on an SMP system.)

5 pdeconfig confirms that this system has never been configured before.


TPA SUMMARY

This system has not been configured for running a TPA.

All components are available for PDE Configuration.

Number of disk blocks per cylinder is 3872.

DEFAULT_VCONFIG currently consists of:

2 Clique(s)

4 Node(s)

e=Examine or modify system info


Enter command (e/c/h/j)? >>e


Chapter 6: pdeconfig Utility (NCR UNIX MP-RAS Only)Task 1: Gathering System Information

6 To set up the system name next, type the following:e


TPA DETAILED DISPLAY

System Name: DEFAULT_VCONFIG

Number of disk blocks per cylinder: 3872

Total vprocs: 0

State of vprocs:

The system has not been configured for running a TPA.

b=modify number of Blocks per cylinder/s=modify System name


Enter command (b/s/c/h/j)? >>s

7 To modify the system name, type the following:

s

The system prompts for the new system name:

Enter new system name: >>LRH

8 Type the new system name (for example: LRH).

Note: UNIX uses LRH (the system name for all MPP nodes) or the system name for the SMP node. The system name is different from the Host Name you assign later.


TPA DETAILED DISPLAY

System Name: LRH

Number of disk blocks per cylinder: 3872

Total vprocs: 0

State of vprocs:

The system has not been configured for running a TPA.

b=modify number of Blocks per cylinder/s=modify System name


Enter command (b/s/c/h/j)? >>c

Step Action


Chapter 6: pdeconfig Utility (NCR UNIX MP-RAS Only)Task 2: Configuring the Disk Array

Task 2: Configuring the Disk Array

To configure the disk array, do the following:

Step Action

1 In the TPA Detailed Display screen, type the following to continue:

c


DISK ARRAY SUMMARY


2 Cliques

16 Disk Array Ranks

Cliques with 2 nodes, 8 ranks are:

0 1

d=Default disk array setup for clique/e=Examine or modify disk array


Enter command (d/e/c/h/j)? >>d

The system has two cliques: 0 and 1. Each clique has 8 ranks. Each clique is accessed by two nodes.

The pdeconfig default can sense the array manufacturer, model, and size. From this information, the default setup decides how to set up the disk array configuration.

2 To select the default disk array setup, type the following:

d

The system prompts for the clique number.

Enter a clique number for default array setup, or q to quit (xx/q) >>0


Chapter 6: pdeconfig Utility (NCR UNIX MP-RAS Only)Task 2: Configuring the Disk Array

3 To enter the first clique, type the following:

0


DISK ARRAY SUMMARY


2 Cliques

16 Disk Array Ranks


0 1



Enter command (d/e/c/h/j)? >>d

Enter a clique number for default array setup, or q to quit (xx/q) >>1

pdeconfig prompts for the next clique number.

4 Type the following:

1


DISK ARRAY SUMMARY


2 Cliques

16 Disk Array Ranks


0 1



Enter command (d/e/c/h/j)? >>c

Note: In an MPP with more than two cliques, this Disk Array Summary screen repeats until all cliques have been configured.

All cliques are configured.

Step Action


Chapter 6: pdeconfig Utility (NCR UNIX MP-RAS Only)Task 3: Configuring Disk Slicing

Task 3: Configuring Disk Slicing

To configure disk slicing, do the following:

Step Action


c

The Disk Slicing Summary screen appears:



2 Cliques

64 Disks

Cliques with 2 nodes, 32 disks are:

0 1

d=Default disk slicing for clique/e=Examine or modify disk slicing for clique/

p=coPy disk slicing for clique


Enter command (d/e/p/c/h/j)? >>d


Chapter 6: pdeconfig Utility (NCR UNIX MP-RAS Only)Task 3: Configuring Disk Slicing

2 To select default disk slicing, type the following:

d

The system prompts for a clique number or range of clique numbers:

Enter a clique number or range of numbers, or q to quit (xx/xx-xx/q) >>0-1

3 For a range of clique numbers, type the following:

0-1


Finished setting up default slices on clique 0.

Finished setting up default slices on clique 1.

When pdeconfig finishes setting up the slices on all cliques, the following screen appears:



2 Cliques

64 Disks

Cliques with 2 nodes, 32 disks are:

0 1

d=Default disk slicing for clique/e=Examine or modify disk slicing for clique/

p=coPy disk slicing for clique


Enter command (d/e/p/c/h/j)? >>c

Step Action


Chapter 6: pdeconfig Utility (NCR UNIX MP-RAS Only)Task 4: Mapping Pdisks

Task 4: Mapping Pdisks

To map pdisks, do the following:

Step Action


c

pdeconfig maps the pdisks in the cliques:

PDISK MAPPINGS SUMMARY


2 Cliques

64 Disks

Cliques with 2 nodes, 0 pdisks are:

0 1

d=Default pdisk mappings for clique/

e=Examine or modify pdisk mappings for clique/p=coPy pdisk mappings for clique/


Enter command (d/e/p/c/h/j)? >>d

2 To select default mapping, type the following:

d

The system prompts for a clique number or range of clique numbers:

Enter a clique number or range of numbers, or q to quit (xx/xx-xx/q) >>0-1

3 Type the range of clique numbers (for example: 0-1).


Setting up default pdisk mappings on Clique 0 ...

There are 32 unassigned pdisks.

There are currently 0 AMP vprocs managing 0 pdisks.

Up to 32 AMP vprocs can be added, depending on the number of pdisks per vproc.

Enter number of AMP vprocs to add or q to quit (##/q)? >>8


Chapter 6: pdeconfig Utility (NCR UNIX MP-RAS Only)Task 4: Mapping Pdisks

4 Type the appropriate number of AMP vprocs to add (for example: 8).

Note: This number is a common choice. Be sure to follow the plan for the system you are installing. If you are in doubt, ask the TSC. This example uses eight vprocs to manage four pdisks per vproc (8 x 4 = 32 vprocs maximum).

Based on the number of AMP vprocs you chose, pdeconfig tells you how many pdisks you can assign to each AMP vproc. Then pdeconfig prompts for the number of pdisk per AMP vproc:

There can be up to 4 pdisks per AMP vproc.

Enter number of pdisks per AMP vproc or q to quit (##/q)? >>4

5 Type the number of pdisks per AMP vproc (for example: 4).

6 Perform steps 4 and 5 for Clique 1:

Setting up default pdisk mappings on Clique 1 ...

There are 32 unassigned pdisks.

There are currently 0 AMP vprocs managing 0 pdisks.

Up to 32 AMP vprocs can be added, depending on the number of pdisks per vproc

Enter number of AMP vprocs to add or q to quit (##/q)? >>8

There can be up to 4 pdisks per AMP vproc.

Enter number of pdisks per AMP vproc or q to quit (##/q)? >>4

The mappings continue until all cliques have pdisks mapped.


PDISK MAPPINGS SUMMARY


2 Cliques

64 Disks

Cliques with 2 nodes, 32 pdisks are:

0 1

d=Default pdisk mappings for clique/

e=Examine or modify pdisk mappings for clique/p=coPy pdisk mappings for clique/


Enter command (d/e/p/c/h/j)? >>c

Step Action


Chapter 6: pdeconfig Utility (NCR UNIX MP-RAS Only)Task 5: Mapping a LAN

Task 5: Mapping a LAN

To map a LAN, do the following:

Step Action


c


LAN SUMMARY

4 LANs, consisting of:

Unassigned LANs: 4

e=Examine or modify LAN mappings



2 To set up the LANs and PE vprocs, type the following:

e

The following screen appears, showing the LAN hardware on the system. Initially, the LANS are not assigned to PE vprocs.



---------------------

LANs: (00) node:863-01 bus:1 slot:3 kind:ETHERNET

description: WD EtherCard PLUS/A (WD8013EP/A)

(01) node:863-03 bus:1 slot:3 kind:ETHERNET






PE vprocs:

a=Add LAN/d=Default assign/l=LAN assign/m=Modify LAN/v=PE Vproc assign


Enter command (a/d/l/m/v/c/h/j)? >>d


Chapter 6: pdeconfig Utility (NCR UNIX MP-RAS Only)Task 5: Mapping a LAN

3 To select the default assignments, type the following:

d

The default choice assigns one PE vproc to each LAN. The following screen appears:



---------------------

LANs:

PE vprocs:

HGID 1

-------

LANs: (00) node:863-01 bus:1 slot:3 kind:ETHERNET








PE vprocs: 16383 16382 16381 16380

a=Add LAN/d=Default assign/l=LAN assign/m=Modify LAN/v=PE Vproc assign


Enter command (a/d/l/m/v/c/h/j)? >>c

Step Action


Chapter 6: pdeconfig Utility (NCR UNIX MP-RAS Only)Task 6: Assigning Host Channels

Task 6: Assigning Host Channels

To assign host channels, do the following:

Step Action


c

Note: If you do not have any Host Channels to connect to the system, select c again to continue.


HOST CHANNEL SUMMARY

0 Host Channels, consisting of:

HGID 0: 0 Host Channel(s) mapped to 4 PE vproc(s)

Unassigned Channels: 4

e=Examine or modify Host Channel mappings



2 To set up host channel mappings, type the following:

e


HOST CHANNEL TO PE VPROC ASSIGNMENTS


Channels: (00) node:863-01 bus:2 slot:2 port:0 kind:IBMMUX speed:4MB cua:0

(01) node:863-03 bus:2 slot:2 port:0 kind:IBMMUX speed:4MB cua:1



PE vprocs:


Channels:

PE vprocs: 16383 16382 16381 16380

a=Add chan/d=Default assign/m=Modify chan/n=chaN assign/v=PE Vproc assign


Enter command (a/d/m/n/v/c/h/j)? >>d


Chapter 6: pdeconfig Utility (NCR UNIX MP-RAS Only)Task 6: Assigning Host Channels

3 To assign the Host Channels to PE vprocs if you have a simple one-to-one assignment plan, type the following for the default:

d

Be sure to follow the plan for this system. If you are not sure about these assignments, ask for help from the TSC.

4 Use the n and v options in the Host Channels to PE Vproc Assignments screen to assign channels and vprocs.

5 After you finish assigning channels and vprocs, the assigned PE vprocs are listed with their assigned Host Group ID (HGID), Host Channel number (00, 01....), and Channel Unit Address (cua), as shown below.

PHOST CHANNEL TO PE VPROC ASSIGNMENTS


Channels:

PE vprocs:


Channels:

PE vprocs: 16383 16382 16381 16380

HGID 2


PE vprocs: 16379

HGID 3


PE vprocs: 16378

HGID 4


PE vprocs: 16377

HGID 5


PE vprocs: 16376

a=Add chan/d=Default assign/m=Modify chan/n=chaN assign/v=PE Vproc assign


Enter command (a/d/m/n/v/c/h/j)? >>j

Step Action


Chapter 6: pdeconfig Utility (NCR UNIX MP-RAS Only)Task 7: Applying Changes

Task 7: Applying Changes

To apply changes, do the following:

Step Action

1 To skip RSG vproc mapping and continue to the Apply Changes screen, type the following:

j 8

The Apply Changes screen appears:

APPLY CHANGES

No changes have been made to the system so far.

You can do one of the following:

Apply the changes that you have specified.

Jump to the Main Menu.

a=Apply changes/j=Jump

Enter command (a/j)? >>a

IF you want to . . . THEN type the following . . .

apply changes a.

make more changes n and go to the particular screen for those changes.

pdeconfig prompts whether you want to configure the system:


Note: You still have one more chance after this question to quit and avoid committing the changes.

2 To configure the system, type the following:

y



This may take a while...

pdeconfig compiles the configuration data from the selections you made.

pdeconfig prompts for the last time whether you want to configure the system:


This is your last chance to back out and avoid committing the changes. You can always come back later and run pdeconfig again. Doing this takes a lot of extra work to reconfigure the RDBMS. Double checking the selections and making sure this is the configuration you want is easier.



3 If you are sure you want these configuration selections, type the following:

y

pdeconfig assigns the AMP vprocs to specific nodes. Assigning an AMP vproc to a node commits the vproc to those certain physical disks that are cabled to the node.


pdeconfig either will reassign all AMP vprocs to specific nodes or leave all AMP vproc assignments as they are. pdeconfig prompts the following:

Can pdeconfig reassign all AMPs to specific nodes (y/n)? >>y

4 To allow pdeconfig to reassign all AMPs, type the following:

y

pdeconfig uses all your selections to write the vconfig.out file. The following message appears:


This may take a while...

Moving current /ntos/vconfig.out to /ntos/vconfig.out.old.


vconfig checks the configuration for obvious errors and returns error messages. You must correct the configuration errors by running pdeconfig again and fixing the selections.

Running /usr/ntos/bin/vconfig.

*****vcf: Reading/Processing vconfig.out file*****

vcf: warning: No BYNET lans were specified in vconfig.out

*****vcf: Consistency checking against existing vprocs *****

Error 2 accessing file: /ntos/vprocconfig.gdo

vcf: Could not read vprocconfig gdo....no consistency checking of vprocs was done.

vcf: Syntax error(s) or warning(s) reported above should be corrected before continuing. Otherwise, results are unpredictable

Do you wish to continue? (Y or N): y

Note: These warning messages might not be important to your configuration but are generated to encourage you to check your configuration. pdeconfig generates warnings if it sees the lack of BYNET LANs, channel assignments, or anything else pdeconfig thinks you should have. These messages appear even if you do not have the hardware that pdeconfig warns that you have not specified. MPP systems do not have to specify BYNET LANs, but pdeconfig warns you about not specifying them.

Step Action



5 To make corrections, type the following:

n

When you stop getting errors from vconfig, the configuration is good. The following prompt appears:

Can pdeconfig reassign all AMPs to specific nodes (y/n)? >>y

6 To reassign all AMPs, type the following:

y


vconfig.gdo successfully written

vconfig finished.

Distributing new vconfig gdo to all nodes.

Generating configuration information file: /ntos/config.info.

Running mktable... this may take several minutes.

Remote command DONE

Restarting Array Monitor Daemon(s) (amd).

System configuration completed.

pdeconfig closes.

Step Action


Chapter 6: pdeconfig Utility (NCR UNIX MP-RAS Only)6210 Disk Array Special Procedure

6210 Disk Array Special Procedure

The 6210 Disk Array is a small disk array that can be used with a 4300 SMP system and only can be configured in RAID 5. pdeconfig does not support the 6210. You must use the makeluns command to set up the 6210. Then run all the other steps of pdeconfig, except for the Disk Array screen. The procedure is as follows:

Step Action

1 Enter the following UNIX command:

/opt/adpxspt/makeluns -c device_name -x -r5 -l4 -d10,11,12,13,14 -d20,21,22,23,24

Substitute your 6210 device name into the command string for device_name. The -l4 option reads as "dash L four."

This creates four LUNs of equal size in a RAID 5 (4+1) configuration on the two internal channels.

2 Return to the beginning of this chapter and perform all the tasks except for Screen 2: Disk Array Summary.


Chapter 7:

Priority Scheduler

The Priority Scheduler is a resource management tool that oversees the dispersal of system resources based on a blueprint that you construct to satisfy your site-specific requirements. Priority Scheduler does the following:

• Keeps resource usage in your data warehouse balanced around your specific needs

• Offers flexibility for prioritizing users differently and specifying scheduling options

The Priority Scheduler controls the allocation and consumption of the computer resources available to the RDBMS. The Priority Scheduler controls resource allocation for RDBMS sessions based on the following:

• A session-related priority designation• The system-level priority strategy that you define

The Priority Scheduler is active in all Teradata systems. Teradata RDBMS itself automatically moves internal jobs into different priority levels, especially when a quick boost to one activity is critical to overall throughput.

The default state of Priority Scheduler assigns the same priority to the jobs of all users. You can take advantage of the capabilities of the Priority Scheduler by doing the following:

• Assigning different priorities to different types of jobs• Assigning jobs of favored users more CPU and faster I/O than the lower-

priority jobs

The first part of this chapter generally describes the structure and relationships of the scheduling components and parameters. The second part describes the following interfaces you can use to add and modify scheduling parameters:

• schmon - a command line interface. For detailed information, see “schmon Utility” on page 7-45.

• xschmon - a graphical user interface (GUI) using X-Windows (NCR UNIX MP-RAS only). For detailed information, see “xschmon Utility” on page 7-89.

• Priority Scheduler Administrator (PSA) - a Teradata Manager (TM) application. PSA provides an easy-to-use graphical interface to define Priority Scheduler configurations and to observe scheduler performance to Teradata Manager users. Unlike schmon, PSA does not require root privileges. For more information, see the PSA documentation.


Chapter 7: Priority Scheduler

In addition to these, the Priority Scheduler Simulator (PSS), a Microsoft Excel spreadsheet, allows you to generate “what-if” situations with different priority attributes. PSS allows you to emulate Priority Scheduler weighting configurations to determine expected relative weights for various activity situations.

To determine the actual allocation of CPU in real-world situations, you need to take into account 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.

For detailed instructions on the use of the Priority Scheduler Simulator, see the documentation, which includes a Microsoft PowerPoint presentation.

The Microsoft Excel spreadsheet (pss.xls) and Microsoft PowerPoint presentation (pss.ppt) are located in the /usr/ntos/etc directory on UNIX MP-RAS.

Appendix B: “Priority Scheduler Frequently Asked Questions (FAQ)” contains frequently asked questions and answers about Priority Scheduler.

Audience

Users of the Priority Scheduler include the following:

• Database administrators• System administrators• System programmers


Chapter 7: Priority SchedulerAbout Priority Scheduler

About Priority Scheduler

Priority Scheduler consists of the following three-tiered control structure to group user sessions for scheduling purposes:

• Resource partition• Performance group• Allocation group

Each of these components includes parameters that relate them to each other. You define and associate these components to design an environment that favors or inhibits the performance of individual sessions based on their logon account attributes.

Succeeding sections discuss the purpose of each of these components and its associated control parameters.

About Resource Partitions

A resource partition is composed of a set of performance groups that are related by their users’ associations. For more information, see “Resource Partitions” on page 7-9 and “Performance Groups” on page 7-13.

Each resource partition is assigned a weight that determines the proportion of resources available to that partition relative to the other partitions defined in the system. A resource partition can limit the amount of CPU used by sessions assigned to the performance groups that make up the resource partition by specifying a percentage limit. For more information, see “Determining the Relative Weight of a Resource Partition” on page 7-10 and “Limiting Resource Partition CPU Usage” on page 7-11.

About Performance Groups and Allocation Groups

A performance group is a collection of parameters used to control and prioritize resource allocation for a particular set of RDBMS sessions. Every RDBMS session is assigned to a performance group during the logon process. You might make the assignment explicitly by including a performance group name in the logon accountid string that matches the name of one of the performance groups defined by the Priority Scheduler parameters. Or, a default assignment might be made for you by the logon process.

A performance group defines from one to five performance periods.

Each performance period has a threshold or limit value that determines when sessions are under the control of the performance period. Also, each performance period links sessions controlled by the performance period to an allocation group that defines a scheduling strategy.


Chapter 7: Priority SchedulerAbout Priority Scheduler

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.


Chapter 7: Priority SchedulerOverview of Priority Scheduler Components

Overview of Priority Scheduler Components

The following figure shows the hierarchical structure of the Priority Scheduler.

FF07D421

ResourcePartition

PerformancePeriod

Milestone LimitAllocation Group

WeightCPU Limit

AllocationGroup

PolicyTypeWeight

1:1

1:M

1:M

Hierarchy of Components of One Resource Partition

1:M = one to many1:1 = one to one

PerformanceGroup

Milestone Type


Chapter 7: Priority SchedulerOverview of Priority Scheduler Components

The following table briefly summarizes the components of Priority Scheduler.

For detailed information on each component, see the following:

• “Resource Partitions” on page 7-9• “Performance Groups” on page 7-13• “Performance Periods” on page 7-19• “Allocation Groups” on page 7-23

To configure the Priority Scheduler, use either of these tools:

• “schmon Utility” on page 7-45 (command level interface)• “xschmon Utility” on page 7-89 (GUI interface)

Component Descriptions

Resource Partition • A resource partition is a collection of prioritized performance groups.

• A resource partition carries a weight that will be compared to other resource partition weights.

• A resource partition can limit the total amount of CPU used by sessions assigned to its performance groups.

• Priority Scheduler provides resource partition zero (0) as the default partition.

• You can define four additional resource partitions.

Performance Group • You define performance groups within each additional resource partition.

• The performance group name matches an entry in the column named AccountName in the USER record and in the accountid string in the logon statement and must be unique.

Performance Period • You must define at least one performance period, but you can have up to five performance periods per performance group.

• A performance period links a performance group to an allocation group.

• A performance period allows you to change allocation group assignments based on time-of-day or resource usage.

Allocation Group • An allocation group carries a weight that will be compared to other allocation group weights.

• An allocation group determines the scheduling policy and set division type.

• Several performance groups within a single resource partition might share the same allocation group.


Chapter 7: Priority SchedulerPriority Scheduler Default Settings

Priority Scheduler Default Settings

The following figure shows the Priority Scheduler default settings.

Scheduler Times & Attributes Age Time(sec): 60 Active Time(sec): 61 Limit(%): none Disp Age(sec): 0 Attrs: Active, Thruput, I/O Prio Resource Partitions (0 - 4)Id Partition Name Weight Limit 0 Default 100 none Performance Groups (0 - 39)Id Group Name RP Val Type Milestones & Allocation Groups[0-4] 0 L 0 0 S 0.00 1 1 low$ 0 1 S 0.00 1 2 M 0 2 S 0.00 2 3 med$ 0 3 S 0.00 2 4 H 0 4 S 0.00 3 5 high$ 0 5 S 0.00 3 6 R 0 6 S 0.00 4 7 rush$ 0 7 S 0.00 4 Allocation Groups (0 - 199) Id Type Pol Weight Id Type Pol Weight Id Type Pol Weight Id Type Pol Weight 1 N DEF 5 2 N DEF 10 3 N DEF 20 4 N DEF 40

AWT Expedited work type limits res max 0 999

You can expand or customize these settings to meet your desired level of granularity or degree of division for prioritizing computer resources in relation to the overall workload.


Chapter 7: Priority SchedulerUsing the Priority Scheduler

Using the Priority Scheduler

The Priority Scheduler can do the following for you:

• Provide better service for your more important work• Control resource sharing among different applications• Automate changes in priority by time of day or by amount of CPU used• Place a ceiling on system resources for specific applications

When using the Priority Scheduler, keep the following in mind:

• Start out simple, monitor, and build from there.• You can change parameters at any time using the schmon or xschmon

utility or the Priority Scheduler Administrator, a Teradata Manager application.

• If you use Priority Scheduler on UNIX MP-RAS, you must have UNIX root privileges to monitor and change parameters and settings.

• Any changes you make to any parameter, including weight, take place immediately across all nodes in the configuration.

• You cannot delete a resource partition, performance group, or allocation group. You can only remove these components by removing the /ntos/system.gdo from all TPA nodes and initiating an RDBMS restart to rebuild the system.gdo with the original defaults. Any user-defined elements will be lost and will need to be reconfigured with Priority Scheduler. Because of this limitation, NCR recommends that you script your customized Priority Scheduler user configuration, so that you can rebuild it easily.

• You can change the name of a defined but unused resource partition or performance group to make it obvious it is unused. For example, you might name the unused resource partition or performance group UNUSED or NULL.


Chapter 7: Priority SchedulerResource Partitions

Resource Partitions

Resource partitions divide the Teradata RDBMS users into groups based on some use or priority strategy, such as by subject area or type of work.

The Priority Scheduler provides you with a default resource partition named Default, but you can create up to four more resource partitions. The default resource partition has a partition weight of 100 and has four performance groups accessible by users.

The following table presents a logical view of partition 0.

The Teradata RDBMS uses performance groups in resource partition 0 for some internal system work, such as the following:

• Deadlock detection• File system utilities• Error logging• Session handling• System recovery

Note: To sustain a high priority for internal system work, NCR recommends that the weighting of default resource partition 0 should be higher than any other resource partition.

Resources are distributed to the RDBMS sessions that specify a performance group linked to a resource partition. The parameters associated with the performance groups and allocations groups of a resource partition control this resource allocation.

For detailed information, see the following:

• “Performance Groups” on page 7-13• “Allocation Groups” on page 7-23• “Scheduling Policy” on page 7-31

Performance group … Uses a scheduling policy of … And has a weight of …

L (low) DEFAULT 5.

M (medium) DEFAULT 10.

H (high) DEFAULT 20.

R (rush) DEFAULT 40.



Resource Partition Parameters

The following table briefly describes the parameters of a resource partition.

Determining the Relative Weight of a Resource Partition

Resource partition weight is a relative weight, since its value is relative to the weights of the currently active partitions. Dividing the weight of a partition by the sum of the weights of all active partitions gives the percentage of total system resources for that partition. This percentage is neither a guarantee or a limit on the amount of resource a partition will receive. This percentage is the proportion of resource the partition will receive relative to other partitions.

Suppose three resource partitions are active. Their respective weights are shown in the following table.

Parameter … Is …

ID a number between zero and four that identifies the resource partition.

Partition Name

a unique name for the resource partition. The name contains no more than 16 characters.

Weight a number that will be used to calculate a relative weight at execution time to determine the proportion of system resources the resource partition will receive.

Limit an optional number between 1 and 100, inclusive, that specifies a percentage limit on the total CPU usage by sessions assigned to the performance groups associated with the resource partition.

Resource partition … Has a weight of …

1 10.

2 20.

3 30.



To determine the relative weight of each partition, do the following:

Limiting Resource Partition CPU Usage

Optionally, you can limit a resource partition to a specified percentage of CPU resource usage. This CPU limit has no affect on the scheduling strategy defined by other Priority Scheduler parameters. The relative weights of allocation groups and resource partitions are observed. The normal distribution of resources prevails within the specified amount of CPU usage. Any other CPU resource limits defined by either an allocation group policy or a system CPU limit are observed.

Suggestions for Using Resource Partitions

The following sections are suggestions for using resource partitions.

Dividing Your Work into Equal Resource Partitions

Suppose the following:

• You have five resource partitions: RP0 through RP4. • You want to assign critical database administration work to RP0 to ensure it

a higher priority. • You have four equally important subject areas to which you want to give

equal priority.

You could define your resource partitions to be weighted similar to the following:

• RP0 = 100 • RP1 through RP4 = 25 each

Step Action

1 Add the individual respective weights of the active partitions (10 + 20 + 30) for a sum of 60.

2 Divide each respective weight (10, 20, and 30) by the sum of 60.

The relative weight for each partition is as follows:

• Partition 1 = .17• Partition 2 = .33• Partition 3 = .50

Note: The relative weights have been rounded up for ease of calculation.



Keeping Only High Priority Work in the Default Resource Partition

The following table shows one method of dividing your work based on its importance.

The following table shows an example of this approach.

Step Action

1 Group applications by the importance of the work.

2 Leave all high-priority work in the default resource partition.

3 Move other, less important work into other resource partitions.

Resource Partition … Has a weight of … And is used for …

0 100 very short, fast turn-around queries.

1 25 complex queries.

2 10 batch jobs and reports.


Chapter 7: Priority SchedulerPerformance Groups

Performance Groups

The logon process assigns each user session to a performance group based on the accountid string of the logon command. If a performance group cannot be assigned based on the accountid string, a default assignment is made.

Performance groups are ordered within their resource partition based on their performance group value parameter. Teradata RDBMS recognizes this order during session logon to permit a session to be assigned to a performance group with a lower priority than the authorization of a user specifies.

Performance Groups and Allocation Groups

A performance group selects one of a set of performance periods and an associated allocation group, for a session based on session resource use or the time of day. The associated allocation group parameters control resource allocation for the session.

The parameters of an allocation group establish the proportion of resources available to sessions. The availability of more or less resources affects the performance of the session relative to sessions controlled by other allocation groups, thereby providing more or less priority for sessions.

The following table briefly describes the parameters used to define a performance group.


Performance Group ID a number between 0 and 39.

Performance Group Name the name of the performance group that allows it to be assigned to a session. For more information, see “Performance Group Name” on page 7-15.

Resource Partition ID a number between zero and four inclusive that identifies the resource partition owning the performance group. For more information, see “Resource Partitions” on page 7-9.

Performance Group Value a number between 0 and 7 inclusive that designates the relative priority of a performance group within the resource partition. For more information, see “Performance Group Value” on page 7-17.


Chapter 7: Priority SchedulerPerformance Groups

You can define a maximum of 40 performance groups. Priority Scheduler provides eight performance groups by default, which have performance group IDs of 0 through 7. These performance groups belong to the default resource partition 0. You can define as many as eight performance groups for each additional resource partition.

Performance Group and Weight Defaults for Resource Partition 0

The following table lists the default performance groups and their associated allocation group weights for the default resource partition 0. As shown in the table, each default performance group doubles the relative weight assigned to the previous lower-valued performance group.

Performance Period Type a code that indicates the type of milestone limits used to define performance periods. All performance periods of a performance group will be the same type. For more information, see “Performance Period Types and Limits” on page 7-21.

Performance Periods from one to five performance period specifications. Each period is defined by a milestone limit and an allocation group identifier.

You can express milestone limits in the following units:

• Time-of-day• Session resource usage• Query resource usage

Default performance group … Has a performance group value of … And a default weight of …

L 0 5.

M 2 10.

H 4 20.

R 6 40.



Chapter 7: Priority SchedulerPerformance Group Name

Performance Group Name

All performance group names must be unique and no longer than 16 characters. To add clarity to the name of your performance groups, name them in a manner similar to the resource partition name.

Because the 30-character AccountName column in the USER record includes performance group names, NCR recommends creating short ones. For example, you might name performance groups belonging to the second resource partition (resource partition 1) as follows:

• L1• M1• H1• R1

If you specify an invalid or no performance group name in your session logon command, then the session is assigned to the first AccountName string performance group in your USER record. If you do not have a USER record AccountName string with a performance group name, the session defaults to the default performance group (M). As session requests are processed, the respective performance group and allocation group parameters control the resource allocation for the processes performing work for the requests.

Recording the Performance Group Name in a User Record

When you authorize a user to use a performance group with the CREATE USER or MODIFY USER command, you record the performance group name in the accountid string of the USER record for that user. The performance group name portion of an accountid string in a USER record consists of the following:

• A leading $ character• A performance group name• A terminating $ character

The following example shows both user-defined and default performance group names that might appear in the AccountName column of a USER record:

'$L1$','$L$','$M2$','$M$'

In the example above, a beginning and ending single quote mark and a beginning and ending $ character surround each performance group name. A comma separates the performance group names from each other.

Note: The Teradata RDBMS enforces other rules for the length and format of accountid strings and influences the choice of performance group names.


Chapter 7: Priority SchedulerPerformance Group Name

Alternative Formatting for Default Resource Partition 0 Performance Group Names

In earlier RDBMS versions, a single character (L, M, H, or R) prefixed by the $ character in the accountid string indicated the performance group (priority in V1 systems) of a session.

To provide backward compatibility, Priority Scheduler provides each of these single character identifiers as a performance group name within default resource partition 0.

In this special case, the four performance group names (L, M, H, and R) do not require an ending $ character in the accountid string. In this case, the strings $M and $M$ are equivalent.

The following user-defined and default performance group names might appear in the AccountName column of a USER record:

'$L1$','$H3$','$H','$R3$','$R'

Note: Although both of the syntax ($M and $M$) yield equivalent performance group names, the accountid strings are not equivalent. The accountid strings might give different results when used for resource accounting purposes (as opposed to priority scheduling).

Associating a Performance Group Name to a User

The following is an example of how to associate a performance group name to a user. In this example, both low and medium priorities within resource partition 1 are assigned to user ITBATCH.

modify user ITBATCH as account=('$L1$','$M2$')

Supplying Performance Group Names During an RDBMS Session Logon

You might supply a performance group name during an RDBMS session logon to assign the session to a performance group. This performance group name must be in your USER record AccountName column. If no performance group name is supplied at logon, the first performance group name in the AccountName column is used.

The following example shows a user-defined performance group other than the default:

.logon testdb/itbatch, cab,'$M2$'


Chapter 7: Priority SchedulerPerformance Group Value

Performance Group Value

Each performance group is assigned a value that defines its relative importance within the resource partition. The Teradata RDBMS internally references these performance group values of 0 to 7 to identify a performance group with a higher or lower relative importance.

Performance Group Values in Default Resource Partition 0

The following table gives the performance group names, their usage, and the values for the default resource partition 0. The table indicates the correspondence between the traditional accountid priority strings (L, M, H, and R) and their performance group values.

After the logon process creates a session, processes are invoked to respond to requests entered during the session. These processes are assigned to the performance group declared during logon. The associated allocation group parameters control the resource allocation to these processes. This assignment accompanies all processes performing work for the session for the duration of the work process.

Note: A process refers to a single unit of Teradata work, such as one step in a query plan. A single query might have more than one process active on a node at the same time.

Example

Suppose that a logon specifies H2 as its priority, and the performance group named H2 belongs to a resource partition with the definitions shown in the following table.

Performance group name … Has a value of … And a usage of …

L 0 low priority.

low$ 1 internal Teradata RDBMS priority.

M 2 medium priority.

med$ 3 internal Teradata RDBMS priority.

H 4 high priority.

high$ 5 internal Teradata RDBMS priority.

R 6 rush priority.

rush$ 7 internal Teradata RDBMS priority.


Chapter 7: Priority SchedulerPerformance Group Value

In this case, H2 corresponds to the high-priority performance group of a non-default resource partition, which might be named Adhoc.

The Teradata RDBMS assigns a performance group value of four to the work requests for most of the work for this session. However, sometimes when the work requires relatively higher priority, Teradata RDBMS increments the basic value by one, assigning the work to a performance group whose value is five.

Performance group name … Has a value of … And a usage of …

L2 0 low priority.

L2$ 1 internal Teradata RDBMS priority.

M2 2 medium priority.

M2$ 3 internal Teradata RDBMS priority.

H2 4 high priority.

H2$ 5 internal Teradata RDBMS priority.

R2 6 rush priority.

R2$ 7 internal Teradata RDBMS priority.


Chapter 7: Priority SchedulerPerformance Periods

Performance Periods

Each session has a designated performance group. When a session begins a process, it falls under the control of a performance period whose milestone limit conditions are met. A performance period associates processes assigned to the performance group to an allocation group, thereby controlling the scheduling policies and weights used for resource allocation at that point in time. A process might fall under the control of several performance periods in the course of its activities as its resource usage or the time-of-day advances through the milestone limits.

Often performance groups, such as those in default resource partition 0, have a fixed association to one and only one allocation group. Under these conditions, only a single performance period is defined for the performance group. This performance period acts as a link from the performance group to the allocation group.

Each performance group specifies one milestone type parameter that indicates the units used for its performance period milestone limits.

Each performance period has a milestone limit and an allocation group identifier. These performance period parameters define when the performance period is to control a session and how resources are to be allocated to the session.


Chapter 7: Priority SchedulerPerformance Periods

Performance Period Components

The following table describes the components of a performance period.

The following sections describe milestone limits and allocation groups.

Component … Defines the …

Milestone Type type of threshold used to define each performance period for a performance group. You can express types in the following units:

• Time-of-day (T)• Session resource usage (S or R)• Query resource usage (Q)

For more information, see “Performance Period Types and Limits” on page 7-21.

Milestone Limit value of the threshold used to change performance periods for a performance group. You can express this value in the following units:

• A valid time-of-day, such as 0800 for 8:00 A.M.• A number of seconds of CPU usage.


Allocation Group number of the allocation group used to control sessions during this performance period.

For more information, see “Allocation Groups” on page 7-23.


Chapter 7: Priority SchedulerPerformance Period Types and Limits

Performance Period Types and Limits

A performance period type defines a type of threshold used to change performance periods for a performance group. The milestone limit represents that threshold. The milestone limit triggers an automatic change in allocation group when a threshold you define is reached.

You can express milestone limits in the following units:

• Time-of-day• Session resource usage• Query resource usage

The following table shows the relationship between performance period types and milestone limits.

Since each performance period has an allocation group that defines a scheduling policy and weight used to allocate resources for the processes, process resource allocation can vary as the milestone limits are reached. For more information, see “Allocation Groups” on page 7-23.

Time-of-day

When you express milestone limits in units of time-of-day, the respective performance period and its associated allocation group control every process assigned to the performance group, up until the time specified in that performance period.

The actual time-of-day selected for the performance periods represents an upper limit of time. When this threshold is passed, the performance period with the next higher time-of-day and its associated allocation group take control. This performance period will change as the day proceeds through the 24-hour cycle. When the last-specified performance period expires, the first performance period and its allocation group take control of the processes assigned to the performance group.

When performance period type is … Milestone limits are specified in …

Time-of-day minutes of military time and represent time periods during a 24-hour day. For example, 0800 is 8:00 A.M.

Session resource usage seconds and define an amount of session CPU resource consumption per node. For example, 300.

Query resource usage seconds and define an amount of query CPU resource consumption per node. For example, 10.


Chapter 7: Priority SchedulerPerformance Period Types and Limits

Suppose you rely on a window of time at night to perform batch work. To keep your query users from interfering with night work without shutting them out completely, do the following:

At the same time, you can increase the weighting of any batch work. Suppose you raise the assigned weight of the batch work performance group from 5 to 30 between 11:00 p.m. and 8:00 a.m. In doing so, you have helped the important batch work to finish, even if users issue queries after hours.

Resource Usage

When you express milestone limits in units of session or query resource usage, their values indicate the total resource usage of all processes working on behalf of a session, or a query submitted by a session, on that node. In this case, a performance period controls processes grouped into sessions. Since some sessions or queries might consume more or less resources than others, several performance periods of a performance group might be actively controlling processes of different sessions concurrently.

The selected resource usage value is an upper limit. When a given session, or a query submitted by a session, reaches that limit, the performance period with the next higher resource usage limit and its associate allocation group take control. With multiple performance periods, the final performance period should specify zero (0) as the resource usage limit.

When more than one performance period is defined for a performance group, processes are controlled by successive performance periods as the total session or query resource consumption increases beyond each milestone limit.

Since each performance period has an allocation group that defines a scheduling policy and weight used to allocate resources for the processes, process resource allocation can vary as the milestone limits are reached. For more information, see “Allocation Groups” on page 7-23.

The following command defines a performance group with two performance periods. When a session logs on, all of its processes are under the control of allocation group 9 until 100 seconds of CPU are used on that node. At that time, allocation group 33 controls the session for the remainder of its life.

schmon -p 10 H1 1 2 R 100 9 0 33

Note: The time to accumulate 100 seconds of CPU time might be different than 100 seconds of clock time.

Step Action

1 Between 8:00 a.m. and 5:00 p.m., give the query users an assigned weight of 20.

2 Between 5:00 p.m. and 11:00 p.m., reduce the assigned weight to 10.

3 Between 11:00 p.m. and 8:00 a.m., further reduce the assigned weight to 5.


Chapter 7: Priority SchedulerAllocation Groups

Allocation Groups

An allocation group establishes how resources are allocated to processes. It defines the following:

• A method for disbursing resources among sessions active within that allocation group

• An attribute that optionally expedites work requests for sessions controlled by the allocation group

• A weight• A scheduling policy

In a single resource partition, multiple performance periods or their associated performance groups can reference the same allocation group, as shown in the following figure.

1102E423

PerformanceGroup M1

One Resource Partition

PerformanceGroup L1

PerformancePeriod

PerformancePeriod

PerformancePeriod

PerformancePeriod

AllocationGroup 7

AllocationGroup 6

AllocationGroup 5


Chapter 7: Priority SchedulerAllocation Groups

An allocation group cannot be referenced by performance groups from more than one resource partition.

Allocation Group Parameters

The following table describes the parameters of an allocation group.

For more information, see the following:

• “Set Division Type” on page 7-25• “Expedite Attribute” on page 7-26• “Allocation Group Weight” on page 7-27• “Scheduling Policy” on page 7-31

Associating Allocation Groups to Performance Groups

The following suggestions might help you associate allocation groups to performance groups:

• Use the default partition 0 as a template.• Associate allocation groups so that their weights increase in the same

direction that the performance group value increases.– Associate a performance group with a value of zero to the allocation

group with the lowest weight.– Associate performance groups with values of six and seven to the

allocation group with the highest weight.• Avoid extreme differences between weights.

Parameter Description

Set Division Type Defines how resources are disbursed to the processes controlled by the allocation group.

Expedite Attribute Indicates that work requests are to be expedited through the AWT invocation procedures.

Allocation Group Weight Is a numeric value used to compute the proportion of resources each process should receive.

Allocation Group ID Is any number from 0 to 199 inclusive.

Scheduling Policy Determines how the weight of the allocation group is applied to control the resource allocation of individual processes.


Chapter 7: Priority SchedulerSet Division Type

Set Division Type

The set division type parameter of an allocation group defines how resources are disbursed to the processes controlled by the allocation group. The set division type parameter causes processes to be grouped into a scheduling set in one of two possible ways. The resources of the allocation group are divided among these scheduling sets according to the set division type described in the following table.

Type … Determines that set division type can specify …

None only one scheduling set for the allocation group.

All processes controlled by the allocation group belong to this scheduling set. The resources of the allocation group are divided equally among them.

In this case, a session with a multi-AMP request that has invoked several processes (one process per AMP) receives the same resource per process as a single-AMP request with one process. With this type of set division, the multi-AMP request receives more resources than the single-AMP request.

This parameter favors sessions that perform complex, multi-AMP queries.

Session one scheduling set per session.

The resources of the allocation group are divided equally among the sessions that have processes controlled by the allocation group.

In this case, a session with a multi-AMP request receives the same resources as a session with a single-AMP request. The resources available for the multi-AMP request are divided among the processes associated with it. The same amount of resources available for the single-AMP request are given to the single process associated with the single AMP.

This parameter favors single-AMP queries over queries that require multiple AMPs.


Chapter 7: Priority SchedulerExpedite Attribute

Expedite Attribute

You can specify an Expedite Attribute for an allocation group to indicate that work requests for sessions controlled by the allocation group are to be expedited through the AMP work task (AWT) invocation procedures. Work requests controlled by the allocation group are favored over non-expedited work requests controlled by other allocation groups during the invocation procedure in two ways:

• Expedited work requests receive increased priority in the work request input queue. They bypass normal work requests in the input queue and have quicker access to an AWT.

• Expedited work requests have access to a pool of reserved AWTs that have been dedicated for this expedited work by the system administrator.

Caution: NCR recommends that only allocation groups supporting short, response-sensitive work, such as single-AMP operations, be expedited. Work performed in this mode will have some impact on resources available to non-expedited work. Use this option judiciously.

For more information on reserved AWT pool, see “AMP Work Task (AWT) Reservations and Limits” on page 7-39.


Chapter 7: Priority SchedulerAllocation Group Weight

Allocation Group Weight

Allocation group weights are values used to compute the proportion of resources each process should receive. The allocation group scheduling policy determines the interpretation of the weight value. You can use this value when calculating relative weight. Also, under the ABSOLUTE and RELATIVE policies, you can interpret this value as percent of CPU. For more information, see “Scheduling Policy” on page 7-31.

The relative weight of an allocation group is the ratio of its weight divided by the sum of the weights of all active allocation groups within the same resource partition multiplied by the relative weight of the resource partition. This relative weight is used to determine the portion of resources that the allocation group should receive.

Determining Allocation Group Relative Weight

Suppose each performance group of a resource partition is linked to one allocation group. The weights of these allocation groups are as follows:

• Allocation Group 1 = 5• Allocation Group 2 = 10• Allocation Group 3 = 20• Allocation Group 4 = 40

Suppose that only allocation groups 1, 2, and 3 are active.

To determine the weight for each of these active allocation groups, do the following:



The following example shows how Priority Scheduler handles resource partitions and associated performance groups.

Suppose you have three active resource partitions with the following weightings:

• Marketing = 30• Scheduling = 35• Customer Service = 50

The Customer Service resource partition consists of the following:

Step Action

1 Add the individual respective weights of the three active performance groups (5 + 10 + 20) for a sum of 35.

2 Divide the weight (5, 10, and 20) of each performance group by the sum of 35.

The relative weight for each allocation group, relative to its resource partition, is as follows:

• Allocation Group 1 = .14 (5/35)• Allocation Group 2 = .29 (10/35)• Allocation Group 3 = .57 (20/35)

3 If the relative weight of the resource partition is .50, multiply the relative weight for each allocation group by .50 to determine the relative weight for each allocation group.

The final allocation group weights are as follows:

• Allocation Group 1 = .07 (.14 x .50)• Allocation Group 2 = .15 (.29 x .50)• Allocation Group 3 = .29 (.29 x .50)

Performance group … Has an allocation group weight of … And the user is …

L3 5 batch jobs.

M3 10 regular clerks.

H3 20 premium member clerks.

R3 50 complaint clerks.



To determine the resources allocated to regular clerks, do the following:

Number of Active Users Assigned to an Allocation Group Affects Query Response Time

The consistency of response times within a given allocation group depends on the following:

• The number of users active at the same time• The nature of the queries (such as data skew, complexity of the work

submitted, and how long the queries take to complete.)

The average query response time grows as active users in the same allocation group increase.

Step Action

1 Sum the assigned weights of all active resource partitions:

30 + 35 + 50 = 115

2 Find the percentage of resources allocated to the Customer Service resource partition by dividing the weight of the Customer Service resource partition (50) by the sum of the active resource partitions (115):

50/115 = .43

3 Sum the assigned weights (5, 10, 20, and 50) of the active allocation groups within the Customer Service resource partition:

5 + 10 + 20 + 50 = 85

4 Find the percentage of the Customer Service resource partition allocation that the regular clerk users can expect by dividing the M3 group weight (10) by the sum of the active performance groups (85):

10/85 = .12

5 Multiply the percentage of resources (.43) allocated to the Customer Service resource partition by the percentage (.12) of the Customer Service resource partition allocation that the regular clerks can expect:

.43 x .12 = .05

With all resource partitions and all performance groups in the system active, the relative weight of the allocation group for regular clerks is .05. The relative weight of the allocation group for complaint clerks is .10. In this example, the complaint clerks will have twice as much access to resources as the regular clerks.



The following table shows how the number of users in performance group H (and its associated allocation group) affects query response time of all queries in that allocation group.

IF the number of active users in a performance group/allocation group pair is …

THEN the average query response time might be …

1 7 seconds.

5 11 seconds.

10 19 seconds.

20 38 seconds.


Chapter 7: Priority SchedulerScheduling Policy

Scheduling Policy

Each allocation group uses a scheduling policy that determines how the weight of the allocation group is applied to control the resource allocation of individual processes. The scheduling policies include the following:

• DEFAULT• IMMEDIATE• ABSOLUTE• RELATIVE

Each scheduling policy type interprets resource consumption and allocation group weight to determine how much access individual processes should have to the CPU resources. By controlling this access, these processes control how long work takes to complete.

A scheduling policy only dictates the behavior of the allocation group to which the scheduling policy is assigned. Other allocation groups fall under the control of their individual scheduling policies.

To provide this control, the Priority Scheduler compares the resource consumption of sessions controlled by the allocation group against the resource allocation specified by the weight of the allocation group. When a process consumes less than its share of the allocation, the scheduling policy gives that process more access to resources. When a process consumes more than its share of the allocation, the scheduling policy gives that process less access to resources.



The following table describes the four scheduling policies in detail.

Schedulingpolicy

Group weight Description

DEFAULT Treated as a relative weight.

The DEFAULT scheduling policy considers the following:

• Resource consumption of all processes assigned to the allocation group

• Resource consumption of each individual process

By considering both group and process consumption, individual processes that have lagged behind in consumption are given more access to resources, and individual processes that have overconsumed resources are given less access.

A graph of the consumption by the group over time is a saw tooth curve, with high and low peaks contributed by individual processes. The average value of the curve matches the weight value.

IMMEDIATE Treated as a relative weight.

The IMMEDIATE scheduling policy only considers the sum of the resource consumption of all processes assigned to the allocation group. The IMMEDIATE scheduling policy does not evaluate each individual process or seek to adjust over or under consumers at the individual process level.

A graph of the consumption by the group over time is a smooth line, with little fluctuation from the weight value.



ABSOLUTE Treated as a relative weight (similar to the DEFAULT scheduling policy) up until resource usage reaches the absolute percentage specified by this weight. At that point, group weight is treated as an absolute percentage of total system resources to limit the CPU usage by processes controlled by the allocation group.

The ABSOLUTE scheduling policy considers the following:


• Resource consumption of each individual process, as it is scheduled, when comparing consumption against allocation

If the processes belonging to the group cannot use all the available resources, the unused resources are available for use by other allocation groups.

This policy limits the set of processes under its control to an absolute limit or percentage of the system CPU resources. Processes are forced to wait to enforce this policy, and that wait period can cause idle system time.

You might want to use the ABSOLUTE scheduling policy to make sure that a category of low priority work never receives more than 5% of the system resources.

Note: Use the ABSOLUTE policy carefully, since it might create a situation where system resources remain unused.

RELATIVE Treated as a relative weight (similar to the DEFAULT scheduling policy) up until resource usage reaches the percentage specified by this relative weight. At that point, group relative weight is treated as an absolute percentage of total system resources to limit CPU usage by processes controlled by the allocation group.

The RELATIVE scheduling policy considers the following:


• Resource consumption of each individual process, as it is scheduled, when comparing consumption against allocation

This policy limits the set of processes under its control to a percentage of the resources as defined by the relative weight. Processes are forced to wait to enforce this policy, and that wait period can cause idle system time.

The ceiling imposed by the RELATIVE policy can be different, depending upon the number of other resource partitions or allocation groups that are active. When few resource partitions and/or allocation groups are active, the RELATIVE scheduling policy provides a higher ceiling. When more resource partitions and/or allocation groups are active, the RELATIVE scheduling policy provides a lower ceiling.

If the processes belonging to the group cannot use all the available resources, other policies can use the unused resources.

Schedulingpolicy

Group weight Description



Using Scheduling Policies

You might use scheduling policies when you have the following scenarios:

• A group of users you want to keep at a low resource usage even when the system has idle CPU and I/O

• To introduce greater response time consistency into a Teradata application and when users might otherwise experience fluctuation in their query turnaround times

The DEFAULT and IMMEDIATE scheduling policies are not restrictive. Unused resources are distributed to other allocation groups based on the relative weights. The Priority Scheduler prioritizes the work under these policies to use as many resources as available, based on relative weightings.

The following table shows how the ABSOLUTE and RELATIVE policies restrict the level of system resources a performance group can use.

When Priority Scheduler uses the ABSOLUTE or RELATIVE policy to give an allocation group a fixed limit on resources, the unused resources are divided among the remaining allocation groups according to their weights and policies.

Allocating Resources Using the ABSOLUTE Scheduling Policy

The ABSOLUTE scheduling policy sets a fixed upper limit on resource usage. In the following table, you have a resource partition in which performance group L has an ABSOLUTE scheduling policy, and performance groups H and R have the DEFAULT scheduling policy.

In this case, M receives four times as much and H receives eight times as much access to resources as L receives. Only L, M, and H are active.

The policy … Sets a cap on group usage based on …

ABSOLUTE an absolute percentage of system resources.

ABSOLUTE is the only policy where the weighting number represents a percentage of total system resources.

RELATIVE the calculated relative weight of the resource partition performance group weights.

Allocation group … Has a scheduling policy of … And allocation group weight of …

L ABSOLUTE 5

M DEFAULT 20

H DEFAULT 40

R DEFAULT 60



To find the relative weight of each active allocation group, do the following:

Then the following applies:

When the workload is so heavy that all three performance groups can consume as much CPU resources as possible, CPU usage is divided as follows:

• L = 5%• M = 31% (.33 x 95%)• H = 63% (.66 x 95%)

Step Action

1 Sum the weights of active allocation groups L, M, and H:

5 + 20 + 40 = 65

2 Divide the weight of each active allocation group by the sum of all active allocation group weights:

• 5/65 = .08 (L)• 20/65 = .30 (M)• 40/65 = .62 (H)

IF the workload of L is … THEN the …

less than 5% of the CPU resources

relative weight of .08 determines the portion of CPU resources allocated to L, relative to the other active performance groups, until the CPU resource consumption by L reaches its specified 5% limit.

5% of the CPU resources

other active performance groups divide the remaining 95% of the CPU resource in proportion to their relative weights:

• M = 29% (.30 x 95%)• H = 59% (.62 x 95%)



Allocating Resources Using the RELATIVE Scheduling Policy

The RELATIVE scheduling policy allocation ceiling depends on other active performance groups.

The following table shows a resource partition in which M has an RELATIVE scheduling policy, and L, H, and R have DEFAULT scheduling policies.

To determine the limit on CPU resource for M when M, H, and R performance groups are active, do the following:

To determine the targeted allocation of resources for M when only performance groups M and H are active, do the following:

Performance group … Has a scheduling policy of … And allocation group weight of …

L DEFAULT 5.

M RELATIVE 10.

H DEFAULT 20.

R DEFAULT 40.

Step Action

1 Sum the allocation weights of all active performance groups:

10 + 20 + 40 = 70

2 Find the percentage of resources allocated to the M performance group by dividing the allocation group weight of M (10) by the sum of all allocation group weights (70):

10/70 = .14

M will never receive more than 14% of the CPU resource. If H and R performance groups cannot consume 86% of the CPU resource, idle time will occur.

Step Action

1 Sum the allocation weights of performance groups M and H:

10 + 20 = 30

2 Find the percentage of resources allocated to the M performance group by dividing the allocation group weight of M (10) by the sum of all allocation group weights (30):

10/30 = .33

M will never receive more than 33% of the CPU resource. If the H performance group cannot consume 66% of the CPU resource, idle time will occur.


Chapter 7: Priority SchedulerResource Accounting

Resource Accounting

The Priority Scheduler measures resource consumption for each allocation group to ensure compliance with its scheduling policy and weight. This resource consumption is the amount of resources used by each scheduling set during a specified period of time known as Set Age Time.

The Priority Scheduler monitors allocation group activity. The Priority Scheduler removes from its calculations those groups that have had no processes running during a recent period of time known as Set Active Time.

The Priority Scheduler provides a method to limit the total CPU resource used by the Teradata RDBMS.

The Priority Scheduler includes the facilities to prioritize FSG subsystem I/O requests in managed queues. On Microsoft Windows 2000, this facility is known as I/O Concurrency Level.

The following sections describe Set Age Time, Set Active Time, I/O Concurrency Level, and System CPU Usage Limit.

Set Age Time

The default value for Set Age Time is 60 seconds. Decreasing or increasing Set Age Time makes the Priority Scheduler more or less responsive to changes in resource usage. This responsiveness affects the frequency and degree of changes 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 Set Age Time does not affect query response time. You should monitor adjustments in Set Age Time carefully to judge their effects on system performance.

Set Active Time

The default value for Set Active Time is 61 seconds. During this period, an allocation group retains a record of its resource consumption when no processes are active in anticipation of a new process being associated with the allocation group.

During this period, the allocation group weight continues to influence 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 Set Active Time period, the allocation group is considered


Chapter 7: Priority SchedulerResource Accounting

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. You should monitor adjustments to Set Active Time carefully to judge their effect on system performance.

I/O Concurrency Level (Windows 2000 Only)

The Priority Scheduler includes the following facilities to prioritize FSG subsystem I/O requests in managed queues. On Windows 2000, you can control the number of active concurrent I/O requests by using the Priority Scheduler parameter known as the I/O concurrency counter. You can adjust this parameter using the schmon utility -t command. The I/O queue is managed on a vproc level. The default concurrency counter setting is 10. For more information, see “schmon Utility” on page 7-45.

Note: On UNIX MP-RAS, the I/O queue is integrated into the UNIX MP-RAS I/O subsystem. You can adjust the number of active concurrent requests by using the I/O subsystem parameters.

System CPU Usage Limit

You can use an optional Priority Scheduler parameter to limit the total amount of CPU resources used by the Teradata RDBMS sessions under its control. This 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 applied separately on each individual node of the system


Chapter 7: Priority SchedulerAMP Work Task (AWT) Reservations and Limits

AMP Work Task (AWT) Reservations and Limits

AWTs are processes (threads on some platforms) dedicated to servicing Teradata RDBMS work requests. A fixed number of AWTs are pre-allocated during system initialization for this purpose for each AMP vproc. Each AWT looks for a work request to arrive in the system, services the request, and then looks for another. An AWT can process requests of any work type.

Each Teradata RDBMS query is composed of a series of work requests that are performed by AWTs. Each work request is assigned a work type that indicates when the request should be executed relative to other work requests that are waiting to execute. Work types include the following:

• New work• Spawned work• Transaction completion and control requests

New work is the lowest in importance.

A single query might require different types of work requests to reach completion.

AWT Resource Allocation

Since the number of AWTs is fixed, when all AWTs are busy and none are available to service new arriving requests, these are placed in an input queue. When an AWT completes a request for service and is available to service another, the queued work requests are removed from the input queue and serviced.

An AWT resource manager controls the number of active requests for each AMP vproc based on request work type. The resource manager reserves tasks for each work type to insure that requests for each work type can be processed when necessary. For example, an ongoing query might spawn additional tasks of a different work type part way to completion. A deadlock condition can result if reserve tasks of this new work type are unavailable.

The resource manager allows a task to process a request of a particular work type if one of the following conditions is met:

• The number of active tasks of that type is below its reserved number.• The total number of active tasks is less than a Current Limit.

where:

Current Limit = # of AWTs - (Total Reserved - Active Reserved)



The default system provides 80 AWTs for each AMP vproc and reserves three tasks for each of eight work types (or 24 reserved tasks).

When only one work type is active and all of its reserved tasks (3) are in use, the current limit on the number of active tasks will be 59:

80 - (24-3) =59

At this point, no more than 59 tasks can be active because 21 tasks are reserved for other work types that have no current activity.

When two work types are active and have used all their reserved tasks (three each), the current limit becomes 62:

80 - (24 - 6) = 62

Assuming that more than the three reserved tasks are active for both work types, the 62 tasks can be divided in any way between the two work types. Examples of this second case can be seen on running systems when many redistribution requests are active. Redistribution uses two different work types:

• For new work• For spawned work

Besides reserving work tasks, the AWT resource manager also enforces an upper limit of 50 on requests of work type NEWWORK. Since many queries rely on multiple work types to reach completion, the limit on NEWWORK insures that these requests do not use too many unreserved AWTs. Other work types have no upper limit.

AWTs Reservation for Expedited Allocation Groups

To aid response time consistency for short queries, Priority Scheduler parameters can extend the default resource management function and allow an administrator to reserve and limit AWTs that process these types of work requests. All requests controlled by allocation groups to which the administrator has given the Expedite attribute fall into this category. Reservation and limit are applied to a set of three work types used solely to process requests controlled by one or more expedited allocation groups.

As described in “AWT Resource Allocation” on page 7-39, the number of reserved tasks for expedited requests determines the minimum number of tasks that are always available. This ensures that these tasks will run concurrently any time. When the reserved tasks are all active, additional requests of that type can still be started until the current limit, or the limit on that work type, is reached. When either limit is reached, requests are queued until an active task completes and is available to service another request. Of course, if the work type limit is reached, an active task of that type must complete before another can be started.

The number of reserved tasks for the three work types used by expedited requests is added to the number of reserved tasks defined for normal work. If



you reserve three tasks for expedited requests, each of the three work types will receive a reservation of three tasks. A total of nine tasks would be reserved across the three work types and the total number of reserved tasks would be raised to 33. Under these conditions, when only one expedited work type is active and all reserved tasks of that type are in use, the current limit on the number of active tasks will then be 50:

80 - (33 - 3) = 50

For example, suppose that the reserve and limit values for expedited work requests are three and five, respectively. This allows three requests to always run concurrently. Depending on the arrival and service rate of expedited requests, the three reserved tasks might be enough to allow one to always be available to service an incoming request. If the arrival and service rates do not allow this, then arriving requests are queued to wait for an available AWT. These queued requests will be handled by any available task when the number of active tasks for the work type is less than five. In this case, five requests might be running concurrently, but two of them might have had to wait in the queue for service. When the number of active tasks reaches five, arriving requests must wait on the input queue until one of those five has completed.

If expedited work consists of short, single, or few AMP queries, the amount of time a reserved work task is held by any such query might be very short, such that a single work task could service hundreds of queries per second. Under these conditions, a reservation of one or two tasks might be adequate, depending on the expected arrival and service rate of the queries.

Note: The work request for a single-AMP query is processed by just one task of the AMP vprocs of an MPP system. Each AMP in the system could be performing a similar single-AMP request simultaneously.

If the number of reserved tasks for expedited work types is zero, these expedited requests will be treated as non-expedited requests and handled as ordinary work. Use a limit of zero, or a large number, such as 999, to indicate that no limit is to be applied.

The schmon -m display includes data indicating the queue length, queue wait time, and service time for all allocation groups. This data might be useful for adjusting the Expedited work type reservation and limit values. If the queue wait time is zero for a non-expedited allocation group, then it might not benefit from being expedited, because no shortage of AWTs is being experienced.

The optional Expedite attribute of an allocation group is intended to provide quicker and more consistent response time for queries than might be experienced with a non-expedited allocation group. This allocation group option is intended for use by sessions submitting short, simple queries where quick response time is critical. This type of work is sometimes referred to as Operational Data Store (ODS) type work.



The puma utility includes a command option to display data describing AWTs for each VPROC. The puma -c command shows the reserve, limit, in-use, and peak values for each work type.



AMP Work Task (AWT) Examples

The following examples show how AWTs might be allocated under a heavy load of normal data warehouse work and various expedited work loads and settings.

In the examples, the following applies:

• An asterisk indicates which work types are used for expedited work requests.

• The Min and Max columns indicate reserved and limit values, respectively.• A Max value of 999 indicates that no individual limit on that work type

exists and only the computed current-limit will control the number of tasks of that type that can be active. Further, this assumes that normal (non-expedited) requests require two AWTs to complete (one NEWWORK and one WORKONE type tasks [for redistribution and other spawned work]), while expedited requests require only a WORKEIGHT type task.

Example 1

WorkType Min Max Inuse Peak

MSGWORKNEW 3 50 31 31MSGWORKONE 3 999 31 31MSGWORKTWO 3 999 0 0MSGWORKTHREE 3 999 0 0

*MSGWORKEIGHT 0 0 0 0*MSGWORKNINE 0 999 0 0*MSGWORKTEN 0 999 0 0MSGWORKABORT 3 999 0 0MSGWORKSPAWN 3 999 0 0MSGWORKNORMAL 3 999 0 0MSGWORKCONTROL 3 999 0 0

This is an ordinary case where no tasks are reserved for expedited work types. No expedited queries are running. The total number of reserved tasks is 24 (the sum of the Min column), and the current limit is 62 (the sum of the Inuse column).

The output shows 62 active tasks on behalf of 31 queries divided between WORKNEW and WORKONE. Because 62 is the current limit in this example, newly arriving requests are placed on the input queue.



Example 2




In this case, a reserve of one and limit of three have been made for expedited work types. Each of the three work types associated with expedited requests will reserve one task for a total of three. The total number of reserve tasks now has been increased from 24 (in Example 1) to 27. When only normal work is running, the current limit drops from 62 to 59, reducing the level of non-expedited work that can be supported.

Example 3




In this case, a reserve of three and limit of five have been made for expedited work types. Because there are three work types for expedited work, and each will receive a reservation of three, the total reserved for expedited work is now nine. The total number of reserve tasks now has been increased from 24 (in Example 1) to 33. When only normal work is running, the current limit is 53.

When the maximum number of expedited requests are running (and using both reserved and non reserved tasks), the current limit is 56.


Chapter 7: Priority Schedulerschmon Utility

schmon Utility

Function

The schmon utility provides a command line interface that allows you to display and alter Priority Scheduler parameters.

Syntax

schmon-a

allid#

-s-S

TypeX

policy weight

-ballid#

name weightlimit

-s

-S-d-e-E

-pallid#

name R V T L1 A1 A2 A3 A4 A5L2 L3 L4 L5-s

-S

-minterval-seconds

repetitions

-ffile_path

-h-i-I-l

-r

-R

limit

none

-Minterval-seconds

repetitions

-p

-tage-time active-time disp-time I/O concurrency

-sall

-S

id#

-S

-S

-wreserve maximum

HH01A001


Chapter 7: Priority Schedulerschmon -a

schmon -a

Function

Sets or displays allocation group parameters.

Syntax

where:

Syntax element Description

-a Without options, displays the parameters for all allocation groups.

all (or null) Sets the parameters for all allocation groups.

id# • Without options, displays the parameters for a single allocation group.• With options, sets the parameters for a single allocation group.

-s Displays Priority Scheduler data for all sessions controlled by the allocation group on the current node.

-S Displays Priority Scheduler data for all sessions controlled by the allocation group on all nodes of the system.

Type A single character that indicates the type of scheduling set division enforced by the allocation group. A scheduling set is a collection of processes controlled by the allocation group.

The resources of the allocation group are shared equally by its scheduling sets. Permissible values for Type are as follows:

Value … Specifies …

N (NONE) all processes controlled by the allocation group form one scheduling set and the allocation group resources are divided equally among these processes:

• The lone process invoked by a single-AMP query receives the same resource allocation as each process invoked by an all-AMP query that has several processes, one per vproc.

• This is an advantage for multi-AMP queries if work within an allocation group is mixed.

schmon -aallid#

-s-S

TypeX

policy weight HH01A003



Usage Notes

You can reference allocation groups by multiple performance periods in multiple groups, which must all belong to the same resource partition.

Example 1

Example 1 shows how to display session data for an allocation group from the current node.

schmon -a 2 -sschmon -a 2 -S


Type (cont) Value … Specifies …

S (SESSION) processes are grouped into one scheduling set for each session. The allocation group resources are divided equally among the scheduling sets. The resources for each scheduling set are divided equally among its processes.

• Each query receives the same resources no matter how many processes are involved.

• This is an advantage for single-AMP queries if work within the allocation group is mixed.

X The allocation group is expected to process expedited work. Work requests controlled by the allocation group receive special treatment in the request input queue and AWT allocation phase. Requests receive superior priority in the input queue, bypassing normal requests, and are assigned to work processes from a pool reserved for the purpose.

You can use this option with more than one allocation group. When multiple allocation groups have the expedited attribute, work requests for all of the allocation groups are satisfied from a single reserved work process pool.

Note: You can use the schmon -l command to define the reserved work process pool.

policy One of the following scheduling policies:

• ABS (ABSOLUTE)• DEF (DEFAULT)• IMD (IMMEDIATE)• REL (RELATIVE)

weight A numeric value used to compute a relative weight to determine the proportion of resources the processes of the allocation group are to receive.



Example 2

Example 2 shows how to set the expedite attribute on an allocation group.

schmon -a 6 N X DEF 30

Allocation Groups (0 - 199) Id Type Pol Weight 6 N DEF 30

>>>>> Changed to: 6 NX DEF 30

Example 3

Example 3 shows how to define an allocation group.

schmon -a 5 S DEF 5

Allocation Groups (0 - 199) Id Type Pol Weight 5 S DEF 1

>>>>> Changed to: 5 S DEF 5


Chapter 7: Priority Schedulerschmon -b

schmon -b

Function

Sets or displays resource partition parameters.

Syntax

where:


-b Without options, displays the parameters for all resource partitions.

all (or null) Sets the parameters for all resource partitions.

id# • Without options, displays the parameters for a single resource partition.

• With options, sets the parameters for a single resource partitions.

name The name of the resource partition.

weight A numeric value used to compute a relative weight to determine the proportion of resources that the processes controlled by the resource partition are to receive.

limit A percentage limit on total CPU usage by all processes controlled by this resource partition or the character string none.

The value ranges from 1 through 100.

• A value of 100 indicates that no limit is to be enforced.• The character string none indicates that no limit is to be enforced.

If limit is not present, any previously defined limit is removed.

-s Displays Priority Scheduler data for all sessions controlled by the resource partition on the current node.

-S Displays Priority Scheduler data for all sessions controlled by the resource partition on all nodes of the system.

schmon -ballid#

name weightlimitnone

-s

-S

HH01A004


Chapter 7: Priority Schedulerschmon -b

Usage Notes

For information on the settings displayed using the -b option, see “schmon -d” on page 7-51.

Example 1

Example 1 shows how to display session data for a resource partition from the current node, or all nodes in the system.

schmon -b 1 -s

schmon -b 0 -S

AG HostID Session Request #prc CPU(msec) DSK(blk) RP PG [PP]=== ====== ========== ========== ==== ========== ========== === ===============1 0 0 0 11 0 7218 0 L[0] low$[0]2 0 0 0 2 3460 60 0 M[0] med$[0]2 2049 1104 4 1 1470 32139 0 M[0] med$[0]2 2049 1114 2 3 220 0 0 M[0] med$[0]4 0 0 0 18 22860 282082 0 R[0] rush$[0]4 0 0 0 2 2100 116 0 R[0] rush$[0]

Example 2

Example 2 shows how to set a limit on CPU resource usage by a resource partition. This will limit CPU usage by processes controlled by the resource partition to 40 percent of the total CPU available.

schmon -b 1 RP1 50 40 Resource Partitions (0 - 4)Id Partition Name Weight Limit 1 RP1 50 none

>>>>> Changed to: 1 RP1 50 40

Example 3

Example 3 shows how to reset the limit to none on a resource partition.

schmon -b 1 RP1 50 Resource Partitions (0 - 4)Id Partition Name Weight Limit 1 RP1 50 40

>>>>> Changed to: 1 RP1 50 none


Chapter 7: Priority Schedulerschmon -d

schmon -d

Function

Displays the current Priority Scheduler settings in multi-line format.

Syntaxschmon -d

where:

Setting category Description

Scheduler Times & Attributes Displays scheduler times and attributes.

Setting … Specifies the …

Age Time time period over which recent resource usage by a scheduling set is measured. The default is 60 seconds.

Active Time time period 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 calculations. The default is 61 seconds.

Limit system CPU limit or none if you do not specify one.

Scheduler • Active by default or if you enable the Scheduler with the schmon -e command

• Inactive if you disable the Scheduler with the schmon -E command.

Performance • Throughput by default or if you enable the Scheduler throughput mode with the schmon -R command

• Response if you disable the Scheduler throughput mode with the schmon -r command.

I/O Priority • Prioritize by default or if you enable the state with the schmon -i command

• No Prioritize if you disable the state with the schmon -I command.




Resource Partitions Displays resource partition parameters.

Setting … Specifies …

ID the identifier number of the resource partition.

Partition Name

the name of the resource partition.

Weight the numeric value used to compute the relative weight of this resource partition.

Limit a number between 1 and 100, inclusive, that specifies a percentage limit on the total CPU usage by sessions assigned to the performance groups associated with the resource partition or the string none to indicate no limit is present.

Performance Groups Displays performance group parameters.


ID system-wide, unique identifier of the performance group.

Group Name name of the performance group.

RP resource partition to which this performance group is to be assigned.

Val performance group value within the resource partition. Val is a numeric value between 0 and 7 inclusive, indicating the relative importance of the group within its resource partition.




Performance Groups (cont) Setting … Specifies …

Type the single character that specifies the type of units used in these performance period definitions:

Character … Indicates that milestone …

R limits are seconds (1-86400) of resource usage.

T units are time-of-day, in military time (0 to 2359). You must define at least two periods.

Milestones & Allocation Groups

that each milestone defines a period milestone (in units defined by Type above), and that the corresponding allocation group defines the allocation group in effect during that period.

If you are defining only one performance period for the performance group, use R as the default milestone type and 0 (zero) as the default milestone limit.

Allocation Groups Displays allocation group parameters.


ID the system-wide, unique identifier of the allocation group.

Type a single character that indicates the type of scheduling set division supported by the allocation group.

The resources of the allocation group are shared equally by its scheduling sets. Permissible values for Type are the following:

Value … Specifies that resources are divided …

N (NONE) among processes:

• For all-AMP operations, each AMP counts for one process.

• Each step in a parallel-step plan counts for one process.

• Complex queries could be offered more system resources.




Allocation Groups (cont) Setting … Specifies …

Type (cont) Value … Specifies that resources are divided …

S (SESSION) by the number of active sessions and then by processes:

• Each query receives the same resources no matter how many AMPS are involved.

• This is an advantage for single-AMP queries if work within the allocation group is mixed.

X that an allocation group has the Expedite attribute.

Pol one of the following scheduling policies:

• ABS (ABSOLUTE)• DEF (DEFAULT)• IMD (IMMEDIATE)• REL (RELATIVE)

Weight a numeric value used to compute the relative weight of the allocation group.



Exampleschmon -d

Scheduler Times & Attributes:Age Time(sec): 60 Active Time(sec): 61 Limit(%): 90Attrs: Active, Thruput, I/O Prio

Resource Partitions (0 - 4)Id Partition Name Weight Limit0 Default 100 none1 RP1 50 40

Performance Groups (0 - 39)Id Group Name RP Val Type Milestones & Allocation Groups[0-4]0 L 0 0 S 0 10 L 0 0 S 0.00 11 low$ 0 1 S 0.00 12 M 0 2 T 1100 3 1800 23 med$ 0 3 T 1100 3 1800 24 H 0 4 S 0.00 35 high$ 0 5 S 0.00 36 R 0 6 S 0.00 47 rush$ 0 7 S 0.00 48 RP1L 1 0 S 0.00 59 RP1M 1 2 Q 0.50 7 0.00 6

Allocation Groups (0 - 199)Id Type Pol Weight Id Type Pol Weight Id Type Pol Weight Id Type Pol Weight

1 S DEF 5 2 S DEF 10 3 S DEF 20 4 S DEF 40

5 N DEF 5 6 N DEF 10 7 NX DEF 20 8 N DEF 40

AWT Expedited work type limitsres max0 999


Chapter 7: Priority Schedulerschmon -e

schmon -e

Function

Enables priority scheduling if the -E option disabled priority scheduling.

Syntaxschmon -e

Exampleschmon -eScheduler state set to Active.


Chapter 7: Priority Schedulerschmon -E

schmon -E

Function

Disables priority scheduling, causing all processes to receive the same scheduling priority.

Syntaxschmon -E

Exampleschmon -EScheduler state set to Inactive.


Chapter 7: Priority Schedulerschmon -f

schmon -f

Function

Reads schmon commands from a file or standard input device.

Syntax

where:

Usage Notes

Input data is assumed to be a single file of schmon commands separated by new line characters. A command that begins with the # character is treated as a comment. Each input command is written to the standard error device when the command is read. Changes to Priority Scheduler parameters are accumulated until the end of file is encountered and then applied to the system. An error in a command will terminate reading, and no changes are applied. Errors are reported on the standard output device.

Example

The following example is an input file of schmon commands and the schmon -f command to process the file.

schmon -f fsample

The contents of the file fsample:

schmon -a 6 N DEF 10schmon -a 7 N X DEF 20schmon -p 9 RP1M 1 2 Q .5 7 0 6schmon -p 2 M 0 2 T 1100 3 1800 2schmon -p 3 med$ 0 3 T 1100 3 1800 2


file_path a path from which input is to be read. If you do not specify file_path, data is read from the standard input device.

-ffile_path

schmon

HH01A005


Chapter 7: Priority Schedulerschmon -h

schmon -h

Function

Displays help for schmon.

Syntax

schmon -h

Usage Notes

This is also the equivalent of issuing the command with no options.

Exampleschmon -h

schmon [-deEiIrRh][-a [all | <id#> [-s | -S | [<div> <policy> <GRAW>]]]][-b [all | <id#> [-s | -S | [<name> <RPAW> <limit>]]]][-f [path]][-l <limit>][-m [-S [[-]p]] [interval-seconds [#-of-reps]]][-M[p] [interval-seconds [#-of-reps]]][-p [all | <id#> [-s | -S | [<name> <R> <V> <T> <PP(i)(i = 0,4)>]]]][-s [all | ssn# [-S]][-t <age-dsecs> <active-dsecs>][-w <res max>]


Chapter 7: Priority Schedulerschmon -i

schmon -i

Function

Enables the prioritized queuing of FSG I/O requests. Requests are ordered according to the scheduling priority of the submitting process.

Syntaxschmon -i

Exampleschmon -iScheduler state set to Prioritize I/O.


Chapter 7: Priority Schedulerschmon -I

schmon -I

Function

Disables the prioritized queuing of FSG I/O requests and causes these requests to be serviced in an order established by the normal driver method.

Syntaxschmon -I

Exampleschmon -IScheduler state set to No Prioritize I/O.


Chapter 7: Priority Schedulerschmon -l

schmon -l

Function

Sets the system CPU usage limit.

Syntax

where:

Example 1

Example 1 sets the system CPU resource limit to 90 percent on each node.

schmon -l 90 System CPU Limit(%) none>>>>> Changed to: 90


-l Without options, displays the current limit.

limit A percentage value to limit the amount of CPU usage by Teradata RDBMS sessions or the character string none. This usage does not include non-Teradata work, such as time-share users, I/O or other interrupt services, Gateway processing, or streams work.

The value ranges from 1 through 100.

• A value of 100 indicates that no limit is to be enforced.• The character string none indicates that no limit is to be

enforced.• Zero is not a valid limit value.

schmon

HH01A012

-llimitnone


Chapter 7: Priority Schedulerschmon -l

Example 2

Example 2 shows that the schmon -l command with no limit value will reset the CPU limit to none or unlimited.

schmon -l System CPU Limit(%) 90>>>>> Changed to: none


Chapter 7: Priority Schedulerschmon -m

schmon -m

Function

Monitors Priority Scheduler statistics for the current node.

Syntax

where:


-m Monitors Priority Scheduler statistics for the current node.

where:

Syntax element … Specifies the …

interval-seconds monitoring interval.

The interval ranges from 5 to 1800 seconds. The minimum monitoring interval is 5 seconds.

repetitions number of times the display repeats.

The number of repetitions must be positive. The interval cannot match the actual time between statistics collection displays due to the time required for the collection activity itself.

• On MPP systems, this time varies, depending on the number of nodes and speed of response.

• On SMP systems, this time should be insignificant.

-minterval-seconds

repetitions

schmon

HH01A006



-m (cont) The statistics are described as follows.

Display category Description

Stats Collection The date and time of the statistics displayed, as well as repetition number, if you specify multiple repetitions.

Resource Partitions

The statistics for each active resource partition, including the following:


RP the resource partition ID Number.

Rel Wgt the weight of the resource partition relative to the active resource partitions.

Avg CPU the resource usage during the preceding age period for a single CPU. The CPU data is shown in two columns.

Column … Is the …

% percentage of CPU consumed by the resource partition. On multi-node systems, this is the average percentage per resource partition for all nodes.

msec milliseconds of CPU time consumed by the resource partition.




-m (cont) Display category Description

Resource Partitions (cont)


Avg I/O a normalized number of data blocks transferred by the resource partition. On multi-node systems, this is the average normalized resource use per resource partition for all nodes on the system. I/O data is shown in two columns.


% percentage of disk consumed by the resource partition. On multi-node systems, this is the average percentage per resource partition for all nodes.

sblks number of blocks read and written by the resource partition.

# of Procs the number of processes assigned to the resource partition at the end of the preceding collection period. On multi-node systems, this is the average per resource partition for all nodes.

# of Sets the number of scheduling sets associated with the resource partition at the end of the preceding collection period.

IF allocation group Set Division is …

THEN one scheduling set …S

Session per session exists.

None to the allocation group exists.





Allocation Groups

The statistics for each active allocation group, including the following:


AG the allocation group ID number.

Rel Wgt the weight of the allocation group relative to the active allocation groups of the resource partition and the active resource partitions.

Avg CPU resource usage by the allocation group during the preceding age period for a single CPU. The CPU data is shown in two columns.


% percentage of total available CPU on the node consumed by the allocation group. On multi-node systems, this is the average percentage for all nodes.

msec milliseconds of CPU usage consumed by the group.

Avg I/O a normalized number of data blocks transferred by the allocation group. On multi-node systems, this is the average normalized resource use per allocation group for all nodes on the system. I/O data is shown in two columns.


% percentage of total I/O blocks transferred by the allocation group. On multi-node systems, this is the average percentage for all nodes.

sblks number of blocks read and written by the group.

# of Procs a number of processes assigned to the allocation group at the end of the proceeding collection period. On multi-node systems, this is the average per allocation group for all nodes.





Allocation Groups (cont)


# of Sets a number of scheduling sets associated with the allocation group at the end of the preceding collection period. On multi-node systems, this is the total per allocation group for all nodes.


THEN one scheduling set …



Performance Groups Affected

all performance groups by name that reference the allocation group at that time. Since allocation groups can be shared among performance groups, this information is useful for resource usage traceback. (This information is not displayed on multi-node systems unless you use the -p option.)

Work Requests Displays work request statistics for each active allocation group. This data refers to the preceding age period and is the average for all nodes on a multi-node system. The data includes the following:


AG allocation group number.

# requests number of work requests received.

Avg queue wait

average time, in milliseconds, that a work request waited on an input queue before being serviced.

Avg queue length

average number of work requests waiting on the input queue for service.

Avg service time

average time, in milliseconds, that a work request required for service.




-m (cont) The following example is the second of five displays obtained at 10-second intervals.

Example:

schmon -m 10 5

Stats Collection #2: Tue Mar 19 09:59:54 2002

Rel Avg CPU Avg I/O # of # of RP Wgt % (msec) % (sblks) Procs Sets

=== === === ======= === ======= ===== ======0 100 17 461 100 605878 22 14

Rel Avg CPU Avg I/O # of # of AG Wgt % (msec) % (sblks) Procs Sets Performance Groups Affected

=== === === ======= === ======= ===== ===== ===========================2 14 0 4 0 0 0 4 med$4 57 0 29 15 95066 20 6 R, rush$7 28 17 428 84 510812 2 4 M

Avg queue Avg queue Avg serviceAG #requests wait(msec) length time(msec)

=== ========== ========== ========== ===========2 197 0 0 24 53 0 0 37 688 0 0 21



Chapter 7: Priority Schedulerschmon -M

schmon -M

Function

Monitors Priority Scheduler statistics for all nodes. You can enter this command from any node in an MPP system.

Syntax

where:


-M Monitors Priority Scheduler statistics for all nodes.

where:


-p to display performance group names associated with the allocation groups that are displayed with the -M command.

interval-seconds the monitoring interval.

The interval ranges from 5 to 1800 seconds. The minimum monitoring interval is 5 seconds.

repetitions the number of times the display repeats.


On … This time …

MPP systems varies, depending on the number of nodes and speed of response.

SMP systems should be insignificant.

-Minterval-seconds

repetitions

-pschmon

HH01A007



-M (cont) The settings are described as follows.


Stats The date and time of the statistics displayed, as well as repetition number if multiple repetitions are specified.

Resource Partitions

The statistics for each active resource partition, including the following:


RP the resource partition ID Number.

Rel Wgt the weight of the resource partition relative to the active resource partitions.

Avg CPU resource usage during the preceding age period for a single CPU. The CPU data is shown in two columns.


% percentage of CPU consumed by the resource partition. On multi-node systems, this is the average percentage per resource partition for all nodes.

msec milliseconds of CPU time consumed by the resource partition.

Avg I/O a normalized number of data blocks transferred by the resource partition. On multi-node systems, this is the average normalized resource use per resource partition for all nodes on the system. I/O data is shown in two columns.


% percentage of disk consumed by the resource partition. On multi-node systems, this is the average percentage per resource partition for all nodes.

sblks number of blocks read and written by the resource partition.




-M (cont) Setting category Description

Resource Partitions (cont)


Avg # of Procs the number of processes assigned to the resource partition at the end of the preceding collection period. On multi-node systems, this is the average per resource partition for all nodes.

Avg # of Sets the number of scheduling sets associated with the resource partition at the end of the preceding collection period.


THEN one scheduling set …S



Minimum CPU

the lowest value in milliseconds of CPU resource usages from all nodes.

Minimum I/O

the lowest value of I/O data blocks transferred from all nodes in sblks.

Minimum Procs

the lowest number of processes from all nodes.

Maximum CPU

the highest value in milliseconds of CPU resource usages from all nodes.

Maximum I/O

the highest value of I/O data blocks transferred from all nodes in sblks.

Maximum Procs

the highest number of processes from all nodes.





Allocation Groups

The statistics for each active allocation group, including the following:


AG the allocation group ID number.

Rel Wgt the weight of the allocation group relative to the active allocation groups of the resource partition and the active resource partitions.

Avg CPU resource usage by the allocation group during the preceding age period for a single CPU. The CPU data is shown in two columns.


% percentage of total available CPU on the node consumed by allocation group. On multi-node systems, this is the average percentage for all nodes.

msec milliseconds of CPU usage consumed by the group.







Avg I/O a normalized number of data blocks transferred by the allocation group. On multi-node systems, this is the average normalized resource use per allocation group for all nodes on the system. I/O data is shown in two columns.


% percentage of total I/O blocks transferred by the allocation group. On multi-node systems, this is the average percentage for all nodes.

sblks number of blocks read and written by the group.

Avg # of Procs the number of processes assigned to the allocation group at the end of the proceeding collection period. On multi-node systems, this is the average per allocation group for all nodes.

Avg # of Sets the number of scheduling sets associated with the allocation group at the end of the preceding collection period. On multi-node systems, this is the total per allocation group for all nodes.


THEN one scheduling set …








• When you submit the -M command on an MPP system, the following minimum and maximum values are displayed:


Minimum CPU

lowest value in milliseconds of CPU resource usages from all nodes.

Minimum I/O

lowest value of I/O data blocks transferred from all nodes in sblks.

Minimum Procs

lowest number of processes from all nodes.

Maximum CPU

highest value in milliseconds of CPU resource usages from all nodes.

Maximum I/O

highest value of I/O data blocks transferred from all nodes in sblks.

Maximum Procs

highest number of processes from all nodes.

• When you submit the -M command or specify the -p option on an SMP system, the affected performance groups are displayed instead of the minimum and maximum values:


Performance Groups Affected

all performance groups by name that reference the allocation group at that time. Since allocation groups can be shared among performance groups, this information is useful for resource usage traceback.




Example 1

The following example is from an MPP system.

schmon -M

Stats Tue Mar 19 10:00:20 2002

Avg Avg Node Resource UsageRel Avg CPU Avg I/O # of # of Minimum Maximum

RP Wgt % (msec) % (sblks) Procs Sets CPU I/O Procs CPU I/O Procs=== === === ======= === ======= ===== ===== ================= ==================

0 100 3 1816 100 689461 20 35 1098 342137 2 2519 1062399 4

Avg Avg Node Resource UsageRel Avg CPU Avg I/O # of # of Minimum Maximum

AG Wgt % (msec) % (sblks) Procs Sets CPU I/O Procs CPU I/O Procs=== === === ======= === ======= ===== ===== ================= ==================

2 14 0 125 0 0 0 10 27 0 0 324 0 04 57 0 461 59 413171 17 14 34 273346 15 1283 662616 217 28 2 1229 40 276290 2 10 814 18207 2 1996 669604 4

Avg queue Avg queue Avg serviceAG #requests wait(msec) length time(msec)

=== ========== ========== ========== ===========2 550 0 0 24 155 0 0 37 1668 0 0 15


Work Requests Displays work request statistics for each active allocation group. This data refers to the preceding age period and is the average for all nodes on a multi-node system. The data includes the following:


AG allocation group number.

# requests number of work requests received.

Avg queue wait

average time, in milliseconds, that a work request waited on an input queue before being serviced.

Avg queue length

average number of work requests waiting on the input queue for service.

Avg service time

average time, in milliseconds, that a work request required for service.




Example 2

The following is an example of the -M command with the -p option executed on an MPP system. This display also appears if you execute the -M command (with or without the -p option) on an SMP system.

schmon -M -p

Stats Collection #4: 4 node(s) Mon Apr 15 16:55:35 2002

Avg Avg Rel Avg CPU Avg I/O # of # of RP Wgt % (msec) % (sblks) Procs Sets === === === ======= === ======= ===== ===== ============================== 0 100 1 687 100 694729 23 2

Avg Avg Rel Avg CPU Avg I/O # of # of AG Wgt % (msec) % (sblks) Procs Sets Performance Groups Affected=== === === ======= === ======= ===== ===== =========================== 2 20 0 577 55 384298 6 1 M, med$ 4 80 0 110 44 310431 17 1 R, rush$

Avg queue Avg queue Avg service AG #requests wait(msec) length time(msec)=== ========== ========== ========== ========== 2 649 0 0 17 4 25 0 0 5


Chapter 7: Priority Schedulerschmon -p

schmon -p

Function

Sets or shows performance group parameters.

Syntax

where:


-p Sets or shows performance group parameters.

where:


-p Without options, displays the parameters for all performance groups.

all (or null) Sets the parameters for all performance groups.

id# • Without options, displays the parameters for a single performance group.

• With options, sets the parameters for a single performance group.

name Specifies the name of the performance group with the resource partition.

R Specifies the resource partition to which this performance group is to be assigned.

V Specifies the performance group value within the resource partition.

V is a numeric value between 0 and 7 inclusive, indicating the priority of the group. V must be unique within the resource partition.

schmon

HH01A008

-pallid#

name R V T L1 A1 A2 A3 A4 A5L2 L3 L4 L5-s

-S



-p (cont) Syntax element Description

T Specifies a single character that indicates the milestone type used in the performance period definitions for that performance group:

Character … Specifies …

Q that milestone units are seconds of query resource usage. Each query submitted by a session begins a new resource usage accumulation at the first performance period defined for the performance group.

S or R indicates that milestone units are seconds of session resource usage. These two characters are equivalent. The R option is provided for backward compatibility with earlier software versions.

T milestone units as time-of-day, in military time (0-2359). You must define at least two periods.

Performance Period Pairs L1 A1, L2 A2 through L5 A5

These are performance period designator pairs consisting of milestone limit values and allocation group numbers for each of up to five performance periods.

Allocation groups can be referenced by multiple performance groups, which must belong to the same resource partition.

When the milestone type is T, you must specify at least two performance periods. The lower inclusive bound for the first period is the milestone limit value for the last performance period.

When the milestone type is Q, R, or S, the lower bound for the first performance period is assumed to be zero. Also, the milestone of the last performance period must be zero. After a session or query enters the last performance period, that period remains in control for the remainder of the session or query.

When the milestone type is Q, R, or S, the milestone limit is a real number greater than 0 and less than 86400. You can enter this number with an optional decimal point and fractional value. The given number is rounded to the nearest 1/100 second value. The following examples are valid milestone limit CPU usage times:

• .01• 2.5• 3.1415• 200




Example

The following example shows how to display session data for a performance group from the current node or from all nodes in the system.

schmon -p 4 -sschmon -p 6 - S

AG HostID Session Request #prc CPU(msec) DSK(blk) RP PG [PP]=== ====== ========== ========== ==== ========== ========== === ===============

1 0 0 0 11 0 7218 0 L[0] low$[0]2 0 0 0 2 3460 60 0 M[0] med$[0]2 2049 1104 4 1 1470 32139 0 M[0] med$[0]2 2049 1114 2 3 220 0 0 M[0] med$[0]4 0 0 0 18 22860 282082 0 R[0] rush$[0]4 0 0 0 2 2100 116 0 R[0] rush$[0]

-p (cont) Syntax element Description

-s Displays Priority Scheduler data for all sessions controlled by the performance group on the current node.

-S Displays Priority Scheduler data for all sessions controlled by the performance group on all nodes of the system.



Chapter 7: Priority Schedulerschmon -r

schmon -r

Function

Sets scheduling state to provide more favorable response time for interactive events, at some cost to CPU-intensive activities.

Syntaxschmon -r

Usage Notes

Setting this option allows more frequent process switching and a corresponding increase in system service time.

Exampleschmon -rScheduler state set to Response.


Chapter 7: Priority Schedulerschmon -R

schmon -R

Function

Sets scheduling state to improve performance for CPU-intensive activities at some cost in response time for interactive events.

Syntaxschmon -R

Exampleschmon -RScheduler state set to Throughput.


Chapter 7: Priority Schedulerschmon -s

schmon -s

Function

Displays Priority Scheduler data for the specified sessions from the current node or all nodes in the system.

Syntax

where:


-s Displays Priority Scheduler data for the specified sessions from the current node or all nodes in the system.

where:


all all sessions.

id# the session identification number. A session number is unique for a host ID. However, a small possibility exists that duplicate session numbers might occur. But since this is not likely, this command accepts a session number and reports data for all host IDs if duplicate session numbers exist.

-S data from all nodes in the system.

The following applies:

IF performance period type is …

THEN data indicates …

session (S) session activity.

request (Q) request activity.

schmon

HH01A009

-sall

-S

id#

-S

-S


Chapter 7: Priority Schedulerschmon -s

Exampleschmon -s

AG HostID Session Request #prc CPU(msec) DSK(blk) RP PG [PP]=== ====== ========== ========== ==== ========== ========== === ===============

1 0 0 0 11 0 7218 0 L[0] low$[0]2 0 0 0 2 3460 60 0 M[0] med$[0]2 2049 1104 4 1 1470 32139 0 M[0] med$[0]2 2049 1114 2 3 220 0 0 M[0] med$[0]4 0 0 0 18 22860 282082 0 R[0] rush$[0]4 0 0 0 2 2100 116 0 R[0] rush$[0]

-s (cont) The settings are described as follows.

Setting category … Specifies the …

AG allocation group identifier.

Host ID host system of an active session.

Session session number of an active session.

Request request number of an active session.

#prc number of processes working on behalf of the session.

CPU (msec) number of milliseconds of CPU time accumulated by the session or request during the previous age period.

DSK (blk) number of disk blocks transferred by the session or request during the previous age period.

RP resource partition to which the allocation group belongs.

PG performance group to which the session is assigned.

[PP] performance period currently controlling the session.



Chapter 7: Priority Schedulerschmon -t

schmon -t

Function

Sets or displays Age Time, Active Time, Disp Time, and I/O Concurrency Level.

Syntax

where:


-t Sets or displays Age Time, Active Time, Disp Time, and I/O Concurrency Level.

where:

Option Description

active-time 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 calculations.

The range is 1 to 1800 seconds. The default is 61 seconds.

age-time The time period, in seconds, over which recent allocating group resource usage is measured.

The range is 1 to 1800 seconds. The default is 60 seconds.

disp-time The maximum period of time 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.

A value of … Specifies …

0 that processes are not to be promoted.

1 - 127 a wait period in seconds.

I/O concurrency The number of concurrent I/O requests that might be active for each AMP vproc.

The default is 10.

Note: This is a Windows 2000 only feature.

schmon

HH01A010

-tactive-time age-time disp-time I/O concurrency


Chapter 7: Priority Schedulerschmon -t

Usage Notes

I/O Concurrency Level applies to Windows 2000 only and is ignored, if present, on a UNIX MP-RAS platform.

Example 1 - UNIX MP-RASc:>schmon -t 60 61 0 Age Time(sec): 60 Active Time(sec): 61 Disp Age(sec): 5>>>>> Changed to: Age Time(sec): 60 Active Time(sec): 61 Disp Age(sec): 0

Example 2 - Windows 2000c:>schmon -t 60 61 10 0 Age Time(sec): 60 Active Time(sec): 61 I/O Concurrency: 10 Disp Age(sec): 0>>>>> Changed to: Age Time(sec): 60 Active Time(sec): 61 I/O Concurrency: 10 Disp Age(sec): 0

-t (cont) The following applies.

IF you do … THEN …

not specify any options

the current settings display.

specify options you must specify Active Time, Age Time, and Disp Time. On Windows 2000, you must also specify I/O concurrently.



Chapter 7: Priority Schedulerschmon -w

schmon -w

Function

Sets or displays the number of processes available on each vproc for use by work requests assigned to allocation groups having the Expedite attribute.

Syntax

where:


-w Sets or displays the number of processes available on each vproc for use by work requests assigned to allocation groups having the Expedite attribute.

where:

Option Description

reserve A number between 0 and 10, inclusive, that indicates the number of AWTs reserved within each AMP vproc for work requests assigned to allocation groups having the EXPEDITE attribute.

This reserve ensures that at least this specified number of AWTs will be ready to service a work request when it arrives. When the number of expedited work requests exceeds this reserve, arriving expedited work requests might be forced to wait in an input queue, depending on overall work load conditions. This reserve determines the minimum number of expedited work requests that will run concurrently.

This reserve, multiplied by three, is deducted from the general pool of AWTs and will impact the number of tasks available for normal non-expedited work requests.

NCR recommends the following:

• Initially select a low number for reserve (1-3).• Expedite only allocation groups supporting short, response-sensitive

queries.

maximum A number between 0 and 80, inclusive, that indicates the maximum number of AWTs that can run at any time. The number of tasks that run might be less than this maximum, depending on the current limit.

If you do not supply any parameters, the current settings for reserve and maximum are displayed.

schmon

HH01A011

-wreserve maximum


Chapter 7: Priority Schedulerschmon -w

Usage Notes

The Expedite attribute is defined by an allocation group. For more information see “Expedite Attribute” on page 7-26 and “AMP Work Task (AWT) Reservations and Limits” on page 7-39.

Consider scripting a set of schmon commands for each restoration and maintenance.

Exampleschmon -w 3 5 AWT Expedited work type limits res max 3 5


Chapter 7: Priority Schedulerxschmon Utility

xschmon Utility

Function

The xschmon utility is a graphical user interface X-window system that uses the OSF/Motif Toolbox to manage its window resources. xschmon allows you to display and alter Priority Scheduler parameters.

Syntax

where:

Syntax element … Specifies the …

-display display is output to a particular host, server, and screen specified.

host IP address of your machine.

server server number.

screen screen number.

GS02A009

xschmon

-display

host

server:

.screen


Chapter 7: Priority Schedulerxschmon Main Window

xschmon Main Window

When you start xschmon, the main window appears, as shown below.

The main window consists of the following attributes.

Attribute Description

Age Time The time period over which recent resource usage is measured. The default is 60 seconds.

Active Time The time period during which an allocation group is considered active if any process assigned to the group has been scheduled for execution. Inactive allocation groups are not included in resource consumption or relative weight calculations. The default is 61 seconds.

System CPU Limit (%)

A percentage value to limit the amount of CPU usage by Teradata RDBMS sessions. This usage does not include non-Teradata work, suchas time-share users, I/O or other interrupt services, Gateway processing, or streams work. The value ranges from 1 through 100.

A value of … Specifies that…

100 or none no limit is to be enforced.

1 - 99 CPU resource use is to be limited to the indicated percentage.


Chapter 7: Priority Schedulerxschmon Main Window

Dispatch Age Time (sec)

The maximum period of time 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.

A value of … Specifies …

0 that processes are not to be promoted.

1 - 127 a wait period in seconds.

Scheduler State

Displays the current states of Scheduler.

Scheduler state is … If you …

Active enabled Priority Scheduler. The default is Active.

Inactive disabled the Priority Scheduler.

Performance State

Displays the current states of Performance.

Performance state is … If you …

Response enabled the Priority Scheduler response mode. The default is Response.

Throughput disabled the Priority Scheduler throughput mode.

I/O Prio State

Displays the current states of I/O Priority.

I/O Priority state is … If you …

Prioritize enabled the Priority Scheduler prioritize mode. The default is Prioritize.

No Prioritize disabled the Priority Scheduler prioritize mode.

Attribute Description


Chapter 7: Priority SchedulerMain Window Menus

Main Window Menus

The main window contains the following menus:

• File• Edit• View• Help

The following sections describe the main window menus.


Chapter 7: Priority SchedulerFile Menu

File Menu

The File menu allows you to do the following:

• Display Priority Scheduler performance parameters• Adjust the scheduling mode switches• Exit the program

The following table describes the File menu items.

Menu item … Allows you to …

Monitor Activity monitor Priority Scheduler operational statistics using the Monitor Mode window shown below.

The Monitor Mode window is the functional equivalent to the schmon -M command, which monitors all nodes, and the schmon -m command, which monitors the current node. The Monitor Mode window consists of the following.


Chapter 7: Priority SchedulerFile Menu

Monitor Activity (cont) Window component or button

Description

Interval The interval ranges from 5 to 1800 seconds.

The minimum monitoring interval is 5 seconds.

Repetitions The display repeats for the number of repetitions.


• On MPP systems, this time varies, depending on the number of nodes and speed of response.

• On SMP systems, this time should be insignificant.

If you do not set the Repetitions field, it defaults to a value of forever.

Monitoring You can toggle among the following:

• This node only• All nodes• Cancel (stops monitoring)

Apply Modifies the settings.

Close Closes the window without changing any settings.

The settings remain if the window is re-opened.

Undo Makes all edited settings revert to the last applied settings.

Help Displays the appropriate help screen.

Settings set the following schedule state switches:

• Enable/Disable Scheduler• Optimize Response/Throughput• Prioritize/No Prioritize I/O

These switches are equivalent to the -e, -E, -i, -I, -r, and -R schmon utility options.

Exit exit xschmon.



Chapter 7: Priority SchedulerEdit Menu

Edit Menu

The Edit menu allows you to set the following:

• Resource partitions parameters• Performance groups parameters• Allocation groups parameters• General Scheduler parameters

All of the Edit windows display four buttons at the bottom of the window. The following table describes each button.

The following table describes the Edit menu items.

Button Description

Apply Modifies the settings.

Close Closes the window without changing any settings.

The settings remain if the window is re-opened.

Undo Makes all edited settings revert to the last applied settings.

Help Displays the appropriate help screen.


Resource Partition

set resource partition parameters using the Resource Partitions window shown below.

The Resource Partitions window is the functional equivalent to the schmon -b command and consists of the following.



Resource Partition (cont)

Window component … Specifies …

ID identifier number of the resource partition.

Name name of the resource partition.

Weight numeric value used to compute the percentage of resources to be assigned to this resource partition.

Limit optional number between 1 and 100, inclusive, that specifies a percentage limit on the total CPU usage by sessions assigned to the performance groups associated with the resource partition. None indicates that no limit is to be enforced.

Performance Group

set performance group parameters using the Performance Groups window shown below.

The Performance Groups window is the functional equivalent to the schmon -p command and consists of the following.

Window component … Specifies the …

ID identifier number of the performance group.

Name name of the performance group.

RP resource partition to which this performance group is to be assigned.

Value performance group value within the resource partition.

Value is a numeric value between 0 and 7 inclusive, indicating the priority of the group. Value must be unique within the resource partition.




Performance Group (cont)

Window component … Specifies the …

Type single character that specifies the type of units used in the following performance period definitions:

• Q indicates that milestone limits are seconds (01 - 86400) of query resource usage.

• R or S indicates that milestone limits are seconds (01-86400) of session resource usage.

• T indicates milestone units as time-of-day, in military time (0-2359). You must define at least two periods.

Limit[i], AG[i] up to five performance periods.

Each limit defines a period milestone (in units defined by T in Type above). The corresponding AG defines the allocation group in effect during that period.

Allocation Group

set or display allocation group parameters using the Allocation Groups window shown below.

The Allocation Groups window is the functional equivalent of the schmon -a command and consists of the following:




Allocation Group (cont)

Window component … Specifies …

ID the identifier of the allocation group.

Type a single character that indicates the type of scheduling set division enforced by the allocation group.

The resources of the allocation group are shared equally by its scheduling sets. Permissible values for Type are as follows:

• N (NONE). Allocation group resources are divided among processes:

– For all-AMP operations, each AMP counts for one process.– Each step in a parallel-step plan counts for one process.– Complex queries could be offered more system resources.• S (SESSION). Resources are divided by the number of active

sessions and then by processes:– Each query receives the same resources no matter how many

processes are involved.– This is an advantage for single-AMP queries if work within the

allocation group is mixed.

X that the allocation group is expected to process expedited work.

Policy one of the following scheduling policies:

• ABS (ABSOLUTE)• REL (RELATIVE)• IMD (IMMEDIATE)• DEF (DEFAULT)

Weight a numeric value used to compute the percent of partition resources the processes of the allocation group are to receive.




Parameters modify the current Priority Scheduler Active and Aging Times, the System CPU Limit, the Dispatch Queue Age Time, the AWT Reserve and Limit values using the Set Scheduler Times window shown below.

The Set Scheduler Times window is the functional equivalent of the schmon -t and -l commands and consists of the following:

Parameter … Is the …

Active Time (sec) time period 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 for Active Time is from 1 - 1800 seconds. The default is 61 seconds.

Age Time (sec) time period over which recent resource usage by a scheduling set is measured. The range for Age Time is from 1 - 1800 seconds. The default is 60 seconds.

System CPU Limit (%)

maximum percentage limit on total CPU usage by a node. The value ranges from 1 - 100. None indicates 100. Click the none button to set the the limit to 100.

Dispatch Queue Age Time (sec)

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 value ranges from 1 - 127. A value of 0 indicates that processes are not to be promoted. Clicking the none button sets the value to 0.




Parameters (cont)

Parameter … Is the …

AWT Reserve # number of reserve AWT processes available for use by requests controlled by allocation groups having the expedite attribute.

AWT Limit # maximum number of AWT processes available for use by requests controlled by allocation groups having the expedite attribute.

To change the current value for Active Time, Age Time, System CPU Limit, and Dispatch Queue Age Time, do the following:

• To drag the slider, click and hold while sliding.• To increment or decrement by seconds, click the hot zone with the left mouse button.• To move the slider to the cursor location, click inside the slider with the middle mouse

button.

After you apply changes made in this window, the changes will appear in the Attributes window.



Chapter 7: Priority SchedulerView Menu

View Menu

The View menu allows you to display the current settings for the following:

• Resource partitions• Performance groups• Allocation groups• Session data

For detailed information on each of these windows (except for Session data), see “Edit Menu” on page 7-95.

The following table describes the Session Data window.


Session Data view session data using the View Session window shown below.

The View Session window is the functional equivalent to the schmon -s command and consists of the following:

Node

CategorySelector

Selector


Chapter 7: Priority SchedulerView Menu

Session Data (cont)

Window component … Allows you to …

Node selector scroll bar

view session data from the following:

• This Node (the node on which xschmon is running)• All Nodes (in the system)

To toggle between the options, click the up or down arrow.

Category selector scroll bar

select from the following:

• Session #• Resource Partition (RP) ID• Performance Group (PG) ID• Allocation Group (AG) ID

To cycle through the options, click the up or down arrow.

Select All Sessions button

view data for all sessions.

Text field enter a session number, RP, PG, or AG ID to display information about sessions controlled by that scheduler group.

Session numbers are unique for each host ID. Although unlikely, duplicate session numbers might occur. Therefore, if duplicate session numbers exist, this field accepts a session number and reports data for all host IDs.

Note: This field changes depending on which category you have selected.



Chapter 7: Priority SchedulerGetting Help

Getting Help

The xschmon Help screens briefly describe each function or window. For more complete descriptions of each function or window, see “schmon Utility” on page 7-45.

To display help, click the following:

• Help menu item in the xschmon main window• Help button in any of the subwindows

The xschmon Help window is shown below.


Chapter 7: Priority SchedulerGetting Help


Chapter 8:

Query Configuration Utility

The Query Configuration utility reports the current RDBMS configuration from a system console running the Database Window or from a host terminal. This configuration was defined using the Configuration and Reconfiguration utilities. For more information, see “Configuration Utility” in Teradata RDBMS Utilities and Chapter 10: “Reconfiguration Utility.”

Query Configuration also is referred to as Configuration Display and QryConfig.

Audience

Users of Query Configuration include the following:

• NCR system engineers• Field engineers• System developers


Chapter 8: Query Configuration UtilityStarting and Exiting Query Configuration on NCR UNIX MP-RAS

Starting and Exiting Query Configuration on NCR UNIX MP-RAS


You can start and exit Query Configuration from the following:

• Database Window• Remote Console


To start Query Configuration, do the following:


To exit Query Configuration, do the following:

Step Action




start qryconfig

3 Press Enter.


Started ‘qryconfig’ in window 1.

The number represents the application window in which Query Configuration is running. The Query Configuration window appears.

Step Action

1 In the Enter a command subwindow of the Query Configuration window, type one of the following:

• END

• QUIT

2 Press Enter.


Exiting



From the Remote Console

If you access Query Configuration from the remote console, you cannot employ user IDs designating pooled sessions. Starting Query Configuration from a remote console does not require a special privilege.


For a description of how to type options and display configuration status and components, see “Query Configuration Utility” on page 8-1.

3 In the Query Configuration window, select File -> Close.


Step Action

1 At the remote console, type the following:

HUTCNS

The initial display appears as shown below.

When you type a valid tdpid, user ID, and password (except a user ID designating a pooled session), the terminal displays the following information.

2 To select the Query Configuration utility, type the following:

CON

The initial Query Configuration screen appears.

Step Action

**** **** ***** * * * ** * **** * * * * * ***** **** ****

Program: DBS Console Interface

Enter logon string as ‘TDPID/UserID,Password’

Data Base Computer

Enter the Utility to execute - SESsionStatus

- LOCKsDisplay- CONfiguration

- RCVmanager

First 3 characters are acceptable




Step Action

1 At the remote console screen, type one of the following:

• END

• QUIT

2 Press Enter.


Exiting


Chapter 8: Query Configuration UtilityStarting and Exiting Query Configuration on Microsoft Windows 2000

Starting and Exiting Query Configuration on Microsoft Windows 2000


You can start and exit Query Configuration from the following:

• Database Window• Teradata MultiTool




Step Action






start qryconfig

4 Press Enter.



The number represents the application window in which Query Configuration is running. The Query Configuration window appears.






Step Action

1 In the Enter a Command subwindow of the Query Configuration window, type one of the following:

• END

• QUIT

2 Press Enter.


Exiting

3 In the Query Configuration window, select File -> Close.


Step Action




The DBW appears.



start qryconfig

5 Press Enter.



The number represents the application window in which Query Configuration is running. The tab that previously said Application 1 now says Query Configuration and is the active window.




Step Action

1 In the DBW, select the Query Configuration tab.


• END

• QUIT

3 Press Enter.


Exiting



Chapter 8: Query Configuration UtilityAbout Query Configuration

About Query Configuration

Vprocs and Physical Processors

The Query Configuration utility displays configuration information about the node in an RDBMS. This utility supplies information about the PEs associated with the node and the AMPs.

While physical processor identifiers are presented where appropriate in the configuration displays, the focus of the Query Configuration utility is on the vprocs managed by the node.

These vprocs exist within a previously defined physical configuration. Use the pdeconfig utility to configure parts of the physical configuration, such as creating Logical Units (LUNs) on disk arrays. pdeconfig then maps the virtual components, for example, vprocs) to the physical configuration. For more detailed information, see Chapter 6: “pdeconfig Utility (NCR UNIX MP-RAS Only).”

pdeconfig automatically invokes the vconfig utility, which specifies how the virtual configuration (for example, AMP vprocs) maps to the physical configuration (for example, disk storage).

Display Options

The Query Configuration utility can display a variety of status and configuration information for the entire RDBMS or portions of the RDBMS including the following:

• Complete configuration• Node, online or offline• AMPs, online or offline• PEs, online or offline

To access these options, see “Starting and Exiting Query Configuration on NCR UNIX MP-RAS” on page 8-2.


Chapter 8: Query Configuration UtilityQuery Configuration Options

Query Configuration Options

You can display all or parts of the current RDBMS system configuration by entering various Query Configuration options.

The following sections describe the options and their use:

• ALL• Processors• Online processors• Offline processors• AMPs• Online AMPS• Offline AMPs • PEs• Online PEs• Offline PEs

In a large system configuration (the Node, and many AMPs and PEs managed by the Node), you should use discretion when selecting the All, AMPs, and Online AMPs options to display vproc level data, because of the potentially very large numbers of output lines that may be produced.

Instead of the All, AMPs, and Online AMPs options, you should consider Processor level options or the Offline AMPs and Offline PEs options when the configuration is large, to avoid having to deal with large numbers of Query Configuration output lines consuming valuable space and time resources.


Chapter 8: Query Configuration UtilityALL Option

ALL Option

To produce a display of all the components in the RDBMS and their current status, use the ALL option. The following figure is an example of an ALL display.

Enter display option, QUIT or END to terminate.all

DBS Configuration Status Report: 00/06/13 18:31:23 Vproc Node Config Config Cluster/ Vproc Node Config Config Cluster/ Number ID Type Status Host No. Number ID Type Status Host No. ------ ------- ---- -------- -------- ------ ------- ---- -------- -------- 0 1-01 AMP Online 0 1 1-01 AMP Online 0 2 1-01 AMP Online 1 3 1-01 AMP Online 1 4 1-01 AMP Online 2 5 1-01 AMP Online 2 6 1-01 AMP Online 3 7 1-01 AMP Online 3 8 1-01 AMP Online 4 9 1-01 AMP Online 4 10 1-01 AMP Online 5 11 1-01 AMP Online 5 12 1-01 AMP Online 6 13 1-01 AMP Online 6 14 1-01 AMP Online 7 15 1-01 AMP Online 7 16 1-01 AMP Online 8 17 1-01 AMP Online 8 18 1-01 AMP Online 9 19 1-01 AMP Online 9 16380 1-01 PE Online 1 16381 1-01 PE Online 1 16382 1-01 PE Online

The information in the ALL display is ordered by vproc number. The display shows the following for each vproc:

• The identifier (Node ID) of the Node associated with each vproc (virtual processor).

• The type (AMP or PE) of each vproc.• The status (online or offline) of each vproc. A status of Online means that

the associated Node is available and online to the operating system.• The cluster (for an AMP) or host number (for a PE) associated with each

vproc.


Chapter 8: Query Configuration UtilityProcessors Option

Processors Option

To obtain configuration information for all processors in the system, use the Processors option. This option produces a display identical to that produced by the “ALL Option” on page 8-10.


Chapter 8: Query Configuration UtilityOnline Processors or Offline Processors Options

Online Processors or Offline Processors Options

Configuration information for all online or all offline processors that is similar to that of all processors is also available.

To obtain configuration information for online processors, use the Online Processors option. This option includes the same information as the all processors display option with the exception of the Status column. The following figure is an example of an Online Processors display.

Enter display option, QUIT or END to terminate.online processors

DBS Configuration Status Report: 00/06/13 18:35:56 Vproc Node Config Cluster/ Vproc Node Config Cluster/ Number ID Type HostId Number ID Type Host No. ------ ------- ---- -------- ------ ------- ---- -------- 0 1-01 AMP 0 1 1-01 AMP 0 2 1-01 AMP 1 3 1-01 AMP 1 4 1-01 AMP 2 5 1-01 AMP 2 6 1-01 AMP 3 7 1-01 AMP 3 8 1-01 AMP 4 9 1-01 AMP 4 10 1-01 AMP 5 11 1-01 AMP 5 12 1-01 AMP 6 13 1-01 AMP 6 14 1-01 AMP 7 15 1-01 AMP 7 16 1-01 AMP 8 17 1-01 AMP 8 18 1-01 AMP 9 19 1-01 AMP 9 16380 1-01 PE 1 16381 1-01 PE 1 16382 1-01 PE 1 16383 1-01 PE 1

To obtain configuration information for offline processors, use the Offline Processors option. The information displayed is similar to that for all processors, but the Status column does not appear, since only offline processors are displayed.


Chapter 8: Query Configuration UtilityAMPs Option

AMPs Option

To obtain configuration information for all AMPs in the system, use the AMPs option. It produces a display containing AMP numbers, node identifiers, status (online or offline), and cluster numbers. The following figure is an example of an AMPs configuration display.

Enter display option, QUIT or END to terminate.amps DBS Configuration Status Report: 00/06/13 18:38:20 Vproc Node Config Config Cluster/ Vproc Node Config Config Cluster/ Number ID Type Status Host No. Number ID Type Status Host No. ------ ------- ---- -------- -------- ------ ------- ---- -------- -------- 0 1-01 AMP Online 0 1 1-01 AMP Online 0 2 1-01 AMP Online 1 3 1-01 AMP Online 1 4 1-01 AMP Online 2 5 1-01 AMP Online 2 6 1-01 AMP Online 3 7 1-01 AMP Online 3 8 1-01 AMP Online 4 9 1-01 AMP Online 4 10 1-01 AMP Online 5 11 1-01 AMP Online 5 12 1-01 AMP Online 6 13 1-01 AMP Online 6 14 1-01 AMP Online 7 15 1-01 AMP Online 7 16 1-01 AMP Online 8 17 1-01 AMP Online 8 18 1-01 AMP Online 9 19 1-01 AMP Online 9


Chapter 8: Query Configuration UtilityOnline AMPS or Offline AMPs Options

Online AMPS or Offline AMPs Options

The same type of configuration information previously described for all AMPs is also available for all online or all offline AMPs.

To obtain configuration information for online AMPs, use the Online AMPs option. The information displayed is similar to that for all AMPs, but the Status column does not appear, since only online AMPs are displayed.

To obtain configuration information for offline AMPs, use the Offline AMPs option. The information displayed is similar to that for all AMPs, but the Status column does not appear, since only offline AMPs are displayed.


Chapter 8: Query Configuration UtilityPEs Option

PEs Option

To obtain configuration information for all PEs in the system, use the PEs option. It produces a display containing PE numbers, node identifiers, status (online or offline), and host numbers. The following is an example of a PEs configuration display.

Enter display option, QUIT or END to terminate.pes

DBS Configuration Status Report: 00/06/13 18:44:20 Vproc Node Config Config Cluster/ Vproc Node Config Config Cluster/ Number ID Type Status Host No. Number ID Type Status Host No. ------ ------- ---- -------- -------- ------ ------- ---- -------- -------- 16380 1-01 PE Online 1 16381 1-01 PE Online 1 16382 1-01 PE Online 1 16383 1-01 PE Online 1


Chapter 8: Query Configuration UtilityOnline PEs and Offline PEs Options

Online PEs and Offline PEs Options

The same type of configuration information available as described above for all PEs is also available for all online or all offline PEs.

To obtain configuration information for online PEs, use the Online PEs option. The information displayed is similar to that for all PEs, but the status is Online for each PE listed.

To obtain configuration information for offline PEs, use the Offline PEs option. The information displayed is similar to that for all PEs, but the status is Offline for each PE listed.


Chapter 8: Query Configuration UtilityGetting HELP

Getting HELP

To produce a list of all of the Query Configuration options, type HELP or question mark (?). The list of options displays as follows:

Enter display option, QUIT or END to terminate.help

The following key words return the indicated display. All; - complete configuration. Processors; - processor status. Online Processors; - online processors. Offline Processors; - offline processors. AMPs; - AMP status. Online AMPs; - online AMPs. Offline AMPs; - offline AMPs. PEs; - PE status. Online PEs; - online PEs. Offline PEs; - offline PEs.

As indicated in the HELP option list, type a keyword to produce the desired display.


Chapter 8: Query Configuration UtilityGetting HELP


Chapter 9:

Query Session Utility

Query Session provides information about active Teradata sessions. It allows you to monitor the state of all or selected database sessions on all or selected logical host IDs attached to the Teradata RDBMS. Query Session also is known as Session States.

This chapter provides an overview of the information Query Session reports as well as several sample Query Session displays.

Because the Query Session displays for sessions involved in Archive and Recovery, FastLoad, MultiLoad (MLOAD), and FastExport operations are different from other session displays, these displays are described at the end of this chapter.

Audience

Users of Query Session include the following:

• Teradata RDBMS operators• System programmers• System administrators


Chapter 9: Query Session UtilityStarting and Exiting Query Session on NCR UNIX MP-RAS

Starting and Exiting Query Session on NCR UNIX MP-RAS


You can start and exit Query Session from the following:



To start Query Session, do the following:

Step Action




start qrysessn

3 Press Enter.


Started ‘Qrysessn’ in window 1at Thu Jun 15 16:59:00 2000

The number represents the application window in which Query Session is running. The Query Session window appears.

Note: The Query Session date format is year, month, and date (yy/mm/dd).

4 Enter the Logical Host ID or type an asterisk to report specified sessions for every logical host or a question mark to view help.

For more information on what you can input, see “Query Session Displays” on page 9-10.

When you type the Logical Host ID or an asterisk (*), you are prompted for the following:

Please Enter Session Ids (? For Help)

5 Enter the session IDs, an asterisk, or a question mark to view help on what you are allowed to input.

For more information on what you can input, see “Query Session Displays” on page 9-10.




To exit Query Session, do the following:


If you start Query Session from a remote console, you cannot use user IDs designating session pools. Starting Query Session from a remote console does not require a special privilege.

Step Action

1 You can exit Query Session in one of the following ways:

• Without entering anything in the Enter a command subwindow of the application window, press Enter. The system displays this message:QrySession Has Terminated.

or

• In the Enter a command subwindow of the application window, type the following:quit;

The system displays this message:QrySession has terminated.

2 In the Query Session window, select File -> Close.

3 In the Supervisor window, select File -> select Close.





Step Action


HUTCNS

You should see the initial Query Session display, as shown below.

**** **** **** Data Base Computer* * * * ** * **** * Program: DBS Console Interface* * * * ***** **** ****Enter logon string as ‘TDPID/UserID,Password’

2 Enter a valid tdpid, user ID, and password (except user IDs designating pooled sessions).

The following is displayed:

Enter the Utility to execute - SESsion Status

- Configuration

- LOCKsDisplay

- RCVmanager


Enter QUIT, END or STOP to terminate.

3 To start Query Session, type the following:

SES

The initial Query Session screen appears.

4 Enter responses to Query Session prompts as you normally would type commands at your remote console.

Step Action

1 At the remote console, type one of the following:

• END

• QUIT

Query Session terminates and displays this message:

Exiting


Chapter 9: Query Session UtilityStarting and Exiting Query Session on Microsoft Windows 2000

Starting and Exiting Query Session on Microsoft Windows 2000


You can start and exit Query Session from the following:





Step Action






start qrysessn

4 Press Enter.


Started ‘qrysessn’ in window 1.

Note: The Query Session date format is year, month, and date (yy/mm/dd).

The number represents the application window in which Query Session is running. The Query Session window appears.






Step Action


• Without entering anything in the Enter a command subwindow of the application window, press Enter. The system displays this message:QrySession Has Terminated.

or

• In the Enter a command subwindow of the application window, type the following and press Enter:quit;

The system displays this message:

QrySession has terminated.

2 In the Query Session window, select File -> Close.


Step Action




The DBW appears.



start qrysessn

5 Press Enter.


Started ‘qrysessn’ in window 1.

The number represents the application window in which Query Session is running. The tab that previously said Application 1 now says Query Session and is the active window.




Step Action

1 In the DBW window, select the Query Session tab.


• Without entering anything in the Command field, press Enter. The system displays this message:QrySession Has Terminated.

or

• In the Command field, type the following and press Enter:quit;

The system displays this message:QrySession has terminated.



Chapter 9: Query Session UtilityQuery Session States

Query Session States

Query Session provides information that a session can type on the following possible states.

The Session State … Indicates that …

ABORTING the session is aborting its latest request.

ACTIVE the session has sent steps to the dispatcher and possibly to one or more AMP vprocs.

BLOCKED an active session is waiting for a database lock to be released.

IDLE the RDBMS recognizes a session, but no processing is taking place.

INDOUBT a two-phase commit session is in doubt.

INDOUBT PARSING a two-phase commit session is in doubt and is parsing a vote or commit request.

PARSING the session is active in the Teradata SQL parser phase, before the steps are dispatched to the AMP vprocs.

QUIESCED ABORT the session is blocked from executing further requests because transactions associated with this session are being aborted.

QUIESCED ABORT WITH LOGOFF

the session is quiesced because the transactions or requests associated with this session are being aborted, after which this session will be logged off the machine.

QUIESCED INDOUBT the session is blocked from exercising further requests because the outstanding transaction/request will be terminated.

RESPONSE a response to a session request is in process.


Chapter 9: Query Session UtilityParent and Child Sessions

Parent and Child Sessions

When a connected session is part of either a FastLoad, MultiLoad, FastExport, or Archive and Recovery operation, that session establishes subordinate sessions to accomplish the task more quickly. The originating session is then called a Parent session; the subordinate sessions are called Child sessions that belong to that Parent.

A Child session is not recognized as such, and its activity is not reported until it has transmitted at least one request to the AMPs in the current transaction.

Information about the activity of Child sessions is available to Query Session when the Parent session is in the Active state or when one of several inactive states described later in this chapter.

The following table describes when Child sessions are reported.

Query Session reports the status of Child sessions when you request detail information.

In … Child sessions exist and are reported only while the Parent session is in the …

FastLoad operations

loading phase.

MultiLoad operations

acquisition phase.


Chapter 9: Query Session UtilityQuery Session Displays

Query Session Displays

The following sections describe the Query Session displays that provide information on what you can input. General Help displays are described first, followed by displays for sessions involved in Archive and Recovery, FastLoad, FastExport, and MultiLoad operations.

After you have started Query Session, it prompts for the following:

Please Enter A Logical Host ID (? For Help)

You can type any of the following responses when you are prompted for the logical host ID.

If you type an integer or an asterisk, the following prompt displays:

Please Enter Session Ids (? For Help):

You can input any of the following when you are prompted for the Session ID.

IF you type … THEN you will …

an integer be asked for a specific logical host ID.

an asterisk (*) get all host IDs.

a question mark (?) get Help for this entry.

a carriage return (Enter) exit from the Query Session utility.

IF you type … THEN you see …

an integer to indicate a specific session ID

Note: Up to five session Ids, in integer format can be input. They can be entered on one or multiple lines or separated by a space.

the following prompt:

Detail Information Needed if the session involved in HUT/FastLoad/MLoad/Export?

y-yes, n-no

IF you type … THEN …

y to view the Child session states.

n if the session is not part of a FastLoad, MultiLoad, FastExport, or an Archive and Recovery operation.


Chapter 9: Query Session UtilityQuery Session Displays

Note: If an unsuccessful attempt was made to obtain temporary table information for the given session, the following query session message could display:

WARNING: Session may contain incomplete temporary table information due to deadlock!

If temporary table information is important to you, then you should retry querying the session at a later time.

an asterisk (*) the following prompt:

Detail Information Needed if the session involved in HUT/FastLoad/MLoad/Export?

y-yes, n-no

IF you type … THEN …

y to view the Child session states.

n if the session is not part of a FastLoad, MultiLoad, FastExport, or an Archive and Recovery operation.

a question mark help concerning input information.

IF you type … THEN you see …


Chapter 9: Query Session UtilitySession State Display

Session State Display

The session state display consists of session identifier information and session state details. Displays for sessions involved in FastLoad, MultiLoad, FastExport, or Archive and Recovery operations provide additional information described later in this chapter.

If a session is idle, only the session identifier information is displayed, as shown below.

Host Session PE DBC User ID---- ------- -- -----------110 1006 11 DBC

The columns for the Session Identifier display the following information.

If a session is active, and not part of a FastLoad, MultiLoad, FastExport, or Archive and Recovery operation, the following session state detail information displays.

Session State Query Results : 00/06/15 14:14:13


State Details : ACTIVE

Statements Dispatched Time CPU Usage Accesses---------- ---------- -------- --------- --------

1 1 14:22:09 2 22

The column named … Contains the …

Host logical host identifier.

Session session identifier.

PE PE number of the PE to which the session is assigned.

DBC User ID user assigned to the session.


Chapter 9: Query Session UtilitySession State Display

Session State Details During Stored Procedure Execution

If a stored procedure is being executed, the following session state information is displayed.



State Details : ACTIVE (Stored Procedure is executing)

The State Details correspond to the latest SQL request that the stored procedure executed.

Session State Details Pertaining to the Teradata Index Wizard

Query Session reports the index analysis state pertaining to the Teradata Index Wizard. If a workload is being analyzed for indexes, the following session state information is displayed.


Host Session PE DBC User ID---- ------- ----- -----------

52 1893 16383 USER1 State Details: <status> Analyzing a workload for index recommendations.


Chapter 9: Query Session UtilityState Information Displays

State Information Displays

This following sections provides session information for each possible state:

• ABORTING• ACTIVE• BLOCKED• IDLE• INDOUBT• INDOUBT PARSING• PARSING• QUIESCED ABORT• QUIESCED ABORT WITH LOGOFF• QUIESCED INDOUBT• RESPONSE


Chapter 9: Query Session UtilityABORTING State

ABORTING State

The ABORTING state indicates that the session is aborting its latest request.

The ABORTING state display is shown below.

State Details : ABORTING

Statements Code Time CPU Usage Accesses---------- ---- -------- --------- --------

1 1043 14:22:09 2 22

The columns on the ABORTING state display provide the following information.


Statements statements up to the number displayed are aborting.

Code error that caused the abort.

Time time that the abort step was sent to the AMP.

CPU Usage accumulated time in thousandths of a second that all AMPs spent processing the current request.

Accesses total number of segment access calls executed on all AMPs for the session request.


Chapter 9: Query Session UtilityACTIVE State

ACTIVE State

The ACTIVE state indicates that the session has sent steps to the dispatcher and possibly to one or more AMP vprocs.

The ACTIVE state display for a session not part of a FastLoad, MultiLoad, FastExport or Archive and Recovery operation is shown below.

State Details : ACTIVE


1 1 14:22:09 2 22

The columns on the ACTIVE state display provide the following information.


Statements total number of statements in the current session request.

Dispatched highest statement number dispatched to the AMPs.

Time time that the last step in the highest statement number was sent to the AMPs.




Chapter 9: Query Session UtilityBLOCKED State

BLOCKED State

The BLOCKED state indicates that an active session is waiting for a database lock to be released.

The BLOCKED state display for a session is shown below.

State Details : BLOCKED

Resource-------------------------------------------------------X.T

Statement AMPs Mode AMP Vproc HUT--------- ---- ---- --------- ---

1 1 READ 19 NO

The columns on the BLOCKED state display provide the following information.


Resource database or table for which the lock is requested.

IF the lock is requested for a … THEN this column displays the information …

database X.*

where:

X is the database name.

table or row X.T

where:

X is the database name, and T is the table name.

Statement highest statement number for which steps have been dispatched to the AMPs.

AMPs number of AMPs for which the session is waiting to acquire a lock.

Mode type of lock requested by the session.

AMP Vproc number of the AMP with the blocked session.

HUT host utility lock (if encountered).


Chapter 9: Query Session UtilityIDLE State

IDLE State

The IDLE state indicates that the RDBMS recognizes a session, but no processing is taking place.

The IDLE state display for a session is shown below.

State Details : IDLE


Chapter 9: Query Session UtilityINDOUBT State

INDOUBT State

The INDOUBT state indicates that a two-phase commit session is in doubt. This state continues until an abort or commit is received from the host application.

The INDOUBT state display for a session is shown below.

State Details : INDOUBT


Chapter 9: Query Session UtilityINDOUBT PARSING State

INDOUBT PARSING State

The INDOUBT PARSING state indicates that a two-phase commit session is in doubt and is parsing a vote or commit request.

The INDOUBT PARSING state display for a session is shown below.

State Details : INDOUBT PARSING


Chapter 9: Query Session UtilityPARSING State

PARSING State

The PARSING state indicates that the session is active in the Teradata SQL parser phase, before the steps are dispatched to the AMP vprocs. The PARSING state displays no column information and only the word PARSING.

The PARSING state for a session display is shown below.

State Details : PARSING


Chapter 9: Query Session UtilityQUIESCED ABORT State

QUIESCED ABORT State

The QUIESCED ABORT state indicates that the session is blocked from executing further requests because transactions associated with this session are being aborted. The outstanding transaction or request will be aborted by the performance monitor.

The QUIESCED ABORT state for a session display is shown below.

State Details : QUIESCED ABORT


Chapter 9: Query Session UtilityQUIESCED ABORT WITH LOGOFF State

QUIESCED ABORT WITH LOGOFF State

The QUIESCED ABORT WITH LOGOFF state indicates that the session is quiesced because the transactions or requests associated with this session are being aborted by the system or the performance monitor. The session is logged off.

The QUIESCED ABORT WITH LOGOFF state for a session display is shown below.

State Details : QUIESCED ABORT WITH LOGOFF


Chapter 9: Query Session UtilityQUIESCED INDOUBT State

QUIESCED INDOUBT State

The QUIESCED INDOUBT state indicates that the session is blocked from exercising further requests because the outstanding transaction/request will be terminated by the resolver base module.

The QUIESCED INDOUBT state for a session display is shown below.

State Details : QUIESCED INDOUBT


Chapter 9: Query Session UtilityRESPONSE State

RESPONSE State

The RESPONSE state indicates a response to a session request is in process.

The RESPONSE state for a session display is shown below.

State Details : RESPONSE

Statements----------

1

This column for the RESPONSE display contains the following information.


Statements highest statement number for which a response has been returned to the host or the stored procedure in execution.


Chapter 9: Query Session UtilityArchive and Recovery Sessions State Displays

Archive and Recovery Sessions State Displays

Several displays for sessions are part of the Archive and Recovery operations. If you request detail information, Query Session reports child sessions and the parent information.

The following sections describe these displays:

• Active Parent Session with Regular Request• Active Parent Session with Directed Request• Inactive Parent Session• Child Session


Chapter 9: Query Session UtilityActive Parent Session with Regular Request Display

Active Parent Session with Regular Request Display

The following figure shows an example display for a parent session involved in an Archive and Recovery operation.

State Details : Active Parent Session with regular request involved in HUT.Operation: Restore

Statements Dispatched Time CPU Usage Accesses Byte Count---------- ---------- -------- --------- -------- ----------

1 1 14:22:09 2 22 2,367

The Active State Display for a parent session involved in processing an Archive and Recovery request contains the following information.




Time time that the last step for the highest statement number was sent to the AMPs.



Byte Count total number of bytes accessed by the Archive and Recovery operation.


Chapter 9: Query Session UtilityActive Parent Session with Directed Request Display

Active Parent Session with Directed Request Display

The following figure shows an example display for a parent session involved in an Archive and Recovery operation processing a directed request.

State Details : Active Parent Session with directed request involved in HUT.

Request # Operation Time CPU Usage Accesses Byte Count--------- --------- -------- --------- -------- ----------

1 Restore 14:22:09 2 22 6,234

The directed request active state display for a parent session involved in processing an Archive and Recovery request contains the following information.


Request # number of the request.

Operation type of operation being performed.

Time time that the last step for the highest statement was sent to the AMPs.





Chapter 9: Query Session UtilityInactive Parent Session Display

Inactive Parent Session Display

The following figure shows an example display for an inactive parent session involved in an Archive and Recovery operation.

State Details : Inactive Parent Session involved in HUT.

Operation CPU Usage Accesses Byte Count--------- --------- -------- ----------Restore 1,234 9,543 1,259,234

The inactive state display for a parent session involved in processing an Archive and Recovery request contains the following information.


Operation type of operation being performed.





Chapter 9: Query Session UtilityChild Session Display

Child Session Display

The following figure shows an example display for child sessions involved in an Archive and Recovery operation.

Session # Request # State TimeStamp Byte Count--------- --------- -------- --------- ----------

1063 1759 Inactive 17:57:21 1,0231064 1755 Active 17:57:30 691065 1754 Inactive 17:57:41 3,024

Child sessions involved in Archive and Recovery operations display these columns.


Session # session identifier.


State state of the session, indicating whether the session is active or inactive.

TimeStamp time that is updated whenever a request is received from the host, a request is re-initiated to another AMP, or a response is sent to the host.

Byte Count total number of bytes accessed by the session.


Chapter 9: Query Session UtilityFastLoad Sessions State Displays

FastLoad Sessions State Displays

Several displays for sessions are part of FastLoad operations.

The following sections describe those displays:

• Active Parent Session in a Loading Phase• Active Parent Session in a Nonloading Phase• Inactive Parent Session in a Loading Phase• Inactive Parent Session in a Nonloading Phase• Child Sessions

If you request detail information, Query Session reports child sessions as well. These displays are identified after the phrase State Details by two lines describing the current phase.

Information for a FastLoad session in the loading phase is different from information for a non-loading phase of FastLoad.


Chapter 9: Query Session UtilityActive Parent Session in a Loading Phase Display

Active Parent Session in a Loading Phase Display

The following figure is an example display for an active parent session for a FastLoad operation in the loading phase.

State Details : Active Parent Session involved in FASTLOAD utilityFastLoad Phase : Loading

Statements Dispatched Time CPU Usage Accesses Row Count---------- ---------- -------- --------- -------- ---------

1 1 14:22:09 15,110 6,462 2,060

The display for an active parent session in the loading phase of a FastLoad operation contains the following information.







Row Count total number of rows loaded by the FastLoad utility.


Chapter 9: Query Session UtilityActive Parent Session in a Nonloading Phase Display

Active Parent Session in a Nonloading Phase Display

The following figure shows an example display for an active parent session of a FastLoad operation in any phase other than the loading phase.

State Details : Active Parent Session involved in FASTLOAD utilityFastLoad Phase : LoadPending


1 1 14:22:09 2 22

The display for an active parent session in any phase other than the loading phase of a FastLoad operation contains the following information.








Chapter 9: Query Session UtilityInactive Parent Session in a Loading Phase Display

Inactive Parent Session in a Loading Phase Display

The following figure shows an example display for an inactive parent session of a FastLoad operation in the loading phase.

State Details : Inactive Parent Session involved in FASTLOAD utilityFastLoad Phase : Loading

CPU Usage Accesses Row Count--------- -------- ---------

234 567 456,321

The display for an inactive parent session in the loading phase of a FastLoad operation contains the following information.




Row Count total number of rows loaded by the FastLoad utility.


Chapter 9: Query Session UtilityInactive Parent Session in a Nonloading Phase Display

Inactive Parent Session in a Nonloading Phase Display

The following figure shows an example display for an inactive parent session involved in a FastLoad operation in any phase other than the loading phase.

State Details : Inactive Parent Session involved in FASTLOAD utility.FastLoad Phase : Load Pending

CPU Usage Accesses--------- --------

65 870

The inactive parent session display for sessions involved in any phase other than the loading phase contains the following information.





Chapter 9: Query Session UtilityChild Sessions Display

Child Sessions Display

A FastLoad operation only involves child sessions when in the loading phase.

If the parent of the queried child session is not in the loading phase, the child session information is not available. The following figure shows an example display for child sessions involved in a FastLoad operation when the long form of the display is requested in response to the Detail Information Needed prompt.

Session # Request # State TimeStamp Byte Count--------- --------- -------- --------- ----------

1055 1632 Inactive 15:57:10 5,2861056 1635 Active 15:57:23 372

The display for Child sessions involved in FastLoad operations contain the following information.


Sessions# session identifier.



TimeStamp time that is updated whenever a request is received from the host, a request is reinitiated to another AMP, or a response is sent to a host.

Row Count total number of rows loaded by the session.


Chapter 9: Query Session UtilityMultiLoad Sessions State Displays

MultiLoad Sessions State Displays

Several displays are defined for the sessions which are part of MultiLoad operations.

The following sections describe those displays:

• Preliminary Phase Sessions• Application Phase Session for Apply Task• Application Phase Session for Delete Task• Active Parent Session in an Acquisition Phase• Inactive Parent Session in an Acquisition Phase• Child Session in an Acquisition Phase

In addition to the phrase State Detail line, a line describing the current phase is displayed.

If the session is in the Preliminary or Application phase, the current task type (Delete or Apply) is displayed. The information displayed is different for each phase: Preliminary, Application, and Acquisition. In the Application phase, each of the two task types is displayed.

When the action involves more than one AMP, row count summaries are meaningless and are not reported.


Chapter 9: Query Session UtilityPreliminary Phase Session Display

Preliminary Phase Session Display

The following figure shows an example display for a session, which is part of a MultiLoad operation, in the Preliminary phase.

State Details : Session involved in MLOAD utilityMLoad Phase : Preliminary - Received all DML Steps.Task Running : Apply Task

Statements Dispatched Time CPU Usage Accesses DMLCount---------- ---------- -------- --------- -------- --------

10 2 12:09:09 7 15 5

The possible tasks include Apply Task and Delete Task. These are the Subphases:

• No MLOAD step has been received.• Receiving MLOAD step.• Received all MLOAD steps.• Received all DML (Data Manipulation Language) steps.

The state display for the preliminary phase of a MultiLoad operation contains the following information.







DML Count number of DML steps received if the current phase is Received all DML Steps.


Chapter 9: Query Session UtilityApplication Phase Session for Apply Task Display

Application Phase Session for Apply Task Display

The Query Session display for each table during an Apply Task includes the name of the database and table, the current action, the number of workrows applied, and the total number of workrows. The following figure shows an example display for a session involved in a MultiLoad operation during an Apply Task.

State Details : Session involved in MLOAD utilityMLoad Phase : Application.Task Running : Apply Task


1 1 11:09:37 811751 349,637

DataBase.Table = SPOOL_RES.WT_TDEM_PAIMT_MEDAction = Process Data and Secondary index# of WorkRows applied = 1,210,838Total # of WorkRows = 51,639,908# of NUSI change rows applied = 0Total # of NUSI change rows = 0

The display for active parent sessions involved in the Apply Task of a MultiLoad operation provides the following information.








Chapter 9: Query Session UtilityApplication Phase Session for Apply Task Display

In addition, the display provides the following information.

Field Description

DataBase.Table Identifies the table on which the MultiLoad operation is running.

Action Describes the action being performed in the MultiLoad session.

# of WorkRows applied Displays the number of work rows processed in the apply phase.

Total # of WorkRows Displays the total number of rows processed.

# of NUSI change rows applied

Number of nonunique secondary index rows processed in the apply phase.

Total # of NUSI change rows

Total number of nonunique secondary index rows processed.


Chapter 9: Query Session UtilityApplication Phase Session for Delete Task Display

Application Phase Session for Delete Task Display

The following figure shows the Query Session display for each table during a Delete Task, which includes the name of the database and table, the current action, the number of rows scanned, and the number of rows deleted.

State Details : Session involved in MLOAD utilityMLoad Phase : Application.Task Running : Delete Task


3 3 11:24:32 844679 310,987

DataBase.Table = SPOOL_RES.WT_TDEM_PAIMT_MEDAction = Process Data# of rows scanned = 22,357# of rows deleted = 245,349

Note: The values shown include both the primary and the fallback count.

The Delete Task display for a MultiLoad operation contains the same information as described for the Apply Task display except that it reports the number of rows processed and deleted rather than the rows processed by the apply phase.


Chapter 9: Query Session UtilityActive Parent Session in an Acquisition Phase Display

Active Parent Session in an Acquisition Phase Display

The following figure shows an example display for an active parent session which is part of a MultiLoad operation.

State Details : Active Parent Session involved in MLOAD utilityMLoad Phase : Acquisition - Data Loading is in progress.

Statements Dispatched Time CPU Usage Accesses Row Count---------- ---------- -------- --------- -------- ---------

1 1 09:23:45 8 166 9,854

If you request detail information, Query Session reports child sessions as well. These are the descriptions of the phase:

• Data Loading is in progress.• Data Loading is complete.

The display for active parent sessions involved in MultiLoad operations provides the following information.







Row Count total number of rows processed by the MultiLoad task.


Chapter 9: Query Session UtilityInactive Parent Session in an Acquisition Phase Display

Inactive Parent Session in an Acquisition Phase Display

The following figure is an example display for an inactive parent session that is part of a MultiLoad operation.

State Details: InActive Parent Session involved in MLOAD UtilityMLoad Phase : Acquisition - Data Loading is complete.

CPU Usage Accesses Row Count--------- -------- ---------

130 654 45,673

These are the possible descriptions of the phase:

• Data Loading is in progress.• Data Loading is complete.

The display for inactive parent sessions involved in a MultiLoad operation contains the following information.




Row Count total number of rows processed by the MultiLoad task.


Chapter 9: Query Session UtilityChild Session in an Acquisition Phase Display

Child Session in an Acquisition Phase Display

The following figure shows an example display for child sessions involved in a MultiLoad operation when the long form of the display is requested in response to the Detail Information Needed prompt.

State Details: CHILD session involved in MLOAD Acquisition Phase

Session # Request # State TimeStamp Row Count--------- --------- -------- --------- ---------

1055 1632 Inactive 15:57:10 5,2861056 1635 Active 15:57:23 372

Child sessions involved in MultiLoad operations display these columns.


Session # session identifier.



TimeStamp time that is updated whenever a request is received from the host, a request is reinitiated to another AMP, or a response is sent to the host.

Row Count total number of rows loaded by the session.


Chapter 9: Query Session UtilityFastExport Sessions State Displays

FastExport Sessions State Displays

FastExport of data includes sessions under which Teradata SQL statements are executed, as well as sessions used to transfer response data to the host.

The Teradata SQL session assumes one of five sequential states:

• Executing the select• Releasing resource locks• Vertical data redistribution• Horizontal data redistribution• Inactive

Vertical data redistribution and horizontal data redistribution are processes executed to prepare the response data from a SELECT request for transfer back to the host. Vertical redistribution occurs only if the SELECT contains an ORDER BY clause. The idle state occurs before the select request is transmitted to the RDBMS, or while the FastExport sessions are transmitting data to the host.

FastExport sessions are children of the Teradata SQL session which executes the select request. A child session exists in one of two states. A child session in the inactive state means that either the select has not completed, or that the host utility has not yet issued a request for this child session in returning response data. A child session in the active state is currently transmitting response data.

Like FastLoad and MultiLoad, the FastExport utility executes bulk activities. The RDBMS limits the maximum number of load operations (that is, FastExport, FastLoad, or MultiLoad) to the number specified in DBS Control field MaxLoadTasks.

Examples of Teradata SQL sessions involved in FastExport activity, and examples of the output for a FastExport session are shown in the following sections.



Teradata SQL Session - Releasing Locks

The following figure shows a display of a single FastExport Teradata SQL session in release locks state.


Host Session PE DBC User ID---- ------- --- -----------114 1090 1-4 DBC

State Details : Active PARENT session involved in FastExport

FastExport Phase : Vertical redistribution.


1 1 18:35:54 6174 2,922

Detail information for CHILDREN sessions in FastExport Util.

Session # Request # State --------- --------- --------

1091 0 Inactive 1092 0 Inactive 1093 0 Inactive 1094 0 Inactive



Teradata SQL Session - Vertical Redistribution

The following figure shows a display of the Teradata SQL session in the vertical redistribution state. The select request consists of a single select statement.




FastExport Phase : Vertical redistribution.


1 1 18:37:54 6603 3,314




The following figure shows an example that the RDBMS continues to process the vertical redistribution phase.




FastExport Phase : Horizontal redistribution.


1 1 18:42:35 6603 3,314






The CPU Usage and the Accesses counts have increased, indicating the system is in operation.



Teradata SQL Session - Horizontal Redistribution

With the Teradata SQL session in the horizontal redistribution state, the display might take the form shown in the following figure.




FastExport Phase : Horizontal redistribution.


1 1 18:42:35 7893 5,305






FastExport Session - Inactive

The following figure shows that the FastExport session is inactive, waiting for the select to complete.


Host Session PE DBC User ID---- ------- --- -----------114 1091 N/A DBC

State Details : Child Session involved in FastExport Utility

FastExport Phase : Returning data.

Request # State Parent Session--------- -------- --------------

0 Inactive 1069



FastExport Session - Data Transmission

The following figure shows FastExport returning data. This child session has returned one data block to the host for the first select statement, where the response data contains 69 blocks.


Host Session PE DBC User ID---- ------- --- -----------114 1091 N/A DBC



Request # State Statement Blocks Returned Total Block--------- -------- --------- --------------- -----------

1000 Active 1 4 69

FastExport transmission continues. As shown in the following figure, the session has returned four data blocks to the host. In this way, the user is able to monitor the progress of the data transmission phase.





Request # State Statement Blocks Returned Total Block--------- -------- --------- --------------- -----------

1003 Active 1 4 69


Chapter 10:

Reconfiguration Utility

The Reconfiguration and Configuration utilities are used to define the AMPs and PEs that operate together as a Teradata Relational Database Management System (RDBMS). (Configuration is described in an earlier chapter of this manual.)

Reconfiguration is the second step of the configuration and reconfiguration process that defines or modifies an RDBMS. Reconfiguration implements the system that is described in the new configuration map created in a previous Configuration utility session.

The Reconfiguration utility is most often used when adding nodes to an existing configuration. In addition, use the Reconfiguration utility to change the following:

• Relationships of AMP and PE vprocs to nodes • Clustering of AMP vprocs

Audience

Users of Reconfiguration include the following:



Chapter 10: Reconfiguration UtilityBefore Starting Reconfiguration

Before Starting Reconfiguration

Before starting Reconfiguration, verify the following:

• Hardware is in place, properly configured, and online. Hardware configuration is detailed in the hardware service manuals for your system.

• Use the Vproc Manager utility to ensure all AMP-to-PE vprocs are online and ready. For more information, see Chapter 10: “Vproc Manager Utility.”

• Run the CheckTable utility CHECK command at the PENDINGOP level to verify that no tables are in pending status. The command is as follows:CHECK ALL TABLES AT LEVEL PENDINGOP SKIPLOCKS PRIORITY = H;

Do not use the CHECK command with the PARALLEL option when using the PENDINGOP option and with users logged on. A hang will occur. For more information, see the CheckTable utility in Teradata RDBMS Utilities.

• Logons are disabled, and the RDBMS is in a quiescent state.

Disabling Logons

To disable logons and quiesce the RDBMS, do the following:

Note: After you exit Reconfiguration, you must enable logons. See “Enabling Logons” on page 10-3.

Step Action




DISABLE LOGONS

This command denies user access to the RDBMS by disabling logons.

3 Press Enter.


Logons disabled.


Chapter 10: Reconfiguration UtilityBefore Starting Reconfiguration

Enabling Logons

After Reconfiguration has completed, you must enable the logons.

To enable the logons, do the following:

Step Action


ENABLE LOGONS

2 Press Enter.


Chapter 10: Reconfiguration UtilityStarting and Exiting Reconfiguration on NCR UNIX MP-RAS

Starting and Exiting Reconfiguration on NCR UNIX MP-RAS

Before you start Reconfiguration, you must disable logons. For more information, see “Disabling Logons” on page 10-2.


You can start and exit Reconfiguration from the Database Window.

After you exit Reconfiguration, you must enable logons. For more information, see “Enabling Logons” on page 10-3.

To start Reconfiguration, do the following:


Step Action




start reconfig

3 Press Enter.


Started ‘reconfig’ in window 1

The number represents the application window in which Reconfiguration is running. The Reconfiguration window appears.


Chapter 10: Reconfiguration UtilityStarting and Exiting Reconfiguration on NCR UNIX MP-RAS

To exit Reconfiguration, do the following:

Step Action

1 In the Enter a command subwindow of the Reconfiguration utility, do one of the following:

• Enter Stop and press Enter.• Press F3.


Reconfig is about to be stopped.

2 In the Reconfiguration window, select File -> Close.



Chapter 10: Reconfiguration UtilityStarting and Exiting Reconfiguration on Microsoft Windows 2000

Starting and Exiting Reconfiguration on Microsoft Windows 2000

Before you start Reconfiguration, you must disable logons. For more information, see “Disabling Logons” on page 10-2.


You can start and exit Reconfiguration from the following:


After you exit Reconfiguration, you must enable logons. For more information, see “Enabling Logons” on page 10-3.



Note: For details on the Database and Supervisor Windows, see Teradata Database Window.

Step Action




start reconfig

3 Press Enter.


Started ‘reconfig’ in window 1

The number represents the application window in which Reconfiguration is running. The Reconfiguration window appears.






Step Action

1 In the Enter a command subwindow of the Reconfiguration utility, do one of the following:

• Enter Stop and press Enter.• Press F3.


Reconfig is about to be stopped.

2 In the Reconfiguration window, select File -> Close.


Step Action




The DBW appears.



start reconfig

5 Press Enter.


Started ‘reconfig’ in window 1.

The number represents the application window in which Reconfiguration is running. The tab that previously said Application 1 now says Reconfig and is the active window.




Step Action

1 In the DBW, select the Reconfig tab.


Stop X

where X is the number of the window in which Reconfiguration is running.

3 Press Enter.



Chapter 10: Reconfiguration UtilityAbout Reconfiguration

About Reconfiguration

Typically, you use Reconfiguration to alter the number of AMPs in an RDBMS. The new configuration map includes the status of each AMP in a system. AMP status in a new configuration map is shown in the following table.

Vprocs

Virtual processors (vprocs) are instances of AMP or PE software within the RDBMS. Vprocs allow the RDBMS to execute multiple instances of AMP or PE software, each instance behaving as though executing in a dedicated processor.

Physical Processors

The Configuration and Reconfiguration utilities are not responsible for the maintenance of the physical environment in which the RDBMS configuration is defined.

The AMPs and PEs exist within a previously defined physical configuration. Use the pdeconfig utility to configure parts of the physical configuration, such as creating Logical Units (LUNs) on disk arrays. The pdeconfig utility then maps the virtual components (for example, vprocs) to the physical configuration. For more information, see Chapter 6: “pdeconfig Utility (NCR UNIX MP-RAS Only).”

pdeconfig automatically invokes the vconfig utility, which specifies how the virtual configuration (for example, AMP vprocs) maps to the physical configuration (for example, disk storage).

Configuration Utility Activities

When the RDBMS is initialized, System Initializer (SysInit) procedures build a default configuration map that describes the one target AMP involved in SysInit. This configuration is stored in both the current and new configuration maps.

When the RDBMS is operational, you use Configuration to describe the complete system in the new configuration map area.

AMP Status … Means that the AMP …

Add is new and is to be added to the current configuration.

ChgClust cluster assignment was modified.

Delete is to be deleted from the current configuration.

Online has not been modified.



As the system grows and changes, use Configuration to revise the new configuration map to reflect the following types of changes to the system:

• Addition and deletion of vprocs and hosts• Changes to cluster assignments

Warning: When changing cluster assignments without adding AMPs, ample disk space must be available on all AMPs.

If ample space is not available, the system stops. To recover, SYSINIT the RDBMS, which results in loss of data. NCR recommends that currentperm space should be less than 53% of the total maxperm space before starting a change of clusters without adding AMPs.

New Configuration Map

Use the configuration maps to perform these tasks:

• Store the identification and status of each vproc in the RDBMS• Identify the AMPs that comprise each AMP cluster• Identify each PE and its associated host

The RDBMS contains these two configuration maps:

• The current configuration map, which describes the current arrangement and status of vprocs in the system

• The new configuration map, which includes changes and additions to the configuration

The new configuration map serves as input to Reconfiguration.

Reconfiguration Utility Activities

After Configuration builds a new configuration map, Reconfiguration redefines the system configuration according to the new map. Reconfiguration copies the new configuration map to the current configuration map on each node.

During reconfiguration, data is redistributed among AMPs, if AMPs were added or deleted, or if cluster assignments were changed. Redistribution causes hash bucket assignments to be recalculated. These assignments describe the AMPs responsible for primary data and the AMPs responsible for fallback data.



Hash bucket arrays contain hash bucket assignments for each AMP:

• Primary data rows for the current configuration• Fallback data rows for the current configuration• Primary data rows for the new configuration• Fallback data rows for the new configuration

Information that defines the new configuration is used during reconfiguration.

Effects on Journal Tables

Reconfiguration deletes all journal tables (active, saved, and restored subtables).

Timestamps

Reconfiguration displays timestamps at the beginning and the end of each phase.


Chapter 10: Reconfiguration UtilityReconfiguration Utility Commands

Reconfiguration Utility Commands

A reconfiguration session consists of reconfiguring the system according to the new configuration map built by the Configuration utility.

The following table lists Reconfiguration commands and their functions.

To display help information on Reconfiguration, press F7.

Commands Function

RECONFIG (or press F2) Begins a session that changes the system configuration according to the map provided by the Configuration utility.

STATUS Determines the status of Reconfiguration.

STOP (or press F3) Stops Reconfiguration.


Chapter 10: Reconfiguration UtilityReconfiguration Utility Process

Reconfiguration Utility Process

This section summarizes the process performed by Reconfiguration commands. The details of command syntax and use are described later in this chapter.

As Reconfiguration runs, it performs these functions:

• Checks the RDBMS status to ensure that reconfiguration is possible. Disk storage capacity is checked to ensure that the system has sufficient storage to accommodate the redistributed data in the event of a delete AMP reconfiguration. Reconfiguration terminates if the system does not have sufficient storage capacity. After system status is verified, new hash bucket arrays are calculated based on current and new configuration maps.

• Redistributes primary and fallback data. Unique secondary index subtables, if any, are redistributed also.

• Deletes rows that were redistributed elsewhere from AMPs on which they formerly resided. Nonunique secondary indexes, if any, are rebuilt.

• Updates space accounting information, hash bucket arrays, and configuration maps.

Reconfiguration functions are completed sequentially in this order:

Step Action

1 Before starting Reconfiguration, see the following sections:

• “Before Starting Reconfiguration” on page 10-2.• “Disabling Logons” on page 10-2.

2 To start Reconfiguration, see “Starting and Exiting Reconfiguration on NCR UNIX MP-RAS” on page 10-4 or “Starting and Exiting Reconfiguration on Microsoft Windows 2000” on page 10-6.

3 Specify whether to or not to pause before Reconfiguration enters the irreversible phase.

The irreversible phase begins when Reconfiguration reaches a point at which it must run to completion, or the RDBMS must be re-initialized by running System Initializer.

When the irreversible phase begins depends upon the purpose of the reconfiguration. The beginning of the irreversible phase is identified as one of these named phases:

• The table redistribution phase for add AMP, delete AMP, and cluster reassignment operations• The saving new primary hash map phase for all other operations



IF you … THEN Reconfiguration does …

type RECONFIG without the WITH PAUSE option

not prompt you before the irreversible phase begins.

type RECONFIG with the WITH PAUSE option

prompt you before the irreversible phase begins.

press the F2 key prompt you whether to pause before the irreversible phase begins:

Do you want to pause before irreversible phase. Yes or No?

IF you type … THEN Reconfiguration will …

Yes prompt you after the hash maps are created.

No not prompt you after the hash maps are created and will continue the reconfiguration process.

If you interrupt Reconfiguration after the irreversible phase, Reconfiguration restarts automatically to complete the remaining phases when the system is restarted.

4 During the initialization of reconfiguration, the existence of all RDBMS table headers on all AMPs is verified.

If a table header is missing, the table ID and the corresponding vproc ID from which the header is missing are displayed in the Database Window.

At the end of the verification, the following message appears in the application window:

DBS Table Header verification failed, the missing header is available on the Database Window. Repair all missing table headers before reattempting Reconfiguration.

***** Depress the ENTER key to reset DBS.

At this point, you should switch to the Database Window to obtain a list of missing table headers before resetting the RDBMS.

Caution: If this error condition occurs, contact the Teradata Support Center (TSC) for the procedures to fix the missing headers.

5 Before entering the hash map calculation phase, Reconfiguration checks all AMPs for active user sessions. If any users are logged on, Reconfiguration issues an error message and halts. The application window and the Database Window display a message similar to the following:

Reconfig stopped, logged on sessions found in DBC.Session Table

A message similar to the following appears in the application window, describing which PEs have users logged on:

They include the following PEs:

16383, 16382, mmm ......

Step Action



6 Reconfig calculates hash map.

7 If you requested Reconfiguration to pause in Step 3, Reconfiguration prompts with the following:

Reconfiguration pauses before the irreversible phase.

Do You Want to Abort? Type Y(es) or N(o).

IF you type … THEN Reconfiguration will …

Yes stop.

No continue to the next phase.

8 Reconfiguration redistributes tables (including stored procedures.When reconfiguration reaches the Table Redistribution phase (the irreversible phase) and begins to change data in the current configuration, you must run the operation to completion.

In the table redistribution phase, Reconfiguration verifies that the table to be redistributed exists on all online AMPs before table redistribution is started. This integrity check identifies those database tables that are corrupted between initialization and this phase.

If a database table is missing from one or more of the online AMPs, the application window shows this message:

Table DBName. TBLName

*** is missing from some of the online AMPs

*** This table is skipped.

9 Reconfiguration deletes moved rows from tables and rebuilds NUSIs.

10 Reconfiguration saves the following:

• New primary hash map• New fallback hash map• Current primary hash map• Current fallback hash map• Current configuration map• New configuration map• Backup IDs

11 Reconfiguration deletes new hash maps.

12 Reconfiguration saves bitmap hash table.

13 Reconfiguration updates the following:

• Disk space• Vproc configuration

When reconfiguration completes, the system displays this message:

Restart DBS due to completion of Reconfiguration.

System is about to reset.

Step Action



IF … THEN …

reconfiguration is aborted by the system due to a hardware or software error before reconfiguration reaches a terminating state

the reconfiguration session is resumed automatically when the RDBMS is restarted.

an RDBMS restart (either a tpareset or a system crash) occurs when Reconfiguration is in the middle of the Hash Map calculation phase

the following message appears:

Hash Map Calculation Phase Begins.

{ Reconfig Phase one -- rcophas1 }

Hash Map Calculation Phase Ends.

a restart occurs after the first message and before the second one

Reconfiguration will not start automatically during system start up.

Step Action



IF … THEN …

you are adding new AMPS before Reconfiguration

a 6140 error message displays if you start Reconfiguration manually after the system comes up.

6140: RECONFIG aborted due to improper disk initialization procedure.

In this case, do the following and then start Reconfiguration:

aa To start xctl from the command prompt, type the following and press Enter:

xctl -nw

b To access the Debug screen, type the following and press Enter:

screen debug


c(0) Start ALL Appls: On (1) Break Stop: Off(2) Start with Debug: Off (3) Do not Reset: On (4) Save Dumps: On (5) Snapshot Crash: Off(6) Dump Type: System (7) Maximum Dumps: -1(8) Maximum Dump Size: -1 (MB) (9) Maximum FSG Area Dumped: 10 (MB)(A) Auto Dump Clear: On

START INDIVIDUAL APPLICATIONS

(B) Start Appl1: On (C) Start Appl2: Off(D) Start Appl3: Off Start Appl4: Off

d To turn Start ALL Appls to Off, type the following and press Enter:

0=Off

e To write the change, type the following and press Enter:

write


XCTL: Control GDO successfully written

f At the command prompt, type the following and press Enter:

quit

Step Action



IF … THEN …

you are adding new AMPS before Reconfiguration (cont)

g To restart the RDBMS, type the following and press Enter:

tpareset -f reason

where reason is why you are restarting the RDBMS.


You are about to restart the database on the system xyz

where xyz is the name of your database system.

Do you wish to continue (yes/no) [no]:

Note: For additional information, see “Starting and Stopping the System” in Teradata RDBMS Database Administration.

h Type Y and press Enter.

i To clean all data from the newly added vprocs, start the Database Window. For information, see Teradata RDBMS Database Window.

j Select the Supervisor (Supvr) icon.


k In the Enter a command subwindow of the Supervisor window, type the following and press Enter.

start vprocmanager


Started 'vprocmanager' in window 4 at Wed Mar 28 16:55:16 2001

Step Action



IF … THEN …


l To view the status of the RDBMS, type the following and press Enter:

status dbs


SYSTEM NAME: DEFAULT_VCONFIG 01/03/16 11:06:58

DBS LOGICAL CONFIGURATION

-------------------------

Vproc Rel. Node Crash Vproc Config Config Cluster/ RcvJrnl/Number Vproc# ID Movable Count State Status Type Host No. Host Type

------ ------ ---- ------- ----- ------ ------ ------ -------- ---------

0* 1 1-01 Yes 0 ONLINE Online AMP 0 On 1 2 1-01 Yes 0 NEWPROC NewReady AMP ? ?

16383 3 1-01 Yes 0 ONLINE Online PE 52 COP

-------------------------------------------------------------------------

* DBS Control AMPDBS State: DBS is not runningDBS RestartKind: COLD

m To start the INITVDISK command, type the following and press Enter:

INITVDISK vprocid

where vprocid is defined as either a decimal or hexadecimal number in the range of 0 through 16383 or 0 through 3FFF, respectively.

Note: A hexadecimal number is specified by appending a trailing X or x (for example, 123X or B6x).

For example, assume you want to initialize the RDBMS file system on vproc 1. You type the following:

initvdisk 1


Starting the file system initialization task on 1...

The Vdisk associated with Vproc 1 has been initialized.

Enter a command, HELP or QUIT:

Step Action



IF … THEN …


n Type the following and press Enter:

quit


Exiting VprocManager...

o To start xctl from the command prompt, type the following and press Enter:

xctl -nw

p To access the Debug screen, type the following and press Enter:

screen debug


(0) Start ALL Appls: On (1) Break Stop: Off(2) Start with Debug: Off (3) Do not Reset: On (4) Save Dumps: On (5) Snapshot Crash: Off(6) Dump Type: System (7) Maximum Dumps: -1(8) Maximum Dump Size: -1 (MB) (9) Maximum FSG Area Dumped: 10 (MB)(A) Auto Dump Clear: On

START INDIVIDUAL APPLICATIONS

(B) Start Appl1: On (C) Start Appl2: Off(D) Start Appl3: Off Start Appl4: Off

q To turn Start ALL Appls to On, type the following and press Enter:

0=On

r To write the change, type the following and press Enter:

write


XCTL: Control GDO successfully written

s At the command prompt, type the following and press Enter:

quit

t To start Reconfiguration, see “Starting and Exiting Reconfiguration on NCR UNIX MP-RAS” on page 10-4.

Step Action


Chapter 10: Reconfiguration UtilityRECONFIG

RECONFIG

Function

The RECONFIG command begins the process of changing the system configuration.

Note: A new configuration map must have been produced previously using the Configuration utility.

Syntax

where:


DISPLAY whether to enable or disable output of Reconfiguration status (but not statistics):

• ON enables output. (Default)• OFF disables output.

n TASKS the limitation of the number of Reconfiguration sessions running in parallel.

nn is a number between 1 and 10 inclusive. The default is three.

PRIORITY p the priority string determined by Priority Scheduler. The default is M.

1102B002

R

RECONFIG

WITH DISPLAY ON

OFF

PAUSE

STATISTICS ON

OFF

n TASKS

PRIORITY p



Example 1

To disable statistics collection, type the following:

reconfig with statistics off

Example 2

To reconfigure with 10 control tasks and statistics disabled, type the following:

reconfig with 10 tasks statistics off

Example 3

To reconfigure with eight control tasks and statistics enabled, type the following:

reconfig with 8 tasks

reconfig with statistics on 8 tasks

Example 4

To reconfigure with eight control tasks and output display disabled, type the following:

reconfig with 8 tasks display off

Example 5

To reconfigure with eight control tasks at low priority and output display disabled, type the following:

reconfig with 8 tasks priority l display off

Example 6

To reconfigure with eight control tasks at a user-defined priority of utilprio and output display disabled, type the following:

reconfig with 8 tasks priority utilprio display off

PAUSE whether Reconfiguration is to pause before entering the irreversible phase.

Each AMP stores the current phase of reconfiguration.

STATISTICS whether to enable or disable output of Reconfiguration statistics:

• ON enables statistics. (Default)• OFF disables statistics.




Example 7

The following is a representation of Reconfiguration output. Reconfiguration output displays the following:

• Start and end time of each table processed during redistribution• Run-time statistics of the table process that includes statistics for all AMPs

This information is included with the deletion and NUSI building. The output might become excessive for a large number of tables, so you might want to disable DISPLAY. If you disable DISPLAY, you can still obtain status using the STATUS command.

Note: You can disable the table begin/completion output with the RECONFIG WITH DISPLAY OFF command. You can disable the statistics output with the RECONFIG WITH STATISTICS OFF command.

Redist DeletionTableSize RowCount NUSICount FB Estimate Estimate Database.Table--------- --------------- --------- -- -------- -------- --------------------------------------------

.

.

. 78.00KB 80 0 Y 00:00:01 00:00:00 DBC.Translation (0000H 003BH)

32.00KB 32 0 Y 00:00:01 00:00:00 DBC.Dbase_V1R4 (0000H 003DH) 48.00KB 32 0 Y 00:00:01 00:00:00 DBC.TVM_V1R5 (0000H 003EH) 145.00KB 402 0 Y 00:00:01 00:00:00 DBC.EventLog (0000H 003FH) 32.00KB 32 0 Y 00:00:01 00:00:00 DBC.Next_V2R2 (0000H 0040H) 32.00KB 32 0 Y 00:00:01 00:00:00 DBC.AccessRights_V1R5 (0000H 0041H) 16.00KB 32 0 Y 00:00:01 00:00:00 DBC.Accounts_V2R4 (0000H 0042H) 268.00KB 2,296 0 N 00:00:01 00:00:00 DBC.Acctg (0000H 0043H) 32.00KB 32 0 Y 00:00:01 00:00:00 DBC.Indexes_V2R2 (0000H 0044H) 32.00KB 32 0 Y 00:00:01 00:00:00 DBC.RCEvent (0000H 0046H) 48.00KB 32 0 Y 00:00:01 00:00:00 DBC.TVFields_V1R5 (0000H 0047H) 32.00KB 32 0 Y 00:00:01 00:00:00 DBC.Hosts (0000H 0048H) 16.00KB 32 0 N 00:00:01 00:00:00 DBC.RecoveryLockTable (0000H 0049H) 16.00KB 32 0 N 00:00:01 00:00:00 DBC.RecoveryPJTable (0000H 004AH) 18.00KB 36 0 Y 00:00:01 00:00:00 DBC.DBCInfoTbl (0000H 004BH) 48.00KB 32 0 Y 00:00:01 00:00:00 DBC.SessionTbl (0000H 004CH) 48.00KB 32 0 Y 00:00:01 00:00:00 DBC.Dbase_V1R5 (0000H 004DH) 33.00KB 34 0 Y 00:00:01 00:00:00 DBC.SysSecDefaults (0000H 004EH) 32.00KB 32 0 Y 00:00:01 00:00:00 DBC.OldPasswords (0000H 004FH) 32.00KB 32 0 Y 00:00:01 00:00:00 DBC.InDoubtResLog (0000H 0050H) 32.00KB 32 0 Y 00:00:01 00:00:00 DBC.ReferencingTbls_V2R2 (0000H 0051H) 32.00KB 32 0 Y 00:00:01 00:00:00 DBC.ReferencedTbls_V2R2 (0000H 0052H) 32.00KB 32 0 Y 00:00:01 00:00:00 DBC.TableConstraints_V2R2 (0000H 0053H) 48.00KB 32 0 Y 00:00:01 00:00:00 DBC.AccLogRuleTbl_V2R2 (0000H 0054H) 48.00KB 32 0 Y 00:00:01 00:00:00 DBC.Dbase_V2R2 (0000H 0055H) 48.00KB 32 0 Y 00:00:01 00:00:00 DBC.TVM_V2R2 (0000H 0056H) 32.00KB 32 0 Y 00:00:01 00:00:00 DBC.AccessRights_V2R2 (0000H 0057H) 32.00KB 32 0 Y 00:00:01 00:00:00 DBC.TVFields_V2R2 (0000H 0058H) 32.00KB 32 0 Y 00:00:01 00:00:00 DBC.UnResolvedReferences (0000H 0059H) 32.00KB 32 0 Y 00:00:01 00:00:00 DBC.ConstraintNames_V2R2 (0000H 005AH) 143.00KB 882 0 Y 00:00:01 00:00:00 DBC.Indexes (0000H 005BH)

.

.

.


Chapter 10: Reconfiguration UtilitySTATUS

STATUS

Function

The STATUS command allows you to determine the status of Reconfiguration at any time during the process.

Syntax

Usage Notes

STATUS is available at any time during Reconfiguration and includes the status of the following:

• Total number of tables processed for the redistribution, deletion, and NUSI phases

• Total number of tables remaining to be processed for the redistribution, deletion, and NUSI phases

• Completion percentage according to the total number of bytes processed• Status of each non-idle, parallel reconfiguration control task• Completion percentage and name of table being processed for each non-

idle, parallel reconfiguration control task

HH01A002

S

STATUS



Example 1

The following is an example of STATUS output during hash map calculation:

Current reconfig phase: Hash Map Calculation

Example 2

The following is an example of STATUS output during redistribution:

Current reconfig phase: Redistribution Estimated time remaining: 00:19:21 Redistribution status - tables processed: 152 tables remaining: 26 70% of total bytes processed Deletion/NUSI status - tables processed: 0 tables remaining: 178 0% of total bytes processed

Reconfig task 0 Processed 69% of RKPMED.SIW_XXXX_FB_12 (0000H 04C4H) Reconfig task 1 Processed 69% of RKPMED.SIW_XXXX_FB_7 (0000H 04BFH) Reconfig task 2 Processed 69% of RKPMED.SIW_XXXX_FB_11 (0000H 04C3H) Reconfig task 3 Processed 68% of RKPMED.SIW_XXXX_FB_15 (0000H 04C7H) Reconfig task 4 Processed 69% of RKPMED.SIW_XXXX_FB_8 (0000H 04C0H) Reconfig task 5 Processed 68% of RKPMED.SIW_XXXX_FB_13 (0000H 04C5H) Reconfig task 6 Processed 64% of RKPMED.SIW_XXXX_FB_14 (0000H 04C6H) Reconfig task 7 Processed 69% of RKPMED.SIW_XXXX_FB_9 (0000H 04C1H) Reconfig task 8 Processed 69% of RKPMED.SIW_XXXX_FB_6 (0000H 04BEH)

Reconfig task 9 Processed 69% of RKPMED.SIW_XXXX_FB_10 (0000H 04C2H)

Example 3

The following is an example of STATUS output during Deletion/NUSI rebuilding:

Current reconfig phase: Redistribution Estimated time remaining: 00:19:21 Redistribution status - tables processed: 152 tables remaining: 152 100% of total bytes processed Deletion/NUSI status - tables processed: 152 tables remaining: 26 70% of total bytes processed

Reconfig task 0 Processed 69% of RKPMED.SIW_XXXX_FB_12 (0000H 04C4H) Reconfig task 1 Processed 69% of RKPMED.SIW_XXXX_FB_7 (0000H 04BFH) Reconfig task 2 Processed 69% of RKPMED.SIW_XXXX_FB_11 (0000H 04C3H) Reconfig task 3 Processed 68% of RKPMED.SIW_XXXX_FB_15 (0000H 04C7H) Reconfig task 4 Processed 69% of RKPMED.SIW_XXXX_FB_8 (0000H 04C0H)



Reconfig task 5 Processed 68% of RKPMED.SIW_XXXX_FB_13 (0000H 04C5H) Reconfig task 6 Processed 64% of RKPMED.SIW_XXXX_FB_14 (0000H 04C6H) Reconfig task 7 Processed 69% of RKPMED.SIW_XXXX_FB_9 (0000H 04C1H) Reconfig task 8 Processed 69% of RKPMED.SIW_XXXX_FB_6 (0000H 04BEH) Reconfig task 9 Processed 69% of RKPMED.SIW_XXXX_FB_10 (0000H 04C2H)


Chapter 10: Reconfiguration UtilitySTOP

STOP

Function

The STOP command stops Reconfiguration.

Syntax

Usage Notes

When the STOP command is accepted, Reconfiguration displays this message:

Are You Sure? Enter Y(es) or N(o):

Enter Y to stop or N to continue.

GT10B001S

STOP


Chapter 10: Reconfiguration UtilityError Messages

Error Messages

The application window running Reconfiguration can contain the types of messages displayed in the output subwindow, as shown in the following table.

Teradata RDBMS Messages contains the error messages for Reconfiguration.

Message Description

Information Indicates the status of a command or the result of an operation.

OK indicates that a command has been accepted or an operation has completed successfully.

Prompt Prompts for a response to a request or for confirmation of an action.

Error Composed of a message code and text.

All error messages issued by Reconfiguration are contained in Teradata RDBMS Messages.


Chapter 10: Reconfiguration UtilityReconfiguration Example

Reconfiguration Example

_______ | | | | ___ __ ____ | ____ __|__ ____ | / |/ \ ____| ____| ____| | ____| | --- | / | / | / | | / | | \___ | \____| \____| \____| |__ \____| Release V2R.05Y.00.00.00 Version 05Y.00.00.00 RECONFIG Utility (Dec 94)

The RECONFIG program provides the user with a facility to redistribute data when the configuration of a DBS is changed by pressing the appropriate function key.

System Time (Reconfiguration): 02/09/30 15:07:35.

Enter command orPress <F2> for Reconfig command <F3> for Stop command <F4> for Query or Status command <F7> for helpDo you want to pause before irreversible phase?,(Yes or No)?yes

Redist DeletionTableSize RowCount NUSICount FB Estimate Estimate Database.Table--------- --------------- --------- -- -------- -------- -------------------------------------------------- 10.00KB 10 0 Y 00:00:01 00:00:00 DBC.HW_Event_Log (0000H 0005H) 40.00KB 214 0 Y 00:00:01 00:00:00 DBC.SW_Event_Log (0000H 0006H) 10.00KB 10 0 Y 00:00:01 00:00:00 DBC.RCConfiguration (0000H 0007H) 20.00KB 20 0 Y 00:00:01 00:00:00 DBC.CollationTbl (0000H 0008H) 6.00KB 12 0 Y 00:00:01 00:00:00 DBC.Global (0000H 0019H) 1.03MB 7,257 0 N 00:00:01 00:00:00 DBC.TransientJournal (0000H 001AH) 6.00KB 20 0 Y 00:00:01 00:00:00 DBC.Owners (0000H 001BH) 8.00KB 20 0 Y 00:00:01 00:00:00 DBC.Parents (0000H 001CH) 325.00KB 4,750 0 Y 00:00:01 00:00:00 DBC.ErrorMsgs (0000H 001EH) 5.00KB 10 0 N 00:00:01 00:00:00 DBC.ChangedRowJournal (0000H 0020H) 5.00KB 10 0 N 00:00:01 00:00:00 DBC.SavedTransactionStatusTable (0000H 0024H) 5.00KB 10 0 N 00:00:01 00:00:00 DBC.LocalTransactionStatusTable (0000H 0025H) 5.00KB 10 0 N 00:00:01 00:00:00 DBC.UtilityLockJournalTable (0000H 0027H) 5.00KB 10 0 N 00:00:01 00:00:00 DBC.LocalSessionStatusTable (0000H 0028H) 780.00KB 360 0 N 00:00:01 00:00:00 DBC.SysRcvStatJournal (0000H 0029H) 5.00KB 10 0 N 00:00:01 00:00:00 DBC.OrdSysChngTable (0000H 002AH) 10.00KB 10 0 Y 00:00:01 00:00:00 DBC.RCConfiguration_V1R5 (0000H 002CH) 10.00KB 10 0 Y 00:00:01 00:00:00 DBC.RCMedia (0000H 0030H) 10.00KB 10 0 Y 00:00:01 00:00:00 DBC.LogonRuleTbl_V2R2 (0000H 0031H) 10.00KB 10 0 Y 00:00:01 00:00:00 DBC.AccLogRuleTbl_V1R5 (0000H 0032H) 15.00KB 10 0 Y 00:00:01 00:00:00 DBC.AccLogTbl_V2R2 (0000H 0033H) 10.00KB 10 0 Y 00:00:01 00:00:00 DBC.DBCAssociation_V2R2 (0000H 0034H) 50.00KB 58 0 Y 00:00:01 00:00:00 DBC.Translation (0000H 003BH) 10.00KB 10 0 Y 00:00:01 00:00:00 DBC.Dbase_V1R4 (0000H 003DH) 15.00KB 10 1 Y 00:00:01 00:00:00 DBC.TVM_V1R5 (0000H 003EH) 20.00KB 34 0 Y 00:00:01 00:00:00 DBC.EventLog (0000H 003FH) 10.00KB 10 0 Y 00:00:01 00:00:00 DBC.Next_V2R2 (0000H 0040H) 10.00KB 10 1 Y 00:00:01 00:00:00 DBC.AccessRights_V1R5 (0000H 0041H) 5.00KB 10 0 Y 00:00:01 00:00:00 DBC.Accounts_V2R4 (0000H 0042H) 15.00KB 30 0 N 00:00:01 00:00:00 DBC.Acctg (0000H 0043H) 10.00KB 10 0 Y 00:00:01 00:00:00 DBC.Indexes_V2R2 (0000H 0044H) 10.00KB 10 0 Y 00:00:01 00:00:00 DBC.RCEvent (0000H 0046H) 15.00KB 10 0 Y 00:00:01 00:00:00 DBC.TVFields_V1R5 (0000H 0047H) 10.00KB 10 0 Y 00:00:01 00:00:00 DBC.Hosts (0000H 0048H) 5.00KB 10 0 N 00:00:01 00:00:00 DBC.RecoveryLockTable (0000H 0049H)



5.00KB 10 0 N 00:00:01 00:00:00 DBC.RecoveryPJTable (0000H 004AH) 7.00KB 14 0 Y 00:00:01 00:00:00 DBC.DBCInfoTbl (0000H 004BH) 15.00KB 10 0 Y 00:00:01 00:00:00 DBC.SessionTbl (0000H 004CH) 15.00KB 10 0 Y 00:00:01 00:00:00 DBC.Dbase_V1R5 (0000H 004DH) 11.00KB 12 0 Y 00:00:01 00:00:00 DBC.SysSecDefaults (0000H 004EH) 10.00KB 10 0 Y 00:00:01 00:00:00 DBC.OldPasswords (0000H 004FH) 10.00KB 10 0 Y 00:00:01 00:00:00 DBC.InDoubtResLog (0000H 0050H) 10.00KB 10 0 Y 00:00:01 00:00:00 DBC.ReferencingTbls_V2R2 (0000H 0051H) 10.00KB 10 0 Y 00:00:01 00:00:00 DBC.ReferencedTbls_V2R2 (0000H 0052H) 10.00KB 10 0 Y 00:00:01 00:00:00 DBC.TableConstraints_V2R2 (0000H 0053H) 15.00KB 10 0 Y 00:00:01 00:00:00 DBC.AccLogRuleTbl_V2R2 (0000H 0054H)15.00KB 10 0 Y 00:00:01 00:00:00 DBC.Dbase_V2R2 (0000H 0055H) 15.00KB 10 1 Y 00:00:01 00:00:00 DBC.TVM_V2R2 (0000H 0056H) 10.00KB 10 0 Y 00:00:01 00:00:00 DBC.AccessRights_V2R2 (0000H 0057H) 10.00KB 10 0 Y 00:00:01 00:00:00 DBC.TVFields_V2R2 (0000H 0058H) 10.00KB 10 0 Y 00:00:01 00:00:00 DBC.UnResolvedReferences (0000H 0059H) 10.00KB 10 0 Y 00:00:01 00:00:00 DBC.ConstraintNames_V2R2 (0000H 005AH) 61.00KB 430 0 Y 00:00:01 00:00:00 DBC.Indexes (0000H 005BH) 11.00KB 12 0 Y 00:00:01 00:00:00 DBC.Next (0000H 005CH) 15.00KB 10 0 Y 00:00:01 00:00:00 DBC.Dbase_V2R4 (0000H 005DH) 15.00KB 10 0 Y 00:00:01 00:00:00 DBC.TVM_V2R4 (0000H 005EH) 15.00KB 10 0 Y 00:00:01 00:00:00 DBC.TVFields_V2R4 (0000H 005FH) 10.00KB 10 0 Y 00:00:01 00:00:00 DBC.DBCAssociation (0000H 0060H) 10.00KB 10 0 Y 00:00:01 00:00:00 DBC.TableConstraints_V2R4 (0000H 0061H) 10.00KB 10 0 Y 00:00:01 00:00:00 DBC.ReferencingTbls (0000H 0062H) 10.00KB 10 0 Y 00:00:01 00:00:00 DBC.ReferencedTbls (0000H 0063H) 10.00KB 10 0 Y 00:00:01 00:00:00 DBC.ConstraintNames (0000H 0064H) 15.00KB 10 0 Y 00:00:01 00:00:00 DBC.AccLogTbl (0000H 0065H) 216.00KB 3,096 1 Y 00:00:01 00:00:00 DBC.AccessRights (0000H 0066H) 13.00KB 16 0 Y 00:00:01 00:00:00 DBC.LogonRuleTbl (0000H 0067H) 10.00KB 10 0 Y 00:00:01 00:00:00 DBC.TempTables (0000H 0068H) 10.00KB 10 0 Y 00:00:01 00:00:00 DBC.TempStatistics (0000H 0069H) 10.00KB 10 0 Y 00:00:01 00:00:00 DBC.TriggersTbl_V2R4 (0000H 006AH) 10.00KB 10 0 Y 00:00:01 00:00:00 DBC.RepBatchStatus (0000H 006BH) 15.00KB 10 0 Y 00:00:01 00:00:00 DBC.AccLogRuleTbl_V2R4 (0000H 006CH) 130.00KB 1,210 0 N 00:00:01 00:00:00 DBC.DataBaseSpace (0000H 006DH) 2.32MB 16,958 0 Y 00:00:01 00:00:00 DBC.TVFields (0000H 006EH) 233.00KB 16 0 Y 00:00:01 00:00:00 DBC.TextTbl (0000H 006FH) 6.00KB 12 0 Y 00:00:01 00:00:00 DBC.Migration (0000H 0070H) 10.00KB 10 0 Y 00:00:01 00:00:00 DBC.Roles (0000H 0071H) 10.00KB 10 1 Y 00:00:01 00:00:00 DBC.RoleGrants (0000H 0072H) 10.00KB 10 0 Y 00:00:01 00:00:00 DBC.UDFInfo (0000H 0073H) 10.00KB 10 0 Y 00:00:01 00:00:00 DBC.Profiles (0000H 0074H) 10.00KB 10 0 Y 00:00:01 00:00:00 DBC.TableConstraints (0000H 0075H) 10.00KB 10 0 Y 00:00:01 00:00:00 DBC.DBQLRuleTbl (0000H 0076H) 6.00KB 12 0 Y 00:00:01 00:00:00 DBC.DBQLRuleCountTbl (0000H 0077H) 20.00KB 10 0 Y 00:00:01 00:00:00 DBC.DBQLogTbl (0000H 0078H) 15.00KB 10 0 Y 00:00:01 00:00:00 DBC.DBQLStepTbl (0000H 0079H) 10.00KB 10 0 Y 00:00:01 00:00:00 DBC.DBQLObjTbl (0000H 007AH) 10.00KB 10 0 Y 00:00:01 00:00:00 DBC.DBQLSqlTbl (0000H 007BH) 10.00KB 10 0 Y 00:00:01 00:00:00 DBC.DBQLSummaryTbl (0000H 007CH) 10.00KB 10 0 Y 00:00:01 00:00:00 DBC.DBQLExplainTbl (0000H 007DH) 55.00KB 10 0 Y 00:00:01 00:00:00 DBC.ResUsageSpma (0000H 007EH) 35.00KB 10 0 Y 00:00:01 00:00:00 DBC.ResUsageIpma (0000H 007FH) 10.00KB 10 0 Y 00:00:01 00:00:00 DBC.ResUsageScpu (0000H 0080H) 85.00KB 10 0 Y 00:00:01 00:00:00 DBC.ResUsageSvpr (0000H 0081H) 45.00KB 10 0 Y 00:00:01 00:00:00 DBC.ResUsageIvpr (0000H 0082H) 15.00KB 10 0 Y 00:00:01 00:00:00 DBC.ResUsageSldv (0000H 0083H) 25.00KB 10 0 Y 00:00:01 00:00:00 DBC.ResUsageShst (0000H 0084H) 25.00KB 10 0 Y 00:00:01 00:00:00 DBC.ResUsageSobj (0000H 0085H) 10.00KB 10 0 Y 00:00:01 00:00:00 DBC.IdCol (0000H 0086H) 1.87MB 1,684 1 Y 00:00:01 00:00:00 DBC.TVM (0000H 0087H) 10.00KB 10 0 Y 00:00:01 00:00:00 DBC.TriggersTbl (0000H 0089H) 32.00KB 46 0 Y 00:00:01 00:00:00 DBC.Dbase (0000H 008AH) 15.00KB 10 0 Y 00:00:01 00:00:00 DBC.AccLogRuleTbl (0000H 008BH) 13.00KB 22 0 Y 00:00:01 00:00:00 DBC.Accounts (0000H 008CH) 5.00KB 10 0 Y 00:00:01 00:00:00 DBC.MDSRecoveryTbl (0000H 008DH) 10.00KB 10 0 Y 00:00:01 00:00:00 DBC.ParentChildCorrelation (0000H 008EH) 10.00KB 10 0 Y 00:00:01 00:00:00 SysAdmin.FastLog (0000H 0436H) 1.00MB 6,532 0 Y 00:00:01 00:00:00 SysAdmin.HelpSyntax (0000H 045FH)



5.00KB 10 0 Y 00:00:01 00:00:00 SystemFE.Temp_ReconfigSpace (0000H 0470H) 55.00KB 10 0 Y 00:00:01 00:00:00 SystemFE.opt_cost_table (0000H 0472H) 60.00KB 10 0 Y 00:00:01 00:00:00 systemfe.opt_ras_table (0000H 0473H) 81.00KB 570 0 Y 00:00:01 00:00:00 systemfe.CreateQCF (0000H 0474H) 14.00KB 52 0 Y 00:00:01 00:00:00 systemfe.CleanupQCF (0000H 0475H) 2.53MB 146,838 0 Y 00:00:01 00:00:00 SYS_CALENDAR.CALDATES (0000H 0495H) 5.00KB 10 0 N 00:00:01 00:00:00 DBC.FIRSTJOURNALTABLE (4000H 0000H)

The current configuration has: 2 Nodes with 10 AMPsThe new configuration will be: 2 Nodes with 8 AMPsThe system has: 112 tables using 11.94MB of dataThe estimated table redistribution time will be: 0 hours and 1 minutes.The estimated table deletion time will be: 0 hours and 0 minutes.

Reconfig waiting for Recovery to complete...Recovery has been stopped02/09/30 15:08:54 Hash Map Calculation Phase Begins02/09/30 15:08:54 Hash Map Calculation Phase Ends

Reconfiguration pauses before the irreversible phase on 02/09/30 at 15:08:54.

Do You Want to Abort? Type Y(es) Or N(o):no

02/09/30 15:10:20 Table Redistribution Phase Begins02/09/30 15:10:20 Task 00 Begin redistribution DBC.HW_Event_Log (0000H 0005H).02/09/30 15:10:21 Task 00 End redistribution DBC.HW_Event_Log (0000H 0005H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:21 Task 01 Begin redistribution DBC.SW_Event_Log (0000H 0006H).02/09/30 15:10:21 Task 00 Begin redistribution DBC.RCConfiguration (0000H 0007H).02/09/30 15:10:21 Task 01 End redistribution DBC.SW_Event_Log (0000H 0006H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 80 9.73KB 0 0 19802/09/30 15:10:21 Task 02 Begin redistribution DBC.CollationTbl (0000H 0008H).02/09/30 15:10:21 Task 00 End redistribution DBC.RCConfiguration (0000H 0007H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:21 Task 01 Begin redistribution DBC.Global (0000H 0019H).02/09/30 15:10:21 Task 02 End redistribution DBC.CollationTbl (0000H 0008H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19302/09/30 15:10:21 Task 00 Begin redistribution DBC.TransientJournal (0000H 001AH).02/09/30 15:10:21 Task 00 End redistribution DBC.TransientJournal (0000H 001AH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:21 Task 01 End redistribution DBC.Global (0000H 0019H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19102/09/30 15:10:21 Task 02 Begin redistribution DBC.Owners (0000H 001BH).02/09/30 15:10:21 Task 00 Begin redistribution DBC.Parents (0000H 001CH).02/09/30 15:10:22 Task 02 End redistribution DBC.Owners (0000H 001BH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19102/09/30 15:10:22 Task 01 Begin redistribution DBC.ErrorMsgs (0000H 001EH).02/09/30 15:10:22 Task 00 End redistribution DBC.Parents (0000H 001CH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19302/09/30 15:10:22 Task 02 Begin redistribution DBC.ChangedRowJournal (0000H 0020H).02/09/30 15:10:22 Task 02 End redistribution DBC.ChangedRowJournal (0000H 0020H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19102/09/30 15:10:22 Task 01 End redistribution DBC.ErrorMsgs (0000H 001EH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 926 58.56KB 0 0 20102/09/30 15:10:22 Task 00 Begin redistribution DBC.SavedTransactionStatusTable (0000H 0024H).02/09/30 15:10:22 Task 00 End redistribution DBC.SavedTransactionStatusTable (0000H 0024H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19302/09/30 15:10:22 Task 01 Begin redistribution DBC.LocalTransactionStatusTable (0000H 0025H).



02/09/30 15:10:22 Task 01 End redistribution DBC.LocalTransactionStatusTable (0000H 0025H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 926 58.56KB 0 0 20102/09/30 15:10:22 Task 00 Begin redistribution DBC.UtilityLockJournalTable (0000H 0027H).02/09/30 15:10:22 Task 00 End redistribution DBC.UtilityLockJournalTable (0000H 0027H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19302/09/30 15:10:22 Task 01 Begin redistribution DBC.LocalSessionStatusTable (0000H 0028H).02/09/30 15:10:22 Task 01 End redistribution DBC.LocalSessionStatusTable (0000H 0028H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 926 58.56KB 0 0 20102/09/30 15:10:22 Task 00 Begin redistribution DBC.SysRcvStatJournal (0000H 0029H).02/09/30 15:10:22 Task 00 End redistribution DBC.SysRcvStatJournal (0000H 0029H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19302/09/30 15:10:23 Task 01 Begin redistribution DBC.OrdSysChngTable (0000H 002AH).02/09/30 15:10:23 Task 01 End redistribution DBC.OrdSysChngTable (0000H 002AH).Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 926 58.56KB 0 0 20102/09/30 15:10:23 Task 00 Begin redistribution DBC.RCConfiguration_V1R5 (0000H 002CH).02/09/30 15:10:23 Task 01 Begin redistribution DBC.RCMedia (0000H 0030H).02/09/30 15:10:23 Task 00 End redistribution DBC.RCConfiguration_V1R5 (0000H 002CH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:23 Task 02 Begin redistribution DBC.LogonRuleTbl_V2R2 (0000H 0031H).02/09/30 15:10:23 Task 01 End redistribution DBC.RCMedia (0000H 0030H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:23 Task 00 Begin redistribution DBC.AccLogRuleTbl_V1R5 (0000H 0032H).02/09/30 15:10:23 Task 02 End redistribution DBC.LogonRuleTbl_V2R2 (0000H 0031H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:23 Task 01 Begin redistribution DBC.AccLogTbl_V2R2 (0000H 0033H).02/09/30 15:10:23 Task 00 End redistribution DBC.AccLogRuleTbl_V1R5 (0000H 0032H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:23 Task 02 Begin redistribution DBC.DBCAssociation_V2R2 (0000H 0034H).02/09/30 15:10:23 Task 01 End redistribution DBC.AccLogTbl_V2R2 (0000H 0033H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:23 Task 00 Begin redistribution DBC.Translation (0000H 003BH).02/09/30 15:10:23 Task 02 End redistribution DBC.DBCAssociation_V2R2 (0000H 0034H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:24 Task 01 Begin redistribution DBC.Dbase_V1R4 (0000H 003DH).02/09/30 15:10:24 Task 00 End redistribution DBC.Translation (0000H 003BH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 12 8.45KB 0 0 22302/09/30 15:10:24 Task 02 Begin redistribution DBC.TVM_V1R5 (0000H 003EH).02/09/30 15:10:24 Task 01 End redistribution DBC.Dbase_V1R4 (0000H 003DH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 21002/09/30 15:10:24 Task 00 Begin redistribution DBC.EventLog (0000H 003FH).02/09/30 15:10:24 Task 02 End redistribution DBC.TVM_V1R5 (0000H 003EH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 21002/09/30 15:10:24 Task 01 Begin redistribution DBC.Next_V2R2 (0000H 0040H).02/09/30 15:10:24 Task 00 End redistribution DBC.EventLog (0000H 003FH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19602/09/30 15:10:24 Task 02 Begin redistribution DBC.AccessRights_V1R5 (0000H 0041H).02/09/30 15:10:24 Task 01 End redistribution DBC.Next_V2R2 (0000H 0040H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:24 Task 00 Begin redistribution DBC.Accounts_V2R4 (0000H 0042H).02/09/30 15:10:24 Task 02 End redistribution DBC.AccessRights_V1R5 (0000H 0041H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:24 Task 01 Begin redistribution DBC.Acctg (0000H 0043H).02/09/30 15:10:24 Task 01 End redistribution DBC.Acctg (0000H 0043H).



Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:24 Task 00 End redistribution DBC.Accounts_V2R4 (0000H 0042H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:25 Task 02 Begin redistribution DBC.Indexes_V2R2 (0000H 0044H).02/09/30 15:10:25 Task 00 Begin redistribution DBC.RCEvent (0000H 0046H).02/09/30 15:10:25 Task 02 End redistribution DBC.Indexes_V2R2 (0000H 0044H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:25 Task 01 Begin redistribution DBC.TVFields_V1R5 (0000H 0047H).02/09/30 15:10:25 Task 00 End redistribution DBC.RCEvent (0000H 0046H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:25 Task 02 Begin redistribution DBC.Hosts (0000H 0048H).02/09/30 15:10:25 Task 01 End redistribution DBC.TVFields_V1R5 (0000H 0047H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 21002/09/30 15:10:25 Task 00 Begin redistribution DBC.RecoveryLockTable (0000H 0049H).02/09/30 15:10:25 Task 00 End redistribution DBC.RecoveryLockTable (0000H 0049H).Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:25 Task 02 End redistribution DBC.Hosts (0000H 0048H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 21002/09/30 15:10:25 Task 01 Begin redistribution DBC.RecoveryPJTable (0000H 004AH).02/09/30 15:10:25 Task 01 End redistribution DBC.RecoveryPJTable (0000H 004AH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 21002/09/30 15:10:25 Task 00 Begin redistribution DBC.DBCInfoTbl (0000H 004BH).02/09/30 15:10:26 Task 01 Begin redistribution DBC.SessionTbl (0000H 004CH).02/09/30 15:10:26 Task 00 End redistribution DBC.DBCInfoTbl (0000H 004BH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 2 74 0 0 19202/09/30 15:10:26 Task 02 Begin redistribution DBC.Dbase_V1R5 (0000H 004DH).02/09/30 15:10:26 Task 01 End redistribution DBC.SessionTbl (0000H 004CH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:26 Task 00 Begin redistribution DBC.SysSecDefaults (0000H 004EH).02/09/30 15:10:26 Task 02 End redistribution DBC.Dbase_V1R5 (0000H 004DH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 21002/09/30 15:10:26 Task 01 Begin redistribution DBC.OldPasswords (0000H 004FH).02/09/30 15:10:26 Task 00 End redistribution DBC.SysSecDefaults (0000H 004EH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 2 48 0 0 19002/09/30 15:10:26 Task 02 Begin redistribution DBC.InDoubtResLog (0000H 0050H).02/09/30 15:10:26 Task 01 End redistribution DBC.OldPasswords (0000H 004FH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:26 Task 00 Begin redistribution DBC.ReferencingTbls_V2R2 (0000H 0051H).02/09/30 15:10:26 Task 02 End redistribution DBC.InDoubtResLog (0000H 0050H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:26 Task 01 Begin redistribution DBC.ReferencedTbls_V2R2 (0000H 0052H).02/09/30 15:10:26 Task 00 End redistribution DBC.ReferencingTbls_V2R2 (0000H 0051H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:26 Task 02 Begin redistribution DBC.TableConstraints_V2R2 (0000H 0053H).02/09/30 15:10:26 Task 01 End redistribution DBC.ReferencedTbls_V2R2 (0000H 0052H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:27 Task 00 Begin redistribution DBC.AccLogRuleTbl_V2R2 (0000H 0054H).02/09/30 15:10:27 Task 02 End redistribution DBC.TableConstraints_V2R2 (0000H 0053H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:27 Task 01 Begin redistribution DBC.Dbase_V2R2 (0000H 0055H).02/09/30 15:10:27 Task 00 End redistribution DBC.AccLogRuleTbl_V2R2 (0000H 0054H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 190



02/09/30 15:10:27 Task 02 Begin redistribution DBC.TVM_V2R2 (0000H 0056H).02/09/30 15:10:27 Task 01 End redistribution DBC.Dbase_V2R2 (0000H 0055H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 21002/09/30 15:10:27 Task 00 Begin redistribution DBC.AccessRights_V2R2 (0000H 0057H).02/09/30 15:10:27 Task 02 End redistribution DBC.TVM_V2R2 (0000H 0056H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 21002/09/30 15:10:27 Task 01 Begin redistribution DBC.TVFields_V2R2 (0000H 0058H).02/09/30 15:10:27 Task 00 End redistribution DBC.AccessRights_V2R2 (0000H 0057H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:27 Task 02 Begin redistribution DBC.UnResolvedReferences (0000H 0059H).02/09/30 15:10:27 Task 01 End redistribution DBC.TVFields_V2R2 (0000H 0058H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 21002/09/30 15:10:27 Task 00 Begin redistribution DBC.ConstraintNames_V2R2 (0000H 005AH).02/09/30 15:10:27 Task 02 End redistribution DBC.UnResolvedReferences (0000H 0059H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:27 Task 01 Begin redistribution DBC.Indexes (0000H 005BH).02/09/30 15:10:28 Task 00 End redistribution DBC.ConstraintNames_V2R2 (0000H 005AH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCountAllAmps: 0 0 0 0 19002/09/30 15:10:28 Task 02 Begin redistribution DBC.Next (0000H 005CH).02/09/30 15:10:28 Task 01 End redistribution DBC.Indexes (0000H 005BH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 94 9.91KB 0 0 19902/09/30 15:10:28 Task 00 Begin redistribution DBC.Dbase_V2R4 (0000H 005DH).02/09/30 15:10:28 Task 02 End redistribution DBC.Next (0000H 005CH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19102/09/30 15:10:28 Task 01 Begin redistribution DBC.TVM_V2R4 (0000H 005EH).02/09/30 15:10:28 Task 00 End redistribution DBC.Dbase_V2R4 (0000H 005DH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:28 Task 02 Begin redistribution DBC.TVFields_V2R4 (0000H 005FH).02/09/30 15:10:28 Task 01 End redistribution DBC.TVM_V2R4 (0000H 005EH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:28 Task 00 Begin redistribution DBC.DBCAssociation (0000H 0060H).02/09/30 15:10:28 Task 02 End redistribution DBC.TVFields_V2R4 (0000H 005FH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:28 Task 01 Begin redistribution DBC.TableConstraints_V2R4 (0000H 0061H).02/09/30 15:10:28 Task 00 End redistribution DBC.DBCAssociation (0000H 0060H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:28 Task 02 Begin redistribution DBC.ReferencingTbls (0000H 0062H).02/09/30 15:10:28 Task 01 End redistribution DBC.TableConstraints_V2R4 (0000H 0061H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:28 Task 00 Begin redistribution DBC.ReferencedTbls (0000H 0063H).02/09/30 15:10:29 Task 02 End redistribution DBC.ReferencingTbls (0000H 0062H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:29 Task 01 Begin redistribution DBC.ConstraintNames (0000H 0064H).02/09/30 15:10:29 Task 00 End redistribution DBC.ReferencedTbls (0000H 0063H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:29 Task 02 Begin redistribution DBC.AccLogTbl (0000H 0065H).02/09/30 15:10:29 Task 01 End redistribution DBC.ConstraintNames (0000H 0064H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:29 Task 00 Begin redistribution DBC.AccessRights (0000H 0066H).02/09/30 15:10:29 Task 02 End redistribution DBC.AccLogTbl (0000H 0065H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:29 Task 01 Begin redistribution DBC.LogonRuleTbl (0000H 0067H).02/09/30 15:10:29 Task 00 End redistribution DBC.AccessRights (0000H 0066H).



Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 1,742 108.88KB 0 0 19802/09/30 15:10:29 Task 02 Begin redistribution DBC.TempTables (0000H 0068H).02/09/30 15:10:29 Task 01 End redistribution DBC.LogonRuleTbl (0000H 0067H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19302/09/30 15:10:29 Task 00 Begin redistribution DBC.TempStatistics (0000H 0069H).02/09/30 15:10:29 Task 02 End redistribution DBC.TempTables (0000H 0068H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:29 Task 01 Begin redistribution DBC.TriggersTbl_V2R4 (0000H 006AH).02/09/30 15:10:29 Task 00 End redistribution DBC.TempStatistics (0000H 0069H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:30 Task 02 Begin redistribution DBC.RepBatchStatus (0000H 006BH).02/09/30 15:10:30 Task 01 End redistribution DBC.TriggersTbl_V2R4 (0000H 006AH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:30 Task 00 Begin redistribution DBC.AccLogRuleTbl_V2R4 (0000H 006CH).02/09/30 15:10:30 Task 02 End redistribution DBC.RepBatchStatus (0000H 006BH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:30 Task 01 Begin redistribution DBC.DataBaseSpace (0000H 006DH).02/09/30 15:10:30 Task 01 End redistribution DBC.DataBaseSpace (0000H 006DH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:30 Task 00 End redistribution DBC.AccLogRuleTbl_V2R4 (0000H 006CH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:30 Task 02 Begin redistribution DBC.TVFields (0000H 006EH).02/09/30 15:10:30 Task 00 Begin redistribution DBC.TextTbl (0000H 006FH).02/09/30 15:10:30 Task 02 End redistribution DBC.TVFields (0000H 006EH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 3,592 559.06KB 0 0 25302/09/30 15:10:30 Task 01 Begin redistribution DBC.Migration (0000H 0070H).02/09/30 15:10:30 Task 00 End redistribution DBC.TextTbl (0000H 006FH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 2 110.37KB 0 0 19202/09/30 15:10:30 Task 02 Begin redistribution DBC.Roles (0000H 0071H).02/09/30 15:10:30 Task 01 End redistribution DBC.Migration (0000H 0070H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19102/09/30 15:10:31 Task 00 Begin redistribution DBC.RoleGrants (0000H 0072H).02/09/30 15:10:31 Task 02 End redistribution DBC.Roles (0000H 0071H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 21002/09/30 15:10:31 Task 01 Begin redistribution DBC.UDFInfo (0000H 0073H).02/09/30 15:10:31 Task 00 End redistribution DBC.RoleGrants (0000H 0072H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 21002/09/30 15:10:31 Task 02 Begin redistribution DBC.Profiles (0000H 0074H).02/09/30 15:10:31 Task 01 End redistribution DBC.UDFInfo (0000H 0073H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 21002/09/30 15:10:31 Task 00 Begin redistribution DBC.TableConstraints (0000H 0075H).02/09/30 15:10:31 Task 02 End redistribution DBC.Profiles (0000H 0074H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 21002/09/30 15:10:31 Task 01 Begin redistribution DBC.DBQLRuleTbl (0000H 0076H).02/09/30 15:10:31 Task 00 End redistribution DBC.TableConstraints (0000H 0075H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:31 Task 02 Begin redistribution DBC.DBQLRuleCountTbl (0000H 0077H).02/09/30 15:10:31 Task 01 End redistribution DBC.DBQLRuleTbl (0000H 0076H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:31 Task 00 Begin redistribution DBC.DBQLogTbl (0000H 0078H).02/09/30 15:10:32 Task 02 End redistribution DBC.DBQLRuleCountTbl (0000H 0077H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 195



02/09/30 15:10:32 Task 01 Begin redistribution DBC.DBQLStepTbl (0000H 0079H).02/09/30 15:10:32 Task 00 End redistribution DBC.DBQLogTbl (0000H 0078H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19402/09/30 15:10:32 Task 02 Begin redistribution DBC.DBQLObjTbl (0000H 007AH).02/09/30 15:10:32 Task 01 End redistribution DBC.DBQLStepTbl (0000H 0079H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:32 Task 00 Begin redistribution DBC.DBQLSqlTbl (0000H 007BH).02/09/30 15:10:32 Task 02 End redistribution DBC.DBQLObjTbl (0000H 007AH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:32 Task 01 Begin redistribution DBC.DBQLSummaryTbl (0000H 007CH).02/09/30 15:10:32 Task 00 End redistribution DBC.DBQLSqlTbl (0000H 007BH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:32 Task 02 Begin redistribution DBC.DBQLExplainTbl (0000H 007DH).02/09/30 15:10:32 Task 01 End redistribution DBC.DBQLSummaryTbl (0000H 007CH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:32 Task 00 Begin redistribution DBC.ResUsageSpma (0000H 007EH).02/09/30 15:10:32 Task 02 End redistribution DBC.DBQLExplainTbl (0000H 007DH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:32 Task 01 Begin redistribution DBC.ResUsageIpma (0000H 007FH).02/09/30 15:10:33 Task 00 End redistribution DBC.ResUsageSpma (0000H 007EH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:33 Task 02 Begin redistribution DBC.ResUsageScpu (0000H 0080H).02/09/30 15:10:33 Task 01 End redistribution DBC.ResUsageIpma (0000H 007FH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:33 Task 00 Begin redistribution DBC.ResUsageSvpr (0000H 0081H).02/09/30 15:10:33 Task 02 End redistribution DBC.ResUsageScpu (0000H 0080H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:33 Task 01 Begin redistribution DBC.ResUsageIvpr (0000H 0082H).02/09/30 15:10:33 Task 00 End redistribution DBC.ResUsageSvpr (0000H 0081H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:33 Task 02 Begin redistribution DBC.ResUsageSldv (0000H 0083H).02/09/30 15:10:33 Task 01 End redistribution DBC.ResUsageIvpr (0000H 0082H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:33 Task 00 Begin redistribution DBC.ResUsageShst (0000H 0084H).02/09/30 15:10:33 Task 02 End redistribution DBC.ResUsageSldv (0000H 0083H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:33 Task 01 Begin redistribution DBC.ResUsageSobj (0000H 0085H).02/09/30 15:10:33 Task 00 End redistribution DBC.ResUsageShst (0000H 0084H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:33 Task 02 Begin redistribution DBC.IdCol (0000H 0086H).02/09/30 15:10:34 Task 01 End redistribution DBC.ResUsageSobj (0000H 0085H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:34 Task 00 Begin redistribution DBC.TVM (0000H 0087H).02/09/30 15:10:34 Task 02 End redistribution DBC.IdCol (0000H 0086H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:34 Task 01 Begin redistribution DBC.TriggersTbl (0000H 0089H).02/09/30 15:10:34 Task 00 End redistribution DBC.TVM (0000H 0087H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 224 351.47KB 0 0 24702/09/30 15:10:34 Task 02 Begin redistribution DBC.Dbase (0000H 008AH).02/09/30 15:10:34 Task 01 End redistribution DBC.TriggersTbl (0000H 0089H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 21002/09/30 15:10:34 Task 00 Begin redistribution DBC.AccLogRuleTbl (0000H 008BH).02/09/30 15:10:34 Task 02 End redistribution DBC.Dbase (0000H 008AH).



Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 6 942 0 0 22002/09/30 15:10:34 Task 01 Begin redistribution DBC.Accounts (0000H 008CH).02/09/30 15:10:34 Task 00 End redistribution DBC.AccLogRuleTbl (0000H 008BH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:34 Task 02 Begin redistribution DBC.MDSRecoveryTbl (0000H 008DH).02/09/30 15:10:34 Task 01 End redistribution DBC.Accounts (0000H 008CH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19302/09/30 15:10:34 Task 00 Begin redistribution DBC.ParentChildCorrelation (0000H 008EH).02/09/30 15:10:34 Task 02 End redistribution DBC.MDSRecoveryTbl (0000H 008DH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19602/09/30 15:10:35 Task 01 Begin redistribution SysAdmin.FastLog (0000H 0436H).02/09/30 15:10:35 Task 00 End redistribution DBC.ParentChildCorrelation (0000H 008EH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:35 Task 02 Begin redistribution SysAdmin.HelpSyntax (0000H 045FH).02/09/30 15:10:35 Task 01 End redistribution SysAdmin.FastLog (0000H 0436H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:35 Task 00 Begin redistribution SystemFE.Temp_ReconfigSpace (0000H 0470H).02/09/30 15:10:35 Task 02 End redistribution SysAdmin.HelpSyntax (0000H 045FH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 1,736 264.47KB 0 0 20202/09/30 15:10:35 Task 01 Begin redistribution SystemFE.opt_cost_table (0000H 0472H).02/09/30 15:10:35 Task 00 End redistribution SystemFE.Temp_ReconfigSpace (0000H 0470H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:35 Task 02 Begin redistribution systemfe.opt_ras_table (0000H 0473H).02/09/30 15:10:35 Task 01 End redistribution SystemFE.opt_cost_table (0000H 0472H).Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:35 Task 00 Begin redistribution systemfe.CreateQCF (0000H 0474H).02/09/30 15:10:35 Task 02 End redistribution systemfe.opt_ras_table (0000H 0473H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19002/09/30 15:10:35 Task 01 Begin redistribution systemfe.CleanupQCF (0000H 0475H).02/09/30 15:10:35 Task 00 End redistribution systemfe.CreateQCF (0000H 0474H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 96 11.31KB 0 0 19802/09/30 15:10:35 Task 02 Begin redistribution SYS_CALENDAR.CALDATES (0000H 0495H).02/09/30 15:10:35 Task 01 End redistribution systemfe.CleanupQCF (0000H 0475H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 4 162 0 0 19802/09/30 15:10:36 Task 00 Begin redistribution DBC.FIRSTJOURNALTABLE (4000H 0000H).02/09/30 15:10:36 Task 00 End redistribution DBC.FIRSTJOURNALTABLE (4000H 0000H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 96 11.31KB 0 0 19802/09/30 15:10:36 Task 02 End redistribution SYS_CALENDAR.CALDATES (0000H 0495H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 30,028 469.19KB 0 0 24602/09/30 15:10:36 Table Redistribution Phase Ends02/09/30 15:10:36 Old Table Deletion Phase Begins02/09/30 15:10:36 Task 00 Begin deletion DBC.HW_Event_Log (0000H 0005H).02/09/30 15:10:36 Task 00 End deletion DBC.HW_Event_Log (0000H 0005H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:36 Task 01 Begin deletion DBC.SW_Event_Log (0000H 0006H).02/09/30 15:10:36 Task 01 End deletion DBC.SW_Event_Log (0000H 0006H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:36 Task 00 Begin deletion DBC.RCConfiguration (0000H 0007H).02/09/30 15:10:37 Task 00 End deletion DBC.RCConfiguration (0000H 0007H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:37 Task 01 Begin deletion DBC.CollationTbl (0000H 0008H).02/09/30 15:10:37 Task 01 End deletion DBC.CollationTbl (0000H 0008H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount



AllAmps: 0 0 0 0 19802/09/30 15:10:37 Task 00 Begin deletion DBC.Global (0000H 0019H).02/09/30 15:10:37 Task 00 End deletion DBC.Global (0000H 0019H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:37 Task 01 Begin deletion DBC.TransientJournal (0000H 001AH).02/09/30 15:10:37 Task 01 End deletion DBC.TransientJournal (0000H 001AH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:37 Task 00 Begin deletion DBC.Owners (0000H 001BH).02/09/30 15:10:37 Task 00 End deletion DBC.Owners (0000H 001BH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:37 Task 01 Begin deletion DBC.Parents (0000H 001CH).02/09/30 15:10:37 Task 01 End deletion DBC.Parents (0000H 001CH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:37 Task 00 Begin deletion DBC.ErrorMsgs (0000H 001EH).02/09/30 15:10:37 Task 00 End deletion DBC.ErrorMsgs (0000H 001EH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:37 Task 01 Begin deletion DBC.ChangedRowJournal (0000H 0020H).02/09/30 15:10:37 Task 01 End deletion DBC.ChangedRowJournal (0000H 0020H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:37 Task 00 Begin deletion DBC.SavedTransactionStatusTable (0000H 0024H).02/09/30 15:10:38 Task 00 End deletion DBC.SavedTransactionStatusTable (0000H 0024H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:38 Task 01 Begin deletion DBC.LocalTransactionStatusTable (0000H 0025H).02/09/30 15:10:38 Task 01 End deletion DBC.LocalTransactionStatusTable (0000H 0025H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:38 Task 00 Begin deletion DBC.UtilityLockJournalTable (0000H 0027H).02/09/30 15:10:38 Task 00 End deletion DBC.UtilityLockJournalTable (0000H 0027H).Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:38 Task 01 Begin deletion DBC.LocalSessionStatusTable (0000H 0028H).02/09/30 15:10:38 Task 01 End deletion DBC.LocalSessionStatusTable (0000H 0028H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:38 Task 00 Begin deletion DBC.SysRcvStatJournal (0000H 0029H).02/09/30 15:10:38 Task 00 End deletion DBC.SysRcvStatJournal (0000H 0029H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:38 Task 01 Begin deletion DBC.OrdSysChngTable (0000H 002AH).02/09/30 15:10:38 Task 01 End deletion DBC.OrdSysChngTable (0000H 002AH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:38 Task 00 Begin deletion DBC.RCConfiguration_V1R5 (0000H 002CH).02/09/30 15:10:38 Task 00 End deletion DBC.RCConfiguration_V1R5 (0000H 002CH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:38 Task 01 Begin deletion DBC.RCMedia (0000H 0030H).02/09/30 15:10:38 Task 01 End deletion DBC.RCMedia (0000H 0030H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:39 Task 00 Begin deletion DBC.LogonRuleTbl_V2R2 (0000H 0031H).02/09/30 15:10:39 Task 00 End deletion DBC.LogonRuleTbl_V2R2 (0000H 0031H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:39 Task 01 Begin deletion DBC.AccLogRuleTbl_V1R5 (0000H 0032H).02/09/30 15:10:39 Task 01 End deletion DBC.AccLogRuleTbl_V1R5 (0000H 0032H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:39 Task 00 Begin deletion DBC.AccLogTbl_V2R2 (0000H 0033H).02/09/30 15:10:39 Task 00 End deletion DBC.AccLogTbl_V2R2 (0000H 0033H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:39 Task 01 Begin deletion DBC.DBCAssociation_V2R2 (0000H 0034H).



02/09/30 15:10:39 Task 01 End deletion DBC.DBCAssociation_V2R2 (0000H 0034H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:39 Task 00 Begin deletion DBC.Translation (0000H 003BH).02/09/30 15:10:39 Task 00 End deletion DBC.Translation (0000H 003BH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:39 Task 01 Begin deletion DBC.Dbase_V1R4 (0000H 003DH).02/09/30 15:10:39 Task 01 End deletion DBC.Dbase_V1R4 (0000H 003DH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:39 Task 00 Begin deletion DBC.TVM_V1R5 (0000H 003EH).02/09/30 15:10:39 Task 00 End deletion DBC.TVM_V1R5 (0000H 003EH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:39 Task 01 Begin deletion DBC.EventLog (0000H 003FH).02/09/30 15:10:39 Task 01 End deletion DBC.EventLog (0000H 003FH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:39 Task 00 Begin deletion DBC.Next_V2R2 (0000H 0040H).02/09/30 15:10:40 Task 00 End deletion DBC.Next_V2R2 (0000H 0040H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:40 Task 01 Begin deletion DBC.AccessRights_V1R5 (0000H 0041H).02/09/30 15:10:40 Task 01 End deletion DBC.AccessRights_V1R5 (0000H 0041H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:40 Task 00 Begin deletion DBC.Accounts_V2R4 (0000H 0042H).02/09/30 15:10:40 Task 00 End deletion DBC.Accounts_V2R4 (0000H 0042H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:40 Task 01 Begin deletion DBC.Acctg (0000H 0043H).02/09/30 15:10:40 Task 01 End deletion DBC.Acctg (0000H 0043H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:40 Task 00 Begin deletion DBC.Indexes_V2R2 (0000H 0044H).02/09/30 15:10:40 Task 00 End deletion DBC.Indexes_V2R2 (0000H 0044H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCountAllAmps: 0 0 0 0 002/09/30 15:10:40 Task 01 Begin deletion DBC.RCEvent (0000H 0046H).02/09/30 15:10:40 Task 01 End deletion DBC.RCEvent (0000H 0046H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:40 Task 00 Begin deletion DBC.TVFields_V1R5 (0000H 0047H).02/09/30 15:10:40 Task 00 End deletion DBC.TVFields_V1R5 (0000H 0047H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:40 Task 01 Begin deletion DBC.Hosts (0000H 0048H).02/09/30 15:10:40 Task 01 End deletion DBC.Hosts (0000H 0048H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:41 Task 00 Begin deletion DBC.RecoveryLockTable (0000H 0049H).02/09/30 15:10:41 Task 00 End deletion DBC.RecoveryLockTable (0000H 0049H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:41 Task 01 Begin deletion DBC.RecoveryPJTable (0000H 004AH).02/09/30 15:10:41 Task 01 End deletion DBC.RecoveryPJTable (0000H 004AH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:41 Task 00 Begin deletion DBC.DBCInfoTbl (0000H 004BH).02/09/30 15:10:41 Task 00 End deletion DBC.DBCInfoTbl (0000H 004BH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:41 Task 01 Begin deletion DBC.SessionTbl (0000H 004CH).02/09/30 15:10:41 Task 01 End deletion DBC.SessionTbl (0000H 004CH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:41 Task 00 Begin deletion DBC.Dbase_V1R5 (0000H 004DH).02/09/30 15:10:41 Task 00 End deletion DBC.Dbase_V1R5 (0000H 004DH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount



AllAmps: 0 0 0 0 002/09/30 15:10:41 Task 01 Begin deletion DBC.SysSecDefaults (0000H 004EH).02/09/30 15:10:41 Task 01 End deletion DBC.SysSecDefaults (0000H 004EH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:41 Task 00 Begin deletion DBC.OldPasswords (0000H 004FH).02/09/30 15:10:41 Task 00 End deletion DBC.OldPasswords (0000H 004FH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:41 Task 01 Begin deletion DBC.InDoubtResLog (0000H 0050H).02/09/30 15:10:41 Task 01 End deletion DBC.InDoubtResLog (0000H 0050H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:42 Task 00 Begin deletion DBC.ReferencingTbls_V2R2 (0000H 0051H).02/09/30 15:10:42 Task 00 End deletion DBC.ReferencingTbls_V2R2 (0000H 0051H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:42 Task 01 Begin deletion DBC.ReferencedTbls_V2R2 (0000H 0052H).02/09/30 15:10:42 Task 01 End deletion DBC.ReferencedTbls_V2R2 (0000H 0052H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:42 Task 00 Begin deletion DBC.TableConstraints_V2R2 (0000H 0053H).02/09/30 15:10:42 Task 00 End deletion DBC.TableConstraints_V2R2 (0000H 0053H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:42 Task 01 Begin deletion DBC.AccLogRuleTbl_V2R2 (0000H 0054H).02/09/30 15:10:42 Task 01 End deletion DBC.AccLogRuleTbl_V2R2 (0000H 0054H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:42 Task 00 Begin deletion DBC.Dbase_V2R2 (0000H 0055H).02/09/30 15:10:42 Task 00 End deletion DBC.Dbase_V2R2 (0000H 0055H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:42 Task 01 Begin deletion DBC.TVM_V2R2 (0000H 0056H).02/09/30 15:10:42 Task 01 End deletion DBC.TVM_V2R2 (0000H 0056H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:42 Task 00 Begin deletion DBC.AccessRights_V2R2 (0000H 0057H).02/09/30 15:10:42 Task 00 End deletion DBC.AccessRights_V2R2 (0000H 0057H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:42 Task 01 Begin deletion DBC.TVFields_V2R2 (0000H 0058H).02/09/30 15:10:42 Task 01 End deletion DBC.TVFields_V2R2 (0000H 0058H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:43 Task 00 Begin deletion DBC.UnResolvedReferences (0000H 0059H).02/09/30 15:10:43 Task 00 End deletion DBC.UnResolvedReferences (0000H 0059H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:43 Task 01 Begin deletion DBC.ConstraintNames_V2R2 (0000H 005AH).02/09/30 15:10:43 Task 01 End deletion DBC.ConstraintNames_V2R2 (0000H 005AH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:43 Task 00 Begin deletion DBC.Indexes (0000H 005BH).02/09/30 15:10:43 Task 00 End deletion DBC.Indexes (0000H 005BH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:43 Task 01 Begin deletion DBC.Next (0000H 005CH).02/09/30 15:10:43 Task 01 End deletion DBC.Next (0000H 005CH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:43 Task 00 Begin deletion DBC.Dbase_V2R4 (0000H 005DH).02/09/30 15:10:43 Task 00 End deletion DBC.Dbase_V2R4 (0000H 005DH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:43 Task 01 Begin deletion DBC.TVM_V2R4 (0000H 005EH).02/09/30 15:10:43 Task 01 End deletion DBC.TVM_V2R4 (0000H 005EH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:43 Task 00 Begin deletion DBC.TVFields_V2R4 (0000H 005FH).



02/09/30 15:10:43 Task 00 End deletion DBC.TVFields_V2R4 (0000H 005FH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:43 Task 01 Begin deletion DBC.DBCAssociation (0000H 0060H).02/09/30 15:10:43 Task 01 End deletion DBC.DBCAssociation (0000H 0060H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:44 Task 00 Begin deletion DBC.TableConstraints_V2R4 (0000H 0061H).02/09/30 15:10:44 Task 00 End deletion DBC.TableConstraints_V2R4 (0000H 0061H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:44 Task 01 Begin deletion DBC.ReferencingTbls (0000H 0062H).02/09/30 15:10:44 Task 01 End deletion DBC.ReferencingTbls (0000H 0062H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:44 Task 00 Begin deletion DBC.ReferencedTbls (0000H 0063H).02/09/30 15:10:44 Task 00 End deletion DBC.ReferencedTbls (0000H 0063H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:44 Task 01 Begin deletion DBC.ConstraintNames (0000H 0064H).02/09/30 15:10:44 Task 01 End deletion DBC.ConstraintNames (0000H 0064H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:44 Task 00 Begin deletion DBC.AccLogTbl (0000H 0065H).02/09/30 15:10:44 Task 00 End deletion DBC.AccLogTbl (0000H 0065H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:44 Task 01 Begin deletion DBC.AccessRights (0000H 0066H).02/09/30 15:10:44 Task 01 End deletion DBC.AccessRights (0000H 0066H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 23.59KB 0 0 19802/09/30 15:10:44 Task 00 Begin deletion DBC.LogonRuleTbl (0000H 0067H).02/09/30 15:10:44 Task 00 End deletion DBC.LogonRuleTbl (0000H 0067H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:45 Task 01 Begin deletion DBC.TempTables (0000H 0068H).02/09/30 15:10:45 Task 01 End deletion DBC.TempTables (0000H 0068H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:45 Task 00 Begin deletion DBC.TempStatistics (0000H 0069H).02/09/30 15:10:45 Task 00 End deletion DBC.TempStatistics (0000H 0069H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:45 Task 01 Begin deletion DBC.TriggersTbl_V2R4 (0000H 006AH).02/09/30 15:10:45 Task 01 End deletion DBC.TriggersTbl_V2R4 (0000H 006AH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:45 Task 00 Begin deletion DBC.RepBatchStatus (0000H 006BH).02/09/30 15:10:45 Task 00 End deletion DBC.RepBatchStatus (0000H 006BH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:45 Task 01 Begin deletion DBC.AccLogRuleTbl_V2R4 (0000H 006CH).02/09/30 15:10:45 Task 01 End deletion DBC.AccLogRuleTbl_V2R4 (0000H 006CH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:45 Task 00 Begin deletion DBC.DataBaseSpace (0000H 006DH).02/09/30 15:10:45 Task 00 End deletion DBC.DataBaseSpace (0000H 006DH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:45 Task 01 Begin deletion DBC.TVFields (0000H 006EH).02/09/30 15:10:45 Task 01 End deletion DBC.TVFields (0000H 006EH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:45 Task 00 Begin deletion DBC.TextTbl (0000H 006FH).02/09/30 15:10:45 Task 00 End deletion DBC.TextTbl (0000H 006FH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:45 Task 01 Begin deletion DBC.Migration (0000H 0070H).02/09/30 15:10:46 Task 01 End deletion DBC.Migration (0000H 0070H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount



AllAmps: 0 0 0 0 19802/09/30 15:10:46 Task 00 Begin deletion DBC.Roles (0000H 0071H).02/09/30 15:10:46 Task 00 End deletion DBC.Roles (0000H 0071H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:46 Task 01 Begin deletion DBC.RoleGrants (0000H 0072H).02/09/30 15:10:46 Task 01 End deletion DBC.RoleGrants (0000H 0072H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:46 Task 00 Begin deletion DBC.UDFInfo (0000H 0073H).02/09/30 15:10:46 Task 00 End deletion DBC.UDFInfo (0000H 0073H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:46 Task 01 Begin deletion DBC.Profiles (0000H 0074H).02/09/30 15:10:46 Task 01 End deletion DBC.Profiles (0000H 0074H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:46 Task 00 Begin deletion DBC.TableConstraints (0000H 0075H).02/09/30 15:10:46 Task 00 End deletion DBC.TableConstraints (0000H 0075H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:46 Task 01 Begin deletion DBC.DBQLRuleTbl (0000H 0076H).02/09/30 15:10:46 Task 01 End deletion DBC.DBQLRuleTbl (0000H 0076H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:46 Task 00 Begin deletion DBC.DBQLRuleCountTbl (0000H 0077H).02/09/30 15:10:46 Task 00 End deletion DBC.DBQLRuleCountTbl (0000H 0077H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:46 Task 01 Begin deletion DBC.DBQLogTbl (0000H 0078H).02/09/30 15:10:47 Task 01 End deletion DBC.DBQLogTbl (0000H 0078H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:47 Task 00 Begin deletion DBC.DBQLStepTbl (0000H 0079H).02/09/30 15:10:47 Task 00 End deletion DBC.DBQLStepTbl (0000H 0079H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:47 Task 01 Begin deletion DBC.DBQLObjTbl (0000H 007AH).02/09/30 15:10:47 Task 01 End deletion DBC.DBQLObjTbl (0000H 007AH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:47 Task 00 Begin deletion DBC.DBQLSqlTbl (0000H 007BH).02/09/30 15:10:47 Task 00 End deletion DBC.DBQLSqlTbl (0000H 007BH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:47 Task 01 Begin deletion DBC.DBQLSummaryTbl (0000H 007CH).02/09/30 15:10:47 Task 01 End deletion DBC.DBQLSummaryTbl (0000H 007CH).Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:47 Task 00 Begin deletion DBC.DBQLExplainTbl (0000H 007DH).02/09/30 15:10:47 Task 00 End deletion DBC.DBQLExplainTbl (0000H 007DH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:47 Task 01 Begin deletion DBC.ResUsageSpma (0000H 007EH).02/09/30 15:10:47 Task 01 End deletion DBC.ResUsageSpma (0000H 007EH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:47 Task 00 Begin deletion DBC.ResUsageIpma (0000H 007FH).02/09/30 15:10:47 Task 00 End deletion DBC.ResUsageIpma (0000H 007FH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:47 Task 01 Begin deletion DBC.ResUsageScpu (0000H 0080H).02/09/30 15:10:48 Task 01 End deletion DBC.ResUsageScpu (0000H 0080H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:48 Task 00 Begin deletion DBC.ResUsageSvpr (0000H 0081H).02/09/30 15:10:48 Task 00 End deletion DBC.ResUsageSvpr (0000H 0081H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:48 Task 01 Begin deletion DBC.ResUsageIvpr (0000H 0082H).



02/09/30 15:10:48 Task 01 End deletion DBC.ResUsageIvpr (0000H 0082H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:48 Task 00 Begin deletion DBC.ResUsageSldv (0000H 0083H).02/09/30 15:10:48 Task 00 End deletion DBC.ResUsageSldv (0000H 0083H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:48 Task 01 Begin deletion DBC.ResUsageShst (0000H 0084H).02/09/30 15:10:48 Task 01 End deletion DBC.ResUsageShst (0000H 0084H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:48 Task 00 Begin deletion DBC.ResUsageSobj (0000H 0085H).02/09/30 15:10:48 Task 00 End deletion DBC.ResUsageSobj (0000H 0085H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:48 Task 01 Begin deletion DBC.IdCol (0000H 0086H).02/09/30 15:10:48 Task 01 End deletion DBC.IdCol (0000H 0086H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:48 Task 00 Begin deletion DBC.TVM (0000H 0087H).02/09/30 15:10:48 Task 00 End deletion DBC.TVM (0000H 0087H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:49 Task 01 Begin deletion DBC.TriggersTbl (0000H 0089H).02/09/30 15:10:49 Task 01 End deletion DBC.TriggersTbl (0000H 0089H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:49 Task 00 Begin deletion DBC.Dbase (0000H 008AH).02/09/30 15:10:49 Task 00 End deletion DBC.Dbase (0000H 008AH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:49 Task 01 Begin deletion DBC.AccLogRuleTbl (0000H 008BH).02/09/30 15:10:49 Task 01 End deletion DBC.AccLogRuleTbl (0000H 008BH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:49 Task 00 Begin deletion DBC.Accounts (0000H 008CH).02/09/30 15:10:49 Task 00 End deletion DBC.Accounts (0000H 008CH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:49 Task 01 Begin deletion DBC.MDSRecoveryTbl (0000H 008DH).02/09/30 15:10:49 Task 01 End deletion DBC.MDSRecoveryTbl (0000H 008DH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:49 Task 00 Begin deletion DBC.ParentChildCorrelation (0000H 008EH).02/09/30 15:10:49 Task 00 End deletion DBC.ParentChildCorrelation (0000H 008EH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:49 Task 01 Begin deletion SysAdmin.FastLog (0000H 0436H).02/09/30 15:10:49 Task 01 End deletion SysAdmin.FastLog (0000H 0436H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCountAllAmps: 0 0 0 0 19802/09/30 15:10:49 Task 00 Begin deletion SysAdmin.HelpSyntax (0000H 045FH).02/09/30 15:10:49 Task 00 End deletion SysAdmin.HelpSyntax (0000H 045FH). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:49 Task 01 Begin deletion SystemFE.Temp_ReconfigSpace (0000H 0470H).02/09/30 15:10:50 Task 01 End deletion SystemFE.Temp_ReconfigSpace (0000H 0470H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:50 Task 00 Begin deletion SystemFE.opt_cost_table (0000H 0472H).02/09/30 15:10:50 Task 00 End deletion SystemFE.opt_cost_table (0000H 0472H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:50 Task 01 Begin deletion systemfe.opt_ras_table (0000H 0473H).02/09/30 15:10:50 Task 01 End deletion systemfe.opt_ras_table (0000H 0473H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:50 Task 00 Begin deletion systemfe.CreateQCF (0000H 0474H).02/09/30 15:10:50 Task 00 End deletion systemfe.CreateQCF (0000H 0474H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount



AllAmps: 0 0 0 0 002/09/30 15:10:50 Task 01 Begin deletion systemfe.CleanupQCF (0000H 0475H).02/09/30 15:10:50 Task 01 End deletion systemfe.CleanupQCF (0000H 0475H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:50 Task 00 Begin deletion SYS_CALENDAR.CALDATES (0000H 0495H).02/09/30 15:10:50 Task 00 End deletion SYS_CALENDAR.CALDATES (0000H 0495H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 002/09/30 15:10:50 Task 01 Begin deletion DBC.FIRSTJOURNALTABLE (4000H 0000H).02/09/30 15:10:50 Task 01 End deletion DBC.FIRSTJOURNALTABLE (4000H 0000H). Statistics: RowCount ByteCount TotSecs CPUSecs IOCount AllAmps: 0 0 0 0 19802/09/30 15:10:50 Old Table Deletion Phase Ends02/09/30 15:10:50 Saving New Primary Hash Map Phase Begins02/09/30 15:10:51 Saving New Primary Hash Map Phase Ends02/09/30 15:10:51 Saving New Fallback Hash Map Phase Begins02/09/30 15:10:51 Saving New Fallback Hash Map Phase Ends02/09/30 15:10:51 Saving Current Primary Hash Map Phase Begins02/09/30 15:10:52 Saving Current Primary Hash Map Phase Ends02/09/30 15:10:52 Saving Current Fallback Hash Map Phase Begins02/09/30 15:10:52 Saving Current Fallback Hash Map Phase Ends02/09/30 15:10:52 Saving Current Configuration Map Phase Begins02/09/30 15:10:53 Saving Current Configuration Map Phase Ends02/09/30 15:10:53 Saving New Configuration Map Phase Begins02/09/30 15:10:53 Saving New Configuration Map Phase Ends02/09/30 15:10:53 Saving Backup IDs Phase Begins02/09/30 15:10:54 Saving Backup IDs Phase Ends02/09/30 15:10:54 Deleting New Hash Maps Phase Begins02/09/30 15:10:54 Deleting New Hash Maps Phase Ends02/09/30 15:10:54 Saving Bitmap Hash Table Phase Begins02/09/30 15:10:54 Saving Bitmap Hash Table Phase Ends02/09/30 15:10:54 Updating Disk Space Phase Begins02/09/30 15:10:55 Updating Disk Space Phase Ends02/09/30 15:10:55 Updating Vproc Configuration Begins02/09/30 15:10:55 Updating Vproc Configuration EndsSystem Time (Reconfiguration): 02/09/30 15:10:55 6120: Restarting DBS due to completion of reconfiguration.System is about to be reset.


Chapter 11:

Reconfiguration Estimator Utility

The Reconfiguration Estimator utility estimates an elapsed time for reconfiguration based upon the number and size of tables on your current system. The Reconfiguration Estimator prompts you for information about the planned upgrade and provides estimates for the following phases:

• Redistribution• Deletion• NUSI building

Audience

Users of Reconfiguration Estimator include the following:



Chapter 11: Reconfiguration Estimator UtilityStarting and Exiting Reconfiguration Estimator on NCR UNIX MP-RAS

Starting and Exiting Reconfiguration Estimator on NCR UNIX MP-RAS

Run Reconfiguration Estimator before you run Reconfiguration.


You can start and exit Reconfiguration from the Database Window.

To start Reconfiguration Estimator, do the following:

Step Action



2 In the Enter a command subwindow of the Supervisor window, type one of the following.

IF you type …THEN Reconfiguration Estimator assumes that the estimate …

start reconfig_estimator is based upon performance characteristics and current table sizes found on the running system.

You are prompted for the number of nodes and AMPs you are adding to the current configuration as well as the number of control tasks.

start reconfig_estimator parameter-file-name

is based upon performance characteristics and table sizes found in a specific parameter file.

Note: This is for NCR use only.

3 Press Enter.


Started ‘reconfig_estimator’ in window 1

The number represents the application window in which Reconfiguration Estimator is running. The Reconfiguration Estimator window appears.


Chapter 11: Reconfiguration Estimator UtilityStarting and Exiting Reconfiguration Estimator on NCR UNIX MP-RAS

To exit Reconfiguration Estimator, do the following:

Step Action

1 In the Enter a command subwindow of the Reconfiguration Estimator utility, do one of the following:

• Type Stop and press Enter.• Press F3.


Reconfiguration Estimator is about to be stopped.

2 In the Reconfiguration Estimator window, select File -> Close.



Chapter 11: Reconfiguration Estimator UtilityStarting and Exiting Reconfiguration Estimator on Microsoft Windows 2000

Starting and Exiting Reconfiguration Estimator on Microsoft Windows 2000


You can start and exit Reconfiguration Estimator from the following:




Step Action



2 In the Enter a command subwindow of the Supervisor window, type one of the following:







3 Press Enter.



The number represents the application window in which Reconfiguration Estimator is running. The Reconfiguration Estimator window appears.



Note: For details on the Database and Supervisor Windows, see Teradata Database Window.




Step Action

1 In the Enter a command subwindow of the Reconfiguration Estimator utility, do one of the following:

• Enter Stop and press Enter

or

• Press F3


Reconfiguration Estimator is about to be stopped.

2 In the Reconfiguration Estimator window, select File -> Close.


Step Action




The DBW appears.












5 Press Enter.



The number represents the application window in which Reconfiguration Estimator is running. The tab that previously said Application 1 now says Reconfig Estimator and is the active window.

Step Action

1 In the DBW, select the Reconfig Estimator tab.


Stop X

where X is the number of the window in which Reconfiguration Estimator is running.

3 Press Enter.


Step Action



Example

The following is sample output from Reconfiguration Estimator.

The current configuration has: 1 Nodes with 2 AMPs

The new configuration will be: 1 Nodes with 4 AMPs

The "my.sql" file shows: 105 tables using 3GB of data.

The estimated table redistribution time will be: 10 hours and 54 minutes.

The estimated table deletion time will be: 7 hours and 8 minutes.

The total estimated reconfig time will be: 18 hours and 12 minutes.


Chapter 12:

Recovery Manager Utility

The Recovery Manager (RCVManager) utility monitors the progress of a system in recovery as the result of a system crash and provides information to the user about the progress of the recovery. The utility also provides a mechanism for setting priority levels to optimize system recovery.

The recovery process might include one or more of the following:

• Online Transaction recovery• Down AMP recovery of changed data rows• Down AMP recovery of system level changes

Audience

Users of Recovery Manager include the following:

• NCR system engineers• System programmers• System administrators


Chapter 12: Recovery Manager UtilityStarting and Exiting Recovery Manager

Starting and Exiting Recovery Manager

You can run Recovery Manager only while the Teradata RDBMS is in one of the following states:

• Logon • Logon/quiet • Logoff • Logoff/quiet • Startup (if the system has completed voting for transaction recovery)

If you attempt to start Recovery Manager while the system is not in one of the allowable states, the utility displays the following error information and terminates:

RCVMANAGER can only be run when the system is in the “LOGON” or “LOGOFF” state or if the system is in the “STARTUP” state and has completed voting for transaction recovery. The current system is not in one of these allowable states thus preventing RCVMANAGER from operating.

RCVMANAGER terminated.


Chapter 12: Recovery Manager UtilityStarting and Exiting Recovery Manager on NCR UNIX MP-RAS

Starting and Exiting Recovery Manager on NCR UNIX MP-RAS


You can start and exit Recovery Manager from the following:



To start Recovery Manager, do the following:


After you start Recovery Manager, you cannot stop it by using the Supervisor STOP command. If you attempt to do so, you receive a message saying that the utility is unstoppable.

Step Action

1 In the Database window, select the Supervisor (Supvr) icon.



start rcvmanager

3 Press Enter.


Started ‘rcvmanager’ in window 1

The number represents the application window in which Recovery Manager is running. The Recovery Manager window appears.



To exit Recovery Manager, do the following:


If you start Recovery Manger from a remote console, you cannot use user IDs designating pooled sessions. Starting Recovery Manager from a remote console does not require a special privilege.


Step Action

1 In the Enter a command subwindow of the Recovery Manager utility, type the following:

QUIT;

2 Press Enter.



3 In the Recovery Manager window, select File -> Close.


Step Action


HUTCNS

You should see the initial Recovery Manager display, as shown below.





- Configuration

- LOCKsDisplay

- RCVmanager






3 To start Recovery Manager, type the following:

RCV

The initial Recovery Manager screen appears.

4 Enter responses to Recovery Manager prompts as you normally would type commands at your remote console.

Step Action

1 At the remote console screen, type the following:

QUIT;



Step Action


Chapter 12: Recovery Manager UtilityStarting and Exiting Recovery Manager on Microsoft Windows 2000

Starting and Exiting Recovery Manager on Microsoft Windows 2000


You can start and exit Recovery Manager using the following:





After you start Recovery Manager, you cannot stop it by using the Supervisor STOP command. If you attempt to do so, you receive a message saying that the utility is unstoppable.

Step Action






start rcvmanager

4 Press Enter.


Started ‘rcvmanager’ in window 1

The number represents the application window in which Recovery Manager is running. The Recovery Manager window appears.






Step Action

1 In the Enter a Command subwindow of the Recovery Manager, type the following:

QUIT;

2 Press Enter.



3 In the Recovery Manager window, select File -> Close.


Step Action




The DBW appears.



start rcvmanager

5 Press Enter.


Started ‘rcvmanager’ in window 1.

The number represents the application window in which Recovery Manager is running. The tab that previously said Application 1 now says Recovery Manager and is the active window.




Step Action

1 In the DBW, select the Recovery Manager tab.


QUIT;

3 Press Enter.





Chapter 12: Recovery Manager UtilityPriority Levels

Priority Levels

Priority levels can be assigned to system recovery or table rebuild by using the PRIORITY command feature of Recovery Manager. Control over job priority is assigned by selecting one of three priority levels:

• HIGH• MEDIUM• LOW

For information about these priority levels, see “REBUILD/RECOVERY PRIORITY” on page 12-44.

System recovery and disk rebuild are primarily I/O intensive tasks. The major portion of the time taken by a given task is involved in setting up for or waiting for completions of a disk or a BYNET message traffic operation. Very little manipulation or computation is required involved on the data once it is available.

If the competing work load of the system can be reasonably characterized, then it is possible to gauge the impact of the priority changes to recovery and rebuild operations. In general, you can use the following guidelines when assigning priorities:

Guideline Description

No work load competition

If there is no competition for resources as in a COLDWAIT restart for recovery, the priority setting of the recovery and rebuild jobs will have no practical effect.

Compute-intensive work load

If the online system work load is heavily compute intensive, raising the priority of the I/O intensive recovery operations can dramatically improve the recovery (including rebuild).

The high recovery will have a relatively minor impact on the online system operations. However, it will provide a better resource utilization and result in better system throughput. Similarly, a low priority of recovery in this work load will dramatically slow down recovery with only a moderate gain in online throughput.


Chapter 12: Recovery Manager UtilityPriority Levels

Moderate or heavy disk work load

If a moderate or heavy amount of disk and/or BYNET usage occurs by the online system, then recovery will show moderate throughput changes by controlling the priority setting but with a larger impact against the system throughput. Memory contention becomes a major component of operation in these cases.

I/O saturation As the I/O utilization approaches saturation, there are fewer opportunities to improve throughput or execution time of either the online system or the recovery job. In this case, we are competing for the same resource and that resource is not amenable to manipulation by control over the scheduling priority.

Guideline Description


Chapter 12: Recovery Manager UtilityOnline Transaction Recovery

Online Transaction Recovery

Online transaction recovery is automatically invoked by a system restart and includes the following processes:

• Rolling back transactions that were not completed at the time of the crash or restart.

• Completing transactions that were committed

Changes made to underlying data by transactions are recorded in the Transient Journal (TJ). AMPs keep track of transactions in progress using the TJ which is stored on each AMP’s disk.

IF … THEN …

all the modification operations successfully complete on all the AMPs working on behalf of the transaction

that transaction is successful and there is no further concern for recovery of that transaction.

a transaction does not complete due to a system crash or forced restart

those transactions are backed out as part of the system recovery process when the system restarts.


Chapter 12: Recovery Manager UtilityTransaction Recovery Sequence

Transaction Recovery Sequence

The general sequence of a system recovery is as follows:

Sequence Action

1 The status of each transaction on each online AMP is determined by the system.

All of the online AMPs at the time of the restart work together to determine which transactions were complete, and which ones were not completed. Completed transactions are ignored and incomplete ones are backed out. The process of rolling back incomplete transactions might take some time.

Write and exclusive locks are set against all data modified by incomplete transaction.

2 All locks needed for the recovery are set, and the system begins roll back or completion of the transactions.

3 The system accepts work and is operational.

Note: If new transactions reference the inconsistent data of to-be-rolled-back transactions, they are blocked until the recovery process restores the data and releases the lock.

4 Down AMP recovery begins.


Chapter 12: Recovery Manager UtilityMultiple Recovery Sessions

Multiple Recovery Sessions

A recovery session is the set of actions to be taken as a result of the system restart for all transactions that were in progress at the time the system restarted.

All of the online AMPs at the time of the restart work together to determine which transactions were complete, and which ones were not completed. Completed transactions are ignored and incomplete ones are backed out.

If new work or transactions are allowed in during recovery, and another restart occurs, an additional recovery session is created. Then there will be two recovery sessions:

• The first one that was created for the previous restart• The new one that was created for the current work

Since there is a sequential relationship between these two recovery sets and they are inherently mutually exclusive, they are kept as separate operations.

Therefore, if the system is unreliable (prone to crashing) and the amount of work to be done in each recovery session is large, then three, four or more recovery sessions may be created. Each session exists until all the incomplete transactions of the session are rolled back.

The issue of multiple recovery sessions may be avoided by having all the restarts be COLDWAIT, since the WAIT means to wait for recovery to complete before allowing the system to accept new work from the hosts. Although the recovery proceeds faster, since it is not competing with any other new work for computing resources, the system remains totally unavailable to the database users.


Chapter 12: Recovery Manager UtilityDeferred Transaction Recovery

Deferred Transaction Recovery

When the RDBMS crashes, a COLD restart is activated and an online transaction recovery or deferred recovery is started. The only time a deferred recovery is not done is when the operator enters a COLDWAIT restart.

Deferred transaction recovery allows new transactions to come in from the connected hosts. The process of bringing the system up after a crash causes the locks to be set. If new transactions should attempt to reference the inconsistent data of the to-be-rolled-back transactions, they are blocked until the recovery process restores the data and releases the lock.


Chapter 12: Recovery Manager UtilityDown AMP Recovery

Down AMP Recovery

Down AMP Recovery is a process that handles all changes to entire tables or rows, either fallback and primary, while the AMP is down or offline. Down AMP Recovery updates a recovering AMP with data that the system processed while the AMP was down. The down AMP is considered to be in offline catchup mode. Catchup mode indicates that the AMP is logically offline and in the process of updating its tables so that they are synchronized with the online AMPs in the cluster.

In a crash or restart condition, it is possible to lose an AMP from, for example, a CPU board failure without losing its underlying disk data. The remainder of the system can then restart and recover the transactions without the failed AMP.

After the down AMP is ready to rejoin the system, the down AMP recovers the lost data by performing the following steps:

Down AMP Recovery Operations Display

The following display indicates the fields that are referenced in the down AMP recovery operations explanation on the next page. This display is printed out by the Recovery Manager. For a description of the fields in the following display, see “Down/Catchup AMP Recovery Status” on page 12-36.

Step Action

1 Restoring the data to a consistent state, relative to the transactions the down AMP was working on at the time of the failure.

The down AMP applies the information in its Transient Journal against its underlying data. Moreover, the down AMP must concur with the choice of the rest of the system whether to rollback or commit each transaction.

2 Updating the restored data to match all changes made to the online system while the AMP was down (Down AMP Recovery)


Chapter 12: Recovery Manager UtilityDown AMP Recovery

DOWN AMP RECOVERY STATUS at HH:MM:SS MM/DD/YY

AMP to be Current Pass Next Pass

caught up Pass OJ CJ OJ CJ

---------- ---- --- --------- --- ---------

0001 0 0 0 1 1,081

- AMP Status: Online Catchup

- Not currently executing recovery

0002 1 5 145,822 1 25,081

- AMP Status: Offline Catchup

- Transaction Recovery: 25,488 TJ Rows

0003 1 0 2,142 0 0


- Change Row Recovery: 26% complete in this pass

0004 2 2 201,558 0 4,228


- Rebuilding Database1.Table1: 45% complete

0005* 4 0 0 0 2,888


- Between passes

* - would probably be placed in online catch up if a restart occurred


Chapter 12: Recovery Manager UtilityRecovering Down AMPs

Recovering Down AMPs

Perform steps 1 through 4 only when offline catchup AMPs exist. If an AMP is still physically down, do not perform these steps.

To recover a down AMP, do the following:

Step Action

1 Previously down AMPs that are now available begin their local transaction recovery (referred to as offline catchup AMPs). This step must be completed before going to step 2.

2 The extracted OJ is processed, rebuilding various subtables.

3 The extracted CJ rows are then processed by sending the changed rows (or notification that the rows were deleted) to the catchup AMP.

4 The OJ entries are applied. Ones which take a significant amount of time are the build operations.

5 Current CJ entries are applied. Each CJ entry represents one row to be updated (insert, delete, update).

6 Online AMPs in the down AMP cluster extract all the current build records from the OJ and CJ, and sort them to eliminate duplicates. Any CJ entries referring to rows in a table which will be rebuilt are deleted. Other OJ operations are sent to the catchup AMP for execution.

7 The Next Pass OJ and CJ entries become the Current Pass entries.

8 Repeat steps 2 through 7 indefinitely.

9 After the AMP is sufficiently caught up, it becomes eligible to become an online catchup AMP on the next restart. This is denoted by displaying an asterisk (*) under the column entitled, AMP to be caught up, in the DOWN AMP RECOVERY STATUS screen of the RCVManager status display. See the previous display screen.


Chapter 12: Recovery Manager UtilityRecovery Journal

Recovery Journal

When an AMP in a cluster goes down, and the fallback option is specified for a table, the Down AMP Recovery Journal (RJ) records changes made to the fallback tables that are applicable to the down AMP. The journal is active only during an AMP failure and is only used for fallback tables.

The Recovery Journal process for a down AMP is as follows:

Step Action

1 Operational AMPs in the cluster begin logging entries into the Down AMP RJ.

2 The Down AMP RJ records the changes that should have been made to fallback-protected rows of the inoperative AMP.

3 The changes are applied when the down AMP recovers.


Chapter 12: Recovery Manager UtilityTypes of Recovery Journal Records

Types of Recovery Journal Records

The Recovery Journal maintains the following two sets of records:

Record Function

Changed Row Journal (CJ)

Logs changed rows in an AMP cluster by logging pointers to the rows that have been changed, but does not log the actual rows.

Ordered System Change Journal (OJ)

Logs events such as, building the index, creating a permanent journal, and performing a table rebuild.

These types of changes may be termed system-level changes and involve Data Definition Language (DDL) operations, since they affect all AMPs, not only a single row update.


Chapter 12: Recovery Manager UtilityChanged Row Journal

Changed Row Journal

The CJ recovery needs to match its data against all changes made to the online system while the AMP was down. The most common type of changes includes modifications made to individual rows by Data Manipulation Language (DML) operations of inserting, deleting, and updating rows in pre-existing tables.

Each modified row is remembered in the system CJ, which is local to each AMP on which the modification takes place. Since the modification is done only while an AMP is down, the CJ is only populated on AMPs in a cluster while an AMP is down. AMPs are arranged into a group called clusters so that each AMP provides fallback protection to other members within that same group.

Entries stored in the CJ include only the table ID and row ID of the row which was modified. When the down AMP recovers, the actual row is extracted from the fallback or primary subtable; the row image is not stored redundantly in the CJ.


Chapter 12: Recovery Manager UtilityOrdered System Change Journal

Ordered System Change Journal

System-level changes are data changes that are applied to the online system while an AMP is down. These changes are called system level because they affect all AMPs, as opposed to a single row update.

These changes cover DDL operations such as, DROP TABLE, CREATE TABLE, and CREATE/DROP INDEX. Other operations include a change to every single row within a table, for example, drop a column. For these types of operations, recovery involves copying every single row of the table, for those rows the AMP owns, over to that down AMP (a table rebuild).

Therefore, the majority of the rows found in the OJ are build records that identify tables that need to be built for created tables, or rebuilt when the AMP is recovered. Other OJ records are HUT Lock set and release records, and in-doubt two-phase commit transaction.


Chapter 12: Recovery Manager UtilityDeferred Down AMP Recovery

Deferred Down AMP Recovery

The process of Deferred Down AMP Recovery means that while a down AMP remains down and recovering, the rest of the system continues its operations with the connected hosts.

The following sections describe the modes:

• Offline catchup• Online catchup


Chapter 12: Recovery Manager UtilityOffline Catchup

Offline Catchup

In offline catchup mode, the new transactions for the down AMP are performed by other AMPs in the cluster. Therefore, new change row and system change entries are made while the down AMP is processing the old ones. While the AMP is in catchup mode, it is considered logically offline.


Chapter 12: Recovery Manager UtilitySetting a Down AMP to Offline Catchup Mode

Setting a Down AMP to Offline Catchup Mode

To set a down AMP to offline catchup mode, do the following:

Step Action

1 Start the Vproc Manager utility.

2 Enter the following command to list the RDBMS logical configuration:

status;

A screen similar to the following one displays:


Vproc Rel. Node Crash Vproc Config Config Cluster/ RvcJrnl/Number Vproc# ID Movable Count State Status Type Host No. Host Type

0* 1 0-0 No 0 Online Online AMP 0 On1 2 0-0 No 0 Offline Down AMP 0 On16383 3 0-0 No 0 Online Online PE 52 COP

_____________________________________________________________________________________

* DBS Control AMPDBS State: Logons are enabled - Users are logged onDBS RestartKind: COLDThe disable list is empty


Chapter 12: Recovery Manager UtilitySetting a Down AMP to Offline Catchup Mode

3 Enter the following command to bring up the downed AMP:

set 1 = online;

If vproc 1 goes into catchup mode, you will get the following message:

Vproc 1 will begin recovery in the background via the Recovery Control Task

4 Enter the command:

status:

to verify that the AMP is in Utility Catchup mode.

While in the offline mode, it has OJ build records to process and/or a large number of CJ rows. This reduces the amount of data that is locked, but any new transactions on the online system creates additional OJ and CJ rows. Since you cannot place an offline AMP into the online system, these passes could continue forever or until the system restarts.

A screen similar to the following one displays:

Step Action


Vproc Rel. Node Crash Vproc Config Config Cluster/ RvcJrnl/Number Vproc# ID Movable Count State Status Type Host No. Host Type

0* 1 0-0 No 0 Online Online AMP 0 On1 2 0-0 No 0 Utility Catchup AMP 0 On16383 3 0-0 No 0 Online Online PE 52 COP

_____________________________________________________________________________________

* DBS Control AMPDBS State: Logons are enabled - The system is quiescentDBS RestartKind: COLDThe disable list is empty


Chapter 12: Recovery Manager UtilityVerifying if an Offline AMP is in Catchup Mode

Verifying if an Offline AMP is in Catchup Mode

To verify if an offline AMP, for example, is almost in catchup, do the following:

One of the following messages appears:

If a COLDWAIT restart is performed, the operations are similar to those of Transaction Recovery. In COLDWAIT the system remains offline with no incoming transactions until all recovering AMPs have fully recovered. After recovery, the AMPs are all set to online status and the system completes start-up.

In offline catchup, there is a race to see if the catchup can run faster than the new update transactions coming in online. The other AMPs handle the fallback responsibility for the down AMP, and the additional work involved in writing CJ or OJ records.

If an AMP is designated to be in offline catchup mode, then a COLD restart must be initiated, but only after the AMP has sufficiently recovered, to bring the offline AMP back online.

Note: Sufficiently recovered refers to the third message in the table above.

Step Action

1 Start up the RcvManager utility.

2 Enter the following command to check the offline AMP status:

list status;

Message … Means that the …

- AMP Status: Not in recovery

- Down

AMP is still down.


- Executing miscellaneous Recovery actions

AMP is in catchup mode.


- Between Passes

* - would probably be placed in online catchup if a restart occurs.

AMP is in catchup mode, and if a restart occurs, the AMP is placed in online catchup mode.


Chapter 12: Recovery Manager UtilityOnline Catchup Mode

Online Catchup Mode

In online catchup mode, the previously down AMP will also accept transactions, as will the rest of the system. In this mode, all the data that needs updating is locked, so that new data does not operate on the obsolete data.

When the down AMP has a small amount to recover, it can be placed into online catchup.

To begin online catchup mode, follow the steps that are described in the Offline Catchup section.

Since the AMP is online and participating in the new transaction coming into the system, there are no new CJ or OJ entries being created for it. After all of the residual CJ processing is completed, the system becomes online. If you go to Vproc Manager and look at the AMP status, you will see Online on Vproc State and Online on Config Status. At this point, the AMP rejoins the other online AMPs automatically without the need of a system restart.


Chapter 12: Recovery Manager UtilityStartup/Restart Messages

Startup/Restart Messages

At startup, messages are displayed to report the startup progress and the system status. This report includes some recovery process messages as shown below:

The following table lists and explains these and other messages.

Message # … Means …

1 - AMP mmmm in cluster nnn is back online

the specified AMP which was offline is now back online.

2 - AMP mmmm is in offline catchup

the AMP is in offline catchup mode.

3 - AMP mmmm is in online catchup

the AMP is in online catchup mode.

H005 Control AMP 001-2

98/02/06 11:35:31 Running DBS Version: 02.00.02.5098/02/06 11:35:31 Running PDE Version: 2.0.2.118.5798/02/06 11:35:32 Current DBS config maps are synchronized (Version: 11)98/02/06 11:35:32 New DBS config maps are synchronized (Version: 11)98/02/06 11:35:32 AMP 0000 has been selected as the Control AMP98/02/06 11:35:33 Initializing DBS Vprocs98/02/06 11:35:36 Configuration is operational98/02/06 11:35:36 Starting AMP partitions98/02/06 11:35:40 Connection accepted98/02/06 11:36:02 Voting for transaction recovery98/02/06 11:36:05 Recovery session 1 contains 77 rows on AMP 000098/02/06 11:36:16 Starting transaction recovery98/02/06 11:36:18 Completed transaction recovery98/02/06 11:36:18 Starting PE partitions98/02/06 11:37:03 System is operational98/02/06 11:37:05 Users are logged on98/02/06 11:37:05 Logons are enabled


Chapter 12: Recovery Manager UtilityStartup/Restart Messages

4 - AMP mmmm not brought online for the following reason(s):

one of the following:

• Changed row journal count of ZZ,ZZZ,ZZ9 exceeds 3000 rows.

• At least one “long” running ordered journal record remains.

• At least one HUT lock might exist in the cluster.

• At least one two-phase-commit transaction is in doubt.

5 - Completed transaction recovery

Transaction Recovery for online AMPs is compete.

6 - Recovering down AMPs the recovery process is updating tables on AMPs that are in offline catchup.

Note: If there was no down AMP in catchup recovery mode, this message is not displayed.

7 - Recovery session 1 contains 103 rows on AMP 0001

that AMP 0001 has the largest number of rows in the transient journal for the given recovery session. Other AMPs probably have a similar or less rows for the same recovery session. The count reflects how many rows were in the transient journal at the time of the system restart. It does not necessarily mean a rollback action has to be performed for each row.

8 - Starting transaction recovery

transaction recovery has started on online AMPs.

9 - Startup will wait for recovery to complete

the user initiated a COLDWAIT restart.

10 - Voting for transaction recovery

the application software is determining if there were any incomplete transactions left from the previous operation. Voting is a process by which each AMP examines the transactions that were in process. Any uncompleted transaction will have to be rolled back.

Message # … Means …


Chapter 12: Recovery Manager UtilityRestarts

Restarts

Two types of restarts exist:

• Automatic • User-initiated

Automatic Restarts

When a software or hardware failure occurs, the system automatically attempts to bring itself back up into an operational state. This type of restart results in an automatic execution of a system-recovery operation. As part of the restart processing, the system saves the error codes that were generated, reloads system software (RDBMS), and enables logons.

User-Initiated Restarts

Manual restarts are activated by the user. Users can initiate a restart from any of the hardware switches or by one of the following methods:

• Issue the RESTART command. For information on the RESTART command, see the Vproc Manager utility in Teradata RDBMS Utilities.

• At the system command line, type the following command:tpareset comment-string


Chapter 12: Recovery Manager UtilityRecovery Manager Commands

Recovery Manager Commands

After you start Recovery Manager, you are prompted to type commands as shown below:

Enter command, “QUIT;” or “HELP;” :

At the prompt of either your application window or your terminal screen, you can type in any valid Recovery Manager command.

All Recovery Manager commands end with a semicolon. The utility does not process a command until it detects a semicolon, even if you press Enter.

The following sections describe each of the Recovery Manger commands in alphabetical order.


Chapter 12: Recovery Manager UtilityRecovery Manager Commands

DEFAULT PRIORITY

The DEFAULT PRIORITY command sets the priorities to the default values (that is, REBUILD will be set to MEDIUM and RECOVERY to LOW).

Syntax

Usage Notes

If the PRIORITY command has never been executed or the system has been sysinited, the priorities are set to the default values. The priority remains the same until an initial or subsequent PRIORITY command changes it again. When the priority command is entered during a rebuild or recovery operation, several minutes may elapse before the new priorities take effect.

When you type the DEFAULT PRIORITY command, the event is logged in the /var/adm/streams/error.mm-dd file in the system you are working on, and the following messages are displayed.

YY/MM/DD HH:MM:SS RECOVERY priority changed to LOW; it was <old priority>

YY/MM/DD HH:MM:SS REBUILD priority changed to MEDIUM; it was <old priority>

When the default priority command is entered, both messages are generated.

DEFAULT

GS04A035

PRIORITY ;


Chapter 12: Recovery Manager UtilityHELP

HELP

Function

The HELP command displays the syntax for the commands supported by Recovery Manager.

Syntax

Usage Notes

The HELP command displays information for all the Recovery Manager commands:

HELP

GT11A001

;

RCVMANAGER provides a means for the user to interact with the recoverysub-system. The syntax of a RCVMANAGER command is:

HELP ; or <F7>

QUIT;

{ STATUS [<proc-id>] }LIST { } ; { LOCKS }

{ REBUILD } [Low ]{ } PRIORITY [ medium ] ;{ RECOVERY } [ High ]

DEFAULT PRIORITY;

The HELP command displays this help message text.

The <7> function key will display a menu driven HELP screen, however,it is available only from the local DBS console.

The QUIT command will terminate the RcvManager Utility.

The LIST STATUS command displays information about recovery operationsin progress. The processor id option provides additional detailed information about a specific down AMP.

The LIST LOCKS command displays a list of all locks currently held byonline transaction recovery.

The PRIORITY command can be used to either display or set the currentpriorities for rebuild or recovery. For example:

RECOVERY PRIORITY; Displays the currrent recovery priority setting.

RECOVERY PRIORITY LOW; Sets the recovery priority to low.

DEFAULT PRIORITY; Sets the recovery priority to low and the rebuild priority to medium

For additional information consult the documentation.


Chapter 12: Recovery Manager UtilityLIST

LIST

Function

The LIST command displays information related to either a transaction recovery or an AMP recovery.

Syntax

where:

Syntax element … Provides …

STATUS transaction recovery information and AMP recovery information for unavailable AMPS.

• The displayed row count of a large sized table will be rounded to the nearest thousand.

• The recovery build records specify rebuild operations separately for each index of a table, which causes a rebuild of both the primary and fallback data for that index. Hence, the displayed sector count is not the total size for the table as derived from other methods.

• The sector count that is displayed is the sum of the estimated number of sectors for both primary and fallback rows to be copied over from the other AMPs in the cluster or recreated Non Unique Secondary Index (NUSI) indexes for all index subtables of the table which have an OJ build record. This includes the OJ build records of both the current pass and the next pass.

proc-id additional detailed information about the recovery process of a specific AMP including the list of tables needing to be rebuilt.

The LIST STATUS proc-id command is only allowed for processors that are in down AMP recovery (offline catchup) or the AMPs listed in the LIST STATUS display. No additional detail information is provided for AMPs that are in online catchup, since no build records exist for these AMPs.

LOCKS an option that displays locks held by online transaction recovery.

LIST

GT11A002

;

LOCKSproc-id

STATUS



LIST STATUS

The LIST STATUS command generates two reports:

• Online Transaction Recovery Journal Counts• Down/Catchup AMP Recovery Status

The first reports transaction recovery information, and the second reports AMP recovery information for unavailable AMPs.

Online Transaction Recovery Journal Counts

The Online Transaction Recovery Journal Counts allows the user to monitor transaction recovery processing. It displays information on the transient journal and transactions that were in progress during transaction recovery processing. An example report is shown below:

Note: A new recovery session is created for each restart that is not a COLDWAIT restart.

Report Information

This report displays a list of all active recovery sessions and the maximum number of transaction journal rows remaining to be processed for the AMP that has this maximum count.

Since all AMPs must complete processing of a given recovery session before the processing of the next session begins, this information is sufficient to calculate the worst-case count of transaction journal entries to be scanned. You can use this count as a rough guide to recovery processing time.

However, because this is only a rough guide, you must also take into consideration the following variables when estimating the time involved in the recovery process:

• The amount of work required by recovery to process a given transaction journal row can vary by orders of magnitude; that is, some rows can be processed in a fraction of a second, whereas others can take hours to process.

• The transaction journal may contain many rows which require no recovery processing.

The online transaction recovery journal counts are updated by each AMP every time a checkpoint is taken.

ONLINE TRANSACTION RECOVERY JOURNAL COUNTS at 13:49:28 98/02/06

Recovery AMPSession Count W/Count------- ---------- -------

1 765 12 2 38,432 5 3 1,388 20



Thus, every time an AMP performs checkpoint, its online transaction recovery journal count is decreased by 1000, and a later LIST STATUS command may display different results.

If no recovery sessions are active, the report title is printed without any contents.

Down/Catchup AMP Recovery Status

The Down AMP Recovery Status report generates the information shown in the following screen example:

The example report contains three sets of data lines (together with a column header) for each AMP participating in the down AMP recovery process. The first data line is explained by the column headers. The second and third data lines indicate the status.

The following table describes the Header and first-line data.

DOWN AMP RECOVERY STATUS at HH:MM:SS MM/DD/YY

AMP to be Current Pass Next Pass

caught up Pass OJ CJ OJ CJ

---------- ---- --- --------- --- ---------

0001 0 0 0 1 1,081


- Not currently executing recovery

0002 1 5 145,822 1 25,081


- Transaction Recovery: 25,488 TJ Rows

0003 1 0 2,142 0 0


- Change Row Recovery: 26% complete in this pass

0004 2 2 201,558 0 4,228


- Rebuilding Database1.Table1: 45% complete

0005* 4 0 0 0 2,888


- Between passes

* - would probably be placed in online catch up if a restart occurred



Data Description

AMP to be caught up

Indicates the AMP number to be caught up.

In addition to the processor number, this column might contain one of the following notations:

Notation … Indicates that . . .

* this AMP may be placed in online catchup if the system restarts. If the displayed information is no longer valid by the time the system restarts, the AMP might remain in offline catchup.

[1] one or more host utility locks are held in the cluster of the recovering AMP and that the data on the AMP cannot be recovered because there is a conflict between the host utility lock and the recovery locking requirements.

[2] one or more 2 Phase Commit (2PC) in-doubt sessions exist within the cluster of the recovering AMP.

Pass Indicates the number of the recovery pass. At the beginning of a recovery pass all rows in the OJ and CJ are extracted. This is the total number of rows to be processed during that pass. If additional changes are sent to the AMP during the processing of the current pass, they are queued up for the next pass. When the processing of rows of the current pass is complete, the pass number is incremented and the rows for the next pass are extracted from the OJ and CJ and processed.

Current Pass The OJ column contains the number of rows in the ordered system change journal to be processed during the current recovery pass. The CJ column contains the number of rows in the changed row journal to be processed during the current recovery pass.

Next Pass The OJ column contains the number of rows in the ordered system change journal to be processed during the next recovery pass. The CJ column contains the number of rows in the changed row journal to be processed during the next recovery pass.

If there are transactions that are updating user tables, these counts will go up as a result of those updated transactions. Subsequent displays could show an increase in the count.



The following table describes the second data line (AMP Status).

The following table describes the third data line (AMP Recovery Status Line).

Data Description

Online Catchup This AMP is online during recovery processing and accepts new work. Locks are applied against all objects that need to be updated before new work is accepted. In this status, the OJ count is usually zero and no new OJ or CJ entries are created.

Offline Catchup This AMP is logically (not physically) offline during recovery processing. No new work is accepted by this AMP. Read locks are applied on the online AMPs in the cluster only against the specific data of an object that has to be updated.

Not In Recovery This AMP is not running down AMP recovery; it is physically offline.

Data Description

Transaction Recovery: ZZZ,ZZZ,ZZ9 TJ Rows

Specifies the number of rows in the transaction recovery journal to be processed in this recovery pass. The transaction recovery journal contains the before images of all change objects affected by every transaction. Transaction recovery is the first step of the first recovery pass only. Each Z represents a digit and 9 represents any non-zero value.

Rebuilding Table [DBase.Table]: Z9% complete in this pass

Specifies the name of the table being rebuilt and the percentage of completion. Tables are rebuilt as a result of DDL changes (that is, drop or add a column) to a table, or a Multiload operation has affected a table while an AMP was down.

Change Row Recovery: Z9% complete in this pass

This is caused by DML changes to the tables. This step of recovery is entered when DML (for example insert update, or delete) changes have been made to tables in a down AMP. While an AMP is down, the other AMPs in the cluster modify their fallback rows for the down AMP, and also modify their own rows for which the down AMP has fallback responsibility.

Between Passes The state of between passes arises since there is a five minute pause between passes. Primarily, this is intended to allow current operations, including any new work creating CJ and OJ entries, to finish and release their locks, so that recovery will not compete with online operations.



LIST STATUS proc-id

The LIST STATUS command with the proc-id option specified as mmmm provides additional detailed information about the recovery process of a specific AMP, including the following:

• Status• Pass number• Current pass count• Next pass count• A list of tables that need to be rebuilt• The tables for which an OJ build record exists• An estimated sector count of that table

The LIST STATUS proc-id command is only allowed for processors that are in down AMP recovery (offline catchup), or the AMPs listed in the LIST STATUS display. No additional detail information is provided for AMPs that are in online catchup since no build records exist for these AMPs.

A typical down AMP recovery status report is shown in the example report below:

Miscellaneous OJ Processing Indicates that time is spent processing the various short running OJ entries, for example, releasing host utility locks.

Down Indicates that this AMP is not involved in the recovery process. However, statistics are maintained to indicate how much accumulated work remains to be recovered before the AMP can become operational.

Not currently executing recovery

Indicates that the AMP has not yet reached the point of starting Transaction Recovery or extracting OJ logs. The AMP is neither at the very early stage in recovery or has not yet started it. (The AMP might be down.)

Data Description



DOWN AMP RECOVERY STATUS AT 12:27:25 99/10/13

AMP to be Current Pass Next Passcaught up Pass OJ CJ OJ CJ--------- ---- ----------- ----------- ----------- ----------- 00001 0 0 0 107 16,531 - AMP Status: Not in recovery - Down

TABLES TO BE REBUILT

Row Count Status Name------------ ------------------------------- ------------------- 1,896 "DBC"."ErrorMsgs" 12 "DBC"."Translation" 0 "DBC"."Dbase_V1R4" 0 "DBC"."TVM_V1R5" 0 "DBC"."AccessRights_V1R5" 0 "DBC"."TVFields_V1R5" 0 "DBC"."Hosts" 0 "DBC"."Dbase_V1R5" 0 "DBC"."Dbase_V2R2" 0 "DBC"."TVM_V2R2" 0 "DBC"."TVFields_V2R2" 24 "DBC"."Dbase" 696 "DBC"."TVM" 5,892 "DBC"."TVFields" 3,354 "DBC"."AccessRights"-------------------------------------------------------------------- 95,534 total. The estimated rebuild time is 7 minutes.



The following table shows the information contained in the columns under the TABLES TO BE REBUILT report.

Data Description

Row Count The number of rows in the table to be rebuilt.

Status Displays up to six possible states where the recovery process may be when LIST STATUS proc-id is executed. The possible values in this column can be the following:

Value Description

Blank Indicates that the table might be or will be rebuilt.

Multiload Target Table in Apply

Indicates that the table is a target table of a MultiLoad job. In this case the OJ build record is discarded since the likelihood is that the AMP will be online before the MultiLoad job finishes. If this is the case, MultiLoad will force a rebuild of the table while the AMP is online. If the MultiLoad job completes before the AMP is online, a new OJ build record is generated, meaning the rebuild will occur in a later pass.

Locked Indicates that the table is currently locked by an EXCLUSIVE lock and that a valid sector count cannot be taken. Unless the lock is part of a drop table operation, the table will eventually be rebuilt in the next pass.

Non-Fallbacked Indicates that a non-fallback table has been marked for a rebuild operation. Since all non-fallback tables are deleted during rebuild operation, the sector count associated with this table is meaningless.

Table Rebuild Indicates that this OJ build record is for a table that is currently being rebuilt. This OJ build record will be discarded.

Restore Indicates that a table may have an OJ build record for it, but it is currently the target of a (not necessarily active) restore operation. In this case, the OJ build record is discarded.

Name The name of the tables to be rebuilt.



LIST LOCKS

The LIST LOCKS command displays all locks currently held by transaction recovery.

Only a single report is generated by the LIST LOCKS command. An example of this report is shown below:

LOCKS HELD BY ONLINE TRANSACTION RECOVERY AT 15:27:23 00/04/05

Lock Lock ObjectMode Object Name---------- -------- ------------------------------------Exclusive Table 0 1001, 0 1050 (0000H 03E9H, 0000H 041AH)Write Database “AssetsDB”Write Row hash “Clients”.”TurnOver”Write Row hash “EmployeeInfo”.”NewHires”Exclusive Table “SampleDB.sampleTable”

The report displays the mode of the lock held (write or exclusive), the object type locked (database, table, row range, or row hash) and the name of the object. The report is sorted alphabetically by object name.

For row range and row hash locks, the row information does not display. Only the table within which the row resides is displayed.

If Recovery Manager is unable to determine the database name associated with an object, Recovery Manager displays the database ID in decimal and hex. The same is true if the table name cannot be determined.

LIST LOCKS displays only those locks currently held by transaction recovery. You cannot display locks held by online catchup or offline catchup.


Chapter 12: Recovery Manager UtilityQUIT

QUIT

Function

The QUIT command exits Recovery Manager.

Syntax

Usage Notes

You can only type this command when Recovery Manager is prompting for a command.

You cannot abort a Recovery Manager command in progress.

QUIT

GT11A004

;


Chapter 12: Recovery Manager UtilityREBUILD/RECOVERY PRIORITY

REBUILD/RECOVERY PRIORITY

Function

The REBUILD/RECOVERY PRIORITY command sets or displays a priority level for use by the Table Rebuild utility and a system recovery operation.

Syntax

Usage Notes

Setting a priority will apply to future and currently running operations. The PRIORITY command takes the following forms.

Both priorities are independent of each other and can hold different values at any period of time. That is, recovery initiated rebuilds will use recovery priority and not rebuild priority. If you type the command without specifying high, medium, or low, the current priority setting is displayed.

The REBUILD PRIORITY command applies to any Table Rebuild started from the console, automatic table rebuild due to disk error recovery, and MLOAD rebuild of target tables for non-participant online AMPs.

The REBUILD PRIORITY command sets a priority for the rebuild utility. You can select HIGH, MEDIUM, or LOW level priority. If you do not explicitly set a priority, default rates exist and will be used. If you do not type a new priority, the current priority setting is displayed.

The RECOVERY PRIORITY command sets a priority for the system recovery operation. You can select HIGH, MEDIUM, OR LOW level priority. If you do not explicitly set a priority, the current priority setting is displayed. The priority settings are saved in the Recovery Status system table.

REBUILD

RECOVERY

GT11A005

;PRIORITY

HIGHMEDIUMLOW


Chapter 13:


Resource Check Tools (RCT) is a utility that is designed to assist in the following:

• Identifying a slow down or hang of the Teradata RDBMS• Providing system statistics to help you determine the cause of the slow

down or hang

The RCT consists of several components, as shown in the following table.

Audience

Users of RCT include the following:

• Field engineers• System administrators• Teradata Support Center (TSC) personnel

Component Description

dbschk A standalone tool that checks to see if the RDBMS is hung or congested.

nodecheck A standalone tool that displays local, node-level resources only. Provides summary data to syscheck for analysis or provides detailed output to the nodecheck log file, which is used later for analysis when called from syscheck.

syscheck A standalone tool that analyzes relevant system data from the local node.

syscheckrc A file containing user-defined parameters that syscheck and nodecheck employ as criteria to determine when certain statistics of the system have reached alert or warning levels.


Chapter 13: Resource Check Toolsdbschk

dbschk

Function

dbschk identifies a slowdown or hang of the Teradata RDBMS.

Syntax

where:

Syntax element … Description

-b Runs in daemon mode continuously if the PDE and RDBMS are up.

-debug debug-level Activates debug audit and tracing.

You can set debug to one of the following:

Value Description

0 Debugging is off. (Default)

1 Display debugging messages only.

2 Stop the program at certain checkpoints.

You might want to stop the debugger for the following reasons:

• To attach the debugger• To validate process flow• To slow down the execution

Note: The debug value is not recorded in the GDO. You cannot change the debug value while dbschk is running.

dbschk

FF07E400

-b

-debug debug-level

-h

-l

-log logfile

-number of iterations

-logflush logflush

-delay success-delay

-power

-rate frequency

-timeout time



-delay success-delay Sets the time in seconds that dbschk waits between successful execution of the all-AMP requests against the RDBMS.

Default is 300 seconds.

The minimum input is zero. The maximum input is the largest discrete value or integer allowed on the machine.

-h Displays usage information as well as a short description of the utility.

-l Prints the current settings that the running dbscheck is using or will use.

The following settings are printed:

• Delay• Logflush• Power• Rate• Timeout

-log logfile Specifies a user-defined filename that contains the log information from both dbschk and any tool you run against dbschk during a batch run.

If you do not specify a log filename, the default log filename is used. The default is the temporary PDE directory as set by PDEPATH. However, if this directory is undefined, then the /TMP directory is used for NCR UNIX MP-RAS, and the C:\TEMP directory is used for Microsoft Windows 2000.

Note: The log filename is not recorded in the control GDO. You cannot change this while dbschk is running.

-logflush logflush Sets the time in seconds after which the log file is overwritten with new log information.



number of iterations Specifies the number of times dbschk runs.

-power Turns dbschk on or off at any time.

For example, you could use this option to shut down all running instances of dbschk gracefully without any consequences to the RDBMS.

You can set power to one of the following:




Usage Notes

Normally, you run dbschk in batch mode during PDE startup. However, you can run dbschk interactively.

The following are interactive examples, which do not leave any information in the log file:

• If run without any parameters, dbschk queries the RDBMS and reports its response.

• If run with only a numeric value as the only parameter, dbschk queries the RDBMS for the fixed number of times as specified by the numeric value.

By default, when the PDE reaches the TPA/TPA ready state, dbschk is started to run on the control node. You can run multiple instances of dbschk

-power (cont) Value Description

0 Power is off.

This is the default.

Note: dbschk will not start after a tpareset.

1 Power is on.

Note: When NCR first ships you any version of PDE with dbschk, the flag in the control GDO for power is set to off. You must turn the power to on to start dbschk for the first time.

To turn the power on, type the following:

dbschk -power 1

-rate frequency Sets the number of times that dbschk executes the all-AMP requests before generating a logevent.

Default is 5.


-timeout time Sets the time interval that dbschk waits for a response from an all-AMP request to the RDBMS.

The new value is written to the control GDO when dbschk executes the next all-AMP request.






simultaneously. However, unless each instance is run with its own log file, all log information from each instance is appended to the same default log file.

The dbschk run-time parameters are recorded in the PDE control GDO. You can change any of the parameters, except for debug, while dbschk is running.

dbschk runs until you either kill it or issue a tpareset.

Example 1

The following is an example of running dbschk in ping mode without any iterations.

dbschk

****************** dbschk started on Tue May 15 09:53:51 2001

fdlcsp: Searching for dumps in Teradata database Crashdumps on the local systemfdlcsp: No dumps found, no dumps to processdbschk: Sample Query finished normally, response time=9 seconds

(dbschk) Press <CTRL-C> to stop...

dbschk: sleep 5 seconds before restart.

Example 2

The following is an example of running dbschk in ping mode with three iterations.

dbschk 3

****************** dbschk started on Tue May 15 09:55:04 2001

fdlcsp: Searching for dumps in Teradata database Crashdumps on the local systemfdlcsp: No dumps found, no dumps to processdbschk: Sample Query finished normally, response time=3 seconds,






Chapter 13: Resource Check Toolsnodecheck

nodecheck

Function

nodecheck is a command-line diagnostic tool that finds node-level resource values on the local node. nodecheck provides summary data by node to syscheck for analyses or provides detailed output to the nodecheck log file, which is used later for analysis by syscheck.

Syntax

where:


-D Displays threshold values for -nodeonly and -timercontrol tunables in syscheckrc format.

Use this option to redirect the output to quickly create a syscheckrc file that you can customize. Then use the -r rscfile option to read from that customized syscheckrc file.

-f log Overrides the default log file location as specified in the -L option.

The -f option must be used with the -L option.

The directory path must previously exist. If you specify a file, that file is written. If you specify a directory, then the default filename specified in the -L option is written to that directory.

-h Provides basic help on command line options.

-I Lists threshold values for -nodeonly and -timercontrol tunables.

nodecheck

FF07D399

-f log

-D

-h

-L

-t n

-v

log

-I

-r rscfile



Usage Notes

If you invoke nodecheck without any options, then nodecheck does the following:

• Displays the current resource values on the local node• Evaluates the resource values• Notifies you of resources which have reached WARN or ALERT levels

The defined node-level resource names and values are located in the -nodeonly section of the syscheckrc configuration file. The syscheckrc file is read and processed at the following locations:

-L Logs the output to a file in the /tpi-data directory on the node where nodecheck is run.

The default log filename is nodecheck with an extension indicating the TPA cyclecount at the time of the run (for example, nodecheck.2).

You can specify a specific log filename or location using the -f log option. Additional tools are executed during logging mode, but their output is sent only to the resulting file.

-r rscfile Specifies an additional syscheckrc file to be read and processed that will override the values processed in the default syscheckrc file. For information on the syscheckrc file, see “The Default syscheckrc File” on page 13-30.

-t Directs nodecheck to read node-level resource data from one of the following previously created log files.

IF the value is … THEN nodecheck reads data from …

n the /tpi-data/nodecheck.n file, where n indicates the TPA cyclecount at the time of the run.

log a user-defined path or filename that contains the log information.

-v Displays the current resource values on the local node, evaluates the resource values, and notifies you of the status of all tunable resources, regardless of level.




Note: When executed through syscheck, nodecheck will only read and process the default and optional syscheckrc files on the node in which nodecheck is executed. This means that changes to the -timercontrol section must be propagated to all nodes in order for nodecheck to execute in the same manner on each node (when executed through syscheck).For information on the -timercontrol section, see “Timercontrol Section” on page 13-32. For more information on the syscheckrc file, see “The Default syscheckrc File” on page 13-30.

Creating a Log File

To run a single instance of nodecheck, creating a log file for later analysis, do the following:

On … syscheckrc is stored in the …

UNIX MP-RAS • /usr/ntos/etc directory (default). • /ntos directory (optional).

Note: The second path is only processed when it exists. You can use the -r rscfile option to have your custom syscheckrc configuration file read and processed. The values in each subsequently processed file override any values defined in the default syscheckrc file.

The configuration file also specifies the PDE tools that are used to extract the values of the node-level resources.

Caution: NCR does not recommend you modify the values for the PDE tools (under the -testdriver section), since this might cause program failure or unexpected results. The -testdriver section in the second path (Teradata Configuration directory) is ignored but processed at the first path and in a user-specified syscheckrc file. For more information on the -testdriver section of the syscheckrc file, see “Testdriver Section” on page 13-31.

Windows 2000 • Program Files\NCR\TDAT\LPDE\etc directory (default).• Program Files\NCR\TDAT\tdConfig directory (optional).

Step Action

1 Type the following:

nodecheck -L -f log

where log is the eventual location (a user-defined path or filename) that contains the log information. nodecheck will still print and evaluate the current resources.



Example 1 - NCR UNIX MP-RAS

The following is an example of running nodecheck with no options.

nodecheck

Reading Node Resources... please wait...

FreeMemory(Pages) and FreeSwap(Blocks)/usr/sbin/sar -r 2 5FREEMEM 46152FREESWAP 317492

Inuse Vproc Pages/usr/ntos/bin/puma -pCount Vproc6 1638429 029 129 229 329 429 529 629 729 829 911 1638011 1638111 1638211 16383

Available AMP Worker Tasks/usr/ntos/bin/puma -cCount Vproc39 040 140 240 340 440 540 640 740 840 9



BNS reject% for different Message types /usr/ntos/bin/tdnstat -a 5 2 SBR_FCount% Message Type 0 RXGRPSEG 0 RXP2PSEG 0 RXGRPREC 0 RXP2PREC SegTblFull% Message Type 0 RXGRPSEG 0 RXP2PSEG

PDE Msg Daemon Queue length /usr/ntos/bin/puma -D msgevcount/d MSGEVCOUNT 0

BNS Block Queue /usr/ntos/bin/puma -D *BSCp/3d BNSBLKQ 0

Evaluating results... please wait...

No tunables show status of WARN or ALERT

Example 2 - Windows 2000

nodecheck


FreeMemory(Pages) and FreeSwap(Blocks)e:\PROGRA~1\ncr\tdat\LPDE\BIN/sar.exe -r 1 1FREEMEM 1185FREESWAP 620128

PDE Msg Daemon Queue lengthe:\PROGRA~1\ncr\tdat\LPDE\BIN/pdeglobal.exe msg -knodeMSGEVCOUNT 0

BNS Block Queuee:\PROGRA~1\ncr\tdat\LPDE\BIN/puma.exe -D BlockStats/dBNSBLKQ 0

Available AMP Worker Taskse:\PROGRA~1\ncr\tdat\LPDE\BIN/puma.exe -cCount Vproc55 056 1



BNS reject% for different Message typese:\PROGRA~1\ncr\tdat\LPDE\BIN/tdnstat.exe -a 1 1SBR_FCount% Message Type0 RXGRPREC0 RXGRPSEG0 RXP2PREC0 RXP2PSEGSegTblFull% Message Type0 RXGRPSEG0 RXP2PSEG



Example 3 - UNIX MP-RAS

The following is an example of running syscheck with the -D option to display -nodeonly and -timercontrol tunables in syscheckrc format.

nodecheck -D

-nodeonly

AMPWT WARN -0 ALERT -0BNSBLKQ WARN 500 ALERT 100FREEMEM WARN -1000 ALERT -500FREESWAP WARN -2000 ALERT -1000MSGEVCOUNT WARN 100 ALERT 300RXMSGFC WARN 90 ALERT 100SEGTBLFULL WARN 80 ALERT 100VPRPAGES WARN -2 ALERT -0

-timercontrol

SARSAMPLE 5SARSLEEP 2TDNSTATSAMPLE 2TDNSTATSLEEP 5




nodecheck -D

-nodeonly

AMPWT WARN -0 ALERT -0BNSBLKQ WARN 500 ALERT 100FREEMEM WARN -1000 ALERT -500FREESWAP WARN -2000 ALERT -1000MSGEVCOUNT WARN 100 ALERT 300RXMSGFC WARN 90 ALERT 100SEGTBLFULL WARN 80 ALERT 100

-timercontrol



The following is an example of running syscheck with the -I option to display -nodeonly and -timercontrol tunables.

nodecheck -I

Tunable WARN ALERT

AMPWT <=0 <=0BNSBLKQ >=500 >=100FREEMEM <=1000 <=500FREESWAP <=2000 <=1000MSGEVCOUNT >=100 >=300RXMSGFC >=90 >=100SEGTBLFULL >=80 >=100VPRPAGES <=2 <=0

Tunable Value





nodecheck -I

Tunable WARN ALERT

AMPWT <=0 <=0BNSBLKQ >=500 >=100FREEMEM <=1000 <=500FREESWAP <=2000 <=1000MSGEVCOUNT >=100 >=300RXMSGFC >=90 >=100SEGTBLFULL >=80 >=100

Tunable Value



The following is an example of running nodecheck with the -L option.

nodecheck -LWriting to log file: /tpi-data/nodecheck.969Reading Node Resources... please wait...


Inuse Vproc Pages/usr/ntos/bin/puma -pCount Vproc6 1638429 029 129 229 329 429 529 629 729 829 911 1638011 1638111 1638211 16383




BNS reject% for different Message types/usr/ntos/bin/tdnstat -a 5 2SBR_FCount% Message Type0 RXGRPSEG0 RXP2PSEG0 RXGRPREC0 RXP2PRECSegTblFull% Message Type0 RXGRPSEG0 RXP2PSEG

PDE Msg Daemon Queue length/usr/ntos/bin/puma -D msgevcount/dMSGEVCOUNT 0

BNS Block Queue/usr/ntos/bin/puma -D *BSCp/3dBNSBLKQ 0




nodecheck -L

Writing to log file: e:\PROGRA~1\ncr\tdat\tdconfig\tmp\tpi-data\nodecheck.22










Resource Current Current Threshold Vproc Number/Description Level Value Value Message TypeFreeMemory(Pages) WARN 975 <=1000


The following is an example of running nodecheck with the -v option.

nodecheck -vReading Node Resources... please wait...


Inuse Vproc Pages/usr/ntos/bin/puma -pCount Vproc6 1638429 029 129 229 329 4



29 529 629 729 829 911 1638011 1638111 1638211 16383






Resource Current Current Threshold Vproc NumberDescription Level Value Value Message Type

FreeMemory(Pages) OK 46151FreeSwap(Blocks) OK 317506Available Vproc Pages OK 6 16384Available Vproc Pages OK 29 0Available Vproc Pages OK 29 1Available Vproc Pages OK 29 2



Available Vproc Pages OK 29 3Available Vproc Pages OK 29 4Available Vproc Pages OK 29 5Available Vproc Pages OK 29 6Available Vproc Pages OK 29 7Available Vproc Pages OK 29 8Available Vproc Pages OK 29 9Available Vproc Pages OK 11 16380Available Vproc Pages OK 11 16381Available Vproc Pages OK 11 16382Available Vproc Pages OK 11 16383Available AMP Worker Tasks OK 39 0Available AMP Worker Tasks OK 40 1Available AMP Worker Tasks OK 40 2Available AMP Worker Tasks OK 40 3Available AMP Worker Tasks OK 40 4Available AMP Worker Tasks OK 40 5Available AMP Worker Tasks OK 40 6Available AMP Worker Tasks OK 40 7Available AMP Worker Tasks OK 40 8Available AMP Worker Tasks OK 40 9BNS Msg Reject%(FC) OK 0 RXGRPSEGBNS Msg Reject%(FC) OK 0 RXP2PSEGBNS Msg Reject%(FC) OK 0 RXGRPRECBNS Msg Reject%(FC) OK 0 RXP2PRECBNS Msg Reject%(SEGTBLFULL) OK 0 RXGRPSEGBNS Msg Reject%(SEGTBLFULL) OK 0 RXP2PSEGPDE Msg Daemon Queue Length OK 0BNS Block Queue Length OK 0


>nodecheck -vReading Node Resources... please wait...









Resource Current Current Threshold Vproc Number/Description Level Value Value Message Type

FreeMemory(Pages) OK 1192FreeSwap(Blocks) OK 620128PDE Msg Daemon Queue Length OK 0BNS Block Queue Length OK 0Available AMP Worker Tasks OK 55 0Available AMP Worker Tasks OK 56 1BNS Msg Reject%(FC) OK 0 RXGRPRECBNS Msg Reject%(FC) OK 0 RXGRPSEGBNS Msg Reject%(FC) OK 0 RXP2PRECBNS Msg Reject%(FC) OK 0 RXP2PSEGBNS Msg Reject%(SEGTBLFULL) OK 0 RXGRPSEGBNS Msg Reject%(SEGTBLFULL) OK 0 RXP2PSEG


The following is an example of running nodecheck with the -v option and reading output from a previously generated log file. The TPA cyclecount is specified to gain access to the recently created default log file.

nodecheck -t 969 -vReading from log file: /tpi-data/nodecheck.969


Inuse Vproc Pages/usr/ntos/bin/puma -pCount Vproc6 1638429 029 129 229 329 429 529 6



29 729 829 911 1638011 1638111 1638211 16383






Resource Current Current Threshold Vproc NumberDescription Level Value Value Message TypeFreeMemory(Pages) OK 46146FreeSwap(Blocks) OK 317510Available Vproc Pages OK 6 16384Available Vproc Pages OK 29 0Available Vproc Pages OK 29 1Available Vproc Pages OK 29 2Available Vproc Pages OK 29 3Available Vproc Pages OK 29 4Available Vproc Pages OK 29 5



Available Vproc Pages OK 29 6Available Vproc Pages OK 29 7Available Vproc Pages OK 29 8Available Vproc Pages OK 29 9Available Vproc Pages OK 11 16380Available Vproc Pages OK 11 16381Available Vproc Pages OK 11 16382Available Vproc Pages OK 11 16383Available AMP Worker Tasks OK 39 0Available AMP Worker Tasks OK 40 1Available AMP Worker Tasks OK 40 2Available AMP Worker Tasks OK 40 3Available AMP Worker Tasks OK 40 4Available AMP Worker Tasks OK 40 5Available AMP Worker Tasks OK 40 6Available AMP Worker Tasks OK 40 7Available AMP Worker Tasks OK 40 8Available AMP Worker Tasks OK 40 9BNS Msg Reject%(FC) OK 0 RXGRPSEGBNS Msg Reject%(FC) OK 0 RXP2PSEGBNS Msg Reject%(FC) OK 0 RXGRPRECBNS Msg Reject%(FC) OK 0 RXP2PRECBNS Msg Reject%(SEGTBLFULL) OK 0 RXGRPSEGBNS Msg Reject%(SEGTBLFULL) OK 0 RXP2PSEGPDE Msg Daemon Queue Length OK 0BNS Block Queue Length OK 0


The following is an example of running nodecheck with the -L and -f options and writing output to a log file.

nodecheck -L -f mylog

Writing to log file: mylog












The following is an example of running nodecheck with the -t option and reading input from a previously generated log file.

nodecheck -t mylog

Reading from log file: mylog










Messages

nodecheck displays the following types of messages.

The message … Displays if …

Error nodecheck encounters any error to extract the resource value.

An Error message could occur if nodecheck cannot find or execute the related PDE tool to extract the resource value. If STDERR output exists, it displays.

Warning invalid information is found during processing of the syscheckrc file or for other reasons.


Chapter 13: Resource Check Toolssyscheck

syscheck

Function

syscheck monitors the system for signs of congestion that might lead to system slowdowns or perceived hangs and notifies you when Warning or Alert thresholds are reached.

Syntax

where:


-D Displays threshold values for -nodeonly and -timercontrol tunables in syscheckrc format.

Use this option to redirect the output to quickly create a syscheckrc file that you can customize. Then use the -r rscfile option to read from that customized syscheckrc file.

Note: syscheck will not take into account the -timercontrol section of the custom syscheckrc file you indicate with the -r rscfile option. Since syscheck executes nodecheck locally as well as on each remote node, modifications to the default and optional syscheckrc file on the local node will be considered for that local spawn of nodecheck. That is, where syscheck is concerned, -timercontrol changes are local, and nodeonly changes are global. Where nodecheck is concerned, all changes take effect locally.

For more information, see “Timercontrol Section” on page 13-32 and “Nodeonly Section” on page 13-31.

-h Provides basic help on command line options.

-I Lists threshold values for -nodeonly and -timercontrol tunables.

syscheck

FF07D398

-D

-h

-L

-t n

-v

-I

-r rscfile

-n nl



-L Logs the output to a file in the /tpi-data directory on each node where nodecheck is run.

The default log filename is nodecheck with an extension indicating the TPA cyclecount at the time of the run (for example, nodecheck.2).

You can specify a specific log filename or location using the -f log option. Additional tools are executed during logging mode, but their output is sent only to the resulting file. For more information, see “nodecheck” on page 13-6.

-n nl Specifies the list of nodes on which nodecheck is invoked.

By default, nodecheck is invoked on all live TPA nodes.

Note: Separate the nodes in the list by commas.

-r rscfile Specifies an additional syscheckrc file to be read and processed that will override the values processed in the default syscheckrc file.

Note: syscheck will not take into account the -timercontrol section of the custom syscheckrc file you indicate with the -r rscfile option. Since syscheck executes nodecheck locally as well as on each remote node, modifications to the default and optional syscheckrc file on the local node will be considered for that local spawn of nodecheck. That is, where syscheck is concerned, -timercontrol changes are local, and nodeonly changes are global. Where nodecheck is concerned, all changes take effect locally.

For more information, see “The Default syscheckrc File” on page 13-30.

-t n Directs nodecheck to read node-level resource data from a previously created log file (with a default name) on each node.

nodecheck reads the data from the /tpi-data/nodecheck.n file, where n indicates the TPA cyclecount at the time of the run.

-v Displays all the resource values for each node, evaluates the resource values, and notifies you of the status of all tunable resources, regardless of level.




Usage Notes

syscheck does not automatically reset the system when any threshold is reached. The DBA or operator decides when to reset the system if the congestion persists.

syscheck is a system-wide tool (as compared to nodecheck, which is node-only tool) and does the following in this order:

syscheck also checks the Teradata PDE and RDBMS states on the node on which you execute syscheck, informing you if either is not in a fully functional state.

You can use a custom-formatted syscheckrc file by specifying the -r rscfile option. The values in this file will override the values specified in the default syscheckrc file. For more information, see “The Default syscheckrc File” on page 13-30.

IF you invoke syscheck … THEN syscheck …

without any options • spawns an instance of nodecheck on all live TPA nodes.• compares the nodecheck results from each node against

threshold values indicated in the local syscheckrc file or files, which are located on the machine where you run syscheck.

• displays the current resource values on the local node.• evaluates the resource values.• notifies you of resources which have reached WARN or

ALERT levels.

with the -v option • spawns an instance of nodecheck on all live TPA nodes.• compares the nodecheck results from each node against

threshold values indicated in the local syscheckrc file or files, which are located on the machine where you run syscheck.

• displays the current resource values on the local node.• evaluates the resource values.• notifies you of the status of all tunable resources,

regardless of level.



The defined node-level resource names and values are located in the -nodeonly section of the syscheckrc configuration file. The syscheckrc file is read and processed at the following locations:

Example 1 - UNIX MP-RAS and Windows 2000

The following is an example of running syscheck with no options.

syscheck

Processing resource values for WARN/ALERT status... please wait...

NODE ID: localhost


FreeMemory(Pages) WARN 992 <=1000

On … syscheckrc is stored in the …

UNIX MP-RAS • /usr/ntos/etc directory (default).• /ntos directory (optional).

Note: The second path is only processed when it exists. You can use the -r rscfile option to have your custom syscheckrc configuration file read and processed. The values in each subsequently processed file override any values defined in the default syscheckrc file.

The configuration file also specifies the PDE tools that are used to extract the values of the node-level resources.

Caution: NCR does not recommend you modify the values for the PDE tools (under the -testdriver section), since this might cause program failure or unexpected results. The -testdriver section in the second path (Teradata Configuration directory) is ignored but processed at the first path and in a user-specified syscheckrc file. For more information on the -testdriver section of the syscheckrc file, see “Testdriver Section” on page 13-31.

Windows 2000 • Program Files\NCR\TDAT\LPDE\etc (default).• Program Files\NCR\TDAT\tdConfig (optional).




The following is an example of running syscheck with the -D option to display -nodeonly and -timercontrol tunables in syscheckrc format.

syscheck -D

-nodeonly


-timercontrol



The following is an example of running syscheck with the -I option to display -nodeonly and -timercontrol tunables.

Note: In Windows 2000 output, the Tunable VPRPAGES will not appear.

syscheck -I

Tunable WARN ALERT

AMPWT <=0 <=0BNSBLKQ >=500 >=100FREEMEM <=1000 <=500FREESWAP <=2000 <=1000MSGEVCOUNT >=100 >=300RXMSGFC >=90 >=100SEGTBLFULL >=80 >=100VPRPAGES <=2 <=0

Tunable Value





The following is an example of running syscheck with the -L option.

syscheck -L

Processing resource values for WARN/ALERT status... please wait...

NODE ID: localhost



The following is an example of running syscheck with the -v option.

syscheck -v

Processing resource values for any status... please wait...

NODE ID: localhost


FreeMemory(Pages) OK 1166FreeSwap(Blocks) OK 1013880Available Vproc Pages OK 6820 16384Available Vproc Pages OK 6820 0Available Vproc Pages OK 6820 1Available Vproc Pages OK 6820 16383Available Vproc Pages OK 6820 8192Available AMP Worker Tasks OK 39 0Available AMP Worker Tasks OK 40 1BNS Msg Reject%(FC) OK 0 RXGRPSEGBNS Msg Reject%(FC) OK 0 RXP2PSEGBNS Msg Reject%(FC) OK 0 RXGRPRECBNS Msg Reject%(FC) OK 0 RXP2PRECBNS Msg Reject%(SEGTBLFULL) OK 0 RXGRPSEGBNS Msg Reject%(SEGTBLFULL) OK 0 RXP2PSEGPDE Msg Daemon Queue Length OK 0BNS Block Queue Length OK 0

Example 6 - Windows 2000syscheck -v

Processing resource values for any status... please wait...

NODE ID: localhost


FreeMemory(Pages) OK 3158FreeSwap(Blocks) OK 620128



PDE Msg Daemon Queue Length OK 0BNS Block Queue Length OK 0Available AMP Worker Tasks OK 55 0Available AMP Worker Tasks OK 56 1BNS Msg Reject%(FC) OK 0 RXGRPRECBNS Msg Reject%(FC) OK 0 RXGRPSEGBNS Msg Reject%(FC) OK 0 RXP2PRECBNS Msg Reject%(FC) OK 0 RXP2PSEGBNS Msg Reject%(SEGTBLFULL) OK 0 RXGRPSEGBNS Msg Reject%(SEGTBLFULL) OK 0 RXP2PSEG


The following is an example of running nodecheck to read output from a logfile that was just created. The TPA cyclecount is specified to gain access to the recently created default logfile.

syscheck -t 24

Logfile to be processed: /tpi-data/nodecheck.24Processing resource values for WARN/ALERT status... please wait...

NODE ID: localhost



syscheck -t 22 -v

Logfile to be processed: e:\PROGRA~1\ncr\tdat\tdconfig\tmp\tpi-data\nodecheck.22Processing resource values for any status... please wait...

NODE ID: localhost


FreeMemory(Pages) OK 3207FreeSwap(Blocks) OK 620128PDE Msg Daemon Queue Length OK 0BNS Block Queue Length OK 0Available AMP Worker Tasks OK 55 0Available AMP Worker Tasks OK 56 1BNS Msg Reject%(FC) OK 0 RXGRPRECBNS Msg Reject%(FC) OK 0 RXGRPSEGBNS Msg Reject%(FC) OK 0 RXP2PRECBNS Msg Reject%(FC) OK 0 RXP2PSEGBNS Msg Reject%(SEGTBLFULL) OK 0 RXGRPSEGBNS Msg Reject%(SEGTBLFULL) OK 0 RXP2PSEG


Chapter 13: Resource Check ToolsThe Default syscheckrc File

The Default syscheckrc File

syscheckrc is an editable text file that contains system, kernel, and Teradata RDBMS-specific parameters. When parameters are exceeded, your system might be reaching its resource constraints. You can expect certain performance problems if this occurs.

Although not mandatory, all copies of syscheckrc should be identical on all nodes. However, each copy of syscheckrc must correspond to the specific node on which syscheckrc resides.

Caution: Do NOT modify the default syscheckrc file. To create an optional syscheckrc file, see “Default syscheckrc File Example” on page 13-30.

The default syscheckrc file is read and processed at the following locations.

Default syscheckrc File Example

syscheck reads and parses the resource files at startup. Resource files have a line-oriented syntax:

• A line starting with a # is a comment. • A line containing only comments or white space (spaces or tabs) is ignored. • Each line can have a single resource entry that has name and value strings

separated by white space.

The following is an example of the default syscheckrc file.

#-testdriver:

## This section is provided as a tool for GSC to provide test input## to syscheck and nodecheck. This section is not meant for## modification by the customer. NOTE: Modification of this## section can yield unexpected errors or results. To override a## tool that is used in nodecheck or syscheck, uncomment the## appropriate line and provide a different path or executable for## the tool.

# SAR %PDE_BIN\sar.exe# PUMA %PDE_BIN\puma.exe# TDNSTAT %PDE_BIN\tdnstat.exe# BLMSTAT blmstat.exe

On … The default syscheckrc file is located in the …

UNIX MP-RAS /usr/ntos/etc directory.

Windows 2000 Program Files\NCR\TDAT\LPDE\etc directory.



# VPROCMANAGER %PDE_BIN\vprocmanager.exe# PDESTATE %PDE_BIN\pdestate.exe# PCL %PDE_BIN\pcl.exe# MPPLIST %PDE_CFG\mpplist# NETECHO %PDE_BIN\tdinfo.exe# NODECHECK %PDE_BIN\nodecheck.bat# CONTROLGDO %PDE_BIN\controlgdo.exe# PDEGLOBAL %PDE_BIN\pdeglobal.exe

-nodeonly: This section defines node-only parameters


-timercontrol

# used to override behavior of sar and tdnstat in nodecheck# i.e. sar.exe -r SARSLEEP SARSAMPLE# values need to be integers >= 1

SARSLEEP 2SARSAMPLE 5TDNSTATSLEEP 5TDNSTATSAMPLE 2

Testdriver Section

The -testdriver section maps to the executables of each node and is different, depending on the platform.

Caution: Do NOT modify the -testdriver section. If you modify the -testdriver section, nodecheck and syscheck might fail.

Nodeonly Section

The -nodeonly section allows you to define the WARN and ALERT threshold levels for each system resource. If the threshold value is negative, then the condition (either WARN or ALERT) will be triggered when that system resource attribute falls below that value. Otherwise, the condition is triggered when the attribute rises above that value.

The default syscheckrc file contains default values. You can redefine the warning and alert values only in the optional syscheckrc file and in a custom syscheckrc file (using the -r rscfile option). The following table describes each system resource attribute.



Timercontrol Section

The -timercontrol section allows you to adjust the sample number and sleep time. Currently, only two tools use these parameters:

• System Activity Reporter (SAR)• TDNSTAT utility

The value must be an integer greater than or equal to one.

For the -timercontrol section to work on all nodes, you must provide a modified optional syscheckrc file on each node.

System Resource Attribute Description

AMPWT WARN XXX ALERT XXX Warning and alert threshold level for available (or running out) of AMP work tasks (AWTs).

BNSBLKQ WARN XXX ALERT XXX Warning and alert threshold level for BNS services in BNS block queue.

FREEMEM WARN XXX ALERT XXX Warning and alert threshold levels for freemem pages.

FREESWAP WARN XXX ALERT XXX Warning and alert threshold levels for freeswap blocks.

MSGEVCOUNT WARN XXX ALERT XXX Warning and alert threshold levels for message count in PDE message event queue.

RXMSGFC WARN XXX ALERT XXX Warning and alert threshold for percentage of message count being flow controlled at the receiver side.

VPRPAGES WARN XXX ALERT XXX Warning and alert threshold level for available pages in virtual address of the PDE vproc. (UNIX MP-RAS only)

SEGTBLFULL WARN XXX ALERT XXX Warning and alert threshold for percentage occupation of multi-segment table entries. 100% indicates that the multi-packet messages are naked or all the multi-packet segment table slots are currently occupied.


Chapter 13: Resource Check ToolsCreating an Optional syscheckrc File

Creating an Optional syscheckrc File

An optional (or modified) syscheckrc file provides a permanent way to override the default syscheckrc file resource settings. NCR recommends that you use a naming convention for resources, such as an uppercase name.

To create an optional syscheckrc file, do the following:

Modified syscheckrc File Example

The following is an example of a modified syscheckrc file on UNIX MP-RAS. On Windows 2000, VPRPAGES would not appear.

nodecheck -D

-nodeonly


-timercontrol


Step Action

1 Do one of the following:

• Copy the default syscheckrc file to one of the optional locations below and modify the copied file:

On … The optional resource file is located in the …

UNIX MP-RAS /ntos directory.

Windows 2000 Program Files\NCR\TDAT\tdConfig directory.

• Create a new syscheckrc file in one of the optional locations above by running nodecheck or syscheck with the -D option.


Chapter 13: Resource Check ToolsCreating an Optional syscheckrc File


Chapter 14:

RSSmon Utility (NCR UNIX MP-RAS Only)

The RSSmon utility provides Parallel Database Extensions (PDE) real-time resource usage per node. Because the Resource Sampling Subsystem (RSS) collects a wide-range of resource usage data, RSSmon allows the selection of relevant data fields from a specific RSS table to be examined for PDE resource usage monitoring purposes.

The following applies to the statistical data displayed by RSSmon:

• Data is collected by the Resource Sampling Subsystem (RSS) of PDE.• Data currently is organized into seven logical tables. For more information

about the logical tables, see “The Monitoring Configuration File” on page 14-4.

Note: An additional table is reserved for future use.

For additional information about RSS, the logical tables and their usage, and the specific statistical data fields in each table, see Teradata RDBMS Resource Usage Macros and Tables.

Audience

Users of RSSmon include the following:

• Field engineers• System administrators• Database administrators


Chapter 14: RSSmon Utility (NCR UNIX MP-RAS Only)Starting and Exiting RSSmon

Starting and Exiting RSSmon

RSSmon is a terminal-mode program that requires a terminal or terminal-emulation window (for example, xterm). One useful technique is to execute the xterm command on the node of interest, directing the display to an appropriate X-capable workstation or terminal, and then running RSSmon from this window.

At every associated ResUsage collection interval, the statistical data display is refreshed with new statistics.

You can start RSSMon from the command line and exit RSSMon from the RSSMon window.

To start RSSMon, located in the /usr/ntos/bin directory, type the following:

rssmon

1102B001

-f config-file

-S output-file


Chapter 14: RSSmon Utility (NCR UNIX MP-RAS Only)Starting and Exiting RSSmon

where:

To exit RSSMon at the RSSMon window, type the following:

q


config-file a configuration file for PDE resource usage monitoring. You can use either a customized file or one of the following standard files supplied with RSSmon in /usr/ntos/bin:

• ipmadata.cfg• ivprdata.cfg• scpudata.cfg• shstdata.cfg• sldvdata.cfg• spmadata.cfg• svprdata.cfg

Note: If the configuration file is not in the current working directory when you execute the RSSmon command, then you must specify a correct full or relative path name with the -f flag.

output-file an output file to which RSSmon logs resource usage data. (If you do not specify the -S option, the default does not save to the output file.) A complete set of data, corresponding to the specified configuration file, is written to output-file at the end of each RSS collection interval (not the logging interval).

Without this option in the command, no record is saved.


Chapter 14: RSSmon Utility (NCR UNIX MP-RAS Only)The Monitoring Configuration File

The Monitoring Configuration File

To use RSSmon, you must specify a monitoring configuration file. The function of the configuration file is to define the layout and content of the RSSmon display. The file also defines the content of the output file, if you specified the -S flag when you started RSSmon.

The configuration file that you specify can be one of the following:

• One of the seven standard configuration files, provided with RSSmon utility

• A customized configuration file that you create


Chapter 14: RSSmon Utility (NCR UNIX MP-RAS Only)Standard Configuration Files

Standard Configuration Files

The seven standard configuration files supplied with RSSmon correspond to the seven logical ResUsage tables. Each file defines the layout as column format and selects as its content all of the fields that are available for its corresponding logical ResUsage table.

The following standard files are supplied with RSSmon:

• ipmadata.cfg• ivprdata.cfg• scpudata.cfg• shstdata.cfg• sldvdata.cfg• spmadata.cfg• svprdata.cfg


Chapter 14: RSSmon Utility (NCR UNIX MP-RAS Only)Customized Configuration Files

Customized Configuration Files

By creating and then specifying a customized configuration file, you can have RSSmon display a different layout and content rather than the ones provided in the standard configuration files. For example, you can select tabular rather than columnar format. You can select only those fields you are interested in rather than all available fields.

In addition, you can specify more than one ResUsage table. If you do this, only the first table will appear in the RSSmon display. But all of the selected fields from all of the specified tables will appear in the output file, if you specified one.

To create a customized configuration file, rename and modify one of the standard files by using any text editor (such as vi) and save the new file.


Chapter 14: RSSmon Utility (NCR UNIX MP-RAS Only)Customizing a Configuration File

Customizing a Configuration File

To customize a configuration file, do the following:

Step Action

1 Line 1 — Specify the output format (that is, the format you want to use for displaying ResUsage Data) by selecting one of the following:

• table — If you specify table, ResUsage data is displayed horizontally with one resource (that is, vproc, device, and so on) per row using the tabular format. For example, the table format allows you to see data for all vprocs at one time, as shown in the following display:

• list — If you specify list, ResUsage data is displayed vertically in columnar format. When one column is filled, data continues onto a second column. For example, the columnar format displays data for only one vproc at a time, as shown in the following display:

2 Line 2 — Leave this line blank.

vpr msgworkqlenavg dblockblocksavg dblocksheldavg cpuuservpart00 cpuuservpart

0 0 0.00 0.00 0.00 0.00

1 0 0.00 0.00 0.00 0.00

2 0 0.00 0.00 0.00 0.00

3 0 0.00 0.00 0.00 0.00

4 0 0.00 0.00 0.00 0.00

5 0 0.00 0.00 0.00 0.00

6 0 0.00 0.00 0.00 0.00

7 0 0.00 0.00 0.00 0.00

8 0 0.00 0.00 0.00 0.00

9 0 0.00 0.00 0.00 0.00

10 0 0.00 0.00 0.00 0.00

1023 0 0.00 0.00 0.00 0.00

1024 0 0.00 0.00 2.00 0.00

Press <cursor keys> to scroll.

--- PDE ResUsage --------------------------------------------------------

vpr 0 cpuuservpart09 0.00

msgworkqlenavg 1 cpuuservpart10 0.00

dblockblocksavg 0.00 cpuuservpart11 0.00

dblocksheldavg 0.00 cpuuservpart12 0.00

cpuuservpart00 0.00 cpuuservpart13 0.00









Press <cursor keys> to scroll.


Chapter 14: RSSmon Utility (NCR UNIX MP-RAS Only)Customizing a Configuration File

Example

An example of a customized monitoring configuration file follows:

table

svprdatamsgworkqlenavgcpuuservpart00cpuuservpart01cpuuservpart02cpuuservpart03

3 Line 3 — Specify the ResUsage table to be displayed using keywords as follows:

Keyword ResUsage Table Name

ipmadata ResUsageIpma

ivprdata ResUsageIvpr

scpudata ResUsageScpu

shstdata ResUsageShst

sldvdata ResUsageSldv

spmadata ResUsageSpma

svprdata ResUsageSvpr

Note: The remainder of the file lists the ResUsage fields from the corresponding table to be displayed.

4 Lines 4 through n — Specify the selected field names for the ResUsage table, in any order you choose.

Note: You must spell out the field names in lowercase letters.

5 Line n+1 — Leave a blank line between different table entries.

6 Lines n+2 — Specify the keyword for the next ResUsage table. You can specify multiple tables as long as they report ResUsage data for the same resource type.

Note: You must spell out the field names in lowercase letters.

Step Action


Chapter 14: RSSmon Utility (NCR UNIX MP-RAS Only)Displaying ResUsage Data

Displaying ResUsage Data

For information on table usage and a complete list of fields for each table, see Teradata RDBMS Resource Usage Macros and Tables.

The following table lists the keyboard cursor keys you can use to scroll through the resource usage statistics displays. You can use one of the alternatives listed if one of the following occurs:

• Your terminal is not defined properly.• The keyboard does not have a cursor keypad.• The cursor keys are not operational.

Cursor Key/Key Combinations Effect on the RSSmon Display

Left Arrow or

< (Shift+Comma)

Moves to the previous set of fields, if any, for the currently displayed resource

Right Arrow or > (Shift+Period)

Moves to the next set of fields, if any, for the currently displayed resource

Up Arrow or Comma (,)

Moves to the previous resource, if any. For example, the next CPU if displaying Scpu data or the next vproc if displaying Svpr data

Down Arrow or Period (.)

Moves to the next resource, if any. For example, the next CPU if displaying Scpu data or the next vproc if displaying Svpr data


Chapter 14: RSSmon Utility (NCR UNIX MP-RAS Only)Displaying ResUsage Data


Chapter 15:

Showlocks Utility

Showlocks provides information about Host Utility Locks (HUT) placed on databases and tables by the Archive/Recovery (ARC) utility during database operations.

These locks might interfere with application processing and should be released after utility processing is complete. Showlocks also displays information about locks placed during a system failure.

Audience

Users of Showlocks include the following:

• NCR operators• System programmers• System administrators• Database administrators


Chapter 15: Showlocks UtilityStarting and Exiting Showlocks on NCR UNIX MP-RAS

Starting and Exiting Showlocks on NCR UNIX MP-RAS


You can start and exit Showlocks from the following:



To start Showlocks, do the following:


To exit Showlocks, do the following:

Step Action




start showlocks

3 Press Enter.


Started ‘showlocks’ in window 1

The number represents the application window in which Showlocks is running. The Showlocks window appears.

Step Action

1 In the Enter a command subwindow of the Showlocks utility, type the following:

quit

2 Press Enter.


Showlocks terminated.




If you access Showlocks through the remote console, you cannot employ user IDs designating pooled sessions. Starting Showlocks from a remote console does not require a special privilege.


3 In the Showlocks window, select File -> Close.


Step Action


HUTCNS

You should see the initial Showlocks display, as shown below.





- Configuration

- LOCKsDisplay

- RCVmanager



3 To start Showlocks, type the following:

LOC

The initial Showlocks screen appears.

4 Enter responses to Showlocks prompts as you normally would type commands at your remote console.

Step Action




Step Action

1 At the remote console screen, type the following:

quit


Showlocks terminated.


Chapter 15: Showlocks UtilityStarting and Exiting Showlocks on Microsoft Windows 2000

Starting and Exiting Showlocks on Microsoft Windows 2000


You can start and exit Showlocks from the following:





Step Action






start showlocks

4 Press Enter.


Started ‘showlocks’ in window 1

The number represents the application window in which Showlocks is running. The Showlocks window appears.


Chapter 15: Showlocks UtilityStarting and Exiting Showlocks on Microsoft Windows 2000





Step Action

1 In the Enter a Command subwindow of the Showlocks, type the following:

quit

2 Press Enter.

3 In the Showlocks window, select File -> Close.


Step Action




The DBW appears.



start showlocks

5 Press Enter.


Started ‘showlocks’ in window 1.

The number represents the application window in which Showlocks is running. The tab that previously said Application 1 now says Showlocks and is the active window.

Step Action

1 In the DBW, select the Abort Host tab.


quit

3 Press Enter.



Chapter 15: Showlocks UtilityHost Utility Locks

Host Utility Locks

You can release HUT locks either by submitting a separate RELEASE LOCK SQL command, or by using the RELEASE LOCK option of the appropriate command. For example, ARCHIVE, ROLLBACK, RESTORE, BUILD, and ROLLFORWARD.

HUT locks placed by the Archive/Recovery utility or the ASF2 facility differ from locks placed by other operations or transactions.

HUT locks have the following characteristics:

• Archive/Recovery locks are associated with the currently logged-on user who entered the command, rather than with a batch job or transaction.

• Only the AMPs that are participating in the Archive/Recovery operation are locked.

• Archive/Recovery locks placed at one level of an object never conflict with a utility lock at another level that was placed on the same object for the same user.The locking modes and levels are applied as follows:– A Read lock is placed on an object being dumped. – Locks are placed at the cluster level during a CLUSTER dump.– If a table being dumped is defined for an after-image permanent journal

(and the appropriate option was selected on the DUMP command), a group Read lock is placed on the table rows.

– A Write lock is placed on all tables involved in ROLLFORWARD and ROLLBACKWARD recovery operations.

– A Write lock is placed on a journal table that is being deleted.– A Write lock is placed on a permanent journal table that is being

restored. – An Exclusive lock is placed on any object being restored that is not a

journal table.• Archive/Recovery locks remain active until you release them.

Note: If Archive/Recovery locks are not specifically released, they are automatically reinstated following a Teradata RDBMS or client system restart.


Chapter 15: Showlocks UtilityInterpreting the Showlocks Display

Interpreting the Showlocks Display

The Showlocks display provides this information:

• Summary of the showlocks function• Name of the databases and tables on which locks are placed• Username that placed each lock• Lock mode: read, write, exclusive, or access• Number of the AMPs on which the locked database or table resides

Showlocks reports All AMPs rather than individual AMP numbers when the locked database or table resides on all AMPs. Information is provided for only the most restrictive lock a user has placed on an object. An example of a complete Showlocks display is shown below:

In the previous example, exclusive locks are placed on the employee table in the personnel database and on the entire service database. One read lock is placed on the parts database, and another read lock on the invoice table in the accounting database. Also, the following locks are applied:

- Data Base Name- Table Name (if applicable)- User Name of user who placed lock- Lock Mode- AMP Number

accounting.invoice USER ADMIN MODE Read AMP All AMPs

parts USER PETERS MODE Read AMP 24

personnel.employee USER ACCMGR MODE Excl AMP 27

service USER DBC MODE Excel AMP 3

--ShowLocks Processing Complete--

which currently exist at both the data base level and the table level.

_______ | | | | ___ __ ____ | ____ __|__ ____ | / |/ \ ____| ____| ____| | ____| | --- | / | / | / | | / | | \___ | \____| \____| \____| |__ \____| Release V2R1.0 Version 5.0.2.5 Host Utility Lock Display

This program queries all AMPs and reports all Host Utility locks.

For each lock which is found, an entry will appear on your consolewhich includes the following information:



When no locks are found, Showlocks reports this message:

There are currently no host utility locks in the DBS.

Conflicts

If a host utility lock that conflicts with Showlocks is in place when Showlocks is executed, the system displays this message:

’Unable to proceed due to xxxx lock on yyyy’

where:

After reporting a conflict, Showlocks terminates.

Username … Placed the lock on the …

ADMIN invoice table that resides on all AMPs.

PETERS parts database which resides on AMP 24.

ACCMGR portion of the employee table that resides on AMP 27.

DBC portion of the service database that resides on AMP 3.

Syntax element … Is …

xxxx either a Write or Exclusive lock.

yyyy DBC, DBC.TVM, or DBC.DBase.


Chapter 16:

System Initializer Utility

The System Initializer (SYSINIT) utility does the following:

• Initializes the Teradata RDBMS• Creates or updates the DBS Control Record and other Globally Distributed

Objects (GDOs)• Initializes or updates configuration maps• Allows you to set the hash function value in the DBS Control Record

Audience

Users of System Initializer include the following:

• System engineers• Field engineers• System developers


Chapter 16: System Initializer UtilityStarting and Exiting SYSINIT on NCR UNIX MP-RAS

Starting and Exiting SYSINIT on NCR UNIX MP-RAS


You can start and exit SYSINIT from the Database Window.

To start SYSINIT, do the following:


SYSINIT completes after you respond to the last prompt in the user dialog. Also, you can terminate SYSINIT early by entering Quit in response to certain prompts. In either case, SYSINIT displays a message indicating that SYSINIT is complete or was terminated. For a description of these prompts and messages, see “Using System Initializer” on page 16-7.

To exit SYSINIT following SYSINIT completion or termination, do the following:

Step Action




start sysinit

3 Press Enter.


Started ‘sysinit’ in window 1.

The number represents the application window in which SYSINIT is running. The SYSINIT window appears.

Step Action

1 In the SYSINIT window, select File -> Close.



Chapter 16: System Initializer UtilityStarting and Exiting SYSINIT on Microsoft Windows 2000

Starting and Exiting SYSINIT on Microsoft Windows 2000


You can start and exit SYSINIT from the following:






Step Action






start sysinit

4 Press Enter.


Started ‘sysinit’ in window 1

The number represents the application window in which SYSINIT is running. The SYSINIT window appears.


Chapter 16: System Initializer UtilityStarting and Exiting SYSINIT on Microsoft Windows 2000






Step Action

1 In the SYSINIT window, select File -> Close.


Step Action




The DBW appears.



start sysinit

5 Press Enter.


Started ‘sysinit’ in window 1.

The number represents the application window in which SYSINIT is running. The tab that previously said Application 1 now says SYSINIT and is the active window.

Step Action



Chapter 16: System Initializer UtilityAbout System Initializer

About System Initializer

Initializing the Teradata RDBMS

Running SYSINIT is part of the overall RDBMS initialization process. SYSINIT handles system configuration differently, depending on the following:

• The Teradata RDBMS is being initialized for the first time• The Teradata RDBMS was initialized previously

Setting a New System

When used in a new system, SYSINIT initializes a configuration that includes all the vprocs defined in a vprocconfig GDO.

On a new, not previously initialized system (or on a corrupted system whose configuration map cannot be read), SYSINIT creates a full configuration based on the vprocconfig GDO. All the vprocs are set online. If a problem exists with any vproc, then a 0 PE, 1 AMP configuration is created. If a full configuration was created, then you are given options later for selecting a particular configuration for the new and old config maps.

Setting a Previously Initialized System

Warning: You must use SYSINIT with caution in a previously initialized system because SYSINIT will destroy all user and dictionary data currently in the system.

On a previously initialized system, SYSINIT retains the current configuration map and prompts you to do one of the following:

• Retain the current configuration in the new configuration map• Select a different configuration for the current and the new configuration

maps

On UNIX MP-RAS systems, SYSINIT might have to create a new configuration GDO based on the V2R3 configuration GMO. The system then issues a tpareset, and you need to restart SYSINIT. Once SYSINIT has a configuration map (GDO), you are asked to choose a configuration.

Globally Distributed Objects

GDOs are a fixed set of named objects that is kept consistent across all vprocs in a system. A GDO is shared by all vprocs and presents the same picture of its state to all of them.


Chapter 16: System Initializer UtilityAbout System Initializer

When you run SYSINIT, it initializes the following GDOs:

• BMHASHTBL• DBSCONTROL• HASHMAP• HASHMAPFB• ISF• MSCHASHINFO• PDECONTROL• VPROCCONFIG

SYSINIT initializes these GDOs automatically. Depending on the state of the DBS Control Record and the current configuration when SYSINIT is run, SYSINIT prompts you for certain information, such as the hash function and locale (Japanese support). For information on these prompts, see “Using System Initializer” on page 16-7.

Configuration Maps

Configuration maps define the current/new configuration of the RDBMS vprocs. A configuration map does the following:

• Stores the identification and status of each vproc in the RDBMS• Identifies the AMPs that constitute each AMP cluster• Identifies each PE and its associated host

The system contains two configuration maps, as follows:

• The current configuration map, which describes the current arrangement and status of vprocs in the system

• The new configuration map, which describes changes and additions to the configuration

SYSINIT can create a new configuration map and keep or revise a current map. For the new configuration maps initialized by SYSINIT from the current configuration, the current configuration can retain one AMP and all existing PEs. The new configuration can retain one or all AMPs and all existing PEs.

Configuration and Reconfiguration Utilities

After the RDBMS is initialized, run the Configuration and Reconfiguration utilities to define the AMPs and PEs that will operate together as an RDBMS.

The Configuration utility adds, changes, modifies, or displays vprocs or hosts in the new configuration map. The Reconfiguration utility then redefines the system configuration according to the new map.

For more information, see “Configuration” in Teradata RDBMS Utilities and Chapter 10: “Reconfiguration Utility.”


Chapter 16: System Initializer UtilityUsing System Initializer

Using System Initializer

Warning: Running SYSINIT on a previously initialized system destroys all existing data and deletes all tables.

Step Action

1 Start SYSINIT.

For operating-specific instructions on how to start SYSINIT, see “Starting and Exiting SYSINIT on NCR UNIX MP-RAS” on page 16-2.


***********************************************************************

***********************************************************************

***** *****

***** W A R N I N G *****

***** *****

***** This program will destroy all user and dictionary data on *****

***** the system. *****

***** *****

***********************************************************************

***********************************************************************

SYSINIT Master AMP Vproc is 0 at 11:25:42 on 00/04/14

If the RDBMS is running, SYSINIT displays the following message is displayed also:

The DBS is currently running!!!

SYSINIT cannot execute while the DBS is running.

Would you like to restart the system without the DBS (YES/NO)?

2 At the prompt, answer one of the following:

IF you answer … THEN SYSINIT …

YES does the following:

• Implicitly sets the Start DBS flag to Off in the PDE control parameters GDO

• Automatically restarts the RDBMS• Displays the following message and exits:

SYSINIT terminated without updating disks.

You will have to start SYSINIT again.




NO displays the following message and exits:

Set the "Start DBS" flag to "Off" using the XCTL utility program and restart the system prior to running SYSINIT again.


3 In this case, you must terminate SYSINIT, type the following:

NO

4 Use ctl (Windows 2000) or xctl (UNIX MP-RAS) to set the Start DBS flag to OFF. For information, see “ctl Utility (Windows 2000 Only)” and xctl Utility (UNIX MP-RAS Only)” in Teradata RDBMS Utilities.

5 Restart SYSINIT. (For operating-specific instructions on how to start SYSINIT, see “Starting and Exiting SYSINIT on NCR UNIX MP-RAS” on page 16-2.) The following message appears:

***********************************************************************

***********************************************************************

***** *****

***** W A R N I N G *****

***** *****

***** This program will destroy all user and dictionary data on *****

***** the system. *****

***** *****

***********************************************************************

***********************************************************************

A display indicating the console AMP vproc number, the current time, and the current date, as shown below:

SYSINIT Master AMP Vproc is 0 at 11:25:42 on 00/04/14

6 SYSINIT attempts to read the DBS Control Record GDO.

The DBS Control Record is a GDO that contains the global variables that the RDBMS needs, including the hash function value. SYSINIT handles the DBS Control Record differently, depending on whether the RDBMS was initialized previously or is being initialized for the first time.

IF the DBS Control Record GDO …

THEN SYSINIT displays the following message …

is corrupted or does not exist

A new DBS Control Record will be initialized to default values.

If a new DBS Control Record is used, the file system tunables in the GDO are the V2R5 default values.

Step Action



IF the DBS Control Record GDO …

THEN SYSINIT displays the following message …

does exist indicating:

The existing DBS CONTROL GDO will be used.

If an existing DBS Control record is used, the action depends on the current values for the File System tunables and the value of Disk Blocks Per Cylinder. For an explanation of the File System tunables, their definition, and how to change their values, see DBS Control utility in Teradata RDBMS Utilities.

The following are the cases for an existing DBS Control Record:

• Disk Blocks Per Cylinder and all File System Tunables are the V2R2 defaults.

– A warning is printed indicating the Disk Blocks Per Cylinder is not the preferred value.

• Disk Blocks Per Cylinder is the V2R2 default, and some File System Tunables are the V2R3 defaults.


– A second warning is printed indicating some of the File System Tunables are the V2R3 defaults.

• Disk Blocks Per Cylinder is the V2R2 default, and all File System Tunables are the V2R3 defaults.


– A second warning is printed indicating all of the File System Tunables are the V2R3 defaults.

• Disk Blocks Per Cylinder is the V2R3 default, and any of the File System tunables are the V2R2 defaults.

– All File System tunables will be set to the V2R3 defaults, and a warning indicating this fact is printed.

If the DBS Control Record exists, the RDBMS was previously initialized. In this case, SYSINIT keeps the current values in the DBS Control Record, but you can change the current values for the hash function or the locale attribute later.

If the system was last initialized on a release prior to V2R3, SYSINIT recommends that you first run pdeconfig to change the cylinder size. Before V2R3, the only cylinder size supported was 1488. With V2R3, NCR recommends that you switch to the new cylinder size of 3872. This new size provides a more efficient support of the larger data blocks allowed with V2R3 and also allows for AMP VPROC sizes of 120 GB (120 * 10**9 or 112 * 2**30). If you use the old cylinder size, the AMP vproc size limit will remain 46 GB (46 * 10**9 or 43 * 2**30).

Step Action



7 Note: SYSINIT supports old hashing functions.

The following message appears and prompts you for action:

The HashFuncDBC value in the DBSCONTROL GDO is International

Universal Hash is recommended for all new installations

Do you wish to use Universal Hash (YES/NO/QUIT)?

IF you answer … THEN SYSINIT displays the following …

NO Enter hash function

1 Universal Hash - Japanese/no Japanese support

2 Kanji Hash - Japanese support

3 International Hash - no Japanese support

Type the hash setting you want (for example: 2).

The locale is set based on the hash setting:

• For Kanji hash (2), Japanese language support is enabled. • For International hash (3), Japanese language support is not enabled.

YES Enable Japanese language support (YES/NO/QUIT)?

IF you answer … THEN you get … And the system data is …

YES standard support plus Japanese support

Kanji1.

Note: Hash function choices are prompted, and, by default, the hash function is Universal Hash.

Japanese characters and functions are available.

Enabling Japanese Language Support might impact system performance.

This affects DBS Control GDOs locale attribute.

NO standard support Latin.

Step Action



8 SYSINIT attempts to read the current configuration map.

IF a valid configuration map …

THEN SYSINIT …

does not exist or is corrupted

initializes the configuration to a full configuration based on vprocconfig GDO and displays the following:

Config Map will be initialized.

does exist retains the current configuration and displays the following message:

The current configuration map has been read.

9 SYSINIT displays a message about destroying user and dictionary data and prompts you to confirm this action, as shown below:

SYSINIT is about to destroy all user and dictionary data. Are you sure that you want to do this? (YES/NO/QUIT)?

IF you answer … THEN SYSINIT displays the following message …

YES Deleting all tables...

NO or QUIT before terminating:


10 If you answer YES, SYSINIT checks to see if AMP vproc 0 is defined or if the hardware required to run AMP vproc 0 is available. If not, one of the following messages is displayed before SYSINIT terminates:

AMP vproc 0 is not operational.SYSINIT terminated without updating disks.

or

AMP vproc 0 is not defined.SYSINIT terminated without updating disks.

SYSINIT will not initialize any AMPs that are not operational, that is, their VprocState is NONODE. The following message is displayed if any are found:

The following AMPs are defined in the current configuration map and the physical hardware required to run them is not available. Hence, they will not be initialized by SYSINIT.

nnnn nnnn nnnn ...

where nnnn nnnn nnnn ... represent the vproc numbers of the AMPs in question.

For a previously initialized system where SYSINIT was able to read the current configuration, SYSINIT first displays the current number of AMPs and PEs, as follows:

Accessing the current configuration map.. .

The current configuration map includes:

4 PE(s) and 8 AMP(s)

Step Action



11 If more than one AMP and one PE exist, SYSINIT displays four options for the current and new configuration maps, as follows:

The current configuration map includes:


Enter a value for the current/new configuration maps:

1 for current: 4 PE(s) and 8 AMP(s)

new: 4 PE(s) and 8 AMP(s)







12 Type a value for the current/new configuration maps (for example: 1):

1

13 SYSINIT displays the following messages to confirm your selection:

Updating the new configuration to:


Updating the current configuration to:


Updating current hash maps...

Step Action



14 Before terminating, SYSINIT prompts you for the following action:

Would you like to continue with startup (YES/NO)?

IF you answer … THEN the following message appears …

YES if you previously set the Start ALL Appls flag in XCTL to Off:

The CONTROL GDO has 'Start ALL applications' turned off.

This will prevent the database application from starting.

Would you like to turn it on (YES/NO)?

Note: This applies only to UNIX MP-RAS systems.


YES turns on the Start DBS flag and quits.

NO displays the following message and quits:

Don’t forget to reset the Start DBS flag to On using the XCTL utility program prior to restarting the system.

NO Don't forget to set the "Start DBS" flag to "On" usingXCTL utility program prior to restarting the system.

SYSINIT complete.

After displaying the message, SYSINIT quits.

Step Action



Example 1

This example shows that after the user started SYSINIT, a message stating that the RDBMS is running appears, and SYSINIT terminates.

_______ | | | | ___ __ ____ | ____ __|__ ____ | / |/ \ ____| ____| ____| | ____| | --- | / | / | / | | / | | \___ | \____| \____| \____| |__ \____| Release V2R.04t.00.00.00 Version 04D.00.00.00.00 SYSINIT Utility (Feb 97)

*********************************************************************************************************************************************** ******** W A R N I N G ******** ******** This program will destroy all user and dictionary data on ******** the system. ******** ********************************************************************************************************************************************* SYSINIT Master AMP Vproc is 0 at 10:40:47 on 00/04/14.+ The DBS is currently running!!!SYSINIT cannot execute while the DBS is running.Would you like to restart the system without the DBS (YES/NO)?no

Set the "Start DBS" flag to "Off" using the XCTL utility programand restart the system prior to running SYSINIT again. SYSINIT terminated without updating disks.



Example 2

The following example shows a complete SYSINIT session on a V2R4 system that has been upgraded from a V2R3 system, including prompts, user responses, and messages. The example assumes a previously configured Teradata RDBMS with an existing DBS Control Record and an existing current configuration map. Universal Hash is accepted, and the Start All Applications flag is not turned on prior to SYSINIT completion.

_______ | | | | ___ __ ____ | ____ __|__ ____ | / |/ \ ____| ____| ____| | ____| | --- | / | / | / | | / | | \___ | \____| \____| \____| |__ \____| Release V2R.04t.00.00.00 Version 04D.00.00.00.00 SYSINIT Utility (Feb 97) *********************************************************************************************************************************************** ******** W A R N I N G ******** ******** This program will destroy all user and dictionary data on ******** the system. ******** ********************************************************************************************************************************************* SYSINIT Master AMP Vproc is 0 at 11:23:53 on 00/04/14. The existing DBSCONTROL GDO will be used.

The HashFuncDBC value in the DBSCONTROL GDO is Universal

Universal hash is recommended for all new installations

Do you wish to use Universal Hash (YES/NO/QUIT)?yes

Enable Japanese language support (YES/NO/QUIT)?yes

The current configuration map has been read.



SYSINIT is about to destroy all user and dictionary data!!!Are you sure that you want to do this (YES/NO/QUIT)?yes

Deleting all tables... Accessing the current configuration map... The current configuration map includes: 2 PE(s) and 2 AMP(s)


1 for current: 2 PE(s) and 2 AMP(s) new: 2 PE(s) and 2 AMP(s)



4 for current: 0 PE(s) and 1 AMP(s) new: 0 PE(s) and 1 AMP(s)1

Updating the new configuration to: 2 PE(s) and 2 AMP(s)

Updating the current configuration to: 2 PE(s) and 2 AMP(s) Updating current hash maps... Would you like to continue with start up (YES/NO)?yes

The CONTROL GDO has 'Start ALL applications' turned off.This will prevent the database application from starting.Would you like to turn it on (YES/NO)?no

Prior to restarting the system set 'Start ALL Appl' to 'on' by using XCTL SYSINIT complete.



Example 3

The following example shows a complete SYSINIT session on a V2R4 system that has been upgraded from a V2R3 system, including prompts, user responses, and messages. The example assumes a previously configured Teradata RDBMS with an existing DBS Control Record and an existing current configuration map. The user enables Kanji hash and allows SYSINIT to turn on Start All Applications flag prior to SYSINIT completion.

_______ | | | | ___ __ ____ | ____ __|__ ____ | / |/ \ ____| ____| ____| | ____| | --- | / | / | / | | / | | \___ | \____| \____| \____| |__ \____| Release V2R.04t.00.00.00 Version 04D.00.00.00.00 SYSINIT Utility (Feb 97) *********************************************************************************************************************************************** ******** W A R N I N G ******** ******** This program will destroy all user and dictionary data on ******** the system. ******** ********************************************************************************************************************************************* SYSINIT Master AMP Vproc is 0 at 11:25:42 on 00/04/14. The existing DBSCONTROL GDO will be used.

The HashFuncDBC value in the DBSCONTROL GDO is Universal

Universal hash is recommended for all new installations

Do you wish to use Universal Hash (YES/NO/QUIT)?no

Enter hash function1 Universal Hash2 Kanji Hash3 International Hash2



Enable Japanese language support (YES/NO/QUIT)?yes

The current configuration map has been read. SYSINIT is about to destroy all user and dictionary data!!!Are you sure that you want to do this (YES/NO/QUIT)?yes

Deleting all tables... Accessing the current configuration map... The current configuration map includes: 2 PE(s) and 2 AMP(s)





4 for current: 0 PE(s) and 1 AMP(s) new: 0 PE(s) and 1 AMP(s)1

Updating the new configuration to: 2 PE(s) and 2 AMP(s)

Updating the current configuration to: 2 PE(s) and 2 AMP(s) Updating current hash maps... Would you like to continue with start up (YES/NO)?yes

The CONTROL GDO has 'Start ALL applications' turned off.This will prevent the database application from starting.Would you like to turn it on (YES/NO)?yes

SYSINIT complete.


Appendix A:

How to Read Syntax Diagrams

This appendix describes the conventions that apply to reading the syntax diagrams used in this book.

Teradata RDBMS Utilities - G-S A – 1

Appendix A: How to Read Syntax DiagramsSyntax Diagram Conventions

Syntax Diagram Conventions

Notation Conventions

The following table defines the notation used in this section:

Item Definition / Comments

Letter An uppercase or lowercase alphabetic character ranging from A through Z.

Number A digit ranging from 0 through 9.

Do not use commas when entering a number with more than three digits.

Word Variables and reserved words.

IF a word is shown in . . . THEN it represents . . .

UPPERCASE LETTERS

a keyword.

Syntax diagrams show all keywords in uppercase, unless operating system restrictions require them to be in lowercase.

If a keyword is shown in uppercase, you can type it in uppercase or mixed case.

lowercase letters a keyword that you must type in lowercase, such as a UNIX command.

lowercase italic letters

a variable such as a column or table name.

You must substitute a proper value.

lowercase bold letters

a variable that is defined immediately following the diagram that contains it.

UNDERLINED LETTERS

the default value.

This applies both to uppercase and to lowercase words.

Spaces Use one space between items, such as keywords or variables.

Punctuation Enter all punctuation exactly as it appears in the diagram.

Teradata RDBMS Utilities - G-SA – 2


Paths

The main path along the syntax diagram begins at the left, and proceeds, left to right, to the vertical bar, which marks the end of the diagram. Paths that do not have an arrow or a vertical bar only show portions of the syntax.

The only part of a path that reads from right to left is a loop.

Paths that are too long for one line use continuation links. Continuation links are small circles with letters indicating the beginning and end of a link:

When you see a circled letter in a syntax diagram, go to the corresponding circled letter and continue.

Required Items

Required items appear on the main path:

If you can choose from more than one item, the choices appear vertically, in a stack. The first item appears on the main path:

Optional Items

Optional items appear below the main path:

If choosing one of the items is optional, all the choices appear below the main path:

You can choose one of the options, or you can disregard all of the options.

FE0CA002

A

A

FE0CA003

SHOW

FE0CA005

SHOW

VERSIONS

CONTROLS

FE0CA004

SHOW

CONTROLS

FE0CA006

SHOW

CONTROLS

VERSIONS



Abbreviations

If a keyword or a reserved word has a valid abbreviation, the unabbreviated form always appears on the main path. The shortest valid abbreviation appears beneath.

In the above syntax, the following formats are valid:

• SHOW CONTROLS• SHOW CONTROL

Loops

A loop is an entry or a group of entries that you can repeat one or more times. Syntax diagrams show loops as a return path above the main path, over the item or items that you can repeat.

The following rules apply to loops:

IF . . . THEN . . .

there is a maximum number of entries allowed

the number appears in a circle on the return path.

In the example, you can type cname a maximum of 4 times.

there is a minimum number of entries required

the number appears in a square on the return path.

In the example, you must type at least three groups of column names.

a separator character is required between entries

the character appears on the return path.

If the diagram does not show a separator character, use one blank space.

In the example, the separator character is a comma.

a delimiter character is required around entries

the beginning and end characters appear outside the return path.

Generally, a space is not needed between delimiter characters and entries.

In the example, the delimiter characters are the left and right parentheses.

FE0CA042

SHOW

CONTROL

CONTROLS

JC01B012

(

, 4

cname )

, 3



Excerpts

Sometimes a piece of a syntax phrase is too large to fit into the diagram. Such a phrase is indicated by a break in the path, marked by | terminators on either side of the break. A name for the excerpted piece appears between the break marks in boldface type.

The named phrase appears immediately after the complete diagram, as illustrated by the following example.

LOCKING excerpt

where_cond

A

cname

excerpt

JC01A014

A

HAVING con

,

col_pos

,


Appendix B:

Priority Scheduler Frequently Asked Questions (FAQ)

This section contain frequently asked questions and answers about the following:

• Basic concepts• Priority weighting and resource allocation• Performance periods and allocation groups

Teradata RDBMS Utilities - G-S B – 1

Appendix B: Priority Scheduler Frequently Asked Questions (FAQ)Basic Concepts

Basic Concepts

Question

Does dynamically changing the priority of a session immediately impact the currently running query or only the next query that runs within the session?

Answer

If you change the priority of a session from the Performance Monitor by modifying the account string of the session, this causes the priority of the new account to take effect immediately. This change in priority does not wait for the next query to begin. For detailed information, see SET SESSION ACCOUNT in Teradata RDBMS PM/API Reference.

Question

Do we have to maintain the default resource partition?

Does this mean we can only create four new resource partitions in addition to the default resource partition?

Answer

Yes, you must maintain the default resource partition. You cannot zero it out. All of its performance groups must keep the same names. The Teradata RDBMS uses the default performance groups within the default resource partition for some internal processes, even if all users are assigned to performance groups within other resource partitions.

Yes, you can create and use four additional resource partitions and also assign users to the default resource partition if you want.

For more information on resource partitions, see “Resource Partitions” on page 7-9.

Question

When I run the schmon -m command, a display appears almost instantaneously, but when I run the schmon -M command, the display takes a long time to appear. Why?

Answer

The schmon -m command is quicker because it reports activity for the current node only. Most of the time, the schmon -m command provides adequate information.

The schmon -M command takes longer because it communicates with all nodes, gathering details from each and reporting system-wide. Although schmon -M takes longer, it returns you a minimum and a maximum resource.

Teradata RDBMS Utilities - G-SB – 2


However, the schmon -M command does not specify which node has the minimum or the maximum resource usage. For more information on the schmon utility, see “schmon Utility” on page 7-45.

Question

When no processes were active for allocation group 3 (associated with performance group names H and high$) in the default resource partition, allocation group 3 still appeared on the schmon -m command report. Why would an allocation group with no active processes be reported?

Answer

You might see an allocation group in schmon -m output with zero processes active because of the 60-second aging interval in Priority Scheduler. You can see the current value of this sliding interval with a schmon -t command, which displays Age Time.

Every two seconds, the Priority Scheduler looks at the preceding 60 seconds resource usage for each allocation group and makes a re-assessment of what constitutes recent usage. In doing so, the Priority Scheduler adds in the resource usage for the recent two seconds and drops the oldest two seconds from the end.

Then, the Priority Scheduler makes adjustments in its next allocation to compensate for any past inequalities.

When the last process (or only process) in an allocation group completes, this allocation group takes 61 seconds (the length of the active interval) to disappear from the display, even if no new resources are being accumulated (which is the case when you see zero processes).

The Priority Scheduler phases out the presence of an allocation group over the aging interval. If no activity has occurred for the active interval, then Priority Scheduler removes the presence of an allocation group from any calculation. You can alter this aging interval if you want. When the schmon -m command counts the number of processes, that number equals the processes at that point in time only, rather than processes accumulated over the aging interval. For more information, see “schmon Utility” on page 7-45.

Question

How often will the default resource partition be used if all end users are assigned to other resource partitions?

Will the relative weighting of the default resource partition be a factor in determining run-time allocations most of the time or all of the time?

Answer

A low number of significant tasks consume resources in the default resource partition if all users execute queries in performance groups within resource partitions other than the default resource partition.




• “Determining the Relative Weight of a Resource Partition” on page 7-10• “Limiting Resource Partition CPU Usage” on page 7-11• “Performance Group and Weight Defaults for Resource Partition 0” on page

7-14

Question

The documentation for the RollbackPriority field in the DBS Control utility states that when this field is set to the default (FALSE), subsequent transaction aborts then are rolled back at the priority level defined by the R performance group within the default resource partition. Does that mean that the query might run in a user resource partition while the rollback runs in the default resource partition?

Answer

Yes. For example, you could run a query under a performance group in resource partition 2 and the rollback, if needed, would happen in the default resource partition.

For more information on RollbackPriority, see the DBS Control Utility in Teradata RDBMS Utilities.

Question

Does this mean that if RollbackPriority is set to TRUE that subsequent aborts then are rolled back at the priority level defined by the performance group of the aborted job and within the assigned resource partition of the performance group?

Answer

Yes. TRUE means use the accountid of the logon of the user to determine what priority to execute the rollback in. If set to TRUE then any rollback that originates from a user transaction will be done at the priority used by the user query. If the field is FALSE, then all rollbacks will take place at a default resource partition performance group value 6, which is the R priority.

For more information on RollbackPriority, see the following:

• DBS Control Utility in Teradata RDBMS Utilities• “Performance Group Value” on page 7-17

Question

Will assigning the default resource partition a low resource partition relative weight compared to that of other resource partitions impact any internal Teradata RDBMS processes?



For example, rollbacks use R as the default performance group. If the default resource partition had only one tenth of total resource partition weighting, could rollbacks take 10 times as long to run?

What other Teradata RDBMS processes might be impacted by a low relative weight for the default resource partition?

Answer

If all users are assigned to performance groups in user-defined resource partitions, then only a small level of internal activity occurs within the default resource partition.

The following are some of the processes that use performance groups in the default resource partition:

• Deadlock detection• File system utilities• Resource usage data collection• Space accounting• Transaction rollbacks• Event logging• Miscellaneous express requests

NCR recommends making the weighting of your default resource partition comparatively high, even though it uses low amounts of resources. Do not alter individual performance group weightings within the default resource partition too radically from their current settings, particularly keeping performance group values 6 and 7 with a higher relative weighting.


• “Determining the Relative Weight of a Resource Partition” on page 7-10• “Performance Group and Weight Defaults for Resource Partition 0” on page

7-14• “Performance Group Name” on page 7-15

Question

While using the schmon -m command, I noticed that allocation group #4 (associated with performance groups R and rush$) in the default resource partition seems to have a number of processes active when the system is idle. Is this normal?

Answer

Yes. A number of internal processes can be active when user queries are idle. These processes operate at a very low level of CPU usage and should not impact other processes when they begin. These processes could include M, H, and R.



Question

Does the schmon -E command disable priority scheduling just for users that have been associated with performance groups?

Or does the command also impact all internal use of priority scheduling?

Answer

The schmon -E command removes any sensitivity of priority in all internal queues. Every allocation of resource is first come, first served. NCR recommends that you do not disable priority scheduling, since Teradata relies on priorities for most internal processes.

For more information, see “schmon Utility” on page 7-45.

Question

Can names of resource partitions and performance groups be changed once I have created them?

Answer

Yes. Your database administrator must be aware that changing a performance group name might affect session logon success. Sessions already logged on with a performance group assignment continue to use that assignment even if its parameters, including its name, are changed. Resource partition names are not used by the Priority Scheduler, except for descriptive purposes in the schmon utility.

The one exception to changing names is the default resource partition performance groups (L, M, H, and R). You cannot change those names.

Question

How can I delete components, such as allocation groups?

Answer

You cannot delete a resource partition, performance group, or allocation group. If they are not being used, they have no impact. However, you can remove these components by removing the /ntos/system.gdo from all TPA nodes and initiating an RDBMS restart to rebuild the system.gdo with the original defaults, although NCR does not recommend this procedure.

Any user-defined elements will be lost. You will need to reconfigure them with Priority Scheduler. Because of this limitation, NCR recommends not to remove the system.gdo record but instead to script the original Priority Scheduler user configuration, so that you can revert to it easily if you want.

Question

Are restarts required when I make a change to a component?



Answer

No. You do not need to perform a restart for component changes. However, the schmon utility forces some order when you create resource partitions, performance groups, and allocation groups. You must define a resource partition and allocation group before a performance group, which references the resource partition and allocation group.


Appendix B: Priority Scheduler Frequently Asked Questions (FAQ)Priority Weighting & Resource Allocation

Priority Weighting & Resource Allocation

Question

Can I change priority allocation weightings on the fly, without a restart?

Answer

Yes. Changes to allocation group weightings are effective immediately.

Question

What combination of CPU and I/O is used to decide resource usage and future allocation?

Are any other resources taken into account?

Does table caching affect the I/O calculation?

Answer

Only CPU and I/O are considered, and both count equally. Physical I/O, rather than logical I/O, is counted. Therefore, if a data block has been cached, and no actual I/O to disk is performed, then accessing that block in memory will not count as resource use to the Priority Scheduler.


• “Using Scheduling Policies” on page 7-34• “Resource Accounting” on page 7-37

Question

Does a Teradata Performance Monitor user count in allocating resources?

Answer

Teradata Performance Monitor is a client interface to PM/API, which itself uses only a small amount of CPU. PM/API dips into the database for information, mainly from memory, without using much CPU. Teradata Performance Monitor executes at the default performance group (M) and is unlikely to be impacted by other priority changes in the system.

Question

What is the time interval for re-assessing resource allocation?



Answer

Priorities are derived by two methods:

• The Priority Scheduler counts resource usage of each process in terms of its relationship to the allocation group every 10 ms and computes a new dispatch priority for each process within the allocation group at the end of that interval.

• In addition, the Priority Scheduler computes resource usage for each allocation group every two seconds and reconsiders the percentage of resources allocated to each allocation group based on its weight and usage system-wide.

The DEFAULT scheduling policy uses both of these timing intervals.


• “Resource Usage” on page 7-22• “Determining Allocation Group Relative Weight” on page 7-27• “Allocation Group Weight” on page 7-27• “Using Scheduling Policies” on page 7-34

Question

The Teradata Performance Monitor documentation states that I can dynamically change the priority of a running query through the PM/API. Does this mean that I can send the query to any performance group defined in the system?

Or does the query have to remain in the same resource partition?

Answer

When the database administrator uses Teradata Performance Monitor to change the priority of a session, the database administrator might assign any valid performance group in the system, regardless of what resource partition the performance group is associated with. The normal USER check in the dictionary is bypassed, so no check occurs to verify whether the new account is associated with that user. A user is not identified with a resource partition but with a performance group.

Question

How are scheduling sets best used? Although I think I understand its functionality (that is, resource allocation based on processes within a performance group versus sessions within a performance group), I am not sure of the impact of this parameter. The implication is that when set to NONE, sessions with more processes will get relatively more resources.

How is this important and what does this affect?

Are there certain types of activities that generate more processes than others?



Answer

Your interpretation is correct.

In the schmon utility, the default of NONE (appears as an N in the schmon utility display screen) means the Priority Scheduler lumps all active processes in that allocation group into one grouping called a scheduling set. Resources are divided by individual need at the process level.

In the schmon utility, if SESSION (appears as an S in the schmon utility display screen) is specified instead, then the Priority Scheduler divides the allocation group weight by the number of active sessions. Then, all sessions get the same allocation, regardless of whether they have multiple processes started.

Certain types of activities do generate more processes than others, such as complex tasks which spawn processes to other AMPs. An example is row redistribution. Also, if the query plan has multiple parallel steps, more AMP work tasks (and more processes) are used for that same session on each AMP. Sessions with these types of queries would benefit from N, the default. Sessions that perform single-AMP operations will be less favored by N.

This is a division of resources within the same allocation group. Changing the default to S will not help your short-running, single-AMP operation queries if they are assigned to a different allocation group at a higher priority. The difference you are likely to see is between less complex queries versus more complex queries all running at the same allocation group. In this case, N might be a slightly better choice for the more complex queries, and S is slightly better choice for the less complex.

For more information, see “schmon Utility” on page 7-45.


Appendix B: Priority Scheduler Frequently Asked Questions (FAQ)Performance Periods & Allocation Groups

Performance Periods & Allocation Groups

Question

Can the Priority Scheduler recognize weekends in a performance period milestone limit that controls changes to resource allocations by time of day?

Answer

No. The performance period only allows expression of a time of day, not day of the week. One useful alternative to performance periods is to create an NCR UNIX MP-RAS script of schmon commands to alter the weights as you would like them for the weekend or whenever. If you use the UNIX cron utility, you can schedule these Priority Scheduler commands to execute on specific dates and times. After the schmon commands are executed, the new weights take effect immediately. Then you can batch and schedule a second set of commands to reverse the weight changes.

For more information, see “Time-of-day” on page 7-21.

Question

In the definition of a performance group you can specify performance periods with milestone limits.

Is this resource usage (which is in seconds) the same as AmpUsage seconds?

Is it across all AMPs?

Answer

When the Priority Scheduler accumulates CPU time, it is accumulated for all AMPs on a single node. The accumulation is not related to either ResUsage or AmpUsage. AmpUsage is AMP based, not node based. Priority Scheduler accumulations are for the life of the user session and are zeroed out when a session logs off. AmpUsage does not get zeroed out when a session logs off.

Question

How does the Priority Scheduler take skewing into account, which would result in a different resource use on each node?

Answer

Priority Scheduler does not try to control the scheduling algorithms on one node based on the resource usage on another. If milestone limits based on accumulation of CPU are set up, then work on behalf of one session could be using different allocation groups and have different weightings on different nodes.




Question

Is the milestone limit based on resource usage an upper or a lower limit?

Answer

The resource usage milestone limit value that is carried in the performance period is considered an upper limit. You should give the milestone limit something larger than zero when defining multiple performance periods for a given performance group; however, the final milestone limit always should be zero. Also, use zero as a milestone limit if all processes in that performance group are controlled by a single performance period.

One exception is the final resource milestone limit. It should always be zero, which tells Priority Scheduler to remain in this performance period until the session logs off.


Question

Can you give a good example of when the Time-of-Day Milestone Limit would be valuable?

Answer

The milestone limit in the performance period could be used to automate a decrease in priority for day-time query processes when the batch window start-time occurs every night. For example, at 11 P.M. every night, online query users could go from an allocation weighting of 30 down to 5, with no change in their logon account string. And then at 7 A.M. each morning they could automatically get the weight of 30 back. Other uses could revolve around different times of day when different departments are doing critical processes. The other milestone limit, accumulated CPU, could be used to push sessions that have used an unacceptably high amount of CPU into a lower weight automatically.


• “Performance Period Types and Limits” on page 7-21• “Time-of-day” on page 7-21

Question

When a query is running and the allocation group associated with a performance group changes because of a time-of-day milestone limit, does an in-process query dynamically adhere to the new allocation group characteristics?



Answer

Yes, immediately.


• “Performance Period Types and Limits” on page 7-21• “Time-of-day” on page 7-21

Question

Does the ABSOLUTE policy lead to a fixed allocation of resources within the share of the resource partition or system-wide?

Answer

If you assign a weight of 5 and a policy of ABSOLUTE to the allocation group associated with the L performance group, then users running the L performance group will get no more than 5% of the resources of the entire system that are available for users. The ABSOLUTE policy is not a function of the weight of the partition. However, until the ceiling of 5% is reached, that allocation group receives resources consistent with its relative weight. ABSOLUTE never reserves CPU equal to the threshold. ABSOLUTE only caps CPU usage if it reaches that threshold.

Remember, because the L performance group is associated with an allocation group with a scheduling policy of ABSOLUTE, if no other groups are active, then 95% of the resource usage might be idle.


• “Allocation Group Weight” on page 7-27• “Allocating Resources Using the ABSOLUTE Scheduling Policy” on page

7-34

Question

In the schmon utility you can set up ABSOLUTE scheduling policies. The documentation states that no more than 100% worth of ABSOLUTE weighting can be allocated across multiple ABSOLUTE policies, but the front end utility allows this to happen.

Is there a later check to capture this error? What happens if not?

Answer

No check is performed on the sum of ABSOLUTE policy weightings being 100. Although this recommendation is made, no actual harm occurs when this happens.


Appendix C:

Starting and Exiting Utilities

The following table includes the following information for each utility:

• Available operating systems• Links to starting and exiting information

Utility NCR UNIX MP-RAS Microsoft Windows 2000

Gateway Control

“Starting and Exiting Gateway Control on UNIX MP-RAS” on page 1-2

“Starting and Exiting Gateway Control on Microsoft Windows 2000” on page 1-3

Gateway Global “Starting and Exiting Gateway Global on UNIX MP-RAS” on page 2-3

“Starting and Exiting Gateway Global on Microsoft Windows 2000” on page 2-5

Lock Display “Starting and Exiting Lock Display on NCR UNIX MP-RAS” on page 3-2

“Starting and Exiting Lock Display on Microsoft Windows 2000” on page 3-3

Locking Logger “Starting and Exiting Locking Logger on NCR UNIX MP-RAS” on page 4-2

“Starting and Exiting Locking Logger on Microsoft Windows 2000” on page 4-3

modmpplist “Starting modmpplist” on page 5-2 “Starting modmpplist” on page 5-2

pdeconfig “Starting and Exiting pdeconfig” on page 6-7 “Starting and Exiting pdeconfig” on page 6-7

Priority Scheduler

“schmon Utility” on page 7-45

“xschmon Utility” on page 7-89

“schmon Utility” on page 7-45

Query Configuration

“Starting and Exiting Query Configuration on NCR UNIX MP-RAS” on page 8-2

“Starting and Exiting Query Configuration on Microsoft Windows 2000” on page 8-5

Query Session “From the Database Window” on page 9-2 “From the Database Window” on page 9-5

Reconfiguration “Starting and Exiting Reconfiguration on NCR UNIX MP-RAS” on page 10-4

“Starting and Exiting Reconfiguration on Microsoft Windows 2000” on page 10-6

Reconfiguration Estimator

“Starting and Exiting Reconfiguration Estimator on NCR UNIX MP-RAS” on page 11-2

“Starting and Exiting Reconfiguration Estimator on Microsoft Windows 2000” on page 11-4

Recovery Manager

“Starting and Exiting Recovery Manager on NCR UNIX MP-RAS” on page 12-3

“Starting and Exiting Recovery Manager on Microsoft Windows 2000” on page 12-6


“dbschk” on page 13-2

“nodecheck” on page 13-6

“syscheck” on page 13-23

“dbschk” on page 13-2

“nodecheck” on page 13-6

“syscheck” on page 13-23

RSSmon “Starting and Exiting RSSmon” on page 14-2 N/A

Teradata RDBMS Utilities - G-S C – 1

Appendix C: Starting and Exiting Utilities

Showlocks “Starting and Exiting Showlocks on NCR UNIX MP-RAS” on page 15-2

“Starting and Exiting Showlocks on Microsoft Windows 2000” on page 15-5

Sysinit “Starting and Exiting SYSINIT on NCR UNIX MP-RAS” on page 16-2

“Starting and Exiting SYSINIT on Microsoft Windows 2000” on page 16-3

Utility NCR UNIX MP-RAS Microsoft Windows 2000

Teradata RDBMS Utilities - G-SC – 2

Index

Symbols

!COMMAND command, modmpplist utility 5–12

A

Allocation group parametersallocation group weight 7–27resource accounting 7–37scheduling policy 7–31set division type 7–25

Allocation group weight 7–27Allocation groups 7–23

determining relative weight 7–27parameters 7–24performance groups and 7–24weight 7–27

AMP work tasks 7–39limiting 7–40limits 7–39reservations 7–39reserving 7–40

B

BLOCKERS command, Lock Display utility 3–11

C

Configuration maps, System Initializer utility and 16–6

D

DB command, Lock Display utility 3–15dbschk command, Resource Check Tools utility 13–2DEFAULT PRIORITY command, Recovery Manager

utility 12–32

Teradata RDBMS Utilities - G-

DISABLE EXLOGON command, Gateway Global utility 2–16

DISABLE LOGONS command, Gateway Global utility 2–17

DISABLE TRACE command, Gateway Global utility 2–18

DISCONNECT SESSION command, Gateway Global utility 2–19

DISCONNECT USER command, Gateway Global utility 2–20

DISPLAY commandmodmpplist utility 5–6

DISPLAY DISCONNECT command, Gateway Global utility 2–22

DISPLAY FORCE command, Gateway Global utility 2–23

DISPLAY GTW command, Gateway Global utility 2–24

DISPLAY NETWORK command, Gateway Global utility 2–27

DISPLAY SESSION command, Gateway Global utility 2–30

DISPLAY STATS command, Gateway Global utility 2–34

DISPLAY TIMEOUT command, Gateway Global utility 2–36

DISPLAY USER command, Gateway Global utility 2–37

E

ENABLE EXLOGON command, Gateway Global utility 2–39

ENABLE LOGONS command, Gateway Global utility 2–40

ENABLE TRACE command, Gateway Global utility 2–41

Error messages, pdeconfig utility 6–12

F

FLUSH TRACE command, Gateway Global utility 2–43

S Index –1

Index

Index –2

G

Gateway Control utilitychanging maximum sessions per node 1–10log files 1–4overview 1–1starting on Microsoft Windows 2000 1–3starting on NCR UNIX MP-RAS 1–2

Gateway Global utilityadministering sessions 2–12administering users 2–12command line functions 2–9displaying network information 2–11displaying session information 2–11exiting on Microsoft Windows 2000 2–5exiting on NCR UNIX MP-RAS 2–3exiting X Window interface 2–51getting help 2–15logging sessions off 2–14overview 2–1performing special diagnostics 2–13specifying hosts 2–10starting on Microsoft Windows 2000 2–5starting on NCR UNIX MP-RAS 2–3starting X Window interface 2–51user interfaces 2–8X Window interface 2–51

Gateway Global utility commandsDISABLE EXLOGON 2–16DISABLE LOGONS 2–17DISABLE TRACE 2–18DISCONNECT SESSION 2–19DISCONNECT USER 2–20DISPLAY DISCONNECT 2–22DISPLAY FORCE 2–23DISPLAY GTW 2–24DISPLAY NETWORK 2–27DISPLAY SESSION 2–30DISPLAY STATS 2–34DISPLAY TIMEOUT 2–36DISPLAY USER 2–37ENABLE EXLOGON 2–39ENABLE LOGONS 2–40ENABLE TRACE 2–41FLUSH TRACE 2–43HELP 2–44KILL SESSION 2–46KILL USER 2–47SELECT HOST 2–49SET TIMEOUT 2–50

GDOs, System Initializer utility and 16–5Globally Distributed Objects. See GDOs

Teradata RDBMS

H

HELP commandGateway Global utility 2–44Lock Display utility 3–18Recovery Manager utility 12–33

I

I/O concurrency level 7–38

J

Journal tables, Reconfiguration utility 10–11

K

KILL SESSION command, Gateway Global utility 2–46

KILL USER command, Gateway Global utility 2–47

L

LIST commandmodmpplist utility 5–7Recovery Manager utility 12–34

Lock Display utilitycommand overview 3–10exiting on Microsoft Windows 2000 3–3exiting on NCR UNIX MP-RAS 3–2explicit lock modes 3–8implicit lock modes 3–8lock mode contention 3–7lock modes 3–6lock request status 3–9overview 3–1starting on Microsoft Windows 2000 3–3starting on NCR UNIX MP-RAS 3–2

Lock Display utility commandsBLOCKERS 3–11DB 3–15HELP 3–18QUIT 3–19ROWHASH 3–20ROWRANGE 3–23

Utilities - G-S

Index

TABLE 3–25TRAN 3–27

Lock log reportdetermining the blocked user 4–27hexadecimal names support 4–30hexadecimal syntax 4–30inserting rows 4–24Locking Logger utility 4–16non-standard names support 4–30reducing the size of DBC.EventLog table 4–23reducing the size of lock log table 4–22reducing the size of tables 4–20

Lock log tables, Locking Logger utility 4–10Lock logger table requirements, Locking Logger

utility 4–8Lock modes, Lock Display utility 3–6Locking Logger utility

buffers 4–6creating lock log tables 4–10enabling LockLogger field in DBS Control

utility 4–7exiting on Microsoft Windows 2000 4–3exiting on NCR UNIX MP-RAS 4–2lock log buffers 4–6lock log tables 4–10lock logger table requirements 4–8messages 4–15overview 4–1producing a lock log report 4–16starting on Microsoft Windows 2000 4–3starting on NCR UNIX MP-RAS 4–2

Locksexplicit modes 3–8implicit mode 3–8mode contention 3–7modes 3–6request status 3–9

M

Messages, Locking Logger utility 4–15Milestone limits

resource usage 7–22time-of-day 7–21

modmpplist utilityoverview 5–1using 5–5

modmpplist utility commands!COMMAND 5–12DISPLAY 5–6LIST 5–7


OFF id_list 5–8ON id_list 5–9QUIT 5–10WRITE 5–11

N

nodecheck command, Resource Check Tools utility 13–6

O

OFF id_list command, modmpplist utility 5–8ON id_list command, modmpplist utility 5–9

P

Parallel Database Extensions. See PDEPDE

configuration, pre-installation planning 6–3configuring 6–13setting PDE to NULL state 6–14

pdeconfig utilityabout 6–2applying changes 6–54, 6–71assigning host channels 6–69configuring disk slicing 6–63configuring PDE 6–13configuring the disk array 6–61copying disk slicing 6–28copying pdisk mappings 6–32definitions of terms 6–5disk array summary screen 6–22disk slicing summary screen 6–28error messages 6–12examining a disk array 6–22examining disk slicing 6–28examining LAN mappings 6–38examining pdisk mappings 6–32example setup 6–58exiting with no changes 6–56gathering system information 6–59host channel mapping 6–45LAN summary screen 6–38mapping a LAN 6–67mapping pdisks 6–65modifying a disk array 6–22modifying disk slicing 6–28

S Index –3

Index

Index –4

modifying host channel mappings 6–45modifying LAN mappings 6–38modifying pdisk mappings 6–32modifying system configuration 6–20moving between screens 6–17overview 6–1pdisk mapping screen 6–32RSG vproc mapping screen 6–52running 6–16screens 6–16starting on NCR UNIX MP-RAS 6–7TPA summary screen 6–20viewing system configuration 6–20

Performance groups 7–13allocation groups and 7–13associating a name to a user 7–16naming 7–15number of active users and 7–29recording names in a user record 7–15resource partition 0 name differences 7–16supplying names during RDBMS session

logon 7–16values in default resource partition 0 7–17weight defaults for resource partition 0 7–14

Performance periodscomponents of 7–20limits 7–21time-of-day limit 7–21types 7–21

Priority Scheduler utilityabout 7–3about allocation groups 7–3about performance groups 7–3about resource partitions 7–3allocation groups 7–23basic concepts FAQ B–2components 7–5default settings 7–7FAQ B–1overview 7–1performance group names 7–15performance group values 7–17performance groups 7–13performance period limits 7–21performance periods 7–19priority weighting FAQ B–8resource allocation FAQ B–8resource partitions 7–9schmon utility 7–45using 7–8xschmon utility 7–89

Teradata RDBMS

Q

Query Configuration utilityabout 8–8ALL option 8–10AMPs option 8–13display options 8–8exiting on Microsoft Windows 2000 8–5exiting on NCR UNIX MP-RAS 8–2HELP 8–17Offline AMPs display 8–14offline PEs option 8–16Offline Processors option 8–12Online AMPs display 8–14online PEs option 8–16Online processors option 8–12options 8–9overview 8–1PE display 8–15physical processors 8–8processors option 8–11starting on Microsoft Windows 2000 8–5starting on NCR UNIX MP-RAS 8–2vprocs 8–8

Query Session utilityABORTING state 9–15ACTIVE state 9–16Archive sessions state displays 9–26BLOCKED state 9–17child sessions 9–9displays 9–10exiting on Microsoft Windows 2000 9–5exiting on NCR UNIX MP-RAS 9–2FastExport sessions state displays 9–45FastLoad sessions state displays 9–31IDLE state 9–18INDOUBT PARSING state 9–20INDOUBT state 9–19MultiLoad sessions state displays 9–37overview 9–1parent sessions 9–9PARSING state 9–21QUIESCED ABORT state 9–22QUIESCED ABORT WITH LOGOFF state 9–23QUIESCED INDOUBT state 9–24Recovery sessions state displays 9–26RESPONSE state 9–25Session State display 9–12session states 9–8starting on Microsoft Windows 2000 9–5starting on NCR UNIX MP-RAS 9–2

Utilities - G-S

Index

State Information displays 9–14stored procedures and 9–13Teradata Index Wizard and 9–13

Query Session utility statesABORTING 9–15ACTIVE 9–16BLOCKED 9–17IDLE 9–18INDOUBT 9–19INDOUBT PARSING 9–20PARSING 9–21QUIESCED ABORT 9–22QUIESCED ABORT WITH LOGOFF 9–23RESPONSE 9–25

QUIESCED INDOUBT state, Query Session utility 9–24

QUIT commandLock Display utility 3–19modmpplist utility 5–10Recovery Manager utility 12–43

R

REBUILD PRIORITY command, Recovery Manager utility 12–44

RECONFIG command, Reconfiguration utility 10–21Reconfiguration Estimator utility

exiting on Microsoft Windows 2000 11–4exiting on NCR UNIX MP-RAS 11–2overview 11–1starting on Microsoft Windows 2000 11–4starting on NCR UNIX MP-RAS 11–2

Reconfiguration utilityabout 10–9before starting 10–2commands overview 10–12disabling logons 10–2effects on journal tables 10–11enabling logons 10–3error messages 10–28exiting on Microsoft Windows 2000 10–6exiting on NCR UNIX MP-RAS 10–4journal tables 10–11new configuration map 10–9overview 10–1physical processors 10–9process 10–13starting on Microsoft Windows 2000 10–6starting on NCR UNIX MP-RAS 10–4timestamps 10–11vprocs 10–9


Reconfiguration utility commandsRECONFIG 10–21STATUS 10–24STOP 10–27

Recovery journal 12–18Recovery Manager utility

changed row journal 12–20commands 12–31deferred down AMP recovery 12–22deferred transaction recovery 12–14down AMP recovery 12–15down AMP recovery operations 12–15exiting on Microsoft Windows 2000 12–6exiting on NCR UNIX MP-RAS 12–3messages 12–28multiple recovery sessions 12–13online transaction recovery 12–11ordered system change journal 12–21overview 12–1priority levels 12–9recovery journal 12–18recovery journal records 12–19restarting 12–30starting on Microsoft Windows 2000 12–6starting on NCR UNIX MP-RAS 12–3transaction recovery sequence 12–12

Recovery Manager utility commandsDEFAULT PRIORITY 12–32HELP 12–33LIST 12–34QUIT 12–43REBUILD PRIORITY 12–44RECOVERY PRIORITY 12–44

RECOVERY PRIORITY command, Recovery Manager utility 12–44

Resource accounting 7–37I/O concurrency level 7–38limiting system CPU usage 7–38set active time 7–37set age time 7–37

Resource Check Tools utilitycreating a log file 13–8creating an optional syscheckrc file 13–33default syscheckrc file 13–30overview 13–1

Resource Check Tools utility commandsdbschk 13–2nodecheck 13–6syscheck 13–23syscheckrc 13–30

Resource partitions 7–9determining the relative weight 7–10limiting CPU usage 7–11

S Index –5

Index

Index –6

parameters 7–10suggestions for using 7–11

Resource usage milestone limit 7–22ROWHASH command, Lock Display utility 3–20ROWRANGE command, Lock Display utility 3–23RSSmon utility

customized configuration files 14–6customizing the Configuration file 14–6displaying ResUsage data 14–9overview 14–1standard configuration files 14–5

S

Scheduling policy 7–31allocating resources using ABSOLUTE 7–34allocating resources using RELATIVE 7–36using 7–34

schmon utility 7–45SELECT HOST command, Gateway Global

utility 2–49Set active time 7–37Set age time 7–37Set division type 7–25SET TIMEOUT command, Gateway Global

utility 2–50Showlocks utility

exiting on MP-RAS UNIX 15–2exiting on Windows 2000 15–5host utility (HUT) locks 15–7host utility locks 15–7HUT lock conflicts and 15–9interpreting the display 15–8overview 15–1starting on MP-RAS UNIX 15–2starting on Windows 2000 15–5

STATUS command, Reconfiguration utility 10–24STOP command, Reconfiguration utility 10–27Syntax, how to read A–1syscheck command, Resource Check Tools

utility 13–23syscheckrc command, Resource Check Tools

utility 13–30syscheckrc file 13–30System CPU usage, limiting 7–38System Initializer utility

about 16–5configuration maps 16–6exiting on MP-RAS UNIX 16–2exiting on Windows 2000 16–3GDOs 16–5

Teradata RDBMS

overview 16–1setting a new system 16–5setting a previously initialized system 16–5starting on MP-RAS UNIX 16–2starting on Windows 2000 16–3Teradata RDBMS initialization and 16–5using 16–7

T

TABLE command, Lock Display utility 3–25Time-of-day milestone limit 7–21TRAN command, Lock Display utility 3–27

W

WRITE command, modmpplist utility 5–11

X

X Window interface, Gateway Global utility 2–51xschmon utility 7–89

Utilities - G-S

Teradata RDBMS Utilities Volume 2 G-S - …dbmanagement.info/Books/MIX/Teradata_Vol_2_V2R4... ·...

Documents

Transcript of Teradata RDBMS Utilities Volume 2 G-S - …dbmanagement.info/Books/MIX/Teradata_Vol_2_V2R4... ·...