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

Similar Messages

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

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.

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

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

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

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

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.

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.

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.

Adding online redo logs with standby database in place

Hi group,
I have decided to add one new member to my existing redo log groups and an additional redo log group to my primary database.
That change went ok without problems. I assumed that with standby_file_management=auto the equivalent online redo logs are created on the standby database. But this is not the case.
The documentation is unclear about this point and I did not find anything suitable on metalink. The docs suggest to cancel managed recovery on the standy, setting standby_file_management to MANUAL and then adding online logs, quote:
"To add an online redo log, use a SQL statement such as this:
SQL> ALTER DATABASE ADD STANDBY LOGFILE 'prmy3.log' SIZE 100K;"
This however - IMO - adds a new STANDBY redo log to the standby database, what I need is an ONLINE redo log.
Does anybody have some experience to share here?
Facts:
Solaris 8
Oracle 9.2.0.6
Thanks!
Martin

OK, for those who come across the same problem.
You need to create a new standby controlfile, copy it as well as any new online redo log from production to the standby environment.
Once the files are in place, start the standby as normal and open it read only to see if everything is ok:
startup nomount
alter database mount standby database;
alter database open read only
Only when there are no errors in your alert.log you are safe.
Martin

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.

Online redo log switching

Hello.
I have a question about online redo logs.
Assume that I have two small redo log groups in my database. I am processing a big batch load consisting of many inserts, but no checkpoing. The first redo log group gets full, it's switched to the second one. The second one gets full too and it need to be switched to the first. No commit until this time, so (I guess) the data has not been saved to datafiles.
Is that possible? Will the database hung ?
If not the first redo log group gets overwritten, doesn't it? What if, after the commit, the database crashes. I will not be able to restore the operations from the first redo group...?

Depends,
If you are running in archive log mode then when you fill the first redo log group it is copied to the archvielog destination, then when the second is filled its copied and we switch back to the first if the archiver hasn't completed you will get a short 'hang' whillst the archiver completes then the transaction will proceed.
if in no archivelog mode you will just switch back and forth between the two log files.
You may be confused because you think that the datablocks in the buffer cache and datafiles are not updated untill the transaction is completed this is not true, the assumption is that most transactions will be completed and commited for a usefull discussion of the concepts see.
Re: basic concepts

Separate ASM diskgroup for Online redo logs

Version: 11.2.0.3
Platform : Solaris 10
One of the Hitachi support guy has suggested to create a separate disk group for Online redo logs. His rationale was that ORLs was write only files and it would be better to put in a separate disk group.
What do you guys think ?

Tom wrote:
Version: 11.2.0.3
Platform : Solaris 10
One of the Hitachi support guy has suggested to create a separate disk group for Online redo logs. His rationale was that ORLs was write only files and it would be better to put in a separate disk group.
What do you guys think ?
A separate disk group for just the ORL's? The files are indeed write only but that does'nt mean that you would need to "isolate" them over a few disks by putting them in an individual disk group. With one diskgroup spread across several disks, ORL's would enjoy a better IO bandwidth as ASM knows how to deal with them by allocating the AU size of 128kb for them. So as the suggestion factor goes, mine is a no. If you haven't experienced a really really bad performance impact due to the ORL's than may be, you may want to think doing it.
Aman....

Windows Modified date for online redo logs

I am doing a full database backup (oracle 10g) weekly and incremental backups nightly. The database is running in archivelog mode and I am multiplexing the online redo logs. However, when I look in windows the modified date for all Redo logs is displayed at the time the database was started up (Sunday night)... datafiles, controlfiles etc... show the latest modified date correctly.
Is this normal that the modified date is not updating on redo logs or do I need to do something else to ensure my online redo is operating correctly.
Any help would be appreciated.

Redo3 was the setting before the switch... redo1 is now the current log. As regards the alert log... what file should I check... there is nothing showing in OEM.
MEMBER
GROUP# STATUS
D:\ORACLE\PRODUCT\ORADATA\WATLI1\REDO03.LOG
3 ACTIVE
D:\ORACLE\PRODUCT\ORADATA\WATLI1\REDO02.LOG
2 INACTIVE
D:\ORACLE\PRODUCT\ORADATA\WATLI1\REDO01.LOG
1 CURRENT
MEMBER
GROUP# STATUS
E:\BACKUP\ONLINELOGS\REDO01_A.LOG
1 CURRENT
E:\BACKUP\ONLINELOGS\REDO02_A.LOG
2 INACTIVE
E:\BACKUP\ONLINELOGS\REDO03_A.LOG
3 ACTIVE

Online redo log group needed??

Similar Messages

Maybe you are looking for