RE: Data extraction over dblink

Hmm..I didn't realize it could be done at the tablespace level, but, Paul is absolutely correct.  

Here's a reference to the Oracle documentation where it's discussed:  

http://download-east.oracle.com/docs/cd/B19306_01/server.102/b14231/crea te.htm#sthref326    

-Mark
 

--

Mark J. Bobak
Senior Oracle Architect
ProQuest Information & Learning

For a successful technology, reality must take precedence over public relations, for Nature cannot be fooled. --Richard P. Feynman, 1918-1988  

From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Paul Drake Sent: Thursday, April 13, 2006 5:09 PM
To: dubey.sandeep_at_gmail.com
Cc: oracle-l_at_freelists.org
Subject: Re: Data extraction over dblink

On 4/13/06, Sandeep Dubey <dubey.sandeep_at_gmail.com> wrote:

        David,         

        Transportable tablespace is on my second test list. I need to pull

        data from 6 tables and insert into 3 tables. So I will need staging

        tables on both source and target databases. My concern is the unneeded

        logging that will occur on both the source and target database while

        inserting data in the staging tables. We are using dataguard with

        forced logging, so we can not use nologging feature while inserting in

        the staging tables.         

        Thanks         

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

Sandeep,

IIRC, the forced logging attribute can be set at both the database level and at the tablespace level.
You could in theory set force logging = false at the database level and set it to be true at the tablespace level. Test in your environment, your mileage may vary, etc.

Paul

--

http://www.freelists.org/webpage/oracle-l Received on Thu Apr 13 2006 - 16:55:17 CDT