Has anyone run into bug 8236843 with the dbms_profiler where one of the units shows a very high elapsed time? My report (and the data in the profiler tables) show 9.22337203685478E18 when it should only be about 120. I found the bug on MOS which says it has been fixed but doesn't day the version or if there is a patch. I'm on 10.2.0.4 on linux. Is there a work around? Thanks, Ken