** v$log.status

[A Joshi]

Hi,

  In view v$log there is a column status. This changes from current (if the redo log is in use) to atcive then to inactive. Documentation says  :

 

ACTIVE: The log is active but is not the current log. It is needed for crash recovery. It may be in use for block recovery. It might or might not be archived.

INACTIVE: The log is no longer needed for instance recovery. It may be in use for media recovery. It might or might not be archived.

So if it is in 'ACTIVE' status :  it means it is needed for crash/instance recovery?  So what does it mean? That changes in this log are still not written to data files? What else? Is this related to delayed block cleanout etc or no connection?

What factor affects  how long it will be in ACTIVE state before going to INACTIVE? What can be changed to control how long it takes. Any trade off?

Any detailed explanation on this will be greatly appreciated. You can mail me direct or to the list. Thank you. 

 

---

Do you Yahoo!?
Yahoo! SiteBuilder - Free web site building tool. Try it!