A Differences in RMAN Commands

This appendix describes changes and limitations to standard RMAN commands when using Recovery Appliance.

Table A-1 Modified RMAN Commands

RMAN Command	Notes
CHANGE BACKUP ... UNAVAILABLE	This command should not be used with virtual backups.
CHANGE BACKUP ... UNCATALOG	This command should not be used with virtual backups.
CONFIGURE ... RETENTION POLICY	If RETENTION POLICY is set to NONE, then it is recommended that you configure a fast recovery area for local archived logs. The fast recovery area automatically manages its storage. As long as the fast recovery area has been sized appropriately for maintaining local logs, the fast recovery area will purge its storage space when necessary. Note: You can also store archived redo log backups to any disk directory when using a parallel backup strategy.
DELETE	DO NOT USE. Unlike normal backups, Recovery Appliance backup sets can include virtual backup and SBT pieces that are critical for successful recovery operations. In addition, missing backup pieces can interfere with indexing operations, tying up system resources and affecting the ingestion of new backups.
DROP DATABASE	Use the DBMS_RA.DELETE_DB procedure to unregister the protected database from the Recovery Appliance and then use the DROP DATABASE command.
MAXPIECESIZE clause	The MAXPIECESIZE clause of the CONFIGURE or ALLOCATE command is not supported for Recovery Appliance.
UNREGISTER DATABASE	Use the DBMS_RA.DELETE_DB procedure, instead of UNREGISTER DATABASE, to unregister a protected database from the Recovery Appliance. Note: See Zero Data Loss Recovery Appliance Administrator's Guide for information about the DELETE_DB procedure.