Skip to Main Content

APEX

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Adding a schema to a workspace raises ORA-1031 insufficient privileges

Dave_VZMar 18 2022 — edited Mar 27 2022

[addendum Okay, for those who have responded to my related queries, it's getting through at last why I cannot assign the SYS schema to a workspace.]
I've inherited a scenario in which APEX is the only permitted interface (using SQL Workshop). My predecessors created just two schemas and two workspaces, RO and RW.
As the INTERNAL user, I thought I'd see whether I could create a third workspace and populate it with my own DBA-privileged schema. I raise a ORA-1031 instead. If this is covered in some documentation somewhere, my old eyes are completely missing it. TIA for guidance.

Comments

Post Details

Added on Mar 18 2022
3 comments
320 views