Skip to main content
Connect your Oracle Database so Myrmex can audit its hardening and compliance, check its operational health, explore its schema, and — with approval — run SQL for you. Myrmex reaches the database through the Oracle listener via a Collector on your network. Operations run live and on demand through the Integration Specialist agent — Myrmex reads only what you ask for and keeps none of your data on the Myrmex side.

​
What Myrmex Can Do

Compliance audit

Run a Security Posture audit and map findings to CIS, ISO 27001, NIST CSF, and BACEN frameworks.

Health checks

Review sessions, tablespace usage, wait events, and Data Guard status.

Explore tables

List schemas and tables so you can see what the database holds.

Describe structure

Inspect columns, types, indexes, and constraints for any table.

Sensitive-data scan

Scan tables and columns for personal or sensitive data that needs protection.

Run SQL

Execute read queries any time; write statements (DDL/DML) require your confirmation.

​
Before You Start

  • A Collector on a network that can reach the Oracle listener on its TCP port (default 1521). See Collector mode.
  • The Collector host must have the Oracle Instant Client (libclntsh) and libaio installed — the connector loads them at runtime.
  • A dedicated database user for Myrmex (create it in Step 1).
  • The connection uses the service name (e.g. XEPDB1, ORCLPDB1) as host:port/service.

​
Step 1 — Create the Credential in Oracle

Create a dedicated, least-privilege user for auditing. SELECT_CATALOG_ROLE grants read access to the V$ and DBA_* dictionary views the audit relies on.
Keep the account read-only for auditing. Grant a write-capable user only if you want the agents to run write statements (DDL/DML) through Run SQL.

​
Step 2 — Add the Integration in Myrmex

From the Directory, choose Add Integration → Oracle Database, then fill in:

​
Connect

Click Connect to validate the login and TLS settings. The database then appears under Environment → Integrations alongside your other integrations, and you can start asking the AI about it in the Workspace.

​
Notes

  • Read-only by default. Auditing, health, schema exploration, and sensitive-data scans only need the read-only user. Provide a write-capable user only if you want confirmation-gated Run SQL writes.
  • Nothing is stored. Every operation runs in real time through the Collector; results return to your Workspace and no database data is retained on the Myrmex side.
  • TLS. Use disable for plain TCP listeners; switch to require or a verifying mode once the listener is configured for TCPS.