It appears to me that parent/child and root/leaf are interchangeable.
Though I could be wrong.
A root/parent can have one and only one leaf/child (directly). However,
that leaf/child can also be a root/parent if a leaf/child is created after
ORA$BASE -> edition_1 -> edition_2 -> edition_3
Once edition_1 is not needed (all editioned objects have been 'actualized'
in edition_3 as part of the patching process), it should be able to be
I can 'drop' the objects in the edition (object_type of NON-EXISTENT), but
the edition still cannot be dropped. (I need to rerun the POC script and
upload the output).
On Tue, Jul 9, 2019 at 3:45 PM Mark W. Farnham <mwf@xxxxxxxx> wrote:
hmm. so the first parent is ora$base. Tim Hall didn’t show dropping that,
only dropping the “leaf.”
*From:* oracle-l-bounce@xxxxxxxxxxxxx [mailto:
oracle-l-bounce@xxxxxxxxxxxxx] *On Behalf Of *Daniel Fink
*Sent:* Tuesday, July 09, 2019 4:19 PM
*Subject:* EBR and ORA-38810
Working on a POC for using Edition Based Redefinition for patching a 12c
environment. The client plans on weekly, perhaps more frequent, patching
and wants to avoid downtime. EBR *appears* to be the answer.
One main issue is the cleanup of old editions. For a simple POC (using the
example at oracle-base as the source), I create an edition (v1), then
another (v2) for a view and procedure. Once I have 'migrated' to V2, I want
to be able to drop V1. However when I try to drop that edition, the command
results in "ORA-38810: Implementation restriction: cannot drop edition that
has a parent and a child".
I find online information that indicates you can drop an edition, however
none of them show an actual example of the creation and subsequent drop of
an edition. And in looking at the architecture of editioning published by
Oracle (an edition is always the child of the most recent edition, causing
the previous edition to be a parent), it seems like no edition, other than
the most recent one, can ever be dropped.
Is this accurate or am I missing something?