Skip to Content
Former Member
Jun 09, 2008 at 11:08 AM

BRBACKUP terminates during FullOnline of Oracle Database



Our FullOnline backups (to disk) of a Production Oracle database are failing with the following error message:


BR0278E Command output of 'e:\oracle\SID\920\bin\RMAN nocatalog':

Recovery Manager: Release - Production

Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.


RMAN> connect target /;

connected to target database: SID (DBID=1609604882)

using target database controlfile instead of recovery catalog

RMAN> *end-of-file*


host command complete

RMAN> 2> 3> 4> 5>

allocated channel: dsk

channel dsk: sid=131 devtype=DISK

Starting copy at 07-JUN-08

released channel: dsk

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: failure of copy command at 06/07/2008 11:12:37

ORA-00235: controlfile fixed table inconsistent due to concurrent update

RMAN-06010: error while looking up datafile: G:\ORACLE\SID\SAPDATA4\SID_15\SID.DATA15

RMAN>Recovery Manager complete.

BR0280I BRBACKUP time stamp: 2008-06-07 11.12.37

BR0279E Return code from 'e:\oracle\SID\920\bin\RMAN nocatalog': 3

BR0536E RMAN call for database instance SID failed

BR0280I BRBACKUP time stamp: 2008-06-07 11.12.37

BR0503E Normal database backup using RMAN failed

BR0222E Copying G:\ORACLE\SID\SAPDATA4\SID_15\SID.DATA15 to/from S:\backtodisk\Database\bdycauxg failed due to previous errors

BR0056I End of database backup: bdycauxg.and 2008-06-07 11.12.37

BR0280I BRBACKUP time stamp: 2008-06-07 11.12.42

BR0280I BRBACKUP terminated with errors: 2008-06-07


We are running the following versions of software:

Windows Server 2003 Enterprise Edition 32-bit (SP0)

BRBACKUP 640 (40)


We have gone through a number of Notes and found relatively litttle resolution to this problem. Has anyone been able to resolve this or have any suggetions, other than a DB or hardware upgrade, that might solve this issue.

Thanks and regards,