Appendix I. Precautions Regarding Permissions

The permissions needed for using PFM - RM for Oracle differ depending on what is being used.

The following lists the permissions required for each operation target.

Organization of this section
(1) When the sp_rist.sql script is executed
(2) When the sp_rdrp.sql script is executed
(3) When the mk_rmus.sql script is executed
(4) When performance information is collected

(1) When the sp_rist.sql script is executed

The following table lists the system privileges needed for the Oracle account executing the sp_rist.sql script.

Table I-1 Oracle account privileges needed to execute the sp_rist.sql script

Privileges requiredDescription
CREATE SESSIONRequired when a session is established for the monitored Oracle Database.
CREATE TABLERequired when a table#1 required to monitor the monitored Oracle Database is registered.
CREATE PROCEDURERequired when a procedure#1 required to monitor the monitored Oracle Database is registered.
SELECT ANY DICTIONARYRequired when information#1 required to monitor the monitored Oracle Database is registered.
UNLIMITED TABLESPACERequired when information#1 required to monitor the monitored Oracle Database is registered#2.
#1
See the following tables.
In Windows
In 2.1.4(3) (c) Registering objects in the Oracle Database, see Table 2-11
In UNIX
In 2.2.4(4) (c) Registering objects in the Oracle Database, see Table 2-24
For details about the CREATE TABLE privilege, see Table 2-11 or Table 2-24. For details about the CREATE PROCEDURE privilege, see the corresponding package.
#2
This privilege is not needed when the assignment limit that allows writing to the default tablespace of the account used for monitoring has been set.

(2) When the sp_rdrp.sql script is executed

The following table lists the system privileges needed for the Oracle account executing the sp_rdrp.sql script.

Table I-2 Oracle account privileges needed to execute the sp_rdrp.sql script

Privileges requiredDescription
CREATE SESSIONRequired when a session is established for the monitored Oracle Database.

(3) When the mk_rmus.sql script is executed

The following table lists the system privileges needed for the Oracle account executing the mk_rmus.sql script.

Table I-3 Oracle account privileges needed to execute the mk_rmus.sql script

Privileges requiredDescription
CREATE SESSIONRequired when a session is established for the monitored Oracle Database.
CREATE USERRequired when a user is created for the monitored Oracle Database.
GRANT ANY PRIVILEGERequired when system privileges are granted for the monitored Oracle Database.

(4) When performance information is collected

The following table lists the Oracle account system privileges needed for PFM - RM for Oracle to collect performance information.

Table I-4 Oracle account privileges needed by PFM - RM for Oracle to collect performance information

Privileges requiredDescription
CREATE SESSIONRequired when a session is established for the monitored Oracle Database.
SELECT ANY DICTIONARYRequired to obtain performance information from the monitored Oracle Database.
UNLIMITED TABLESPACERequired to obtain the Explain Plan field for the PD_PDSQ records.#
SELECT ANY TABLERequired to obtain the Explain Plan (EXPLAIN_PLAN) field for SQL Text (PD_PDSQ) records.
INSERT ANY TABLERequired to obtain the Explain Plan (EXPLAIN_PLAN) field for SQL Text (PD_PDSQ) records.
UPDATE ANY TABLERequired to obtain the Explain Plan (EXPLAIN_PLAN) field for SQL Text (PD_PDSQ) records.
DELETE ANY TABLERequired to obtain the Explain Plan (EXPLAIN_PLAN) field for SQL Text (PD_PDSQ) records.
CREATE ANY INDEXRequired to obtain the Explain Plan (EXPLAIN_PLAN) field for SQL Text (PD_PDSQ) records.
ALTER ANY INDEXRequired to obtain the Explain Plan (EXPLAIN_PLAN) field for SQL Text (PD_PDSQ) records.
#
This privilege is not needed when the assignment limit that allows writing to the default tablespace of the account used for monitoring has been set.

The Oracle user account needs all of the privileges listed in Table I-4 to obtain PD_PDSQ records.

When PD_PDSQ records are not obtained, the CREATE SESSION and SELECT ANY DICTIONARY privileges are needed for the Oracle user account.