Common reasons for interrupted systems include the following:
- Mismatch on certain DDL statements, for example CREATE DATABASE.
Repairing the mismatch will resolve this issue.
- Timeout while reading or writing to the system's heartbeat table.
For a heartbeat timeout, make sure that unitymgmtuser has no TASM restrictions and that no backup or restore jobs were running that could impact access to the Unity Management User.
- Timeout during automatic recovery of a long-running transaction.
If Unity does not receive a response within the specified recovery timeout, the system interrupts to allow the long-running transaction to complete, then restarts recovery. If this is an ongoing issue, contact Teradata Customer Support.