Standby redo logs status

Hi, I see following status from my standby redo logs
SQL> select GROUP#, status from V$STANDBY_LOG;
GROUP# STATUS
5 UNASSIGNED
6 UNASSIGNED
7 UNASSIGNED
8 UNASSIGNED
What could be reason for this.

Log file which are unassigned mean the Online redo log has never been written to. This is the state of a redo log that was just added, or just after a RESETLOGS when it is not the current redo log
http://www.mcs.csueastbay.edu/support/oracle/doc/10.2/server.102/b14237/dynviews_2134.htm

Similar Messages

  • Standby redo log status

    Can anyone explain what the status of clearing means when viewing standby redo log status?
    SQL> select status from v$log;
    STATUS
    CLEARING
    CLEARING
    CURRENT
    This is a bit different to what we'd see on an open database.

    Hello;
    Log is being re-created as an empty log.
    In a Standby database the regular redo are not used ( when not in PRIMARY MODE) only the standby redo logs are used. Sometimes as buffers for the redo coming from the primary.
    You should be able to change the status by doing a ALTER SYSTEM SWITCH LOGFILE on your primary.
    This note may help:
    Online Redo Logs on Physical Standby [ID 740675.1]
    Also
    Take a look at v$standby_log too.
    http://docs.oracle.com/cd/B28359_01/server.111/b28320/dynviews_3068.htm
    Best Regards
    mseberg

  • Unassigned Status Of Standby Redo Log Files

    I created 2 standby redo log groups, and use LGWR in primary site to
    transfer redo data, all are good. But when I query the V$STANDBY_LOG
    view, I found that the status column of my both standby redo logs is UNASSIGNED".
    also sequence#
    THREAD# and all others are 0 and 0.
    Any explains.

    Thanks for the reply Sophie. I did perform log switch at my primary site but the status of standby redo log files remained unassinged. I am pasting here the message in my Alert Log file may be that can help you to diagonose the problem.
    ALTER DATABASE SET STANDBY DATABASE PROTECTED
    Tue Jul 26 15:35:18 2005
    Completed: ALTER DATABASE SET STANDBY DATABASE PROTECTED
    Tue Jul 26 15:35:22 2005
    ALTER DATABASE OPEN
    Tue Jul 26 15:35:23 2005
    LGWR: Primary database is in CLUSTER CONSISTENT mode
    LGWR: Primary database is in MAXIMUM PROTECTION mode
    LGWR: Destination LOG_ARCHIVE_DEST_1 is not serviced by LGWR
    LNS0 started with pid=18
    Tue Jul 26 15:35:28 2005
    LGWR: Error 16086 verifying archivelog destination LOG_ARCHIVE_DEST_2
    LGWR: Continuing...
    Tue Jul 26 15:35:28 2005
    Errors in file e:\oracle\admin\test\bdump\test_lgwr_1864.trc:
    ORA-16086: standby database does not contain available standby log files
    LGWR: Error 16086 disconnecting from destination LOG_ARCHIVE_DEST_2 standby host 'TESTstdb'
    LGWR: Minimum of 1 applicable standby database required
    Tue Jul 26 15:35:28 2005
    Errors in file e:\oracle\admin\test\bdump\test_lgwr_1864.trc:
    ORA-16072: a minimum of one standby database destination is required
    LGWR: terminating instance due to error 16072
    Instance terminated by LGWR, pid = 1864

  • Physical standby database standby redo log problem

    Hello
    We have a physical standby database , I've created some standby redo log files but my problem is that they aren't used,
    their status in v$stanby_log view is UNASSIGNED
    and I see this message (ORA-16086: standby database does not contain available standby log files) in primary database alert_log file
    while when I run "alter system switch logfile" in the primary database it transfer redo logs to the physsical standby database
    and archive log file will be created in standby database
    I've even recreated the standby redo log files and I added new ones to them but the problem wasn't solved
    Do you know what is problem ?
    elect group#,THREAD#,BYTES,STATUS from V$STANDBY_LOG;
    group#     THREAD#      BYTES       STATUS
    1                   0                   524288000                   UNASSIGNED                  
    2                   0                   524288000                   UNASSIGNED                  
    3                   0                   524288000                   UNASSIGNED                  
    8                   0                   524288000                   UNASSIGNED                  
    9                   0                   524288000                   UNASSIGNED                  
    10                   0                   524288000                   UNASSIGNED                  
    select group#,THREAD#,BYTES,MEMBERS,STATUS from v$log;
    group#                    THREAD#                    BYTES                    MEMBERS                    STATUS
    4                   1                   524288000                   2                   CLEARING                  
    7                   1                   524288000                   2                   CLEARING_CURRENT                  
    6                   1                   524288000                   2                   CLEARING                  
    5                   1                   524288000                   2                   CLEARING                  
    thanks

    Hello Anurag
    Thank you for your reply
    I have found some issue in the standby database alert_log too , in the standby database alert_log it has been written:
    RFS[782]: Assigned to RFS process 3919
    RFS[782]: Identified database type as 'physical standby'
    Primary database is in MAXIMUM AVAILABILITY mode
    Standby controlfile consistent with primary
    Primary database is in MAXIMUM AVAILABILITY mode
    Standby controlfile consistent with primary
    RFS[782]: No standby redo logfiles selected (reason:6)
    Sun Jan 31 13:59:43 2010
    Errors in file /u01/app/oracle/admin/tehrep/udump/tehrep_rfs_3919.trc:
    ORA-16086: standby database does not contain available standby log files
    Sun Jan 31 13:59:48 2010
    RFS[781]: Archived Log: '/disks/sda/tehrep/archivelogs/1_6516_670414641.dbf'
    Sun Jan 31 13:59:50 2010
    and the context "/u01/app/oracle/admin/tehrep/udump/tehrep_rfs_3919.trc"  is below :
    +/u01/app/oracle/admin/tehrep/udump/tehrep_rfs_3919.trc+
    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
    With the Partitioning, OLAP and Data Mining options
    ORACLE_HOME = /u01/app/oracle/product/10.2.0/db_1
    System name:    Linux
    Node name:      linserver2.com
    Release:        2.6.9-42.ELsmp
    Version:        #1 SMP Wed Jul 12 23:27:17 EDT 2006
    Machine:        i686
    Instance name: tehrep
    Redo thread mounted by this instance: 1
    Oracle process number: 58
    Unix process pid: 3919, image: [email protected]
    *** SERVICE NAME:() 2010-01-31 13:59:43.865
    *** SESSION ID:(109.1225) 2010-01-31 13:59:43.865
    KCRRFLAS
    KCRRSNPS
    No space in recovery area for active standby redo logs
    The primary database is operating in MAXIMUM PROTECTION
    or MAXIMUM AVAILABILITY mode, and the standby database
    does not contain adequate disk space in the recovery area
    to safely archive the contents of the standby redo logfiles.
    ORA-16086: standby database does not contain available standby log files
    when I saw this line "No space in recovery area for active standby redo logs" I thought that STANDBY_ARCHIVE_DEST parameter points where that there is no enough space , but when I consider I found out that points a directory on disk a "sda" that has enough space , I don't know what that means
    by the way, at below I've written a section of the primary database alert_log context and "lgwr" trace file around Sun Jan 31 13:30:34 2010
    alert_log :
    ORA-16086: standby database does not contain available standby log files
    Sun Jan 31 13:30:34 2010
    LGWR: Failed to archive log 7 thread 1 sequence 6512 (16086)
    Thread 1 advanced to log sequence 6512
    Current log# 7 seq# 6512 mem# 0: /disks/sdb/tehrep/redo71.log
    Current log# 7 seq# 6512 mem# 1: /disks/sdd/tehrep/redo72.log
    LNSc started with pid=53, OS id=11451
    Sun Jan 31 13:36:34 2010
    Errors in file /u01/app/oracle/admin/tehrep/bdump/tehrep_lgwr_3692.trc:
    ORA-16086: standby database does not contain available standby log files
    Sun Jan 31 13:36:34 2010
    LGWR: Failed to archive log 5 thread 1 sequence 6513 (16086)
    Thread 1 advanced to log sequence 6513
    Current log# 5 seq# 6513 mem# 0: /disks/sdb/tehrep/redo51.log
    Current log# 5 seq# 6513 mem# 1: /disks/sdd/tehrep/redo52.log
    */u01/app/oracle/admin/tehrep/bdump/tehrep_lgwr_3692.trc file :*
    Error 16086 creating standby archive log file at host '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=linserver2.com
    +)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=tehrep_XPT.com)(INSTANCE_NAME=tehrep)(SERVER=dedicated)))'+
    *** 2010-01-31 13:30:34.712 60679 kcrr.c
    LGWR: Attempting destination LOG_ARCHIVE_DEST_3 network reconnect (16086)
    *** 2010-01-31 13:30:34.712 60679 kcrr.c
    LGWR: Destination LOG_ARCHIVE_DEST_3 network reconnect abandoned
    ORA-16086: standby database does not contain available standby log files
    *** 2010-01-31 13:30:34.712 60679 kcrr.c
    LGWR: Error 16086 creating archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=linserver2.com)(PORT=1521
    +)))(CONNECT_DATA=(SERVICE_NAME=tehrep_XPT.com)(INSTANCE_NAME=tehrep)(SERVER=dedicated)))'+
    *** 2010-01-31 13:30:34.712 58941 kcrr.c
    kcrrfail: dest:3 err:16086 force:0 blast:1
    Receiving message from LNSc
    *** 2010-01-31 13:30:34.718 55444 kcrr.c
    Making upidhs request to LNSc (ocis 0x0xb648db48). Begin time is <01/31/2010 13:30:30> and NET_TIMEOUT <180> seconds
    NetServer pid:11196
    *** 2010-01-31 13:30:38.718 55616 kcrr.c
    upidhs done status 0
    *** 2010-01-31 13:36:31.062
    LGWR: Archivelog for thread 1 sequence 6513 will NOT be compressed
    *** 2010-01-31 13:36:31.062 53681 kcrr.c
    +Initializing NetServer[LNSc] for dest=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=linserver2.com)(PORT=1521)))(CO+
    NNECT_DATA=(SERVICE_NAME=tehrep_XPT.com)(INSTANCE_NAME=tehrep)(SERVER=dedicated))) mode SYNC
    LNSc is not running anymore.
    New SYNC LNSc needs to be started
    Waiting for subscriber count on LGWR-LNSc channel to go to zero
    Subscriber count went to zero - time now is <01/31/2010 13:36:31>
    Starting LNSc ...
    Waiting for LNSc to initialize itself
    *** 2010-01-31 13:36:34.116 53972 kcrr.c
    +Netserver LNSc [pid 11451] for mode SYNC has been initialized+
    Performing a channel reset to ignore previous responses
    +Successfully started LNSc [pid 11451] for dest (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=linserver2.com)(PORT=1+
    +521)))(CONNECT_DATA=(SERVICE_NAME=tehrep_XPT.com)(INSTANCE_NAME=tehrep)(SERVER=dedicated))) mode SYNC ocis=0x0xb648db48+
    *** 2010-01-31 13:36:34.116 54475 kcrr.c
    +Making upiahm request to LNSc [pid 11451]: Begin Time is <01/31/2010 13:36:31>. NET_TIMEOUT = <180> seconds+
    Waiting for LNSc to respond to upiahm
    *** 2010-01-31 13:36:34.266 54639 kcrr.c
    upiahm connect done status is 0
    Receiving message from LNSc
    Receiving message from LNSc
    Destination LOG_ARCHIVE_DEST_3 is in STANDBY RESYNCHRONIZATION mode
    Receiving message from LNSc

  • The stubborn standby redo log

    I publish this question here, Due to the similarity between the technologies, and I know for you this is very familiar.
    I have a dowstreams which has four standbys redo log groups. One of these groups is still in a redo of the day 23/04/2010. This old redo is not filed, always there.
    this implies that the database downstreams only work with three groups of redo log and some oacaciones all these are in active status and at that time the view v $ archived_dest returns error for that destination (downstreams).
    The question is:
    how I can eliminate that standby redo log which is not being archived.
    Thank you very much for your attention

    I run this query
    SELECT GROUP#, THREAD#, SEQUENCE#, ARCHIVED, STATUS,FIRST_TIME FROM V$STANDBY_LOG;
    and it returns me
    GROUP#____THREAD#__SEQUENCE#__ARC__STATUS__________FIRST_TIME
    4___________ 1__________0_________NO____UNASSIGNED
    5 ___________1_________2760_______YES_____ACTIVE__________04/05/10
    6____________1________2328 _______YES______ACTIVE__________27/04/10 --> The stubborn redo
    7____________1__________0_________NO_____UNASSIGNED

  • Resizing online and standby redo log in dataguard setup.

    In 10gr2 dataguard i would like to increase redo logsize from 50M to 100M.
    on primary
    standby_file_management=manual
    added online redo groups with 100M
    log switched
    drop old one and readded with 100m
    deleted log added in step2.
    same for standby redo logs.
    On standby
    was able to resize standby redo logs.
    but cannot resize online redologs status is clearing or clearing_current.
    please comment. thanks.

    I assume you just had to wait until the Primary switched out of that online log so it became inactive at the standby as well? We track where the Primary is by marking the online redo log files at the standby as clearing_current so you can tell where the primary was at any given moment.
    Make sure you create new standby redo log files at the Primary and Standby to match the new online redo log file size.
    Larry

  • Standby Redo Log Groups

    I have a problem on my standby database.
    When I check the status of v$standby_log
    one loggroup by one is getting active.
    At the end all 15 loggroups have the status active and I get the message no logs of size #### available
    What is the reason that those logs are not written to disk ?
    MRP is running.
    database is in archivelogmode
    flashback is enabled
    Recover database using backup controlfile is not working
    archive log all not allowed the backup controlfile....

    This issue is normally found when the 'standby redo' log on the standby is not as large as the 'redo' log on the primary.
    Per oracle, all standby redo log size should be equal to or larger than the largest redo log on the primary database. Oracle recommends keeping all the redo logs and standby logs of the same size.
    Would you like to confirm all logs have been set as oracle mandates?
    Cheers.

  • Standby redo log does not exist...

    Hello,
    Oracle 11.2.0.2, running on Solaris
    This is kind of a continuation of a previous thread, but this is a different question:
    I have a DG configuration, with the primary database having 2 redo logs per redo log group.
    And, it has 2 redo logs for the standby redo log groups.
    But I just found out something very strange:
    For the standby redo log group, even though the database shows it has two redo log files per group, the second file does not actually exist on the file system.
    And, I have no idea where it is, or why the database is not complaining about it.
    See below:
    SQL> select * from v$logfile;
             GROUP# STATUS    TYPE    MEMBER                                        IS_
                 11           STANDBY /opt/oracle/oradata2/PROD/REDO01A_STDBY.log NO
                 11           STANDBY /opt/oracle/oradata3/PROD/REDO01B_STDBY.log NO    <== does not exist on file system
                 12           STANDBY /opt/oracle/oradata2/PROD/REDO02A_STDBY.log NO
                 12           STANDBY /opt/oracle/oradata3/PROD/REDO02B_STDBY.log NO    <== does not exist on file system
                 13           STANDBY /opt/oracle/oradata2/PROD/REDO03A_STDBY.log NO
                 13           STANDBY /opt/oracle/oradata3/PROD/REDO03B_STDBY.log NO    <== does not exist on file system
                 14           STANDBY /opt/oracle/oradata2/PROD/REDO04A_STDBY.log NO
                 14           STANDBY /opt/oracle/oradata3/PROD/REDO04B_STDBY.log NO    <== does not exist on file system
                 15           STANDBY /opt/oracle/oradata2/PROD/REDO05A_STDBY.log NO
                 15           STANDBY /opt/oracle/oradata3/PROD/REDO05B_STDBY.log NO    <== does not exist on file system
                  5           ONLINE  /opt/oracle/oradata1/PROD/REDO05A.log       NO
                  5           ONLINE  /opt/oracle/oradata2/PROD/REDO05B.log       NO
                  6           ONLINE  /opt/oracle/oradata1/PROD/REDO06A.log       NO
                  6           ONLINE  /opt/oracle/oradata2/PROD/REDO06B.log       NO
                  7           ONLINE  /opt/oracle/oradata1/PROD/REDO07A.log       NO
                  7           ONLINE  /opt/oracle/oradata2/PROD/REDO07B.log       NO
                  8           ONLINE  /opt/oracle/oradata1/PROD/REDO08A.log       NO
                  8           ONLINE  /opt/oracle/oradata2/PROD/REDO08B.log       NO
    18 rows selected.
    Notice below that the "B" redo logs do not exist.
    SQL> !ls -l /opt/oracle/oradata3/PROD/REDO01B_STDBY.log
    /opt/oracle/oradata3/PROD/REDO01B_STDBY.log: No such file or directory
    SQL> !ls -l /opt/oracle/oradata3/PROD/REDO02B_STDBY.log
    /opt/oracle/oradata3/PROD/REDO02B_STDBY.log: No such file or directory
    SQL> !ls -l /opt/oracle/oradata3/PROD/REDO03B_STDBY.log
    /opt/oracle/oradata3/PROD/REDO03B_STDBY.log: No such file or directory
    SQL> !ls -l /opt/oracle/oradata3/PROD/REDO04B_STDBY.log
    /opt/oracle/oradata3/PROD/REDO04B_STDBY.log: No such file or directory
    SQL> !ls -l /opt/oracle/oradata3/PROD/REDO05B_STDBY.log
    /opt/oracle/oradata3/PROD/REDO05B_STDBY.log: No such file or directory
    But here, you can see that the "A" redo logs actually do exist.
    SQL> !ls -l /opt/oracle/oradata2/PROD/REDO01A_STDBY.log
    -rw-r-----   1 oracle   dba      536871424 Jan  7  2011 /opt/oracle/oradata2/PROD/REDO01A_STDBY.log

    Hello;
    I'm able to recreate
    SQL> select * from v$logfile;
        GROUP# STATUS  TYPE    MEMBER                                             IS_
             3         ONLINE  /u01/app/oracle/flash_recovery_area/RECOVER2/onlin YES
                               elog/o1_mf_3_8gtxxrl6_.log
             2         ONLINE  /u01/app/oracle/flash_recovery_area/RECOVER2/onlin YES
                               elog/o1_mf_2_8gtxxr4f_.log
             1         ONLINE  /u01/app/oracle/flash_recovery_area/RECOVER2/onlin YES
                               elog/o1_mf_1_8gtxxqng_.log
             4         STANDBY /u01/app/oracle/oradata/RECOVER2/redo04.log        NO
             5         STANDBY /u01/app/oracle/oradata/RECOVER2/redo05.log        NO
             6         STANDBY /u01/app/oracle/oradata/RECOVER2/redo06.log        NOAnd then
    SQL> !ls -al /u01/app/oracle/oradata/RECOVER2/redo04.log
    ls: /u01/app/oracle/oradata/RECOVER2/redo04.log: No such file or directoryChecking... *Not there, but Oracle ( 11.2.0.3 ) allows clean up without barking. Had only one member so I did GROUP drop.
    SQL> ALTER DATABASE DROP LOGFILE GROUP 4;
    Database altered.
    SQL> select * from v$logfile;
        GROUP# STATUS  TYPE    MEMBER                                             IS_
             3         ONLINE  /u01/app/oracle/flash_recovery_area/RECOVER2/onlin YES
                               elog/o1_mf_3_8gtxxrl6_.log
             2         ONLINE  /u01/app/oracle/flash_recovery_area/RECOVER2/onlin YES
                               elog/o1_mf_2_8gtxxr4f_.log
             1         ONLINE  /u01/app/oracle/flash_recovery_area/RECOVER2/onlin YES
                               elog/o1_mf_1_8gtxxqng_.log
             5         STANDBY /u01/app/oracle/oradata/RECOVER2/redo05.log        NO
             6         STANDBY /u01/app/oracle/oradata/RECOVER2/redo06.log        NO
    SQL> Best Regards
    mseberg

  • Standby Redo Log just sits as IN-MEMORY

    Hi, I have shipped an archived redo log from my Primary to my physical standby.
    I can see the log arriving at my Standby and being applied
    select thread#, max(sequence#) "Last Standby Seq Received"
    from v$archived_log val, v$database vdb
    where val.resetlogs_change# = vdb.resetlogs_change#
    group by thread# order by 1;
    returns
       THREAD# Last Standby Seq Received
             1                       151
    select thread#, max(sequence#) "Last Standby Seq Applied"
    from v$archived_log val, v$database vdb
    where val.resetlogs_change# = vdb.resetlogs_change#
    and applied='YES'
    group by thread# order by 1;
       THREAD# Last Standby Seq Applied
             1                      150
    select stamp,name,applied
    from v$archived_log
    where applied != 'YES'
        STAMP
    NAME
    APPLIED
    827498375
    /home/app/oracle/fast_recovery_area/STANDBYL/archivelog/2013_09_30/o1_mf_1_151_9
    4lrqpj3_.arc
    IN-MEMORY
    This log continually sits like this
    I know that Redo Appply is active
    select * from v$managed_standby where process = 'MRP0';
    PROCESS          PID STATUS       CLIENT_P
    CLIENT_PID
    CLIENT_DBID
    GROUP#                                   RESETLOG_ID    THREAD#  SEQUENCE#
        BLOCK#     BLOCKS DELAY_MINS KNOWN_AGENTS ACTIVE_AGENTS
    MRP0            3068 APPLYING_LOG N/A
    N/A
    N/A
    N/A                                        820252586          1        152
          5038     102400          0            3             3
    It looks as if 151 has been applied - yet
    select thread#, max(sequence#) "Last Standby Seq Applied"
    from v$archived_log val, v$database vdb
    where val.resetlogs_change# = vdb.resetlogs_change#
    and applied='YES'
    group by thread# order by 1;
    still shows 150 !
    151 is not that big, I still would have expected it to have applied by now ( in excess of 30 mins )
    Also I know there is no defer or time delay on the archive_destination setting on the Primary.
    Any ideas why this standby redo log just sits IN-MEMORY ?
    thanks,
    Jim

    Hello;
    Not able to reproduce issue. Using Oracle 11.2.0.3 without Real-time apply.
    select thread#, max(sequence#) "Last Standby Seq Received"
    from v$archived_log val, v$database vdb
    where val.resetlogs_change# = vdb.resetlogs_change#
    group by thread# order by 1;
    THREAD#                Last Standby Seq Received
    1                      194    
    select thread#, max(sequence#) "Last Standby Seq Applied"
    from v$archived_log val, v$database vdb
    where val.resetlogs_change# = vdb.resetlogs_change#
    and applied='YES'
    group by thread# order by 1;
    THREAD#                Last Standby Seq Applied
    1                      194         
    select thread#, max(sequence#) "Last Standby Seq Applied"
    from v$archived_log val, v$database vdb
    where val.resetlogs_change# = vdb.resetlogs_change#
    And Applied='YES'
    group by thread# order by 1;
    THREAD#                Last Standby Seq Applied
    1                      194   
    SELECT ARCH.THREAD# "Thread", ARCH.SEQUENCE# "Last Sequence Received", APPL.SEQUENCE# "Last Sequence Applied"
    FROM
    (SELECT THREAD# ,SEQUENCE# FROM V$ARCHIVED_LOG WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$ARCHIVED_LOG GROUP BY THREAD#)) ARCH,
    (SELECT THREAD# ,SEQUENCE# FROM V$LOG_HISTORY WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$LOG_HISTORY GROUP BY THREAD#)) APPL
    WHERE
    Arch.Thread# = Appl.Thread#
    ORDER BY 1;
    Thread                 Last Sequence Received Last Sequence Applied 
    1                      194                    194                  
    select * from v$managed_standby where process = 'MRP0';
    ( shows the next sequence 195 on mine )
    Is it possible the Standby has one extra archive? I've noticed that sometime you will see one extra on that side which appears to have nothing to do with the Data Guard process.
    Best Regards
    mseberg

  • Data Guard : Standby Redo Log CONFUSION

    Trying to set up test Standby db on 10.2.0
    I am well confused about below step 3.1.3, how is the normal redo linked with standby redo, should standby not be members of orginal redo groups?
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ps.htm#i1225703
    Original redo logs:
    SQL>  select * from v$log;
        GROUP#    THREAD#  SEQUENCE#      BYTES    MEMBERS ARC STATUS           FIRST_CHANGE# FIRST_TIME
             1          1         28   52428800          1 YES INACTIVE                375136 22-NOV-07
             2          1         29   52428800          1 YES INACTIVE                375138 22-NOV-07
             3          1         30   52428800          1 NO  CURRENT                 375143 22-NOV-07I added below from notes:
    ALTER DATABASE ADD STANDBY LOGFILE GROUP 10
    ('/u01/oracle/oradata/db01/redo01_stb.log') SIZE 50M;
    ALTER DATABASE ADD STANDBY LOGFILE GROUP 11
    ('/u02/oracle/oradata/db01/redo02_stb.log') SIZE 50M;
    ALTER DATABASE ADD STANDBY LOGFILE GROUP 12
    ('/u03/oracle/oradata/db01/redo03_stb.log') SIZE 50M;After few alter system switch logfile; I still have:
        GROUP#    THREAD#  SEQUENCE# ARC STATUS
            10          0          0 YES UNASSIGNED
            11          0          0 YES UNASSIGNED
            12          0          0 YES UNASSIGNEDAll are UNASSIGNED, should one standby group not be ACTIVE like the above link shows.
    Many think for any help

    First things first:
    From the Docs.:
    "Minimally, the configuration should have one more standby redo log file group than the number of online redo log file groups on the primary database. However, the recommended number of standby redo log file groups is dependent on the number of threads on the primary database. Use the following equation to determine an appropriate number of standby redo log file groups:
    (maximum number of logfiles for each thread + 1) * maximum number of threads
    Using this equation reduces the likelihood that the primary instance's log writer (LGWR) process will be blocked because a standby redo log file cannot be allocated on the standby database. For example, if the primary database has 2 log files for each thread and 2 threads, then 6 standby redo log file groups are needed on the standby database."
    You are 1 short!

  • Remove standby redo log, get ORA-00600

    Hi,
    My v$logfile
    GROUP# STATUS TYPE MEMBER
    IS_RECOVERY_DEST_FILE
    3 ONLINE /u01/app/oracle/oradata/orcl/redo03.log
    NO
    2 ONLINE /u01/app/oracle/oradata/orcl/redo02.log
    NO
    1 ONLINE /u01/app/oracle/oradata/orcl/redo01.log
    NO
    GROUP# STATUS TYPE MEMBER
    IS_RECOVERY_DEST_FILE
    4 STANDBY /u01/app/oracle/oradata/orcl/stdlog01.log
    NO
    5 STANDBY /u01/app/oracle/oradata/orcl/stdlog02.log
    NO
    And when i clear standby log 5
    SQL> alter database clear logfile group 5;
    alter database clear logfile group 5
    ERROR at line 1:
    ORA-00600: internal error code, arguments: [2130], [0], [8], [2], [], [], [],[]
    Please help me :(

    This is the information
    SQL> select * from v$version;
    BANNER
    Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
    PL/SQL Release 11.1.0.6.0 - Production
    CORE 11.1.0.6.0 Production
    TNS for Linux: Version 11.1.0.6.0 - Production
    NLSRTL Version 11.1.0.6.0 - Production
    - Because the standby redo log group 5 is created with smaller size than the redo log. So, i want to remove this standby log and recreate the new one with equal or larger size of the online redo log
    Chuong

  • How do look if i have Standby Redo Log files

    How do look if i have Standby Redo Log files
    example of creating them..

    To check existence of Standby Redo Log Files:
    SQL> v$standby_log
    Name                                      Null?    Type
    ----------------------------------------- -------- ---------------------------- GROUP#                                             NUMBER
    DBID                                               VARCHAR2(40)
    THREAD#                                            NUMBER
    SEQUENCE#                                          NUMBER
    BYTES                                              NUMBER
    USED                                               NUMBER
    ARCHIVED                                           VARCHAR2(3)
    STATUS                                             VARCHAR2(10)
    FIRST_CHANGE#                                      NUMBER
    FIRST_TIME                                         DATE
    LAST_CHANGE#                                       NUMBER
    LAST_TIME                                          DATE
    SQL> select * from v$standby_log;
    no rows selected
    SQL>To Create a Standby Redo Log file:
    SQL> alter database add standby logfile group 11 ('/u01/app/test.log') size 5m;
    Database altered.
    SQL> set line 10000
    SQL> select * from v$standby_log;
        GROUP# DBID                                        THREAD#  SEQUENCE#      BYTES       USED ARC STATUS     FIRST_CHANGE# FIRST_TIM LAST_CHANGE# LAST_TIME
            11 UNASSIGNED                                        0          0    5242880        512 YES UNASSIGNED              0                      0
    SQL>and this is how you drop:
    SQL> alter database drop standby logfile group 11;
    Database altered.
    SQL> ! rm /u01/app/test.log
    SQL>Asif Momen
    http://momendba.blogspot.com
    Edited by: Asif Momen on Mar 16, 2010 1:32 PM
    Included DROP example

  • Standby Redo Log Files and Directory Structure in Standby Site

    Hi Guru's
    I just want to confirm, i know that if the Directory structure is different i need to mention these 2 parameter in pfile
    on primary site:
    DB_CONVERT_DATAFILE='standby','primary'
    LOG_CONVERT_DATAFILE='standby','primary'
    On secondary Site:
    DB_CONVERT_DATAFILE='primary','standby'
    LOG_CONVERT_DATAFILE='primary','standby'
    But i want to confirm this wheather i need to issue the complete path of the directory in both the above paramtere:
    like:
    DB_CONVERT_DATAFILE='/u01/oracle/app/oracle/oradata/standby','/u01/oracle/app/oracle/oradata/primary'
    LOG_CONVERT_DATAFILE='/u01/oracle/app/oracle/oradata/standby','/u01/oracle/app/oracle/oradata/primary'
    Second Confusion:-
    After transferring Redo Standby log files created on primary and taken to standby on the above mentioned directory structure and after restoring the backup of primary db alongwith the standby control file will not impact the physical standby redo log placed on the above mentioned location.
    Thanks in advance for your help

    Hello,
    Regarding your 1st question, you need to provide the complete path and not just the directory name.
    On the standby:
    db_file_name_convert='<Full path of the datafiles on primary server>','<full path of the datafiles to be stored on the standby server>';
    log_file_name_convert='<Full path of the redo logfiles on primary server>','<full path of the redo logfiles on the standby server>';
    Second Confusion:-
    After transferring Redo Standby log files created on primary and taken to standby on the above mentioned directory structure and after restoring the backup of primary db alongwith the standby control file will not impact the physical standby redo log placed on the above mentioned location.
    How are you creating the standby database ? Using RMAN duplicate or through the restore/recovery options ?
    You can create the standby redo logs later.
    Regards,
    Shivananda

  • Why do we need standby redo log on Primary database.

    Hi Gurus,
    I was going through the document in OBE,
    http://www.oracle.com/technology/obe/11gr1_db/ha/dataguard/physstby/physstdby.htm
    I have two queries:
    1) I noticed the statement -
    "Configure the primary database to receive redo data, by adding the standby logfiles to the primary. "
    Why do we have to create standby redo log on a primary database?
    2) There is another statement --
    "It is highly recommended that you have one more standby redo log group than you have online redo log groups as the primary database. The files must be the same size or larger than the primary database’s online redo logs. "
    Why do we need one additional standby redo log group than in Primary database.
    Could anyone please explain to me in simple words.
    Thanks
    Cherrish Vaidiyan

    Hi,
    1. Standby redo logs are used only when the database_role is standby, it is recommended to be added in primary also so that they can be used on role reversal, however during normal working standby redo logs will not be used at all on primary.
    2. In case of 3 online redo log groups, it is recommended to use 4 standby redo log group this is in case if log switching is happening frequently on primary and all 3 standby redo logs are still not completely archived on the standby and 4th can be used here as there will be some delay on standby due to network or slowness of arch on standby.
    Use of the standby redo log groups depends on the redo generation rate, you can see only 2 standby redo logs are getting used while you have 4 standby redo log groups, when the redo generation rate is less.
    So it is recommended to have one more standby redo log group when redo generation rate is high and all of the existing standby redo log group are getting used.
    Regards
    Anudeep

  • Where RFS exactly write redo data ?  ( archived redo log or standby redo log ) ?

    Good Morning to all ;
    I am getting bit confused from oracle official link . REF_LINK : Log Apply Services
    Redo data transmitted from the primary database is received by the RFS on the standby system ,
    where the RFS process writes the redo data to either archived redo log files  or  standby redo log files.
    In standby site , does rfs write redo data in any one file or both ?
    Thanks in advance ..

    Hi GTS,
    GTS (DBA) wrote:
    Primary & standby log file size should be same - this is okay.
    1) what are trying to disclose about  largest & smallest here ? -  You are confusing.
    Read: http://docs.oracle.com/cd/E11882_01/server.112/e25608/log_transport.htm#SBYDB4752
    "Each standby redo log file must be at least as large as the largest redo log file in the redo log of the redo source database. For administrative ease, Oracle recommends that all redo log files in the redo log at the redo source database and the standby redo log at a redo transport destination be of the same size."
    GTS (DBA) wrote:
    2) what abt group members ? should be same as primary or need  to add some members additionally. ?
    Data Guard best practice for performance, is to create one member per each group in standby DB. on standby DB, one member per group is reasonable enough. why? to avoid write penalty; writing to more than one log files at the standby DB.
    SCENARIO 1: if in your source primary DB you have 2 log member per group, in standby DB you can have 1 member  per group, additionally create an extra group.
    primary
    standby
    Member per group
    2
    1
    Number of log group
    4
    5
    SCENARIO 2: you can also have this scenario 2 but i will not encourage it
    primary
    standby
    Member per group
    2
    2
    Number of log group
    4
    5
    GTS (DBA) wrote:
    All standby redo logs of the correct size have not yet been archived.
      - at this situation , can we force on standby site ? any possibilities ? 
    you can not force it , just size your standby redo files correctly and make sure you don not have network failure that will cause redo gap.
    hope there is clarity now
    Tobi

Maybe you are looking for

  • Manual sync iPod

    Does anyone know how to change the settings on iTunes so that the iPod does not auto sync when I connect it, but change the settings whilst the iPod is not connected? I cannot seem to do it, but it seems ridiculous that you cannot do this! Please hel

  • IPhoto 11 low resolution photo in full screen mode

    In the 09 version a low resolution picture is shown full on the screen, but can be a little bit blurry. In the 11 version the low resolution picture is shown small. How can we change that?

  • Nokia E6 live streaming not working

    its only one month i've updated my mobibe due to hanging problem and now it s giving me another pain for not playing any live streaming video like online tv or you tube streaming... Also still have the hanging problem. Help me out if anybody has a so

  • Internet suddenly VERY VERY VERY SLOW!!

    I have had my Airport Express for about 2 months now and it has worked fabulously. However, a few nights ago, I think it decided to die out on me or something. It connects to the internet and everything, web pages load, but it just takes about 5 minu

  • Agent not starting

    Hi, I uninstalled ODI(10.1.3.5) and reinstalled it again. I was able to set up the master and work repository. But when I try to run the agent, I am getting the below message and nothing happens after this. D:\Oracle\oracledi\bin>agentscheduler "-por