15.00 - Chapter 29 TPA Reset (tpareset) - Teradata Database

Teradata Database Utilities

Teradata Database
Release Number
Content Type
Publication ID
English (United States)
Last Update

The TPA Reset utility, tpareset, resets Teradata Database. All PDE tasks except for some kernel daemons are killed. All database processes, including those for AMPs and PEs, are stopped and restarted. TPA Reset options control whether dump information is collected, whether the node on which tpareset is run is rebooted, and whether the system remains down or restarts.

TPA Reset can be used:

  • after Teradata Database has been reconfigured
  • to activate new versions of Teradata Database software
  • to recover from a database hang
  • in other situations that warrant a full database shutdown and restart
  • Caution:

    Use TPA Reset only when absolutely necessary. TPA Reset has a system-wide effect. Shutting down the system and restarting not only causes system down time, but can also have a performance impact when the system starts up and runs standard recovery and reconcile operations.

    Scenarios Runs From

  • Database Window or comparable interface to the Teradata Database console subsystem, such as cnsterm
  • Linux command line
  • For general information on starting the utilities from different interfaces, see Appendix B: “Starting the Utilities”

    Scenarios Syntax

    Note: Some strictly internal and rarely-needed options have been omitted from this discussion. Those options are documented in the tpareset command-line help.


    Syntax element





    Shuts down Teradata Database on all nodes of the system. The system must be explicitly restarted after the -x option is used.




    Brings PDE down on the node from which the tpareset was initiated. The other nodes go through a reset cycle, but the initiating node stays down. On an SMP system, this is equivalent to -exit.

    Sets the state of the initiating node to DOWN/TDMAINT. Nodes in this state stay down until tpareset -f or a system wide shutdown and restart brings them back into the Teradata Databasesystem.


    Forces a full restart on all nodes of the system. This option has the following effects:

  • Brings any nodes that are running but in DOWN/TDMAINT state back into the Teradata Database system.
  • Clears the system-wide crash count
  • If the crash count was preventing the database from being started, this option forces the database to be started on all nodes. -force should not be used until the condition that caused the crash loop has been corrected.

  • Forces reconcile to run
  • Reconcile normally runs when any node that was down is brought back up, or when a Teradata Database version switch has been requested, necessitating a system reset.


  • validates that each node is running the same version of the various software components that comprise Teradata Database
  • ensures that these versions are compatible with each other
  • switches versions of specific components if such a version switch has been requested. (Such version switches are specified from the ctl utility programs.)
  • The -f option forces reconcile to run during a reset, regardless of status of system nodes and regardless of whether a version switch has been requested.

  • Forces the database cache to be discarded
  • The database cache may also be discarded in other reset situations when the ‑f option has not been specified.

    Note: Reinitializing the cache can add several minutes to restart time.



    Initiates a reboot of the node where tpareset was executed. A database dump is captured from all nodes, and an operating system dump is captured on the rebooted node. The remaining nodes undergo a normal reset and restart cycle without being rebooted.

    When the database restarts, the node from which tpareset was run is excluded from the parallel database system. When the problem that required the panic reset is resolved, the node can be returned to service by issuing another tpareset.

    Note: This option should be used only if the Teradata Support Center determines that a dump is necessary for problem isolation.



    Prevents the -panic option from capturing a database-level dump. However, an operating system dump will still be captured on the initiating node, initiating a node reboot.



    Causes a database dump to be captured before the system is reset and restarted.

    Note: This option should be used only if the Teradata Support Center determines that a dump is necessary for problem isolation.



    Suppresses the normal tpareset confirmation prompt.



    The tpareset command must end with a string that describes the reason for the reset. The reason need not be delimited by double quotation marks or apostrophes. The string cannot start with a dash (-).



    Displays tpareset command syntax information.


    Scenarios Usage Notes

    The RESTART TPA command, available from Database Window (DBW), is similar to TPA Reset, in that it resets and restarts Teradata Database. However, RESTART TPA lacks several of the options of TPA Reset. For example, RESTART TPA cannot be used to shut down the PDE component of Teradata Database. For more information about DBW, see Database Window (xdbw).

    TPA Reset can only be run on nodes where PDE is running.


    > tpareset -d Recover from DBS hang.

    You are about to restart the database
                     on the system
            Do you wish to continue (default: n) [y,n]