This discussion is archived
1 2 Previous Next 28 Replies Latest reply: Mar 2, 2012 12:39 PM by Shivananda Rao RSS

Archive log can not ship to GAP logfiles to standby DB automatically

799683 Newbie
Currently Being Moderated
we have a non-real time standby database, which will receive the archive file from the primary database server most of the time, and will apply the logfiles only at one point of time daily.
Some times, we need to shutdown the Standby DB server for a while ( 3-4 hours).
The missed logfiles will catch up during the standby down time later.

But since last week we had an storage incident, the primary DB server stops to catch up the missed logfiles, and saw this message at the archvie trace file:

ABC: tkrsf_al_read: No mirror copies to re-read data

Current, we found the archive log gaps on the standby server, and have to manually copy those logfiles over and register them.

Saw some tips on the internet to change the parameter "log_archive_max_processes", but no help for us at all.

Here is the parameter on the Primary DB server:

log_archive_dest_2 = SERVICE=Standby_server reopen=300
  • 1. Re: Archive log can not ship to GAP logfiles to standby DB automatically
    mseberg Guru
    Currently Being Moderated
    Hello

    Can you tell me exactly what you mean by " non-real time standby database" is this Data Guard?

    Also can you supply the OS and Oracle version?

    Since the issue are there new entries in either alert log?

    Best Regards

    mseberg
  • 2. Re: Archive log can not ship to GAP logfiles to standby DB automatically
    799683 Newbie
    Currently Being Moderated
    "non-real time standby database" means: we dont apply the archive log files on the standby DB server even the logfile arrives. Only apply them at one special time ( see 5:00 am daily).

    Both OS are: Sun Microsystems Inc. SunOS 5.10
    Both Oracle are: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production

    Here are the lines on the alert logfile:

    Error 1034 received logging on to the standby
    Errors in file /******/***arc210536.trc:
    ORA-01034: ORACLE not available
    FAL[server, ARC2]: FAL archive failed, see trace file.
    ...
    Errors in file /******/***arc210536.trc:
    ORA-16055: FAL request rejected
    ARCH: FAL archive failed. Archiver continuing

    ORACLE Instance **** - Archival Error. Archiver continuing.
  • 3. Re: Archive log can not ship to GAP logfiles to standby DB automatically
    mseberg Guru
    Currently Being Moderated
    Thank you for the information.

    I believe you have a connection issue ( no way to say this and be profound ). Double check the value for ORACLE_HOME used on the standby site.

    Make sure the ORACLE_HOME has no trailing characters like a /

    I would double check the listener.ora file for anything odd too.


    I have a couple of notes :

    ORA - 03135 : connection lost contact while shipping from Primary Server to Standby server [ID 739522.1]

    PHYSICAL: When Data Guard and TCPS ASO Configured receive ORA-3113 and ORA-16055 during Redo Transport [ID 889763.1]

    Bug 8842032 - ORA-3113 AND ORA-16055 OCCURS ON FAL REQUESTS


    Will double check everything.


    Best Regards

    mseberg

    Edited by: mseberg on Feb 28, 2012 12:03 PM
  • 4. Re: Archive log can not ship to GAP logfiles to standby DB automatically
    CKPT Guru
    Currently Being Moderated
    which will receive the archive file from the primary database server most of the time
    Most times from primary. Then remaining times? so you Copy manually and register?
    Then it's dataguard not an manual standby.
    Error 1034 received logging on to the standby
    Errors in file /******/***arc210536.trc:
    ORA-01034: ORACLE not available
    FAL[server, ARC2]: FAL archive failed, see trace file.
    these errors in primary when , stanby is down and when primary tries to connect to standby, so tese errors not considerable to investigate ,
    When you don't want to apply archives on standby no need to shutdown. Just put this value log_archive_dest_state_2='defer'
    Once you enable check what are the errors in primary alert log file.
    How is your network band width speed? Is it capable to hold that much archive data?
    May be it will take some time when you pause & start.

    Also use LGWR in log_archive_dest_2 for real time apply after creatin standby redo logs.

    So post the alert log information once you enable standby database.
  • 5. Re: Archive log can not ship to GAP logfiles to standby DB automatically
    799683 Newbie
    Currently Being Moderated
    Most times from primary. Then remaining times? so you Copy manually and register? 
    Then it's dataguard not an manual standby. 
    Before Oracle would automatically fill the missed logfiles due to the shutdown of the standby server.
    Now, I have to manually and register them. This is the reason I am asking this question here.
    these errors in primary when , stanby is down and when primary tries to connect to standby, so tese errors not considerable to investigate , 
    When you don't want to apply archives on standby no need to shutdown. Just put this value log_archive_dest_state_2='defer'
    Once you enable check what are the errors in primary alert log file. 
    How is your network band width speed? Is it capable to hold that much archive data? 
    May be it will take some time when you pause & start. 
    Yes, change the parameters may solve this. But we already use this architecture for years. No problem at all before.
  • 6. Re: Archive log can not ship to GAP logfiles to standby DB automatically
    CKPT Guru
    Currently Being Moderated
    Now, I have to manually and register them. This is the reason I am asking this question here.
    No need to copy and apply manually.
    That's why asked log file information. You have posted but that log information is when standby was down , I need log information once after you start database with MRP. what errors you have seen in standby?

    Also

    SQL> show parameter fal

    Change your strategy to disable destination instead of shutdown.
  • 7. Re: Archive log can not ship to GAP logfiles to standby DB automatically
    799683 Newbie
    Currently Being Moderated
    thanks for your help.

    Errors in file /****/***stby_ora_18795.trc:
    ORA-01009: missing mandatory parameter
    ...
    FAL[client]: Failed to request gap sequence
    GAP - thread 1 sequence 3217860-3721862
    DBID 2479581232703 branch 676712346655
    FAL[client]: All defined FAL servers have been attempted.
    -------------------------------------------------------------
    Check that the CONTROL_FILE_RECORD_KEEP_TIME initialization
    parameter is defined to a value that is sufficiently large
    enough to maintain adequate log switch information to resolve
    archivelog gaps.
    -------------------------------------------------------------

    SQL> show parameter fal

    NAME TYPE VALUE
    ------------------------------------ --------------------------------- ------------------------------
    fal_client string
    fal_server string PRIMARY_DB
  • 8. Re: Archive log can not ship to GAP logfiles to standby DB automatically
    mseberg Guru
    Currently Being Moderated
    I'm thinking your Primary log_archive_dest_n remote destination and your Standby fal_client should be using the same tns alias.

    In Oracle 11R2 FAL_CLIENT is optional.

    And this idea of CKPT's

    "Change your strategy to disable destination instead of shutdown." I think this is a good idea too.



    Best Regards

    mseberg
  • 9. Re: Archive log can not ship to GAP logfiles to standby DB automatically
    799683 Newbie
    Currently Being Moderated
    problem is: we have never set this on the standby server before, and it worked well before.
  • 10. Re: Archive log can not ship to GAP logfiles to standby DB automatically
    mseberg Guru
    Currently Being Moderated
    I understand your position, in fact if I were you I would want to know the "why" too.

    But I don't see how I can answer that. I think the best I can do is say here's another way to get is working again.

    My best guess is the Primary tnsnames is not happy and if you want to continue down that path then try tnsping and try to connect to the Standby would be where I start.

    Best Regards

    mseberg
  • 11. Re: Archive log can not ship to GAP logfiles to standby DB automatically
    799683 Newbie
    Currently Being Moderated
    Thanks for your help.
    In fact,I did the test at the very beginning. Nothing wrong for those TNS connections.
    Sure we have several options as suggested above to fix/around this.
    But we wont want to touch the production DB at best, currently, I am writing a shell scripts to manually send the missed logfiles and register them.
  • 12. Re: Archive log can not ship to GAP logfiles to standby DB automatically
    CKPT Guru
    Currently Being Moderated
    FAL[client]: Failed to request gap sequence
    GAP - thread 1 sequence 3217860-3721862
    DBID 2479581232703 branch 676712346655
    FAL[client]: All defined FAL servers have been attempted.
    It shows there is archive gap with three archives.
    What is the sync status with primary now?

    Post from primary

    Sql> Select thread#,max(sequence#) from v$archived_log group by thread#;

    From standby:

    Sql> Select thread#,max(sequence#) from v$archived_log group by thread#;
    Sql> Select thread#,max(sequence#) from v$archived_log where applied='YES' group by thread#;
  • 13. Re: Archive log can not ship to GAP logfiles to standby DB automatically
    799683 Newbie
    Currently Being Moderated
    Those gap already filled by my manual scripts (copy the logfiles, and register them)

    At this moment, here is the info.

    -----on the Primary -----
    19:17:41 SQL> Select thread#,max(sequence#) from v$archived_log group by thread#;

    THREAD# MAX(SEQUENCE#)
    ---------- --------------
    1 3218037

    Elapsed: 00:00:00.24
    -----on the standby -----
    19:18:33 SQL> Select thread#,max(sequence#) from v$archived_log group by thread#;

    THREAD# MAX(SEQUENCE#)
    ---------- --------------
    1 3218037

    Elapsed: 00:00:00.02
    19:18:53 SQL> Select thread#,max(sequence#) from v$archived_log where applied='YES' group by thread#;

    THREAD# MAX(SEQUENCE#)
    ---------- --------------
    1 3218014

    Elapsed: 00:00:00.02
  • 14. Re: Archive log can not ship to GAP logfiles to standby DB automatically
    Shivananda Rao Guru
    Currently Being Moderated
    Hi,

    Your database version is 10.2. So, do you have the FAL_SERVER and FAL_CLIENT set on the standby database initialization file (pfile/spfile)

    These two parameters are very much necessary on the standby side. As Mseberg already mentioned, FAL_CLIENT can be ignored on standby side from 11gR2.

    Post from the standby pfile/spflie:
    show parameter FAL
    Ok. From one of your previous post, I just checked that FAL_CLIENT is unset. Can you just set it to the NET Service Name used for Standby database and update us.

    Edited by: Shivananda Rao on Feb 29, 2012 9:53 AM
1 2 Previous Next

Legend

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