It's certainly possible for Oracle to be pushed into very heavy CPU usage, particularly for PX slaves, but even in serial queries.
Two common 'causes' are queries with correlated sub-queries against small tables; and queries which have been over-indexed and hinted to avoid table-scans. Bottom line, though, is that if the session does not appear to be in an Oracle-recorded wait state, it is either using (or scheduled to use) CPU, or you've hit a wait state that isn't instrumented properly. Jonathan Lewis http://www.jlcomp.demon.co.uk Host to The Co-Operative Oracle Users' FAQ http://www.jlcomp.demon.co.uk/faq/ind_faq.html Author of: Practical Oracle 8i: Building Efficient Databases -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Jonathan Lewis INET: [EMAIL PROTECTED] Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
