Hi Darrell, You mean to say that once the rm command is issued. Try checking the free space availability as the file might be virtually removed and cannot be seen. Once we reboot the instance or shutdown the server and try checking the free space availability so that it confirms the files are not removed completely from the system. Please let me know if i am wrong. But coming to the recovery part, can the files which are rmed be roll back with any possibility if the files are not removed completely and oracle still accepts the commit command having redo log files deleted?. Please let us know for this issue. Its a good topic though!! On 5/17/07, mailbox@xxxxxxxxxxx <darrell@xxxxxxxxxxx> wrote:
I'm suspecting that the current redo log was open and active until the shutdown took place. The rm command simply "flagged" it for removal to the OS. It might be interesting to try your scenario again, but add in steps to check the volume of space available / used on that file system before the rm, after the rm and then again after the shutdown. If this theory holds you won't see the space available from the removed redo log until after the shutdown.