Q
Problem solve Get help with specific problems with your technologies, process and projects.

Switching database to archive log mode

I have a database that is not in archive log mode that is going to be changed to archive log mode. I'm trying to plan how often I'll have to back up the archived log files and how much space I will need to hold them. How can I tell how many log switches would have happened since the database has been restarted?

I have a database that is not in archive log mode that is going to be changed to archive log mode. I'm trying to plan how often I'll have to back up the archived log files and how much space I will need to hold them. How can I tell how many log switches would have happened since the database has been restarted? Thanks in advance.
Without having implemented archive logging already, the best place for planning how many archived redo logs will be generated is to look at your Alert Log. Count the number of times you see a log switch in your Alert Log for one day. Since an archived redo log is created for each log switch, you can have a pretty good estimate of how many archived redo logs you'll create in one day. Multiple this value by the number of bytes your online redo logs are occupying. You can query V$LOG to see how big your online redo logs are. This information can be used to see how many bytes a day's worth of archived redo logs will require.

Dig Deeper on Oracle database backup and recovery

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.

-ADS BY GOOGLE

SearchDataManagement

SearchBusinessAnalytics

SearchSAP

SearchSQLServer

TheServerSide.com

SearchDataCenter

SearchContentManagement

SearchHRSoftware

Close