Follow Following. Smart way of Technology Join other followers. Sign me up. Already have a WordPress. Log in now. Post was not sent - check your email addresses! Sorry, your blog cannot share posts by email. As you can see I have 3 Redo Log Groups, each of them having their own logfile. Instead of dropping a logfile, I am going to drop the whole logfile group as I am having only one logfile present in each of them and recreate a new one.
For that I'll use the command,. If you have multiple log files present in your Redo Log Group and one of them is corrupted, you don't need to drop the whole log group.
You can drop a log file alone and recreate it. To drop a logfile, give command For example, I am using mine. Also learn - How to Multiplex Redo Log Files in Oracle to know how to add more redo log files in the redo log groups to keep the logs secure. To make this process faster, issue command. Note:- Don't forget to delete the log file manually after giving the drop command otherwise whenever you'll try to create the same log file again, it will through error saying that the file already exists.
After you have physically removed the logfile from the disk, you can easily create a new log group or a log file for your Oracle Database. After dropping a redo log group, make sure that the drop completed successfully, and then use the appropriate operating system command to delete the dropped redo log files.
When using Oracle Managed Files, the cleanup of operating systems files is done automatically for you. Consider the following restrictions and precautions before dropping individual redo log members:. It is permissible to drop redo log files so that a multiplexed redo log becomes temporarily asymmetric. For example, if you use duplexed groups of redo log files, you can drop one member of one group, even though all other groups have two members each.
However, you should rectify this situation immediately so that all groups have at least two members, and thereby eliminate the single point of failure possible for the redo log.
An instance always requires at least two valid groups of redo log files, regardless of the number of members in the groups. If the member you want to drop is the last valid member of the group, you cannot drop the member until the other members become valid. A stale log file becomes valid again the next time its group is made the active group.
You can drop a redo log member only if it is not part of an active or current group. If you want to drop a member of an active group, first force a log switch to occur. Make sure the group to which a redo log member belongs is archived if archiving is enabled before dropping the member. When a redo log member is dropped from the database, the operating system file is not deleted from disk.
0コメント