RE: rollback segments during export

Perhaps you missed the part where I said I could be misreading the docs. :)

Guess I was.

Jared

                                                                                       
                                 
                    Jacques Kilchoer                                                   
                                 
                    <Jacques.Kilchoer@       To:     Multiple recipients of list 
ORACLE-L <ORACLE-L_at_fatcity.com>        
                    quest.com>               cc:                                       
                                 
                    Sent by:                 Subject:     RE: rollback segments during 
export                           
                    root_at_fatcity.com                                                   
                                 
                                                                                       
                                 
                                                                                       
                                 
                    10/01/01 10:35 AM                                                  
                                 
                    Please respond to                                                  
                                 
                    ORACLE-L                                                           
                                 
                                                                                       
                                 
                                                                                       
                                 

> -----Original Message-----
> From: Jared Still [mailto:jkstill_at_cybcon.com]
>
> > Just because there is a PK/FK between tables, it does not
> mean they will be
> > exported in the same transaction. And thus, possibly out of sync.
>
> I didn't say there was. My implication was that your
> tables would get out of sync. Setting 'consistent=y'
> won't prevent that:
>
> : If you specify CONSISTENT=N (the default), each table is
> usually exported
> : in a single transaction. However, if a table contains
> nested tables, th
>
> Now it *could* be that I'm misreading the docs. It' been known
> to happen, but that sentence says to me that each table is
> exported as part of a single transaction.

I am totally confused. Mr. Still, it seems to me that you are quoting a section of document that describes the behaviour of <<consistent = "N">> and claiming that the description applies to <<consistent = "Y">>? I was told by an Oracle employee that <<consistent = "Y">> would guarantee that all data would be "consistent" from the time of the start of the export, and I have successfully used that option to carry data from one database to another without constraint errors.

The 8.1.7 Utilities manual says
<<CONSISTENT
...
Specifies whether or not Export uses the SET TRANSACTION READ ONLY statement to ensure that the data seen by Export is consistent to a single point in time and does not change during the execution of the export command. You should specify CONSISTENT=Y when you anticipate that other applications will be updating the target data after an export has started.>>

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: 
  INET: Jared.Still_at_radisys.com

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).