Database Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

archive log sequence after certain incarnation in data guard

951290Dec 24 2014 — edited Dec 24 2014

HI experts ,

I have one data guard setup , where both primary and standby went through so many incarnation in the past . so while I am checking the data guard sync status the max(sequence#) from v$archive_log showing hight value but archive log list showing very low number (But actually they are in sync)

Here is the details

----------------------------------------on primary---------------------------

SQL> select name,open_mode,controlfile_type,database_role from v$database;

NAME OPEN_MODE CONTROL DATABASE_ROLE

--------- -------------------- ------- ----------------

DTHTB READ WRITE CURRENT PRIMARY

SQL> select thread#,max(sequence#) from v$archived_log group by thread#;

THREAD# MAX(SEQUENCE#)

---------- --------------

1 11697

SQL> archive log list

Database log mode Archive Mode

Automatic archival Enabled

Archive destination USE_DB_RECOVERY_FILE_DEST

Oldest online log sequence 1952

Next log sequence to archive 1954

Current log sequence 1954

SQL>

RMAN> list incarnation

2> ;

using target database control file instead of recovery catalog

List of Database Incarnations

DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time

------- ------- -------- ---------------- --- ---------- ----------

1 1 DTHTB 493031936 PARENT 5965217028383 22-MAR-13

2 2 DTHTB 493031936 PARENT 5965226229888 03-MAY-13

3 3 DTHTB 493031936 ORPHAN 5965241545183 12-JUN-13

4 4 DTHTB 493031936 ORPHAN 5965270581021 28-AUG-13

5 5 DTHTB 493031936 ORPHAN 5965285872763 04-OCT-13

6 6 DTHTB 493031936 ORPHAN 5965290859481 23-OCT-13

7 7 DTHTB 493031936 ORPHAN 5965388678159 25-MAR-14

8 8 DTHTB 493031936 ORPHAN 5965399563647 31-MAR-14

9 9 DTHTB 493031936 ORPHAN 5965401493622 07-APR-14

10 10 DTHTB 493031936 ORPHAN 5965401950202 08-APR-14

11 11 DTHTB 493031936 ORPHAN 5965409680344 05-MAY-14

12 12 DTHTB 493031936 ORPHAN 5965445817027 18-AUG-14

13 13 DTHTB 493031936 CURRENT 5965446906194 22-AUG-14

14 14 DTHTB 493031936 ORPHAN 5965457976285 24-SEP-14

15 15 DTHTB 493031936 ORPHAN 5965459650477 29-SEP-14

16 16 DTHTB 493031936 ORPHAN 5965478439879 11-NOV-14

RMAN>

---------at standby-----

SQL> select name,open_mode,controlfile_type,database_role from v$database;

NAME OPEN_MODE CONTROL DATABASE_ROLE

--------- -------------------- ------- ----------------

DTHTB READ ONLY WITH APPLY STANDBY PHYSICAL STANDBY

SQL> select thread#,max(sequence#) from v$archived_log group by thread#;

THREAD# MAX(SEQUENCE#)

---------- --------------

1 11690

SQL> select process,status,sequence# from v$managed_standby;

PROCESS STATUS SEQUENCE#

--------- ------------ ----------

ARCH CLOSING 1952

ARCH CLOSING 1951

ARCH CONNECTED 0

ARCH CLOSING 1953

RFS IDLE 0

RFS IDLE 1954

MRP0 APPLYING_LOG 1954

9 rows selected.

SQL> archive log list

Database log mode Archive Mode

Automatic archival Enabled

Archive destination USE_DB_RECOVERY_FILE_DEST

Oldest online log sequence 1952

Next log sequence to archive 0

Current log sequence 1954

SQL>

RMAN> list incarnation;

using target database control file instead of recovery catalog

List of Database Incarnations

DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time

------- ------- -------- ---------------- --- ---------- ----------

1 1 DTHTB 493031936 PARENT 5965217028383 22-MAR-13

2 2 DTHTB 493031936 PARENT 5965226229888 03-MAY-13

3 3 DTHTB 493031936 ORPHAN 5965241545183 12-JUN-13

4 4 DTHTB 493031936 ORPHAN 5965246529208 26-JUN-13

5 5 DTHTB 493031936 ORPHAN 5965249395746 04-JUL-13

6 6 DTHTB 493031936 ORPHAN 5965251976536 11-JUL-13

7 7 DTHTB 493031936 ORPHAN 5965254866175 19-JUL-13

8 8 DTHTB 493031936 ORPHAN 5965256673489 24-JUL-13

9 9 DTHTB 493031936 ORPHAN 5965264215287 12-AUG-13

10 10 DTHTB 493031936 ORPHAN 5965293230437 28-OCT-13

11 11 DTHTB 493031936 ORPHAN 5965297864407 28-OCT-13

12 12 DTHTB 493031936 ORPHAN 5965314412979 02-DEC-13

13 13 DTHTB 493031936 ORPHAN 5965314927753 03-DEC-13

14 14 DTHTB 493031936 ORPHAN 5965314944367 03-DEC-13

15 15 DTHTB 493031936 ORPHAN 5965315014764 03-DEC-13

16 16 DTHTB 493031936 ORPHAN 5965318192395 09-DEC-13

17 17 DTHTB 493031936 ORPHAN 5965319412330 12-DEC-13

18 18 DTHTB 493031936 ORPHAN 5965356386810 04-MAR-14

19 19 DTHTB 493031936 ORPHAN 5965358951338 10-MAR-14

20 20 DTHTB 493031936 ORPHAN 5965363153270 19-MAR-14

21 21 DTHTB 493031936 CURRENT 5965446906194 22-AUG-14

22 22 DTHTB 493031936 ORPHAN 5965448432001 26-AUG-14

23 23 DTHTB 493031936 ORPHAN 5965455068351 15-SEP-14

24 24 DTHTB 493031936 ORPHAN 5965483647392 19-NOV-14

25 25 DTHTB 493031936 ORPHAN 5965490341204 08-DEC-14

26 26 DTHTB 493031936 ORPHAN 5965493178888 17-DEC-14

27 27 DTHTB 493031936 ORPHAN 5965494826573 22-DEC-14

--------------------------

How to get rid of from these misbehavior of archive log sequence in data guard ?

Locked Post

New comments cannot be posted to this locked post.

Locked on Jan 21 2015

Added on Dec 24 2014

#data-guard, #performance-availability

3 comments

2,561 views