About Me

My photo
Bangalore, India
I am an Oracle Certified Professional working in SAP Labs. Everything written on my blog has been tested on my local environment, Please test before implementing or running in production. You can contact me at amit.rath0708@gmail.com.

Wednesday, June 5, 2013

RMAN-06900: WARNING: unable to generate V$RMAN_STATUS or V$RMAN_OUTPUT row

Today I faced below error when I was trying to connect to RMAN prompt :-

bash-3.2$ rman target /

Recovery Manager: Release 11.2.0.1.0 - Production on Wed Jun 5 12:56:32 2013

Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.

connected to target database: AMIT (DBID=913650087)
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

I checked that these errrors(RMAN-06900, RMAN-06901) were just warnings from RMAN, whenever we get this error check for the additional error message. Here we got additional error message as  "ORA-19921: maximum number of 128 rows exceeded". Now our solution depends on ORA-19921 error which says that Oracle is not able to write output in V$RMAN_OUTPUT due to too many RMAN connections , check for the number of RMAN connections :-

bash-3.2$ ps -ef |grep rman
  oracle 24314072        1  50   Jun 03      - 369:15 rman target /
  oracle 35258568 37748790   0 13:00:59  pts/1  0:00 grep rman
  oracle 55115904 28311624   0 12:59:30  pts/2  0:00 rman target /

From output of above command we come to know that two rman sessions are there. If any backup is not going on then kill these RMAN sessions through kill command.

bash-3.2$ kill -9 55115904
bash-3.2$ kill -9 24314072
bash-3.2$ ps -ef |grep rman
  oracle 33685564 37748790   0 13:01:34  pts/1  0:00 grep rman

Now try to connect to RMAN :-

bash-3.2$ rman target /

Recovery Manager: Release 11.2.0.1.0 - Production on Wed Jun 5 13:01:38 2013

Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.

connected to target database: AMIT (DBID=903650087)

RMAN>


I hope this article helped you.

Regards,
Amit Rath

4 comments:

  1. It just did. Thanks! There were no 2 rman processes when I checked, but there was 1 hanging rman process that cause this error after backup ended with error. I was advised to use kill -15 next time so that there will be logs.

    ReplyDelete
    Replies
    1. Thanks Stephanie for writing in. Reason is same for both cases that Oracle is not able to write log output in v$RMAN_OUTPUT as its too large. It can be due to Control file corruption or an oracle bug also.

      Delete
  2. Thanks. It worked for me.
    wblntest:/home/oracle $> ps -ef|grep rman
    oracle 65798180 64422054 0 11:02:29 pts/0 0:01 rman target /
    wblntest:/home/oracle $> kill -9 65798180
    wblnddb01:/home/oracle $> ps -ef|grep rman
    oracle 37027846 55115888 0 12:34:36 pts/1 0:00 grep rman
    wblntest:/home/oracle $> rman target /

    Recovery Manager: Release 10.2.0.4.0 - Production on Tue Mar 19 12:34:44 2019

    Copyright (c) 1982, 2007, Oracle. All rights reserved.

    connected to target database: NACItest (DBID=3983062619)

    RMAN>

    ReplyDelete