SQL and relational

Oracle

Oracle 19c+ uses a bundled managed driver for live SQL and PL/SQL, schema and package inspection, DBMS output, plans, and guarded writes.

Available12 minDesktop

Prerequisites

  • Install the current DataPad++ desktop pre-release on Windows, macOS, or Linux.
  • Have the endpoint, database file, or cloud account details for a Oracle datastore you are authorized to use. Start with least-privileged, read-only access.
  • Keep an independent backup before enabling edits, administration, restore, or transfer execution.

Connect and run a safe query

  1. 1

    Create the connection

    Open Library, choose Create connection, and select Oracle and a supported Connection method tab.

  2. 2

    Test and save

    Complete the applicable fields and enable Read-only connection. Test connection when available; new local files and pending secondary credential changes must be saved first. Review runtime limitations and warnings.

    Oracle connection setup. The Oracle connection dialog with supported method tabs and illustrative, non-secret settings. Expand optional sections and review runtime limitations before saving.
    Oracle connection setup. The Oracle connection dialog with supported method tabs and illustrative, non-secret settings. Expand optional sections and review runtime limitations before saving. Open full size
  3. 3

    Open the native explorer

    Use Save Connection, or Create Database and Save Connection for a new local file, then open the Oracle Explorer where supported.

  4. 4

    Select a scope

    Select the database / schema scope that should be attached to the new tab.

  5. 5

    Run a bounded read

    Open a query tab, paste the bounded read-only sample below, and choose Run or press Ctrl/Cmd+Enter.

    Oracle native workflow. A representative Oracle explorer and bounded read-only workflow. Replace the example objects with names from your datastore.
    Oracle native workflow. A representative Oracle explorer and bounded read-only workflow. Replace the example objects with names from your datastore. Open full size
  6. 6

    Inspect the result

    Inspect Results, Messages, History, and Details; dock the panel on the bottom or right as needed.

  7. 7

    Export when needed

    Export only the required rows after reviewing format, destination, and redaction options.

  8. 8

    Open diagnostics or transfers

    Open Diagnostics or Transfers from the drawer/status bar and treat disabled reasons as capability boundaries, not transient errors.

Connection fields

FieldRequiredPurposeSafe example
NameYesA clear profile name, without credentials.Oracle development
Connection methodYesChoose a supported tab. The fields below apply only to the selected method and deployment.Connection fields / Connection string
EnvironmentNoAttach the intended variable and safety context.Local development
Read-only connectionNoEnable for initial exploration. This does not make pre-release software safe for production workloads.Enabled
Host / PortNoEndpoint for a fields-based connection. Follow the selected deployment and runtime limitations; MongoDB SRV does not use an explicit port.localhost / engine default
Database / default scopeNoInitial scope for browsing, where supported.catalog
Complete connection stringYesRequired in Connection string mode only. Saved unchanged as one vault secret with Save Connection. Blank keeps an existing stored value.Paste your complete provider string; do not share it
UsernameNoAuthentication identity for the selected method.catalog_reader
PasswordNoRequired only when the chosen authentication needs it. Save Connection stores changes; blank preserves an existing value, and Reveal… explicitly discloses it.Stored in the desktop OS vault
Connect usingNoGeneral. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.service-name / sid / tns-alias / easy-connect / tcps / cloud-wallet
Service nameNoGeneral. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default
SIDNoGeneral. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default
TNS aliasNoGeneral. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default
Easy Connect descriptorNoGeneral. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default
RuntimeNoAdvanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.managed / sqlplus / contract
RoleNoAuthentication. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.default / sysdba / sysoper / sysbackup / sysdg / syskm / sysrac
Proxy userNoAuthentication. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default
Wallet folderNoTLS & certificates. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default
TNS admin folderNoTLS & certificates. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default
Wallet passwordNoAuthentication. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Saved with the connection
SQL*Plus executableNoAdvanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default
Client identifierNoAdvanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default
Application nameNoAdvanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default
EditionNoAdvanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default
Statement cache sizeNoAdvanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default
Fetch sizeNoAdvanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default
Connect timeout (ms)NoAdvanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default
Request timeout (ms)NoAdvanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default

Run the sample query

Oracle read-only example
SELECT customer_id, customer_name, status
FROM customers
ORDER BY customer_id
FETCH FIRST 25 ROWS ONLY

Explore and inspect

  • Browse live schemas, tables and columns, views, materialized views, packages and routines, types, sequences, synonyms, links, constraints, indexes, triggers, storage, security, performance, and permission-aware dictionary details.
  • Inspect table, JSON, raw status, affected-row, multiple-result, DBMS output, DBMS_XPLAN, profile, package metadata, and edit-evidence views.

Diagnose, administer, and transfer

  • Review DBMS_XPLAN, SQL Monitor availability, PL/SQL compile diagnostics, storage posture, security posture, restricted dictionary warnings, and row identity checks.
  • Preview schema/package operations, storage and security reviews, import/export plans, RMAN boundary plans, and restore-sensitive workflows.
  • Import — Live. Oracle streams CSV through the bundled managed driver and imports into an existing empty table with array binding and exact column validation. Formats: CSV (portable-lossy). Destinations: local file.
  • Export — Live. Oracle streams CSV through the bundled managed driver and imports into an existing empty table with array binding and exact column validation. Formats: CSV (portable-lossy). Destinations: local file.
  • Backup — Live. Oracle uses DBMS_DATAPUMP for table and schema archives. Formats: Oracle Data Pump (native). Destinations: server path.
  • Restore — Live. Oracle uses DBMS_DATAPUMP for table and schema archives. Formats: Oracle Data Pump (native). Destinations: server path.
Transfers Center. Transfers Center shows a failed example transfer with its warning count, failure detail, retry control, and dismiss action.
Transfers Center. Transfers Center shows a failed example transfer with its warning count, failure detail, retry control, and dismiss action. Open full size

Capabilities and availability

CapabilityStatusNotes
Native explorerAvailableBrowse live schemas, tables and columns, views, materialized views, packages and routines, types, sequences, synonyms, links, constraints, indexes, triggers, storage, security, performance, and permission-aware dictionary details.
Read queriesAvailableRun SQL, DML, DDL, MERGE, procedure calls, transaction control, and multi-statement PL/SQL scripts, with bounded reads, DBMS output, explain, and profile results.
Inline editingGuardedRequires key evidence, a writable profile, and environment confirmation.
Diagnostics / administrationGuardedPreview schema/package operations, storage and security reviews, import/export plans, RMAN boundary plans, and restore-sensitive workflows.
Import / export / transferGuardedAvailability follows the authoritative runtime transfer manifest and shows a disabled reason when execution is not implemented.

Safety and limitations

Troubleshooting

SymptomResolution
Test connection fails or times outVerify endpoint, port, TLS mode, proxy settings, service health, firewall rules, and network access. Keep the profile unsaved until the test explains the failure.
Explorer branches are empty or disabledConfirm the selected database / schema, refresh the branch, and grant the minimum metadata permissions described in the connection warning.
Run, edit, admin, or transfer is disabledRead the visible disabled reason. Select a compatible target, turn off read-only only when authorized, or use the documented preview/export fallback.
The sample query fails or returns different columnsReplace the example names with objects from your Oracle datastore, confirm the selected database / schema, and keep the query bounded while you validate the result.