Reduce Oracle database user privileges to avoid cross schemas clashes
Description
Today Oracle database users for testing/CI have way too much privileges that may have impacts when querying Database Metadata (i.e. seeing tables that should not be seen).
Current set of privileges are enough:
RESOURCE role
CREATE VIEW
CREATE SESSION
CREATE SYNONYM
CREATE ANY INDEX (for XMLType tables)
EXECUTE ANY TYPE (to avoid a grant just after type creation)
Today Oracle database users for testing/CI have way too much privileges that may have impacts when querying Database Metadata (i.e. seeing tables that should not be seen).
Current set of privileges are enough:
RESOURCE role
CREATE VIEW
CREATE SESSION
CREATE SYNONYM
CREATE ANY INDEX (for XMLType tables)
EXECUTE ANY TYPE (to avoid a grant just after type creation)
For 23c, DB_DEVELOPER_ROLE would be perfect.