My database was abruptly shut down (I don't know why). While we were opening the database it was showing the error in log files, so we tried to add a new redo log file for the existing group. It was added, and we are not able to switch the database because we are at mount stage, and even when we use the command to clear the logfile with "alter database clear unarchived logfile group 4," it is not clearing the group and the database is not switching. At mount stage, the database is in hang position. The database will open if we drop that redolog file offline, but we will lose some data. To overcome from these types of errors, what precautions should we take at this moment?
The first thing to do in the future is to make sure that the online redo logs are multiplexed. If one redo log file becomes corrupt, Oracle can use the other one. The multiplexed online redo log files should be on separate disk devices.
If you are still unable to open your database, you can try to open the database with the RESETLOGS option. This...
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
will clear out all online redo log files. You may experience loss of some transactions, so this should be a last option. But this may also be your only option, too.
Dig Deeper on Oracle database administration
Oracle expert Brian Peasland answers one reader's question about common pitfalls when connecting Oracle to outside programs.continue reading
One reader asks expert Brian Peasland a question about datafile sizes with the Oracle RMAN duplicate 10g command.continue reading
Managing parent table-child table relations in Oracle SQL environments is key to efficient programming.continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.