Skip to Main Content
Feature Request FR-3902
Product Area Application Builder
Status CLOSED

2 Voters

Remove requirement to install as SYS

jwells Public · Jul 12 2024

Idea Summary
Allow APEX to be installed without having to be logged in with SYS as SYSDBA.

Use Case
Large companies I have worked with always have  their IT areas highly segmented.  Application delivery teams are typically segregated from the Enterprise DBA teams, and Enterprise DBA teams are separated from other Enterprise Infrastructure teams covering areas like server hardware, storage, O/S, networking, etc.  This makes it difficult for Application teams to install and upgrade APEX because it requires an intake/ticketing process to get the E-DBA team to do the installation, and more often than not gets slowed down because of the requirement to install the software as SYS.

Preferred Solution (Optional)
Ideally, APEX could be installed and upgraded using a separate “installer” account that has all the necessary privileges, exactly the same way it is done with ORDS installations.  In this way, Application teams only have to do an initial, one-time intake process with the E-DBA team to get that special account created, and then from then on do not have to involve them for ongoing APEX installations, patches, and upgrades.

We reviewed this idea carefully, and while it was interesting, we concluded that it is unlikely to make its way into APEX in the foreseeable future.

Comments

Comments

  • vincent morneau Admin OP 1.9 years ago

    This is a valid request, however we can't commit to action this idea in the short term given all the implications for APEX installs, therefore we are closing it for now. Hopefully we can revisit this later.