|
|
|
|
|
|
After completing this lesson, you should be able
to |
|
do the following: |
|
Determine if processes are waiting for space in
the redo log buffer |
|
Size the redo log buffer appropriately |
|
Reduce redo operations |
|
|
|
|
|
|
|
LOG_BUFFER parameter |
|
Default value: OS-specific, generally four times
the maximum block size |
|
|
|
|
|
|
|
V$SESSION_WAIT |
|
Log Buffer Space event |
|
|
|
|
The Redo Buffer Allocation Retries value should
be near 0; the number should be less than 1% of Redo Entries. |
|
|
|
|
|
|
|
Fewer redo operations require fewer redo entries
and thus less redo log buffer space. |
|
Some ways of reducing the redo entries are: |
|
Direct Path loading without archiving |
|
Direct Path loading with archiving using
NOLOGGING mode |
|
Direct Load INSERT in NOLOGGING mode |
|
Using NOLOGGING mode in SQL statements |
|
|
|
|
|
In this lesson, you should have learned how to: |
|
Tune log buffer space |
|
Redo buffer allocation retries |
|
Size the redo log buffer appropriately |
|
Reduce redo operations with the NOLOGGING
attribute |
|