Questions about CURRENT status on archive log files in a logical standby database (Doc ID 943933.1)

Last updated on FEBRUARY 07, 2017

Applies to:

Oracle Database - Enterprise Edition - Version 10.1.0.2 to 12.1.0.2 [Release 10.1 to 12.1]
Information in this document applies to any platform.
This applies to 10g logical standby database.

***Checked for relevance on 03-MAI-2013***

Goal

QUESTIONS

Based on the logical standby database diagnostic output (Note.241512.1) below,
SQL> set numwidth 15
SQL> column trd format 99
SQL>
SQL> select thread# trd, sequence#,
2 first_change#, next_change#,
3 dict_begin beg, dict_end end,
4 to_char(timestamp, 'hh:mi:ss') timestamp,
5 (case when l.next_change# < p.read_scn then 'YES'
6 when l.first_change# < p.applied_scn then 'CURRENT'
7 else 'NO' end) applied
8 from dba_logstdby_log l, dba_logstdby_progress p
9 order by thread#, first_change#;

TRD SEQUENCE# FIRST_CHANGE# NEXT_CHANGE# BEG END TIMESTAM APPLIED
--- --------------- --------------- --------------- --- --- -------- -------
1 4726 324929463 325017137 NO NO 09:05:54 CURRENT
1 4727 325017137 325144127 NO NO 10:13:13 CURRENT
1 4728 325144127 325216928 NO NO 10:44:54 CURRENT
1 4729 325216928 325269447 NO NO 10:53:25 CURRENT
1 4730 325269447 325305446 NO NO 11:00:03 CURRENT
1 4731 325305446 325305823 NO NO 11:00:08 CURRENT
1 4732 325305823 325307321 NO NO 11:00:18 CURRENT
1 4733 325307321 325359346 NO NO 11:07:52 CURRENT
1 4734 325359346 325459042 NO NO 11:41:42 CURRENT
2 4008 324918492 325025595 NO NO 09:12:46 CURRENT
2 4009 325025595 325102515 NO NO 09:50:06 CURRENT
2 4010 325102515 325189917 NO NO 10:39:19 CURRENT
2 4011 325189917 325203262 NO NO 10:42:24 CURRENT
2 4012 325203262 325216784 NO NO 10:44:54 CURRENT
2 4013 325216784 325229528 NO NO 10:47:08 CURRENT
2 4014 325229528 325244704 NO NO 10:50:28 CURRENT
2 4015 325244704 325268679 NO NO 10:53:26 CURRENT
2 4016 325268679 325285510 NO NO 10:56:21 CURRENT
2 4017 325285510 325303074 NO NO 10:59:44 CURRENT
2 4018 325303074 325305438 NO NO 11:00:09 CURRENT
2 4019 325305438 325305828 NO NO 11:00:10 CURRENT
2 4020 325305828 325307341 NO NO 11:00:18 CURRENT
2 4021 325307341 325335040 NO NO 11:03:19 CURRENT
2 4022 325335040 325358969 NO NO 11:07:58 CURRENT
2 4023 325358969 325386468 NO NO 11:15:01 CURRENT
2 4024 325386468 325404890 NO NO 11:15:55 CURRENT
2 4025 325404890 325459021 NO NO 11:41:44 CURRENT

You had the following questions:

 

1) What does CURRENT really mean ? 

2) Why the archive LOGS are not being deleted sooner?

3) How do you know which archive logs are really applied? 

4) What caused so many archive logs were in CURRENT status?

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms