This discussion is archived
1 2 Previous Next 29 Replies Latest reply: Jul 6, 2012 10:57 PM by DB RSS

Failed to request gap sequence. Thread #: 1, gap sequence: 6859-6859

DB Newbie
Currently Being Moderated
Dear all,

1.while applying the log manually 6859 it tells that is already registered. then i appplied 6860,6861,6862,6863 its get appplied.
2.But while check on the alertlog it tells
Failed to request gap sequence. Thread #: 1, gap sequence: 6859-6859,All FAL server has been attempted.
Thu May 17 13:04:59 2012
idle dispatcher 'D000' terminated, pid = (11, 18)"
3.the alert logfile from standby is given below
-------------------------------------------------------------------------------------------------------------------------
Completed: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DI
Thu May 17 13:04:20 2012
Failed to request gap sequence. Thread #: 1, gap sequence: 6859-6859
All FAL server has been attempted.
Thu May 17 13:04:59 2012
idle dispatcher 'D000' terminated, pid = (11, 18)
--------------------------------------------------------------------------------------------------------------------------

thanks in advance,


regards,
DB
  • 1. Re: Failed to request gap sequence. Thread #: 1, gap sequence: 6859-6859
    mseberg Guru
    Currently Being Moderated
    Hello;

    I would check to see if an Archive log is missing. From the Primary try this :
    clear screen
    set linesize 100
     
    column STANDBY format a20
    column applied format a10
    
    SELECT  
      NAME AS STANDBY, 
      SEQUENCE#, 
       APPLIED, 
       COMPLETION_TIME 
    FROM 
      V$ARCHIVED_LOG 
    WHERE  
      DEST_ID = 2 
    AND 
      NEXT_TIME > SYSDATE -1;
    Change DEST_ID and SYSDATE as needed.

    Also to Monitor Data Guard Transport use this query :

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

    Best Regards

    mseberg
  • 2. Re: Failed to request gap sequence. Thread #: 1, gap sequence: 6859-6859
    CKPT Guru
    Currently Being Moderated
    Failed to request gap sequence. Thread #: 1, gap sequence: 6859-6859,All FAL server has been attempted.
    Can you check this archive log is exist or not in primary?
    Why you are copying archives and performing recover manually? , Any network issues check from v$dataguard_status;

    Also post the output of from primary

    SQL> select name from v$archived_log where thread#=1 and sequence# = 6859;
    SQL> select max(sequence#) from v$archived_log;
    SQL> select severity,message,timestamp,error_code from v$dataguard_status where dest_id=2;

    From standby:-
    SQL> select max(sequence#) from v$archived_log;
    SQL> select max(sequence#) from v$archived_log where applied='YES';
  • 3. Re: Failed to request gap sequence. Thread #: 1, gap sequence: 6859-6859
    DB Newbie
    Currently Being Moderated
    1.clear screen
    set linesize 100
    column STANDBY format a20
    column applied format a10

    SELECT
    NAME AS STANDBY,
    SEQUENCE#,
    APPLIED,
    COMPLETION_TIME
    FROM
    V$ARCHIVED_LOG
    WHERE
    DEST_ID = 2
    AND
    NEXT_TIME > SYSDATE -1;


    2.Also to Monitor Data Guard Transport use this query :

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

    STANDBY               SEQUENCE# APPLIED    COMPLETIO
    -------------------- ---------- ---------- ---------
    OVSDSTBY                   6866 NO         17-MAY-12
    OVSDSTBY                   6868 NO         18-MAY-12

    3.how to change the
    Change DEST_ID and SYSDATE as needed?

    regards,
    DB.

    Edited by: DB on May 17, 2012 10:13 PM
  • 4. Re: Failed to request gap sequence. Thread #: 1, gap sequence: 6859-6859
    DB Newbie
    Currently Being Moderated
    1.Why you are copying archives and performing recover manually?
    Any network issues check from v$dataguard_status;

    yes i had some network issues,after the accidental restart of standby

    2.Also post the output of from primary
    SQL> select name from v$archived_log where thread#=1 and sequence# = 6859;

    NAME
    --------------------------------------------------------------------------------
    /archive/ovsd/archive-ovsd_1_6859.arc

    3.SQL> select max(sequence#) from v$archived_log;

    MAX(SEQUENCE#)
    --------------
    6868

    4.SQL> select severity,message,timestamp,error_code from v$dataguard_status where dest_id=2;

    no rows selected

    From standby:-
    5.SQL> select max(sequence#) from v$archived_log;
    MAX(SEQUENCE#)
    --------------
    6868

    6.
    SQL> select max(sequence#) from v$archived_log where applied='YES';

    MAX(SEQUENCE#)
    --------------
    6858

    regards,
    DB
  • 5. Re: Failed to request gap sequence. Thread #: 1, gap sequence: 6859-6859
    CKPT Guru
    Currently Being Moderated
    3.how to change the Change DEST_ID and SYSDATE as needed?
    If your log archive remote destination can be from 2 to n.. so you can replace any value.
    Its weird that no error information from v$dataguard_status, Please do perform log switches and then check any errors in alert log file, then recheck that query.

    You have only 10 archives lag between standby and primary, So either perform as said above or register & recover manually, If there is real network problems.
  • 6. Re: Failed to request gap sequence. Thread #: 1, gap sequence: 6859-6859
    mseberg Guru
    Currently Being Moderated
    how to change the Change DEST_ID and SYSDATE as needed?

    What I mean is you can change the query.

    For example change SYSDATE to look at two or three days :

    SYSDATE -1
    SYSDATE -2
    SYSDATE -3

    Also if you INIT parameter for standby uses something besides 2 you can change that

    DEST_ID = 2

    Try the "Monitor Data Guard Transport" query because it gives an excellent summary.


    Best Regards

    mseberg
  • 7. Re: Failed to request gap sequence. Thread #: 1, gap sequence: 6859-6859
    DB Newbie
    Currently Being Moderated
    hi ,

    The log generated on the production server it shows 6858 and 6859 are generated at the same time.

    May be for this reason, not apply log on the standby?

    -rw-r----- 1 oracle dba 52427776 May 15 16:32 archive-ovsd_1_6856.arc
    -rw-r----- 1 oracle dba 52425728 May 15 19:54 archive-ovsd_1_6857.arc
    -rw-r-----   1 oracle     dba        52424704 May 16 03:02 archive-ovsd_1_6858.arc
    -rw-r-----   1 oracle     dba        52424704 May 16 03:02 archive-ovsd_1_6859.arc
    -rw-r----- 1 oracle dba 52427776 May 16 13:57 archive-ovsd_1_6860.arc
    -rw-r----- 1 oracle dba 52427776 May 16 18:39 archive-ovsd_1_6861.arc
    -rw-r----- 1 oracle dba 52427776 May 16 23:47 archive-ovsd_1_6862.arc
    -rw-r----- 1 oracle dba 52427776 May 17 07:03 archive-ovsd_1_6863.arc
    -rw-r----- 1 oracle dba 52427776 May 17 12:22 archive-ovsd_1_6864.arc
    -rw-r----- 1 oracle dba 52427776 May 17 17:00 archive-ovsd_1_6865.arc

    regards,
    DB
  • 8. Re: Failed to request gap sequence. Thread #: 1, gap sequence: 6859-6859
    CKPT Guru
    Currently Being Moderated
    Well, if you query with seconds probably you will get exact timestamp

    SQL> select to_char(completion_time,'DD-MON-YYYY HH24:MI:SS') from v$archived_log where sequence# in (6858,6859);
  • 9. Re: Failed to request gap sequence. Thread #: 1, gap sequence: 6859-6859
    DB Newbie
    Currently Being Moderated
    hi ckpt,

    Thanks for your suggestion.Now we done the full DR restoration.so ,yet now the log from Production is not applying automatically.so i had checked using the query on primary

    1.SELECT DEST_ID "ID", STATUS "DB_status",DESTINATION "Archive_dest",ERROR "Error" FROM V$ARCHIVE_DEST WHERE DEST_ID <=5;

    ID      DB_status      Archive_dest     Error
    ------------------------------------------------------
    1      VALID          /archive/ovsd
    2 ERROR          OVSDSTBY          ORA-12154: TNS:could not resolve service name
    3 INACTIVE
    4 INACTIVE
    5 INACTIVE
    regards,
    DB.
  • 10. Re: Failed to request gap sequence. Thread #: 1, gap sequence: 6859-6859
    mseberg Guru
    Currently Being Moderated
    Hello again;

    12154 is a common error. If this was Oracle 11 i would say check your Standby password file, I assume this is OK.
    If not you must copy the password to the standby and rename it. After that you must cancel recovery and shutdown the standby
    and START MOUNT on the new password file.


    Can you tnsping both servers from the other?

    Can you connect from ( sqlplus ) from each server to the other?

    Example :

    sqlplus sys/password@primary as sysdba (from the standby system)

    Most likely your tnsname is missing an entry or has an incorrect entry. Sometimes this is a listener issue, double check your status.



    Is your listener setup correctly?

    If you do a :

    lsnrctl status

    The READY status comes from the instance registering with the listener.


    The UNKNOWN status comes from the sid list entry in listener.ora.


    from standby

    $lsnrctl services

    And make sure your service is available.


    You can compare you tnsnames and listener.ora setup with my short notes :

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

    Best Regards

    mseberg
  • 11. Re: Failed to request gap sequence
    DB Newbie
    Currently Being Moderated
    hi mseberg,

    1.tnsping connecting well.
    2.sqlplus connecting well on both production and standby.
    3.lsnrctl status also fine.
    4.$lsnrctl services also fine.

    Now for every 5 logs 3 logs are shipping automatically.


    Regards,
    DB.
  • 12. Re: Failed to request gap sequence. Thread #: 1, gap sequence: 6859-6859
    Hemant K Chitale Oracle ACE
    Currently Being Moderated
    i appplied 6860,6861,6862,6863 its get appplied.
    That shouldn't and wouldn't happen if 6859 has not been applied.
    What is the evidence that 6860-6863 did get applied ?

    Hemant K Chitale
  • 13. Re: Failed to request gap sequence
    mseberg Guru
    Currently Being Moderated
    Hello again;

    Can you run this query from your Primary and post the results ? ( Change DEST_ID = 2 as needed for your Standby )
    clear screen
    set linesize 100
     
    column STANDBY format a20
    column applied format a10
     
    
    SELECT  
      NAME AS STANDBY, 
      SEQUENCE#, 
      APPLIED, 
      COMPLETION_TIME
    FROM 
      V$ARCHIVED_LOG 
    WHERE  
      DEST_ID = 2 
    AND 
      NEXT_TIME > SYSDATE -1;
    Best Regards

    mseberg
  • 14. Re: Failed to request gap sequence
    DB Newbie
    Currently Being Moderated
    hi,

    STANDBY SEQUENCE# APPLIED COMPLETIO
    -------------------- ---------- ---------- ---------
    OVSDSTBY 6923 NO 31-MAY-12
    OVSDSTBY 6925 NO 01-JUN-12

    Best regards,
    DB
1 2 Previous Next

Legend

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