RE: Enable novalidate contains after import?

From: Norman Dunbar <oracle_at_dunbar-it.co.uk>
Date: Tue, 24 May 2016 20:51:34 +0100
Message-ID: <E964016D-EA1A-49D2-A4B4-7E717BBFDA23_at_dunbar-it.co.uk>



Thanks again Jonathan.

All the foreign key constraints are enable novalidate. I set them all before the exports, I reset them after the imports are done. Just doing that saved me 4 hours.

Actually, I set the primary and unique to novalidate as well, but they always import as enable validate. Which is a pain as they validated all the data on the source database anyway.

I have a norows export of all the affected schemas, it's 25 mb in size. Yesterday I ran a show=y on it and after a couple of hours, the index file was 100gb in size, and still not finished. Most of the 100gb was "REM " per line. Or as grep sees it "^REM $" with two spaces. Lots of effectively blank lines.

I get exactly The same with the 9i and 11g norows export file.

I think windows is out to get me on this contract! I'm looking at DDLWizard next I suspect if I need to go down the route of extracting the ddl.

Cheers,
Norm.
--

Sent from my Android device with K-9 Mail. Please excuse my brevity.

--

http://www.freelists.org/webpage/oracle-l Received on Tue May 24 2016 - 21:51:34 CEST

Original text of this message