How Oracle Rman configures exclude for tablespace

Briefly describe the Rman configure EXCLUDE for tablespace command.

Rman can use configure EXCLUDE for tablespace to set up a full library to skip some tablespaces. In general, you can use this command to skip the read-only or offline table space during a whole-library backup to reduce the time required for a whole-library backup and the space it takes.

A customer uses this configuration, configure EXCLUDE for tablespace skips a read-only tablespace before the backup starts, and includes all tablespaces in order to get control file backups, so that the control files are backed up in a separate configure EXCLUDE for tablespace Clear, then back up the control file, and finally in configure EXCLUDE for tablespace.

This method can effectively reduce the total space of backup, accelerate the speed of the whole library backup, but the personal view, this configuration is slightly inappropriate. Because in addition to the clear backup control file, this database also opens the control file automatic backup, when performs other backup, the copy operation or because of the database structure change produces the automatic control file backup, because the default set configure EXCLUDE for Tablespace, can cause problems with subsequent backup restores.

And when you create standby controlfile, you will also encounter this problem, so a better approach is to configure EXCLUDE for tablespace before backing up the database, and once the backup is complete, configure EXCLUDE for Tablespace clear so that any exclude information is not included, even if the control file is backed up automatically.

In fact, for the current situation, I personally do not choose to use the Configure EXCLUDE for tablespace this method, but will perform a full library backup with the Skip ReadOnly statement.