Connect Oracle To Mini DBA


Start Here

Console

SQL Server

Azure SQL

PostgreSQL

MySQL/MariaDB

Oracle

Settings And Integrations

Legacy Documentation

Use the Oracle connection workflow to add an Oracle server to Mini DBA monitoring. Oracle monitoring uses database privileges for V$ views, GV$ views, DBA dictionary views, and multitenant container information, plus optional host OS login for CPU and drive metrics.

Mini DBA connect Oracle

Add Server Fields

In Servers, select Add Server and choose Oracle.

Field What to enter
Type Oracle
Instance / Host Oracle host name
Username Oracle monitoring user
Password Password for the monitoring user
Service Name Oracle service name, such as ORCL
Port Oracle listener port, normally 1521

The Mini DBA Engine must be able to reach the Oracle listener and service name.

What Mini DBA Monitors After Connection

With the required Oracle privileges, Mini DBA can monitor:

  • Oracle activity, sessions, waits, and query workload.
  • V$ and GV$ performance views for instance and global diagnostics.
  • DBA dictionary views for database inventory and configuration.
  • CDB and PDB information in multitenant environments when a common user has container access.
  • Oracle memory, health checks, alerts, and performance tuning evidence.
  • Host CPU and drive metrics when Host OS Login or cloud host access is configured.

Required Oracle Permissions

The Oracle permissions modal checks:

  • CREATE SESSION: essential, allows the monitoring user to connect.
  • SELECT ANY DICTIONARY: essential, grants access to V$ performance views, GV$ global views, DBA_ dictionary views, and CDB_ views for multitenant systems.
  • Common User (C##): recommended for Oracle 12c+ multitenant environments when monitoring containers.
  • Container Access: recommended for Oracle 12c+ multitenant environments.
  • DBA Role: not essential and powerful; useful for testing only.
  • OS Login or Cloud Host: optional, enables host-level metrics where available.

SQL Example: Oracle 12c+ Multitenant Common User

Run this as an Oracle administrator. Change the password first.

ALTER SESSION SET CONTAINER = CDB$ROOT;

CREATE USER C##MINIDBA_MONITOR IDENTIFIED BY "UseASecretPasswordHere" CONTAINER = ALL;

GRANT CREATE SESSION TO C##MINIDBA_MONITOR CONTAINER = ALL;
GRANT SELECT ANY DICTIONARY TO C##MINIDBA_MONITOR CONTAINER = ALL;

Use a common user when Mini DBA needs container and pluggable database visibility from a single connection.

SQL Example: Non-CDB Or Single Database User

For non-multitenant Oracle or a single database scope, use a local user:

CREATE USER MINIDBA_MONITOR IDENTIFIED BY "UseASecretPasswordHere";

GRANT CREATE SESSION TO MINIDBA_MONITOR;
GRANT SELECT ANY DICTIONARY TO MINIDBA_MONITOR;

For short-lived testing only, the modal notes that the DBA role can provide broader access:

GRANT DBA TO MINIDBA_MONITOR;

Do not use the DBA role for routine production monitoring unless your security policy explicitly permits it.

Verify Permissions In Mini DBA

After adding Oracle, open the Oracle server and use the Oracle Connectivity Permissions modal. Select Refresh to probe current privileges, common user status, container access, DBA role status, and host login status.

Use the modal when:

  • The Oracle server connects but monitoring pages are incomplete.
  • A multitenant database does not show expected PDB/container information.
  • Activity, waits, query, or health check data is missing.
  • Host CPU or drive metrics are missing.

Host OS Login And Metrics

Oracle host OS login is configured from the Oracle permissions modal after the server is added. On Linux, use SSH with password or private key authentication. On Windows, use an account with suitable local performance access.

Host OS login can add:

  • Host CPU percentage.
  • Drive capacity and free space.
  • Disk reads and writes per second where available.
  • Disk utilization and queue metrics where available.

For cloud-hosted Oracle platforms where direct OS access is unavailable, configure cloud provider credentials in Cloud Provider Settings.

For detailed setup, see Host OS Login.

Oracle Connection Troubleshooting

  • If connection fails, confirm listener host, port, service name, username, and password.
  • If the login cannot connect, grant CREATE SESSION.
  • If performance views are empty, grant SELECT ANY DICTIONARY or the equivalent approved dictionary privileges.
  • If CDB/PDB data is incomplete, use a common user with container access in Oracle 12c+ multitenant environments.
  • If host metrics are missing, configure OS Login or cloud host credentials.
  • Right-click the Oracle server in the tree and open Connectivity Log for listener, service name, authentication, timeout, dictionary privilege, and data-access errors captured by the engine.

Oracle Monitoring Permissions FAQ

Is the DBA role required?

No. The DBA role is powerful and should usually be avoided for routine monitoring. The core recommended privileges are CREATE SESSION and SELECT ANY DICTIONARY, adjusted for your security policy.

Should I use a common user?

Use a common C## user for Oracle 12c+ multitenant environments when Mini DBA should monitor containers and pluggable databases from one connection.

Does Mini DBA require Oracle Diagnostics Pack?

The basic connection and permission examples do not grant or imply license rights for Oracle optional packs. If your environment uses AWR, ASH, or Diagnostics Pack related views, confirm your Oracle licensing position separately.

Related Pages