ORA-16072: a minimum of one standby database destination is required
2012-11-06 15:04
671 查看
今天在测试环境中弄DG的时候出现了ORA-16072: a minimum of one standby database destination is required的报错:
环境如下:OS :RHEL 5.6 X86_64 DB:11.2.0.3.2 (单机)
原来是一个DG环境,由于备库已经损坏了,现在需要删除现有环境中的DG,重新搭建一个新的DG环境。在主库上面删除DG相关的参数、redo与相关的物理文件的。启动主库时就报错。后台日志如下:
trace文件中的内容如下:
原因是由于原环境配置了FSFO,数据库在最大可性的模式下面,删除DG,需要修改数据库在最大性能下面。修改语法如下:
修改后数据库启动正常。
环境如下:OS :RHEL 5.6 X86_64 DB:11.2.0.3.2 (单机)
原来是一个DG环境,由于备库已经损坏了,现在需要删除现有环境中的DG,重新搭建一个新的DG环境。在主库上面删除DG相关的参数、redo与相关的物理文件的。启动主库时就报错。后台日志如下:
ARC0: Archival started LGWR: STARTING ARCH PROCESSES COMPLETE ARC0: STARTING ARCH PROCESSES LGWR: Primary database is in MAXIMUM AVAILABILITY mode LGWR: Destination LOG_ARCHIVE_DEST_1 is not serviced by LGWR LGWR: Minimum of 1 LGWR standby database required Errors in file /usr/app/oracle/diag/diag/rdbms/vcm01_b/vcm01/trace/vcm01_lgwr_2803.trc: ORA-16072: a minimum of one standby database destination is required
trace文件中的内容如下:
Trace file /usr/app/oracle/diag/diag/rdbms/vcm01_b/vcm01/trace/vcm01_lgwr_2803.trc Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options ORACLE_HOME = /usr/app/oracle/110203/v01 System name: Linux Node name: pekdc1-vcm-04 Release: 2.6.18-238.el5 Version: #1 SMP Thu Jan 13 15:51:15 EST 2011 Machine: x86_64 Instance name: vcm01 Redo thread mounted by this instance: 1 Oracle process number: 11 Unix process pid: 2803, image: oracle@pekdc1-vcm-04 (LGWR) *** 2012-11-06 09:23:30.058 *** SESSION ID:(2267.1) 2012-11-06 09:23:30.058 *** CLIENT ID:() 2012-11-06 09:23:30.058 *** SERVICE NAME:() 2012-11-06 09:23:30.058 *** MODULE NAME:() 2012-11-06 09:23:30.058 *** ACTION NAME:() 2012-11-06 09:23:30.058 Destination LOG_ARCHIVE_DEST_1 is not serviced by LGWR Standby database verification failed:16072 error 16072 detected in background process ORA-16072: a minimum of one standby database destination is required kjzduptcctx: Notifying DIAG for crash event ----- Abridged Call Stack Trace ----- ksedsts()+461<-kjzdssdmp()+267<-kjzduptcctx()+232<-kjzdicrshnfy()+53<-ksuitm()+1332<-ksbrdp()+3344<-opirip()+623<-opidrv()+603<-sou2o()+103<-opimai_real()+266<-ssthrdmain()+252<-main()+201<-__libc_start_main()+244<-_start()+36 ----- End of Abridged Call Stack Trace ----- *** 2012-11-06 09:23:30.166 LGWR (ospid: 2803): terminating the instance due to error 16072 ksuitm: waiting up to [5] seconds before killing DIAG(2783)
原因是由于原环境配置了FSFO,数据库在最大可性的模式下面,删除DG,需要修改数据库在最大性能下面。修改语法如下:
sqlplus / as sysdba SQL> startup mount SQL> alter database set standby to maximize performance; SQL> alter database open;
修改后数据库启动正常。
相关文章推荐
- ORA-16072: a minimum of one standby database destination is required
- ORA-16072: a minimum of one standby database destination is required
- ORA-16072: a minimum of one standby database destination is required
- ORA-16072: a minimum of one standby database destination is required
- ORA-16003: standby database is restricted to read-only access
- Client instance is standby database instead of primary
- 【Vegas原创】ORA-16040 standby destination archive log file is locked解决
- 【Vegas原创】ORA-16040 standby destination archive log file is locked解决
- 【Vegas原创】ORA-16040 standby destination archive log file is locked解决
- ORA-00313, ORA-00312, ORA-27037 in Standby Database [ID 601835.1]
- Oracle Data Guard ORA-16086: standby database does not contain available standby 处理方法
- 4000 ORA-16146: STANDBY DESTINATION C…
- Database '' is in warm standby. A warm-standby database is read-only.
- ORA-16447 Redo apply was not active at the target standby database
- How to grant access to SQL logins on a standby database when the guest user is disabled in SQL Serve
- ORA-16047: DGID mismatch between destination setting and standby
- ORA-10456: cannot open standby database; media recovery session may be in progress
- 不能解析EL表达式解决方案:The identifier [static] is not a valid Java identifier as required by section 1.19 of
- ORA-00313, ORA-00312, ORA-27037 in Standby Database [ID 601835.1]
- Oracle DG故障诊断案例一则:ORA-16047: DGID mismatch between destination setting and standby