Originally posted by bfunky
Believe it or not it's on a select statement. The only thing I can think of is that there are some changes being made to the rows while I am selecting them. These are bank accounts so I am wondering if that could be causing the problem, since they are updated as transactions are performed. But I am not sure of a way around them. Since we are online 24 x 7 I could be running into this problem constantly so there isn't a time when I can run this where there might not be a conflict. Any ideas how to get around this?
Do u have (Manuel) auditing (For SELECT statement) enabled. For more details read "Oracle One-on-One". But this is not an Oracle generaic behavior. Can be a site specific implementation of auditing on SELECT statements and the auditing table may hitting the error. Are you selecting from a 'View'..? Check for any "INSTEAD OF" triggers on the view. Also check the alert log, on which table is getting the error. The query table and the error hitting table must be different.

keep in mind that a SELECT statement cann't produce this error.

Tom Kyte explaind, how you can implement auditing on "SELECT"

Regards

Thomas