设为首页 收藏本站
查看: 382|回复: 0

[经验分享] Oracle DataGuard 之--Physical DG转换Logical DG

[复制链接]

尚未签到

发表于 2018-9-12 11:14:12 | 显示全部楼层 |阅读模式
alter database start logical standby apply immediate  
ORA-16239 signalled during: alter database start logical standby apply immediate...
  
Mon Nov 04 16:50:55 2013
  
alter database add standby logfile
  
'/dsk1/oradata/gz/std_redo01a.log' size 50m
  
Completed: alter database add standby logfile
  
'/dsk1/oradata/gz/std_redo01a.log' size 50m
  
Mon Nov 04 16:51:11 2013
  
alter database add standby logfile
  
'/dsk1/oradata/gz/std_redo02a.log' size 50m
  
Completed: alter database add standby logfile
  
'/dsk1/oradata/gz/std_redo02a.log' size 50m
  
Mon Nov 04 16:51:26 2013
  
alter database add standby logfile
  
'/dsk1/oradata/gz/std_redo03a.log' size 50m
  
Completed: alter database add standby logfile
  
'/dsk1/oradata/gz/std_redo03a.log' size 50m
  
Mon Nov 04 16:51:44 2013
  
alter database add standby logfile
  
'/dsk1/oradata/gz/std_redo04a.log' size 50m
  
Completed: alter database add standby logfile
  
'/dsk1/oradata/gz/std_redo04a.log' size 50m
  
alter database start logical standby apply immediate
  
LOGSTDBY: Creating new session for dbid 242121299 starting at scn 0x0000.00000000
  
LOGSTDBY: Created session of id 1
  
LOGSTDBY: Attempting to pre-register dictionary build logfiles
  
LOGMINER: Error 308 encountered, failed to read  logfile arch_1_57_830282966.log
  
LOGMINER: Encountered error 1291 while adding logfile arch_1_57_830282966.log to session 1
  
LOGSTDBY: Unable to register recovery logfiles, will resend
  
ALTER DATABASE START LOGICAL STANDBY APPLY (gz)
  
with optional part
  
IMMEDIATE
  
Attempt to start background Logical Standby process
  
Mon Nov 04 16:51:51 2013
  
LSP0 started with pid=27, OS id=4433
  
Completed: alter database start logical standby apply immediate
  
LOGMINER: Parameters summary for session# = 1
  
LOGMINER: Number of processes = 3, Transaction Chunk Size = 201
  
LOGMINER: Memory Size = 30M, Checkpoint interval = 150M
  
LOGMINER: SpillScn 0, ResetLogScn 0
  
Mon Nov 04 16:52:03 2013
  
RFS[6]: Opened log for thread 1 sequence 57 dbid 242121299 branch 830282966
  
Mon Nov 04 16:52:03 2013
  
RFS[7]: Assigned to RFS process 4435
  
RFS[7]: Identified database type as 'logical standby': Client is ARCH pid 4792
  
RFS[7]: Opened log for thread 1 sequence 58 dbid 242121299 branch 830282966
  
Mon Nov 04 16:52:04 2013
  
LOGMINER: summary for session# = 1
  
LOGMINER: StartScn: 1022094 (0x0000.000f988e)
  
LOGMINER: EndScn: 0 (0x0000.00000000)
  
LOGMINER: HighConsumedScn: 1022854 (0x0000.000f9b86)
  
LOGMINER: session_flag 0x1
  
RFS LogMiner: Registered logfile [/dsk4/arch_gz/arch_1_58_830282966.log] to LogMiner session id [1]
  
RFS[7]: Opened log for thread 1 sequence 59 dbid 242121299 branch 830282966
  
RFS LogMiner: Registered logfile [/dsk4/arch_gz/arch_1_57_830282966.log] to LogMiner session id [1]
  
RFS LogMiner: Registered logfile [/dsk4/arch_gz/arch_1_59_830282966.log] to LogMiner session id [1]
  
RFS[6]: Opened log for thread 1 sequence 60 dbid 242121299 branch 830282966
  
Mon Nov 04 16:52:04 2013
  
LOGMINER: session#=1, reader MS00 pid=30 OS id=4437 sid=39 started
  
RFS LogMiner: Registered logfile [/dsk4/arch_gz/arch_1_60_830282966.log] to LogMiner session id [1]
  
RFS LogMiner: RFS id [4423] assigned as thread [1] PING handler
  
Mon Nov 04 16:52:04 2013
  
LOGMINER: session#=1, builder MS01 pid=31 OS id=4439 sid=37 started
  
Mon Nov 04 16:52:04 2013
  
LOGMINER: session#=1, preparer MS02 pid=32 OS id=4441 sid=40 started
  
LOGMINER: Turning ON Log Auto Delete
  
LOGMINER: Begin mining logfile during dictionary load for session 1 thread 1 sequence 57, /dsk4/arch_gz/arch_1_57_830282966.log
  
Mon Nov 04 16:52:11 2013
  
