Re: datapump import schema and default values taken from a sequence

Yes, the sequence itself is created correctly with the new owner and set to the correct starting value. It's only the DEFAULT expression that isn't imported correctly.

We have thought about the PDB approach, but for now this is unfortunately not an option.

We have automated that process quite substantially and the "cloning" is often done through a DB link, so it would be hard to change the DEFAULT value before that. But it seems that is the only option we have for now :(

Thanks for the answer
Thomas

Mark W. Farnham schrieb am 27.07.2021 um 05:26:
> Seems like a Painful Incompleteness Awkwardness (PIA), also known shorter and more colorfully.
>
> Still, I wonder if you have a pause on DML whlist you are cloning the schema. IF you do, a woeful work-around might be to temporarily shut off the when NULL sequence directive on the table(s) in THOMAS, do the clone, turn them back on on THOMAS and create the when NULL sequence directive on ARTHUR.
>
> Presumably it is only the when NULL sequence directive that is Fouled Up Beyond All Recognition (FUBAR) and the sequence itself is getting correctly created with the current next number. Right?
>
> What a PIA!
>
> mwf
>
> PS: Another way would be to create a new pluggable database and carefully import THOMAS from the current location into the new pluggable. Some might say that is a better testbed, unless of course you are testing the rename schema completeness of clone schema!

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