APEX 4.2.2
10786316
The bug (15935289) related to packaged application installs requiring APEX_PUBLIC_USER has been fixed in the 4.2.2 patchset so the Builder can be used to install packaged applications.
Questions
1. Is there a way we can choose the application id when installing a packaged application? We like to keep ranges of application ids separate under our control.
2. Instead of always using the
first schema provisioned for the workspace, can the supporting database objects (tables, packages, sequences, etc) be installed in some other schema? o my surprise, there appears to be no way to change this using Instance Administration! Am I missing something? The workspace has a bunch of schemas associaged with it. Why is the "first" schema immutable?!
Thanks