How Do I Verify that the Redo File is Being Used?
August 3rd, 2008 By tushar.chitnis
I have a table on which when I run a procedure for computation through sql*plus it runs fine. But the same when I run it from my application server the redo log file gets full. I don’t understand the reason behind this. So I changed the logging property of the table to no so that it doesn’t write anything in redo log. How do i verify that the redo file is being used by the table or not apart from the processing result?
August 4th, 2008 at 4:01 pm
“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.