5.3 Preparing an Oracle Database for Identity Governance

1. Download the ojdbc7.jar file from the Oracle website.

2. Copy the file to a temporary directory on the tomcat_install server.

   The installation process then places the file in the:

   • Linux: /opt/netiq/idm/apps/tomcat/lib directory

   • Windows: c:\netiq\idm\apps\tomcat\lib directory

   NOTE:Ensure that you do not have an older version of the Oracle JDBC file in the directory or the installation fails.

To create the schemas:

1. Install a supported version of Oracle.

   For more information, see Database Server System Requirements.

2. Create or identify the database that you want Identity Governance to use.

3. In the database, create the schema for igops, igdcs, igwf, and igara with the following privileges:

   • select_catalog_role

   • Create session

   • Create table

   • Create view

   • Create sequence

   • Create procedure

   • Create trigger

   • Analyze any (igops only)

   • Create public synonym (igops only)

   • Drop public synonym (igops only)

4. Specify the same password for all schemas.

   NOTE:The installation process for Identity Governance requires you to specify one password that applies to all schemas. After installing Identity Governance, you can modify the passwords to be unique for each schema.

5. Issue the following commands:

   NOTE:If you use the default values of users and temp, skip the following commands:

   alter user dbName default tablespace users;
   alter user dbName temporary tablespace temp;

   alter user igops default tablespace users;
   alter user igops temporary tablespace temp;
   alter user igops quota unlimited on users;
   alter user igdcs default tablespace users;
   alter user igdcs temporary tablespace temp;
   alter user igdcs quota unlimited on users;
   alter user igwf default tablespace users;
   alter user igwf temporary tablespace temp;
   alter user igwf quota unlimited on users;
   alter user igara default tablespace users;
   alter user igara temporary tablespace temp;
   alter user igara quota unlimited on users;
   CREATE USER idm_rpt_cfg IDENTIFIED BY "<password>";
   GRANT CREATE SESSION, CREATE TABLE, CREATE VIEW, CREATE PROCEDURE, CREATE SEQUENCE, CREATE TRIGGER, UNLIMITED TABLESPACE TO idm_rpt_cfg;
   create role ig_report_role not identified;
   grant EXECUTE ON igops.max_risk_level to igrptuser;
   grant EXECUTE ON igops.min_risk_level to igrptuser;
   grant EXECUTE ON igops.risk_value to igrptuser;

6. Create the reporting user igrptuser.

   CREATE USER igrptuser IDENTIFIED BY "igrptuser_password";

7. Grant the reporting role to the reporting user plus additional privileges.

   GRANT IG_REPORT_ROLE TO igrptuser;
   GRANT CREATE SESSION TO igrptuser;
   ALTER USER igrptuser DEFAULT TABLESPACE USERS;
   ALTER USER igrptuser TEMPORARY TABLESPACE TEMP;
   

8. When installing Identity Governance, specify one of the following settings:

   • Configure database now > Update, if you want the installation program to generate or update the schemas, tables, and views when you migrate from Identity Governance 2.5 to 3.0

   • Configure database now > Use only existing, if your database is already set up correctly with all schemas, roles, and users

   • Generate SQL for later, if your database administrator wants to generate the schemas, tables, and views

   • No database configuration, for using two or more nodes in clustered environment

   For more information about using SQL statements after installation, see Configuring the Databases after Installation.