SYS@RAC>SELECT name, value FROM v$sysstat WHERE name ='redo buffer allocation re
tries';

NAME                                                                  VALUE
---------------------------------------------------------------- ----------
redo buffer allocation retries                                        26603

The value of redo buffer
allocation retries should be near zero over an interval. If this value increments
consistently, then processes have had to wait for space in the redo log buffer.
The wait can be caused by the log buffer being too small or by checkpointing.
Increase the size of the redo log buffer, if necessary, by changing the value of
the initialization parameter LOG_BUFFER. The value of this parameter is expressed
in bytes.

In 11.2, there is also Bug 13520743 - HIGH REDO LATCH CONTENTION ON 'REDO ALLOCATION', closed as not a bug:
The following parameter is used to reduce Redo Allocation contention: "_log_parallelism_max".
The bug instructs to set _log_parallelism_max values of 4,5,6 and measure the improvement based on AWR reports.

1  SELECT  substr(ln.name, 1, 20), gets, misses, immediate_gets, immediate_mis
ses
  2  FROM v$latch l, v$latchname ln
  3  WHERE   ln.name in ('redo allocation', 'redo copy')
  4*                 and ln.latch# = l.latch#
SYS@RAC>/

SUBSTR(LN.NAME,1,20)
--------------------------------------------------------------------------------

      GETS     MISSES IMMEDIATE_GETS IMMEDIATE_MISSES
---------- ---------- -------------- ----------------
redo copy
     27298          0       71398089            30925

redo allocation
  82578913      12330              0                0

Oracle Diagnostic Pack N N Y
=>only EE have this feature

DBA_HIST_SYSSTAT displays historical system statistics information. This view contains snapshots of V$SYSSTAT.