Thread 1 advanced to log sequence 3 (LGWR switch)
  
  Current log# 3 seq# 3 mem# 0: /dsk1/oradata/gz/redo03a.log
  
  Current log# 3 seq# 3 mem# 1: /dsk2/oradata/gz/redo03b.log
  
Mon Nov 04 16:52:13 2013
  
Archived Log entry 2 added for thread 1 sequence 2 ID 0xb284e791 dest 1:
  
Thread 1 advanced to log sequence 4 (LGWR switch)
  
  Current log# 1 seq# 4 mem# 0: /dsk1/oradata/gz/redo01a.log
  
  Current log# 1 seq# 4 mem# 1: /dsk2/oradata/gz/redo01b.log
  
Mon Nov 04 16:52:20 2013
  
Archived Log entry 3 added for thread 1 sequence 3 ID 0xb284e791 dest 1:
  
Mon Nov 04 16:52:21 2013
  
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TAB$ have been marked unusable
  
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TS$ have been marked unusable
  
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_OBJ$ have been marked unusable
  
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_IND$ have been marked unusable
  
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_ICOL$ have been marked unusable
  
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_COL$ have been marked unusable
  
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_USER$ have been marked unusable
  
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_CDEF$ have been marked unusable
  
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_CCOL$ have been marked unusable
  
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_LOB$ have been marked unusable
  
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_PROPS$ have been marked unusable
  
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_ENC$ have been marked unusable
  
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_COLTYPE$ have been marked unusable
  
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_SUBCOLTYPE$ have been marked unusable
  
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_ATTRCOL$ have been marked unusable
  
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TYPE$ have been marked unusable
  
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_ATTRIBUTE$ have been marked unusable
  
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_NTAB$ have been marked unusable
  
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_REFCON$ have been marked unusable
  
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_OPQTYPE$ have been marked unusable
  
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_KOPM$ have been marked unusable
  
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_PARTOBJ$ have been marked unusable
  
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TABPART$ have been marked unusable
  
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_INDPART$ have been marked unusable
  
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TABSUBPART$ have been marked unusable
  
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_INDSUBPART$ have been marked unusable
  
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TABCOMPART$ have been marked unusable
  
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_INDCOMPART$ have been marked unusable
  
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_LOBFRAG$ have been marked unusable
  
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_LOGMNR_BUILDLOG have been marked unusable
  
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_SEED$ have been marked unusable
  
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_DICTIONARY$ have been marked unusable
  
Indexes of table  SYSTEM.LOGMNR_ATTRCOL$ have been rebuilt and are now usable
  
Indexes of table  SYSTEM.LOGMNR_ATTRIBUTE$ have been rebuilt and are now usable
  
Indexes of table  SYSTEM.LOGMNR_CCOL$ have been rebuilt and are now usable
  
Indexes of table  SYSTEM.LOGMNR_CDEF$ have been rebuilt and are now usable
  
Indexes of table  SYSTEM.LOGMNR_COL$ have been rebuilt and are now usable
  
Indexes of table  SYSTEM.LOGMNR_COLTYPE$ have been rebuilt and are now usable
  
Indexes of table  SYSTEM.LOGMNR_DICTIONARY$ have been rebuilt and are now usable
  
Indexes of table  SYSTEM.LOGMNR_ENC$ have been rebuilt and are now usable
  
Indexes of table  SYSTEM.LOGMNR_ICOL$ have been rebuilt and are now usable
  
Indexes of table  SYSTEM.LOGMNR_IND$ have been rebuilt and are now usable
  
Indexes of table  SYSTEM.LOGMNR_INDCOMPART$ have been rebuilt and are now usable
  
Indexes of table  SYSTEM.LOGMNR_INDPART$ have been rebuilt and are now usable
  
Indexes of table  SYSTEM.LOGMNR_INDSUBPART$ have been rebuilt and are now usable
  
Indexes of table  SYSTEM.LOGMNR_KOPM$ have been rebuilt and are now usable
  
Indexes of table  SYSTEM.LOGMNR_LOB$ have been rebuilt and are now usable
  
Indexes of table  SYSTEM.LOGMNR_LOBFRAG$ have been rebuilt and are now usable
  
Indexes of table  SYSTEM.LOGMNR_LOGMNR_BUILDLOG have been rebuilt and are now usable
  
Indexes of table  SYSTEM.LOGMNR_NTAB$ have been rebuilt and are now usable
  
Indexes of table  SYSTEM.LOGMNR_OBJ$ have been rebuilt and are now usable
  
Indexes of table  SYSTEM.LOGMNR_OPQTYPE$ have been rebuilt and are now usable
  
Indexes of table  SYSTEM.LOGMNR_PARTOBJ$ have been rebuilt and are now usable
  
Indexes of table  SYSTEM.LOGMNR_PROPS$ have been rebuilt and are now usable
  
Indexes of table  SYSTEM.LOGMNR_REFCON$ have been rebuilt and are now usable
  
Indexes of table  SYSTEM.LOGMNR_SEED$ have been rebuilt and are now usable
  
