But its real pain limits the type reporting you can your backups

✓ NOCATALOG mode stores backup data only in the control file for each individual database. This is the default.

✓ You have a lot of databases to back up.

✓ All the databases you back up are different versions of Oracle.

✓ Limits the type of reporting you can do on your backups. You can query only one database at a time, after which you have to manually aggregate all the reports for multiple databases together.

Suppose that at the end of every week you want a report that sums up all the backup information for 50 databases ranging from Oracle 8i to 12c. You want that report to include things such as elapsed time, average piece size, com-pression info, and backup type. A recovery catalog can easily generate that report.

1. Create a tablespace to hold the RMAN data by typing in SQL*Plus: <create tablespace rman_data datafile
‘/u01/app/oracle/oradata/dev12c/rman_data01.dbf’ size 100M
autoextend on next 100M maxsize 2G;>
You see this:
Tablespace created.

2. Type the following to create the catalog owner:
<create user rmancat identified by rmancat
default tablespace rman_data
quota unlimited on rman_data;>
You see this:
User created.