Setting Up the AE Database

The Automation Engine supports different databases. This topic guides you through the different database rights for the different databases supported.

DB2

• Read access to system tables such as SYSIBM.SYSTABLES
• Right to create tablespaces
• Right to create indexes
• Full access to the tables

Use the following command to set these rights:

grant dbadm on database to <user>

More information:

• Preparing the AE Database - DB2
• Preparing for the Manual Installation

MS SQL

No further steps are required at this point, provided you have followed the preparation steps.

The database user requires the "db_owner" role. To add it, use the following SQL query:

sp_addrolemember 'db_owner','uc4'

If you use ILM (Information Lifecycle Management) to maintain your AE database, the user must have the following permission:

GRANT VIEW SERVER STATE TO uc4;

More information:

• Preparing the AE Database - MS SQL
• ILM - Information Lifecycle Management
• Preparing for the Manual Installation

ORACLE

• CREATE SESSION

• CREATE TABLE
• CREATE SEQUENCE
• CREATE PROCEDURE
• CREATE TRIGGER
• EXECUTE ANY PROCEDURE
• CREATE VIEW
• CREATE PUBLIC SYNONYM
• DROP PUBLIC SYNONYM
• ALTER SESSION
• Either the system privilege UNLIMITED TABLESPACE or the tablespace quotas for all tablespaces
• The right EXECUTE for the DBMS package (command to set this right: GRANT execute ON dbms_lock TO <schema_name>). This right can only be set by a user who has the SYSDBA privilege.

Example commands that can be used to assign the relevant rights to the database user uc4:

GRANT create table, create sequence, create session, create procedure, create trigger, execute any procedure, create public synonym, drop public synonym, create view, alter session, select any dictionary TO uc4;
GRANT execute ON dbms_lock TO uc4;
GRANT unlimited tablespace TO uc4;

The following example commands can be used to check the rights:

CREATE TABLE

CREATE TABLE UCDUMMY (UCDUMMY_PK INTEGER NOT NULL, UCDUMMY_System VARCHAR2 (8) NULL,
CONSTRAINT PK_UCDUMMY PRIMARY KEY
(
UCDUMMY_PK
) USING INDEX TABLESPACE UC4_INDEX
) TABLESPACE UC4_DATA;

CREATE SEQUENCE

CREATE SEQUENCE SQ_UCDUMMY
INCREMENT BY 1 START WITH 1 MAXVALUE 999999999
MINVALUE 1 CYCLE CACHE 1000 NOORDER;

CREATE PROCEDURE

create or replace PROCEDURE DUMMY_PROCEDURE
as
BEGIN
dbms_output.enable(buffer_size => NULL);
dbms_lock.sleep(5);
dbms_output.put_line('could start procedure');
END;

CREATE TRIGGER 

CREATE OR REPLACE
TRIGGER DUMMY_TRIGGER
AFTER INSERT ON UCDUMMY
BEGIN
NULL;
END;

SET SERVER OUTPUT

set serveroutput on;

ALTER SESSION:

ALTER SESSION SET NLS_DATE_LANGUAGE = American;

EXECUTE PROCEDURE, EXECUTE for the DBMS package:

execute dummy_procedure;

Use the following commands to delete the test data that has been created: 

DROP TABLE UCDUMMY;
DROP SEQUENCE SQ_UCDUMMY;
DROP PROCEDURE DUMMY_PROCEDURE;

More information:

• Preparing the AE Database - Oracle
• ILM - Information Lifecycle Management
• Preparing for the Manual Installation

PostgreSQL

No further steps are required at this point for PostgreSQL, provided you have followed the preparation steps.

More information:

• Preparing the AE Database - PostgreSQL
• Preparing for the Manual Installation.

Next step:

Installing the Utilities