If a non-recoverable database crashes, how can a DBA successfully restart the database if a table
space is damaged and cannot complete crash recovery?

A.
The database must be restarted using the RESTART DATABASE command with the DROP PENDING
TABLESPACES option specified. At that point, the database can be brought on-line and the damaged
table space must be dropped and re-created.

B.
The damaged table space must be restored from the latest backup and any active transaction logs
in the log path can then be applied to it using the TABLESPACE ONLINE option of the ROLLFORWARD
DATABASE command. This will bring
the table space on-line and synchronize it with the rest of the database.

C.
The damaged table space must be restored from the latest backup image. Once restored from the
backup image, the RESTART DATABASE command can be issued to apply all the relevant transactions
from the active logs. At that point,
the database will come on-line and all table spaces will be synchronized.

D.
The damaged table space will require that the entire database be restored from the latest backup
image because the database is non-recoverable and will not be accessible.