How would you correct such a situation?

If a log file becomes corrupted, it may cause the database to stale. How would you correct
such a situation?

If a log file becomes corrupted, it may cause the database to stale. How would you correct
such a situation?

A.
Recover the online redo log from backup.

B.
Delete and re-create the log file.

C.
Use the ALTER DATABASE CLEAR LOGFILE command to clear the log file.

D.
Shut down the database and restart it.

E.
Shut down the database and then mount it. Clear the log file with the ALTER DATABASE
CLEAR LOGFILE command and then restart the database with ALTER DATABASE OPEN
RESETLOGS.

Explanation:
If you don’t use the ALTER DATABASE CLEAR LOGFILE command to clear log online, after
the database restarted, the log file will be INVALID.
So the simple way is to clear the log file directly.



Leave a Reply 3

Your email address will not be published. Required fields are marked *


Eamon

Eamon

Ambigous question as it says that a “redo log file” was corrupted. This requires a different recovery technique than that of a “redo log file group”.

k

k

If you have the recommended setup for mirrored members in a group and only 1 file is corrupted then C is correct and you dont need to recover.