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 .. 178 179 180 181 182 183 < 184 > 185 186 187 188 189 190 .. 218 >> Next


Step

Action

Run the Reconfiguration utility to:

For an add-only operation: Redistribute the data rows across the new and existing vdisks

For a replace operation: Physically copy the contents of the old pdisks to the new pdisks

Copy the new configuration map to the current configuration map

Note: When Reconfig starts, an added AMP shows a status of NewReady, and remains in this state until PUT (or pdeconfig) removes it from the configuration.

Use PUT CONFIGURE TERADATA, or run pdeconfig and use the MOVE AMP/MOVE PE operations, to:

Switch the AMP and/or PE definitions in these files:

- vconfig.txt

- vconfig.gdo

Remove the old node and/or old vproc definitions from the configuration.

Note: When processing is complete, the old AMPs should not appear in a configuration or status list.

Check the state of your databases and data:

Step Action
a Run the full SCANDISK command with logons disabled (quiescent system).
b Run CHECKTABLE LEVEL 3 on database DBC with logons disabled (quiescent system).
c Run CHECKTABLE LEVEL 2 on all critical production databases and tables. If all logons are disabled, it is safe to use the IN PARALLEL option to reduce CheckTable runtime. Caution: CheckTable with IN PARALLEL requires substantial spool space.
d Visually audit the CHECKTABLE output to identify any skipped tables.
e Run CheckTable for each table that was skipped because of lock contention.

When all tables are checked, physically remove the old node and/or storage from the hardware platform.

first, contact the TSC;

then:

Teradata RDBMS Utilities for:

- "Configuration Utility"

- "CheckTable Utility"

- "Reconfiguration Utility"

- SCANDISK command (see "Ferret Utility")

For pdeconfig command-line operation (from a PDN console window only) on UNIX, see Teradata RDBMS Utilities

For pdeconfig GUI operation:

- Parallel Upgrade Tool (PUT) for MP/RAS UNIX

- Parallel Upgrade Tool (PUT) for Windows 2000 User Guide

For node and storage removal, your server hardware

maintenance manual

5

6

7

8

A - 18

Teradata RDBMS Database Administration A - 13 Appendix A: Teradata RDBMS Configuration, Global Defaults, and Client Connections

Client Configuration Overview

Client Configuration Overview

There are two types of Teradata RDBMS clients:

Type Description
Channel attached Mainframe computing system, such as IBM VM or MVS.
Network attached Windows 2000 or UNIX workstation

A session is the transfer of data between a user on a client and the Teradata RDBMS on the server, including the logical and physical connections that make data transfer possible.

Teradata Client Management Subsystems

During a session, all communication between a user and the database pass through a client-resident management subsystem called:

Teradata Director Program (TDP) on a channel-attached client

Micro Teradata Director Program (MTDP) on a network-attached client

Director program functions include:

Session initiation and termination

Logging, verification, recovery and restart notification for client applications

Coordinates the physical input to, and output from, the Teradata RDBMS

Security

Teradata Director Program (TDP) for Channel-Attached Clients

The channel interface enables communication between a mainframe client and the Teradata RDBMS. TDP establishes a session with the associated PE and manages communications between the client and the Teradata server. When a user or application submits an SQL request, the TDP transfers it to the Teradata RDBMS, receives the response, and transfers the response to the application.

Micro Teradata Director Program (MTDP) for Network-Attached Clients

In a network environment, MTDP establishes a session with the Teradata gateway and manages the routing of user request/server response parcels to and from the gateway. The gateway manages the routing of parcels to and from the PE.

The following figure provides a functional overview of channel-attached and network-attached clients, and the Teradata RDBMS.

Teradata RDBMS Database Administration

A - 19 Appendix A: Teradata RDBMS Configuration, Global Defaults, and Client Connections

Client Configuration Overview

Channel-Attached System

Network-Attached System

Channel

Teradata RDBMS

1- Parsing Engine Parsing Engine 1
I I
Message Passing Layer
H H
AMP AMP AMP AMP
H

KY01A022

A - 20

Teradata RDBMS Database Administration Appendix A: Teradata RDBMS Configuration, Global Defaults, and Client Connections

Communicating with Teradata RDBMS

Communicating with Teradata RDBMS

What is a Session?

A session is a logical connection between the user and the Teradata RDBMS. A session permits a user to submit one transaction at a time and receive one response at a time, and the current session can have only one transaction outstanding at any time. A user may communicate through one or more active sessions concurrently.
Previous << 1 .. 178 179 180 181 182 183 < 184 > 185 186 187 188 189 190 .. 218 >> Next