I have a web application that runs on Oracle 10g in a primary/physical standby scenario. As a result, force_logging is turned on for the entire database.
The application uses a table for storing the users 'temporary' information such as last screen, open items, etc. This is not critical data so we don't care if it's lost in the event of database failure but this table is written to every time the user moves to a different area of the application generating a large amount of redo, as well as slowing the application down (I think) substantially.
Is there a way to create a temporary table/tablespace or something that won't generate redo (or even undo) for storing this data in that won't break the standby if I have to activate it? Also, it needs to not be affected by the force_logging parameter.
Ideas? I know this is something that many other Oracle users must have encountered, but I can't figure out a way to do it.