ORA-20079: full resync from primary database is not done
来源:互联网 发布:淘宝市场调查问卷 编辑:程序博客网 时间:2024/06/05 03:51
在介绍ORA-20079前我们先简单介绍一下resync catalog:
Using the RESYNC CATALOG Command
Any structural changes to the database cause the control file and recovery catalog to become “out of synch.” The catalog will be synchronized automatically when a BACKUP or COPY command is issued with a connection to the catalog. However, this synchronization can cause a [B]delay[/B] in the backup operation.
在RMAN中使用catalog时,会使用同步命令来保证catalog与目标数据库的controlfile的內容一致。
通常,如果我们一直使用catalog来做backup or restore的话就不需要手工的做同步,因为我们发出的backup or restore命令完成后会自动同步catalog和controlfile中的內容,只有我们有时候用catalog,而有某些时候又不用catalog来做backup or restore的时候才需要发出 resync catalog的命令来手工做同步。oracle同步catalog时,会先建立个snapshot controlfile并且比较这个文件和catalog,完成比较后,oracle根据这个snapshot controlfile来同步catalog,并使它们保持一致。
公司的某套生产环境库为11.2.0.3RAC+DG(AIX),在备库上作备份。一次发现备份失败,报错如下:
RMAN> RMAN>ORA-20079: full resync from primary database is not donedoing automatic resync from primaryresyncing from database with DB_UNIQUE_NAME EGMMDBRMAN-00571: ===========================================================RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============RMAN-00571: ===========================================================RMAN-03002: failure of configure command at 03/25/2014 04:52:42RMAN-03014: implicit resync of recovery catalog failedRMAN-03009: failure of partial resync command on default channel at 03/25/2014 04:52:42ORA-17629: Cannot connect to the remote database serverORA-17627: ORA-00942: table or view does not exist
在mos上找到了几个处理方案,可供参考
After new files are added to primary, rman fails at Standby with ORA-20079: Full Resync From Primary Database Is Not Done (Doc ID 1604302.1)
RMAN-06613: Connect identifier for DB_UNIQUE_NAME not configured (Doc ID 1598653.1)
本文出自 “技术” 博客,请务必保留此出处http://589985.blog.51cto.com/1609992/1384352
0 0
- ORA-20079: full resync from primary database is not done
- ORA-16416: Switchover target is not synchronized with the primary
- Database log is full
- Could not allocate space for object because the PRIMARY filegroup is full
- Could not allocate space for object in database because the filegroup is full
- ORA-38706: Cannot turn on FLASHBACK DATABASE logging.ORA-38709: Recovery Area is not enabled.
- ORA-38706: Cannot turn on FLASHBACK DATABASE logging.ORA-38709: Recovery Area is not enabled.
- The log file for database '' is full
- ORA-19698: /opt/oradata/orclbj/redo01.log is from different database
- ORA-19698: /home/xxx/xxx/redo01.log is from different database
- ORA-16796: one or more properties could not be imported from the database [ID 358040.1]
- ORA-16796: one or more properties could not be imported from the database [ID 358040.1]
- RMAN-04006: error from auxiliary database: ORA-01034: ORACLE not available
- ORA-01507: database not mounted
- ORA-01507: database not mounted
- ORA-01507: database not mounted
- ORA-01103: database name 'LCRO' in control file is not 'DUMMY'
- ORA-01103: database name 'test' in control file is not 'standby'
- AIX账户密码不能重用和过期的解决
- 11.2.0.3.0 打PSU补丁--自动方式(p14727347_112030_AIX64-5L.zip )
- Why is "opatch auto" not patching my RAC database home?
- Error 12154 received logging on to the standby
- ORA-27300,ORA-27301,ORA-27302
- ORA-20079: full resync from primary database is not done
- LOG_ARCHIVE_CONFIG
- oracle 中带双下划线的参数如(*.__shared_pool_size=)
- oracle查看隐含参数脚本
- ASMM下查看shared_pool_size等内存大小
- ORA-01264: Unable to create logfile file name
- Solr查询语法总结
- PRCS-1007 : Server pool egapdb already exists
- poj(2431)(优先队列http://poj.org/problem?id=2431)