From Jacques.Kilchoer@quest.com Mon, 01 Oct 2001 09:46:17 -0700 From: Jacques Kilchoer Date: Mon, 01 Oct 2001 09:46:17 -0700 Subject: RE: rollback segments during export In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: text/plain Title: RE: rollback segments during export > -----Original Message----- > From: Jared Still [mailto:jkstill@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 <> and claiming that the description applies to <>? I was told by an Oracle employee that <> 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 <>