在对数据库进行备份的时候，使用了backup的 keep 选项，遇到了一个错误 ORA-19811.
Recovery Manager: Release 11.2.0.4.0 - Production on Tue Dec 24 13:39:49 2013
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: ANDREA
run {
2> allocate channel ch1 device type disk;
3> allocate channel ch2 device type disk;
4> backup as backupset tag 'full-base-line'
5> keep forever restore point 'full' database plus archivelog;
6> delete backupset 94;
7> delete backupset 95;
8> crosscheck backupset;
9> release channel ch1;
10> release channel ch2;
11> }
Starting backup at 24-DEC-13
current log archived
backup will never be obsolete
archived logs required to recover from this backup will be backed up
channel ch1: starting archived log backup set
channel ch1: specifying archived log(s) in backup set
input archived log thread=1 sequence=17 RECID=13 STAMP=835019297
channel ch1: starting piece 1 at 24-DEC-13
released channel: ch1
released channel: ch2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 12/24/2013 13:48:20
ORA-19811: cannot have files in DB_RECOVERY_FILE_DEST with keep attributes。
[oracle12@andrew1 Desktop]$ oerr ora 19811
19811, 00000, "cannot have files in DB_RECOVERY_FILE_DEST with keep attributes"
// *Cause: An attempt was made to
// 1) Create a backup piece or image copy in the recovery area with
// KEEP option.
// 2) Update the KEEP attributes of an existing backup piece or
// image copy in the recovery area.
// *Action: Reissue RMAN command without KEEP options.
也可以参考Oracle? Database Backup and Recovery Reference上的有关keep的说明：
Specifies the backup as an archival backup, which is a self-contained backup that is exempt from the configured retention policy.
An archival backup is self-contained because is contains all files
necessary to restore the backup and recover it to a consistent state. If
the database is open during the backup, then RMAN automatically
generates and backs up the archived redo log files needed to make the
database backup consistent (see Example 2-25).
RMAN does not consider backup pieces with the KEEP option when computing the retention policy. If available, RMAN uses
these backups for disaster recovery restore operations, but their
purpose is to produce a snapshot of the database that can be restored on
another system for testing or historical usage.
Note: You cannot use KEEP to override the retention policy for files stored in the fast recovery area. If you specify KEEP when backing up to the recovery area, then RMAN issues an error.
When KEEP is specified, RMAN creates multiple backup
sets. RMAN backs up data files, archived redo log files, the control
file, and the server parameter file with the options specified in the
first backupOperand. Since a backup of the control file is created, an autobackup of the control file is not created. RMAN uses the FORMAT, POOL, and TAG parameters for all the backups. For this reason, the FORMAT string must allow for the creation of multiple backup pieces. Specifying %U is the easiest way to meet this requirement.
See Also: CONFIGURE and Oracle Database Backup and Recovery User's Guide to learn more about autobackup of the control file.
When KEEP is specified with INCREMENTAL LEVEL, the parent backup must be a KEEP backup and have the same TAG string. Unless both these criteria are met, the backup cannot be
created. Backups that meet these criteria do not interfere with other
nightly or archival backup tasks.
Note: A recovery catalog is only required for KEEP FOREVER. No other KEEP options require a catalog.
根据上述提示，可以修改备份文件的存储位置可以解决这个问题
run {
allocate channel ch1 device type disk;
allocate channel ch2 device type disk;
backup as backupset tag 'full-base-line'
format '/oracle/dbbackup/whole-%s-%t-%u'
keep forever restore point 'full' database plus archivelog;
crosscheck backupset;
release channel ch1;
release channel ch2;
}