Deploying GermainUX Monitoring for Oracle Database: Steps and Configuration

๐Ÿ“ก Deploy Monitoring for Oracle Database

Deploy GermainUX monitoring for Oracle Database to monitor availability, performance, SQL, sessions, locks, storage, errors, backups, and application-specific database conditions.

Oracle Database monitoring is executed by the GermainUX Engine using a database connection to the monitored Oracle environment.

๐Ÿ“‹ 1. Determine the Monitoring Scope

Before deployment, determine whether GermainUX will monitor:

  • A single Oracle Database instance

  • Oracle RAC

  • Individual RAC instances

  • The RAC environment as a whole

  • Oracle system telemetry

  • Application-specific tables or data

The required database permissions depend on the selected monitoring scope.

๐Ÿ”‘ 2. Create an Oracle Monitoring Account

For basic monitoring of a single Oracle instance, GermainUX can use a regular Oracle Database account with CONNECT permissions.

More comprehensive monitoring requires SELECT permission on the Oracle system and DBA views required by the deployed monitors.

Use a dedicated monitoring account and grant only the permissions required for the selected monitoring scope.

๐Ÿ” 3. Grant Oracle Monitoring Permissions

For deeper Oracle Database monitoring, grant the monitoring account SELECT access to the required Oracle views.

Single Instance / RAC

Single Instance

RAC / Multi-Instance

V$SYSSTAT

GV$SYSSTAT

V$SYSTEM_EVENT

GV$SYSTEM_EVENT

V$SESSION

GV$SESSION

V$SQL

GV$SQL

V$SQLTEXT

GV$SQLTEXT

V$SYSTEM_PARAMETER

GV$SYSTEM_PARAMETER

V$RESOURCE_LIMIT

GV$RESOURCE_LIMIT

V$SQLSTATS

GV$SQLSTATS

V$SESSTAT

GV$SESSTAT

V$STATNAME

GV$STATNAME

V$DIAG_ALERT_EXT

GV$DIAG_ALERT_EXT

V$LOCKED_OBJECT

GV$LOCKED_OBJECT

Additional Oracle views used by GermainUX include:

  • V$LOG

  • V$RECOVERY_FILE_DEST

  • DBA_DATA_FILES

  • DBA_TABLESPACE_USAGE_METRICS

  • DBA_TEMP_FILES

  • DBA_TEMP_FREE_SPACE

Grant SELECT access only to the views required for the monitoring capabilities being deployed.

๐Ÿ—„๏ธ 4. Application-Specific Database Access โ€” Optional

GermainUX can also monitor other Oracle tables, including:

  • System tables

  • Application tables

  • Business data tables

  • Operational tables

Extend the monitoring account's permissions only when application-specific database monitoring is required.

Use least-privilege access.

๐Ÿš€ 5. Start the Oracle Database Server Wizard

In Germain Workspace, navigate to:

Left Menu โ†’ Wizards โ†’ Oracle Database Server

Start the Oracle Database Server Wizard.

Use the Wizard to configure the Oracle environment GermainUX will monitor.

๐Ÿ” 6. Add Oracle Database Credentials

Navigate to:

Germain Workspace โ†’ Left Menu โ†’ Data Sources โ†’ Credentials

Add the Oracle Database monitoring credentials.

Use the dedicated monitoring account configured for the required monitoring scope.

๐Ÿ—„๏ธ 7. Add Oracle Database as a Data Source

Navigate to:

Germain Workspace โ†’ Left Menu โ†’ Data Sources โ†’ Database โ†’ Add New Configuration

Configure the Oracle Database connection.

Associate the appropriate credentials and database connection information with the data source.

๐Ÿ” 8. Validate Database Connectivity

Verify that GermainUX can connect to Oracle Database using the configured data source.

Confirm that:

  • Credentials are valid

  • Network connectivity is available

  • Database connection succeeds

  • Required Oracle views are accessible

  • RAC views are accessible where applicable

  • Application tables are accessible where specifically configured

Resolve connectivity or permission issues before deploying additional monitors.

โš™๏ธ 9. Select the Monitoring Node & Engine

Oracle Database monitoring executes from a GermainUX Engine.

Configure:

Monitoring Node
The GermainUX Node from which the Engine operates.

Engine
The Engine that executes the Oracle monitor.

Ensure the selected Engine has network connectivity to Oracle Database.

โฑ๏ธ 10. Configure the Monitoring Schedule

Define how frequently the Oracle monitor should execute.

Choose the frequency according to:

  • Required detection speed

  • Database workload

  • Query complexity

  • Operational importance

  • Monitoring overhead

Use high-frequency monitoring selectively for conditions requiring rapid detection.

โœ… 11. Validate the Deployment

After deployment, verify:

  • Oracle connectivity

  • Monitoring-account permissions

  • Oracle system-view access

  • RAC access where applicable

  • Monitoring Node

  • Engine

  • Schedule

  • Expected Oracle telemetry

Verify deployed monitors in:

Germain State

๐Ÿ“Š Next Steps

Once Oracle Database monitoring is operational, configure:

  • SQL Query Monitors

  • KPIs

  • SLAs

  • Sessions and locks

  • Tablespaces and datafiles

  • Redo/archive logs

  • Cursors

  • Errors

  • Custom database conditions

  • Alerts

  • Automation

  • Dashboards and reports

See Configure Monitoring for Oracle Database.

โ„น๏ธ Get Help

The Germain Team can help you set this up. Contact GermainUX Support.

 

Component: Engine

Feature Availability: 2014.1 or later