This discussion is archived
1 2 Previous Next 28 Replies Latest reply: Mar 2, 2012 12:39 PM by Shivananda Rao Go to original post RSS
  • 15. Re: Archive log can not ship to GAP logfiles to standby DB automatically
    CKPT Guru
    Currently Being Moderated
    I think you are very much comfortable with manual copy & register. Thats why you are preferred to do automation all the time.

    Fix your environment with appropriate parameters and make it stable. Without setting parameters if you say "Earlier it was not working" , I have no answer for this.

    You have to careful of below parameters in specific to dataguard environment

    show parameter log_archive_dest_2
    show parameter log_archive_dest_state_2
    show parameter fal_client
    show parameter fal_server
    show parameter log_archive_config
    show parameter db_unique_name
    show parameter standby_file_management (depricated)

    Now check what the view is saying.

    Perform couple of log switches,
    Track your primary alert log file
    &
    SQL> select dest_id,severity, error_code,timestamp,message from v$dataguard_stauts;
  • 16. Re: Archive log can not ship to GAP logfiles to standby DB automatically
    799683 Newbie
    Currently Being Moderated
    I was trying to fix it by no affecting any production DB. but have no clue for why it doesn't work recently.
    We can not wait for the fix, so have to use manual scripts to fix it.

    I did test, by changing the log_archive_dest_state_2 to defer when the DB was down, still no help, once it deferred, oracle has no way to catch up the missed logfiles. I can see the message in the archive trace file:
    ABC: tkrsf_al_read: No mirror copies to re-read data
  • 17. Re: Archive log can not ship to GAP logfiles to standby DB automatically
    CKPT Guru
    Currently Being Moderated
    You are telling same thing again and again.

    You are not posting what we are requesting. It's not difficult to analyze your problem on fly without proof.

    Now it's up to you.

    If you want further help, post all what I/we have requested.
  • 18. Re: Archive log can not ship to GAP logfiles to standby DB automatically
    799683 Newbie
    Currently Being Moderated
    Here is the info, you are looking for.
    No any errors in the alter logfile
    -----on production-------
    18:16:53 SYS@PRIMARY> 
    
    NAME                                 TYPE                              VALUE
    ------------------------------------ --------------------------------- ------------------------------
    log_archive_dest_2                   string                            SERVICE=STANDBY reopen=300
    18:16:55 SYS@PRIMARY>
    NAME                                 TYPE                              VALUE
    ------------------------------------ --------------------------------- ------------------------------
    log_archive_dest_state_2             string                            ENABLE
    18:16:55 SYS@PRIMARY>
    NAME                                 TYPE                              VALUE
    ------------------------------------ --------------------------------- ------------------------------
    fal_client                           string                            STANDBY
    18:16:55 SYS@PRIMARY>
    NAME                                 TYPE                              VALUE
    ------------------------------------ --------------------------------- ------------------------------
    fal_server                           string
    18:16:55 SYS@PRIMARY>
    NAME                                 TYPE                              VALUE
    ------------------------------------ --------------------------------- ------------------------------
    log_archive_config                   string                            SEND,RECEIVE,NODG_CONFIG
    18:16:55 SYS@PRIMARY>
    NAME                                 TYPE                              VALUE
    ------------------------------------ --------------------------------- ------------------------------
    db_unique_name                       string                            PRIMARY
    18:16:55 SYS@PRIMARY>
    
    NAME                                 TYPE                              VALUE
    ------------------------------------ --------------------------------- ------------------------------
    standby_file_management              string                            MANUAL
    
    -------on standby ---------
    18:18:09 SYS@STANDBY> 
    NAME                                 TYPE                              VALUE
    ------------------------------------ --------------------------------- ------------------------------
    log_archive_dest_2                   string
    18:18:10 SYS@STANDBY>
    NAME                                 TYPE                              VALUE
    ------------------------------------ --------------------------------- ------------------------------
    log_archive_dest_state_2             string                            enable
    18:18:10 SYS@STANDBY>
    NAME                                 TYPE                              VALUE
    ------------------------------------ --------------------------------- ------------------------------
    fal_client                           string
    18:18:10 SYS@STANDBY>
    NAME                                 TYPE                              VALUE
    ------------------------------------ --------------------------------- ------------------------------
    fal_server                           string                            PRIMARY
    18:18:10 SYS@STANDBY>
    NAME                                 TYPE                              VALUE
    ------------------------------------ --------------------------------- ------------------------------
    log_archive_config                   string
    18:18:10 SYS@STANDBY>
    NAME                                 TYPE                              VALUE
    ------------------------------------ --------------------------------- ------------------------------
    db_unique_name                       string                            PRIMARY
    18:18:10 SYS@STANDBY>
    
    NAME                                 TYPE                              VALUE
    ------------------------------------ --------------------------------- ------------------------------
    standby_file_management              string                            auto
    
    
    
      1* select dest_id,severity, error_code,timestamp,message from v$dataguard_status
    
       DEST_ID SEVERITY             ERROR_CODE TIMESTAMP           MESSAGE
    ---------- -------------------- ---------- ------------------- ------------------------------------------------------------
             0 Informational                 0 2012-02-29 06:02:30 ARC0: Archival started
             0 Informational                 0 2012-02-29 06:02:30 ARC1: Archival started
             0 Informational                 0 2012-02-29 06:02:30 ARC0: Becoming the 'no FAL' ARCH
             0 Informational                 0 2012-02-29 06:02:30 ARC0: Becoming the 'no SRL' ARCH
             0 Informational                 0 2012-02-29 06:02:30 ARC1: Becoming the heartbeat ARCH
             0 Informational                 0 2012-02-29 07:02:02 Redo Shipping Client Connected as PUBLIC
             0 Informational                 0 2012-02-29 07:02:02 -- Connected User is Valid
             0 Informational                 0 2012-02-29 07:02:02 RFS[1]: Assigned to RFS process 404
             0 Informational                 0 2012-02-29 07:02:02 RFS[1]: Identified database type as 'physical standby'
             0 Informational                 0 2012-02-29 13:39:19 Redo Shipping Client Connected as PUBLIC
             0 Informational                 0 2012-02-29 13:39:19 -- Connected User is Valid
             0 Informational                 0 2012-02-29 13:39:19 RFS[2]: Assigned to RFS process 532
             0 Informational                 0 2012-02-29 13:39:19 RFS[2]: Identified database type as 'physical standby'
             0 Informational                 0 2012-02-29 13:41:47 Redo Shipping Client Connected as PUBLIC
             0 Informational                 0 2012-02-29 13:41:47 -- Connected User is Valid
             0 Informational                 0 2012-02-29 13:41:47 RFS[3]: Assigned to RFS process 734
             0 Informational                 0 2012-02-29 13:41:47 RFS[3]: Identified database type as 'physical standby'
             0 Informational                 0 2012-02-29 13:45:19 Redo Shipping Client Connected as PUBLIC
             0 Informational                 0 2012-02-29 13:45:19 -- Connected User is Valid
             0 Informational                 0 2012-02-29 13:45:19 RFS[4]: Assigned to RFS process 1070
             0 Informational                 0 2012-02-29 13:45:19 RFS[4]: Identified database type as 'physical standby'
             0 Informational                 0 2012-02-29 13:45:20 Redo Shipping Client Connected as PUBLIC
             0 Informational                 0 2012-02-29 13:45:20 -- Connected User is Valid
             0 Informational                 0 2012-02-29 13:45:20 RFS[5]: Assigned to RFS process 1072
             0 Informational                 0 2012-02-29 13:45:20 RFS[5]: Identified database type as 'physical standby'
             0 Informational                 0 2012-02-29 14:45:20 Redo Shipping Client Connected as PUBLIC
             0 Informational                 0 2012-02-29 14:45:20 -- Connected User is Valid
             0 Informational                 0 2012-02-29 14:45:20 RFS[6]: Assigned to RFS process 5693
             0 Informational                 0 2012-02-29 14:45:20 RFS[6]: Identified database type as 'physical standby'
             0 Informational                 0 2012-02-29 15:45:17 Redo Shipping Client Connected as PUBLIC
             0 Informational                 0 2012-02-29 15:45:17 -- Connected User is Valid
             0 Informational                 0 2012-02-29 15:45:17 RFS[7]: Assigned to RFS process 10195
             0 Informational                 0 2012-02-29 15:45:17 RFS[7]: Identified database type as 'physical standby'
             0 Informational                 0 2012-02-29 16:45:15 Redo Shipping Client Connected as PUBLIC
             0 Informational                 0 2012-02-29 16:45:15 -- Connected User is Valid
             0 Informational                 0 2012-02-29 16:45:15 RFS[8]: Assigned to RFS process 14707
             0 Informational                 0 2012-02-29 16:45:15 RFS[8]: Identified database type as 'physical standby'
             0 Informational                 0 2012-02-29 17:45:13 Redo Shipping Client Connected as PUBLIC
             0 Informational                 0 2012-02-29 17:45:13 -- Connected User is Valid
             0 Informational                 0 2012-02-29 17:45:13 RFS[9]: Assigned to RFS process 19207
             0 Informational                 0 2012-02-29 17:45:13 RFS[9]: Identified database type as 'physical standby'
    
    41 rows selected.
    
    Elapsed: 00:00:00.00
  • 19. Re: Archive log can not ship to GAP logfiles to standby DB automatically
    Shivananda Rao Guru
    Currently Being Moderated
    18:18:10 SYS@STANDBY>
    NAME                                 TYPE                              VALUE
    ------------------------------------ --------------------------------- ------------------------------
    fal_client                           string
    18:18:10 SYS@STANDBY>
    NAME                                 TYPE                              VALUE
    ------------------------------------ --------------------------------- ------------------------------
    fal_server                           string                            PRIMARY
    18:18:10 SYS@STANDBY>
    On your standby database, FAL_CLIENT is not set.
    Please set it to the Oracle Net Service Name of standby. Did you read my previous post ?
  • 20. Re: Archive log can not ship to GAP logfiles to standby DB automatically
    799683 Newbie
    Currently Being Moderated
    I did set it yesterday. No help, so I reverted it back.
  • 21. Re: Archive log can not ship to GAP logfiles to standby DB automatically
    Shivananda Rao Guru
    Currently Being Moderated
    After setting it, did you shutdown & started the standby database in mount mode using the modified pfile ?

    This parameter is mandatory in 10g on the standby database.

    In 10g, there is not required to have FAL_SERVER and FAL_CLIENT parameters on the primary database. They are mandatory on the standby database.
    SQL> show parameter fal
    
    NAME                                 TYPE        VALUE
    ------------------------------------ ----------- --------
    fal_client                           string
    fal_server                           string
    SQL>
    SQL>
    SQL>
    SQL> select database_role from v$database;
    
    DATABASE_ROLE
    ----------------
    PRIMARY
    Set FAL_CLIENT on the standby database pfile, and later bounce the standby database using this modified pfile.

    1 more question, can you post the value of standby_archive_dest on the standby database ?

    I am sure this is not set and if so, then this could be 1 of the reasons.

    Edited by: Shivananda Rao on Mar 1, 2012 7:14 PM
  • 22. Re: Archive log can not ship to GAP logfiles to standby DB automatically
    CKPT Guru
    Currently Being Moderated
    18:16:55 SYS@PRIMARY>
    NAME TYPE VALUE
    ------------------------------------ --------------------------------- ------------------------------
    fal_server string
    Here is your clue, Thats why unable fetch archives either from standby to primary (or) unable to send from primary to standby.

    In primary set FAL_SERVER as TNS service of standby.

    This is main Parameter which you have to set.

    Ofcourse you can set FAL_CLIENT, it plays great role in RAC environment, Still recommeded to set that value.
    Set that values first, and start MRP.

    users with PUBLIC are connected, no issues just kick off MRP after setting parameter.

    HTH.
    I did set it yesterday. No help, so I reverted it back.
    Might you did FAL_CLIENT on standby

    Put as i said FAL_SERVER & FAL_CLIENT in this post. Post your findings.

    Edited by: CKPT on Mar 1, 2012 1:31 PM
  • 23. Re: Archive log can not ship to GAP logfiles to standby DB automatically
    799683 Newbie
    Currently Being Moderated
    Thanks all for your input.
    Some updates here:

    1) all the parameter should be okay, since I have setup the same configuration on my test environment, everything works properly

    2) now, system changed a bit: we still have the gap (can be found in "v$archive_gap"), but those gap can only be filled after we issued "recover" command.
    The original situation was: no need "recover" command, the gap would be filled automatically whenever the standby database was up. ( this is also true on my test environment).
  • 24. Re: Archive log can not ship to GAP logfiles to standby DB automatically
    CKPT Guru
    Currently Being Moderated
    Oracle Explorer wrote:
    Thanks all for your input.
    Some updates here:

    1) all the parameter should be okay, since I have setup the same configuration on my test environment, everything works properly

    2) now, system changed a bit: we still have the gap (can be found in "v$archive_gap"), but those gap can only be filled after we issued "recover" command.
    The original situation was: no need "recover" command, the gap would be filled automatically whenever the standby database was up. ( this is also true on my test environment).
    Dear,

    If its working fine.. it will go smooth .
    Some times if you wont set FAL parameters, if you set log_archive_dest_2 also it works.
    But when you have issues with primary & standby, may be due to network or any other else.

    If you wont set FAL parameters, if any gaps it will fail to Fetch , So you should not compare one environment to other environments.
    If you want to fix this issue, please Set what ever all the parameters what i requested in earlier posts.

    If still you want to go with the same process, Really I cant help you.

    Once work with all that, set it if you fail again come back here, we will help you.

    we already given *14* replies, still you are not taken any action. It looks we are just doing argue with you.
    If you want to fix do it please, if not close the thread.

    Edited by: CKPT on Mar 2, 2012 11:37 PM
  • 25. Re: Archive log can not ship to GAP logfiles to standby DB automatically
    Shivananda Rao Guru
    Currently Being Moderated
    You have not posted what is asked.
    all the parameter should be okay, since I have setup the same configuration on my test environment, everything works properly
    Then probably I need to cross verify Oracle Documetations ;)
  • 26. Re: Archive log can not ship to GAP logfiles to standby DB automatically
    799683 Newbie
    Currently Being Moderated
    Thanks for your help anyway.
    Yes, I did changed some of the parameters as you or others suggested. but the issue still here for my real production environment.
    After that, I decide to build a same environment, to check if the original config has issues.
    For me, at this point, seems the original config should work. I still needs more investigations.
  • 27. Re: Archive log can not ship to GAP logfiles to standby DB automatically
    799683 Newbie
    Currently Being Moderated
    After setting it, did you shutdown & started the standby database in mount mode using the modified pfile ?
    Sure, I did
    {1 more question, can you post the value of standby_archive_dest on the standby database ?}
    11:55:20 SYS@Standby> show parameter standby_archive_dest

    NAME TYPE VALUE
    ------------------------------------ --------------------------------- ------------------------------
    standby_archive_dest string /u*****/Standby/arch
  • 28. Re: Archive log can not ship to GAP logfiles to standby DB automatically
    Shivananda Rao Guru
    Currently Being Moderated
    Ok..just re-read all the posts and found 1 more thing on your standby database

    Standby:
    18:18:10 SYS@STANDBY>
    NAME                                 TYPE                              VALUE
    ------------------------------------ --------------------------------- ------------------------------
    db_unique_name                       string                            PRIMARY
    Primary:
    18:16:55 SYS@PRIMARY>
    NAME                                 TYPE                              VALUE
    ------------------------------------ --------------------------------- ------------------------------
    db_unique_name                       string                            PRIMARY
    The parameter db_unique_name is same on primary and standby databases. This should not be same as this parameter uniquely identifies your database. So, set this parameter to a unique value on primary and standby and not same

    The parameter db_name should be same on both primary and standby databases. So, can you post
    show parameter db_name
    from both primary and standby database ?

    Looks like you are having the required initialization parameters set wrongly in both primary and standby database.
1 2 Previous Next

Legend

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