RE: GLOBAL TEMPORARY TABLE

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_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Nirmalya Das
Sent: October 22, 2006 9:40 PM
To: oracle-l_at_freelists.org
Subject: Fwd: GLOBAL TEMPORARY TABLE

Sorry, it is Oracle 10.1.0.4 on a RHEL 4 system

• Forwarded message from nirmalya_at_hln.com ----- Date: Sun, 22 Oct 2006 18:25:42 -0700 From: Nirmalya Das <nirmalya_at_hln.com> Reply-To: nirmalya_at_hln.com Subject: GLOBAL TEMPORARY TABLE To: oracle-l_at_freelists.org

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
--

http://www.freelists.org/webpage/oracle-l

• End forwarded message -----
  --
  http://www.freelists.org/webpage/oracle-l

--

http://www.freelists.org/webpage/oracle-l Received on Sun Oct 22 2006 - 20:56:01 CDT