Stale status of Redo log files...

Hi ,
Why in the following sql results , the log file situated in group#3 is not stale as it is not currently used.....????
SQL> select * from v$log;
    GROUP#    THREAD#  SEQUENCE#      BYTES    MEMBERS ARCHIVED STATUS           FIRST_CHANGE# FIRST_TIME
         1          1        485   52428800          1 NO       CURRENT               14310098 17/05/2007
         2          1        483   52428800          1 NO       INACTIVE              14265944 16/05/2007
         3          1        484   52428800          1 NO       INACTIVE              14292318 17/05/2007
SQL>
SQL> select * from V$LOGFILE;
    GROUP# STATUS  TYPE    MEMBER                                                                           IS_RECOVERY_DEST_FILE
         3         ONLINE  C:\ORACLE\PRODUCT\10.2.0\ORADATA\EPESY\REDO03.LOG                                NO
         2 STALE   ONLINE  C:\ORACLE\PRODUCT\10.2.0\ORADATA\EPESY\REDO02.LOG                                NO
         1         ONLINE  C:\ORACLE\PRODUCT\10.2.0\ORADATA\EPESY\REDO01.LOG                                NONOTE : I use Oracle 10g v.2 on WinXp platform. The database is running in NOARCHIVELOG mode.
Many thanks,
Simon

The normal status is null (File is in use).
The stale status indicates a 'problem', as documentation part below:
A redo log file becomes INVALID if the database cannot access it. It becomes STALE if the database suspects that it is not complete or correct. A stale log file becomes valid again the next time its group is made the active group.

