Skip to main content

Oracle Autonomous AI Database

Let agents query an Oracle Autonomous AI Database over a TLS connection, no wallet needed.

Connect it with: Connection details. Oracle Autonomous AI Database's own documentation: https://docs.oracle.com/en-us/iaas/autonomous-database-serverless/doc/connect-introduction.html.

What agents can do​

Connect Oracle Autonomous AI Database so the agents working your tasks can reach it. With it connected, they can:

  • Run SQL against your Autonomous AI Database tables to answer a question or check data.
  • Inspect schemas, tables and indexes with the data dictionary views before a migration.
  • Run a PL/SQL procedure your team already uses for a report.

Before you start​

  • An Autonomous AI Database with TLS (wallet-less) connections allowed: under Network, edit Mutual TLS (mTLS) authentication and untick Require mutual TLS so it reads Not Required. On a public endpoint Oracle requires an access control list before it allows that; add the addresses agents connect from.
  • A database user for agents, granted only the tables they need.
  • An Oracle client where the agent runs, such as the python-oracledb package in its thin mode, which needs no wallet.
  • A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.

Connect with Oracle Autonomous AI Database​

Jaah connects to Oracle Autonomous AI Database with connection details, not with a sign-in button.

Connect with an API key​

Find each value first:

  • Host: OCI console > Oracle AI Database > Autonomous AI Database > your database > Database connection; set TLS authentication to TLS and copy the host value from a connection string.
  • Port: The port value from the same TLS connection string: 1521 or 1522.
  • Service name: The service_name value from the connection string; the _low service suits most agent queries, _high runs fewer, bigger ones.
  • User: A database user created for agents (Database actions > Database users), or ADMIN.
  • Password: That database user's password.

Then add it to Jaah:

  1. In Jaah, open Secrets, select New, and pick the Oracle Autonomous AI Database card.
  2. Name the secret and choose who can use it.
  3. Fill in Host, Port, Service name, User, Password.
  4. Select Save. Jaah tests the secret straight away (see Test the connection).

Jaah encrypts what you type and never shows it again — not to you, and not to an admin.

Use your own OAuth app​

Not used: Jaah connects to Oracle Autonomous AI Database with connection details, not through an OAuth app.

Test the connection​

Select Test on the secret. Jaah checks that each value has the right shape, but does not call Oracle Autonomous AI Database: the result reads Format checked — Oracle Autonomous AI Database was not called. The first real check is when an agent uses it.

Who can use it​

Every secret has an owner, and the owner decides who can use it:

  • Personal — only your own tasks can use it. This is the default.
  • Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
  • Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.

More on owners and access: How secrets work.

Use it in an agent session​

An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:

  • org/<name> for an organization secret,
  • projects/<project>/<name> for one attached to a project,
  • me/<name> for your personal one.

A key connection hands the agent its fields: host, port, service_name, username, password.

Tell the agent in your task description which secret to use, for example “use the Oracle Autonomous AI Database secret org/oracle-adb”.

Manage, rotate or disconnect​

Everything is on the secret's page under Secrets:

  • Rotate a key: create a new key at the vendor first, then select Replace on the secret and paste it. Revoke the old key at Oracle Autonomous AI Database once the test passes. Steps: Replace or delete a secret.
  • Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at Oracle Autonomous AI Database's side too, delete the database role at Oracle Autonomous AI Database or change its password.

Limitations​

  • Jaah cannot open an Oracle connection to test: it adds no database drivers. Test checks the values' format and that the host is a public address. The first real check is the agent's first query.
  • Only TLS connections are supported. A database that requires mutual TLS (a wallet) cannot be connected here.
  • A database on a private endpoint is reachable only from its virtual cloud network, so agents elsewhere cannot use it.
  • Agents can do only what the connected Oracle Autonomous AI Database database role allows.

Troubleshooting​

Test says Port is not in the format Oracle Autonomous AI Database uses

Use the port from the TLS connection string: 1521 or 1522.

The agent's connection fails with ORA-12506 or is refused

The access control list does not allow the agent's address. Add it under Network > Access control list.

The agent's connection fails asking for a wallet (ORA-29024 or a certificate error)

Mutual TLS is still required. Set Mutual TLS (mTLS) authentication to Not Required, then copy a TLS (not mTLS) connection string.

The agent's sign-in fails with ORA-01017

The user name or password is wrong, or the user is locked. Reset it in Database actions > Database users and select Replace on the secret.

Still stuck? Select Test and read the result: it names the first value that is missing or not in the shape Oracle Autonomous AI Database uses. It does not call Oracle Autonomous AI Database, so Oracle Autonomous AI Database's own errors show only in the agent's session.

FAQ​

Is this the same as Oracle Autonomous Database?

Yes. Oracle renamed Autonomous Database to Autonomous AI Database; connections work the same way.

Why does Test say it was not called?

Oracle speaks its own database protocol, and Jaah does not run database drivers. So Test checks the format only.

Can Jaah or an admin see the key or token?

No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.

Can I connect more than one Oracle Autonomous AI Database account?

Yes. Add one secret per account, each with its own name, and tell the agent which one to use.