All redo log groups is active

Hello dear gurus!
After shutting database with option "abort"
we have unconsisten state of datafiles.
I ask to explain :
1) - does the ARCH background processes flash whole redo buffer into redolog ?
(In other words how reached consistency if all redo log groups was in active state before shutting down ?)
2) Where buffer contents in this case are dumped ?
Thanks and best regards,
Pavel
Edited by: Pavel on Jul 19, 2012 9:49 PM

Pavel wrote:
Hello dear gurus!
After shutting database with option "abort"
we have unconsisten state of datafiles.That's expected as checkpoint didn't happen. Issue a startup and instance recovery should take care of everything.
I ask to explain :
1) - does the ARCH background processes flash whole redo buffer into redolog ?ARCH process or LGWR? How does this relates to your current question?
(In other words how reached consistency if all redo log groups was in active state before shutting down ?)As I said, issue a startup of the instance and it should take care of the things.
2) Where buffer contents in this case are dumped ?Which case? Your questions are a bit fuzzy you see. Let's stick to one question at one time and follow it shall we?
Aman....

Similar Messages

  • All Redo Log groups are active.

    Hi All,
    In one of our production database now a days we are seeing that all redo logs become active and then everything just get hang. It happens for 15-20 minutes and after that they come normal. Database size is over 4.5 TB and it's OLTP cum MIS database. As per Unix Team at server and storage level everything is fine so what could be other reason for this?
    Database version is 9.2.0.5 and O/S is AIX 5.3 Power System.
    select * from v$log;
    GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRST_CHANGE# FIRST_TIME
    1 1 435847 1,342,177,280 2 YES ACTIVE 1.1782E+13 13-MAR-10
    2 1 435848 1,342,177,280 2 YES ACTIVE 1.1782E+13 13-MAR-10
    3 1 435850 1,342,177,280 2 NO CURRENT 1.1782E+13 13-MAR-10
    4 1 435844 1,342,177,280 2 YES ACTIVE 1.1782E+13 13-MAR-10
    5 1 435845 1,342,177,280 2 YES ACTIVE 1.1782E+13 13-MAR-10
    6 1 435846 1,342,177,280 2 YES ACTIVE 1.1782E+13 13-MAR-10
    7 1 435843 1,342,177,280 2 YES ACTIVE 1.1782E+13 13-MAR-10
    8 1 435849 1,342,177,280 2 YES ACTIVE 1.1782E+13 13-MAR-10
    9 1 435842 1,342,177,280 2 YES INACTIVE 1.1782E+13 13-MAR-10
    9 rows selected.
    VMSTAT output:
    vmstat 2 10
    kthr memory page faults cpu
    r b avm fre re pi po fr sr cy in sy cs us sy id wa
    35 13 23262385 48530 0 0 0 0 0 0 27910 531516 111964 54 7 12 26
    30 12 23270696 26769 0 0 0 4277 19644 0 28759 604423 106619 53 7 14 25
    26 12 23269357 25691 0 0 0 8899 38750 0 28620 552550 103736 55 7 15 23
    32 14 23263410 31111 0 0 0 10778 47248 0 29722 690889 112674 53 7 16 24
    27 17 23268835 25011 0 0 0 10267 51727 0 30321 779933 116936 58 8 13 21
    30 20 23274592 25181 0 0 0 13569 59742 0 28290 731707 109167 59 7 13 22
    33 10 23280476 30823 0 0 0 15259 66334 0 28942 774600 107692 65 7 8 20
    36 13 23280770 26040 0 0 0 7199 33048 0 29351 687375 98487 63 7 10 20
    35 16 23277780 27758 0 0 0 7250 33003 0 30699 622788 97172 65 6 10 19
    31 13 23277431 25107 0 0 0 8521 37996 0 29746 596172 89831 63 6 11 20
    select event, count(*) from v$session_wait group by event order by 2;
    EVENT COUNT(*)
    PL/SQL lock timer 2
    SQL*Net more data from client 2
    jobq slave wait 3
    direct path read 5
    rdbms ipc message 8
    enqueue 11
    log file sync 11
    db file parallel write 12
    latch free 12
    pipe get 22
    PX Deq: Execution Msg 27
    buffer busy waits 33
    db file scattered read 39
    db file sequential read 169
    SQL*Net message from client 2120

    Hi,
    Complete output would be so long so just putting tail of that.
    RECID STAMP
    NAME
    DEST_ID THREAD# SEQUENCE# RESETLOGS_CHANGE# RESETLOGS_TIME FIRST_CHANGE# FIRST_TIME NEXT_CHANGE# NEXT_TIME BLOCKS BLOCK_SIZE CREATOR REGISTR STA ARC APP DEL S COMPLETION_TIME
    DIC DIC END BACKUP_COUNT ARCHIVAL_THREAD# ACTIVATION#
    711558 713531894
    (DESCRIPTION=(ADDRESS_LIST = (ADDRESS=(PROTOCOL=tcp)(HOST=ilerpstdby)(PORT=1540)))(CONNECT_DATA=(SID=ILPROD)(SERVER=DEDICATED)))
    2 1 435868 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH YES YES YES NO A 13-MAR-10
    NO NO NO 0 1 2142322718
    711559 713531942
    /arch/ora/prod/PRODDB_1_00135869.arc
    1 1 435869 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH NO YES NO NO A 13-MAR-10
    NO NO NO 0 1 2142322718
    711560 713531994
    (DESCRIPTION=(ADDRESS_LIST = (ADDRESS=(PROTOCOL=tcp)(HOST=ilerpstdby)(PORT=1540)))(CONNECT_DATA=(SID=ILPROD)(SERVER=DEDICATED)))
    2 1 435869 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH YES YES YES NO A 13-MAR-10
    NO NO NO 0 1 2142322718
    711561 713532090
    /arch/ora/prod/PRODDB_1_00135870.arc
    1 1 435870 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH NO YES NO NO A 13-MAR-10
    NO NO NO 0 1 2142322718
    711562 713532149
    (DESCRIPTION=(ADDRESS_LIST = (ADDRESS=(PROTOCOL=tcp)(HOST=ilerpstdby)(PORT=1540)))(CONNECT_DATA=(SID=ILPROD)(SERVER=DEDICATED)))
    2 1 435870 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH YES YES YES NO A 13-MAR-10
    NO NO NO 0 1 2142322718
    711563 713532276
    /arch/ora/prod/PRODDB_1_00135871.arc
    1 1 435871 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH NO YES NO NO A 13-MAR-10
    NO NO NO 0 1 2142322718
    711564 713532322
    (DESCRIPTION=(ADDRESS_LIST = (ADDRESS=(PROTOCOL=tcp)(HOST=ilerpstdby)(PORT=1540)))(CONNECT_DATA=(SID=ILPROD)(SERVER=DEDICATED)))
    2 1 435871 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH YES YES YES NO A 13-MAR-10
    NO NO NO 0 1 2142322718
    711565 713532449
    /arch/ora/prod/PRODDB_1_00135872.arc
    1 1 435872 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH NO YES NO NO A 13-MAR-10
    NO NO NO 0 1 2142322718
    711566 713532506
    (DESCRIPTION=(ADDRESS_LIST = (ADDRESS=(PROTOCOL=tcp)(HOST=ilerpstdby)(PORT=1540)))(CONNECT_DATA=(SID=ILPROD)(SERVER=DEDICATED)))
    2 1 435872 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH YES YES YES NO A 13-MAR-10
    NO NO NO 0 1 2142322718
    711567 713532607
    /arch/ora/prod/PRODDB_1_00135873.arc
    1 1 435873 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH NO YES NO NO A 13-MAR-10
    NO NO NO 0 1 2142322718
    711568 713532662
    (DESCRIPTION=(ADDRESS_LIST = (ADDRESS=(PROTOCOL=tcp)(HOST=ilerpstdby)(PORT=1540)))(CONNECT_DATA=(SID=ILPROD)(SERVER=DEDICATED)))
    2 1 435873 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH YES YES YES NO A 13-MAR-10
    NO NO NO 0 1 2142322718
    711569 713532773
    /arch/ora/prod/PRODDB_1_00135874.arc
    1 1 435874 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH NO YES NO NO A 13-MAR-10
    NO NO NO 0 1 2142322718
    711570 713532832
    (DESCRIPTION=(ADDRESS_LIST = (ADDRESS=(PROTOCOL=tcp)(HOST=ilerpstdby)(PORT=1540)))(CONNECT_DATA=(SID=ILPROD)(SERVER=DEDICATED)))
    2 1 435874 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH YES YES YES NO A 13-MAR-10
    NO NO NO 0 1 2142322718
    711571 713532933
    /arch/ora/prod/PRODDB_1_00135875.arc
    1 1 435875 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH NO YES NO NO A 13-MAR-10
    NO NO NO 0 1 2142322718
    711572 713532980
    (DESCRIPTION=(ADDRESS_LIST = (ADDRESS=(PROTOCOL=tcp)(HOST=ilerpstdby)(PORT=1540)))(CONNECT_DATA=(SID=ILPROD)(SERVER=DEDICATED)))
    2 1 435875 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH YES YES YES NO A 13-MAR-10
    NO NO NO 0 1 2142322718
    711573 713533101
    /arch/ora/prod/PRODDB_1_00135876.arc
    1 1 435876 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH NO YES NO NO A 13-MAR-10
    NO NO NO 0 1 2142322718
    711574 713533178
    (DESCRIPTION=(ADDRESS_LIST = (ADDRESS=(PROTOCOL=tcp)(HOST=ilerpstdby)(PORT=1540)))(CONNECT_DATA=(SID=ILPROD)(SERVER=DEDICATED)))
    2 1 435876 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH YES YES YES NO A 13-MAR-10
    NO NO NO 0 1 2142322718
    711575 713533258
    /arch/ora/prod/PRODDB_1_00135877.arc
    1 1 435877 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH NO YES NO NO A 13-MAR-10
    NO NO NO 0 1 2142322718
    711576 713533323
    (DESCRIPTION=(ADDRESS_LIST = (ADDRESS=(PROTOCOL=tcp)(HOST=ilerpstdby)(PORT=1540)))(CONNECT_DATA=(SID=ILPROD)(SERVER=DEDICATED)))
    2 1 435877 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH YES YES YES NO A 13-MAR-10
    NO NO NO 0 1 2142322718
    711577 713533366
    /arch/ora/prod/PRODDB_1_00135878.arc
    1 1 435878 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH NO YES NO NO A 13-MAR-10
    NO NO NO 0 1 2142322718
    711578 713533419
    (DESCRIPTION=(ADDRESS_LIST = (ADDRESS=(PROTOCOL=tcp)(HOST=ilerpstdby)(PORT=1540)))(CONNECT_DATA=(SID=ILPROD)(SERVER=DEDICATED)))
    2 1 435878 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH YES YES YES NO A 13-MAR-10
    NO NO NO 0 1 2142322718
    711579 713533497
    /arch/ora/prod/PRODDB_1_00135879.arc
    1 1 435879 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH NO YES NO NO A 13-MAR-10
    NO NO NO 0 1 2142322718
    711580 713533537
    (DESCRIPTION=(ADDRESS_LIST = (ADDRESS=(PROTOCOL=tcp)(HOST=ilerpstdby)(PORT=1540)))(CONNECT_DATA=(SID=ILPROD)(SERVER=DEDICATED)))
    2 1 435879 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH YES YES NO NO A 13-MAR-10
    NO NO NO 0 1 2142322718
    711581 713533678
    /arch/ora/prod/PRODDB_1_00135880.arc
    1 1 435880 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH NO YES NO NO A 13-MAR-10
    NO NO NO 0 1 2142322718
    711582 713533737
    (DESCRIPTION=(ADDRESS_LIST = (ADDRESS=(PROTOCOL=tcp)(HOST=ilerpstdby)(PORT=1540)))(CONNECT_DATA=(SID=ILPROD)(SERVER=DEDICATED)))
    2 1 435880 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH YES YES NO NO A 13-MAR-10
    NO NO NO 0 1 2142322718
    711583 713533841
    /arch/ora/prod/PRODDB_1_00135881.arc
    1 1 435881 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH NO YES NO NO A 13-MAR-10
    NO NO NO 0 1 2142322718
    711584 713533919
    (DESCRIPTION=(ADDRESS_LIST = (ADDRESS=(PROTOCOL=tcp)(HOST=ilerpstdby)(PORT=1540)))(CONNECT_DATA=(SID=ILPROD)(SERVER=DEDICATED)))
    2 1 435881 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH YES YES NO NO A 13-MAR-10
    NO NO NO 0 1 2142322718
    711585 713533983
    /arch/ora/prod/PRODDB_1_00135882.arc
    1 1 435882 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH NO YES NO NO A 13-MAR-10
    NO NO NO 0 1 2142322718
    711586 713534050
    (DESCRIPTION=(ADDRESS_LIST = (ADDRESS=(PROTOCOL=tcp)(HOST=ilerpstdby)(PORT=1540)))(CONNECT_DATA=(SID=ILPROD)(SERVER=DEDICATED)))
    2 1 435882 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH YES YES NO NO A 13-MAR-10
    NO NO NO 0 1 2142322718

  • Delete all redo log groups

    Friends,
    Suddenly I have to delete all of my redo log groups (REDO01.LOG,REDO02.LOG,REDO03.LOG) from my database . Now I cannot open my database . I am using Oracle 10g database . I have no cold backup of my database but have a RMAN backup . Now How can I restore my redo log groups .
    Can anybody plz help me .. ...

    if you are working in archive mode
    SQL> startup
    ORACLE instance started.
    Total System Global Area 272629760 bytes
    Fixed Size 1290136 bytes
    Variable Size 213909608 bytes
    Database Buffers 50331648 bytes
    Redo Buffers 7098368 bytes
    Database mounted.
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1:
    'D:\ORACLE\PRODUCT\10.2.0\ORADATA\PEEGT\REDO01.LOG'
    SQL> recover database until cancel;
    Media recovery complete.
    SQL> alter database open resetlogs;
    Database altered.
    Backup your database...

  • Redo log  group always active or current

    Hi,
    on 11G R2 on Win 2008, I try ro drop a redolog group but it is always CURRENT or ACTIVE. I do alter system switch logfile repeatedly but it does not become inactive .
    Any idea ?
    Thank you.

    If the group stays in the active state for a longer time, it means that the DBWR is taking more time than needed to checkpoint its contents to the data file(s) or you are switching over to the log group more quickly than it would need to make it inactive. So you can do two things, one that you check that if you have any lag in the DBWR's work or there is any slowness in the IO while writing to the disk. Second, make sure that you are not having the size of the log files and the number smaller than needed. You haven't told us about either of the things so we can't suggest anything till you share it. About being the Current, that's normal working and if you think that's a problem, have a read of the Concepts guide.
    HTH
    Aman....

  • Abot loss online Redo log group

    Hi,
    Is there different from recovering between loss CURRENT online redo log group and ACTIVE online redo log group?
    Both of them are needed to incomplete recovery, right?

    For CURRENT redolog recovery:
    startup mount
    recover database until cancel;
    alter database open resetlogs;
    For ACTIVE redolog recovery:
    If the database is still running, force a checkpoint by issuing the following command:
    alter system checkpoint;
    If above was successful and if the lost group has been archived then issue:
    alter database clear logfile group <number of the online redo log group>;
    And if the lost group has NOT been archived then issue:
    alter database clear logfile unarchived group <number of the online redo log group>;
    alter database open;
    If the database is not running (crashed) then
    startup mount
    recover database until cancel;
    alter database open resetlogs;
    Daljit Singh

  • How to know the delay in redo log apply on Active Dataguard 11g

    Hello All,
    How to know the delay in redo log apply on Active Dataguard 11g...
    Do we need to wait till log switch occurs?
    Or is it recommended to schedule a log switch every 15 min, no matter data is updated/inserted or not in primary?
    Please suggest...
    Oracle : oracle 11g Release 2
    OS : RHEL 5.4
    Thanks
    Edited by: user1687821 on Feb 23, 2012 12:02 AM

    Hello CKPT,
    Thank you for the valuable information...
    We have not configured databroker.
    Output of the query
    SELECT * FROM (
    SELECT sequence#, archived, applied,
    TO_CHAR(completion_time, 'RRRR/MM/DD HH24:MI') AS completed
    FROM sys.v$archived_log
    ORDER BY sequence# DESC)
    WHERE ROWNUM <= 10
    Primary...
    SEQUENCE#     ARCHIVED     APPLIED     COMPLETED
    29680          YES          YES     2012/02/23 01:11
    29680          YES          NO     2012/02/23 01:11
    29679          YES          NO     2012/02/22 23:11
    29679          YES          YES     2012/02/22 23:11
    29678          YES          YES     2012/02/22 23:11
    29678          YES          NO     2012/02/22 23:11
    29677          YES          YES     2012/02/22 22:32
    29677          YES          NO     2012/02/22 22:32
    29676          YES          YES     2012/02/22 22:02
    29676          YES          NO     2012/02/22 22:02
    Standby...
    SEQUENCE# ARC APP COMPLETED
    29680 YES YES 2012/02/23 01:11
    29679 YES YES 2012/02/22 23:11
    29678 YES YES 2012/02/22 23:11
    29677 YES YES 2012/02/22 22:32
    29676 YES YES 2012/02/22 22:02
    29675 YES YES 2012/02/22 21:24
    29674 YES YES 2012/02/22 19:24
    29673 YES YES 2012/02/22 18:59
    29672 YES YES 2012/02/22 17:42
    29671 YES YES 2012/02/22 17:41
    Primary shows yes as well as no...
    Next,
    From primary:-
    SQL> select thread#,max(sequence#) from v$archived_log group by thread#;
    THREAD#     MAX(SEQUENCE#)
    1     29680
    From standby:-
    SQL> select thread#,max(sequence#) from v$archived_log where applied='YES' group by thread#;
    THREAD# MAX(SEQUENCE#)
    1 29680
    What is the redo transport service you are using? is it LGWR or ARCH ?
    Output of query select * from v$parameter where name like 'log_archive_dest_2' shows below value...
    SERVICE=b_stdb LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=b_stdb
    So is it lgwr already configured...? if yes then how do i see the delay in both servers..
    Yes, the network is good as they both resides in same LAN within same rack
    Thanks...

  • Online Redo Log groups

    Dear All,
    How to check the health of redo log file, we have 200 MB undo tablespace in our production server is it enough for huge transactions. Can I check how much time my redo log file data have been overwritten?
    Further in which situation we will add Online Redo Log Groups and which situation we will add Log Members.
    My rollback segment is using System tablespace is it recommended?
    What is recommendation about 1 redo log group is redo log member or 1 redo log group is multiple redo log members.

    Thanks Mr. Nicolas. for your informative guidence.
    Can I check how much time my redo log file data have been overwritten?Check v$loghist.
    We have 218 records in v$loghist, it means 218 times data have been overwritten, i think its not good. Can you guide me how to rectyify this.
    in which situation we will add Online Redo Log GroupsIn case of checkpoint not complete reported into alert.log.
    How to findout checkpoint entry in alert.log
    which situation we will add Log Members.This is the redolog multiplexing, at least two members for each redolog group.
    Ok, Can we do multiplexing for members or just do for groups.
    My rollback segment is using System tablespace is it recommended?No.
    OK, can we change rollback segments tablespace.
    1 redo log group is redo log member or 1 redo log group is multiple redo log membersA minimum of two redolog group with two members for each.
    After, it depend of your db activity.
    We have just one member for each group and we have three groups, so whats ur recommnedation we will add 1 member in each group.

  • Unable to drop a Redo Log Group

    Hi,
    My database is running on version 11.1.0.7 on OEL platform.
    I am trying to delete one of the Active Redo Log Group, it fails with the below error. Could someone please help me fix this issue?
    SQL >  select * from v$log;
        GROUP#    THREAD#  SEQUENCE#      BYTES    MEMBERS ARCHIVED  STATUS                                           FIRST_CHANGE# FIRST_TIME
            10          1       8017  524288000          2 YES       INACTIVE                                            1.2120E+13 17-JUN-2012 19:43:49
            11          1       8018  524288000          2 YES       INACTIVE                                            1.2120E+13 18-JUN-2012 06:49:45
            12          1       8019  524288000          2 YES       INACTIVE                                            1.2120E+13 18-JUN-2012 16:56:43
            13          1       8021  524288000          2 YES       INACTIVE                                            1.2120E+13 18-JUN-2012 23:18:07
            14          1       8020  524288000          2 YES       INACTIVE                                            1.2120E+13 18-JUN-2012 23:14:27
            15          1       8022  524288000          2 NO        CURRENT                                             1.2120E+13 19-JUN-2012 01:07:27
            16          2       6835  524288000          2 YES       INACTIVE                                            1.2120E+13 18-JUN-2012 23:15:46
            17          2       6836  524288000          2 YES       INACTIVE                                            1.2120E+13 18-JUN-2012 23:18:04
            18          2       6837  524288000          2 YES       INACTIVE                                            1.2120E+13 18-JUN-2012 23:20:22
            19          2       6838  524288000          2 YES       INACTIVE                                            1.2120E+13 18-JUN-2012 23:22:38
            20          2       6839  524288000          2 NO        CURRENT                                             1.2120E+13 19-JUN-2012 01:07:24
            21          2       6832  524288000          2 YES       INACTIVE                                            1.2120E+13 18-JUN-2012 23:11:45
            22          3       3771  524288000          2 YES       INACTIVE                                            1.2103E+13 09-SEP-2011 22:04:11
            23          3       3772  524288000          2 YES       INACTIVE                                            1.2103E+13 09-SEP-2011 23:55:55
            24          3       3773  524288000          2 YES       ACTIVE                                              1.2103E+13 09-SEP-2011 23:55:59
            25          3       3766  524288000          2 YES       INACTIVE                                            1.2103E+13 08-SEP-2011 22:05:29
            26          3       3767  524288000          2 YES       INACTIVE                                            1.2103E+13 08-SEP-2011 22:05:50
            27          3       3768  524288000          2 YES       INACTIVE                                            1.2103E+13 09-SEP-2011 14:02:05
    SQL > archive log list;
    Database log mode              Archive Mode
    Automatic archival             Enabled
    Archive destination            /archive/MYCSMA/MYCSMA2
    Oldest online log sequence     6832
    Next log sequence to archive   6839
    Current log sequence           6839
    SQL > archive log all;
    ORA-00271: there are no logs that need archiving
    SQL > ALTER SYSTEM ARCHIVE LOG GROUP 24;
    ALTER SYSTEM ARCHIVE LOG GROUP 24
    ERROR at line 1:
    ORA-16013: log 24 sequence# 3773 does not need archiving
    SQL > alter database drop LOGFILE  group 24;
    alter database drop LOGFILE  group 24
    ERROR at line 1:
    ORA-01623: log 24 is current log for instance MYCSMA3 (thread 3) - cannot drop
    ORA-00312: online log 24 thread 3: '/u247/oradata/MYCSMA/redo24_1.log'
    ORA-00312: online log 24 thread 3: '/u247/oradata/MYCSMA/redo24_2.log'This was previously a 3 node RAC and when it was moved to a different machine, it got build with a 2-node RAC.
    Hence thread 3 is no more required. Thats why I am planning to drop these Redo Log Groups.
    Thanks!

    Hi;
    All information cover at:
    NOTE:102995.1 - Maintenance of Online Redo Log Groups and Members
    Regard
    Helios

  • After increasing redo log groups we are getting given alerts continvously

    earlier having 6 redo log groups with 32 MB.but 7 days back our database was hangs .no one was able to login into sqlplus except sys user ,but not able to perform any dml operation.after rebooting our 2-node RAC instances it was running fine nearly about 6-7 hrs and again hangs.we did 4-5 times and same thing happend again and again.so we had added more redo logs of 100 MB size and removed previous one.then our hangs problem resolved but continvously getting given things in alert logs for both RAC instances(9.2.0.8).our os is linux
    {color:#ff0000}Wed Dec 3 05:04:31 2008
    ARC1: Completed archiving log 15 thread 1 sequence 282036
    ARC1: Evaluating archive log 17 thread 1 sequence 282037
    ARC1: Unable to archive log 17 thread 1 sequence 282037
    Log actively being archived by another process
    ARC1: Evaluating archive log 13 thread 1 sequence 282038
    ARC1: Beginning to archive log 13 thread 1 sequence 282038
    Creating archive destination LOG_ARCHIVE_DEST_2: 'SBMEMS'
    Creating archive destination LOG_ARCHIVE_DEST_1: '/MemsArchive/0001_0000282038.arc'
    Wed Dec 3 05:04:31 2008
    Thread 1 advanced to log sequence 282040
    Current log# 15 seq# 282040 mem# 0: /MemsRedoA/redo15_1.log
    Current log# 15 seq# 282040 mem# 1: /MemsRedoB/redo15_2.log
    Wed Dec 3 05:05:21 2008
    ARC1: Completed archiving log 13 thread 1 sequence 282038
    ARC1: Evaluating archive log 17 thread 1 sequence 282037
    {color}{color:#ff0000}*ARC1: Unable to archive log 17 thread 1 sequence 282037*
    Log actively being archived by another process
    ARC1: Evaluating archive log 18 thread 1 sequence 282039
    ARC1: Beginning to archive log 18 thread 1 sequence 282039
    Creating archive destination LOG_ARCHIVE_DEST_2: 'SBMEMS'
    Creating archive destination LOG_ARCHIVE_DEST_1: '/MemsArchive/0001_0000282039.arc'
    Wed Dec 3 05:05:21 2008
    ARC0: Completed archiving log 17 thread 1 sequence 282037
    ARC0: Evaluating archive log 18 thread 1 sequence 282039
    ARC0: Unable to archive log 18 thread 1 sequence 282039
    Log actively being archived by another process
    ARC0: Evaluating archive log 18 thread 1 sequence 282039
    {color}{color:#ff0000}*ARC0: Unable to archive log 18 thread 1 sequence 282039*
    Log actively being archived by another process
    ARC0: Evaluating archive log 18 thread 1 sequence 282039
    {color}{color:#ff0000}*ARC0: Unable to archive log 18 thread 1 sequence 282039*
    Log actively being archived by another process
    ARC0: Evaluating archive log 18 thread 1 sequence 282039
    ARC0: Unable to archive log 18 thread 1 sequence 282039
    Log actively being archived by another process
    ARC0: Evaluating archive log 18 thread 1 sequence 282039
    ARC0: Unable to archive log 18 thread 1 sequence 282039
    Log actively being archived by another process
    ARC0: Evaluating archive log 18 thread 1 sequence 282039
    ARC0: Unable to archive log 18 thread 1 sequence 282039
    Log actively being archived by another process
    Wed Dec 3 05:05:49 2008
    ARC1: Completed archiving log 18 thread 1 sequence 282039
    Wed Dec 3 09:01:02 2008
    Thread 1 advanced to log sequence 282041
    Current log# 17 seq# 282041 mem# 0: /MemsRedoA/redo17_1.log
    Current log# 17 seq# 282041 mem# 1: /MemsRedoB/redo17_2.log
    Wed Dec 3 09:01:02 2008
    ARC1: Evaluating archive log 15 thread 1 sequence 282040
    ARC1: Beginning to archive log 15 thread 1 sequence 282040
    Creating archive destination LOG_ARCHIVE_DEST_2: 'SBMEMS'
    Creating archive destination LOG_ARCHIVE_DEST_1: '/MemsArchive/0001_0000282040.arc'
    Wed Dec 3 09:01:29 2008
    ARC0: Evaluating archive log 15 thread 1 sequence 282040
    {color}{color:#ff0000}*ARC0: Unable to archive log 15 thread 1 sequence 282040*
    Log actively being archived by another process
    Wed Dec 3 09:01:37 2008
    ARC1: Completed archiving log 15 thread 1 sequence 282040
    {color}ORADB1:MEMS1:oracle$
    please suggest solution for this.
    Thanks

    As Sybrand pointed out, this msg can be ignored. It clearly states that a given arch process cannot archive a given redo because that redo is already being handled by a different arch process. If you follow your alert log a little further, you'll see that the referenced thread is eventually completed.
    I'd be curious to see the alert log from when you were locked up and only sysdba could log on. See what led you to believe that adding more redo log groups would solve your problem.

  • Online redo log group needed??

    hey guys!
         Am about to recreate the clone file of the clone db, open it using recover it until cancel using backup controlfile and apply all necessary archive logs!
    My question is, does ai need to have online redo log group of the production db? since ai have all the archive log, so ai think while recraeting the control file, online redo log group will be created too?
    Thanks!

    while recraeting the control file, online redo log group will be created tooWhile creating control file, online redo log group doesn't get created. After applying all the archivel logs you have to open the database with RESET LOG option and then oracle will create redo logs for you.
    Best of Luck !!
    Daljit Singh

  • Redo Log Groups

    Call me stupid, but for some reason I've decided to get certified as a DBA even though I have always been a developer. Honestly, its not my fault. The choices in the development track are pretty boring...
    Anyway, while pouring through the Backup/Recovery documentation, I run across this:
    Every database must have at least two online redo log groups.
    Each redo log group contains at least one online redo log member,
    which is a physical file containing the redo records.I decided to check and see if I have "at least two online redo log groups" for my play database. Now, I am very very confused.
    I think this query shows my 3 log members, but for some reason the 1st column makes me think I have 3 log groups:
    select group#, member from v$logfile
        GROUP# MEMBER
             3 /var/opt/oracle/oradata/db92/redo03.log
             2 /var/opt/oracle/oradata/db92/redo02.log
             1 /var/opt/oracle/oradata/db92/redo01.logI only know of one place where my online redo is located:
    ls $ORACLE_BASE/oradata/db92
    redo01.log  redo02.log  redo03.logCan someone help me figure out if I have one-group and three-members??
    Any comments are welcome,
    Stan

    This information can help you:
    Adding Redo Log File Groups: Examples
    The following statement adds a redo log file group with two members and identifies it with a GROUP parameter value of 3:
    ALTER DATABASE
    ADD LOGFILE GROUP 3
    ('diska:log3.log' ,
    'diskb:log3.log') SIZE 50K;
    The following statement adds a redo log file group containing two members to thread 5 (in a Real Application Clusters environment) and assigns it a GROUP parameter value of 4:
    ALTER DATABASE
    ADD LOGFILE THREAD 5 GROUP 4
    ('diska:log4.log',
    'diskb:log4:log');
    Dropping Log File Members: Example
    The following statement drops one redo log file member added in the previous example:
    ALTER DATABASE
    DROP LOGFILE MEMBER 'diskb:log3.log';
    The following statement drops all members of the redo log file group 3:
    ALTER DATABASE DROP LOGFILE GROUP 3;
    Adding Redo Log File Group Members: Example
    The following statement adds a member to the redo log file group added in the previous example:
    ALTER DATABASE
    ADD LOGFILE MEMBER 'diskc:log3.log'
    TO GROUP 3;
    Renaming a Log File Member: Example
    The following statement renames a redo log file member:
    ALTER DATABASE
    RENAME FILE 'diskc:log3.log' TO 'diskb:log3.log';
    The preceding statement only changes the member of the redo log group from one file to another. The statement does not actually change the name of the file 'diskc:log3.log' to 'diskb:log3.log'. You must perform this operation through your operating system.
    Joel P�rez

  • REDO LOG GROUP QUESTION

    I was reading an article and it said
    the distance(in bytes) between the checkpoint position in a redolog group and the end of the current redolog group can never be more then 90 % of the size of the smallest redo log group
    Can someone elaborate this

    I'm not sure what you want to elaborate on, but yes, it's true. If your redo logs are 100MB in size, and nothing else causes a checkpoint to take place, you'll have a checkpoint issued when you hit the 90MB mark. The idea is simply that you don't want to sit there doing nothing at all and then bang! the logs switch and you have to go hell-for-leather performing a massive checkpoint, all the while praying more log switches don't mean that you're threatening to catch up with yourself (at which point you'd have the 'thread unable to advance to log...' problem). By implementing the 90% rule, the idea is that your log switch, at worst, will cause a "10%-sized" checkpoint, which should be bearable.
    Of course, the situation is made more complex by the fact that other things DO kick in and cause their own checkpoints, so the interaction between -for example, FAST_START_MTTR_TARGET and the 90% rule can get, er, 'interesting'.

  • Why multiplex redo log group ?

    Hello,
    Why should we multiplex redo log groups if we have only file system which is already mirrored. Is there any one who had an incident when he has only one redo log member per group placed on a mirrored file system but still got corrupted and he felt better to have multiple members even if they reside on the same file system (which is mirrored)
    Thanks
    Salman

    Ansiktet wrote:
    EdStevens wrote:
    Salman Qureshi wrote:
    Hello,
    Why should we multiplex redo log groups if we have only file system which is already mirrored. Is there any one who had an incident when he has only one redo log member per group placed on a mirrored file system but still got corrupted and he felt better to have multiple members even if they reside on the same file system (which is mirrored)
    Thanks
    SalmanThe mirror won't protect you from an SA who deletes '/u01/oradata/redo01.log' because he is running out of space on /u01 and figures its safe to delete a log file.
    Or similar types of errors.
    The redo and control files are simply too critical to put all your eggs in one basket when planning their protection.:) Thats why you should not use Oracle default .log on redo, instead .dbf or .dbl can be used. THat's why I use the older (pre-10g) default of .rdo for redo logs
    However, has this happend anyone for real, that a SA delete Oracle files? Where do you think I came up with the example?
    HOw about an SA (or maybe the kind of "fresher" we often see here, Taking a look at a "log" file with notepad?
    If he is isnt stupid he should know that Oracle resides on /u01 partion (for example), and should not delete files there without consulting the DBA."should" is the operative word there. There is no accounting for corporate cultures and attitudes.
    But end the end, my example was to illustrate that not all problems with redo and control files are mitigated with disk mirroring.

  • Créating new redo log group with dataguard

    Hi,
    is there an impact on the standby database if i create a new redo log group on the primary database?
    Thanks

    Hello,
    No, there is no impact at all, it will be a completely independent operation, just be sure to replicate the operation on the Standby database - even if the standby_file_management parameter is set to 'AUTO' I don't believe that that (automatic file management) applies to redo logs, only data files.

  • Redo log groups on ASM

    Hi All
    Is there any difference between creating redo log groups on ASM and creating the same redo log groups on Cluster file system ? if yes , can you please give me an example ?
    Thanks

    ASM supports redo log files like cluster filesystems. But as far as I know Oracle strongly recommends to place redo log files on different physical disks than the datafiles and the archivelogs also. So if you are planning to place your redo logs on the ASM maybe it is better to create a seperate ASM diskgroup.
    ASM also has the ability to stripe and mirror the disks under a diskgroup so this functionality also gives you better performance according to the configuration you already have or planning to have. Of course it depends on your cluster disk infrastructure and ASM infrastructure also.
    You should also check the configuration of the storage and the LUN architecture to avoid double stripe issues.

Maybe you are looking for