Global temporary tables create a lot of log switches
On our database we had a log switch every 15-20 minutes.
Recently there was a new feature where on a heavily used screen, we added logic where a stored procedure is filling global temporary tables to calculate a status that the screen needs to show.
Since this was implemented the log switches are happening every 1 minute.
The main global temporary table is "on commit preserve rows" Inserting data and then truncates on next run.
Is it the global temporary tables that create the excessive entries in archive logs? These data will not be needed in case of recovery. Is there a way to see what statement creates most of the REDO information?