首页 » ORACLE 9i-23ai » RMAN Fails With RMAN-20021: Database Not Set On Physical Standby
RMAN Fails With RMAN-20021: Database Not Set On Physical Standby
前段时间一套11.2.0.4环境standby db因为password file问题与primary db产生了一个月的Archivelog GAP,修复密码文件后Standby已同步跟上Primary db ,但是原备份软件在Standby上的备份任务从那天起一直失败报错RMAN-20021如下:
RMAN> crosscheck archivelog all;
released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=1987 device type=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of crosscheck command at 01/27/2023 16:38:58
RMAN-20021: database not set
即使是nocatalog模式,数据库本机也同样失败,其他一些RMAN命令同样报错,如backup archivelog;
解决方法
$ sqlplus / as sysdba SQL*Plus: Release 11.2.0.4.0 Production on Sat Jan 27 16:38:03 2023 Copyright (c) 1982, 2013, Oracle. All rights reserved. Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options SQL> alter system flush shared_pool; System altered. SQL> alter system flush buffer_cache; System altered. SQL>
RMAN退出重新登录后
$ rman target / Recovery Manager: Release 11.2.0.4.0 - Production on Sat Jan 27 16:40:01 2023 Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved. connected to target database: DB11G (DBID=349395754) RMAN> crosscheck archivelog all; using target database control file instead of recovery catalog allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=1987 device type=DISK validation succeeded for archived log archived log file name=/home/arch/1_4176_879726186.dbf RECID=240202 STAMP=1126541167 validation succeeded for archived log archived log file name=/home/arch/1_4177_879726186.dbf RECID=240203 STAMP=1126541167
上一篇: PostgreSQL explain解析(一): buffers
下一篇: 2022年年终总结
对不起,这篇文章暂时关闭评论。