NetIQ Identity Governance Report Database Update

Details

Overview:

This update includes the modified and affected views required by the report.

System Requirements:

NetIQ Identity Governance 3.0 or higher.

Non-default Database User:

If Identity Governance was installed to use a non-default database user account instead of igops, it will be necessary to modify the SQL files in this download package to replace all instances of igops with the name of the corresponding database account defined for the environment.

Modify only the SQL files necessary for the database type in the environment. The file names for MSSQL begin with "ms-", the file names for Oracle begin with "or-", and the file names for PostgreSQL begin with "pg-".

View Dependencies:

Some Identity Governance report views have dependencies on one another. In cases where a report view definition has been modified for a report, if it is part of a view dependency tree, the view definitions for the entire dependency tree are provided in the SQL file.

The file names for these view dependency tree bundles are prefixed with "ms-", "or-", or "pg-" to indicate whether they are intended for MSSQL, Oracle, or PostgreSQL, followed by the name of the report before the SQL file extension.

Installation:

Download the ZIP file associated with the report that the tool tip indicates contains "additional downloads" to the machine where the database resides. The "additional downloads" are the SQL files. Extract the files contained in the ZIP file.

PostgreSQL Environments

If Identity Governance was installed to use a non-default database name instead of igops, in the steps below replace the references to igops with the corresponding name in the local environment.

1. Open pgAdmin PostgreSQL Tools.
2. Connect to the server that hosts the Identity Governance database.
3. Select the igops database.
4. Navigate to igops > Schemas > public > Views.
5. Open an instance of the Query Tool.
6. Drag and drop or copy the contents of the SQL file for PostgreSQL to the SQL Editor in the Query Tool.
7. Execute the query.

Oracle Environments

If Identity Governance was installed to use a non-default database name instead of igops, in the steps below replace the references to igops with the corresponding name in the local environment.

1. Open Oracle SQL Developer.
2. Connect to the server that hosts the Identity Governance database.
3. Select the Views.
4. Open an SQL Worksheet.
5. Drag and drop or copy the contents of the SQL file for Oracle to the Worksheet.
6. Click Run Script.

MSSQL Environments

If Identity Governance was installed to use a non-default database name instead of igops, in the steps below replace the references to igops with the corresponding name in the local environment.

1. Open Microsoft SQL Server Management Studio.
2. Connect to the server that hosts the Identity Governance database.
3. Select Databases > igops.
4. Open a new query in the Query Editor.
5. Drag and drop or copy the contents of the SQL file for MSSQL to the Query Editor.
6. Execute the query.

NOTE: A data collection might have to be done in order to view changes that have been made.

File Contents

Current-User-Access_3.0.1.1.zip

Files Included
ms-current_user_access.sql
or-current_user_access.sql
pg-current_user_access.sql
ReadMe.html