Requirements checklist

To configure an instance for monitoring, a PATROL OS account user must have SQLPlus connection to the instance. For this, the following permissions are required:

Permissions for PATROL OS account user on UNIX or Windows to connect to SQLPlus 

Directory namePermissions
For SQLPlus binary:
$ORACLE_HOME/binr + x
$ ORACLE_HOME/libr + x
$ ORACLE_HOME/lib/libsqlplus.sor
$ ORACLE_HOME/lib/libclntsh.sor + x
$ORACLE_HOME/sqlplusr + x
$ORACLE_HOME/sqlplus/mesgr + x
$ORACLE_HOME/oracorer + x
$ORACLE_HOME/oracore/mesgr + x
$ORACLE_HOME/oracore/zoneinfor + x
$ORACLE_HOME/oracore/zoneinfo/timezone.datr + x
For lsnrctl:
$ORACLE_HOME/networkr + x
$ORACLE_HOME/network/mesgr + x
All files under $ORACLE_HOME/network/mesgr


The above mentioned lsnrctl permissions are required for ORANET monitoring. When entering the paths, use the appropriate slash marks and ORACLE_HOME symbols for your operating system:

  • For UNIX:

Slash mark: / Symbol: $ORACLE_HOME

  • For Microsoft Windows:

Slash mark: \ Symbol: %ORACLE_HOME% The PATROL OS account must be able to connect to SQLPlus connection from OS prompt.

During instance configuration, if the PATROL OS user belongs to the others group and the Oracle environment is set with permissions on UNIX platform, as shown in the following example, the configuration will fail.


Permissions for Oracle environment:
-rwxr-x---+ 1 oracle dba 1059496 May 5 2010 $ORACLE_HOME/lib
-rwxr-x---+ 1 oracle dba 1059496 May 5 2010 $ORACLE_HOME/bin
-rwxr-x---+ 1 oracle dba 1059496 May 5 2010 sqlplus


For monitoring Oracle instances using ASM storage, the PATROL OS account must be a part of the primary DBA group.

For the instance configuration to be successful, you must skip the permission check by setting the /OracleConfig.ORACLE_SID.ACLFlag pconfig variable to 1.

The following table provides a checklist of the requirements that PATROL for Oracle Database needs to operate successfully.

PATROL for Oracle Database requirements checklist



A supported version of an Oracle database server

SQLPLUS Client for Oracle

init.ora parameters are set:

  • MTS (if applicable)
  • PQO (if applicable)

TNS_ADMIN (specify the location of the tnsname.ora file, if the file is not in the default location - $ORACLE_HOME/network/admin )

If you are using PATROL Classic Console, you should have the same version of Oracle KM installed on PATROL Console and PATROL Agent.

PATROL for your operating system components are loaded and running (used to monitor specific space information):

  • NT_LOGICAL_DISKS for Microsoft Windows

One of the following database accounts can be used to configure instances for monitoring:

  • SYS or
  • SYSTEM or
  • Any DBA privileged user

SQLPLUS must be installed on the computer where PATROL Agent is installed.

A service setup, so the SQLPLUS installed on PATROL Agent computer, can connect and query the database.

SSH connection from the computer where PATROL Agent is installed, to the computer where the database is installed.

SSH connection user must have read permission to the Oracle alert log listener files, and full permission to KM binaries and directory.


The PATROL default account must have read access to the directories where the Oracle database files reside.

If there is no read access to these files, the CollAvailability and CollCapacity parameters will be in a "WARN" State.

 The PATROL database monitoring account requires 20 to 30 MB of space in the default and temporary tablespaces.

Was this page helpful? Yes No Submitting... Thank you


  1. Dony Sheppard

    Is it possible to clarify the above permissions requirements when monitoring the database locale to the agent vs monitoring the DB remotely?

    The Patrol OS Account requirements are those required if the Patrol Agent and the Oracle KM are installed local?  If they have an SSH user that can make the connection to the DB server then what permissions are needed by the SQLPlus client connection to the remote DB?

    Mar 14, 2018 07:54