通过GC创建dataguard备库失败一则(三)
file_dest
that are not known to the database. Use the RMAN command
CATALOG RECOVERY AREA to re-catalog any such files.
Dictionary check complete
Re-creating tempfile +DATA as +DATA/htdb7/tempfile/temp.304.821723767
Re-creating tempfile +DATA as +DATA/htdb7/tempfile/temp.305.821723767
Database Characterset is ZHS16GBK
No Resource Manager plan active
**********************************************************
WARNING: Files may exists in db_recovery_file_dest
that are not known to the database. Use the RMAN command
CATALOG RECOVERY AREA to re-catalog any such files.
If files cannot be cataloged, then manually delete them
using OS command.
One of the following events caused this:
1. A backup controlfile was restored.
2. A standby controlfile was restored.
3. The controlfile was re-created.
4. db_recovery_file_dest had previously been enabled and
then disabled.
**********************************************************
replication_dependency_tracking turned off (no async multimaster replication found)
Physical standby database opened for read only access.
Completed: alter database open
--查看dataguard环境环境正常
[oracle@hotel07 trace]$ dgmgrl sys/oracle123
DGMGRL for Linux: Version 11.2.0.2.0 - 64bit Production
Copyright (c) 2000, 2009,
Oracle. All rights reserved.
欢迎使用 DGMGRL, 要获取有关信息请键入 "help"。
已连接。
DGMGRL> show configuration
配置 - htdb4
保护模式: MaxAvailability
数据库:
htdb4 - 主数据库
htdb5 - 物理备用数据库
htdb6 - 物理备用数据库
htdb7 - 物理备用数据库
快速启动故障转移: DISABLED
配置状态:
SUCCESS
分析原因：
可能是由于创建备库时，正是主库业务比较繁忙的时候，而且主库的数据文件比较大，备份恢复的时间又比较长，造成主库的部分日志没有传输到从节点，从而造成恢复失败。所在做dataguard时尽量在主库业务不忙时进行，确保安全和避免一些错误发生。