Received RMAN-06900,RMAN-06901 and ORA-19921 while logged in to RMAN prompt to verify daily backups. (OS:Redhat linux 6.5)
WARNING message:
[oracle@primary logs]$ rman target / Recovery Manager: Release 11.2.0.1.0 - Production on Fri Aug 26 10:34:39 2016 Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved. connected to target database: BLADE1 (DBID=3381279798) 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 RMAN>
On further diagnosing and suggested by OERR utility, I have realized there is one old active session from Aug 23, as mentioned below.
[oracle@primary ~]$ oerr ORA 19921 19921, 00000, "maximum number of %s rows exceeded" // *Cause: The maximum number of rows in the V$RMAN_STATUS or V$RMAN_OUTPUT // table has been exceeded. // *Action: Close some of existing and unused RMAN connections and sessions.
So lets find out old session with ps -ef:
[oracle@primary logs]$ ps -ef|grep rman oracle 543 32693 0 10:50 pts/4 00:00:00 grep rman oracle 19783 19782 47 Aug23 ? 1-07:13:42 rman target /
There is one old active session above, OS ID: 19783, since 23 aug.
[oracle@primary ~]$ date Fri Aug 26 10:57:13 IST 2016
[oracle@primary logs]$ kill -9 19783
After successfully killed old session, we are no more facing mentioned list of warnings, as below:
[oracle@primary logs]$ rman target / Recovery Manager: Release 11.2.0.1.0 - Production on Fri Aug 26 10:50:54 2016 Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved. connected to target database: BLADE1 (DBID=3381279798) RMAN>
Thanks,
Stay Tune. 🙂
Thank You Mr. Jignesh for this article its really very helpful for me.. Keep up the Good Work 🙂
Thank you Ganesh for writing!
Stay Tune. 🙂