Both Oracle connection variants are currently available in development deployments and are not enabled by default in production. Contact CloudThinker to confirm access before setup. Self-host refers to your database, not a self-hosted deployment of CloudThinker.
Prerequisites
- Cloud: an OCI user in an IAM group whose policies allow the reads you need. Cloud Guard must already be enabled to inspect problems.
- Self-host: Oracle Database 12.1 or later, a dedicated database user, and a DBA who can grant access.
- Self-host network access: a route from CloudThinker to your database listener. Follow Reaching private services; on a self-hosted deployment, allow your CloudThinker deployment. Confirm the listener port and service name with your DBA.
Setup
Choose the Oracle connection that matches the credential you have.
- Cloud
- Self-host
1
Get an API signing key
Use a dedicated OCI user. In the OCI Console, open Profile → User settings → API Keys → Add API Key. Download the private key, then click Add.Copy the user OCID, tenancy OCID, fingerprint, and region from Configuration File Preview. Follow Oracle’s signing-key instructions if you already have a key pair.
2
Grant read access
Ask your OCI administrator to apply the policies in Required permissions to that user’s group.
3
Connect Oracle Cloud
Open More → Workspace settings → Connections, select Oracle, and click Connect. Choose Cloud, fill in its fields below, and click Connect.Success state: the connection shows a Connected status. The connection test confirms the user can list accessible compartments; it does not verify every resource permission.
Connection details
Use the labels shown in the selected tab. Complete each field below.
With Use TLS → No, query results cross the network unencrypted. Yes verifies the server certificate and its name; contact CloudThinker if you need a private certificate authority. See Oracle’s encryption limitations.
Required permissions
Ask your administrator to scope policies to the group and compartments you need. See Search permissions and Cloud Guard policies.
Ask your DBA to apply Oracle grants in the target database. Missing monitoring grants leave those sections unavailable; they do not mean the database is healthy.
Agent capabilities
Database output can be truncated. Ask for a narrower query or an SQL aggregate for exact totals; a returned sample is not a full inventory.
Verify the connection
Example prompts
Write access
Cloud cannot change infrastructure or resolve Cloud Guard problems. Self-host supports approved single-rowINSERT, UPDATE, and DELETE when the connection permits writes and the database user has the corresponding grants. CloudThinker reads the target first, names its complete primary key and proposed values, then requests approval.
Each change returns its result, before/after values, and an undo command. Undo is another write and needs its own approval. A locked row is refused.
Bulk changes, primary-key changes, tables without primary keys, Oracle-maintained schemas, DDL, TRUNCATE, DROP, GRANT, and PL/SQL are unsupported. LOB, RAW, XML, and object columns cannot be changed. Changes are refused when undo cannot safely restore the values, including unsupported types, line breaks, NUL, or undo commands over 16,000 characters.
Troubleshooting
OCI rejected the signature
OCI rejected the signature
Check that the fingerprint and private key belong to the specified OCI user and tenancy. Update the Cloud credentials together.
The listener does not know this service name
The listener does not know this service name
Ask your DBA for the service name registered with the listener. For a multitenant database, enter the pluggable database service rather than a SID.
Oracle rejected the username or password
Oracle rejected the username or password
Update the database username and password. If the account is locked or lacks CREATE SESSION, ask your DBA to correct it.
The TLS handshake failed, or Native Network Encryption is required
The TLS handshake failed, or Native Network Encryption is required
Confirm the listener’s protocol, port, and trusted certificate. If the server requires Native Network Encryption, ask your DBA for a TCPS listener and select Use TLS → Yes. Do not disable encryption to retry.
The Oracle listener did not answer
The Oracle listener did not answer
Check Host, Port, and the firewall route from CloudThinker. A local address on your computer does not identify a database CloudThinker can reach.
Security
- Least privilege — grant only the permissions the agents need for your use case; start read-only and widen later.
- Read-only by default — use read-only credentials unless you want agents to make changes through this connection.
- Rotate credentials — rotate keys and tokens on your normal schedule; CloudThinker picks up the new value when you update the connection.
- Revoke on offboarding — remove the credential at the provider when you delete a connection or a teammate leaves.
- Use a dedicated OCI signing key or database account so you can revoke CloudThinker’s access independently.
- Restrict listener access to CloudThinker and use TLS for database traffic. Keep database grants limited to the tables you intend to expose.
Related
Connections
Manage connection access and reach private services.
Approvals
Review database changes before they run.