Get started for Oracle Database clients:
If the application that connects to the Oracle Database server runs on a virtual machine or bare-metal, install OneAgent on it to get started.
If the application that connects to the Oracle Database server runs as a workload in Kubernetes or OpenShift, set up Dynatrace on Kubernetes or OpenShift.
Activate the following OneAgent features to get full tracing insight:
- Node.js Oracle DB
- PHP Oracle
Get started with Oracle Database servers:
If your Oracle Database server runs on a virtual machine or bare-metal, install OneAgent on it to get started with system performance metrics.
Activate the remote Oracle Database extension to get full insight into the Oracle Database server's health and performance combined with metrics and events. A dedicated user account is recommended for monitoring, with:
CREATE_SESSION
SELECT_CATALOG_ROLE
roles granted, or set of SELECT
permissions on the following performance views (or the corresponding GV$
views in case of RAC setups):
CDB_DATA_FILES
CDB_TABLESPACE_USAGE_METRICS
CDB_TABLESPACES
CDB_TEMP_FILES
V$ARCHIVE_DEST_STATUS
V$ASM_DISK_STAT
V$ASM_DISKGROUP_STAT
V$BACKUP_SET_DETAILS
V$CONTAINERS
V$DATABASE
V$DATAFILE
V$DATAGUARD_STATUS
V$INSTANCE
V$LIBRARYCACHE
V$LOG
V$METRIC
V$METRICGROUP
V$PARAMETER
V$PDBS
V$PGASTAT
V$RECOVERY_FILE_DEST
V$RESOURCE_LIMIT
V$RMAN_BACKUP_JOB_DETAILS
V$SESSION
V$SGASTAT
V$SQLAREA
V$SYS_TIME_MODEL
V$SYSSTAT
V$SYSTEM_EVENT
V$SYSTEM_WAIT_CLASS
V$TABLESPACE
V$TEMPFILE
Users of the Databases App who want to make use of Query Execution Plans, will also need to provide permission for the V$SQL_PLAN
, V$SESSION
, V$SQL_PLAN_STATISTICS_ALL
and V$SQL
views. See the execution plan monitoring section below for more details.
While the extension supports connecting directly to a Pluggable Database (PDB), our recommended approach is to connect your monitoring configuration to the Container Database (CDB) and allow the extension to discover all PDBs automatically. Several metrics are tailored to this approach so the results may be different if connected to the PDB instead. The monitoring account may need explicit permission over PDBs. For example, you can use this statement:
alter user <your_username> set container_data=all for sys.v_$pdbs container = current;
Finally, activate log monitoring to get full log insight.
Note:
With the TopN feature set, the extension reports the most time consuming queries on the Oracle Instance entity page, in a card called "Logs". Enabling this feature may expose sensitive data in the reported queries.