The Oracle Databases page lists database information discovered for a monitored Oracle server. Use it for inventory and database context.
Workflow
- Open Databases under the Oracle server.
- Review database names, status, and related fields where available.
- Continue to Activity, Queries, Memory, or Health Checks.
How To Use Oracle Database Inventory
The Oracle Databases page provides context before deeper performance investigation. Use it to confirm which databases or services are discovered, whether expected entries are visible, and which monitored Oracle server owns the workload you are investigating.
Inventory context matters in larger estates because application teams may use different names for the server, service, database, or environment. Confirm the target before reviewing Oracle Activity or Oracle Queries. This reduces the chance of tuning or alerting against the wrong environment.
If a database is missing, check the connection, account permissions, listener/service details, and whether the monitored engine can reach the Oracle server. For broader estate management, combine this page with Enterprise View, Servers, and Reports.
Oracle Databases FAQ
Why is an expected database missing?
The connection may use a different service, permissions may limit visibility, or collection may not have completed successfully.
Is this page for tuning?
It is mainly inventory context. Use Activity, Queries, Waits, Memory, and Health Checks for tuning evidence.
Can I use it for audits?
It can support operational inventory checks, especially when combined with reports and server groups.
Next Steps From Inventory
After confirming the Oracle database inventory, open the page that matches the problem you are investigating. Use Activity for current sessions, Queries for workload cost, Waits for delay patterns, Memory for instance pressure, and Health Checks for operational risks. If inventory is incomplete, review connection details and permissions before assuming the database is unavailable.