Indexes of table  SYSTEM.LOGMNR_SUBCOLTYPE$ have been rebuilt and are now usable
  
Indexes of table  SYSTEM.LOGMNR_TAB$ have been rebuilt and are now usable
  
Indexes of table  SYSTEM.LOGMNR_TABCOMPART$ have been rebuilt and are now usable
  
Indexes of table  SYSTEM.LOGMNR_TABPART$ have been rebuilt and are now usable
  
Indexes of table  SYSTEM.LOGMNR_TABSUBPART$ have been rebuilt and are now usable
  
Indexes of table  SYSTEM.LOGMNR_TS$ have been rebuilt and are now usable
  
Mon Nov 04 16:52:24 2013
  
Thread 1 cannot allocate new log, sequence 5
  
Checkpoint not complete
  
  Current log# 1 seq# 4 mem# 0: /dsk1/oradata/gz/redo01a.log
  
  Current log# 1 seq# 4 mem# 1: /dsk2/oradata/gz/redo01b.log
  
Indexes of table  SYSTEM.LOGMNR_TYPE$ have been rebuilt and are now usable
  
Indexes of table  SYSTEM.LOGMNR_USER$ have been rebuilt and are now usable
  
Thread 1 advanced to log sequence 5 (LGWR switch)
  
  Current log# 2 seq# 5 mem# 0: /dsk1/oradata/gz/redo02a.log
  
  Current log# 2 seq# 5 mem# 1: /dsk2/oradata/gz/redo02b.log
  
Mon Nov 04 16:52:28 2013
  
Archived Log entry 4 added for thread 1 sequence 4 ID 0xb284e791 dest 1:
  
Mon Nov 04 16:52:37 2013
  
Starting background process SMCO
  
Mon Nov 04 16:52:37 2013
  
SMCO started with pid=33, OS id=4445
  
Mon Nov 04 16:52:52 2013
  
LOGMINER: End mining logfiles during dictionary load for session 1
  
Mon Nov 04 16:52:53 2013
  
LSP2 started with pid=35, OS id=4449
  
Mon Nov 04 16:52:54 2013
  
LOGMINER: Turning ON Log Auto Delete
  
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 57, /dsk4/arch_gz/arch_1_57_830282966.log
  
Mon Nov 04 16:52:54 2013
  
LOGSTDBY Analyzer process AS00 started with server id=0 pid=36 OS id=4451
  
LOGMINER: End   mining logfile for session 1 thread 1 sequence 57, /dsk4/arch_gz/arch_1_57_830282966.log
  
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 58, /dsk4/arch_gz/arch_1_58_830



运维网声明 1、欢迎大家加入本站运维交流群:群②:261659950 群⑤:202807635 群⑦870801961 群⑧679858003
2、本站所有主题由该帖子作者发表,该帖子作者与运维网享有帖子相关版权
3、所有作品的著作权均归原作者享有,请您和我们一样尊重他人的著作权等合法权益。如果您对作品感到满意,请购买正版
4、禁止制作、复制、发布和传播具有反动、淫秽、色情、暴力、凶杀等内容的信息,一经发现立即删除。若您因此触犯法律,一切后果自负,我们对此不承担任何责任
5、所有资源均系网友上传或者通过网络收集,我们仅提供一个展示、介绍、观摩学习的平台,我们不对其内容的准确性、可靠性、正当性、安全性、合法性等负责,亦不承担任何法律责任
6、所有作品仅供您个人学习、研究或欣赏,不得用于商业或者其他用途,否则,一切后果均由您自己承担,我们对此不承担任何法律责任
7、如涉及侵犯版权等问题,请您及时通知我们,我们将立即采取措施予以解决
8、联系人Email:admin@iyunv.com 网址:www.yunweiku.com

所有资源均系网友上传或者通过网络收集,我们仅提供一个展示、介绍、观摩学习的平台,我们不对其承担任何法律责任,如涉及侵犯版权等问题,请您及时通知我们,我们将立即处理,联系人Email:kefu@iyunv.com,QQ:1061981298 本贴地址:https://www.iyunv.com/thread-573289-1-1.html 上篇帖子: oracle监控语句 下篇帖子: 如何查看ORACLE的隐含参数
您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

扫码加入运维网微信交流群X

扫码加入运维网微信交流群

扫描二维码加入运维网微信交流群,最新一手资源尽在官方微信交流群!快快加入我们吧...

扫描微信二维码查看详情

客服E-mail:kefu@iyunv.com 客服QQ:1061981298


QQ群⑦:运维网交流群⑦ QQ群⑧:运维网交流群⑧ k8s群:运维网kubernetes交流群


提醒:禁止发布任何违反国家法律、法规的言论与图片等内容;本站内容均来自个人观点与网络等信息,非本站认同之观点.


本站大部分资源是网友从网上搜集分享而来,其版权均归原作者及其网站所有,我们尊重他人的合法权益,如有内容侵犯您的合法权益,请及时与我们联系进行核实删除!



合作伙伴: 青云cloud

快速回复 返回顶部 返回列表