Oracle Study之--Logical Standby日志应用错误案例
发表于：2024-11-23 作者：千家信息网编辑
千家信息网最后更新 2024年11月23日，Oracle Study之--Logical Standby日志应用错误案例系统环境：操作系统：RedHat EL54数据库： Oracle 11gR2一、错误现象：（在逻辑备库应用日志时）LOGMI
千家信息网最后更新 2024年11月23日Oracle Study之--Logical Standby日志应用错误案例
Oracle Study之--Logical Standby日志应用错误案例
系统环境：
操作系统：RedHat EL54
数据库： Oracle 11gR2
一、错误现象：（在逻辑备库应用日志时）
LOGMINER: session#=1 (Logical_Standby$), preparer MS02 pid=34 OS id=4241 sid=37 startedLOGSTDBY status: ORA-00604: error occurred at recursive SQL level 1ORA-01658: unable to create INITIAL extent for segment in tablespace LOGMNRTBSORA-06512: at "SYS.LOGMNR_KRVRDLUID3", line 1300ORA-06512: at line 1Errors in file /u01/app/oracle/diag/rdbms/bjdb/TestDB12/trace/TestDB12_lsp0_4228.trc:ORA-00604: error occurred at recursive SQL level 1ORA-01658: unable to create INITIAL extent for segment in tablespace LOGMNRTBSORA-06512: at "SYS.LOGMNR_KRVRDLUID3", line 1300ORA-06512: at line 1LOGMINER: session#=1 (Logical_Standby$), reader MS00 pid=32 OS id=4237 sid=43 stoppedLOGMINER: session#=1 (Logical_Standby$), builder MS01 pid=33 OS id=4239 sid=41 stoppedLOGMINER: session#=1 (Logical_Standby$), preparer MS02 pid=34 OS id=4241 sid=37 stopped^[[AThu Mar 12 05:01:49 2015Starting background process SMCOThu Mar 12 05:01:49 2015SMCO started with pid=31, OS id=4260查看logmnr应用：SYS@ TestDB12>select * from v$logstdby_stats;no rows selectedlogmnr没有任何动作。
二、分析问题原因
1、查看trace文件
oracle@bjsrv:/home/oracle> more /u01/app/oracle/diag/rdbms/bjdb/TestDB12/trace/TestDB12_lsp0_4228.trc
Trace file /u01/app/oracle/diag/rdbms/bjdb/TestDB12/trace/TestDB12_lsp0_4228.trcOracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit ProductionWith the Partitioning, Oracle Label Security, OLAP, Data Mining,Oracle Database Vault and Real Application Testing optionsORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1System name: LinuxNode name: bjsrvRelease: 2.6.18-194.el5Version: #1 SMP Tue Mar 16 21:52:39 EDT 2010Machine: x86_64Instance name: TestDB12Redo thread mounted by this instance: 1Oracle process number: 31Unix process pid: 4228, p_w_picpath: oracle@bjsrv (LSP0)*** 2015-03-12 04:58:11.426*** SESSION ID:(38.1) 2015-03-12 04:58:11.426*** CLIENT ID:() 2015-03-12 04:58:11.426*** SERVICE NAME:(SYS$BACKGROUND) 2015-03-12 04:58:11.426*** MODULE NAME:() 2015-03-12 04:58:11.426*** ACTION NAME:() 2015-03-12 04:58:11.426 knahcapplymain: encountered error=604*** 2015-03-12 04:58:11.426dbkedDefDump(): Starting a non-incident diagnostic dump (flags=0x0, level=0, mask=0x0)----- Error Stack Dump -----ORA-00604: error occurred at recursive SQL level 1ORA-01658: unable to create INITIAL extent for segment in tablespace LOGMNRTBSORA-06512: at "SYS.LOGMNR_KRVRDLUID3", line 1300ORA-06512: at line 1KNACDMP: *******************************************************KNACDMP: Dumping apply coordinator's context at 830931c0KNACDMP: Apply Engine # 0KNACDMP: Apply Engine name KNACDMP: Coordinator's Watermarks ------------------------------KNACDMP: Apply High Watermark = 00000014572d (SCN=0x0000.0014572d)KNACDMP: Apply Low Watermark = 00000014572d (SCN=0x0000.0014572d)KNACDMP: Recovery Low Watermark = (SCN=0x0000.00000000)KNACDMP: Fetch Low Watermark = (SCN=0x0000.00000000)KNACDMP: Fetch Low Watermark Time = 0KNACDMP: Oldest SCN = (SCN=0x0000.00000000)KNACDMP: Oldest XID = KNACDMP: Oldest Create Time = 0KNACDMP: Last replicant syncpoint SCN = 0x0000.00000000KNACDMP: Last syncpoint at primary SCN = 0x0000.00000000KNACDMP: First partition max pos = (SCN=0x0000.00000000)KNACDMP: Last partition max pos = (SCN=0x0000.00000000)KNACDMP: Last processed = 00000014572e (SCN=0x0000.0014572e)KNACDMP: Conservative pos = (SCN=0x0000.00000000)KNACDMP: Recovery start pos = (SCN=0x0000.00000000)KNACDMP: Recovery high watermark = (SCN=0x0000.00000000)KNACDMP: Spill LWM = (SCN=0x0000.00000000)KNACDMP: Spill LWM Create Time = 0KNACDMP: Coordinator's constants -------------------------------KNACDMP: number of apply slaves = 5KNACDMP: min number of apply slaves = 5KNACDMP: max number of apply slaves = 5KNACDMP: safety level (K) = 1KNACDMP: max txns in memory = 400KNACDMP: max constraints per table = 620KNACDMP: hash table size (in entries) = 10000000KNACDMP: Coordinator's intervals -------------------------------KNACDMP: syncpoint interval (ms) = 0KNACDMP: write low watermark interval(ms)= 1KNACDMP: Coordinator's timers/counters -------------------------KNACDMP: current time = 1426150690KNACDMP: low watermark timer = 0KNACDMP: syncpoint timer = 0KNACDMP: txnbufsize timer = 0KNACDMP: Coordinator's txn counts -------------------------KNACDMP: total txns applied = 0KNACDMP: number of unassigned comp txns = 0KNACDMP: number of unassigned incomp txns= 0KNACDMP: avg number of unassigned txns = 0.00KNACDMP: total applied at last plwm write= 0KNACDMP: apply prog. entries below plwm = 0KNACDMP: total unassigned lcrs = 0KNACDMP: Coordinator's State/Flags -----------------------------KNACDMP: Coordinator's State = KNACST_APPLY_UNTIL_ENDKNACDMP: Coordinator's Flags = 0x8000KNACDMP: Slave counts ------------------------------------------KNACDMP: number of reserved slaves = 1KNACDMP: number of admin slaves = 0KNACDMP: number of slaves in wait cmt = 0KNACDMP: number of slaves suspended = 0KNACDMP: number of safe slaves = 0KNACDMP: avg number of idle slaves = 0.00KNACDMP: number of slaves initializing = 0KNACDMP: number of slaves terminating = 0KNACDMP: Slave Lists -------------------------------------------KNACDMP: Dumping All Slaves :-Slave id = 0, State = 8, Flags = 0, Not Assigned 0 txns 0 lcrsSlave id = 1, State = 0, Flags = 0, Not Assigned 0 txns 0 lcrsSlave id = 2, State = 0, Flags = 0, Not Assigned 0 txns 0 lcrsSlave id = 3, State = 0, Flags = 0, Not Assigned 0 txns 0 lcrsSlave id = 4, State = 0, Flags = 0, Not Assigned 0 txns 0 lcrsSlave id = 5, State = 0, Flags = 0, Not Assigned 0 txns 0 lcrsKNACDMP: End dumping all slavesKNACDMP: syncdep slaves = { }KNACDMP: cont chunk slaves = { }KNACDMP: cont slaves = { }KNACDMP: exec txn slaves = { }KNACDMP: Active slaves (0) = { }KNACDMP: Idle slaves (5) = { 1 2 3 4 5 }KNACDMP: Txn Lists ---------------------------------------------KNACDMP: Dumping all txns :-KNACDMP: End dumping all txns.KNACDMP: Complete txns = { ** NO UNASS ** }KNACDMP: Unassigned txns = { }KNACDMP: *******************************************************Warning: Apply error received: ORA-26714: User Error encountered during apply process. Clearing.*** 2015-03-12 04:58:11.994knahcapplymain: encountered error=604*** 2015-03-12 04:58:11.994dbkedDefDump(): Starting a non-incident diagnostic dump (flags=0x0, level=0, mask=0x0)----- Error Stack Dump -----ORA-00604: error occurred at recursive SQL level 1ORA-01658: unable to create INITIAL extent for segment in tablespace LOGMNRTBSORA-06512: at "SYS.LOGMNR_KRVRDLUID3", line 1300ORA-06512: at line 1KNACDMP: *******************************************************KNACDMP: Dumping apply coordinator's context at 830931c0KNACDMP: Apply Engine # 0KNACDMP: Apply Engine name KNACDMP: Coordinator's Watermarks ------------------------------KNACDMP: Apply High Watermark = 00000014572d (SCN=0x0000.0014572d)KNACDMP: Apply Low Watermark = 00000014572d (SCN=0x0000.0014572d)KNACDMP: Recovery Low Watermark = (SCN=0x0000.00000000)KNACDMP: Fetch Low Watermark = (SCN=0x0000.00000000)KNACDMP: Fetch Low Watermark Time = 0KNACDMP: Oldest SCN = (SCN=0x0000.00000000)KNACDMP: Oldest XID = KNACDMP: Oldest Create Time = 0KNACDMP: Last replicant syncpoint SCN = 0x0000.00000000KNACDMP: Last syncpoint at primary SCN = 0x0000.00000000KNACDMP: First partition max pos = (SCN=0x0000.00000000)KNACDMP: Last partition max pos = (SCN=0x0000.00000000)KNACDMP: Last processed = 00000014572e (SCN=0x0000.0014572e)KNACDMP: Conservative pos = (SCN=0x0000.00000000)KNACDMP: Recovery start pos = (SCN=0x0000.00000000)KNACDMP: Recovery high watermark = (SCN=0x0000.00000000)KNACDMP: Spill LWM = (SCN=0x0000.00000000)KNACDMP: Spill LWM Create Time = 0KNACDMP: Coordinator's constants -------------------------------KNACDMP: number of apply slaves = 5KNACDMP: min number of apply slaves = 5KNACDMP: max number of apply slaves = 5KNACDMP: safety level (K) = 1KNACDMP: max txns in memory = 400KNACDMP: max constraints per table = 620KNACDMP: hash table size (in entries) = 10000000KNACDMP: Coordinator's intervals -------------------------------KNACDMP: syncpoint interval (ms) = 0KNACDMP: write low watermark interval(ms)= 1KNACDMP: Coordinator's timers/counters -------------------------KNACDMP: current time = 1426150691KNACDMP: low watermark timer = 0KNACDMP: syncpoint timer = 0KNACDMP: txnbufsize timer = 0KNACDMP: Coordinator's txn counts -------------------------KNACDMP: total txns applied = 0KNACDMP: number of unassigned comp txns = 0KNACDMP: number of unassigned incomp txns= 0KNACDMP: avg number of unassigned txns = 0.00KNACDMP: total applied at last plwm write= 0KNACDMP: apply prog. entries below plwm = 0KNACDMP: total unassigned lcrs = 0KNACDMP: Coordinator's State/Flags -----------------------------KNACDMP: Coordinator's State = KNACST_APPLY_UNTIL_ENDKNACDMP: Coordinator's Flags = 0x8200KNACDMP: Slave counts ------------------------------------------KNACDMP: number of reserved slaves = 1KNACDMP: number of admin slaves = 0KNACDMP: number of slaves in wait cmt = 0KNACDMP: number of slaves suspended = 0KNACDMP: number of safe slaves = 0KNACDMP: avg number of idle slaves = 0.00KNACDMP: number of slaves initializing = 0KNACDMP: number of slaves terminating = 0KNACDMP: Slave Lists -------------------------------------------KNACDMP: Dumping All Slaves :-Slave id = 0, State = 8, Flags = 0, Not Assigned 0 txns 0 lcrsSlave id = 1, State = 0, Flags = 0, Not Assigned 0 txns 0 lcrsSlave id = 2, State = 0, Flags = 0, Not Assigned 0 txns 0 lcrsSlave id = 3, State = 0, Flags = 0, Not Assigned 0 txns 0 lcrsSlave id = 4, State = 0, Flags = 0, Not Assigned 0 txns 0 lcrsSlave id = 5, State = 0, Flags = 0, Not Assigned 0 txns 0 lcrsKNACDMP: End dumping all slavesKNACDMP: syncdep slaves = { }KNACDMP: cont chunk slaves = { }KNACDMP: cont slaves = { }KNACDMP: exec txn slaves = { }KNACDMP: Active slaves (0) = { }KNACDMP: Idle slaves (5) = { 1 2 3 4 5 }KNACDMP: Txn Lists ---------------------------------------------KNACDMP: Dumping all txns :-KNACDMP: End dumping all txns.KNACDMP: Complete txns = { ** NO UNASS ** }KNACDMP: Unassigned txns = { }KNACDMP: *******************************************************Warning: Apply error received: ORA-26714: User Error encountered during apply process. Clearing.oracle@bjsrv:/home/oracle>2、查看tablespace信息
SYS@ TestDB12>select file_id,file_name,tablespace_name,bytes/1024/1024 from dba_data_files; FILE_ID FILE_NAME TABLESPACE_NAME BYTES/1024/1024---------- -------------------------------------------------- ------------------------------ --------------- 4 /u01/app/oracle/oradata/TestDB12/users01.dbf USERS 5 3 /u01/app/oracle/oradata/TestDB12/undotbs01.dbf UNDOTBS1 115 2 /u01/app/oracle/oradata/TestDB12/sysaux01.dbf SYSAUX 570 1 /u01/app/oracle/oradata/TestDB12/system01.dbf SYSTEM 730 5 /u01/app/oracle/oradata/TestDB12/example01.dbf EXAMPLE 345.625 6 /u01/app/oracle/oradata/TestDB12/logmnrtbs01.dbf LOGMNRTBS 1006 rows selected.
--作为logminer的应用表空间，"LOGMNRTBS"初始只分配了100M的size，估计在做sql apply时，空间不足，而不能分配extent。
三、解决方法
1、扩展"LOGMNRTBS" size
SYS@ TestDB12>alter database datafile 6 resize 500m;Database altered.SYS@ TestDB12>select file_id,file_name,tablespace_name,bytes/1024/1024 from dba_data_files; FILE_ID FILE_NAME TABLESPACE_NAME BYTES/1024/1024---------- -------------------------------------------------- ------------------------------ --------------- 4 /u01/app/oracle/oradata/TestDB12/users01.dbf USERS 5 3 /u01/app/oracle/oradata/TestDB12/undotbs01.dbf UNDOTBS1 115 2 /u01/app/oracle/oradata/TestDB12/sysaux01.dbf SYSAUX 570 1 /u01/app/oracle/oradata/TestDB12/system01.dbf SYSTEM 730 5 /u01/app/oracle/oradata/TestDB12/example01.dbf EXAMPLE 345.625 6 /u01/app/oracle/oradata/TestDB12/logmnrtbs01.dbf LOGMNRTBS 5006 rows selected.
四、在备库上做SQL APPLY
SYS@ TestDB12>alter database start logical standby apply immediate;
Database altered.
1、查看logmnr视图：
SYS@ TestDB12>select *from v$logstdby_stats;NAME VALUE---------------------------------------------------------------- ----------------------------------------------------------------logminer session id 1number of preparers 1number of appliers 5server processes in use 9maximum SGA for LCR cache (MB) 30maximum events recorded 10000preserve commit order TRUEtransaction consistency FULLrecord skipped errors Yrecord skipped DDLs Yrecord applied DDLs Nrecord unsupported operations Nrealtime apply Yapply delay (minutes) 0peak apply rate (bytes/sec) 15148888coordinator state IDLEcoordinator startup time 12-MAR-15coordinator uptime (seconds) 96txns received from logminer 1523txns assigned to apply 1523txns applied 1523txns discarded during restart 0large txns waiting to be assigned 0session restart SCN 1332344rolled back txns mined 501DDL txns mined 11CTAS txns mined 0bytes of redo mined 72757172bytes paged out 0pageout time (seconds) 0bytes checkpointed 133310checkpoint time (seconds) 0system idle time (seconds) 0standby redo logs mined 0archived logs mined 15gap fetched logs mined 7standby redo log reuse detected 0logfile open failures 0current logfile wait (seconds) 0total logfile wait (seconds) 0thread enable mined 0thread disable mined 0distinct txns in queue 043 rows selected.
查看告警日志：
RFS LogMiner: Registered logfile [/dsk4/arch_bj/arch_1_65_873495347.log] to LogMiner session id [1]Thu Mar 12 05:05:38 2015RFS[2]: Selected log 6 for thread 1 sequence 66 dbid -1483137996 branch 873495347Thu Mar 12 05:06:52 2015alter database start logical standby apply immediateALTER DATABASE START LOGICAL STANDBY APPLY (TestDB12)with optional partIMMEDIATEAttempt to start background Logical Standby processThu Mar 12 05:06:52 2015LSP0 started with pid=33, OS id=4277 Completed: alter database start logical standby apply immediateLOGMINER: Parameters summary for session# = 1LOGMINER: Number of processes = 3, Transaction Chunk Size = 201LOGMINER: Memory Size = 30M, Checkpoint interval = 150MLOGMINER: SpillScn 0, ResetLogScn 1234253LOGMINER: summary for session# = 1LOGMINER: StartScn: 1332344 (0x0000.00145478)LOGMINER: EndScn: 0 (0x0000.00000000)LOGMINER: HighConsumedScn: 1333037 (0x0000.0014572d)LOGMINER: session_flag: 0x1LOGMINER: Read buffers: 16Thu Mar 12 05:06:52 2015LOGMINER: session#=1 (Logical_Standby$), reader MS00 pid=34 OS id=4279 sid=40 startedThu Mar 12 05:06:52 2015LOGMINER: session#=1 (Logical_Standby$), builder MS01 pid=35 OS id=4281 sid=44 startedThu Mar 12 05:06:53 2015LOGMINER: session#=1 (Logical_Standby$), preparer MS02 pid=36 OS id=4283 sid=46 startedLOGMINER: Turning ON Log Auto DeleteLOGMINER: Begin mining logfile during dictionary load for session 1 thread 1 sequence 51, /dsk4/arch_bj/arch_1_51_873495347.logThu Mar 12 05:07:02 2015Thread 1 advanced to log sequence 7 (LGWR switch) Current log# 1 seq# 7 mem# 0: /dsk2/oradata/bjdb/redo01b.log Current log# 1 seq# 7 mem# 1: /dsk1/oradata/bjdb/redo01a.logThu Mar 12 05:07:04 2015Time drift detected. Please check VKTM trace file for more details.Thu Mar 12 05:07:05 2015Archived Log entry 6 added for thread 1 sequence 6 ID 0x38edae0f dest 1:Thread 1 advanced to log sequence 8 (LGWR switch) Current log# 2 seq# 8 mem# 0: /dsk2/oradata/bjdb/redo02b.log Current log# 2 seq# 8 mem# 1: /dsk1/oradata/bjdb/redo02a.logThu Mar 12 05:07:14 2015Archived Log entry 7 added for thread 1 sequence 7 ID 0x38edae0f dest 1:Thu Mar 12 05:07:18 2015Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TAB$ have been marked unusableSome indexes or index [sub]partitions of table SYSTEM.LOGMNR_TS$ have been marked unusableSome indexes or index [sub]partitions of table SYSTEM.LOGMNR_OBJ$ have been marked unusableSome indexes or index [sub]partitions of table SYSTEM.LOGMNR_IND$ have been marked unusableSome indexes or index [sub]partitions of table SYSTEM.LOGMNR_ICOL$ have been marked unusableSome indexes or index [sub]partitions of table SYSTEM.LOGMNR_COL$ have been marked unusableSome indexes or index [sub]partitions of table SYSTEM.LOGMNR_USER$ have been marked unusableSome indexes or index [sub]partitions of table SYSTEM.LOGMNR_CDEF$ have been marked unusableSome indexes or index [sub]partitions of table SYSTEM.LOGMNR_CCOL$ have been marked unusableSome indexes or index [sub]partitions of table SYSTEM.LOGMNR_LOB$ have been marked unusableSome indexes or index [sub]partitions of table SYSTEM.LOGMNR_PROPS$ have been marked unusableSome indexes or index [sub]partitions of table SYSTEM.LOGMNR_ENC$ have been marked unusableSome indexes or index [sub]partitions of table SYSTEM.LOGMNR_COLTYPE$ have been marked unusableSome indexes or index [sub]partitions of table SYSTEM.LOGMNR_SUBCOLTYPE$ have been marked unusableSome indexes or index [sub]partitions of table SYSTEM.LOGMNR_ATTRCOL$ have been marked unusableSome indexes or index [sub]partitions of table SYSTEM.LOGMNR_TYPE$ have been marked unusableSome indexes or index [sub]partitions of table SYSTEM.LOGMNR_ATTRIBUTE$ have been marked unusableSome indexes or index [sub]partitions of table SYSTEM.LOGMNR_NTAB$ have been marked unusableSome indexes or index [sub]partitions of table SYSTEM.LOGMNR_REFCON$ have been marked unusableSome indexes or index [sub]partitions of table SYSTEM.LOGMNR_OPQTYPE$ have been marked unusableSome indexes or index [sub]partitions of table SYSTEM.LOGMNR_KOPM$ have been marked unusableSome indexes or index [sub]partitions of table SYSTEM.LOGMNR_PARTOBJ$ have been marked unusableSome indexes or index [sub]partitions of table SYSTEM.LOGMNR_TABPART$ have been marked unusableSome indexes or index [sub]partitions of table SYSTEM.LOGMNR_INDPART$ have been marked unusableSome indexes or index [sub]partitions of table SYSTEM.LOGMNR_TABSUBPART$ have been marked unusableSome indexes or index [sub]partitions of table SYSTEM.LOGMNR_INDSUBPART$ have been marked unusableSome indexes or index [sub]partitions of table SYSTEM.LOGMNR_TABCOMPART$ have been marked unusableSome indexes or index [sub]partitions of table SYSTEM.LOGMNR_INDCOMPART$ have been marked unusableSome indexes or index [sub]partitions of table SYSTEM.LOGMNR_LOBFRAG$ have been marked unusableSome indexes or index [sub]partitions of table SYSTEM.LOGMNR_LOGMNR_BUILDLOG have been marked unusableSome indexes or index [sub]partitions of table SYSTEM.LOGMNR_SEED$ have been marked unusableSome indexes or index [sub]partitions of table SYSTEM.LOGMNR_DICTIONARY$ have been marked unusableIndexes of table SYSTEM.LOGMNR_ATTRCOL$ have been rebuilt and are now usableIndexes of table SYSTEM.LOGMNR_ATTRIBUTE$ have been rebuilt and are now usableIndexes of table SYSTEM.LOGMNR_CCOL$ have been rebuilt and are now usableIndexes of table SYSTEM.LOGMNR_CDEF$ have been rebuilt and are now usableIndexes of table SYSTEM.LOGMNR_COL$ have been rebuilt and are now usableIndexes of table SYSTEM.LOGMNR_COLTYPE$ have been rebuilt and are now usableIndexes of table SYSTEM.LOGMNR_DICTIONARY$ have been rebuilt and are now usableIndexes of table SYSTEM.LOGMNR_ENC$ have been rebuilt and are now usableIndexes of table SYSTEM.LOGMNR_ICOL$ have been rebuilt and are now usableIndexes of table SYSTEM.LOGMNR_IND$ have been rebuilt and are now usableIndexes of table SYSTEM.LOGMNR_INDCOMPART$ have been rebuilt and are now usableIndexes of table SYSTEM.LOGMNR_INDPART$ have been rebuilt and are now usableIndexes of table SYSTEM.LOGMNR_INDSUBPART$ have been rebuilt and are now usableIndexes of table SYSTEM.LOGMNR_KOPM$ have been rebuilt and are now usableIndexes of table SYSTEM.LOGMNR_LOB$ have been rebuilt and are now usableIndexes of table SYSTEM.LOGMNR_LOBFRAG$ have been rebuilt and are now usableIndexes of table SYSTEM.LOGMNR_LOGMNR_BUILDLOG have been rebuilt and are now usableIndexes of table SYSTEM.LOGMNR_NTAB$ have been rebuilt and are now usableIndexes of table SYSTEM.LOGMNR_OBJ$ have been rebuilt and are now usableIndexes of table SYSTEM.LOGMNR_OPQTYPE$ have been rebuilt and are now usableIndexes of table SYSTEM.LOGMNR_PARTOBJ$ have been rebuilt and are now usableIndexes of table SYSTEM.LOGMNR_PROPS$ have been rebuilt and are now usableIndexes of table SYSTEM.LOGMNR_REFCON$ have been rebuilt and are now usableIndexes of table SYSTEM.LOGMNR_SEED$ have been rebuilt and are now usableIndexes of table SYSTEM.LOGMNR_SUBCOLTYPE$ have been rebuilt and are now usableIndexes of table SYSTEM.LOGMNR_TAB$ have been rebuilt and are now usableIndexes of table SYSTEM.LOGMNR_TABCOMPART$ have been rebuilt and are now usableIndexes of table SYSTEM.LOGMNR_TABPART$ have been rebuilt and are now usableIndexes of table SYSTEM.LOGMNR_TABSUBPART$ have been rebuilt and are now usableIndexes of table SYSTEM.LOGMNR_TS$ have been rebuilt and are now usableIndexes of table SYSTEM.LOGMNR_TYPE$ have been rebuilt and are now usableIndexes of table SYSTEM.LOGMNR_USER$ have been rebuilt and are now usableThu Mar 12 05:07:30 2015Thread 1 advanced to log sequence 9 (LGWR switch) Current log# 3 seq# 9 mem# 0: /dsk2/oradata/bjdb/redo03b.log Current log# 3 seq# 9 mem# 1: /dsk1/oradata/bjdb/redo03a.logThu Mar 12 05:07:31 2015Archived Log entry 8 added for thread 1 sequence 8 ID 0x38edae0f dest 1:Thu Mar 12 05:07:38 2015LOGMINER: End mining logfiles during dictionary load for session 1Thu Mar 12 05:07:38 2015LSP2 started with pid=37, OS id=4286 Thu Mar 12 05:07:40 2015LOGMINER: Turning ON Log Auto DeleteLOGMINER: Begin mining logfile during commit scan for session 1 thread 1 sequence 51, /dsk4/arch_bj/arch_1_51_873495347.logLOGMINER: End mining logfile during commit scan for session 1 thread 1 sequence 51, /dsk4/arch_bj/arch_1_51_873495347.logLOGMINER: Begin mining logfile during commit scan for session 1 thread 1 sequence 52, /dsk4/arch_bj/arch_1_52_873495347.logLOGMINER: End mining logfiles during commit scan for session 1LOGMINER: Turning ON Log Auto DeleteLOGMINER: Begin mining logfile for session 1 thread 1 sequence 51, /dsk4/arch_bj/arch_1_51_873495347.logLOGMINER: End mining logfile for session 1 thread 1 sequence 51, /dsk4/arch_bj/arch_1_51_873495347.logLOGMINER: Begin mining logfile for session 1 thread 1 sequence 52, /dsk4/arch_bj/arch_1_52_873495347.logLOGMINER: End mining logfile for session 1 thread 1 sequence 52, /dsk4/arch_bj/arch_1_52_873495347.logLOGMINER: Begin mining logfile for session 1 thread 1 sequence 53, /dsk4/arch_bj/arch_1_53_873495347.logLOGMINER: End mining logfile for session 1 thread 1 sequence 53, /dsk4/arch_bj/arch_1_53_873495347.logLOGMINER: Begin mining logfile for session 1 thread 1 sequence 54, /dsk4/arch_bj/arch_1_54_873495347.logThu Mar 12 05:07:42 2015LOGSTDBY Analyzer process AS00 started with server id=0 pid=37 OS id=4289Thu Mar 12 05:07:42 2015LOGSTDBY Apply process AS01 started with server id=1 pid=38 OS id=4291Thu Mar 12 05:07:43 2015LOGSTDBY Apply process AS03 started with server id=3 pid=40 OS id=4295Thu Mar 12 05:07:43 2015LOGSTDBY Apply process AS05 started with server id=5 pid=42 OS id=4299Thu Mar 12 05:07:43 2015LOGSTDBY Apply process AS04 started with server id=4 pid=41 OS id=4297Thu Mar 12 05:07:43 2015LOGSTDBY Apply process AS02 started with server id=2 pid=39 OS id=4293LOGMINER: End mining logfile for session 1 thread 1 sequence 54, /dsk4/arch_bj/arch_1_54_873495347.logLOGMINER: Begin mining logfile for session 1 thread 1 sequence 55, /dsk4/arch_bj/arch_1_55_873495347.logLOGMINER: End mining logfile for session 1 thread 1 sequence 55, /dsk4/arch_bj/arch_1_55_873495347.logLOGMINER: Begin mining logfile for session 1 thread 1 sequence 56, /dsk4/arch_bj/arch_1_56_873495347.logLOGMINER: End mining logfile for session 1 thread 1 sequence 56, /dsk4/arch_bj/arch_1_56_873495347.logLOGMINER: Begin mining logfile for session 1 thread 1 sequence 57, /dsk4/arch_bj/arch_1_57_873495347.logLOGMINER: End mining logfile for session 1 thread 1 sequence 57, /dsk4/arch_bj/arch_1_57_873495347.logLOGMINER: Begin mining logfile for session 1 thread 1 sequence 58, /dsk4/arch_bj/arch_1_58_873495347.logLOGMINER: End mining logfile for session 1 thread 1 sequence 58, /dsk4/arch_bj/arch_1_58_873495347.logLOGMINER: Begin mining logfile for session 1 thread 1 sequence 59, /dsk4/arch_bj/arch_1_59_873495347.logThu Mar 12 05:07:55 2015LOGMINER: End mining logfile for session 1 thread 1 sequence 59, /dsk4/arch_bj/arch_1_59_873495347.logLOGMINER: Begin mining logfile for session 1 thread 1 sequence 60, /dsk4/arch_bj/arch_1_60_873495347.logLOGMINER: End mining logfile for session 1 thread 1 sequence 60, /dsk4/arch_bj/arch_1_60_873495347.logLOGMINER: Begin mining logfile for session 1 thread 1 sequence 61, /dsk4/arch_bj/arch_1_61_873495347.logLOGMINER: End mining logfile for session 1 thread 1 sequence 61, /dsk4/arch_bj/arch_1_61_873495347.logLOGMINER: Begin mining logfile for session 1 thread 1 sequence 62, /dsk4/arch_bj/arch_1_62_873495347.logLOGMINER: End mining logfile for session 1 thread 1 sequence 62, /dsk4/arch_bj/arch_1_62_873495347.logLOGMINER: Begin mining logfile for session 1 thread 1 sequence 63, /dsk4/arch_bj/arch_1_63_873495347.logLOGMINER: End mining logfile for session 1 thread 1 sequence 63, /dsk4/arch_bj/arch_1_63_873495347.logLOGMINER: Begin mining logfile for session 1 thread 1 sequence 64, /dsk4/arch_bj/arch_1_64_873495347.logLOGMINER: End mining logfile for session 1 thread 1 sequence 64, /dsk4/arch_bj/arch_1_64_873495347.logLOGMINER: Begin mining logfile for session 1 thread 1 sequence 65, /dsk4/arch_bj/arch_1_65_873495347.logLOGMINER: End mining logfile for session 1 thread 1 sequence 65, /dsk4/arch_bj/arch_1_65_873495347.logLOGMINER: Begin mining logfile for session 1 thread 1 sequence 66, /dsk1/oradata/bjdb/std_redo02.log
--从告警日志可以看出，logmnr已经开始对日志进行挖掘，并开始做SQL APPLY.
五、查看数据库同步信息
主库：
sys@TESTDB12>select count(*) from scott.emp1;
COUNT(*)
----------
120
备库：
SYS@ TestDB12>select count(*) from scott.emp1;
COUNT(*)
----------
120
此时主库和备库数据已经同步！
日志
应用
数据
错误
信息
数据库
空间
系统
分配
同步
案例
操作系统
动作
原因
文件
方法
环境
现象
视图
逻辑
数据库的安全要保护哪些东西
数据库安全各自的含义是什么
生产安全数据库录入
数据库的安全性及管理
数据库安全策略包含哪些
海淀数据库安全审计系统
建立农村房屋安全信息数据库
易用的数据库客户端支持安全管理
连接数据库失败ssl安全错误
数据库的锁怎样保障安全
两台电脑公用一个数据库怎么设置
数据库设置主键有依据吗
嵌入式软件开发应用
如何让网络安全生根
深圳手机应用软件开发费用多少
数据库代做大作哟儿
初三网络安全的利弊
安徽交友软件开发报价
网络安全增强政治安全意识
数据库插入整行
数据库填补
青云数据库
国家网络安全周公众号
我的世界国际联机必须要服务器吗
网络安全组织
湖州java软件开发项目
软件开发制度包括
网络安全有哪些性质
幼儿园网络安全实施方案
敏捷软件开发 mobi
软件开发增值税免税吗
csgo你不能在安全服务器商
学信网文献数据库
服务器8m支持多大访问量
pc互联网时代科技
数据库公开教学
合肥立思行互联网科技有限公司
云锁可以批量管理服务器吗
嘉定区一站式网络技术均价
多升金网络技术科技有限公司
