A run time only environment doesn’t have any of the management web gui for APEX.
Everything is driven and deployed with apex_instance_admin and the underlying
packages for APEX
You need to become more adept at looking at APEX from the metadata tables.
From: oracle-l-bounce@xxxxxxxxxxxxx <oracle-l-bounce@xxxxxxxxxxxxx> On Behalf
Of Jeff Chirco
Sent: Wednesday, October 30, 2019 8:50 AM
To: Dimensional DBA <dimensional.dba@xxxxxxxxxxx>
Cc: oracle-l-freelist <oracle-l@xxxxxxxxxxxxx>
Subject: Re: APEX App rollout to Production
Thanks for the reply. I am curious what is trickier with run-time vs
development install? We just began looking into the different options and pros
On Wed, Oct 30, 2019 at 8:13 AM <dimensional.dba@xxxxxxxxxxx
<mailto:dimensional.dba@xxxxxxxxxxx> > wrote:
99% of what I have worked with in APEX, the DBA has performed the migration to
Besides the APEX specific items there are normally objects that also have to be
Of course it gets trickier if you have run-time only environment install at
production versus a development environment install.
It is doable to have developers migrate APEX items but it really depends on
your Change Management rules.
From: oracle-l-bounce@xxxxxxxxxxxxx <mailto:oracle-l-bounce@xxxxxxxxxxxxx>
<oracle-l-bounce@xxxxxxxxxxxxx <mailto:oracle-l-bounce@xxxxxxxxxxxxx> > On
Behalf Of Jeff Chirco
Sent: Tuesday, October 29, 2019 9:57 AM
To: oracle-l-freelist <oracle-l@xxxxxxxxxxxxx <mailto:oracle-l@xxxxxxxxxxxxx> >
Subject: APEX App rollout to Production
Hey all APEX users. Who typically moves updates to APEX applications to
Production? Only DBA's or do you let developers publish updates? What is your
full process look like for APEX?