Another thought -
From 10g Oracle started doing some very strange restarts while doing a big
update by tablescan.
I haven't got any tests to suggest that this could also happen if you did a
large tablescan query that produced lots of delayed block cleanout - which
might be happening after a massive import. Perhaps your 10 tablescans are
actually the same tablescan restarting.
Regards
Jonathan Lewis
http://jonathanlewis.wordpress.com
@jloracle
________________________________
From: Norman Dunbar [oracle@xxxxxxxxxxxxxxx]
Sent: 24 May 2016 08:18
To: Jonathan Lewis; oracle-l-freelists
Subject: RE: Enable novalidate contains after import?
Morning Jonathan,
The not null constraints are all part of the column definition rather than
added check constraints.
There are definitely only 8 of them, including the pk column. There are a
couple of unique indexes which have been created by the data import, but no
unique constraints.
Interesting.
Cheers,
Norm.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
