Download (direct link):
• To change the running version of the Teradata RDBMS
• To register and globally propagate changes to certain fields in the DBS Control record, such as some user-tunable parameters
• To force a PDE dump to be taken
• To bring AMPs in "offline recovery" online.
• To register a changed default for a user-defined multinational character set or collation sequence.
Note: The default for saving dumps during a forced restart is always No. However, you can explicitly specify whether or not to save a dump.
Restarting in UNIX
To restart Teradata RDBMS on UNIX MP-RAS, follow the procedure below.
Note: If more than one node is down in the same clique, before restarting you can tune the system to not start more vprocs than the remaining nodes can run. To do this, set the Minimum Node Action and Minimum Nodes Per Clique options (in the DBS Settings window) to the appropriate values.
For details and instructions on the parameters of the DBS Settings and RSS Settings windows and the Debug and Dump screens, see the "xctl Utility" in Teradata RDBMS Utilities.
1 First, use the xctl utility to turn the DBS Start flag on:
# /usr/ntos/bin/xctl -nw
> screen debug
Warning: You must perform this step before you start Teradata RDBMS, otherwise the startup fails in
a manner that makes it impossible to initialize it properly.
9 - 2
Teradata RDBMS Database AdministrationChapter 9: Stopping and Restarting the System
Restarts of the Teradata RDBMS
2 Start the Teradata RDBMS using one of the following commands:
IF . THEN . Enter .
PDE is operable on any node: • at the UNIX prompt • from DBW console • using Vproc Manager • tpareset comment [[-f][-x]] • restart tpa comment [cold/coldwait] • restart [cold/coldwait]
PDE is not running on each node /etc/init.d/tpa START
3 Wait for the start to complete, then check the PDE state on all nodes with the command: /sbin/rallsh -sv /usr/ntos/bin/pdestate Verify that all nodes are in the TPA state.
Restarting in Windows 2000
Teradata RDBMS starts automatically on Windows 2000 after a reboot or startup.
To view the status of a restart, select:
Start -> Programs -> Teradata RDBMS -> Database Window
The Teradata RDBMS is fully started when the Database Window status line displays:
Logons enabled - The system is quiescent. Manual Restart
To manually restart the Teradata RDBMS on a Windows 2000 server:
1 Log onto the server as a user with administrator privileges.
2 Bring up the Teradata MultiTool window: Start -> Programs -> Teradata RDBMS -> Teradata MultiTool
3 In the MultiTool window, you can choose one of the following: • Press the Reset button and enter comments in the Restart dialogue box • Or type: net start recond
9 - 2 Teradata RDBMS Database Administration
Chapter 9: Stopping and Restarting the System
Startup and Recovery
Startup and Recovery
Restart processing take place without manual intervention, even in the event of a hardware failure, as long as an operational configuration exists. An operational configuration consists of:
• Not more than one offline/ down AMP in the same cluster.
• At least one available path to at least one copy of the data.
Usually, the configuration will be operational. In some instances, such as after a power loss, your field support personnel may need to reconfigure it manually.
Database Startup and Recovery
The database startup and recovery phases involve the following:
Sequence Teradata RDBMS ...
1 starts the PDE/TDA layers.
2 On an MPP system, PDE recalculates the minimum number of nodes per clique required for normal operation. Note: If you manually changed the Minimum Nodes Per Clique option before the restart, and PDE determines that the set value is smaller than the automatically calculated value, PDE uses the automatically calculated value. (For details, see "xctl Utility" in Teradata RDBMS Utilities.
3 starts the PE and AMP vprocs.
4 attempts to bring up any down AMPs; reports AMP status.
5 rebuilds any special system users and databases (see "The Initial Teradata Database" on page 1-3) and other system objects, as necessary.
6 if TDQM was active at the time of the restart, reads the TDQM.GDO and rebuilds the TDQM rules cache. TDQM resumes query validation as soon as sessions are reconnected and logons are enabled. (For more on TDQM, see "Scheduling Workloads with Teradata Dynamic Query Manager (TDQM)" on page 15-12.)
7 spawns dbscheck when "Logon Enabled" state is achieved (only if you have set dbscheck to run in daemon mode). Running as a background task on the tpa control node (lowest active node), dbscheck periodically samples DBS response time. If response exceeds the timeout interval, DBS issues the logevent; the event message includes the timeout value. To change the sleep and timeout intervals, run the dbscheck tool interactively from any node. To stop dbscheck, in Windows 2000 use <Ctrl>C or Task Manager. On UNIX, use the kill -pid command. (For instructions and examples, see "Resource Check Tools Utility" in Teradata RDBMS Utilities.)