RSA Identity Governance & Lifecycle 7.x (and later)
 

RSA Governance & Lifecycle Support will often request an AWR report from customers to assist with troubleshooting product issues, when customer-supplied database is being used and the customer has the appropriate licensing to generate AWR. The right to use AWR is part of the Oracle Diagnostics Pack. Customers should contact their DBA team to find out whether they are licensed to run AWR reports.

If a customer has the appropriate Oracle licensing to generate AWR reports for their customer-supplied database, the Diagnostics feature must be enabled in the Oracle database to be able to generate an AWR report. This can be verified by running the following SQL statement:
 

oracle@acm-710:~> sqlplus / as sysdba

SQL*Plus: Release 12.1.0.2.0 Production on Tue Feb 26 14:02:44 2019

Copyright (c) 1982, 2014, Oracle.  All rights reserved.

Connected to:
Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

SQL> show parameter CONTROL_MANAGEMENT_PACK_ACCESS;

NAME                                   TYPE                       VALUE
------------------------------------   -------------              ------------------- 

control_management_pack_access          string                     DIAGNOSTIC
SQL>

Seeing the value of DIAGNOSTIC in the above SQL query indicates that the Oracle Diagnostics Pack is enabled (subject to the customer having the required Oracle license) to run AWR reports in a customer-supplied database scenario.

RSA Identity Governance & Lifecycle provides the ability to generate a database performance statistics report, an alternative to AWR, for troubleshooting database performance issues.

Customers using an RSA-provided database for RSA Identity Governance & Lifecycle must generate a database performance statistics report for troubleshooting database performance issues. RSA Identity Governance & Lifecycle versions 7.1.1 P11, 7.2.0 P07, 7.2.1 P02, and all older versions, may have the Oracle parameter 'control_management_pack_access' set to DIAGNOSTIC. This Oracle parameter will be reset to NONE for RSA-provided database, effective 7.1.1 P12, 7.2.0 P08, 7.2.1 P03, and in future versions of RSA Identity Governance & Lifecycle.

For more information about generating the database performance statistics report, see the following: How to generate Oracle database performance statistics in RSA Governance & Lifecycle

Applying patch P12 (or later) on version 7.1.1, patch P08 (or later) on version 7.2.0, or patch P03 (or later) on version 7.2.1 of RSA Identity Governance & Lifecycle deployments using RSA-provided database installed locally on the WildFly application server automatically sets the Oracle parameter ‘control_management_pack_access’ to NONE.  For RSA Identity Governance & Lifecycle deployments using RSA-provided database installed on a remote host, the Oracle parameter ‘control_management_pack_access’ must be set to NONE manually. Use the following steps to verify/change the Oracle parameter:

Step 1: Login as oracle user on the database host pointed to by the RSA Identity Governance & Lifecycle application

Step 2: Start sqlplus as follows:

sqlplus / as sysdba

Step 3: Type the following command at the SQL> prompt:

show parameter CONTROL_MANAGEMENT_PACK_ACCESS;

Step 4: Verify that the above command results in the following output:

NAME                                   TYPE            VALUE
------------------------------------   -------------   ------------------- 
control_management_pack_access         string          NONE

Step 5: If the VALUE column in the output shows anything other than ‘NONE’ (e.g., it may be set to ‘DIAGNOSTIC’), then use the following command at the SQL> prompt:

alter system set control_management_pack_access='NONE' scope=both;

Step 6: Type ‘exit’ at the SQL> prompt to close the sqlplus session.