Dropping online redo!!!

Dear all,
your Views Pls...
i've redo groups with two members each....
if i delete one groups....will its Members will be deleted automatically.?..( i' using Oracle managed files structure..)
one thing more ...after that i've to manually delete .rdo files from O/S..?
ALTER DATABASE DROP LOGFILE GROUP 3;
Thanx in Advance!!!

hi,
thanx for you suggestions..
but alok....my senior has told me to do this..
as i'm not going to do it directly....b'coz i know our prdn. DB...
first i'll try to do this on my test DB...
but...then what should i do now..i've to do it anyway?
Thanx!!!

Similar Messages

  • About the Restrictions of Dropping Online Redo

    Student Guide,7-13, If the database is running in ARCHIVELOG mode and the log file group to which the
    member belongs is not archived, then the member cannot be dropped.
    but:
    SQL> archive log list
    Database log mode Archive Mode
    Automatic archival Disabled
    Archive destination E:\oracle\admin\archive_log
    Oldest online log sequence 1043
    Next log sequence to archive 1045
    Current log sequence 1047
    SQL> select * from v$log;
    GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRST_CHANGE# FIRST_TIME
    1 1 1044 1048576 1 YES INACTIVE
    1762339 2005-06-01 13:44:19
    2 1 1043 1048576 1 YES INACTIVE
    1762335 2005-06-01 13:44:12
    3 1 1045 1048576 2 NO INACTIVE (*****i want to delete group 3 member*****)
    1762344 2005-06-01 13:44:33
    4 1 1046 1048576 1 NO INACTIVE
    1762455 2005-06-01 13:46:11
    5 1 1047 1048576 1 NO CURRENT
    1762460 2005-06-01 13:46:23
    SQL> alter database drop logfile member
    2 .
    SQL> select * from v$logfile;
    GROUP# STATUS TYPE
    MEMBER
    1 ONLINE
    E:\ORACLE\ADMIN\WOSON\DATAFILE\REDO01.LOG
    2 ONLINE
    E:\ORACLE\ADMIN\WOSON\DATAFILE\REDO02.LOG
    3 ONLINE
    E:\ORACLE\ADMIN\WOSON\DATAFILE\REDO03.LOG
    4 ONLINE
    E:\ORACLE\ADMIN\WOSON\DATAFILE\REDO04.LOG
    5 ONLINE
    E:\ORACLE\ADMIN\WOSON\DATAFILE\REDO05.LOG
    3 ONLINE
    E:\ORACLE\ADMIN\WOSON\DATAFILE\REDO03B.LOG (*****i want to delete group 3 member*****)
    6 rows selected.
    SQL> alter database drop logfile member 'E:\ORACLE\ADMIN\WOSON\DATAFILE\REDO03B.
    LOG'
    2 /
    Database altered.
    SQL>
    it is done successfully, why?

    yes ,i drop group 3(ARCHIVED=NO STATUS=INACTIVE) ,it report ORA error ;
    and if drop member ("ARCHIVED=NO STATUS=CURRENT") , it report ORA error also.
    show:
    SQL> select * from v$log;
    GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRS
    T_CHANGE# FIRST_TIME
    1 1 1049 1048576 1 NO INACTIVE
    1762943 2005-06-01 14:10:40
    2 1 1048 1048576 1 YES INACTIVE
    1762941 2005-06-01 14:10:39
    3 1 1050 1048576 1 NO INACTIVE
    1766105 2005-06-01 16:39:51
    4 1 1051 1048576 1 NO INACTIVE
    1766107 2005-06-01 16:39:52
    5 1 1052 1048576 1 NO CURRENT
    1766110 2005-06-01 16:39:52
    Elapsed: 00:00:00.00
    SQL> alter database drop logfile group 3;
    alter database drop logfile group 3
    ERROR at line 1:
    ORA-00350: log 3 of thread 1 needs to be archived
    ORA-00312: online log 3 thread 1: 'E:\ORACLE\ADMIN\WOSON\DATAFILE\REDO03.LOG'
    Elapsed: 00:00:00.00
    SQL> alter database add logfile member 'E:\ORACLE\ADMIN\WOSON\DATAFILE\REDO03b.L
    OG' to group 3;
    Database altered.
    Elapsed: 00:00:02.03
    SQL> start reboot
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    ORACLE instance started.
    Total System Global Area 34675092 bytes
    Fixed Size 453012 bytes
    Variable Size 25165824 bytes
    Database Buffers 8388608 bytes
    Redo Buffers 667648 bytes
    Database mounted.
    Database opened.
    SQL> select * from v$log;
    GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRS
    T_CHANGE# FIRST_TIME
    1 1 1049 1048576 1 NO INACTIVE
    1762943 2005-06-01 14:10:40
    2 1 1048 1048576 1 YES INACTIVE
    1762941 2005-06-01 14:10:39
    3 1 1050 1048576 2 NO INACTIVE
    1766105 2005-06-01 16:39:51
    4 1 1051 1048576 1 NO INACTIVE
    1766107 2005-06-01 16:39:52
    5 1 1052 1048576 1 NO CURRENT
    1766110 2005-06-01 16:39:52
    Elapsed: 00:00:00.00
    SQL> archive log start
    Statement processed.
    SQL> select * from v$log;
    GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRS
    T_CHANGE# FIRST_TIME
    1 1 1049 1048576 1 YES INACTIVE
    1762943 2005-06-01 14:10:40
    2 1 1048 1048576 1 YES INACTIVE
    1762941 2005-06-01 14:10:39
    3 1 1050 1048576 2 YES INACTIVE
    1766105 2005-06-01 16:39:51
    4 1 1051 1048576 1 YES INACTIVE
    1766107 2005-06-01 16:39:52
    5 1 1052 1048576 1 NO CURRENT
    1766110 2005-06-01 16:39:52
    Elapsed: 00:00:00.00
    SQL> alter system switch logfile;
    System altered.
    Elapsed: 00:00:00.02
    SQL> alter system switch logfile;
    System altered.
    Elapsed: 00:00:00.03
    SQL> alter system switch logfile;
    System altered.
    Elapsed: 00:00:00.03
    SQL> select * from v$log;
    GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRS
    T_CHANGE# FIRST_TIME
    1 1 1054 1048576 1 YES INACTIVE
    1766281 2005-06-01 16:44:22
    2 1 1053 1048576 1 YES INACTIVE
    1766279 2005-06-01 16:44:19
    3 1 1055 1048576 2 NO CURRENT
    1766288 2005-06-01 16:44:37
    4 1 1051 1048576 1 YES INACTIVE
    1766107 2005-06-01 16:39:52
    5 1 1052 1048576 1 YES INACTIVE
    1766110 2005-06-01 16:39:52
    Elapsed: 00:00:00.00
    SQL> select * from v$logfile;
    GROUP# STATUS TYPE
    MEMBER
    1 ONLINE
    E:\ORACLE\ADMIN\WOSON\DATAFILE\REDO01.LOG
    2 ONLINE
    E:\ORACLE\ADMIN\WOSON\DATAFILE\REDO02.LOG
    3 ONLINE
    E:\ORACLE\ADMIN\WOSON\DATAFILE\REDO03.LOG
    4 ONLINE
    E:\ORACLE\ADMIN\WOSON\DATAFILE\REDO04.LOG
    5 ONLINE
    E:\ORACLE\ADMIN\WOSON\DATAFILE\REDO05.LOG
    3 ONLINE
    E:\ORACLE\ADMIN\WOSON\DATAFILE\REDO03B.LOG
    6 rows selected.
    Elapsed: 00:00:00.03
    SQL> alter database drop logfile member 'E:\ORACLE\ADMIN\WOSON\DATAFILE\REDO03b.
    LOG'
    2 /
    alter database drop logfile member 'E:\ORACLE\ADMIN\WOSON\DATAFILE\REDO03b.LOG'
    ERROR at line 1:
    ORA-01609: log 3 is the current log for thread 1 - cannot drop members
    ORA-00312: online log 3 thread 1: 'E:\ORACLE\ADMIN\WOSON\DATAFILE\REDO03.LOG'
    ORA-00312: online log 3 thread 1: 'E:\ORACLE\ADMIN\WOSON\DATAFILE\REDO03B.LOG'
    Elapsed: 00:00:00.00
    SQL> alter system switch logfile;
    System altered.
    Elapsed: 00:00:00.03
    SQL> alter database drop logfile member 'E:\ORACLE\ADMIN\WOSON\DATAFILE\REDO03b.
    LOG'
    2 /
    Database altered.
    Elapsed: 00:00:02.00
    SQL>

  • Online redo log files being removed physically

    Grid Infra version: 11.2.0.4
    RDBMS Version: 11.2.0.4
    Although this is a RAC DB, this is not a RAC-specific question. Hence posting it here.
    Few months back, I remember issuing a command similair to below (DROP LOGFILE GROUP ...) and the redo log files were still physically present in the diskgroup.
    If I remember correctly, the file is not deleted physical so that we can use the REUSE functionality (ALTER DATABASE ADD LOGFILE MEMBER '+REDO/orcl/onlinelog/redo1b.log' reuse to group 11; ) ie. you can use the REUSE command to add the logfile of the same name which is physically present in OS Filesystem/Diksgroup to redo log group.
    But today, after I issued the below command, I checked the diskgroup location from ASMCMD
    SQL> alter database drop logfile group 31;
    Database altered.
    From ASMCMD, I can that the file has disappeared physically. Is this a new feature with 11.2.0.4 or am I missing something here ?
    ASMCMD> ls +DATA/msblprd/onlinelog/group_31.548.833154995
    ASMCMD-8002: entry 'group_31.548.833154995' does not exist in directory '+DATA/msblprd/onlinelog/'

    Just to add to what Aman has said.
    It is a bad practice not to let OMF decide the placement of Online redo logs because of this issue especially when you use ASM.
    Executing rm command in Linux/Unix is easy but Dropping ASM aliases in the disk group can be a hassle.
    This is documented.
    "When a redo log member is dropped from the database, the operating system file is not deleted from disk. Rather, the control files of the associated database are updated to drop the member from the database structure. After dropping a redo log file, ensure that the drop completed successfully, and then use the appropriate operating system command to delete the dropped redo log file."
    http://docs.oracle.com/cd/E11882_01/server.112/e25494/onlineredo.htm#ADMIN11324
    BTW . You don't even need to set  db_create_online_log_dest_n to enable OMF for ORLs.
    SQL> show parameter log_dest
    NAME                                 TYPE        VALUE
    db_create_online_log_dest_1          string
    db_create_online_log_dest_2          string
    db_create_online_log_dest_3          string
    db_create_online_log_dest_4          string
    db_create_online_log_dest_5          string
    SQL> show parameter db_create_file_dest
    NAME                                 TYPE        VALUE
    db_create_file_dest                  string      +MBL_DATA
    alter database add logfile thread 4
    group 31 ('+MBL_DATA','+MBL_FRA') size 4096M,
    group 32 ('+MBL_DATA','+MBL_FRA') size 4096M,
    group 33 ('+MBL_DATA','+MBL_FRA') size 4096M,
    group 34 ('+MBL_DATA','+MBL_FRA') size 4096M ;
    Database altered.
    And redo logs will be neatly placed as shown below
       INST     GROUP# MEMBER                                             STATUS           ARC
             4         31 +MBL_DATA/bsblprd/onlinelog/group_31.276.832605441 UNUSED           YES
                          +MBL_FRA/bsblprd/onlinelog/group_31.297.832605445  UNUSED           YES
                       32 +MBL_DATA/bsblprd/onlinelog/group_32.547.832605451 UNUSED           YES
                          +MBL_FRA/bsblprd/onlinelog/group_32.372.832605457  UNUSED           YES
                       33 +MBL_DATA/bsblprd/onlinelog/group_33.548.832605463 UNUSED           YES
                          +MBL_FRA/bsblprd/onlinelog/group_33.284.832605469  UNUSED           YES
                       34 +MBL_DATA/bsblprd/onlinelog/group_34.549.832605475 UNUSED           YES
                          +MBL_FRA/bsblprd/onlinelog/group_34.359.832605481  UNUSED           YES

  • Online redo logs on a physical standby?

    A question on REDO logs on physical standby databases. (10.2.0.4 db on Windows 32bit)
    My PRIMARY has 3 ONLINE REDO groups, 2 members each, in ..ORADATA\LOCP10G
    My PHYSICAL STANDBY has 4 STANDBY REDO groups, 2 members each, in ..ORADATA\SBY10G
    I have shipping occurring from the primary in LGWR, ASYNC mode - max availablility
    However I notice the STANDBY also has ONLINE REDO logs, same as the PRIMARY, in the ..ORADATA\SBY10G folder
    According to the 10g Dataguard docs, section 2.5.1:
    "Physical standby databases do not use an online redo log, because physical standby databases are not opened for read/write I/O."
    I have tried to drop these on the STANDBY when not in apply mode, but I get the following:
    SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
    Database altered.
    SQL> ALTER DATABASE DROP LOGFILE GROUP 3;
    ALTER DATABASE DROP LOGFILE GROUP 3
    ERROR at line 1:
    ORA-01275: Operation DROP LOGFILE is not allowed if standby file management is
    automatic.
    I also deleted them while the STANDBY instance was idle, but it recreated them when moved to MOUNT mode.
    So my question is why is my PHYSICAL recreating and using these, if the docs say the shouldn't?
    I saw the same error mentioned here: prob. with DataGuard
    Is this a case of the STANDBY needing at least a notion of where the REDO logs will need to be should a failover occur, and if the files are already there, the standby database CONTROLFILE will hold onto them, as they are not doing any harm anyway?
    Or, is this a prooduct of having management=AUTOMATIC - i.e. the database will create these 'automatically'
    Ta
    bt

    According to the 10g Dataguard docs, section 2.5.1:
    "Physical standby databases do not use an online redo log, because physical standby databases are not opened for read/write I/O."yes, those are used when database is open.
    You should not perform any changes in Standby. Even if those exist online redo log files, whats the difficulty you have seen?
    These will be used whenever you performed switchover/failover. So nothing to worry on this.
    Is this a case of the STANDBY needing at least a notion of where the REDO logs will need to be should a failover occur, and if the files are already there, the standby database CONTROLFILE will hold onto them, as they are not doing any harm anyway?Then oracle functionality itself harm if you think in that way. When they not used in open then what the harm with that?
    Standby_File_management --> for example if you add any datafile, those information will be in archives/redos once they applied on standby those will be added automatically when it is set to AUTO if its manual, then it creates a unnamed file in $ORACLE_HOME/dbs location later you have to rename that file and recovery need to perform .
    check this http://docs.oracle.com/cd/B14117_01/server.101/b10755/initparams206.htm
    HTH.

  • Multiplexing Online redo logs, archive logs, and control files.

    Currently I am only multiplexing my control files and online redo logs, My archive logs are only going to the FRA and then being backed up to tape.
    We have to replace disks that hold the FRA data. HP says there is a chance we will have to rebuild the FRA.
    As my archive logs are going to the FRA now, can I multiplex them to another disk group? And if all of the control files, online redo logs and archive logs are multiplexed to another disk group, when ASM dismounts the FRA disk group due to insufficient number of disks, will the database remain open and on line.
    If so then I will just need to rebuild the ASM volumes, and the FRA disk group and bring it to the mount state, correct?
    Thanks!

    You can save your online redo logs and archive logs anywhere you want by making use of of init params create_online_log_dest and log_archive_dest_n. You will have to create new redo log groups in the new location and drop the ones in the FRA. The archive logs will simply land wherever you designate with log_archive_dest_n parameters. Moving the control files off FRA is a little trickier because you will need to restore your controlfile to a non-FRA destination and then shutdown your instance, edit the control file param to reflect changes and restart.
    I think you will be happier if you move everything off the FRA diskgroup before dismounting it, and not expecting the db to automagically recover from the loss of files on the FRA.

  • Status of online redo log file INVALID warning appears during online backup

    Hi All,
    I have a peculiar problem in one of the SAP ECC 6.0 systems. The daily online backup is getting completed with warnings.
    Please find below the warnings in DB12 logs:
    BR0335W Status of online redo log file /oracle/AS0/mirrlogB/log_g18m2.dbf is INVALID
    BR0274W File '/oracle/AS0/mirrlogB/log_g18m2.dbf' not found
    BR0335W Status of online redo log file /oracle/AS0/mirrlogA/log_g50_m2.dbf is INVALID
    BR0274W File '/oracle/AS0/mirrlogA/log_g50_m2.dbf' not found
    BR0335W Status of online redo log file /oracle/AS0/mirrlogB/log_g51_m2.dbf is INVALID
    BR0274W File '/oracle/AS0/mirrlogB/log_g51_m2.dbf' not found
    BR0335W Status of online redo log file /oracle/AS0/mirrlogA/log_g52_m2.dbf is INVALID
    BR0274W File '/oracle/AS0/mirrlogA/log_g52_m2.dbf' not found
    BR0335W Status of online redo log file /oracle/AS0/mirrlogA/log_g53_m2.dbf is INVALID
    BR0274W File '/oracle/AS0/mirrlogA/log_g53_m2.dbf' not found
    BR0335W Status of online redo log file /oracle/AS0/mirrlogA/log_g54_m2.dbf is INVALID
    BR0274W File '/oracle/AS0/mirrlogA/log_g54_m2.dbf' not found
    BR0335W Status of online redo log file /oracle/AS0/mirrlogA/log_g55_m2.dbf is INVALID
    BR0274W File '/oracle/AS0/mirrlogA/log_g55_m2.dbf' not found
    BR0335W Status of online redo log file /oracle/AS0/mirrlogA/log_g56_m2.dbf is INVALID
    BR0274W File '/oracle/AS0/mirrlogA/log_g56_m2.dbf' not found
    BR0335W Status of online redo log file /oracle/AS0/mirrlogB/log_g57_m2.dbf is INVALID
    BR0274W File '/oracle/AS0/mirrlogB/log_g57_m2.dbf' not found
    BR0335W Status of online redo log file /oracle/AS0/mirrlogA/log_g58_m2.dbf is INVALID
    BR0274W File '/oracle/AS0/mirrlogA/log_g58_m2.dbf' not found
    BR0335W Status of online redo log file /oracle/AS0/mirrlogB/log_g59_m2.dbf is INVALID
    BR0274W File '/oracle/AS0/mirrlogB/log_g59_m2.dbf' not found
    For the above mentioned alerts I followed the recommendations of SAP Note 491160. I dropped and recreated the mirrorlog files. But the next day again when I checked the backup it finished with warnings. At the database level there is no problem
    SQL> select * from v$logfile;
        GROUP# STATUS  TYPE
    MEMBER
    IS_
            59         ONLINE
    /oracle/AS0/origlogB/log_g59_m1.dbf
    NO
            59         ONLINE
    /oracle/AS0/mirrlogB/log_g59_m2.dbf
    NO
        GROUP# STATUS  TYPE
    MEMBER
    IS_
            58         ONLINE
    /oracle/AS0/origlogA/log_g58_m1.dbf
    NO
            58         ONLINE
    /oracle/AS0/mirrlogA/log_g58_m2.dbf
        GROUP# STATUS  TYPE
    MEMBER
    IS_
    NO
            57         ONLINE
    /oracle/AS0/origlogB/log_g57_m1.dbf
    NO
            57         ONLINE
        GROUP# STATUS  TYPE
    MEMBER
    IS_
    /oracle/AS0/mirrlogB/log_g57_m2.dbf
    NO
            56         ONLINE
    /oracle/AS0/origlogA/log_g56_m1.dbf
    NO
        GROUP# STATUS  TYPE
    MEMBER
    IS_
            56         ONLINE
    /oracle/AS0/mirrlogA/log_g56_m2.dbf
    NO
            55         ONLINE
    /oracle/AS0/origlogA/log_g55_m1.dbf
    NO
            54         ONLINE
    /oracle/AS0/origlogA/log_g54_m1.dbf
        GROUP# STATUS  TYPE
    MEMBER
    IS_
    NO
            54         ONLINE
    /oracle/AS0/mirrlogA/log_g54_m2.dbf
    NO
            53         ONLINE
        GROUP# STATUS  TYPE
    MEMBER
    IS_
    /oracle/AS0/origlogA/log_g53_m1.dbf
    NO
            53         ONLINE
    /oracle/AS0/mirrlogA/log_g53_m2.dbf
    NO
        GROUP# STATUS  TYPE
    MEMBER
    IS_
            52         ONLINE
    /oracle/AS0/origlogA/log_g52_m1.dbf
    NO
            52         ONLINE
    /oracle/AS0/mirrlogA/log_g52_m2.dbf
    NO
        GROUP# STATUS  TYPE
    MEMBER
    IS_
            51         ONLINE
    /oracle/AS0/origlogB/log_g51_m1.dbf
    NO
            51         ONLINE
    /oracle/AS0/mirrlogB/log_g51_m2.dbf
        GROUP# STATUS  TYPE
    MEMBER
    IS_
    NO
            50         ONLINE
    /oracle/AS0/origlogA/log_g50_m1.dbf
    NO
            50         ONLINE
        GROUP# STATUS  TYPE
    MEMBER
    IS_
    /oracle/AS0/mirrlogA/log_g50_m2.dbf
    NO
             8         ONLINE
    /oracle/AS0/origlogB/log_g18m1.dbf
    As you can see from the above output at the database level everything is fine. So why during backup it is giving me warnings in DB12. Any help with this regard will be appreciated.
    Regards
    Mitesh Nair

    Hi Joe,
    My OS is HP-UX. I dont think its a permission problem. Please find below the contents of origlogA and mirrlogA
    predbci2:/oracle/AS0/origlogA#ls -rtl
    total 1433712
    drwxrwxrwx   2 oraas0     dba             96 Oct 15 03:27 cntrl
    -rw-rw----   1 oraas0     dba        104858624 Dec  4 01:50 log_g52_m1.dbf
    -rw-rw----   1 oraas0     dba        104858624 Dec  4 03:51 log_g50_m1.dbf
    -rw-rw----   1 oraas0     dba        104858624 Dec  4 05:51 log_g54_m1.dbf
    -rw-rw----   1 oraas0     dba        104858624 Dec  4 07:52 log_g53_m1.dbf
    -rw-rw----   1 oraas0     dba        104858624 Dec  4 09:50 log_g55_m1.dbf
    -rw-rw----   1 oraas0     dba        104858624 Dec  4 10:50 log_g56_m1.dbf
    -rw-rw----   1 oraas0     dba        104858624 Dec  4 12:41 log_g58_m1.dbf
    predbci2:/oracle/AS0/mirrlogA#ls -rtl
    total 1433728
    -rw-rw----   1 oraas0     dba        104858624 Dec  4 01:50 log_g52_m2.dbf
    -rw-rw----   1 oraas0     dba        104858624 Dec  4 03:51 log_g50_m2.dbf
    -rw-rw----   1 oraas0     dba        104858624 Dec  4 05:51 log_g54_m2.dbf
    -rw-rw----   1 oraas0     dba        104858624 Dec  4 07:52 log_g53_m2.dbf
    -rw-rw----   1 oraas0     dba        104858624 Dec  4 09:50 log_g55_m2.dbf
    -rw-rw----   1 oraas0     dba        104858624 Dec  4 10:50 log_g56_m2.dbf
    -rw-rw----   1 oraas0     dba        104858624 Dec  4 12:41 log_g58_m2.dbf
    Regards
    Mitesh

  • Open database if an active online redo log is missing

    Hi,
    Sorry for the rather long post, but I specified all the steps I performed and couldn't make it shorter :-(
    I need an advice on how to open the database if an active online redo log is missing.
    For test purposes I intentionally performed a shutdown abort when the redo log group 1 was in active state and then renamed its only member (REDO01.LOG) so that the database couldn't perform crash recovery using it. Then upon startup I obviously got the message:
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: 'H:\ORADATA\TESTDB\REDO01.LOG'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 2) The system cannot find the file specified.Ok, so I checked the state of the logs:
    {noformat}
    SQL>SELECT a.GROUP#, first_change#, SEQUENCE#, a.status, SUBSTR(b.MEMBER, 1, 40) MEMBER, b.status mem_status, a.archived
      2    FROM v$log a, v$logfile b
      3   WHERE a.GROUP# = b.GROUP#
      4  ORDER BY a.GROUP#, b.MEMBER;
    GROUP# FIRST_CHANGE#  SEQUENCE# STATUS           MEMBER                         MEM_STA ARC
         1        592134         29 ACTIVE           H:\ORADATA\TESTDB\REDO01.LOG           YES
         2        592268         30 CURRENT          C:\ORADATA\TESTDB\REDO02.LOG           NO
         3        592129         28 ACTIVE           C:\ORADATA\TESTDB\REDO03.LOG           YES
    {noformat}Since opening the database to perform a log switch and thus change the status of the redo log group 1 from ACTIVE to INACTIVE to recreate the member isn't possible, I performed database recovery.
    SQL>recover database until cancel;
    ORA-00279: change 592129 generated at 02/04/2009 10:31:15 needed for thread 1
    ORA-00289: suggestion : C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\TESTDB\ARCHIVELOG\2009_02_04\O1_MF_1_28_%U_.ARC
    ORA-00280: change 592129 for thread 1 is in sequence #28
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    ORA-00279: change 592134 generated at 02/04/2009 10:31:28 needed for thread 1
    ORA-00289: suggestion : C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\TESTDB\ARCHIVELOG\2009_02_04\O1_MF_1_29_%U_.ARC
    ORA-00280: change 592134 for thread 1 is in sequence #29
    ORA-00278: log file 'C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\TESTDB\ARCHIVELOG\2009_02_04\O1_MF_1_28_4RLR3JS9_.ARC' no longer needed for this rec
    overy
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    'C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\TESTDB\ARCHIVELOG\2009_02_04\O1_MF_1_29_4RLR4MF3_.ARC'
    ORA-00279: change 592268 generated at 02/04/2009 10:32:03 needed for thread 1
    ORA-00289: suggestion : C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\TESTDB\ARCHIVELOG\2009_02_04\O1_MF_1_30_%U_.ARC
    ORA-00280: change 592268 for thread 1 is in sequence #30
    ORA-00278: log file 'C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\TESTDB\ARCHIVELOG\2009_02_04\O1_MF_1_29_4RLR4MF3_.ARC' no longer needed for this rec
    overy
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    'C:\ORADATA\TESTDB\REDO02.LOG'
    Log applied.
    Media recovery complete.
    SQL>So for log sequence #28 I accepted the proposed archived redo log in the FRA, for sequence #29 (that's the online redo log that is missing!) I manually specified its archived copy, and for sequence #30 I specified the CURRENT online redo log. And as it seems the media recovery was successful.
    Next I tried to open the database but again got the error:
    SQL>alter database open noresetlogs;
    alter database open noresetlogs
    ERROR at line 1:
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: 'H:\ORADATA\TESTDB\REDO01.LOG'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 2) The system cannot find the file specified.
    The status of the log groups and its members is exactly as it was in the first query I wrote above, i.e. the redo log group 1 is still ACTIVE, so it's needed for crash recovery (which I had already done manually if I understand correctly how Oracle works!). I also checked if the datafiles are inconsistent (described in metalink doc id 1015544.102):
    SQL>SELECT DISTINCT CHECKPOINT_CHANGE#, FUZZY FROM V$DATAFILE_HEADER;
    CHECKPOINT_CHANGE# FUZ
                592269 NOSo, everything seems ok as far as datafile consistency is concerned.
    My question is: how can I rename/drop/clear/whatever the member of redo log group 1 to open the database?
    I tried to rename the log file member, to add another member to it, to open the database with resetlogs, to clear the logfile group 1, but all without success:
    1)
    SQL>alter database clear logfile group 1;
    alter database clear logfile group 1
    ERROR at line 1:
    ORA-01624: log 1 needed for crash recovery of instance testdb (thread 1)
    ORA-00312: online log 1 thread 1: 'H:\ORADATA\TESTDB\REDO01.LOG'
    2)
    SQL>alter database open resetlogs;
    alter database open resetlogs
    ERROR at line 1:
    ORA-01139: RESETLOGS option only valid after an incomplete database recovery
    3)
    SQL>alter database rename file 'H:\ORADATA\TESTDB\REDO01.LOG' to 'C:\ORADATA\TESTDB\REDO01.LOG';
    alter database rename file 'H:\ORADATA\TESTDB\REDO01.LOG' to 'C:\ORADATA\TESTDB\REDO01.LOG'
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01512: error renaming log file H:\ORADATA\TESTDB\REDO01.LOG - new file C:\ORADATA\TESTDB\REDO01.LOG not found
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 2) The system cannot find the file specified.
    4)
    SQL>alter database add logfile member 'C:\ORADATA\TESTDB\REDO01.LOG' to group 1;
    alter database add logfile member 'C:\ORADATA\TESTDB\REDO01.LOG' to group 1
    ERROR at line 1:
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: 'H:\ORADATA\TESTDB\REDO01.LOG'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 2) The system cannot find the file specified.Sorry again for the long post and thank you in advance for any suggestion.
    Regards,
    Jure

    You could check if the recovery was complete by (re)creating the controlfile with the resetlogs option.
    <CREATE CONTROLFILE REUSE DATABASE define_db_name RESETLOGS NOARCHIVELOG
    ...>Thanks for the hint. If possible, could you only check if the steps I'm going to perform are ok.
    I did an "alter database backup controlfile to trace;" and then extracted the create controlfile definition part. So in essence I should run the following statements:
    CREATE CONTROLFILE REUSE DATABASE "TESTDB" RESETLOGS  ARCHIVELOG
        MAXLOGFILES 16
        MAXLOGMEMBERS 3
        MAXDATAFILES 100
        MAXINSTANCES 8
        MAXLOGHISTORY 292
    LOGFILE
      GROUP 1 'C:\ORADATA\TESTDB\REDO01.LOG'  SIZE 20M,
      GROUP 2 'C:\ORADATA\TESTDB\REDO02.LOG'  SIZE 20M,
      GROUP 3 'C:\ORADATA\TESTDB\REDO03.LOG'  SIZE 20M
    -- STANDBY LOGFILE
    DATAFILE
      'C:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\SYSTEM01.DBF',
      'C:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\UNDOTBS01.DBF',
      'C:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\SYSAUX01.DBF',
      'C:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\USERS01.DBF'
    CHARACTER SET EE8MSWIN1250
    ALTER DATABASE OPEN RESETLOGS;
    ALTER TABLESPACE TEMP ADD TEMPFILE 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\TEMP01.DBF' REUSE;Is that correct?
    About the RMAN backups: Wouldn't a 'CATALOG RECOVERY AREA' populate the controlfile with backup information again (I'm not using a recovery catalog in this case)?
    Thanks for the help!
    Regards,
    Jure

  • 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

  • Best practice - online redo logs and virtualization

    I have a 10.1.0.4 instance (soon to be migrated to 11gr2) running under Windows Server 2003.
    We use a non-standard disk distribution scheme -
    on the c: drive we have oracle_home as well as directories for control files and online redo logs.
    on the d: drive we have datafiles
    on the e: drive we have archive log files and another directory with online redo logs and another copy of control file
    my question is this:
    is it smart practice to have ANY online redo logs or control file on the same spindle with archive logs?
    Our setup works fairly well but we are in the process of migrating the instance first to ESX server and SAN and then secondly to 11gtr2 64bit under server 2008 64 and when we bring up our instance on the VM for testing we find that benchmarking the ESX server (dual Xeon 3.4ghz with 48gb RAM running against FalconStor NSS SAN with 15k SAS disks over iSCSI) against the production physical server (dual Xeon 2.0ghz with 4gb RAM using direct attached SATA 7200rpm drives) we find that some processes run faster on the ESX box and some run 40-100% slower. Running Statspack seems to identify lots of physical read waits as well as some waits for redo and controlfiles.
    Is it possible that in addition to any overhead introduced by ESX and iSCSI (we are running Jumbo Frames over 1gb) we may have contention because the archive logs are on the same "spindle" (virtual) as the online redo and control files?
    We're looking at multiple avenues to bring the 2 servers in line from a performance standpoint - db configuration, memory allocation, possible move to 10gb network, possible move to SSD storage tray, possible application rewrites. But from the simplest low hanging fruit idea, if these files should not be on the same spindle thats an easy change to make and possibly eke out an improvement.
    Ideas?
    Mike

    Hi,
    "Old" Oracle standard is to use as many spindles as possible.
    It looks to me, you have only 1 disk with several partitions on it ??
    In my honest opinion you should anyway start by physically seperating OS from Oracle, so let the C: drive to the Windows OS
    Take another physical seperate D: drive to install you application.
    Use yet another set of physical drives, preferably in RAID10 setup, for your database and redo logs
    And finally yet another disk for the archive logs.
    We have recently configured a Windows 2008 server with an 11G Db, which pretty much follows the above setup.
    All non RAID10 disks are RAID1 ( mirror ) and we even have some SSD's for hot tables and redo-logs.
    The machine, or must I say the database, operates like a high speed train, very, very fast.
    Ofcourse keep in mind the number of cores ( not only for licensing ) and the amount of memory.
    Try to prevent the system from swapping, because that is a performance killer!
    Edit: And even if you put a virtual layer in between, try to seperate the virtual disks as much as possible over physical disks
    Success!
    FJFranken
    Edited by: fjfranken on 7-okt-2011 7:19

  • Can we use online redo log to recover lost datafile in NOARCHIVE mode?

    I am working on OCA exam and confued about these 2 sample questions. (similar questions with totally different answer)
    Please give me hint about the different between these 2 questions.
    ** If the database is in NOARCHIVELOG mode, and one of the datafile for tablespace USERS is lost, what kind of recovery is possible? (answer: B)
    A. All transactions except those in the USERS tablespace are recoverable up to the loss of the datafile.
    B. Recovery is possible only up to the point in time of the last full database backup.
    C. The USERS tablespace is recoverable from the online redo log file as long as none of the redo log files have been reused since the last backup.
    D. Tablespace point in time recovery is available as long as a full backup of the USERS tablespace exists.
    ** The database of your company is running in the NOARCHIVELOG mode. You perform a complete backup of the database every night. On Monday morning, you lose the USER1.dbf file belonging to the USERS tablespace. Your database has four redo log groups, and there have been two log switches since Sunday night's backup.
    Which is true (answer: B)
    A. The database cannot be recovered.
    B. The database can be recovered up to the last commit.
    C. The database can be recovered only up to the last completed backup.
    D. The database can be recovered by performing an incomplete recovery.
    E. The database can be recovered by restoring only the USER!.dbf datafile from the most recent backup.

    I think Gaurav is correct, you can recover to the last commit even in NOARCHIVELOG, as long as all the changes in the redo logs have not been overwritten. So answer should be B for question 2.
    Here is my test:
    SQL> select log_mode from v$database;
    LOG_MODE
    NOARCHIVELOG
    SQL> select tablespace_name, file_name from dba_data_files;
    TABLESPACE_NAME
    FILE_NAME
    USERS
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA101RC\USERS01.DBF
    SYSAUX
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA101RC\SYSAUX01.DBF
    UNDOTBS1
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA101RC\UNDOTBS01.DBF
    SYSTEM
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA101RC\SYSTEM01.DBF
    DATA
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA101RC\DATA01.DBF
    SQL> create table names
    2 ( name varchar(16))
    3 tablespace users;
    Table created.
    so this segment 'names' is created in the datafile users01.
    At this point I shut down and mount the DB, then:
    RMAN> backup database;
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:29
    Finished backup at 06-OCT-07
    SQL>alter database open
    SQL> insert into names values ('pippo');
    1 row created.
    SQL> commit;
    Commit complete.
    SQL>shutdown immediate;
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    At this point I delete datafile users01 and restart:
    SQL> startup
    ORACLE instance started.
    Total System Global Area 167772160 bytes
    Fixed Size 1247900 bytes
    Variable Size 67110244 bytes
    Database Buffers 96468992 bytes
    Redo Buffers 2945024 bytes
    Database mounted.
    ORA-01157: cannot identify/lock data file 4 - see DBWR trace file
    ORA-01110: data file 4: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA101RC\USERS01.DBF'
    restoring the backup taken before inserting the value 'pippo' in table names:
    RMAN> restore database;
    Starting restore at 06-OCT-07
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting datafile backupset restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    restoring datafile 00001 to C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA101RC\SYSTEM01.D
    BF
    restoring datafile 00002 to C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA101RC\UNDOTBS01.
    DBF
    restoring datafile 00003 to C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA101RC\SYSAUX01.D
    BF
    restoring datafile 00004 to C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA101RC\USERS01.DB
    F
    restoring datafile 00005 to C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA101RC\DATA01.DBF
    channel ORA_DISK_1: reading from backup piece C:\ORACLE\PRODUCT\10.2.0\DB_1\DATA
    BASE\0AITR52K_1_1
    channel ORA_DISK_1: restored backup piece 1
    piece handle=C:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\0AITR52K_1_1 tag=TAG20071006
    T181337
    channel ORA_DISK_1: restore complete, elapsed time: 00:02:07
    Finished restore at 06-OCT-07
    RMAN> recover database;
    Starting recover at 06-OCT-07
    using channel ORA_DISK_1
    starting media recovery
    media recovery complete, elapsed time: 00:00:05
    Finished recover at 06-OCT-07
    SQL> alter database open;
    Database altered.
    SQL> select * from names;
    NAME
    pippo
    SQL>
    enrico

  • Moving the online redo log files to different location

    We just installed few more drives into our sandbox system and I want to move the online redo log files for better performance.  We've got the SAPARCH directory moved to a different location. 
    Does anyone know how/where I can change the parameters so redo log files are pointed at different drives?  It's not in the <b>init<SID>.ora</b> file...
    Regards,
    Sumit

    Hi Sumit,
    The following link contains information about moving the redo logs:
    http://www.stanford.edu/dept/itss/docs/oracle/9i/server.920/a96521/onlineredo.htm
    Best regards,
    Alwin

  • Physical Standby Online Redo log  files,

    Hi,
    I'm trying to create a physical standby database (10.2.0.3). I'm a little confused about the requirement for online redo logs on the standby.
    in my standby alert log I get the following when I issue:
    SQL> alter database recover managed standby database disconnect from session
    "ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '/appl/oradata/prod/prod_1_redo_01_02.log'
    ORA-27037: unable to obtain file status
    SVR4 Error: 2: No such file or directory
    Additional information: 3"
    /appl/oradata/prod/prod_1_redo_01_02.log is the path to the location of the online redo logs on the production system. This file does not exist on the standby filesystem so the error is correct.
    I assume that it gets this information from the standby control file I created on the production system and copied over to the standby.
    Do I need to copy the online redo logs from the primary over to the standby site or do I need to create online redo logs on the standby?
    Does the standby need to have redo log files?
    I'm not talking about 'standby log files' of the type created using 'alter database add standby log file'. I've not got that far yet.
    I just need to establish if a physical standby requires online redo log files?
    Thanks in advance,
    user234564

    I wanted to update this thread since I've been dealing with the exact same errors. The basic question is: "does a physical standby need the online redo logs?"
    Answer: Not really, until one wants to switchover or failover (and become a primary database). Furthermore, whenever the MRP process is started, Oracle prepares for a possible switchover/failover by "clearing" the online redo logs (MetaLink note# 352879.1). It is not a big deal, since Oracle will build the actual redo files when the "alter database open resetlogs" is accomplished during a "role transition."
    In our situation, we have decided to use our standby for nightly exports. We stop MRP, open the database read-only, then restart MRP. We built these standby DBs with RMAN. The RMAN duplicate process will not build the online redo log files until the database is opened for read/write (with resetlogs). However, we haven't had a need for read/write (i.e. a switchover).
    Thus, every morning we have been getting the same errors that "user234564" posted above. At first the errors seemed scary, then we realized they were just a nusiance. In order to clean things up, all I did was just "cp" our stanby redo logs (SRL) into our online redo directories ensuring the names matched what was in v$logfile. When I restarted MRP, the alert log clearly showed Oracle clearing these "newly found" online redo logs.

  • The file structure online redo log, archived redo log and standby redo log

    I have read some Oracle documentation for file structure and settings in Data Guard environment. But I still have some doubts. What is the best file structure or settings in Oracle 10.2.0.4 on UNIX for a data guard environment with 4 primary databases and 4 physical standby databases. Based on Oracle documents, there are 3 redo logs. They are: online redo logs, archived redo logs and standby redo logs. The basic settings are:
    1. Online redo logs --- This redo log must be on Primary database and logical standby database. But it is not necessary to be on physical standby database because physical standby is not open. It doesn't generate redo log. However, if don't set up online redo log on physical standby, when primary failover and switch standby as primary. How can standby perform without online redo logs? In my standby databases, online redo logs have been set up.
    2. Archived redo logs --- It is obviously that primary database, logical and physical standby database all need to have this log file being set up. Primary use it to archive log files and ship to standby. Standby use it to receive data from archived log and apply to database.
    3. Standby redo logs --- In the document, it says A standby redo log is similar to an online redo log, except that a standby redo log is used to store redo data received from another database. A standby redo log is required if you want to implement: The maximum protection and maximum availability levels of data protection and Real-time apply as well as Cascaded destinations. So it seems that this standby redo log only should be set up on standby database, not on primary database. Am my understanding correct? Because I review current redo log settings on my environment, I have found that Standby redo log directory and files have been set up on both primary and standby databases. I would like to get more information and education from experts. What is the best setting or structure on primary and standby database?

    FZheng:
    Thanks for your input. It is clear that we need 3 type of redo logs on both databases. You answer my question.
    But I have another one. In oracle ducument, it says If you have configured a standby redo log on one or more standby databases in the configuration, ensure the size of the current standby redo log file on each standby database exactly matches the size of the current online redo log file on the primary database. It says: At log switch time, if there are no available standby redo log files that match the size of the new current online redo log file on the primary database. The primary database will shut down
    My current one data gurard envirnment setting is: On primary DB, online redo log group size is 512M and standby redo log group size is 500M. On the standby DB, online redo log group size is 500M and standby redo log group size is 750M.
    This was setup by someone I don't know. Is this setting OK? or I should change Standby Redo Log on standby DB to 512M to exactly meatch with redo log size on primary?
    Edited by: 853153 on Jun 22, 2011 9:42 AM

  • Problem with Whole Database Online+Redo log Backup

    Dear Marcus Sir,
    I am facing while taking "Whole Database Online+Redo log Backup" through DB13 T-Code.
    Below is the "Problem part of the Backup log", however if you need I will send you full log.
    Hope you will find out problem soon
    #FILE..... /oracle/ANP/sapdata2/sr3_8/sr3.data8
    #SAVED.... sr3.data8  ANPB260810/12
    BR0280I BRBACKUP time stamp: 2010-08-27 11.03.22
    BR0063I 9 of 51 files processed - 19400.070 MB of 135986.469 MB done
    BR0204I Percentage done: 14.27%, estimated end time: 11:47
    BR0001I *******___________________________________________
    BR0202I Saving /oracle/ANP/sapdata2/sr3_9/sr3.data9
    BR0203I to /dev/rmt0.1 ...
    BR0278E Command output of 'LANG=C dd obs=1024K bs=1024K if=/oracle/ANP/sapdata2/sr3_9/sr3.data9 of=/dev/rmt0.1':
    dd read error: I/O error
    462+0 records in
    462+0 records out
    BR0280I BRBACKUP time stamp: 2010-08-27 11.03.36
    BR0279E Return code from 'LANG=C dd obs=1024K bs=1024K if=/oracle/ANP/sapdata2/sr3_9/sr3.data9 of=/dev/rmt0.1': 2
    BR0222E Copying /oracle/ANP/sapdata2/sr3_9/sr3.data9 to/from /dev/rmt0.1 failed due to previous errors
    BR0280I BRBACKUP time stamp: 2010-08-27 11.03.41
    BR0317I 'Alter tablespace PSAPSR3 end backup' successful
    BR0056I End of database backup: bedziydp.ant 2010-08-27 11.03.36
    BR0280I BRBACKUP time stamp: 2010-08-27 11.03.41
    BR0054I BRBACKUP terminated with errors
    Warm Regards
    Ahsan

    Hi,
    since you are getting a read error, it might as well be, that your datafile is defective.
    Try the same dd-command to /dev/null, to see if it is possible to read the entire file.
    First make sure that your null-device is existing, otherwise you might face a root-fs full problem.
    dd obs=1024K bs=1024K if=/oracle/ANP/sapdata2/sr3_9/sr3.data9 of=/dev/null
    or try a dbverify on it, which would also read the entire file and do a checksum test.
    brbackup -c -u / -m /oracle/ANP/sapdata2/sr3_9/sr3.data9 -t online -w only_dbv
    Good luck
    Volker

  • Commit Completes although current online redo log file have been removed.

    Although i have removed current online redo log file in linux os (Oracle Linux),when i type "commit" it says that "commit complete".
    Is this fair for this princip?*:" if Only when all redo records associated with a given transaction are safely on disk in the online logs is the user process notified that the transaction has been committed."*
    I think that it can lead to loss of data in some cases..I'm using Oracle 11g R2 on OEL (x64)..
    Can anyone explain me ? I'm getting stuck in this situation..
    P.S : I haven't multiplexed current ORL group files...

    Javid wrote:
    Although i have removed current online redo log file in linux os (Oracle Linux),when i type "commit" it says that "commit complete".
    Is this fair for this princip?*:" if Only when all redo records associated with a given transaction are safely on disk in the online logs is the user process notified that the transaction has been committed."*
    I think that it can lead to loss of data in some cases..I'm using Oracle 11g R2 on OEL (x64)..
    Can anyone explain me ? I'm getting stuck in this situation..
    In *nix, a file that is open by a process isn't really deleted until the process that has it completes.  So even though you 'deleted' a redo log, oracle is still holding it.  As soon as you stop your database (maybe even as soon as the db does a log switch) the redo will really be gone and no longer available.  consider the implications for archive logging.
    P.S : I haven't multiplexed current ORL group files...You need to fix that. the online logs are the achilles heel of the database. That's why it is standard practice to multiplex them.

Maybe you are looking for

  • Why isn't the download installer working ?

    I have been trying to download adobe flash player for two weeks.  I tried to download an older version as I am on an older computer. Found old versions in Adobe archives but when I clicked on them they took me to the page that only downloads the curr

  • Different ways to download os yosemite

    can we download the software through a download accelerator or some other way? the internet is not stable here and it gets disconnected in the middle. i got unto 4.96 and then BAM!! dc and gone!! so any other way?? I am in "INDIA"

  • Can you block callers with private caller IDs?

    Hi Everyone, Some phones send a message that a private caller ID will not be accepted. Can I do this on the iPhone? TIA, Lisa

  • Is this Feasible using Flash?

    Hi All, I am new to Flash. I would like to know if the following is possible. Can I have an .swf template file hosted on server to which user can make some changes and download it. Say there is a template for some greeting card made in Flash (swf fil

  • Cannot get past disc 2 reinstall

    I am attempting to resinstall my original software and I keep getting stuck on Disc 2 - it is clean, no scratches and will not proceed past this part of install process.