Download PDF
Download page Configure Oracle Collectors.
Configure Oracle Collectors
To monitor Oracle with Database Visibility, you must be running Oracle 10g or newer.
If you are configuring a collector for Oracle RAC, you only need to configure one collector for the entire cluster. You can choose any node in the cluster to connect to, and the entire cluster will automatically be detected.
If you are using Oracle 12c as PDB, the query for system metrics is available from Oracle Database 12c Release 2 (12.2.0.1) onwards. See the Oracle documentation for more information.
Connection Details
Section | Field | Description |
---|---|---|
Create New Collector | Database Type | The database type that you want to monitor. |
Agent | The Database Agent that manages the collector. | |
Collector Name | The name you want to identify the collector by. | |
Connection Details | Hostname or IP Address | The hostname or IP address of the machine that your database is running on. |
Listener Port | The TCP/IP address of the port on which your database communicates with the Database Agent | |
SID or Service Name | The SID or service name of the Oracle instance you want to monitor. For CDB (container database) monitoring, provide the CDB service name and for PDB (pluggable database) monitoring, provide the PDB service name. | |
Custom JDBC Connection String | The JDBC connection string generated by the database agent, for example, When using connection string for Kerberos, ensure that you select the LDAP/Kerberos option under Advanced Options. | |
Username and Password | Username | The name of the user who is connecting to and monitoring the database through the Database Agent. The user should have the permissions described in User Permissions for Oracle. |
Password | The password of the user who is connecting to and monitoring the database through the Database Agent. | |
Cyberark | Click to enable CyberArk for database username and password. When CyberArk is enabled, information about Application, Safe, Folder, and Object is required to fetch the username and password for your database. To use CyberArk with Database Visibility, you must download the JavaPasswordSDK.jar file from the CyberArk web site and rename the file to cyberark-sdk-9.5.jar . Then, you must copy the JAR file to the lib directory of the database agent zip file. | |
Advanced Options | Sub-Collectors | Click to monitor multiple database instances in a consolidated view, and aggregate metrics of multiple databases. To monitor a custom cluster, you can add additional hostname or IP address, and port details for each sub-collector. You can add up to a total of 29 sub-collectors. Thereby, 30 databases can be monitored in a custom cluster. In addition to the licenses consumed by the main collector, each sub-collector consumes one or more licenses, depending on the database type. Note
|
Connection Properties | Click to add a new JDBC connection property or edit an existing property for relational databases. For monitoring the database using Kerberos authentication, follow the instructions mentioned at Monitor Oracle Databases Using Kerberos Authentication. | |
Exclude Schemas | The schemas that you want to exclude, separated by commas. | |
SSL Connection | Click to enable the SSL connection. You can use SSL Connection for authentication and signing credentials.
If the SSL_CLIENT_AUTHENTICATION parameter is set to true in
| |
LDAP/Kerberos | Use LDAP/Kerberos authentication to manage the database user and the host user passwords. | |
Monitor Operating System | See this page for more details, Configure the Database Agent to Monitor Server Hardware. |
User Permissions for Oracle
For versions of Oracle 10g and later
The following permissions are required for the Oracle user:
- CREATE SESSION
- SELECT_CATALOG_ROLE
To create a user with these permissions, you can run the following SQL. In this SQL, change "password
" to a safe and secure password, and change the tablespace
names, "users
" and "temp
" to those available in your Oracle instance.
CREATE USER DBMon_Agent_User IDENTIFIED BY password
default tablespace users
temporary tablespace temp;
GRANT CREATE SESSION, SELECT_CATALOG_ROLE TO DBMon_Agent_User;
where DBMon_Agent_User
is the user name under which you run the Database Visibility Agent.
For versions of Oracle 12c and later with Multitenant Container Database Option enabled
The following permissions are required for the Oracle user:
- CREATE SESSION
- SELECT_CATALOG_ROLE
To create a user with these permissions, you can run the following SQL. In this SQL, change "password
" to a safe and secure password, and change the tablespace
names, "users
" and "temp
" to those available in your Oracle instance.
CREATE USER C##DBMon_Agent_User IDENTIFIED BY password default tablespace users temporary tablespace temp CONTAINER=ALL;
GRANT CREATE SESSION, SELECT_CATALOG_ROLE TO C##DBMon_Agent_User CONTAINER=ALL;
ALTER USER C##DBMon_Agent_User QUOTA 100M ON USERS;
alter user C##DBMON_AGENT_USER set container_data=all container=current;
Permissions Required for Oracle Explain Plans
To generate an execution plan for a specified query, paste the query text into the Explain another query box. You must provide a plan table in the AppDynamics monitoring user's schema. You can find a sample output table named PLAN_TABLE
in the UTLXPLAN.SQL
script. To update or view the plan table, you need INSERT and SELECT privileges. To explain a query, you need access privileges for the tables and views included in that query.
AppDynamics Database Visibility can generate explain plans within its SQL drill-down window. To enable this functionality, you must have a plan table accessible to the AppDynamics Database Visibility schema user. You can create this plan table with the following command from sqlplus
when logged on as the AppDynamics Database Visibility user:
Windows:
@?\rdbms\admin\utlxplan.sql
Linux:
@?/rdbms/admin/utlxplan.sql
Permissions for individual views and tables
You can grant permission to individual views and tables even if the SELECT_CATALOG_ROLE permission is not available to your organization.
- Execute permissions on
dbms_application_info.set_module
. - Select permissions on the following privileges:
dba_data_files
dba_free_spacedba_ind_columns
dba_indexes
dba_objects
dba_proceduresdba_segments
dba_sequences
dba_synonyms
dba_recyclebin
dba_tab_columns
dba_tables
dba_users
dba_views
gv$instance
gv$containers
gv$parameter
gv$pdbs
gv$servicesv$archive_dest
v$archive_dest_status
v$con_sysmetricv$database
v$datafile
v$event_name
v$instance
v$license
v$log
v$osstatv$parameter
v$process
v$rowcachev$session
v$sesstat
v$session_wait
v$sga
v$sql
v$sql_plan
v$sqlstats
v$sqltext
v$statname
v$sysmetric
v$sysstat
v$system_event
When you are granting access to v$
views, you must grant SELECT on the underlying objects, which are named using the v_$
format, e.g. GRANT SELECT on v_$archive_dest
.