Similar Messages

  • How to find the configuration status of REDO logs files?

    I am in the process of moving the redo log files.
    Before that I want to find out whether it is set up as duplex or any other configurations.
    How to find the REDO log configurations.
    Oracle 10g R2
    Thank you,
    Smith

    Example:
    Not duplexed redo log - if number of member is 1, then it is not duplexed:
    SQL> select group#, members from v$log;
        GROUP#    MEMBERS
             1          1
             2          1
             3          1
    SQL> select group#, member from v$logfile;
        GROUP# MEMBER
             1 /u01/app/oracle/oradata/db1/redo01.log
             2 /u01/app/oracle/oradata/db1/redo02.log
             3 /u01/app/oracle/oradata/db1/redo03.log
    SQL> alter database add logfile member '/u01/app/oracle/oradata/db1/redo01_2.log' to group 1;
    Database altered.
    SQL> alter database add logfile member '/u01/app/oracle/oradata/db1/redo02_2.log' to group 2;
    Database altered.
    SQL> alter database add logfile member '/u01/app/oracle/oradata/db1/redo03_2.log' to group 3;
    Database altered.Duplexed redolog
    SQL> select group#, members from v$log;
        GROUP#    MEMBERS
             1          2
             2          2
             3          2
    SQL> select group#, member from v$logfile;
        GROUP# MEMBER
             1 /u01/app/oracle/oradata/db1/redo01.log
             2 /u01/app/oracle/oradata/db1/redo02.log
             3 /u01/app/oracle/oradata/db1/redo03.log
             1 /u01/app/oracle/oradata/db1/redo01_2.log
             2 /u01/app/oracle/oradata/db1/redo02_2.log
             3 /u01/app/oracle/oradata/db1/redo03_2.log

  • 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

  • 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

  • Problem in creating database -Missing Redo log file

    I am try to create a new database using DBCA .While creating a database it shows the error oracle instance terminated.Force Disconnected.
    My alert log file is
    Errors in file /u01/app/oracle/diag/rdbms/oracl/oracl/trace/oracl_ora_5424.trc:
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/oracl/redo01.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    Wed Nov 06 10:07:27 2013
    Errors in file /u01/app/oracle/diag/rdbms/oracl/oracl/trace/oracl_ora_5424.trc:
    ORA-00313: open failed for members of log group 2 of thread 1
    ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/oracl/redo02.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    Errors in file /u01/app/oracle/diag/rdbms/oracl/oracl/trace/oracl_ora_5424.trc:
    ORA-00313: open failed for members of log group 3 of thread 1
    ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/oracl/redo03.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    Wed Nov 06 10:07:38 2013
    Setting recovery target incarnation to 2
    Wed Nov 06 10:07:38 2013
    Assigning activation ID 1876274518 (0x6fd5ad56)
    Thread 1 opened at log sequence 1
      Current log# 1 seq# 1 mem# 0: /u01/app/oracle/oradata/oracl/redo01.log
    Successful open of redo thread 1
    Wed Nov 06 10:07:38 2013
    MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
    Wed Nov 06 10:07:38 2013
    SMON: enabling cache recovery
    Errors in file /u01/app/oracle/diag/rdbms/oracl/oracl/trace/oracl_ora_5424.trc  (incident=1345):
    ORA-00600: internal error code, arguments: [kpotcgah-7], [12534], [ORA-12534: TNS:operation not supported
    Incident details in: /u01/app/oracle/diag/rdbms/oracl/oracl/incident/incdir_1345/oracl_ora_5424_i1345.trc
    Wed Nov 06 10:07:46 2013
    Trace dumping is performing id=[cdmp_20131106100746]
    Errors in file /u01/app/oracle/diag/rdbms/oracl/oracl/trace/oracl_ora_5424.trc:
    ORA-00600: internal error code, arguments: [kpotcgah-7], [12534], [ORA-12534: TNS:operation not supported
    Error 600 happened during db open, shutting down database
    USER (ospid: 5424): terminating the instance due to error 600
    Instance terminated by USER, pid = 5424
    ORA-1092 signalled during: alter database "oracl" open resetlogs...
    ORA-1092 : opiodr aborting process unknown ospid (5424_47935551851664)
    Wed Nov 06 10:07:47 2013
    ORA-1092 : opitsk aborting process
                                                                                                                                   251,1         95%

    >I am try to create a new database using DBCA
    >Please help me to resolve this issue.My redo log file was missing
    DROP and recreate the database.  It is a *new* database without any data.
    Check what datafile locations and redo log file locations you specify when creating the new database. Check if you have permissions and enough disk space.
    Hemant K Chitale

  • How to remove a redo log file

    Hi Experts,
    I want to remove a wrong redo log file from 10G R2 database in window.
    how to do that without loss data?
    my steps as
    1. alter system switch logfile;
    2. select * from v$log;
    which ARC and sataus do I can drop redo log file based on above SQL
    no archive and active status?
    ALso Which account should I do above action?
    fExamp, system account added redo log file, i only
    can drop by system? how about sys?
    Thanks help in detail steps
    Jim
    Edited by: user589812 on Dec 23, 2008 4:35 PM

    Jim,
    Check this link out for how to drop a redo log file
    Make sure a redo log group is archived (if archiving is enabled) before dropping it. To see whether this has happened, use the V$LOG view.
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/onlineredo.htm#i1006489
    SELECT GROUP#, ARCHIVED, STATUS FROM V$LOG;
       GROUP# ARC STATUS
            1 YES ACTIVE
            2 NO  CURRENT
            3 YES INACTIVE
            4 YES INACTIVE
    Drop a redo log group with the SQL statement ALTER DATABASE with the DROP LOGFILE clause.
    The following statement drops redo log group number 3:
    ALTER DATABASE DROP LOGFILE GROUP 3;

  • 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

  • Require 9i Primary and Standby redo logs files same size?

    Hi,
    We have 9.2.0.6 Oracle RAC (2 node) and configured data guard (physical standby).
    I want to increase redo log files size, but i can't this do same time primary and standby side.
    Is there a rule, primary and standby database instances have same size redo log files?
    If I increase only primary redo log files, is there any side effect? However I try this issue on test system. I increased all primary redo log files(if status='INACTIVE' drop redo log group and add redo log group, switch logfile,...)
    , but i couldn't changed standby side. So the system is work well. Is this correct solution or not? How can i increase both sides redo log files?
    Thank you for helps..

    Thank you for your helps.. I found this issue answer:
    http://download-west.oracle.com/docs/cd/B19306_01/server.102/b14239/manage_ps.htm#i1010448
    Consequently, when you add or drop an online redo log file at the primary site, it is important that you synchronize the changes in the standby database by following these steps:
    If Redo Apply is running, you must cancel Redo Apply before you can change the log files.
    If the STANDBY_FILE_MANAGEMENT initialization parameter is set to AUTO, change the value to MANUAL.
    Add or drop an online redo log file:
    To add an online redo log file, use a SQL statement such as this:
    SQL> ALTER DATABASE ADD LOGFILE '/disk1/oracle/oradata/payroll/prmy3.log' SIZE 100M;
    To drop an online redo log file, use a SQL statement such as this:
    SQL> ALTER DATABASE DROP LOGFILE '/disk1/oracle/oradata/payroll/prmy3.log';
    Repeat the statement you used in Step 3 on each standby database.
    Restore the STANDBY_FILE_MANAGEMENT initialization parameter and the Redo Apply options to their original states.
    bye..

  • 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.

  • Redo log files are not applied in DR of primary

    Hi All,
    I have a DR database of primary on QA Serevr. The Redo log files are not properly applied in the DR database.
    The Oracle version is 11.2.0.1 Some of the files get shipped and applied to DR database automatically but not all.
    SQL> select status, error from v$archive_dest where dest_id=2; gives following massage
    ERROR     ORA-16086: Redo data cannot be written to the standby redo log
    Please suggest.
    Regards,
    Shashi

    Hi,
    Sorry for delay in response. Here I am attaching the error captured in standby database.
    Please advise
    alert_abc.log
    RFS[1780]: Identified database type as 'physical standby': Client is LGWR SYNC pid 21855
    Primary database is in MAXIMUM AVAILABILITY mode
    Standby controlfile consistent with primary
    Standby controlfile consistent with primary
    RFS[1780]: No standby redo logfiles of file size 94371840 AND block size 512 exist
    Clearing online log 16 of thread 0 sequence number 0
    Errors in file /oracle/diag/rdbms/abc_location11/abc/trace/abc_rfs_27994.trc:
    ORA-00367: checksum error in log file header
    ORA-00315: log 16 of thread 0, wrong thread # 1 in header
    ORA-00312: online log 16 thread 0: '/oracle/abc/origlogB/log_g116m1.dbf'
    Mon Nov 14 00:49:16 2011
    Clearing online log 9 of thread 0 sequence number 0
    Errors in file /oracle/diag/rdbms/abc_location11/abc/trace/abc_arc0_15653.trc:
    /oracle/diag/rdbms/abc_location11/abc/trace/abc_rfs_27994.trc
    2011-11-14 00:49:19.385
    DDE rules only execution for: ORA 312
    START Event Driven Actions Dump -
    END Event Driven Actions Dump -
    START DDE Actions Dump -
    Executing SYNC actions
    START DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (Async) -
    DDE Action 'DB_STRUCTURE_INTEGRITY_CHECK' was flood controlled
    END DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (FLOOD CONTROLLED, 1 csec) -
    Executing ASYNC actions
    END DDE Actions Dump (total 0 csec) -
    ORA-00367: checksum error in log file header
    ORA-00315: log 16 of thread 0, wrong thread # 1 in header
    ORA-00312: online log 16 thread 0: '/oracle/abc/origlogB/log_g116m1.dbf'
    DDE rules only execution for: ORA 312
    START Event Driven Actions Dump -
    END Event Driven Actions Dump -
    START DDE Actions Dump -
    Executing SYNC actions
    START DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (Async) -
    DDE Action 'DB_STRUCTURE_INTEGRITY_CHECK' was flood controlled
    END DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (FLOOD CONTROLLED, -641 csec) -
    Executing ASYNC actions
    END DDE Actions Dump (total 0 csec) -
    ORA-19527: physical standby redo log must be renamed
    ORA-00312: online log 16 thread 0: '/oracle/abc/origlogB/log_g116m1.dbf'
    Error 19527 clearing SRL 16
    /oracle/diag/rdbms/abc_location11/abc/trace/abc_arc0_15653.trc
    ORA-19527: physical standby redo log must be renamed
    ORA-00312: online log 9 thread 0: '/oracle/abc/origlogA/log_g19m1.dbf'
    Error 19527 clearing SRL 9
    DDE rules only execution for: ORA 312
    START Event Driven Actions Dump -
    END Event Driven Actions Dump -
    START DDE Actions Dump -
    Executing SYNC actions

  • Redo log files lost in Disk Corruption/failure

    DB version:10gR2
    In one of our test databases, I have lost all members of a group due to disk corruption(it was a bad practise to store both members on the same filesystem)
    Database is still up. We don't have a backup of the lost redo log group. Altogether we had 3 redo log groups. this is what i am going to do to fix this issue.
    Step 1. Add a redo log group
    ALTER DATABASE
    ADD LOGFILE ('/u04/oradata/ora67tst/log4a.rdo',
       '/u05/oradata/ora67tst/log4b.rdo') SIZE 15m;Step 2. Drop the corrupted redo log group
    ALTER DATABASE DROP LOGFILE GROUP 2;Is this the right way to go about fixing this issue?
    The documentation says that you need to make sure a redo log group is archived before you DROP it.
    When i use the query
    SQL>SELECT GROUP#, ARCHIVED, STATUS FROM V$LOG;
        GROUP# ARC STATUS
             1 YES  ACTIVE
             2 NO  CURRENT
             3 NO  INACTIVE
    How can i force the archiving of a redo log group 2?
    Edited by: Citizen_2 on May 28, 2009 10:10 AM
    Edited by: Citizen_2 on May 28, 2009 10:11 AM

    Citizen_2 wrote:
    How can i force the archiving of a redo log group 2?How could you archive a log group when you have lost all members of that group?
    Have you checked out this documentation: [Recovering After the Loss of Online Redo Log Files|file://///castle/1862/Home%20Directories/Vaillancourt/Oracle%2010gR2%20Doc/backup.102/b14191/recoscen008.htm#sthref1872]
    More specifically:
    If the group is . . .      Current      
    Then . . .
    It is the log that the database is currently writing to.
    And you should . . .
    Attempt to clear the log; if impossible, then you must restore a backup and perform incomplete recovery up to the most recent available redo log.
    >
    HTH!

  • Manual archiving of redo log files....

    Hi ,
    If the database is running in NOARCHIVELOG mode , is it possible to archive the redo log files manually.... and how..????
    Note: I use Oracle 10g v.2
    Many thanks,
    Simon

    Having issued the command , i noticed that the USE_DB_RECOVERY_FILE_DEST is the destination of LOG_ARCHIVE_DEST_10:
    SQL> select dest_id,dest_name,status,destination from V$ARCHIVE_DEST;
       DEST_ID DEST_NAME                                                                        STATUS    DESTINATION
             1 LOG_ARCHIVE_DEST_1                                                               VALID     C:\oracle\product\10.2.0\flash_recovery_area\EPESY\ARCHIVELOG\
             2 LOG_ARCHIVE_DEST_2                                                               INACTIVE 
             3 LOG_ARCHIVE_DEST_3                                                               INACTIVE 
             4 LOG_ARCHIVE_DEST_4                                                               INACTIVE 
             5 LOG_ARCHIVE_DEST_5                                                               INACTIVE 
             6 LOG_ARCHIVE_DEST_6                                                               INACTIVE 
             7 LOG_ARCHIVE_DEST_7                                                               INACTIVE 
             8 LOG_ARCHIVE_DEST_8                                                               INACTIVE 
             9 LOG_ARCHIVE_DEST_9                                                               INACTIVE 
            10 LOG_ARCHIVE_DEST_10                                                              VALID     USE_DB_RECOVERY_FILE_DESTBut... i have set the LOG_ARCHIVE_DEST parameter not ...._10.
    How the system will point to the directory i've set in my previous alter system command...- when i use the archive log list???
    Many thanks,
    Simon

  • Filled redo log files are available to LGWR for reuse

    Hi,
    Oracle version:
    Oracle Database 10g Release 10.2.0.4.0 -
    OS:Windows XP
    In oracle documentation it is mentioned that:
    Filled redo log files are available to LGWR for reuse depending on whether archiving is enabled.
    *> If archiving is disabled (the database is in NOARCHIVELOG mode), a filled redo log file is available after the changes recorded in it have been written to the datafiles*.
    Link for Documentation is:
    http://docs.oracle.com/cd/B28359_01/server.111/b28310/onlineredo001.htm
    My doubt is:
    Redo Records are written to datafiles also??

    user12141893 wrote:
    Does it mean:
    Suppose:
    Online redo log files contains some redo entries and database buffer cache contains some data and this data belong to redo entries of redo log files.
    Now this redo log file can't be reused until those (related) blocks of database buffer cache are written into datafiles.
    This is sort of correct. If the log file would be filled up , LGWR would switch over to the next log group and would initiate a Log Switch which would further trigger DBWR to start checkpointing the content protected by this log group to the data file. By the time this operation would be going on, the Log group's members would have the status of Active and once it would be complete, the status would be marked to Inactive which means that this log group and its members can be reused by LGWR.
    HTH
    Aman....

  • Reg:Redo log files

    Hi,
    By mistake the redo log files have been removed.
    Hence we tried to create the redo log files.
    After creating it when select * from v$log is done, it is as follows
    SQL> select * from v$log;
    GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS
    FIRST_CHANGE# FIRST_TIM
    1 1 0 1073741824 1 YES UNUSED
    0
    3 1 0 1073741824 1 YES UNUSED
    0
    2 1 0 1073741824 1 NO CURRENT
    179433372 20-NOV-10
    Due to this, whatever alter command we use, it is not working.
    For ex.
    SQL> alter database open resetlogs;
    alter database open resetlogs
    ERROR at line 1:
    ORA-01194: file 1 needs more recovery to be consistent
    ORA-01110: data file 1: '/alcatel/oracle/oradata/SNM/system01.dbf'
    SQL> alter database mount;
    alter database mount
    ERROR at line 1:
    ORA-01100: database already mounted
    SQL> alter system switch logfile;
    alter system switch logfile
    ERROR at line 1:
    ORA-01109: database not open
    SQL> ALTER DATABASE OPEN;
    ALTER DATABASE OPEN
    ERROR at line 1:
    ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
    WE want to change the status in v$log table from Current to ACTIVE and UNUSED to INACTIVE.
    How can we do that?
    Can anyone help us?
    Regards
    Srini

    Hi ,
    WE have tried those but in vain..
    Please find the error logs
    SQL> alter system switch logfile;
    alter system switch logfile
    ERROR at line 1:
    ORA-01109: database not open
    SQL> alter database open resetlogs;
    alter database open resetlogs
    ERROR at line 1:
    ORA-01194: file 1 needs more recovery to be consistent
    ORA-01110: data file 1: '/alcatel/oracle/oradata/SNM/system01.dbf'
    SQL> ORA-01194: file 1 needs more recovery to be consistent
    ORA-01110: data file 1: '/alcatel/oracle/oradata/SNM/system01.dbf'SP2-0734: unknown command beginning "ORA-01194:..." - rest of line ignored.
    SQL> ^C
    SQL> recover database until cancel;
    ORA-00283: recovery session canceled due to errors
    ORA-01610: recovery using the BACKUP CONTROLFILE option must be done
    SQL> alter database open resetlogs;
    alter database open resetlogs
    ERROR at line 1:
    ORA-01194: file 1 needs more recovery to be consistent
    ORA-01110: data file 1: '/alcatel/oracle/oradata/SNM/system01.dbf'
    SQL> recover database until cancel using backup controlfile;
    ORA-00279: change 179433372 generated at 11/20/2010 18:00:10 needed for thread
    1
    ORA-00289: suggestion : /alcatel/oracle/admin/SNM/arch/arch_1_635_666206692.arc
    ORA-00280: change 179433372 for thread 1 is in sequence #635
    Srini

  • Backup vs redo log files

    Hi,
    Can anyone tell me what's the real difference between a backup file and a redo log file/archived redo log file and the scenarios (examples) when each of them can be used (for example, "......") ? Both are used for database/instance recovery. I have read the concepts of there 2 terms, but I need some additional information about the difference.
    Thanks!

    Roger25 wrote:
    What i still don't understand is how redo mechanism works; I know, redo logs records changes made to the database and it's used to re-do informations in case of a system failure/crash, for example. Ok, let's say I have a huge update, but when the system crash has occured, the transaction is neither comitted, nor rolled back. Then, how this redo is useful? If a system crash occur, all those updates aren't rolled back automatically? So the database state is as before executing that huge update? So in this case, 'what to redo'?No, with the system's crash, the transaction never gets a chance to get committed (and even rolled back) because a commit is only supposed to happen if there is an explicit or implicit commit statement is issued. Now, for the redo , with the statement, a commit marker is entered at the end of the redo stream of that transaction denoting that it's finally over now and for the corresponding transaction, the status is cleared from the transaction table that's stored in the Undo segment in which the Undo information of that transaction is stored. If you have given a huge update, the redo would be very highly required as you should be knowing that it's not all the time that the dirty buffers that are written to the data files unlikely the redo log files which are written every 3 econds. This means, there is a very fair chance that many changes have yet not even propagated to the data files for which the change vectors are now already there in the redo log files. Now, for the sake of clarity, assume that this transaction was actually committed! So now, without those changes be applied to the data files how Oracle can actually show the committed reults when the database next time would be opened? For this purpose, the redo change vectors are required. And for the uncommitted transactions , the applcation of the redo change vectors would keep on updating the Checkpoint numbers of the data files and would eventually get them synched with the control file and redo log files, without which the database would never be opened.
    HTH
    Aman....

Maybe you are looking for