I had faced this error suddenly while testing backup scripts on my test server. what actually happened here, i executed scripts (sh backup_archivelog.sh). but, scripts get hanged, and unable to proceed after connected to RMAN prompts. so i killed only sh backup_archivelog.sh command process from linux process. but i forgot to kill rman session.
Error:
Recovery Manager: Release 11.1.0.7.0 - Production on Thu Apr 21 13:17:37 2016
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: PROD (DBID=207624248, not open)
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
After above error, i checked number of RMAN connection/running process. i seen two rman target / connection were established.
ps -ef|grep rman
[oraprod@testhost:/usr/tmp]$/PROD/trace]$ ps -ef|grep rman
oraprod 22335 1 23 13:07 pts/1 00:04:50 rman target / log=/Archive/log_remove.log
oraprod 22403 22153 0 13:17 pts/1 00:00:00 rman target /
oraprod 22431 22233 0 13:27 pts/2 00:00:00 grep rman
From above output, i came to know that there are two RMAN session are connect and running.
if you faced above error when you try to connect RMAN, then kill all sessions. you will be able to connect RMAN without any error.
[oraprod@testhost:/usr/tmp]$ kill -9 22335 22403
Recovery Manager: Release 11.1.0.7.0 - Production on Thu Apr 21 13:37:35 2016
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: PROD (DBID=207624248, not open)
RMAN>
I hope this article may help you.
