Re: Temporary table use and the redo log

From: Robert Klemme <shortcutter_at_googlemail.com>
Date: Mon, 07 Sep 2009 18:35:36 +0200
Message-ID: <7gkr2vF2pfleoU1_at_mid.individual.net>



On 07.09.2009 18:23, codefragment_at_googlemail.com wrote:
> Hi
> I'm using a global (session) temporary table to break up a section
> of a stored procedure that is needed in
> a number of places. Always for use in a select.
> If the database crashes, gets rolled back, anything, I don't care
> about the contents of that
> table. Especially -I don't want redo logs for it-. Is there any way I
> can accomplish this?
>
> From what I can see so far I should look into:
> - unrecoverable
> - insert /*+APPEND */ into temp_table select...
> - possibly using a table variable

I suggest to also look into ON COMMIT DELETE ROWS.

> Nologging is on by default for a tempory table but you still get some
> logging
>
> Am I on the right track?

http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:15826034070548#50549336675394 http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:15826034070548#53994537734234

Cheers

        robert

-- 
remember.guy do |as, often| as.you_can - without end
http://blog.rubybestpractices.com/
Received on Mon Sep 07 2009 - 11:35:36 CDT

Original text of this message