Determine the Monitoring Scope
Pick scope before setup
Start the Oracle Database Server Wizard
Set up Oracle environment
Validate Database Connectivity
Check data source access
Validate the Deployment
Confirm monitors are live
Overview
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
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
Additional Oracle views used by GermainUX include:
V$LOGV$RECOVERY_FILE_DESTDBA_DATA_FILESDBA_TABLESPACE_USAGE_METRICSDBA_TEMP_FILESDBA_TEMP_FREE_SPACE
4. Application-Specific Database Access — Optional
GermainUX can also monitor other Oracle tables, including:- System tables
- Application tables
- Business data tables
- Operational tables
5. Start the Oracle Database Server Wizard
In Germain Workspace, navigate to:Left MenuWizardsOracle 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 WorkspaceLeft MenuData SourcesCredentials
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 WorkspaceLeft MenuData SourcesDatabaseAdd 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
9. Select the Monitoring Node & Engine
Oracle Database monitoring executes from a GermainUX Engine. Configure: Monitoring NodeThe 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
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
Next Steps
Once Oracle Database monitoring is operational, configure:- SQL Query Monitors
- KPIs
- SLAs
- Sessions and locks
- Tablespaces and datafiles
- Redo/archive logs
Show all 12
Show all 12
- Cursors
- Errors
- Custom database conditions
- Alerts
- Automation
- Dashboards and reports
Get Help
Contact GermainUX Support
The Germain Team can help you set this up.
Can't find what you need?
Search all GermainUX docs with Ctrl + K, or use the feedback buttons at the bottom of this page to tell us what is missing.
The content of this document is proprietary to GERMAIN SOFTWARE LLC.

