首页 » ORACLE » RMAN-06900&RMAN-06901 RMAN-00600 [3045] ORA-19921 when rman connect target

RMAN-06900&RMAN-06901 RMAN-00600 [3045] ORA-19921 when rman connect target

A friend asked me to help her solve a problems, Today . when her try to connect database with rman ,rman session being terminated, then show the following error, the database other queries operation are normal, butrman connect exception, DB version 11.1.0.6 on windows (currently very not recommend this environment)

C:\Users\sys-admin>rman target /

恢复管理器: Release 11.1.0.6.0 - Production on 星期二 4月 14 09:34:56 2015

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

连接到目标数据库: ORCL (DBID=1380673171)
RMAN-06900: 警告: 无法生成 V$RMAN_STATUS 或 V$RMAN_OUTPUT 行
RMAN-06901: 警告: 禁止更新 V$RMAN_STATUS 和 V$RMAN_OUTPUT 行
DBGANY:     Mismatched message length! [09:34:57.467] (krmiduem)
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: 内部恢复管理器程序包初始化失败
RMAN-00600: internal error, arguments [3045] [] [] [] []

Note:
I checked that these errrors(RMAN-06900, RMAN-06901) were just warnings from RMAN, The RMAN not able to update V$RMAN_STATUS or V$RMAN_OUTPUT due to associated error message. When you receive RMAN-06900 and RMAN-06901 error, you need to look for associated error messages to find the root cause of the error message. Here we got additional error message as “RMAN-00600: internal error, arguments [3045] [] [] [] []”. Search on MOS found there was a bug and is very consistent with the current error ,and just affect this version 11.1.0.6

There is provided a solution to bypass the problem, to change the NLS_LANG to American(NON-CHINESE maybe also, I’m not sure.)

1, set NLS_LANG ENV..

# no-Windows
export NLS_LANG=AMERICAN_AMERICA.ZHS16GBK  

# Windows 
c:/set  NLS_LANG=AMERICAN_AMERICA.ZHS16GBK    

2, Try again

C:\Users\sys-admin>rman target /

Recovery Manager: Release 11.1.0.6.0 - Production on Tue Apr 14 10:24:25 2015

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

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

Note:
Here rman-600 [3045] The problem has been bypassed, but there is an new error message ORA-19921,the rman session however continues successfully. A note of MOS “RMAN Connect Target fails RMAN-06900 RMAN-06901 ORA-19921: maximum number of 128 rows exceeded (ID 943571.1)” this an Know issue.

Cause

– Unpublished bug 4659734 is fixed in 10.2.0.4 and Oracle 11G.
Or
Bug 8264365: ORA-19921: MAXIMUM NUMBER OF 128 ROWS EXCEEDED
which is fixed in 11.2.0.2 and higher

Solution
These warnings can be ignored and will not affect rman functionality.
Depending on your RDBMS version :

– Uptill 10.2.0.4 : Ignore the message
– 10.2.0.5 or higher : Download Patch 8264365 to resolve this issue.

Or

To check for the number of RMAN connections,ORA-19921 error which says that Oracle is not able to write output in V$RMAN_OUTPUT due to too many RMAN connections

ps -ef |grep rman| grep -v grep

If output of above command had rman sessions are there. If any backup is not going on then kill these RMAN sessions through kill command from OS. then try to connect to RMAN again.

TIP:
Selecting a stable DB release is more important.

打赏

对不起,这篇文章暂时关闭评论。