Vivek
Some applications report unusually high rollback rates because "no-work
transactions" are ended with a rollback rather than a commit. So you would
see sequences of one or more selects (but no DML) followed by a rollback
rather than a commit. I seem to recall this being a feature of some JDBC
drivers?
You may be able to change driver settings to avoid this - or in fact it may
not be a problem at all.
Regards Nigel
