Home » Server Options » Data Guard » applied_scn is lagging behind too much (ODS) (11g. 11.2.0.3, solaris 10)
applied_scn is lagging behind too much (ODS) [message #603501] Tue, 17 December 2013 01:04
ishika_20
Messages: 339
Registered: December 2006
Location: delhi
Senior Member
Dear All,

OLTP & ODS of UAT is configured on same server. Now, there are gaps between the applied scn and newest scn.
In alert log file, it's showing "REGISTERED LOGFILE". Does it may be due to network issue?

Below are the details -

UATODS										
										
select applied_thread#,applied_scn,to_char(applied_time,'dd/mm/yyyy hh12:mi:ss'),newest_scn,applied_sequence#,newest_sequence# from DBA_LOGSTDBY_PROGRESS;										
										
APPLIED_THREAD#	APPLIED_SCN	TO_CHAR(APPLIED_TIME,'DD/MM/YY	NEWEST_SCN	APPLIED_SEQUENCE#	NEWEST_SEQUENCE#					
1	8262395095418	06/12/13 09:24	8262399332388	34462	35512					
										
										
select * from dba_logstdby_events order by event_time desc;										
										
EVENT_TIME	EVENT_TIMESTAMP	START_SCN	CURRENT_SCN	COMMIT_SCN	XIDUSN	XIDSLT	XIDSQN	EVENT	STATUS_CODE	STATUS
11/12/13 09:08	11-DEC-13 09.08.23.010698 AM	8262395034181	8262395034186	8262395034192	10	23	524668	<CLOB>	16205	ORA-16205: DDL skipped due to skip setting
11/12/13 09:08	11-DEC-13 09.08.22.818513 AM	8262395033789	8262395033793	8262395033796	5	0	616801	<CLOB>	16205	ORA-16205: DDL skipped due to skip setting
										



				
				
UATOLTP				
				
select sequence#, archived, resetlogs_time, first_time, next_time from v$archived_log order by 1 desc;				
				
SEQUENCE#	ARCHIVED	RESETLOGS_TIME	FIRST_TIME	NEXT_TIME
35511	YES	15/07/13 14:12	17/12/13 10:46	17/12/13 11:26
				
				
				
select group#, sequence#, archived, status from v$log order by group#;				
				
GROUP#	SEQUENCE#	ARCHIVED	STATUS	
1	35512	NO	CURRENT	
2	35510	YES	INACTIVE	
3	35511	YES	INACTIVE	
				
				
select group#, status, members from v$log order by group#, members;				
				
GROUP#	STATUS	MEMBERS		
1	CURRENT	2		
2	INACTIVE	2		
3	INACTIVE	2		
				



alert log -
Mon Dec 16 22:06:33 2013
Archived Log entry 1095 added for thread 1 sequence 1095 ID 0x65998d9a dest 1:
Thread 1 cannot allocate new log, sequence 1097
Checkpoint not complete
  Current log# 1 seq# 1096 mem# 0: +ODS_DATA1/uatods/onlinelog/group_1.324.832005481
Thread 1 advanced to log sequence 1097 (LGWR switch)
  Current log# 2 seq# 1097 mem# 0: +ODS_DATA1/uatods/onlinelog/group_2.325.832005483
Mon Dec 16 22:06:39 2013
Archived Log entry 1096 added for thread 1 sequence 1096 ID 0x65998d9a dest 1:
Mon Dec 16 22:06:45 2013
Thread 1 cannot allocate new log, sequence 1098
Checkpoint not complete
  Current log# 2 seq# 1097 mem# 0: +ODS_DATA1/uatods/onlinelog/group_2.325.832005483
Thread 1 advanced to log sequence 1098 (LGWR switch)
  Current log# 3 seq# 1098 mem# 0: +ODS_DATA1/uatods/onlinelog/group_3.326.832005485
Mon Dec 16 22:06:48 2013
Archived Log entry 1097 added for thread 1 sequence 1097 ID 0x65998d9a dest 1:
Mon Dec 16 22:17:19 2013
RFS[11]: Selected log 4 for thread 1 sequence 35507 dbid 1489133003 branch 820851149
Mon Dec 16 22:17:19 2013
RFS LogMiner: Registered logfile [+ODS_DATA2/archive_ods/uatods_58c25dcb_35506_1_820851149.arc] to LogMiner session id [1]
Mon Dec 16 22:27:00 2013
RFS[11]: Selected log 5 for thread 1 sequence 35508 dbid 1489133003 branch 820851149
Mon Dec 16 22:27:00 2013
RFS LogMiner: Registered logfile [+ODS_DATA2/archive_ods/uatods_58c25dcb_35507_1_820851149.arc] to LogMiner session id [1]
RFS[11]: Selected log 4 for thread 1 sequence 35509 dbid 1489133003 branch 820851149
Mon Dec 16 22:27:04 2013
RFS LogMiner: Registered logfile [+ODS_DATA2/archive_ods/uatods_58c25dcb_35508_1_820851149.arc] to LogMiner session id [1]
Tue Dec 17 02:00:00 2013
Closing scheduler window
Closing Resource Manager plan via scheduler window
Clearing Resource Manager plan via parameter
Tue Dec 17 02:30:23 2013
Thread 1 advanced to log sequence 1099 (LGWR switch)
  Current log# 1 seq# 1099 mem# 0: +ODS_DATA1/uatods/onlinelog/group_1.324.832005481
Tue Dec 17 02:30:24 2013
Archived Log entry 1098 added for thread 1 sequence 1098 ID 0x65998d9a dest 1:
Tue Dec 17 03:30:37 2013
RFS[11]: Selected log 5 for thread 1 sequence 35510 dbid 1489133003 branch 820851149
Tue Dec 17 03:30:37 2013
RFS LogMiner: Registered logfile [+ODS_DATA2/archive_ods/uatods_58c25dcb_35509_1_820851149.arc] to LogMiner session id [1]
Tue Dec 17 07:30:37 2013
Thread 1 advanced to log sequence 1100 (LGWR switch)
  Current log# 2 seq# 1100 mem# 0: +ODS_DATA1/uatods/onlinelog/group_2.325.832005483
Tue Dec 17 07:30:37 2013
Archived Log entry 1099 added for thread 1 sequence 1099 ID 0x65998d9a dest 1:
Tue Dec 17 10:46:08 2013
RFS[11]: Selected log 4 for thread 1 sequence 35511 dbid 1489133003 branch 820851149
Tue Dec 17 10:46:08 2013
RFS LogMiner: Registered logfile [+ODS_DATA2/archive_ods/uatods_58c25dcb_35510_1_820851149.arc] to LogMiner session id [1]



Do I need to check anything else to check whether archive applied and log shipping is happening or not?


Kindly assist me to resolve the problem.

Regards,
Ishika
Previous Topic: Error with shipping redo log from primary to standby
Next Topic: How to Activate ADG instance
Goto Forum:
  


Current Time: Fri Dec 19 09:57:01 CST 2014

Total time taken to generate the page: 0.08495 seconds