Skip to Main Content

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!

UNRESOLVABLE GAP - Thread 2 logs seem to no apply

jimd1673Aug 16 2017 — edited Aug 17 2017

I'm trying to configure our new dataguard environment and for the life of me I can correct an "unresolvable gap". 

I tried to get the standby instance caught up with rman and that seemed to work, however the primary still report an unresolvable gap:

select status,DEST_ID,TYPE,ERROR,GAP_STATUS,SYNCHRONIZED,SYNCHRONIZATION_STATUS, RECOVERY_MODE

from  V$ARCHIVE_DEST_STATUS where STatus <> 'INACTIVE';SQL> SQL> SQL> SQL> SQL>   2

STATUS       DEST_ID TYPE             ERROR                                              GAP_STATUS               SYN SYNCHRONIZATION_STATUS RECOVERY_MODE

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

VALID              1 LOCAL                                                                                        NO  CHECK CONFIGURATION    IDLE

VALID              2 PHYSICAL                                                            UNRESOLVABLE GAP         NO  CHECK CONFIGURATION    MANAGED REAL TIME APPLY

I also noticed that it seems non of the logs from thread 2 are applying:

SQL> select thread#,

  2         inst_id,

  3         sequence#,

  4         first_time,

  5         next_time,

  6         status,

  7         applied,

  8         DECODE(dest_id, 1, 'HERE', 2, 'DG_INSTANCE', 3, 'CLONE')

  9  from   gv$archived_log

10  where  dest_id = 2

11  and inst_id = thread#

12  order  by first_time;

   THREAD#    INST_ID  SEQUENCE# FIRST_TIME                  NEXT_TIME                   S APPLIED   DECODE(DEST

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

         1          1       5070 15-AUG-17 15:32:55          15-AUG-17 15:39:05          A YES       DG_INSTANCE

         2          2       7561 15-AUG-17 15:36:12          15-AUG-17 15:39:06          A NO        DG_INSTANCE

         1          1       5071 15-AUG-17 15:39:05          15-AUG-17 16:08:56          A YES       DG_INSTANCE

         2          2       7562 15-AUG-17 15:39:06          15-AUG-17 16:09:05          A NO        DG_INSTANCE

         1          1       5072 15-AUG-17 16:08:56          15-AUG-17 16:38:57          A YES       DG_INSTANCE

         2          2       7563 15-AUG-17 16:09:05          15-AUG-17 16:39:07          A NO        DG_INSTANCE

         1          1       5073 15-AUG-17 16:38:57          15-AUG-17 17:08:44          A YES       DG_INSTANCE

         2          2       7564 15-AUG-17 16:39:07          15-AUG-17 17:09:08          A NO        DG_INSTANCE

         1          1       5074 15-AUG-17 17:08:44          15-AUG-17 17:38:45          A YES       DG_INSTANCE

         2          2       7565 15-AUG-17 17:09:08          15-AUG-17 17:39:08          A NO        DG_INSTANCE

         1          1       5075 15-AUG-17 17:38:45          15-AUG-17 18:00:08          A YES       DG_INSTANCE

         2          2       7566 15-AUG-17 17:39:08          15-AUG-17 18:00:09          A NO        DG_INSTANCE

         1          1       5076 15-AUG-17 18:00:08          15-AUG-17 18:30:09          A YES       DG_INSTANCE

I'm not sure what to make of this and I can't seem to figure out how to fix it.

Our environment:

Primary:

12.1.0.2 RAC

Standby:

12.1.0.2 Single instance

         2          2       7567 15-AUG-17 18:00:09          15-AUG-17 18:30:07          A NO        DG_INSTANCE

         2          2       7568 15-AUG-17 18:30:07          15-AUG-17 18:38:44          A NO        DG_INSTANCE

Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Sep 14 2017
Added on Aug 16 2017
12 comments
3,815 views