Why the time of the online redo logs doesn't change?

Oracle 11.1.0.7 on windows 2008.I find the time of the online redo logs doesn't change since Jan 18 when I had restarted database,and the time of some datafiles doesn't change either.the database is always online and changes are wrriting to the files, I don't know how this happened?
would anyone help me? thank you.

ROCK wrote:
I found some datafiles have the latest date,but the other not. They all have write/read operations on them.
and the switching of the redo logs doesn't change the timestamps of the logfiles since Jan.18 when I had restarted the database. this situation does not appear on the early 8.1.7 database on windows 2000
Does this situation normal?Hi,
Why dont you post the output of the query you are using such as
select group#, first_time, status from v$log;
select name, last_time, status from v$datafile;
select name, CHECKPOINT_TIME, status from v$datafile_header;Time stamp wont change for offline and may be for temp tablespace.
Regards
Anurag

Similar Messages

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.

Whole database online + redo log backup

Hello all,
we are running SAP on a Oracle Database and doing a daily backup.
In the DBA Planing Calendar, we do have the action
Whole database online + redo log backup
What exactly does that mean?
Thanks,
Anne

This backup will save the CONTENT of the database only, not the database software itself.
To get a full consistent backup you need to backup more things if you want to have everything - depending on the operating system:
On Unix you will need to backup the software directory (/oracle*, oraInventory, oratab (depending on the location)) etc.
On Windows you will need to backup <letter>:\oracle, the registry keys and more things.
However, in case of a recovery you can also install the software after an OS installation and then restore it from tape.
Markus

What is the difference between undo tablespace and online redo log files.

what is the difference between undo tablespace and online redo log files. I am confused
as per my knowledge undo tablespace is used to store the undo information when a table is being updated so that, just incase we need to rollback a transaction we know what was present in the table earlier.
when a transaction fails the SMON performs the rollback of the data.
This undo data is stored in the undo tablespace and read consistency if any is enforced.
is my understanding till here correct?
Now, can this undo data/before image not be stored in the redo log buffer and online redolog files?
can redo-log files not store this information?
in fact, is it that when undo tablespaces exist in a database, the undo data/before image is stored in both the undo tablespace and also the redo log files?
kindly clarify my doubt.
thank you.

This question has been asked many times before. The answer is always the same.
Yes, redo contains the before image of data (and the after-image). Therefore, it **COULD** be used to roll back a transaction.
BUT... Redo is written sequentially. Using it to rollback your transaction would involve reading through all the redo written by maybe thousands of other people. It would be painfully slow.
Your transaction is, however, directly linked to just the UNDO that it generates (which is JUST the before image of the data). So, your undo is your undo and doesn't share space with anyone else's undo. Therefore, using it to roll back YOUR transaction is fast.
The fact that undo is only the before image of the data also makes it faster than wading through a sea of before and AFTER images as you'd find in redo. About twice as fast, in fact, since there's half the data. Roughly.
Redo also gets written and flushed to disk whenever there's a commit, 3 seconds are up or too much (1MB, actually) redo gets generated between flushes caused by other factors. Your redo gets flushed when those things happen, even if you haven't actually committed your transaction. And redo logs recycle themselves, meaning that your redo -even if your transaction hasn't been committed yet- can be over-written by later transactions. Try rolling back when that's happened, if redo was the source of your rollback data!
Undo, however, cannot be over-written if the transaction has not been committed. Ever. If you don't commit for three years, there will be three years' undo stored in your database (assuming you had the space, of course!).
I could go on, but that will do. Redo is there fore RECOVERY, after catastrophe. Undo is there for read-consistency (and the occasional change of mind). Two different functions. Two different mechanisms. Each one highly tuned to doing what it does, why it does it, most efficiently and effectively.

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

Clearing Online redo logs on the target physical standby

