15.10 - Functionality - Teradata Database

Teradata Database Application Programming Reference

prodname
Teradata Database
vrm_release
15.10
category
Programming Reference
featnum
B035-1090-151K

The following table describes the System PMPC interfaces that are used to show how efficiently Teradata Database is using its resources, to identify problem sessions and users, and to abort sessions and users having a negative impact on system performance.

 

If you want to ...

Use the following SQL interface...

OR use the following CLIv2 or Teradata JDBC Driver request ...

abort any outstanding requests or transactions of one or more sessions

“AbortSessions” on page 225

or

“AbortListSessions” on page 222

“ABORT SESSION” on page 56

return the name of a user, by session, who is causing a block

“IdentifySession” on page 229

“IDENTIFY” on page 68

return the name of the specified table ID

“IdentifyTable” on page 230

“IDENTIFY” on page 68

return the name of the specified user ID who is causing a block.

“IdentifyUser” on page 231

“IDENTIFY” on page 68

collect statistics on AMPs based on the inuse AMP Worker Tasks (AWTs)

“MonitorAMPLoad” on page 232 or “MonitorAWTResource” on page 234

“MONITOR AWT RESOURCE” on page 76

collect session information for the current user on the current host

“MonitorMySessions” on page 238

collect overall information on node availability

“MonitorPhysicalConfig” on page 256

“MONITOR PHYSICAL CONFIG” on page 84

collect RSS data and returns node-specific data

“MonitorPhysicalResource” on page 259

“MONITOR PHYSICAL RESOURCE” on page 92

collect global summary information

“MonitorPhysicalSummary” on page 264

“MONITOR PHYSICAL SUMMARY” on page 103

return session or request resource usage statistics

“MonitorSession” on page 269

“MONITOR SESSION” on page 111

return session rate

“MonitorSessionRate” on page 287

“MONITOR SESSION” on page 111

return data about the step being executed of the currently running request

“MonitorSQLCurrentStep” on page 289

“MONITOR SQL” on page 149

return the step information of the current or running request

“MonitorSQLSteps” on page 293

“MONITOR SQL” on page 149

return the SQL text of the request currently being executed for the specified host, session, and vproc

“MonitorSQLText” on page 298

“MONITOR SQL” on page 149

return BYNET status and system type values that are generated once for the entire system or collect overall information on node availability

“MonitorSystemPhysicalConfig” on page 300

“MONITOR PHYSICAL CONFIG”

collect information on virtual processor (vproc) availability

“MonitorVirtualConfig” on page 302

“MONITOR VIRTUAL CONFIG” on page 165

collect performance information for each AMP, PE, or TVS vproc

“MonitorVirtualResource” on page 304

“MONITOR VIRTUAL RESOURCE” on page 172

collect global summary information on system utilization

“MonitorVirtualSummary” on page 310

“MONITOR VIRTUAL SUMMARY” on page 185

return ResUsageSps data from the RSS SPS memory buffer

“MonitorWD”

“MONITOR WD”

return a subset of the RSS ResUsageSps data or return the collection rate, number of nodes with at least one online AMP, and number of nodes with at least one online PE

“MonitorWDRate”

“MONITOR WD”

set either the:

  • ResMonitor rate
  • ResLogging rate
  • “SetResourceRate” on page 325

    “SET RESOURCE RATE” on page 205

    change the account string for the session or for the request.

    “SetSessionAccount” on page 327

    “SET SESSION ACCOUNT” on page 209

    set the global and local rates for updating session-level statistics in memory

    “SetSessionRate” on page 329

    “SET SESSION RATE” on page 214