Comments on: How Do I Verify that the Redo File is Being Used? http://oraqa.com/2008/08/03/redo-log/ Oracle Question and Answer Tue, 06 Jan 2009 18:56:06 +0000 http://wordpress.org/?v=2.7 hourly 1 By: gamyers http://oraqa.com/2008/08/03/redo-log/comment-page-1/#comment-245 gamyers Mon, 04 Aug 2008 23:01:37 +0000 http://oraqa.com/?p=263#comment-245 "redo log file gets full" That is the nature of a redo log file. It gets full, switched and (hopefully) archived. If you mean that running the procedure through SQL*Plus generates less redo than running the same procedure through an application server, then there's probably a difference in the session settings between the two. "So I changed the logging property of the table to no so that it doesn’t write anything in redo log" No you didn't. Updates and deletes ALWAYS get redo generated. Multi-row Inserts (ie not using the VALUES clause of the INSERT statement) with the APPEND hint may reduce the redo generated for the statement. Forget about the redo. Work out what the procedure is doing in the app server mode that it doesn't do in the SQL*Plus mode. “redo log file gets full”
That is the nature of a redo log file. It gets full, switched and (hopefully) archived.
If you mean that running the procedure through SQL*Plus generates less redo than running the same procedure through an application server, then there’s probably a difference in the session settings between the two.
“So I changed the logging property of the table to no so that it doesn’t write anything in redo log”
No you didn’t. Updates and deletes ALWAYS get redo generated. Multi-row Inserts (ie not using the VALUES clause of the INSERT statement) with the APPEND hint may reduce the redo generated for the statement.

Forget about the redo. Work out what the procedure is doing in the app server mode that it doesn’t do in the SQL*Plus mode.

]]>