Hi,
Version 11202.
Primary on machine A
Standby on machine B
Following note: 11.2 Data Guard Physical Standby Switchover Best Practices using SQL*Plus [ID 1304939.1].
Online redo logs on the target physical standby need to be cleared before that standby database can become a primary database. And later :
On the target physical standby run the following query to determine if the online redo logs have not been cleared... 1) I did not understand where i should run the query. On machine A or on machine B ?
2)
Online redo logs on the target physical standby need to be CLEARED
What does it mean that it need to be CLEARED ? Does transaction might be lost by running the clearing command?
Thanks

I have used my note many times in production.
For example they needed to do some power work on the main server room a few months back on the weekend.
We did switchovers until the work was complete and then a switch back.
I wrote a short document called "Switchover post-mortem lessons" the main point from that was :
1.
getting ORA-01017 issues in Oracle forms ( Application ) after the switchover to standby.
The issue was caused by the Standby database having a different parameter for passwords than the Primary database.
This did not show up in testing because all the tester we used had converted passwords from Oracle 10.
Solution
When in doubt issue this on the new Primary :
SQL>ALTER SYSTEM SET SEC_CASE_SENSITIVE_LOGON = FALSE;
Note: This command can be issued repeatedly with no negative effect on the system.2.
The query to check switch_over status was returning "LOG SWITCH GAP"
select switchover_status from v$database;
This is an issue because Oracle says the return values should be one of these :
NOT ALLOWED
SESSIONS ACTIVE
SWITCHOVER PENDING
SWITCHOVER LATENT
TO PRIMARY
TO STANDBY
RECOVERY NEEDED
LOG SWITCH GAP is not one of the expected value. In addition this phase is not search friendly either on the Oracle support site or your favorite search engine.
Given this I ran this query :
SELECT
NAME AS STANDBY,
SEQUENCE#,
APPLIED,
COMPLETION_TIME
FROM
V$ARCHIVED_LOG;
Solution
SQL>ALTER SYSTEM SWITCH LOGFILE;
And wait a few minutesMy switchover document had no issue.
Best Regards
mseberg

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

Archive all the active online redo logs

Hi,
in 9.2.0 and in archivelog mode, how can I archive all the active online redo logs ?
Thank you.

Is ur database already running in archivelog mode?? If yes and if automatic archiving is enabled then ur redo will be archived automatically. I think first you need to check whether ur DB is in archive log mode or not?? Post the output of (from sqlplus):
archive log list
Daljit Singh

When occurs crash recovery,why use active online redo log not archived log?

If current redo log had archived, but it's still 'ACTIVE'. As we all know, archived log is just an archived copy of the current redo log which is still 'ACTIVE', they have the same data. But why use active online redo log not archived log for crash recovery?(I think, if crash recovery can use archived log, then whether the online redo log is 'ACTIVE' or not, it can be overwritten)
Quote:
Re: v$log : How redo log file can have a status ACTIVE and be already archived?
Hemant K Chitale
If your instance crashes, Oracle attempts Instance Recovery -- reading from the Online Redo Logs. It doesn't need ArchiveLogs for Instance Recovery.
TanelPoder
Whether the log is already archived or not doesn't matter here, when the instance crashes, Oracle needs some blocks from that redolog. Archivelog is just an archived copy of the redolog, so you could use either the online or achive log for the recovery, it's the same data in there (Oracle reads the log/archivelog file header when it tries to use it for recovery and validates whether it contains the changes (RBA range) in it what it needs).

Aman.... wrote:
John,
Are you sure that the instance recovery (not the media recovery) would be using the archived redo logs? Since the only thing that would be lost is the isntance, there wouldn't be any archived redo log generated from the Current redo log and the previous archived redo logs, would be already checkpointed to the data file, IMHO archived redo logs won't participate in the instance recovery process. Yep, shall watch the video but tomorrow .
Regards
Aman....
That's what I said. Or meant to say. If Oracle used archivelogs for instance recovery, it would not be possible to recover in noarchive log mode. So recovery relies exclusively on the online log.
Sorry I wasted your time, I'll try to be less ambiguous in future

