I mentioned the new log writer slave processes a few days ago, I think these parameters tell Oracle when to start or stop dispatching writes to the slaves based on work rates and some measure of how close to each other in the log files the writes are.

I was wondering if you have come across my issue as well: I can not re-create the same schema/application on a stand alone, non-container/pluggable 12c at all. Also any attempt to drop either the original (healthy) schema or the “clone” (incomplete – because the process fails during creation) fails too.

They both generate the same error :”ORA-04043: object SYS_PLSQL_1FDD532D_2935_1 does not exist.”

The schema does contain packages relying on “versioned” types for pipelined functions, so it feels like it should be a case of “issue 3” mentioned here (http://www.oracle-developer.net/display.php?id=423) but I’ve got no synonyms. Also no references of the missing type, or its other “versions” can be traced in dba_dependencies …

I wonder if Oracle has introduced a limitation, in favour of picking up (or actually forcing developers to use) pluggable DBs, and create one pluggable DB per application (previously “schema”).

What do you think?

Regards,

p.s. By the way, I have not been able to import any schemas (whether created originally in 12c, or exported from an 11g schema) into 12c …

I haven’t looked at anything like your scenario – but my default position is: “things break when you mix features” (pluggable and versioning might, by themselves, be sufficient to find holes – but I haven’t got that far yet, I’m still breaking simple things ;).

If you haven’t tried it already, I would try to write a script creating the smallest possible schema where the problem appeared, and ship it to Oracle.

U would be a little surprised if Oracle had tried to force developers to use a pluggable DB per application – especially since it’s a licensed option – but all things are possible (sometimes by accident).