CPU patch & 10.2.0.3 patchset

  CPU patch is security-related, applying it needs downtime.
  here's an vulnerability fiexed in CPU Jul2007:
 
  a bug related with FRA fixed in 10.2.0.3 patch.
 
  the symptom is: v$recovery_file_dest.space_reclaimable(0) is not consistent with V$FLASH_RECOVERY_AREA_USAGE.percent_space_reclaimable
  so, although there's enough space in FRA, we still got alarmed that the FRA is over 85%
  SQL> select name,
  2  round(space_limit/(1024*1024),1) as limitMB,
round(space_used/(1024*1024),1) as UsedMB,
round(space_used/space_limit*100,2) as space_perc,
round(space_reclaimable/(1024*1024),1) as ReclaimMB,
round(space_reclaimable/space_limit*100,2) as space_reclaim_perc,
number_of_files as files
from V$RECOVERY_FILE_DEST
where space_limit > 0;  7    8    9 

NAME                         LIMITMB     USEDMB SPACE_PERC  RECLAIMMB SPACE_RECLAIM_PERC      FILES
------------------------- ---------- ---------- ---------- ---------- ------------------ ----------
/oradata/flashback             43008    42994.1      99.97          0                  0        430

SQL> SELECT * FROM V$FLASH_RECOVERY_AREA_USAGE;

FILE_TYPE    PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES
------------ ------------------ ------------------------- ---------------
CONTROLFILE                   0                         0               0
ONLINELOG                     0                         0               0
ARCHIVELOG                    0                         0               0
BACKUPPIECE                   0                         0               0
IMAGECOPY                     0                         0               0
FLASHBACKLOG              99.97                     99.45             430

refer to metalink 392430.1, we hit Bug 5106952 here:
Workaround :
1. shutdown immediate
2. startup mount
3. alter session set events 'immediate trace name KRA_OPTIONS level 1';
4. select from V$FLASH_RECOVERY_AREA_USAGE shows 0 files for flashbacklog.
Fix :
Apply one-off patch for BUG:5106952 / Apply 10.2.0.3 patchset once available
OR
Issue fixed in Oracle 11.