(Picture by Tiia Monto [CC BY-SA 3.0], via Wikimedia Commons)
As explained in my previous blog post, in an attempt to develop a solid script to handle ACE (who says I am a quibbler ?), I also played with Data Pump to export and import ACE/ACL in Oracle 12cR1.
I found out that
OBJECT_PATH=NETWORK_ACL exists in
database_export_objects. I could not get many information about that, so I got confirmation from My Oracle Support that
NETWORK_ACL was the right OBJECT_PATH to use.
This blog post consists in a quick reminder on how to export and import ACE/ACL with Data Pump.
(Picture by Miguel Hermoso Cuesta (Own work) [CC BY-SA 3.0], via Wikimedia Commons)
My work environment has approximately 100 production databases and 400 non-production databases. We developed a self-service web application (with APEX 😉 ) that offers developers the right to clone databases. We have some development databases with ACL, concerning development hosts, which are relevant only in development environment. And of course, some production databases with ACL, concerning production hosts, which are relevant only in production environment.
What happens when we duplicate a production database on a development database ? The ACL from the production database are now on the development database. And the development ACL are gone, obviously.
What can we do to keep those development ACL on the development database after a duplication ?