Re: Avoiding generating redo logs

As I understand the thread until now, you are worried about logging - why?
Also, you want to retain data over web sessions. Beats me as to why, but it's *your* requirement. So, you need a table. And you need some identifier over the web sessions in order to distinguish one returning user from the other.

Again: what's wrong with logging?
Why not create a table with the nologging option? Be advised, it will not be recoverable in case of mishap.

It seems to me, you worry about potential overhead, where you should actually be worried about the efficiency of your code.
Did you put up a test, with your code accessing a session table, created with nologging vs. one created with logging?

Do (because you did not!), and come back with the differences, if you are able to measure these consistently. I bet the differences are not noticeable (though measurable)

-- 
Regards,
Frank van Bortel

Top-posting is one way to shut me up...