Database Administrative User Privileges

Following are the privileges required by the OpenText Application Quality Management database administrative user. Additional explanations about these privileges can be found in the notes at the end of the table.

Privilege	Description
CREATE SESSION WITH ADMIN OPTION ⁽¹⁾	OpenText Application Quality Management uses this privilege to connect to the database as the database administrative user.
CREATE USER	Required to create a new project user schema when creating a new project.
DROP USER	When deleting a project, OpenText Application Quality Management attempts to remove the Site Administration database schema from the database server. If there is an insufficient privileges error, OpenText Application Quality Management ignores the error and requests that the user notify the database administrator to delete (drop) the database user schema.
CREATE TABLE WITH ADMIN OPTION ⁽¹⁾	Required for granting this permission to a newly created project user schema.
CREATE VIEW WITH ADMIN OPTION ⁽¹⁾	Required to create views for projects.
CREATE TRIGGER WITH ADMIN OPTION ⁽¹⁾	Required to create triggers for projects. OpenText Application Quality Management uses database triggers to collect change history for specific tables.
CREATE SEQUENCE WITH ADMIN OPTION ⁽¹⁾	Required to create sequences for projects.
CREATE PROCEDURE WITH ADMIN OPTION ⁽¹⁾	Required to create stored packages for projects. ALM uses packages to collect change history for specific tables.
CTXAPP ROLE WITH ADMIN OPTION ⁽¹⁾	Enables OpenText Application Quality Management to use the Oracle text searching feature. This role exists only if the Oracle text search component was installed and enabled on the database server.
SELECT ON DBA_FREE_SPACE ⁽²⁾	Required to check free space on the database server prior to creating a new Site Administration database schema or a new project.
SELECT ON SYS.DBA_TABLESPACES ⁽²⁾	Required to collect a list of tablespaces that exist on the database server prior to creating a new Site Administration database schema or a new project.
SELECT ON SYS.DBA_USERS ⁽²⁾	Required to verify the existence of specific database project users. For example, you might want to verify the existence of an Oracle CTXSYS user before creating a new project.
SELECT ON SYS.DBA_REGISTRY ⁽²⁾	Required to verify that the text search component is installed on the database server.
SELECT ON SYS.DBA_ROLES ⁽²⁾	Required to verify that the text search role (CTXAPP) is installed on the database server.
SELECT ANY TABLE WITH ADMIN OPTION ⁽¹⁾ and INSERT ANY TABLE	Required for various administrative operations when upgrading the Site Administration database schema during installation using the copy and upgrade method, and for enhancing performance when copying a project that has the same source and target database server.

Note:

⁽¹⁾ An ALM database administrative user must have privileges with Admin Option.
⁽²⁾ The SELECT ON SYS privileges can be given directly by the table owner, or through a database application role. To avoid giving these privileges each time, you can grant this role to the database administrative user. The recommended name for this role is QC_SELECT_ON_SYS_OBJECTS. You should run this script before you run the qc_admin_db___oracle.sql script.