Create database schema
You can skip this step if you plan to use an existing schema for the DIH database objects, such as the
STGADM schema for data conversion.
Below are example statements to create a new schema for DIH. The recommended name for this new schema is DIHADM, but you can choose any name you prefer.
CREATE USER DIHADM IDENTIFIED BY DIHADM
DEFAULT TABLESPACE USERS
TEMPORARY TABLESPACE temp
PROFILE default;
GRANT UNLIMITED TABLESPACE TO DIHADM WITH ADMIN OPTION;
GRANT SELECT ANY TABLE TO DIHADM;
GRANT CREATE DATABASE LINK TO DIHADM;
GRANT connect TO DIHADM;
GRANT resource TO DIHADM;
GRANT CREATE ANY SYNONYM TO DIHADM;
GRANT SELECT ANY DICTIONARY TO DIHADM;
ALTER USER DIHADM DEFAULT ROLE ALL;
GRANT CREATE SESSION TO DIHADM;
-- DBMS Scheduler Permissions
GRANT CREATE JOB TO DIHADM;
GRANT EXECUTE ANY CLASS TO DIHADM;
GRANT MANAGE SCHEDULER TO DIHADM;
GRANT CREATE JOB TO DIHADM;
GRANT EXECUTE ANY CLASS TO DIHADM;
GRANT MANAGE SCHEDULER TO DIHADM;
BEGIN
dbms_rule_adm.grant_system_privilege(
privilege => dbms_rule_adm.create_rule_set_obj,
grantee => 'DIHADM',
grant_option => FALSE
);
dbms_rule_adm.grant_system_privilege(
privilege => dbms_rule_adm.create_evaluation_context_obj,
grantee => 'DIHADM',
grant_option => FALSE
);
dbms_rule_adm.grant_system_privilege(
privilege => dbms_rule_adm.create_rule_obj,
grantee => 'DIHADM',
grant_option => FALSE
);
END;
-- NOTE: The DIH user must have access to DBMS_LOCK
-- Uncomment the "grant" statement below to grant access
-- If not granted here, it must be granted manually outside of this installation
--GRANT EXECUTE ON sys.dbms_lock TO DIHADM;
-- DBA privilege is not typically granted by included as a comment for reference
--GRANT dba TO DIHADM WITH ADMIN OPTION;