There is corruption in a table in the DBC database. Which action should the Administrator take to restore the table?

This action is appropriate for a scenario where table corruption is localized to a single Access Module Processor (AMP), often due to a hardware issue like a disk failure. In such cases, the system may take the faulty AMP offline to isolate the problem. The administrator's subsequent task is to recover the data on that AMP. For tables without Fallback protection, this involves restoring the affected table from the last known good backup. This targeted approach is preferred as it minimizes system downtime and impact compared to a full system restore, adhering to the principle of least impact for recovery.

A. Perform a SYSINIT, and restore the corrupted table.

SYSINIT reinitializes the entire system, deleting all user data and resetting the DBC data dictionary. Restoring a single table into a fresh system is not a valid recovery path.

B. Set the corrupted AMP offline, and restore the entire system.

Restoring the entire system is an excessive and unnecessary action if the corruption is isolated to a single AMP. This contradicts the principle of targeted and efficient recovery.

D. Perform a SYSINIT, and restore the entire system.

This is a last-resort disaster recovery procedure for catastrophic, system-wide DBC corruption that cannot be repaired by other means. It is not the standard first action for a single corrupted table.

1. Teradata Vantage™ - Database Administration, Release 17.20 (B035-1093-172K)

Chapter 10: Recovery and Restart, Section: "AMP Failure": This section details the process when an AMP fails. The system brings the vprocs for the failed AMP offline. The recovery procedure involves either using the Table Rebuild utility (for Fallback tables) or restoring the affected non-Fallback tables from a backup. This supports the sequence of an AMP going offline followed by a table-level recovery action, as described in option C.

Chapter 12: Database Utilities, Section: "SYSINIT": The documentation states, "Reinitialization deletes all user data and returns the Data Dictionary to its initial state." This confirms that SYSINIT is a drastic measure used for complete system reinitialization, making option D an extreme last resort, not a standard procedure for single-table corruption.

2. Teradata Vantage™ - Archive/Recovery Utility Reference, Release 17.20 (B035-1149-172K)

Chapter 2: ARCHIVE/RECOVERY (ARC) Mainframe, Section: "RESTORE": This section describes the syntax for restoring specific database objects, including individual tables. It confirms that restoring a single table is a valid operation, which is a key part of the correct answer. The context of an AMP failure dictates why this specific restore would be necessary.