> Until Oracle can make up their (collective) mind, there will be times that must be divided by 100 > and there will be times that must be divided by 1000000 and of course there will be columns that > will just overflow. The reason why CPU time is still given in centiseconds, is that Oracle is unable to get CPU usage information in more detailed level than a timeslice controlled by hardware clock and kernel settings, normally 10ms. (This might change with the use of microstate accounting in the future, though). Btw, when you check the documented views v$system_event and v$session_event, those return wait times in centiseconds regardless of Oracle version (they just divide the wait times by 10000 starting from 9i), it's just the undocumented x$ views which may change between versions and patch levels.. Tanel. ---------------------------------------------------------------- Please see the official ORACLE-L FAQ: http://www.orafaq.com ---------------------------------------------------------------- To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx put 'unsubscribe' in the subject line. -- Archives are at //www.freelists.org/archives/oracle-l/ FAQ is at //www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------