Information on Retired editions

[Sri]

Hi Erman,

In EBS,will the edition go to retired status automatically when it is no longer needed?sample from our environment

==================================================================
=                             Editions
=========================================================================

Edition Name    Type     Status   Current?
--------------- -------- -------- --------
ORA$BASE                 ACTIVE
V_20170104_1115          ACTIVE
V_20170105_1144          ACTIVE
V_20170904_1329          ACTIVE
V_20170905_1612          ACTIVE
V_20170920_1550          ACTIVE
V_20170922_1009 OLD      ACTIVE
V_20171016_1417 RUN      ACTIVE
V_20171017_1308 PATCH    ACTIVE   CURRENT

Request your help

Thank you

[ErmanArslansOracleBlog]

I didn't understand your question.
Please revise.

[Sri]

Sorry,

we have old run and patch editions in ebs,would like to know when will we see the retired editions

[ErmanArslansOracleBlog]

*You can see the retired editions using @ADZDSHOWED.sql

Example:

SQL> @ADZDSHOWED.sql

Edition Name Type Status Current?
--------------- -------- -------- --------
EDITION1 PATCH RETIRED   ---> this one is retired..
ORA$BASE ACTIVE
V_20000001_2001 ACTIVE
V_20000002_2002 ACTIVE
V_20000003_0003 OLD ACTIVE
V_20000004_0004 RUN ACTIVE CURRENT

*The editions in EBS can be retired using sys.ad_zd_sys.retire_old_editions.

*In general, once you make a new edition  available to all users, you may want to retire the old edition, so that no user except SYS can use the retired edition.

*In EBS online patching, old database editions gets retired during the cutover phase


So, after the cutover phase, you should see them.
Just after the cutover phase, run @ADZDSHOWED.sql.. You should see them at that time..

[Sri]

Thanks for the update.You said old database editions get retired during cutover phase.but in my environment i am not able to see any retired editions.is this normal


==================================================================
=                             Editions
=========================================================================

Edition Name    Type     Status   Current?
--------------- -------- -------- --------
ORA$BASE                 ACTIVE
V_20170104_1115          ACTIVE
V_20170105_1144          ACTIVE
V_20170904_1329          ACTIVE
V_20170905_1612          ACTIVE
V_20170920_1550          ACTIVE
V_20170922_1009 OLD      ACTIVE
V_20171016_1417 RUN      ACTIVE
V_20171017_1308 PATCH    ACTIVE   CURRENT

[ErmanArslansOracleBlog]

Did you check just after running cutover?
I mean before running cleanup or prepare phases..

[ErmanArslansOracleBlog]

Bytheway, retiring and dropping an edition means different things.

cutover should retire the editions.
actualize_all+cleanup(full) should drop the editions.

So, check just after running cutover.. You should see the retired editions at that moment.

[Sri]

Thank you,I have one question here.

If cutover retires the edition,then only sys should have access to connect to old editions right?but i have tried with apps and able to connect.please clarify

Thanks,
sri

[ErmanArslansOracleBlog]

Yes.. When you retire an edition no user except SYS can use that edition.

Was that edition really retired?

[Sri]

Thanks erman,
 
Status was as below

==================================================================
=                             Editions
=========================================================================

Edition Name    Type     Status   Current?
--------------- -------- -------- --------
ORA$BASE                 ACTIVE
V_20170104_1115          ACTIVE
V_20170105_1144          ACTIVE
V_20170904_1329          ACTIVE
V_20170905_1612          ACTIVE
V_20170920_1550          ACTIVE
V_20170922_1009 OLD      ACTIVE
V_20171016_1417 RUN      ACTIVE
V_20171017_1308 PATCH    ACTIVE   CURRENT

[Sri]

That means,cutover was not retiring the editions?

[ErmanArslansOracleBlog]

As seen, you currently have no retired editions.

maybe Cutover retired them and then actualize_all+cleanup removed them..

If you want to know this, you need to check the cutover, actualize_all and cleanup logs.