Reference · built on requestConnectorDatabases & warehouses

Oracle AI Database

Tables and redo-log change records from Oracle AI Database through Oracle Net drivers, ORDS REST endpoints, and LogMiner.

Request accessPricing ↗

About

Oracle AI Database is the current release of Oracle Database, following 19c and 21c. Applications reach it through Oracle Net Services: the JDBC Thin driver connects over TCP/IP to the listener, port 1521 by default, using Easy Connect naming of host, optional port, and service name. Oracle REST Data Services (ORDS) adds HTTP: AutoREST exposes a table or view at /ords/<SchemaAlias>/<ObjectAlias>/ with GET, POST, PUT, and DELETE, and REST Enabled SQL accepts statements at /ords/<schema_alias>/_/sql. LogMiner reads online and archived redo logs into V$LOGMNR_CONTENTS as SQL_REDO and SQL_UNDO text.

An operator on Fibric reads through whichever path you enable and proposes row writes through ORDS for your approval, with a receipt that includes the undo.

This is a reference listing. It documents what Fibric would read from Oracle AI Database and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Rows from tables and views the account can SELECT, over the JDBC Thin driver through Oracle Net Services
  • AutoREST collections at /ords/<SchemaAlias>/<ObjectAlias>/, paged with offset and limit and filtered with a ?q= JSON object
  • Object metadata from GET /ords/<SchemaAlias>/metadata-catalog/
  • Redo records from LogMiner: OPERATION, SCN, COMMIT_SCN, SEG_OWNER, SEG_NAME, and the reconstructed SQL_REDO and SQL_UNDO columns
  • Ad hoc query results from REST Enabled SQL at POST /ords/<schema_alias>/_/sql

Proposed actions

  • Target capability: propose a row insert with POST or an upsert with PUT to an AutoREST-enabled table
  • Target capability: propose a CSV batch load to POST /ords/<SchemaAlias>/<ObjectAlias>/batchload with batchRows and batchesPerCommit set
  • Target capability: propose calling a REST-enabled PL/SQL procedure with a JSON body

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Read the order book without opening a database session

    REST-enable the order view, read it through AutoREST with a ?q= filter on status, and let the operator page by offset and limit.

    With Order Risk, Operations Analyst

  • Answer who changed this row from redo

    When a value looks wrong, mine the redo log range for the table and show the USERNAME, SCN, and SQL_UNDO that would reverse it.

    With Root Cause, Audit Trail

  • Post a status back through REST, not a script

    Propose a PUT to the AutoREST row for a single record so the change is one HTTP call the reviewer sees before it runs.

    With Action Follow-up

Requirements

  • Oracle AI Database or Oracle Database 19c or later with a listener reachable from the connector, port 1521 by default
  • For REST reads and writes, ORDS deployed and the schema and objects enabled with ORDS.ENABLE_SCHEMA and ORDS.ENABLE_OBJECT
  • For change records, supplemental logging on (ALTER DATABASE ADD SUPPLEMENTAL LOG DATA) and an account with the LOGMINING privilege or SYSDBA
  • EXECUTE_CATALOG_ROLE for the DBMS_LOGMNR calls ADD_LOGFILE, START_LOGMNR, and END_LOGMNR
Authentication
For SQL, a database account over Oracle Net; for ORDS, first party cookie-based authentication, third party OAuth 2.0 clients registered with OAUTH.CREATE_CLIENT (client_credentials or authorization_code, tokens from /ords/{schema}/oauth/token), or JWT bearer tokens under a JWT profile.

Limits

  • Oracle documents LogMiner as a debugging tool and states it is not intended for third party replication of data in a production environment
  • LogMiner writes no SQL_REDO or SQL_UNDO for temporary tables and does not support LONG, LONG RAW, CLOB, BLOB, NCLOB, ADT, or COLLECTION values in MINE_VALUE
  • The continuous_mine option of DBMS_LOGMNR.START_LOGMNR was desupported in Oracle Database 19c, so redo is mined in explicit log ranges
  • AutoREST fixes the shape of objects, paging, and filters; custom behavior needs a REST module with templates and handlers

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Oracle AI Database ↗

Questions and answers

Do I need ORDS to use this connector?
No. SQL reads go through Oracle Net Services with the JDBC Thin driver, which needs only the listener. ORDS adds HTTP paths: AutoREST tables, REST Enabled SQL, and OAuth 2.0 clients. Use it when you would rather expose an alias than a database account.
What does LogMiner need before it can show changes?
Supplemental logging, enabled with ALTER DATABASE ADD SUPPLEMENTAL LOG DATA and checked in V$DATABASE.SUPPLEMENTAL_LOG_DATA_MIN. The account needs the LOGMINING privilege or SYSDBA to query V$LOGMNR_CONTENTS, plus a dictionary source such as DICT_FROM_ONLINE_CATALOG.
How does an ORDS client authenticate for server-to-server calls?
Register a client with OAUTH.CREATE_CLIENT and p_grant_type => 'client_credentials', then exchange the client id and secret at /ords/{schema}/oauth/token. Oracle notes this endpoint is for server-to-server use and that CORS is disabled on it.
Ask about Oracle AI Database

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Oracle AI Database through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy