EBS 12.2 upgrade to 19C

[mmanavat]

Hello ,
 We have recently upgraded our 2 node RAC database of our EBS 12.2.4 application  from 12.1 to 19.11. All steps went fine with out any issues. After completing our upgrade and plugging our DB to the 19C CDB we noticed that PDB$SEED was not listing in the list.
When we recheck the alert log we came to know that PDB$SEED was not created in that step as it was trying to create data file in a non-existing mount point. Ie. it was failing to create PDB$SEED datafile in /oradata( which is not in the system)  where our RAC system uses ASM disks.

But we didn't face any issues on the process . EBS DB and Application was also working fine as well.

Our current setting is working and people are accessing it. Can we expect any other issues for this on future? as the expected architecture contains one seeded PDB as well ?

Is there any way to add this seed PDB to the current architecture.



 

[ErmanArslansOracleBlog]

PDB$SEED acts like a template normally.
But! This is EBS and we don't want to be unsupported in any ways.
In the documentation, it is documented to do some actions on PDB$SEED as well.. So it is not that unimportant.
There are ways to recreate the PDB$SEED from an existing PDB.. (it is not documented in MOS, but there is still some ways for it..)
According to Oracle Support, in order to get PDB$SEED, you need to create a new CDB and then unplug / plug your PDB there. This indrectly makes us use rapid cloning techniques.

I would create an SR for this. Get approval from Oracle support before doing anything on this subject.