RMAN-06900 RMAN-06901 ORA-19921: maximum number of 64 rows exceeded

Problem Description
RMAN backup completed successfully but backup logs shows warning message as,
RMAN-06900: WARNING: unable to generate V$RMAN_STATUS or V$RMAN_OUTPUT row
RMAN-06901: WARNING: disabling update of the V$RMAN_STATUS and V$RMAN_OUTPUT rows ORACLE error from target database:
ORA-19921: maximum number of 64 rows exceeded

A variant version of warning message is like below,

connected to target database: PROD1 (DBID=3378321056)
RMAN-06900: WARNING: unable to generate V$RMAN_STATUS or V$RMAN_OUTPUT row
RMAN-06901: WARNING: disabling update of the V$RMAN_STATUS and V$RMAN_OUTPUT rows
ORACLE error from target database:
ORA-19921: maximum number of 128 rows exceeded

Cause of the Problem
The RMAN-06900 RMAN-06901 ORA-19921 error stack indicates oracle RMAN bug. ORA-19921: maximum number of 64 rows exceeded is oracle bug 4659734 and ORA-19921: MAXIMUM NUMBER OF 128 ROWS EXCEEDED is oracle Bug 8264365. This bug fires when the RMAN output is too huge because it couldn't log the output in v$rman_output.

Solution of the Problem
If your RMAN goes well and you only see warning message in your RMAN log then simply you can ignore these warnings. The bug "ORA-19921: maximum number of 64 rows exceeded" is fixed in Oracle 10.2.0.4 version and in 11g. So to solve it upgrade your oracle version or apply oracle patch. If you already have oracle version 10.2.0.4 + and hit this bug then in fact you should do nothing and just to wait for oracle to resolve the issue.

Related Documents
http://arjudba.blogspot.com/2010/01/rman-00571-rman-00569-rman-00571-rman.html
http://arjudba.blogspot.com/2010/01/rman-06900-rman-06901-ora-19921-maximum.html

ORA-00204 ORA-00202 ORA-27071 HP-UX Error: 9: Bad file number

Problem Description
RMAN backup fails with ORA-00204 ORA-00202 ORA-27071 HP-UX Error: 9: Bad file number as below.

Recovery Manager: Release 11.1.0.7.0 - Production on Fri Jan 29 00:01:15 2010
Copyright (c) 1982, 2007, Oracle. All rights reserved.
RMAN-06900: WARNING: unable to generate V$RMAN_STATUS or V$RMAN_OUTPUT row
RMAN-06901: WARNING: disabling update of the V$RMAN_STATUS and V$RMAN_OUTPUT rows
ORACLE error from target database:
ORA-00204: error in reading (block 1, # blocks 1) of control file
ORA-00202: control file: '/SID/oradata/APEXP/control01.ctl'
ORA-27071: unable to seek to desired position in file
HP-UX Error: 9: Bad file number

An another version of error message appear while starting RMAN is,
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-06003: ORACLE error from target database:
ORA-00204: error in reading (block 3, # blocks 1) of control file
ORA-00202: control file: '/SID/oradata/APEXP/control01.ctl'
ORA-27071: unable to seek to desired position in file
HP-UX Error: 9: Bad file number Additional information: 2

Cause of the Problem
The RMAN-06900, RMAN-06901 error occurs when the RMAN couldn't log the output in $rman_output. The actual investigation of the error comes in the associated additional error messages. If you look for additional error message we will see ORA-27071, HP-UX Error: 9: Bad file number. The word 'HP-UX Error: 9: Bad file number' indicates that error is coming from operating system. The OS user who is invoking RMAN don't have OS permission on the control file and hence HP-UX generates bad file number error.

Solution of the Problem
The user who is invoking RMAN don't have write permission on the controlfile. You must need to change permission from operating system. You can do so by issuing,
$chmod 666 /SID/oradata/APEXP/control01.ctl

After you change the permission now try to invoke RMAN command again.
Related Documents:

How to Restore the Controlfile from Backup.

ORA-00214: Controlfile Version Inconsistent on Startup or Shutdown

Controlfile in Oracle Database.

New Feature of 10.2g: Eliminate Control File Re-Creation

Creating controlfile fails with ORA-01503, ORA-01161

Backup Database control file -User Managed

Recover database after only lose of all controlfiles

ORA-01624: log needed for crash recovery

Error Description
In the database dropping standby redo logfile fails with error ORA-01624 as below.

SQL> alter database drop standby logfile group 2;
alter database drop standby logfile group 2
*
ERROR at line 1:
ORA-01624: log 2 needed for crash recovery of instance ctl3 (thread 1)
ORA-00312: online log 2 thread 1: '/oradata3/ctl3/redo02.log'
ORA-00312: online log 2 thread 1: '/oraidx3/ctl3/redo02b.log'

Cause of the Problem
The Online redo log which is being dropped on the primary is either the current online redo log or
it has not completely been archived yet. To know more about the redo logfile status see Redo Log file status. By querying the V$LOG view you can see the status of the redo log file. In order to drop a redo log file the status column should be 'INACTIVE'.

Solution of the Problem
1) Switch the logfile on primary database so that group can become non-current.
SQL> ALTER DATABASE SWITCH LOGFILE;

2) Copy the standby logfile from primary database to standby database.

3) In the primary database move the logfile to a different location

4) Rename the logfile

5) Clear the logfile using 'alter database clear logfile group ..'

6) Drop the standby logfile using 'alter database drop standby logfile group ...'
Related Documents

Startup fails with oracle error ORA-00119, ORA-00132

What will be the Archived Redo Log Destination in Oracle

Recovering After the Loss of Online Redo Log Files

Relocating and Renaming Redo Log Members

ORA-00354 ORA-00353 ORA-00312 Corrupt redo block header

ORA-00313 ,ORA-00312 open failed for members of log group

http://arjudba.blogspot.com/2008/04/redo-log-file-status.html