Your multitenant container (CDB) contains two pluggable databases (PDB), HR_PDB and
ACCOUNTS_PDB, both of which use the CDB tablespace. The temp file is called temp01.tmp.
A user issues a query on a table on one of the PDBs and receives the following error:
ERROR at line 1:
ORA-01565: error in identifying file ‘/u01/app/oracle/oradata/CDB1/temp01.tmp’
ORA-27037: unable to obtain file status
Identify two ways to rectify the error.
A.
Add a new temp file to the temporary tablespace and drop the temp file that that produced the
error.
B.
Shut down the database instance, restore the temp01.tmp file from the backup, and then restart
the database.
C.
Take the temporary tablespace offline, recover the missing temp file by applying redo logs, and
then bring the temporary tablespace online.
D.
Shutdown the database instance, restore and recover the temp file from the backup, and then
open the database with RESETLOGS.
E.
Shut down the database instance and then restart the CDB and PDBs.
Explanation:
* Because temp files cannot be backed up and because no redo is ever generated
for them, RMAN never restores or recovers temp files. RMAN does track the names of temp files,
but only so that it can automatically re-create them when needed.
* If you use RMAN in a Data Guard environment, then RMAN transparently converts primary
control files to standby control files and vice versa. RMAN automatically updates file names for
data files, online redo logs, standby redo logs, and temp files when you issue RESTORE and
RECOVER.
A — in former releases you had to do this quite often. For example after a manual clone process.
E — in Oracle 11g and 12c the database creates a tempfile during startup if it does not exist.
Not B,C,D because there is no need to back up a tempfile so why sould the tempfile be in a backup then?
A and E definitely