They go hand-in-hand with the other types of consistent gets. When Oracle does a consistent get on a block, it may need to rollback changes, or not, and it may need to clean out the block, or not. The following statistics are available in the statistics viewa: no work - consistent read gets cleanouts only - consistent read gets rollbacks only - consistent read gets cleanouts and rollbacks - consistent read gets So, it's just Oracle accounting for the different types of consistent read gets, and how many of each type it did. -Mark -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]On Behalf Of ryan.gaffuri@xxxxxxx Sent: Tuesday, May 18, 2004 9:06 AM To: oracle-l@xxxxxxxxxxxxx Subject: what are 'no work - consistent read gets' Didn't see any reference on metalink?=20 ---------------------------------------------------------------- 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 ----------------------------------------------------------------- ---------------------------------------------------------------- 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 -----------------------------------------------------------------