This discussion is archived
1 2 Previous Next 24 Replies Latest reply: Dec 9, 2012 9:09 PM by Athurumithuru Go to original post RSS
  • 15. Re: Recreate Standby using full datafile backup
    Athurumithuru Newbie
    Currently Being Moderated
    Dear CKPT,

    After considering your comments on network/bandwidth I have found that our network team has implemented traffic shape for primary db, which is abt 2M. Primary db normally creates average of 2GB archive data per day. But our network reports indicates that 17.5 GB has been transfers to stand by server for last 24. can this be happened. According to my memory all these problems were started when I upload a 1.5 GB schema to primary db. Then network people placed a traffic shape and controlled the traffic. Is this information helpful for you.

    Thanks & Rgds,
    Athurumithuru.
  • 16. Re: Recreate Standby using full datafile backup
    Athurumithuru Newbie
    Currently Being Moderated
    Dear CKPT,

    Waiting for your feed back.

    Rgds,
    Athurumithuru.
  • 17. Re: Recreate Standby using full datafile backup
    CKPT Guru
    Currently Being Moderated
    >
    fal_client
    fal_server
    >

    Sorry for delay in response.
    There are no values for FAL_CLIENT & SERVER from primary side, FAL_SERVER is mandatory parameter too to fetch the archives. Put the value and then retry once again.
  • 18. Re: Recreate Standby using full datafile backup
    Athurumithuru Newbie
    Currently Being Moderated
    Dear CKPT,

    Its a good point. Earlier it was there. Anyway how come archive logs shipped to destination?

    Rgds,
    Athurumithuru

    Edited by: Athurumithuru on Dec 7, 2012 4:01 PM
  • 19. Re: Recreate Standby using full datafile backup
    CKPT Guru
    Currently Being Moderated
    Athurumithuru wrote:
    Dear CKPT,

    Its a good point. Earlier it was there. Anyway how come archive logs shipped to destination?

    Rgds,
    Amila
    It will be shipped, but in case of GAPs, these paraemeters plays key role. FAL--> Fetch Archive Lag... Which communicates to send and receive the redo/arch data.
    Have you configured? and what is the current status?

    Thanks.
  • 20. Re: Recreate Standby using full datafile backup
    Athurumithuru Newbie
    Currently Being Moderated
    Dear CKPT,

    I'm just nervous now. Do I have to interchange values like bellow??


    SQL>
    SQL>
    SQL> show parameter fal

    NAME TYPE VALUE
    ------------------------------------ ----------- ----------
    fal_client string dbcdsl
    fal_server string cstdby
    SQL>

    Stand by site
    ===========

    SQL>
    SQL>
    SQL> show parameter fal

    NAME TYPE VALUE
    ------------------------------------ ----------- ----------
    fal_client string cstdby
    fal_server string dbcdsl

    Rgds,
    Athurumithuru.
    SQL>
  • 21. Re: Recreate Standby using full datafile backup
    CKPT Guru
    Currently Being Moderated
    Hi,

    FAL_CLIENT refers to its own and FAL_SERVER refers to remote TNS service, If dbcdsl belongs to primary and cstdby belongs to Standby then your settings are correct.

    Once you set them, Do as follows and let me know results.

    SQL> alter system switch logfile;
    SQL> alter system switch logfile;
    SQL> alter system set log_archive_dest_state_2='defer';
    SQL> alter system set log_archive_dest_state_2='enable';

    Check alert logs and later some time, use below queries and share the output.

    Primary:- select max(sequence#) from v$archived_log;
    SQL>select severity,error_code,message,timestamp from v$dataguard_status where dest_id=2;

    Standby: select max(sequence#) from v$archived_log where applied='YES';
  • 22. Re: Recreate Standby using full datafile backup
    Athurumithuru Newbie
    Currently Being Moderated
    Dear CKPT,

    Sorry for the delay. Here is the results.

    At Primary..


    SQL> alter system set fal_client='dbcdsl';

    System altered.

    SQL> show parameter fal
    NAME TYPE VALUE
    ------------------------------------ ----------- ------------------------------
    fal_client string dbcdsl
    fal_server string
    SQL>
    SQL>
    SQL> alter system set fal_server='cstdby';
    System altered.
    SQL>
    SQL> show parameter fal
    NAME TYPE VALUE
    ------------------------------------ ----------- ------------------------------
    fal_client string dbcdsl
    fal_server string cstdby

    SQL> alter system switch logfile;
    System altered.
    SQL> /
    System altered.
    SQL> alter system set log_archive_dest_state_2='defer';
    System altered.
    SQL> alter system set log_archive_dest_state_2='enable';
    System altered.
    SQL> select max(sequence#) from v$archived_log;
    MAX(SEQUENCE#)
    --------------
    28809

    Error     16198     WARN: ARC8: Terminating ARCH (pid 15089) hung on a network operation     12/8/2012 10:23:40 AM
    Error     16198     WARN: ARCj: Terminating ARCH (pid 15089) hung on a network operation     12/8/2012 10:23:42 AM
    Error     16198     WARN: ARCr: Terminating ARCH (pid 12791) hung on a network operation     12/8/2012 10:25:51 AM
    Error     16198     WARN: ARCr: Terminating ARCH (pid 13713) hung on a network operation     12/8/2012 10:28:41 AM
    Error     16198     WARN: ARCr: Terminating ARCH (pid 15083) hung on a network operation     12/8/2012 10:33:46 AM
    Error     16198     WARN: ARCr: Terminating ARCH (pid 15975) hung on a network operation     12/8/2012 10:33:47 AM
    Error     16198     WARN: ARCr: Terminating ARCH (pid 14801) hung on a network operation     12/8/2012 10:38:54 AM
    Error     16198     WARN: ARCr: Terminating ARCH (pid 14162) hung on a network operation     12/8/2012 10:38:55 AM
    Error     16198     WARN: ARCr: Terminating ARCH (pid 13291) hung on a network operation     12/8/2012 10:38:56 AM
    Error     16198     WARN: ARCr: Terminating ARCH (pid 15979) hung on a network operation     12/8/2012 10:38:58 AM
    Error     16198     WARN: ARCr: Terminating ARCH (pid 15461) hung on a network operation     12/8/2012 10:38:59 AM
    Error     16198     WARN: ARCr: Terminating ARCH (pid 10536) hung on a network operation     12/8/2012 10:44:12 AM
    Error     16198     WARN: ARCr: Terminating ARCH (pid 13018) hung on a network operation     12/8/2012 10:44:13 AM
    Error     16198     WARN: ARCr: Terminating ARCH (pid 15081) hung on a network operation     12/8/2012 10:44:15 AM
    Error     16198     WARN: ARCr: Terminating ARCH (pid 16737) hung on a network operation     12/8/2012 10:44:16 AM
    Error     16198     WARN: ARCr: Terminating ARCH (pid 12274) hung on a network operation     12/8/2012 10:45:52 AM
    Error     16198     WARN: ARCr: Terminating ARCH (pid 11065) hung on a network operation     12/8/2012 10:49:26 AM
    Error     16198     WARN: ARCr: Terminating ARCH (pid 14337) hung on a network operation     12/8/2012 10:49:28 AM
    Error     16198     WARN: ARCr: Terminating ARCH (pid 16009) hung on a network operation     12/8/2012 10:49:29 AM
    Error     16198     WARN: ARCr: Terminating ARCH (pid 17666) hung on a network operation     12/8/2012 10:54:38 AM
    Error     16198     WARN: ARCr: Terminating ARCH (pid 17243) hung on a network operation     12/8/2012 10:54:39 AM
    Error     16198     WARN: ARCr: Terminating ARCH (pid 16148) hung on a network operation     12/8/2012 10:59:45 AM
    Error     16198     WARN: ARCr: Terminating ARCH (pid 13289) hung on a network operation     12/8/2012 10:59:47 AM
    Error     16198     WARN: ARCr: Terminating ARCH (pid 16739) hung on a network operation     12/8/2012 10:59:48 AM
    Error     16198     WARN: ARCr: Terminating ARCH (pid 17245) hung on a network operation     12/8/2012 10:59:50 AM
    Error     16198     WARN: ARCr: Terminating ARCH (pid 17247) hung on a network operation     12/8/2012 10:59:51 AM
    Error     16198     WARN: ARC7: Terminating ARCH (pid 14158) hung on a network operation     12/8/2012 11:00:03 AM
    Error     16198     WARN: ARCf: Terminating ARCH (pid 14158) hung on a network operation     12/8/2012 11:00:04 AM
    Error     16198     WARN: ARCr: Terminating ARCH (pid 18503) hung on a network operation     12/8/2012 11:05:04 AM
    Error     16198     WARN: ARCr: Terminating ARCH (pid 16344) hung on a network operation     12/8/2012 11:05:05 AM
    Error     16198     WARN: ARCr: Terminating ARCH (pid 17668) hung on a network operation     12/8/2012 11:05:06 AM
    Error     16198     WARN: ARCr: Terminating ARCH (pid 13020) hung on a network operation     12/8/2012 11:05:08 AM
    Error     16198     WARN: ARCr: Terminating ARCH (pid 15085) hung on a network operation     12/8/2012 11:05:09 AM
    Error     16198     WARN: ARCr: Terminating ARCH (pid 15977) hung on a network operation     12/8/2012 11:05:10 AM
    Error     16198     WARN: ARC9: Terminating ARCH (pid 14333) hung on a network operation     12/8/2012 11:05:24 AM
    Error     16198     WARN: ARCl: Terminating ARCH (pid 14333) hung on a network operation     12/8/2012 11:05:25 AM
    Error     16198     WARN: ARCr: Terminating ARCH (pid 18505) hung on a network operation     12/8/2012 11:10:25 AM
    Error     16198     WARN: ARCr: Terminating ARCH (pid 13728) hung on a network operation     12/8/2012 11:10:26 AM
    Error     16198     WARN: ARCr: Terminating ARCH (pid 14156) hung on a network operation     12/8/2012 11:14:33 AM
    Error     16198     WARN: ARCr: Terminating ARCH (pid 17664) hung on a network operation     12/8/2012 11:14:34 AM
    Error     16198     WARN: ARCr: Terminating ARCH (pid 17239) hung on a network operation     12/8/2012 11:14:35 AM
    Error     16198     WARN: ARCr: Terminating ARCH (pid 17241) hung on a network operation     12/8/2012 11:14:37 AM
    Error     16198     WARN: ARCr: Terminating ARCH (pid 18057) hung on a network operation     12/8/2012 11:14:38 AM
    Error     16198     WARN: ARCr: Terminating ARCH (pid 19408) hung on a network operation     12/8/2012 11:14:40 AM
    Error     16198     WARN: ARC0: Terminating ARCH (pid 19926) hung on a network operation     12/8/2012 11:14:53 AM
    Error     16198     WARN: ARC2: Terminating ARCH (pid 19926) hung on a network operation     12/8/2012 11:14:54 AM
    Error     16198     WARN: ARC2: Terminating ARCH (pid 18951) hung on a network operation     12/8/2012 11:17:09 AM
    Error     16198     WARN: ARC2: Terminating ARCH (pid 18955) hung on a network operation     12/8/2012 11:18:17 AM
    Error     16198     WARN: ARC2: Terminating ARCH (pid 18959) hung on a network operation     12/8/2012 11:19:23 AM
    Error     16198     WARN: ARC0: Terminating ARCH (pid 18974) hung on a network operation     12/8/2012 11:19:53 AM
    Error     16198     WARN: ARC5: Terminating ARCH (pid 18974) hung on a network operation     12/8/2012 11:19:54 AM
    Error     16198     WARN: ARC2: Terminating ARCH (pid 18061) hung on a network operation     12/8/2012 11:20:28 AM
    Error     16198     WARN: ARC2: Terminating ARCH (pid 14160) hung on a network operation     12/8/2012 11:22:36 AM
    Error     16198     WARN: ARC2: Terminating ARCH (pid 15973) hung on a network operation     12/8/2012 11:25:52 AM
    Error     16198     WARN: ARC2: Terminating ARCH (pid 15079) hung on a network operation     12/8/2012 11:26:57 AM
    Error     16198     WARN: ARC2: Terminating ARCH (pid 15981) hung on a network operation     12/8/2012 11:26:59 AM
    Error     16198     WARN: ARC2: Terminating ARCH (pid 19404) hung on a network operation     12/8/2012 11:28:06 AM
    Error     16198     WARN: ARC2: Terminating ARCH (pid 20540) hung on a network operation     12/8/2012 11:28:07 AM
    Error     16198     WARN: ARC2: Terminating ARCH (pid 15971) hung on a network operation     12/8/2012 11:29:15 AM
    Error     16198     WARN: ARC2: Terminating ARCH (pid 19924) hung on a network operation     12/8/2012 11:30:24 AM

    Primary alert log

    Current log# 1 seq# 28809 mem# 0: /u01/app/oracle/oradata/dbcdsl/redo01.log
    Current log# 1 seq# 28809 mem# 1: /u01/app/oracle/oradata/dbcdsl/redo01b.log
    Current log# 1 seq# 28809 mem# 2: /u01/app/oracle/oradata/dbcdsl/redo01c.log
    2012-12-08 11:15:05.474000 +05:30
    Thread 1 advanced to log sequence 28810 (LGWR switch)
    Current log# 3 seq# 28810 mem# 0: /u01/app/oracle/oradata/dbcdsl/redo03.log
    Current log# 3 seq# 28810 mem# 1: /u01/app/oracle/oradata/dbcdsl/redo03b.log
    Current log# 3 seq# 28810 mem# 2: /u01/app/oracle/oradata/dbcdsl/redo03c.log
    Archived Log entry 61944 added for thread 1 sequence 28809 ID 0xebf51104 dest 1:
    2012-12-08 11:17:09.974000 +05:30
    WARN: ARC2: Terminating ARCH (pid 18951) hung on a network operation
    2012-12-08 11:17:11.351000 +05:30
    krsv_proc_kill: Killing 249108103169 processes (Process by index)
    2012-12-08 11:17:13.355000 +05:30
    ARC2: Detected ARCH process failure
    ARC2: STARTING ARCH PROCESSES
    ARC7 started with pid=46, OS id=20540
    ARC7: Archival started
    ARC2: STARTING ARCH PROCESSES COMPLETE
    Reclaiming FAL entry from dead process [pid 18951]
    2012-12-08 11:18:17.159000 +05:30
    WARN: ARC2: Terminating ARCH (pid 18955) hung on a network operation
    2012-12-08 11:18:18.537000 +05:30
    krsv_proc_kill: Killing 249108103169 processes (Process by index)
    2012-12-08 11:18:20.541000 +05:30
    ARC2: Detected ARCH process failure
    ARC2: STARTING ARCH PROCESSES
    ARCk started with pid=26, OS id=20613
    2012-12-08 11:18:21.561000 +05:30
    ARCk: Archival started
    ARC2: STARTING ARCH PROCESSES COMPLETE
    Reclaiming FAL entry from dead process [pid 18955]
    2012-12-08 11:19:23.087000 +05:30
    WARN: ARC2: Terminating ARCH (pid 18959) hung on a network operation
    2012-12-08 11:19:24.458000 +05:30
    krsv_proc_kill: Killing 249108103169 processes (Process by index)
    2012-12-08 11:19:26.462000 +05:30
    ARC2: Detected ARCH process failure
    ARC2: STARTING ARCH PROCESSES
    ARCt started with pid=73, OS id=20703
    ARCt: Archival started
    ARC2: STARTING ARCH PROCESSES COMPLETE
    Reclaiming FAL entry from dead process [pid 18959]
    2012-12-08 11:19:53.563000 +05:30
    WARN: ARC0: Terminating ARCH (pid 18974) hung on a network operation
    2012-12-08 11:19:54.978000 +05:30
    krsv_proc_kill: Killing 249108103169 processes (Process by index)
    WARN: ARC5: Terminating ARCH (pid 18974) hung on a network operation
    ARCb: Detected ARCH process failure
    ARCb: STARTING ARCH PROCESSES
    Reclaiming FAL entry from dead process [pid 18974]
    FAL[server, ARC5]: FAL archive failed, see trace file.
    ARC6 started with pid=84, OS id=20740
    2012-12-08 11:19:56.022000 +05:30
    ARC6: Archival started
    ARCb: STARTING ARCH PROCESSES COMPLETE
    2012-12-08 11:20:28.995000 +05:30
    WARN: ARC2: Terminating ARCH (pid 18061) hung on a network operation
    2012-12-08 11:20:30.379000 +05:30
    krsv_proc_kill: Killing 249108103169 processes (Process by index)
    2012-12-08 11:20:32.385000 +05:30
    ARC2: Detected ARCH process failure
    ARC2: STARTING ARCH PROCESSES
    ARCq started with pid=82, OS id=20775
    2012-12-08 11:20:33.405000 +05:30
    ARCq: Archival started
    ARC2: STARTING ARCH PROCESSES COMPLETE
    Reclaiming FAL entry from dead process [pid 18061]
    2012-12-08 11:22:36.612000 +05:30
    WARN: ARC2: Terminating ARCH (pid 14160) hung on a network operation
    2012-12-08 11:22:38.019000 +05:30
    krsv_proc_kill: Killing 249108103169 processes (Process by index)
    2012-12-08 11:22:40.022000 +05:30
    ARC2: Detected ARCH process failure
    ARC2: STARTING ARCH PROCESSES
    ARCa started with pid=41, OS id=20993
    2012-12-08 11:22:41.042000 +05:30
    ARCa: Archival started
    ARC2: STARTING ARCH PROCESSES COMPLETE
    Reclaiming FAL entry from dead process [pid 14160]
    2012-12-08 11:25:52.126000 +05:30
    WARN: ARC2: Terminating ARCH (pid 15973) hung on a network operation
    2012-12-08 11:25:53.497000 +05:30
    krsv_proc_kill: Killing 249108103169 processes (Process by index)
    2012-12-08 11:25:55.500000 +05:30
    ARC2: Detected ARCH process failure
    ARC2: STARTING ARCH PROCESSES
    ARCj started with pid=87, OS id=21248
    2012-12-08 11:25:56.519000 +05:30
    ARCj: Archival started
    ARC2: STARTING ARCH PROCESSES COMPLETE
    Reclaiming FAL entry from dead process [pid 15973]
    2012-12-08 11:26:57.859000 +05:30
    WARN: ARC2: Terminating ARCH (pid 15079) hung on a network operation
    2012-12-08 11:26:59.236000 +05:30
    WARN: ARC2: Terminating ARCH (pid 15981) hung on a network operation
    2012-12-08 11:27:00.595000 +05:30
    krsv_proc_kill: Killing 249108103169 processes (Process by index)
    2012-12-08 11:27:02.601000 +05:30
    krsv_proc_kill: Killing 249108103169 processes (Process by index)
    2012-12-08 11:27:04.603000 +05:30
    ARC2: Detected ARCH process failure
    ARC2: Detected ARCH process failure
    ARC2: STARTING ARCH PROCESSES
    ARC4 started with pid=34, OS id=21361
    ARC4: Archival started
    ARCs started with pid=89, OS id=21363
    Reclaiming FAL entry from dead process [pid 15079]
    2012-12-08 11:27:05.642000 +05:30
    ARCs: Archival started
    ARC2: STARTING ARCH PROCESSES COMPLETE
    Reclaiming FAL entry from dead process [pid 15981]
    2012-12-08 11:28:06.376000 +05:30
    WARN: ARC2: Terminating ARCH (pid 19404) hung on a network operation
    2012-12-08 11:28:07.734000 +05:30
    WARN: ARC2: Terminating ARCH (pid 20540) hung on a network operation
    2012-12-08 11:28:09.095000 +05:30
    krsv_proc_kill: Killing 249108103169 processes (Process by index)
    2012-12-08 11:28:11.098000 +05:30
    krsv_proc_kill: Killing 249108103169 processes (Process by index)
    2012-12-08 11:28:13.100000 +05:30
    ARC2: Detected ARCH process failure
    ARC2: Detected ARCH process failure
    ARC2: STARTING ARCH PROCESSES
    ARC7 started with pid=46, OS id=21438
    ARC7: Archival started
    ARCd started with pid=80, OS id=21440
    Reclaiming FAL entry from dead process [pid 19404]
    2012-12-08 11:28:14.137000 +05:30
    ARCd: Archival started
    ARC2: STARTING ARCH PROCESSES COMPLETE
    Reclaiming FAL entry from dead process [pid 20540]
    2012-12-08 11:29:15.167000 +05:30
    WARN: ARC2: Terminating ARCH (pid 15971) hung on a network operation
    2012-12-08 11:29:16.537000 +05:30
    krsv_proc_kill: Killing 249108103169 processes (Process by index)
    2012-12-08 11:29:18.540000 +05:30
    ARC2: Detected ARCH process failure
    ARC2: STARTING ARCH PROCESSES
    ARC8 started with pid=48, OS id=21540
    2012-12-08 11:29:19.559000 +05:30
    ARC8: Archival started
    ARC2: STARTING ARCH PROCESSES COMPLETE
    Reclaiming FAL entry from dead process [pid 15971]
    2012-12-08 11:30:24.045000 +05:30
    WARN: ARC2: Terminating ARCH (pid 19924) hung on a network operation
    2012-12-08 11:30:25.483000 +05:30
    krsv_proc_kill: Killing 249108103169 processes (Process by index)
    2012-12-08 11:30:27.485000 +05:30
    ARC2: Detected ARCH process failure
    ARC2: STARTING ARCH PROCESSES
    ARCc started with pid=72, OS id=21635
    ARCc: Archival started
    ARC2: STARTING ARCH PROCESSES COMPLETE
    Reclaiming FAL entry from dead process [pid 19924]
    2012-12-08 11:32:32.881000 +05:30
    WARN: ARC2: Terminating ARCH (pid 19427) hung on a network operation
    2012-12-08 11:32:34.258000 +05:30
    WARN: ARC2: Terminating ARCH (pid 18957) hung on a network operation
    2012-12-08 11:32:35.678000 +05:30
    krsv_proc_kill: Killing 249108103169 processes (Process by index)
    2012-12-08 11:32:37.680000 +05:30
    krsv_proc_kill: Killing 249108103169 processes (Process by index)
    2012-12-08 11:32:39.684000 +05:30
    ARC2: Detected ARCH process failure
    ARC2: Detected ARCH process failure
    ARC2: STARTING ARCH PROCESSES
    ARCi started with pid=83, OS id=21868
    ARCp started with pid=85, OS id=21870
    ARCi: Archival started
    Reclaiming FAL entry from dead process [pid 19427]
    2012-12-08 11:32:40.721000 +05:30
    ARCp: Archival started
    ARC2: STARTING ARCH PROCESSES COMPLETE
    Reclaiming FAL entry from dead process [pid 18957]

    At Stand by

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

    MAX(SEQUENCE#)
    --------------
    28549

    SQL>

    Stand by Alert

    RFS[2702]: Assigned to RFS process 2889
    RFS[2702]: Identified database type as 'physical standby': Client is ARCH pid 20 265
    RFS[2688]: Possible network disconnect with primary database
    Deleted Oracle managed file /u01/app/oracle/flash_recovery_area/CSTDBY/archivelo g/2012_12_08/o1_mf_1_28560_8d5lkxr7_.arc
    2012-12-08 10:51:06.102000 +05:30
    Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST
    RFS[2703]: Assigned to RFS process 2887
    RFS[2703]: Identified database type as 'physical standby': Client is ARCH pid 20 540
    2012-12-08 10:51:08.150000 +05:30
    RFS[2703]: Opened log for thread 1 sequence 28560 dbid -336253692 branch 7678964 55
    2012-12-08 10:52:06.104000 +05:30
    Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST
    2012-12-08 10:52:09.993000 +05:30
    RFS[2683]: Possible network disconnect with primary database
    Deleted Oracle managed file /u01/app/oracle/flash_recovery_area/CSTDBY/archivelog/2012_12_08/o1_mf_1_28705_8d5lksf7_.arc
    RFS[2704]: Assigned to RFS process 2903
    RFS[2704]: Identified database type as 'physical standby': Client is ARCH pid 20265
    2012-12-08 10:52:11.183000 +05:30
    RFS[2705]: Assigned to RFS process 2905
    RFS[2705]: Identified database type as 'physical standby': Client is ARCH pid 20613
    RFS[2705]: Opened log for thread 1 sequence 28705 dbid -336253692 branch 767896455
    2012-12-08 10:53:06.106000 +05:30
    Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST
    2012-12-08 10:53:15.832000 +05:30
    RFS[2706]: Assigned to RFS process 2921
    RFS[2706]: Identified database type as 'physical standby': Client is ARCH pid 20703
    RFS[2707]: Assigned to RFS process 2923
    RFS[2707]: Identified database type as 'physical standby': Client is ARCH pid 20265
    2012-12-08 10:53:17.927000 +05:30
    RFS[2685]: Possible network disconnect with primary database
    Deleted Oracle managed file /u01/app/oracle/flash_recovery_area/CSTDBY/archivelog/2012_12_08/o1_mf_1_28701_8d5lksxv_.arc
    RFS[2706]: Opened log for thread 1 sequence 28701 dbid -336253692 branch 767896455
    2012-12-08 10:53:52.467000 +05:30
    RFS[2686]: Possible network disconnect with primary database
    Deleted Oracle managed file /u01/app/oracle/flash_recovery_area/CSTDBY/archivelog/2012_12_08/o1_mf_1_28580_8d5lkyb5_.arc
    2012-12-08 10:54:06.109000 +05:30
    Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST
    2012-12-08 10:52:09.993000 +05:30
    RFS[2683]: Possible network disconnect with primary database
    Deleted Oracle managed file /u01/app/oracle/flash_recovery_area/CSTDBY/archivelog/2012_12_08/o1_mf_1_28705_8d5lksf7_.arc
    RFS[2704]: Assigned to RFS process 2903
    RFS[2704]: Identified database type as 'physical standby': Client is ARCH pid 20265
    2012-12-08 10:52:11.183000 +05:30
    RFS[2705]: Assigned to RFS process 2905
    RFS[2705]: Identified database type as 'physical standby': Client is ARCH pid 20613
    RFS[2705]: Opened log for thread 1 sequence 28705 dbid -336253692 branch 767896455
    2012-12-08 10:53:06.106000 +05:30
    Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST
    2012-12-08 10:53:15.832000 +05:30
    RFS[2706]: Assigned to RFS process 2921
    RFS[2706]: Identified database type as 'physical standby': Client is ARCH pid 20703
    RFS[2707]: Assigned to RFS process 2923
    RFS[2707]: Identified database type as 'physical standby': Client is ARCH pid 20265
    2012-12-08 10:53:17.927000 +05:30
    RFS[2685]: Possible network disconnect with primary database
    Deleted Oracle managed file /u01/app/oracle/flash_recovery_area/CSTDBY/archivelog/2012_12_08/o1_mf_1_28701_8d5lksxv_.arc
    RFS[2706]: Opened log for thread 1 sequence 28701 dbid -336253692 branch 767896455
    2012-12-08 10:53:52.467000 +05:30
    RFS[2686]: Possible network disconnect with primary database
    Deleted Oracle managed file /u01/app/oracle/flash_recovery_area/CSTDBY/archivelog/2012_12_08/o1_mf_1_28580_8d5lkyb5_.arc
    2012-12-08 10:54:21.560000 +05:30
    RFS[2708]: Assigned to RFS process 2947
    RFS[2708]: Identified database type as 'physical standby': Client is ARCH pid 20775
    RFS[2709]: Assigned to RFS process 2949
    RFS[2709]: Identified database type as 'physical standby': Client is ARCH pid 20265
    2012-12-08 10:54:22.861000 +05:30
    RFS[2710]: Assigned to RFS process 2951
    RFS[2710]: Identified database type as 'physical standby': Client is ARCH pid 20288
    RFS[2710]: Opened log for thread 1 sequence 28580 dbid -336253692 branch 767896455
    2012-12-08 10:55:06.111000 +05:30
    Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST
    2012-12-08 10:55:10.409000 +05:30
    RFS[2680]: Possible network disconnect with primary database
    Deleted Oracle managed file /u01/app/oracle/flash_recovery_area/CSTDBY/archivelog/2012_12_08/o1_mf_1_28579_8d5ky9do_.arc
    RFS[2708]: Opened log for thread 1 sequence 28579 dbid -336253692 branch 767896455
    2012-12-08 10:55:23.895000 +05:30
    RFS[2711]: Assigned to RFS process 2968
    RFS[2711]: Identified database type as 'physical standby': Client is ARCH pid 20265
    2012-12-08 10:56:06.113000 +05:30
    Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST
    2012-12-08 10:56:29.665000 +05:30
    RFS[2637]: Possible network disconnect with primary database
    Deleted Oracle managed file /u01/app/oracle/flash_recovery_area/CSTDBY/archivelog/2012_12_08/o1_mf_1_28616_8d5h6cvo_.arc
    2012-12-08 10:56:33.495000 +05:30
    RFS[2712]: Assigned to RFS process 2982
    RFS[2712]: Identified database type as 'physical standby': Client is ARCH pid 20265
    2012-12-08 10:56:34.890000 +05:30
    RFS[2713]: Assigned to RFS process 2980
    RFS[2713]: Identified database type as 'physical standby': Client is ARCH pid 20993
    RFS[2713]: Opened log for thread 1 sequence 28616 dbid -336253692 branch 767896455
    2012-12-08 10:57:06.124000 +05:30
    Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST
    2012-12-08 10:57:35.216000 +05:30
    RFS[2714]: Assigned to RFS process 2995
    RFS[2714]: Identified database type as 'physical standby': Client is ARCH pid 20265
    2012-12-08 10:58:06.136000 +05:30
    Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST
    2012-12-08 10:58:39.363000 +05:30
    RFS[2715]: Assigned to RFS process 3019
    RFS[2715]: Identified database type as 'physical standby': Client is ARCH pid 20265
    2012-12-08 10:59:06.147000 +05:30
    Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST
    2012-12-08 10:59:43.584000 +05:30
    RFS[2656]: Possible network disconnect with primary database
    Deleted Oracle managed file /u01/app/oracle/flash_recovery_area/CSTDBY/archivelog/2012_12_08/o1_mf_1_28551_8d5jfmmj_.arc
    RFS[2716]: Assigned to RFS process 3038
    RFS[2716]: Identified database type as 'physical standby': Client is ARCH pid 21248
    2012-12-08 10:59:44.955000 +05:30
    RFS[2716]: Opened log for thread 1 sequence 28551 dbid -336253692 branch 767896455
    RFS[2717]: Assigned to RFS process 3040
    RFS[2717]: Identified database type as 'physical standby': Client is ARCH pid 20265
    2012-12-08 11:00:06.158000 +05:30
    Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST
    2012-12-08 11:00:50.084000 +05:30
    RFS[2651]: Possible network disconnect with primary database
    Deleted Oracle managed file /u01/app/oracle/flash_recovery_area/CSTDBY/archivelog/2012_12_08/o1_mf_1_28657_8d5ht1l8_.arc
    2012-12-08 11:00:53.153000 +05:30
    RFS[2661]: Possible network disconnect with primary database
    Deleted Oracle managed file /u01/app/oracle/flash_recovery_area/CSTDBY/archivelog/2012_12_08/o1_mf_1_28700_8d5jfn96_.arc
    RFS[2718]: Assigned to RFS process 3060
    RFS[2718]: Identified database type as 'physical standby': Client is ARCH pid 20265
    2012-12-08 11:00:54.952000 +05:30
    RFS[2719]: Assigned to RFS process 3058
    RFS[2719]: Identified database type as 'physical standby': Client is ARCH pid 21361
    RFS[2719]: Opened log for thread 1 sequence 28657 dbid -336253692 branch 767896455
    2012-12-08 11:00:57.921000 +05:30
    RFS[2720]: Assigned to RFS process 3062
    RFS[2720]: Identified database type as 'physical standby': Client is ARCH pid 21363
    RFS[2720]: Opened log for thread 1 sequence 28700 dbid -336253692 branch 767896455
    2012-12-08 11:01:06.170000 +05:30
    Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST
    2012-12-08 11:02:00.728000 +05:30
    RFS[2703]: Possible network disconnect with primary database
    Deleted Oracle managed file /u01/app/oracle/flash_recovery_area/CSTDBY/archivelog/2012_12_08/o1_mf_1_28560_8d5ml43d_.arc
    RFS[2694]: Possible network disconnect with primary database
    Deleted Oracle managed file /u01/app/oracle/flash_recovery_area/CSTDBY/archivelog/2012_12_08/o1_mf_1_28699_8d5lvwhw_.arc
    RFS[2721]: Assigned to RFS process 3087
    RFS[2721]: Identified database type as 'physical standby': Client is ARCH pid 21438
    RFS[2721]: Opened log for thread 1 sequence 28699 dbid -336253692 branch 767896455
    2012-12-08 11:02:02.109000 +05:30
    RFS[2722]: Assigned to RFS process 3089
    RFS[2722]: Identified database type as 'physical standby': Client is ARCH pid 21440
    RFS[2723]: Assigned to RFS process 3091
    RFS[2723]: Identified database type as 'physical standby': Client is ARCH pid 20265
    RFS[2722]: Opened log for thread 1 sequence 28560 dbid -336253692 branch 767896455
    2012-12-08 11:02:06.172000 +05:30
    Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST
    2012-12-08 11:03:06.183000 +05:30
    Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST
    2012-12-08 11:03:11.021000 +05:30
    RFS[2724]: Assigned to RFS process 3105
    RFS[2724]: Identified database type as 'physical standby': Client is ARCH pid 20265
    RFS[2725]: Assigned to RFS process 3107
    RFS[2725]: Identified database type as 'physical standby': Client is ARCH pid 21540
    2012-12-08 11:03:39.553000 +05:30
    RFS[2662]: Possible network disconnect with primary database
    Deleted Oracle managed file /u01/app/oracle/flash_recovery_area/CSTDBY/archivelog/2012_12_08/o1_mf_1_28712_8d5jfqgv_.arc
    2012-12-08 11:03:40.629000 +05:30
    RFS[2725]: Opened log for thread 1 sequence 28712 dbid -336253692 branch 767896455
    2012-12-08 11:04:06.186000 +05:30
    Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST
    2012-12-08 11:04:15.880000 +05:30
    RFS[2726]: Assigned to RFS process 3135
    RFS[2726]: Identified database type as 'physical standby': Client is ARCH pid 21635
    RFS[2727]: Assigned to RFS process 3137
    RFS[2727]: Identified database type as 'physical standby': Client is ARCH pid 20265
    2012-12-08 11:04:19.988000 +05:30
    RFS[2697]: Possible network disconnect with primary database
    Deleted Oracle managed file /u01/app/oracle/flash_recovery_area/CSTDBY/archivelog/2012_12_08/o1_mf_1_28550_8d5m5gvn_.arc
    RFS[2726]: Opened log for thread 1 sequence 28550 dbid -336253692 branch 767896455
    2012-12-08 11:05:06.188000 +05:30
    Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST
    2012-12-08 11:05:19.701000 +05:30
    RFS[2728]: Assigned to RFS process 3152
    RFS[2728]: Identified database type as 'physical standby': Client is ARCH pid 20265
    2012-12-08 11:06:06.200000 +05:30
    Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST
    2012-12-08 11:06:27.844000 +05:30
    RFS[2729]: Assigned to RFS process 3164
    RFS[2729]: Identified database type as 'physical standby': Client is ARCH pid 21868
    krsv_proc_kill: Killing 1 processes (idle RFS by thread/sequence)
    RFS[2687]: Possible network disconnect with primary database
    Deleted Oracle managed file /u01/app/oracle/flash_recovery_area/CSTDBY/archivelog/2012_12_08/o1_mf_1_28708_8d5lktfy_.arc
    2012-12-08 11:06:28.953000 +05:30
    Deleted Oracle managed file /u01/app/oracle/flash_recovery_area/CSTDBY/archivelog/2012_12_08/o1_mf_1_28704_8d5lw12o_.arc
    2012-12-08 11:06:30.321000 +05:30
    RFS[2729]: Opened log for thread 1 sequence 28704 dbid -336253692 branch 767896455
    2012-12-08 11:06:32.352000 +05:30
    RFS[2730]: Assigned to RFS process 3172
    RFS[2730]: Identified database type as 'physical standby': Client is ARCH pid 20265
    RFS[2731]: Assigned to RFS process 3170
    RFS[2731]: Identified database type as 'physical standby': Client is ARCH pid 21870
    RFS[2731]: Opened log for thread 1 sequence 28708 dbid -336253692 branch 767896455
    2012-12-08 11:07:06.202000 +05:30
    Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST
    2012-12-08 11:07:32.035000 +05:30
    RFS[2732]: Assigned to RFS process 3183
    RFS[2732]: Identified database type as 'physical standby': Client is ARCH pid 20263
    RFS[2732]: Opened log for thread 1 sequence 28810 dbid -336253692 branch 767896455
    2012-12-08 11:07:33.908000 +05:30
    RFS[2733]: Assigned to RFS process 3186
    RFS[2733]: Identified database type as 'physical standby': Client is ARCH pid 20265
    2012-12-08 11:08:06.213000 +05:30
    Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST
    2012-12-08 11:08:42.394000 +05:30
    RFS[2734]: Assigned to RFS process 3215
    RFS[2734]: Identified database type as 'physical standby': Client is ARCH pid 22026
    RFS[2735]: Assigned to RFS process 3217
    RFS[2735]: Identified database type as 'physical standby': Client is ARCH pid 20265
    RFS[2705]: Possible network disconnect with primary database
    Deleted Oracle managed file /u01/app/oracle/flash_recovery_area/CSTDBY/archivelog/2012_12_08/o1_mf_1_28705_8d5mn3jl_.arc
    2012-12-08 11:08:43.826000 +05:30
    RFS[2734]: Opened log for thread 1 sequence 28705 dbid -336253692 branch 767896455
    RFS[2706]: Possible network disconnect with primary database
    Deleted Oracle managed file /u01/app/oracle/flash_recovery_area/CSTDBY/archivelog/2012_12_08/o1_mf_1_28701_8d5mp63t_.arc
    2012-12-08 11:08:45.045000 +05:30
    RFS[2736]: Assigned to RFS process 3213
    RFS[2736]: Identified database type as 'physical standby': Client is ARCH pid 22024
    RFS[2736]: Opened log for thread 1 sequence 28701 dbid -336253692 branch 767896455


    Can this happend due to network traffic shape? Primarie's daily archive size around 1.5 GB. Avarage archive log size 35 M. Network link between two servers 2.5 M

    Thank you very much for your great help.

    Rgds,
    Athurumithuru.
  • 23. Re: Recreate Standby using full datafile backup
    CKPT Guru
    Currently Being Moderated
    RFS[2685]: Possible network disconnect with primary database
    Deleted Oracle managed file /u01/app/oracle/flash_recovery_area/CSTDBY/archivelog/2012_12_08/o1_mf_1_28701_8d5lksxv_.arc
    You seems to have severe network problem,
    Never consider on average archivelog file size, always look at what is the Redo log file size you have configured? look at tuning network using SDU,
    Check this link for network best practices http://www.oracle.com/technetwork/database/features/availability/maa-wp-10gr2-dataguardnetworkbestpr-134557.pdf

    Also try this workaround by using "REOPEN" to less value in LOG_ARCHIVE_DEST_2 of primary.
    Hope this helps.
  • 24. Re: Recreate Standby using full datafile backup
    Athurumithuru Newbie
    Currently Being Moderated
    Dear CKPT,

    Thank you very much for your support. You are great. I'll be looking forward to solve this issue with network guys.

    Rgds,
    Athurumithuru.
1 2 Previous Next

Legend

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