There is often an awkward quandary among DBA's whenever the development team asks the DBA to create SSE_ROLE per Oracle documentation. This is true especially in production.
Per Oracle Docuentation:
CREATE ROLE SSE_ROLE;
GRANT DBA TO SSE_ROLE;
GRANT SSE_ROLE TO OBAW;
I suggest the following alternative to my clients:
Grant schema with CONNECT, RESOURCE, and SSE_ROLE_ALT. Use SSE_ROLE_ALT instead of SSE_ROLE
Grant below privileges to OBAW:
CREATE TABLE
CREATE TRIGGER
CREATE SEQUENCE
CREATE PROCEDURE
CREATE INDEXTYPE
CREATE CLUSTER
Per Oracle Docuentation:
CREATE ROLE SSE_ROLE;
GRANT DBA TO SSE_ROLE;
GRANT SSE_ROLE TO OBAW;
I suggest the following alternative to my clients:
Grant schema with CONNECT, RESOURCE, and SSE_ROLE_ALT. Use SSE_ROLE_ALT instead of SSE_ROLE
Grant below privileges to OBAW:
CREATE TABLE
CREATE TRIGGER
CREATE SEQUENCE
CREATE PROCEDURE
CREATE INDEXTYPE
CREATE CLUSTER