To recover a table from an RMAN backup to a specified point in time due to logical corruption, you need to determine the backup containing the table, issue the recover table RMAN command with the appropriate parameters, and then create a Data Pump export dump file for the recovered table. Step 1 is necessary to identify the correct backup, step 2 involves using the RMAN recover table command with the auxiliary destination and specified recovery time, and step 4 allows for the creation of the dump file on the target database. Importing the Data Pump export dump file into the auxiliary instance (step 3) is not required in this process. Hence, the correct sequence is 1, 2, 4.
The command 'RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL;' is used in scenarios where the current state of the control file is unreliable or missing, requiring the use of a backup control file to proceed with recovery. One common scenario is when the current online redo log file is missing, making it necessary to use a backup control file (Option A). Another scenario is when the database backup is older than the control file backup, necessitating this command to ensure consistency during the recovery process (Option D).
To set up Flashback Data Archive, Automatic Undo Management must be enabled because it ensures that undo data is managed automatically without user intervention, which is necessary for Flashback operations. Additionally, the tablespace in which the Flashback Data Archive is created should have Automatic Segment Space Management (ASSM) enabled because ASSM provides efficient space management and is required for the storage and management of historical data in Flashback Data Archives.