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
Reserved Size
Identifying High Use Packages
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
Full table Scan
dbFile MultiBlock Read Count
Impact Adding Data Buffers
Predict Amount Spare Memory
Create multiple Buffer Pools
Configure Multiple 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
Intro Tuning Oracle Locks
Oracle Locking Scheme
Shared Exclusive Locks
Oracle Lock Modes
Database Deadlocks
Preventing Database Deadlocks
Dictionary Lock Views
Lock Utility Scripts
DBMS Lock Package
Tuning Oracle Locks Conclusion
Oracle Redo Log Sizing - Exercise
Size redo logs for Oracle 23ai
Objective:
Write a practical sizing plan for online redo logs and archived redo log capacity using modern Oracle best practices.
Current best practice context
In Oracle 23ai, redo log sizing is still relevant for DBA-managed databases (on-premises and co-managed cloud services). Installation tooling can provide defaults, but you still validate log switch frequency, ensure adequate redo log groups, and prevent archive destinations from filling. In Oracle Autonomous Database, redo log sizing is handled by the service.
Exercise scoring
This exercise is worth
12 points
(3 points per response area). There are no “solutions” on this page. Your goal is to describe a defensible approach and how you would verify it after go-live.
Scenario
You are planning a new OLTP database. The vendor estimates about
1,000,000 row changes per day
with an average change size of
~80 bytes
. You have limited workload detail beyond that. Your backup strategy is nightly full backups, and you want to support roll-forward recovery between backups.
Instructions
Provide your plan in the text boxes below. Focus on redo log sizing and operational verification.
1.
Online redo log sizing target
Include: target log switch cadence during peak hours, initial log size proposal, and what you would change if switches are too frequent.
2.
Redo log group design
Include: number of groups, multiplexing (members per group), placement guidance (ASM disk groups / separate failure domains), and why.
3.
Archived redo log capacity plan
Include: how much archive log capacity you want available, what retention window it supports, and how you would prevent a “destination full” outage (for example, FRA sizing plus backup-and-delete strategy).
4.
Verification queries and monitoring steps
Include: which views/logs you would check (for example V$LOG, V$LOGHIST, alert log, AWR) and what signals would indicate redo I/O contention.
Submitting your exercise
After completing all four response areas, click
Submit
. Your text will be posted to the exercise result page for review.