Books
in black and white
Main menu
Share a book About us Home
Books
Biology Business Chemistry Computers Culture Economics Fiction Games Guide History Management Mathematical Medicine Mental Fitnes Physics Psychology Scince Sport Technics
Ads

Teradata RDBMS Database Administration - NCR

NCR Teradata RDBMS Database Administration - NCR , 2004. - 616 p.
Download (direct link): teradatadatabaseadmin2004.pdf
Previous << 1 .. 197 198 199 200 201 202 < 203 > 204 205 206 207 208 209 .. 218 >> Next

Teradata Call-Level Interface Version 2 Reference for Channel-Attached Systems

Teradata Call-Level Interface Version 2 Reference for Network-Attached Systems

D - 6 Teradata RDBMS Database Administration

Appendix D: Tools for Monitoring Performance

Teradata Performance Monitor

Teradata Performance Monitor

Teradata Performance Monitor is an important diagnostic tool, interacting with PM/API and organizing the data that PM/API collects (for details, see "PM/API Dynamic Data" on page D-6).

The result is an orderly presentation of performance, usage, status, contention, and availability data at the following levels:

RDBMS

Resource, including physical and virtual

Session

Monitoring Capabilities

Teradata Performance Monitor enables you to:

Respond to help requests quickly, accurately, and confidently See a graphical representation of performance data Save all Monitor Session data in a history file Dynamically lower the resource priority of an active user In an emergency, abort a specific session Provide detailed and comprehensive reporting Manage Teradata RDBMS and its users effectively and efficiently

The configuration and summary displays in Teradata Performance Monitor are refreshed dynamically, based on the rate you specified through the facility: Tools -> Options -> Alerts.

Starting MONITOR

You invoke Teradata Performance Monitor from:

Teradata Manager via MONITOR

Windows 2000 using Start -> Programs

The ABORT SESSION command is introduced in the following paragraphs. For complete information on all Teradata Performance Monitor commands, see:

"Performance Monitor" in Teradata RDBMS Resource Usage Macros and Tables

The chapter titled "CLIv2 MONITOR Processing" in Teradata RDBMS PM/API Reference

Teradata Manager User Guide

Teradata Manager PMON command online help

D - 10

Teradata RDBMS Database Administration Appendix D: Tools for Monitoring Performance

Teradata Performance Monitor

ABORT SESSION Command

Aborting a session is considered an extreme emergency measure. Because of this, you can issue the ABORT SESSION command through a variety of tools in addition to Teradata Performance Monitor, including the Database Window (see Teradata RDBMS Database Window).

You must have the ABORT SESSION privilege to use the ABORT SESSION command (see Teradata RDBMS Security Administration).

With the ABORT SESSION privilege, you can:

Abort the session of a transaction blocking a critical application

Abort the session of a transaction using too many resources (but first consider simply setting the session to a lower resource priority)

Abort, with Logoff option, all users before a batch or maintenance window

Warning: You cannot halt an abort once you issue the ABORT SESSION command.

IF you . THEN .
use 2PC (Two-Phase Commit) use caution.
processing Caution: Do not abort or logoff internal TDP sessions used by 2PC (job name
*TDPINIT*).
need to use ABORT SESSION you should be aware of the following:
Listing a large number of aborted sessions (>1500) can cause delays.
The override option skips any sessions that cannot be aborted.
Teradata Performance Monitor assumes the Logoff and Override options
Without the Logoff option, abort will not work on the following:
- MultiLoad
- FastLoad
- FastExport
- HUTCTL or HUTPARSE
- DBCUTIL
- Sessions currently committing a transaction (logoff is executed after the
transaction is committed).
- Sessions currently rolling back a transaction (logoff is executed after the
transaction is rolled back).
You cannot abort or logoff sessions that are:
- In-doubt, as a result of two-phase commit
- Currently being switched to another PE
- Currently being aborted

D - 10 Teradata RDBMS Database Administration

Appendix D: Tools for Monitoring Performance

Teradata Performance Monitor

IF you . THEN .
need to abort an ARC operation any HUT locks placed on the objects being archived or restored will remain active unless you take care to remove them. Either: Include the RELEASE LOCKS option in the ARC command Release them after ARC is completed by: - Using ShowLocks to determine whether HUT locks exist - Submit the RELEASE LOCKS to release all active HUT locks
submit an ABORT SESSION and receive error message 3268: Command Disallowed: An identified session is not currently Abortable. you need to resubmit the request at a later time when AMP resources become available. You can use Performance Monitor to determine AMP resource availability (for details, see "Collecting and Reporting Processor (node/vproc) Data" on page D-6 and Teradata Manager User Guide). A high number of ABORT SESSION requests may lead to resource exhaustion if several of the requests are queued up and have not completed processing, or Teradata RDBMS is already under a very heavy workload. Additional information is recorded in the Performance Monitor error log.
Previous << 1 .. 197 198 199 200 201 202 < 203 > 204 205 206 207 208 209 .. 218 >> Next