Tuning and Monitoring RMAN and the Automatic Diagnostic Workflow - OCP: Oracle Database 12c Administrator Certified Professional - page 243

3 25 UNDOTBS1 *** C:\ORACLE\ORADATA\ORCL\UNDOTBS01.DBF
4 5 USERS *** C:\ORACLE\ORADATA\ORCL\USERS01.DBF
5 50 MY_DATA *** C:\ORACLE\ORADATA\ORCL\MY_DATA_01.DBF
List of Temporary Files
=======================
File Size(MB) Tablespace Maxsize(MB) Tempfile Name
---- -------- -------------------- ----------- --------------------
1 20 TEMP 32767 C:\ORACLE\ORADATA\ORCL\TEMP01.DBF
Note that the report header indicates that the control file is being used instead of the
recovery catalog.
Example of the REPORT UNRECOVERABLE Command
Certain types of SQL operations can make an object unrecoverable. This is because these
operations do not produce redo, in an effort to make the process more performant. Since
there is no redo, there is no recovering the object, and what you end up with after a recovery
is a shell of an object with no data in it. Here is an example.
First, you log into RMAN and issue the command REPORT UNRECOVERABLE DATABASE :
RMAN> report unrecoverable database;
starting full resync of recovery catalog
full resync complete
Report of files that need backup due to unrecoverable operations
File Type of Backup Required Name
---- ----------------------- -----------------------------------
You might have noticed the message “full resync complete” in some of our
output. This simply means that we are connected to a recovery catalog, and
the control file and the recovery catalog are being synchronized.
Next, you create an object in the SCOTT schema and load it with data:
SQL> create table unrecover_table (id number);
SQL> begin
2 for dd in 1..50
3 loop
4 insert into unrecover_table values (dd);
5 end loop;
6* end;
7 /