This discussion is archived
10 Replies Latest reply: Dec 2, 2012 3:56 AM by 974842 RSS

archive gap at new standby database

user8875620 Newbie
Currently Being Moderated
I just mounted my physical standby for the first time.
managed recovery is not turned on yet.

Why do I have an archive gap?

This is what I see:


SQL> SELECT sequence#, first_time, next_time, applied
FROM v$archived_log
ORDER BY sequence#; 2 3

SEQUENCE# FIRST_TIME NEXT_TIME APP
---------- ------------------ ------------------ ---
574986 28-NOV-12 21:14:56 28-NOV-12 21:21:11 NO
574987 28-NOV-12 21:21:11 28-NOV-12 21:32:28 NO
574988 28-NOV-12 21:32:28 28-NOV-12 21:38:59 NO

SQL> select * from v$archive_gap;

THREAD# LOW_SEQUENCE# HIGH_SEQUENCE#
---------- ------------- --------------
1 574986 574987

SQL> select SEQUENCE#, thread#, process, status from V$MANAGED_STANDBY;

SEQUENCE# THREAD# PROCESS STATUS
---------- ---------- --------- ------------
0 0 ARCH CONNECTED
0 0 ARCH CONNECTED
0 0 RFS RECEIVING
0 0 RFS RECEIVING
574989 1 RFS WRITING

SQL>
  • 2. Re: archive gap at new standby database
    mseberg Guru
    Currently Being Moderated
    Hello;

    You might be testing too early.

    My system :
    SQL> select SEQUENCE#, thread#, process, status from V$MANAGED_STANDBY;
    
     SEQUENCE#    THREAD# PROCESS   STATUS
    ---------- ---------- --------- ------------
          9754          1 ARCH      CLOSING
             0          0 ARCH      CONNECTED
          9755          1 ARCH      CLOSING
          9749          1 ARCH      CLOSING
          9756          1 ARCH      CLOSING
          9751          1 ARCH      CLOSING
          9752          1 ARCH      CLOSING
          9753          1 ARCH      CLOSING
          9757          1 MRP0      WAIT_FOR_LOG
             0          0 RFS       IDLE
          9757          1 RFS       IDLE
    
     SEQUENCE#    THREAD# PROCESS   STATUS
    ---------- ---------- --------- ------------
             0          0 RFS       IDLE
             0          0 RFS       IDLE
    
    13 rows selected.
    
    SQL> 
    Once you have MRP running consider testing using this :

    http://www.visi.com/~mseberg/monitor_data_guard_transport.html

    Best Regards

    mseberg
  • 3. Re: archive gap at new standby database
    Niket Kumar Pro
    Currently Being Moderated
    I just mounted my physical standby for the first time.
    managed recovery is not turned on yet.
    
    Why do I have an archive gap?
    if you have not started managed recovery then your standby database is lagging and archive gap is there..
  • 4. Re: archive gap at new standby database
    user8875620 Newbie
    Currently Being Moderated
    thanks for the replies.

    I am concerned because:

    The reason I cannot turn on MRP now is because the standby database is not restored yet.
    I don't want to send my backup tapes for restore (means $$ + few days), if my standby is not properly mounted.

    I attempted to create standby control file + mount standby database several times.
    Each attempt still shows similar gap in the beginning before MRP starts.
  • 5. Re: archive gap at new standby database
    mseberg Guru
    Currently Being Moderated
    Hello;

    With all due respect you have put the cart before the horse. You need to have a working Standby, then test for gaps.

    Its a little like trying to test a boat that's still being built, results will vary.

    I get the exact same results when I query a database without Data Guard setup!!

    Best Regards

    mseberg
  • 6. Re: archive gap at new standby database
    Sunny kichloo Expert
    Currently Being Moderated
    Start MRP and see if its still lagging and Share the output
  • 7. Re: archive gap at new standby database
    Acooper Explorer
    Currently Being Moderated
    Please read the posts carefully:

    h2. I cannot turn on MRP now is because the standby database is not restored yet...
  • 8. Re: archive gap at new standby database
    Sunny kichloo Expert
    Currently Being Moderated
    My bad :-)
  • 9. Re: archive gap at new standby database
    974842 Newbie
    Currently Being Moderated
    Hope u ave set each and everything fine.

    Firstcheck whether u have configured ur standby properly.
    means using same mounts or different mount pointsand according to that parameters has been set rename ur password,and pfile name on ur standby server.

    after all doing this just fire.

    Startup mount
    alter database recover managed standby database disconnect from session;

    If not please share ur alert log details of ur standby server.

    And if u are using ur database in maximum performance mode no need to create standby redologs.



    Thanks and regards
  • 10. Re: archive gap at new standby database
    974842 Newbie
    Currently Being Moderated
    And in ur standby pfile just remove old locations of ur controlfiles '/control01.ctl'/../control03.ctl and ur new controlfile location in ur standby pfile'standby.ctl' which u have been created and transfer from ur Production server


    Else mail me ur setup info at rohit_dogra94@yahoo.com
    what parameters u have used and all

    Edited by: user2998224 on Dec 2, 2012 3:55 AM

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points