> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Oracle Database on Vortex IQ

> Monitor Oracle Database health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor Oracle Database health, cost and reliability signals, and catch incidents and runaway spend early.

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [How connecting works](/integrations/connector-catalogue) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=oracle)

<CardGroup cols={5}>
  <Card title="29">
    performance signals
  </Card>

  <Card title="9">
    automated checks
  </Card>

  <Card title="0">
    prepared fixes
  </Card>

  <Card title="0">
    proven workflows
  </Card>

  <Card title="16">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup cols={2}>
      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    No changes are made without the configured approval policy. Read-only operations do not modify the connected system; schedules, access scopes, API usage and data handling remain governed by Vortex IQ controls.
  </Tab>

  <Tab title="Monitor (29)">
    ### Monitor performance

    29 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (13 signals)">
        | Signal                                 | Alert behaviour    | What it tracks                                                                                                                             |
        | -------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Active Sessions**                    | Watch only         | COUNT of V\$SESSION WHERE STATUS='ACTIVE' AND TYPE='USER'.                                                                                 |
        | **Archive Log Apply Gap**              | Merchant rule      | Data Guard only - sequence gap between primary archived and standby applied (V\$ARCHIVED\_LOG). A growing gap shrinks the recovery window. |
        | **Blocked Sessions**                   | Merchant rule      | V$SESSION WHERE BLOCKING_SESSION IS NOT NULL (corroborated by V$LOCK / DBA\_BLOCKERS). Long blocker chains stall the app.                  |
        | **Buffer Cache Hit Ratio %**           | Alert band 95 / 80 | 1 - (physical reads / (db block gets + consistent gets)) from V\$SYSSTAT. Low = SGA / buffer cache undersized, data read from disk.        |
        | **Data Guard Transport Lag (seconds)** | Merchant rule      | Data Guard only - 'transport lag' from V\$DATAGUARD\_STATS. Growing transport lag = redo not shipping (network / archiver stuck).          |
        | **Instance Uptime**                    | Watch only         | SYSDATE - STARTUP\_TIME from V\$INSTANCE. Drop = unplanned restart / instance crash.                                                       |
        | **Library Cache Hit Ratio %**          | Merchant rule      | Oracle-distinctive - GETHITRATIO from V\$LIBRARYCACHE. Low = excessive hard parses (no bind variables) thrashing the shared pool.          |
        | **Oracle Health Score**                | Merchant rule      | Composite of wait-class health, blocking, Data Guard lag, cache hit ratios, and backup recency. \<70 = investigate.                        |
        | **PGA Memory Usage %**                 | Merchant rule      | Total PGA allocated / PGA aggregate target from V\$PGASTAT. Over target = work areas spilling to temp tablespace.                          |
        | **SQL Executions / Second (live)**     | Watch only         | 'execute count' delta from V\$SYSSTAT - primary throughput signal.                                                                         |
        | **Session Saturation %**               | Alert band 70 / 90 | CURRENT\_UTILIZATION / LIMIT\_VALUE for resource\_name='sessions' from V\$RESOURCE\_LIMIT. >90% = ORA-00018 imminent.                      |
        | **Standby Apply State**                | Watch only         | Data Guard only - RECOVERY\_MODE / managed-recovery state per standby destination from V\$ARCHIVE\_DEST\_STATUS.                           |
        | **Tablespace Usage >90%**              | Alert band 70 / 90 | DBA\_TABLESPACE\_USAGE\_METRICS - a tablespace hitting its autoextend MAXSIZE stalls every write to it (ORA-01653).                        |
      </Accordion>

      <Accordion title="Protect revenue (6 signals)">
        | Signal                                                  | Alert behaviour    | What it tracks                                                                                                                                         |
        | ------------------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Blocking / Slow SQL During Checkout Window**          | Merchant rule      | Blocking / Slow SQL During Checkout Window, broken down by row.                                                                                        |
        | **Failed Logins (24h)**                                 | Merchant rule      | 'logon failures' delta from V\$SYSSTAT (or DBA\_AUDIT\_SESSION when auditing is on). Bursts = brute force or stale app credentials.                    |
        | **Oracle Load Spike vs Ecom Order Rate**                | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Oracle Product Table Row Count vs Ecom Catalog Size** | Merchant rule      | Oracle-distinctive XC - many enterprise merchants keep their product / inventory master in Oracle; row-count drift vs ecom = sync failure / oversell r |
        | **Oracle Session Saturation vs Traffic Burst**          | Alert band 70 / 90 | Oracle Session Saturation vs Traffic Burst, broken down by row.                                                                                        |
        | **Tablespace Usage %**                                  | Alert band 70 / 90 | Max used\_percent across permanent tablespaces from DBA\_TABLESPACE\_USAGE\_METRICS. >90% = autoextend exhaustion risk.                                |
      </Accordion>

      <Accordion title="Customer experience (4 signals)">
        | Signal                              | Alert behaviour     | What it tracks                                                                                                                                            |
        | ----------------------------------- | ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Avg SQL Elapsed per Exec (ms)**   | Alert band 50 / 200 | ELAPSED\_TIME / EXECUTIONS across V\$SQLSTATS. Oracle exposes per-statement averages, not native percentiles - p95/p99 derived.                           |
        | **Slow-SQL Rate %**                 | Alert band 1 / 5    | Share of executions over the slow threshold (default 200ms) from V\$SQLSTATS deltas between polls.                                                        |
        | **Top 10 SQL by Elapsed Time**      | Watch only          | Ordered by ELAPSED\_TIME / BUFFER\_GETS from V\$SQLSTATS + SQL\_TEXT. The Top SQL surface DBAs tune first.                                                |
        | **Top Wait Events (by wait class)** | Watch only          | Oracle-distinctive - V$SYSTEM_EVENT / V$ACTIVE\_SESSION\_HISTORY grouped by WAIT\_CLASS. 'db file sequential read', 'log file sync', 'enq: TX' climbing = |
      </Accordion>

      <Accordion title="Catalogue quality (3 signals)">
        | Signal                                 | Alert behaviour    | What it tracks                                                                                                                                              |
        | -------------------------------------- | ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Blocking Lock Chain >30s**           | Merchant rule      | V\$SESSION.BLOCKING\_SESSION chain sustained - row-lock contention stalling the app.                                                                        |
        | **Enqueue (Lock) Waits**               | Merchant rule      | Oracle-distinctive - 'enq: TX - row lock contention' / 'enq: TM' waits from V\$SYSTEM\_EVENT. Climbing = lock contention building.                          |
        | **Last Successful Backup (hours ago)** | Alert band 24 / 72 | MAX(COMPLETION\_TIME) for a successful full / L0 backup from V\$RMAN\_BACKUP\_JOB\_DETAILS. Autonomous / RDS: automatic backups - derive from the managed b |
      </Accordion>

      <Accordion title="Control risk and change (3 signals)">
        | Signal                                                | Alert behaviour    | What it tracks                                                                                                           |
        | ----------------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------ |
        | **Data Guard Apply Lag (seconds)**                    | Alert band 1 / 10  | Data Guard only - 'apply lag' from V\$DATAGUARD\_STATS. Gated when no standby is configured.                             |
        | **Data Guard Apply Lag >10s or Standby Not Applying** | Alert band 1 / 10  | Data Guard only - gated when no standby is configured.                                                                   |
        | **User Error Rate %**                                 | Alert band 0.1 / 1 | 'user errors' delta from V\$SYSSTAT over execute count. Spikes flag failing statements / app retry storms (ORA- errors). |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (9)">
    ### Audit risks and opportunities

    A fix status appears only where the action, inputs, approval, verification and recovery controls are mapped. Candidate remediations are never executable. Open a check for the detail.

    <AccordionGroup>
      <Accordion title="Connection pool saturation above 90%">
        **Severity** critical · **Outcome** Customer experience · **Fix status** Report only

        At 90% of the connection pool in use, the database is close to refusing new connections outright. Once it does, every part of the application that needs a fresh database connection, including new customer sessions and checkout, starts failing, not just slowing down.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CAP-001`
      </Accordion>

      <Accordion title="Disk usage above 90%">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        A database that runs out of disk stops accepting writes entirely, which for most stores means orders, inventory updates and customer records stop being saved, not just that the database gets slower. There is very little runway left at 90%.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CAP-002`
      </Accordion>

      <Accordion title="Query error rate above 1% in last 5 minutes">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 100 queries is failing right now. Depending on what those queries do, this can mean orders not saving, pages failing to load product or customer data, or background jobs silently dropping work, and a rate this high in a 5-minute window is an active incident, not background noise.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-ERR-001`
      </Accordion>

      <Accordion title="Last successful backup older than 72 hours">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        If something goes wrong with this database right now, the most recent point it can be restored to is over 3 days old. Every order, customer record and inventory change since that backup would be unrecoverable in a real incident, not just delayed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-BAK-001`
      </Accordion>

      <Accordion title="Replication lag above 10 seconds">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Anything reading from the replica, reports, dashboards, or read traffic split off the primary for capacity, is now up to 10+ seconds stale. If the primary fails while lag is this high, the replica is also that far behind on failover, which is a bigger problem than the staleness alone.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-REP-001`
      </Accordion>

      <Accordion title="Slow-query rate above 5% of total">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        More than 1 in 20 queries is landing in the slow bucket. That is frequent enough to be a pattern, not noise, and it means a meaningful share of every page load or job that touches this database is paying the slow-query cost, not just an unlucky occasional request.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-002`
      </Accordion>

      <Accordion title="p95 query latency above 200ms sustained 15m">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        One in twenty queries against this database is taking over 200ms, sustained for at least 15 minutes, not a brief spike. Any storefront page, checkout step or order sync that depends on this database inherits that slowness directly, and a sustained p95 this high is usually already visible to customer

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-001`
      </Accordion>

      <Accordion title="Buffer / cache hit rate below 80%">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 5 reads is missing the cache and going to disk instead, which is markedly slower. This shows up as everything the database does feeling incrementally heavier, rather than as one obvious failure.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CACHE-001`
      </Accordion>

      <Accordion title="Deadlocks detected (>0 in last 5 minutes)">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        A deadlock means two operations blocked each other and the database had to kill one of them; whatever that transaction was doing (placing an order, updating stock, writing a record) failed and, depending on how the application handles it, may not have been retried.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-003`
      </Accordion>
    </AccordionGroup>

    #### Build your own automated fixes

    Turn any finding into an automated fix with a Vortex IQ workflow: **over 13,000 read and write operations across more than 200 connectors** are available as building blocks, with approval, verification and rollback on every change.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **16 read** and **0 write** operations across dbatablespaceusagemetrics, v$archivedeststatus, v$archivedlogs, v$databases, v$dataguardstats, v\$instances on Oracle Database. Combine them with anything from the **over 13,000 operations across more than 200 connectors** to automate the work in your own words.

    Changes follow your configured approval policy: the target, proposed change, affected records, risk, reversibility and verification plan are shown before execution.

    [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=oracle)

    #### Ready to build your first Oracle Database workflow

    Pick a trigger, add the operations above as steps, and every step that changes data pauses for your approval. Monitoring and audits are live now and can start any workflow you build.

    <Accordion title="Browse the operations you can build with">
      | Resource                  | Read operations | Write operations |
      | ------------------------- | --------------- | ---------------- |
      | dbatablespaceusagemetrics | 1               | 0                |
      | v\$archivedeststatus      | 1               | 0                |
      | v\$archivedlogs           | 1               | 0                |
      | v\$databases              | 1               | 0                |
      | v\$dataguardstats         | 1               | 0                |
      | v\$instances              | 1               | 0                |
      | v\$librarycaches          | 1               | 0                |
      | v\$locks                  | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>