RE: GLOBAL TEMPORARY TABLE
- From: "Mindaugas Navickas" <mnavickas@xxxxxxxxx>
- To: <nirmalya@xxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Sun, 22 Oct 2006 21:56:01 -0400
http://download-east.oracle.com/docs/cd/B19306_01/server.102/b14220/schema.h
tm#i16096
"DML statements on temporary tables do not generate redo logs for the data
changes. However, undo logs for the data and redo logs for the undo logs are
generated."
I hope, this explains you temporary table relationship to redo logs. I do
not know if there is any way of avoiding redo generated on undo.
Regards
Mindaugas
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Nirmalya Das
Sent: October 22, 2006 9:40 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: Fwd: GLOBAL TEMPORARY TABLE
Sorry, it is Oracle 10.1.0.4 on a RHEL 4 system
----- Forwarded message from nirmalya@xxxxxxx -----
Date: Sun, 22 Oct 2006 18:25:42 -0700
From: Nirmalya Das <nirmalya@xxxxxxx>
Reply-To: nirmalya@xxxxxxx
Subject: GLOBAL TEMPORARY TABLE
To: oracle-l@xxxxxxxxxxxxx
Hi Folks,
I have several tables like the following in our database.
CREATE GLOBAL TEMPORARY TABLE ENTITYCACHE
(
ENTITYNO VARCHAR2(20 BYTE)
)
ON COMMIT DELETE ROWS
NOCACHE;
The question I have is, on COMMIT the data is moved to the "online redo
logs" and then gets deleted. I don't really care about the data and could
not use "NOLOGGING" as well to negate the operation of moving the data to
the "online redo logs".
Any suggestions how to use these Temporary Tables but not burden the system
of writing it to the "online redo logs".
Thanks,
Nirmalya
--
//www.freelists.org/webpage/oracle-l
----- End forwarded message -----
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
