RMAN Backup Failed with RMAN-600 [6000]

APPLIES TO

Oracle Database - Enterprise Edition - Version 11.2.0.2 and later

Oracle Database Exadata Cloud Machine - Version N/A and later

Oracle Cloud Infrastructure - Database Service - Version N/A and later

Oracle Database Cloud Exadata Service - Version N/A and later

Oracle Database Exadata Express Cloud Service - Version N/A and later

Information in this document applies to any platform.

***Checked for relevance on 22-Feb-2013***

SYMPTOMS

Backup of datafiles is complete but after it we see a failure showing

RMAN-00600: internal error, arguments [string] [string] [string] [string] [string]

Cause: An internal error in recovery manager occurred.

Action: Contact Oracle Support Services.

DBGANY: 612 TEXTNOD = sys.dbms_backup_restore.setRmanStatusRowId(rsid=>0, rsts=>0);

DBGANY: 613 TEXTNOD = end;

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00601: fatal error in recovery manager
RMAN-03004: fatal error during execution of command
RMAN-00600: internal error, arguments [6000] [] [] [] []

After the failure the next step on the backup script is not executed, this could be an autobackup or a backup of archives.

CAUSE

Taking a closer look at the RMAN output obtained from the backup we see earlier errors

Channel dsk1: starting piece 2 at 15-MAY-11

RMAN-03009: failure of backup command on dsk2 channel at 05/15/2011 07:29:07
ORA-19504: failed to create file "/<DIR>/<DB_NAME>/<FILE_NAME>"
ORA-27040: file create error, unable to create file

Linux-x86_64 Error: 2: No such file or directory

Channel dsk2 disabled, job failed on it will be run on another channel

RMAN-03009: failure of backup command on dsk3 channel at 05/15/2011 07:29:07
ORA-19504: failed to create file "/<DIR>/FILE_NAME"
ORA-27040: file create error, unable to create file

Linux-x86_64 Error: 2: No such file or directory

Channel dsk3 disabled, job failed on it will be run on another channel

There could be other errors but in this case the output directory to write backup pieces did not exist on disk for at least one of the channels

This causes the channel to be disabled and the job to be executed on another available channel.

Then once the backup is complete the channel fails to be auto-allocated to execute the next backup command

The issue has been raised on unpublished Bug

Bug 6314281: RMAN-600: [6000] [] [] [] [] DOING "BACKUP RECOVERY AREA"

Fixed->12.2

SOLUTION

Workaround:-

------------------

Run {

Set autolocate off;

<... rest of backup commands ...>

}

Check for Availability of One off patch using link Patch 6314281

DBRECOVER Recovery Options

For Oracle incidents, start with the DBRECOVER for Oracle trial to verify table visibility, row previews, and export readiness on copied datafiles. For MySQL and InnoDB incidents, DBRECOVER for MySQL is free software and can inspect.ibd files, ibdata1, and database directories locally.

When the case is urgent, preserve the original files first, work from copies, and contact paid emergency support with the database version, platform, error messages, file list, and recovery objective.