In my last post, I had demonstrated that without OMF, If an application creates new datafiles, application PDB’s always fails to sync with the application. When I mentioned it to Tim, he raised an SR with Oracle who have clarified that it is Bug 21933632. Although it is not documented yet but OMF is mandatory if using the Application Container feature. If it is attempted to sync application PDB’s with an application that creates non-OMF datafile(s), sync will run into problem while trying to replay a create tablespace or similar statement with a hard-coded file name.”
References:
Multitenant: Application Containers in Oracle Database 12c Release 2
————————————————————————————————————————-
Related Links:
The drama on using the application containers is not only in this issue. I faced at least a couple of as serious issues in managing the application containers.
For example, make the application have a few tables with links between them, sequences, views and procedures. Even after enabling the OMF, when you syn the application PDB it will complain:
SQL> ALTER PLUGGABLE DATABASE APPLICATION hr_app SYNC;
ALTER PLUGGABLE DATABASE APPLICATION hr_app SYNC
*
ERROR at line 1:
ORA-00955: name is already used by an existing object
Oracle admits it is a bug and at this time no remedy has yet been provided.