RelationalDBDesign
SiteMap
Advanced Tuning
SQL Tuning
Perform Tuning
Tuning Instance
Tuning Basics
External Environment
Tuning Instance
«Prev
Next»
Tuning Oracle Instance
Instance Tuning
Main Components SGA
Shared Pool Tuning
Oracle Library Cache
Query Dictionary Cache
Global Area Session
Data Buffer Cache
Redo Log Buffer
Instance Tuning Conclusion
Shared Pool Tuning
Shared Pool Optimal Tuning
Pin Packages Shared Pool
Pinning Supplied Packages
Reserved Size
Identifying High Use Packages
Pinned Packages Output
IIdentify Swapped out Items
Statistics gathered from Startup
Detecting Library Cache Contention
Library Cache Statistics
Reuse SQL Library Cache
Tuning Shared Pool
Data Buffer Cache
Tuning Data Buffer
Calculate buffer Hit Ratio
Non- Full table Scan
Full table Scan
Impact Adding Data Buffers
Predict Amount Spare Memory
Create multiple Buffer Pools
Configure Multiple Buffer Pools
Size Buffer Pools
Monitor Buffer Cache
Use Table Caching
Databuffer Cache Conclusion
Redo Log Tuning
Oracle Redo Logs
Tuning Techniques
View RedoLog Activity
Redo Log Parameters
RedoLog Wait Statistics
RedoLogs Online Size Determination
size Archived RedoLog FileSystem
Tune redo Log Operations
log_checkpoint_interval
RedoLog Tuning Conclusion
Sorting Operations
Oracle Sorting Basics
Sorting Parameters
SQL Join Operations
Monitor for Disk Sorts
Sorting Direct Writes
Temporary Sorting Space
Monitoring Temp Tablespace
Remove SQL Sorts
Sorting Operations Conclusion
Tuning Oracle Locks
Sizing Redo Log Files in Oracle - Exercise
Size the online redo log files in Oracle:
Objective:
Size the redo log files.
Exercise scoring
This exercise is worth a total of 12 points - three points for each correct answer you submit. To receive full credit, you will need to respond to the scenario below, answering the questions. Once you have completed your answer, you will submit your answers.
Background and Overview
You have been asked to estimate the redo log sizes for a new database. This includes log_buffer, log_simultaneous_copies, online redo logs, and the archived redo log filesyatem. The vendor reports that this database application package will generate 1,000,000 changes per day, and the average size of a database change is 80 bytes. You are running on an SMP server with eight CPUs and you have a huge amount of RAM memory on the server. They cannot give you any more specific information about the volume of update activity. The end users say that they will be taking full, cold backups each night. You would like to keep enough space in your archived redo log file system to be able to roll-forward all changes between backups.
Instructions
You task is to allocate appropriate sizes for:
1.
log_buffer
2.
The online redo log files
3.
log_simultaneous_copies
4.
The archived redo log filesystem
Hints
For the archived redo log filesystem, think about how far you will need to roll-forward between backups.
Submitting your exercise
Once you have entered your responses into the text boxes, click the
Submit
button to submit the exercise. Remember that you must submit all your responses to this exercise at once.