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

# FAQ

> Common questions about the Oracle connector.

<script type="application/ld+json">
  {`{
            "@context": "https://schema.org",
            "@type": "TechArticle",
            "headline": "Oracle FAQ",
            "description": "Common questions about the Oracle connector.",
            "url": "https://docs.dqlabs.ai/sources/oracle/faq",
            "publisher": {
              "@type": "Organization",
              "name": "DQLabs Inc",
              "logo": "https://media.brand.dev/332adc35-5bc4-4d2b-bf78-256aa4a5e414.svg"
            }
            }`}
</script>

## Connector Lifecycle

<AccordionGroup>
  <Accordion title="What happens if I delete a connector?">
    Deleting a source triggers an approval workflow based on your organization's settings. Once approved, the source and all associated metadata are permanently deleted. The deletion cannot be undone after approval.
  </Accordion>

  <Accordion title="What happens to existing data and alerts if a connector is paused or disconnected?">
    Existing metadata, quality scores, and alerts are retained while the connector is inactive. No new data is collected until the connector is re-enabled. If the connector is permanently deleted (after approval), all associated data is removed.
  </Accordion>

  <Accordion title="How long does Prizm retain historical data?">
    The default data retention window for time-series observability data, quality score history, and query usage history is **90 days**.
  </Accordion>

  <Accordion title="How does manual re-sync work alongside scheduled jobs?">
    Triggering a manual scan runs the job immediately without affecting the configured schedule. Any schedule update overrides the existing schedule and applies to all future executions.
  </Accordion>
</AccordionGroup>

## Oracle-Specific

<AccordionGroup>
  <Accordion title="What Oracle versions are supported?">
    Oracle 19c and higher, across on-premises, self-hosted VM, and Oracle Cloud Infrastructure (OCI) deployments, including Autonomous Database.
  </Accordion>

  <Accordion title="Do I need the Diagnostics Pack license?">
    No. The Diagnostics Pack (AWR, `DBA_HIST_SQLSTAT`, `V$ACTIVE_SESSION_HISTORY`) extends historical usage and performance data beyond the in-memory shared pool's retention, but it isn't required. Without it, the connector operates on `V$SQL`/`V$SQLAREA`/`V$SESSION` alone and shows an advisory in the Prizm integration health dashboard.
  </Accordion>

  <Accordion title="Why does my row count look wrong?">
    `ALL_TABLES.NUM_ROWS` reflects the last time Oracle statistics were gathered (`DBMS_STATS`), not the live row count. If `LAST_ANALYZED` is more than 7 days old, Prizm automatically falls back to `DBA_SEGMENTS` block-based sizing instead of the stale `NUM_ROWS` value.
  </Accordion>

  <Accordion title="Does the connector support PL/SQL package bodies?">
    Package procedures and functions are catalogued and represented as distinct lineage nodes, with the parent package name preserved as context. `ALL_SOURCE` is used as a fallback for dynamic SQL references that `ALL_DEPENDENCIES` doesn't capture. PL/SQL execution itself is out of scope for this release.
  </Accordion>

  <Accordion title="Does lineage follow database links or synonyms?">
    Synonym-based indirection (`ALL_SYNONYMS`) is resolved transparently — lineage edges point to the underlying object, not the synonym. Database link lineage (`DBA_DB_LINKS`) is captured as a labeled cross-database edge, but Prizm does not crawl the remote database unless a separate connector is configured for it.
  </Accordion>

  <Accordion title="Are quality rules created automatically?">
    Yes. NOT NULL, primary/unique key, foreign key, and simple CHECK constraints already enabled in Oracle are auto-generated as activated quality rules on first catalog crawl. You can edit or disable the Prizm-side rule at any time without affecting the underlying Oracle constraint.
  </Accordion>
</AccordionGroup>

***

<CardGroup cols={2}>
  <Card title="Troubleshooting" icon="wrench" href="/help/troubleshooting">
    For connection errors, permission issues, and performance problems.
  </Card>

  <Card title="Glossary" icon="circle-question" href="/help/glossary">
    For definitions of terms used in this FAQ.
  </Card>
</CardGroup>