To where does the LGWR write information in redo log buffer ?

Suppose my online redo logfiles are based on filesystems .I want to know to where the LGWR writes information in redo log buffer ? Just write to filesystem buffer or directly write to disk ? And the same case is associated with the DBWR and the datafiles are based on filesystems too ?

It depends on the filesytem. Normally there is also a filesystem buffer too, which is where LGWR would write.Yes but a redo log write must always be a physical write.
From http://asktom.oracle.com/pls/ask/f?p=4950:8:15501909858937747903::NO::F4950_P8_DISPLAYID,F4950_P8_CRITERIA:618260965466
Tom, I was thinking of a scenario that sometimes scares me...
**From a database perspective** -- theoretically -- when data is commited it
inevitably goes to the redo log files on disk.
However, there are other layers between the database and the hardware. I mean,
the commited data doesn't go "directly" to disk, because you have "intermediate"
structures like i/o buffers, filesystem buffers, etc.
1) What if you have commited and the redo data has not yet "made it" to the redo
log. In the middle of the way -- while this data is still in the OS cache -- the
OS crashes. So, I think, Oracle is believing the commited data got to the redo
logs -- but is hasn't in fact **from an OS perspective**. It just "disapeared"
while in the OS cache. So redo would be unsusable. Is it a possible scenario ?
the data does go to disk. We (on all os's) use forced IO to ensure this. We
open files for example with O_SYNC -- the os does not return "completed io"
until the data is on disk.
It may not bypass the intermediate caches and such -- but -- it will get written
to disk when we ask it to.
1) that'll not happen. from an os perspective, it did get to disk
Message was edited by:
Pierre Forstmann

I have 2 iphones, one for personal and one for business. I need my phones not to sync otherwise they will both ring all the time. How can I log out of my icloud and unsync my phones?

I have 2 iphones, one for personal and one for business. I need my phones not to sync otherwise they will both ring all the time. How can I log out of my icloud and unsync my phones?

Syncing your phones to the same iCloud account won't cause them to both ring all the time, it only puts the same contacts, calendars, and other synced data on the phone. The phones will only ring with someone calls the number associated with the phone.
If you want to stop using iCloud on one or both of the phones, go to Settings>iCloud, tap Delete Account, then choose Keep On My iPhone when prompted. This will disconnect them from iCloud and keep a copy of the synced data on the phone.

Cold backup with online redo logs

I am working on 10G in AIX for a single instance
It is just a general db backup & restore question, but I have something confused.
I am going to perform a cold backup with my ARCHIVELOG database.
No wonder why I perform a cold backup because it is a testing database which can suffer from data lost and down time during backup.
I read some guides. They all mentioned to backup all the datafiles and control files.
During the restoration, I have to copy all the backed up datafiles and control files to the default location.
Then Startup mount;
The last step before open the database is recover database until cancel;
For the acknowledgement, I have to do the command of recover database, because the online redo logs were not backed up, thus we have to recover it in order to reset the redo logs.
For my question,Would I be able to skip the command of recover database, then directly startup the database if I have backed up the online redo logs and copy the default location during the restoration?
However, I read many documents which mention that it is not suggested to backup the online redo logs. Is it just the case which ONLY applied in hot backup? Do you all think that for my case, cold backup for online redo logs is recommended?
Thanks all

jgarry wrote:
Edit: And never forget, those test databases are some developers production.Absolutely true according to my experience. Loosing the work of a payed developer is just as bad as loosing the work of a production system and may even be worse because it may not be possible to re-enter missing data into the system.
I think a cold backup is only suitable on special occasions, for instance, to relocate/copy the database to a different storage media, or if the database doesn't change or if loosing changes is absolutely irrelevant. Otherwise, put the database into archivelog mode and do a hot backup. After that you will also have alternative options which can make the restore and recovery of the database very easy and efficient, like flashback database, etc. but it will take substantial additional disk space.

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

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.

Why the time of the online redo logs doesn't change?

Similar Messages

Maybe you are looking for