If a query does a consistent get on a block that has been changed since that query began or that had uncommitted changes at the time that that query began, then it is necessary to rollback those changes for read consistency. The consistent changes statistics counts the number changes rolled back. However, most consistent gets do not require any such rollback, and so it is normal for the number of consistent gets to be much greater than the number of consistent changes. This is reflected in the no work - consistent read gets statistic.

In my database the value of consistent gets is 2478976 and consistent changes is only 90732. Now according to ORACLE consistent changes are made when a consistent get is requested. So in this case why so many gets requests?