Database user setup and configuration

In general, the database users for external databases must be provided by an operator. The details about the database users and privileges that are required for each module can be found in the module’s operations manual.

Oracle privileges

The following three predefined SOT roles for Oracle each contain a set of privileges. The operator can decide, if he wants to use these Oracle roles to easily assign the permissions to the Oracle users for each module. Alternatively, the users need to have the respective privileges assigned directly. The required SOT roles for Oracle for each module user are documented in the respective Module Operations Manual and they are part of the helm chart of each module.

NEXEED_BASIC_ROLE

This role consists of the following privileges:

ALTER SESSION
CREATE PROCEDURE
CREATE SEQUENCE
CREATE SESSION
CREATE TABLE
CREATE TRIGGER
CREATE VIEW
CREATE SYNONYM

NEXEED_EXTENDED_ROLE

This role consists of the following privileges:

CREATE CLUSTER
CREATE DATABASE LINK
CREATE INDEXTYPE
CREATE JOB
CREATE MATERIALIZED VIEW
CREATE OPERATOR
CREATE SNAPSHOT
CREATE TYPE
DEBUG CONNECT SESSION
EXECUTE ON SYS.DBMS_CRYPTO
EXECUTE ON SYS.DBMS_SCHEDULER
QUERY REWRITE
EXECUTE ON DBMS_LOB
EXECUTE ON DBMS_SESSION

NEXEED_MONITORING_ROLE

This role consists of the following privileges:

SELECT ON DBA_DATA_FILES
SELECT ON DBA_FREE_SPACE
SELECT ON SYS.V_$PARAMETER
SELECT ON SYS.V_$PROCESS
SELECT ON SYS.V_$SESSION
SELECT ON SYS.V_$SESSTAT
SELECT ON V_$SQL
SELECT ON SYS.V_$SQL_PLAN
SELECT ON SYS.V_$SQL_PLAN_STATISTICS_ALL
SELECT ON SYS.V_$STATNAME
SELECT ON DBA_TEMP_FILES

MSSQL privileges

The required privileges for an MSSQL user for each SOT module are defined in the respective SOT operations manual. If it is not defined otherwise, the user requires DBO permissions on the database.