# Oracle

Oracle Database is a relational database management system (RDBMS) developed by Oracle Corporation. It enables organizations to store, manage, and retrieve data using Structured Query Language (SQL). The database includes features for ensuring data integrity, performing backup and recovery, controlling access, and tuning performance.

Oracle Database supports both on-premises and cloud-based deployments through Oracle Cloud Infrastructure.

Through this integration, Apono helps you securely manage just-in-time, just-enough access to your Oracle Database, tables and custom roles.

***

## Prerequisites

<table data-header-hidden><thead><tr><th width="260"></th><th></th></tr></thead><tbody><tr><td><strong>Apono Connector</strong></td><td><p>On-prem connection serving as a bridge between an Oracle Database instance and Apono:</p><ul><li><a href="/pages/U4HFH35XWDo3jyqhJqgQ">AWS</a></li><li><a href="/pages/ztAsRPKJcMNxeQKE2GNB">Azure</a></li><li><a href="/pages/xPrzAcLGsoliEpPJuozp">GCP</a></li><li><a href="/pages/p5PzUV4THznqePSTYgEH">Kubernetes</a></li></ul></td></tr><tr><td><strong>Oracle Database Information</strong></td><td><p>Information for the database instance to be integrated:</p><ul><li>Hostname</li><li>Port number</li></ul></td></tr><tr><td>Admin access to Oracle</td><td>The Admin must be able to create users and manage roles in Oracle</td></tr></tbody></table>

***

## Create an Oracle Database user

You must create a user in your Oracle Database instance for the Apono connector.

Use the following steps to create a user and grant it permissions to your databases:

1. In your preferred client tool, create a new user. Be sure to set a strong password for the user.

{% hint style="warning" %}
The password must be a minimum of 9 characters and satisfy the following minimum requirements:

* 2 lowercase letters
* 2 uppercase letter
* 2 numbers (0-9)
* 2 special characters
* Cannot have 3 consecutive identical characters
* Have 4 different characters than the previous password
* Cannot contain, repeat, or reverse the user name
  {% endhint %}

```sql
CREATE USER apono_connector IDENTIFIED BY password;
ALTER USER apono_connector DEFAULT TABLESPACE users;
ALTER USER apono_connector TEMPORARY TABLESPACE temp;
ALTER USER apono_connector QUOTA UNLIMITED ON users;
```

2. Grant the user permission to connect to the Oracle Database.

```sql
GRANT CREATE SESSION TO apono_connector;
GRANT CONNECT, RESOURCE TO apono_connector;
```

3. Grant user management permissions.

```sql
GRANT CREATE USER TO apono_connector;
GRANT ALTER USER TO apono_connector;
GRANT DROP USER TO apono_connector;
GRANT ALTER SYSTEM TO apono_connector;
GRANT SELECT_CATALOG_ROLE TO apono_connector;
```

4. Grant role management permissions.

```sql
GRANT GRANT ANY ROLE TO apono_connector;
GRANT CREATE ROLE TO apono_connector;
GRANT DROP ANY ROLE TO apono_connector;
```

5. Grant table management permissions.

```sql
GRANT GRANT ANY OBJECT PRIVILEGE TO apono_connector;
```

6. Grant the user permissions to grant permissions to Oracle users.

```sql
GRANT GRANT ANY PRIVILEGE TO apono_connector;  
```

7. Using the credentials from step **1**, [create a secret](/docs/connectors-and-secrets/apono-integration-secret.md) for the database instance.

{% hint style="success" %}
You can also input the user credentials directly into the Apono UI during the [integration process](/docs/connectors-and-secrets/apono-secret-alternative.md).
{% endhint %}

You can now [integrate Oracle Database](#integrate-oracle-database).

***

## Integrate Oracle Database

<figure><img src="/files/gyXLDb37cu98Igi6jZh5" alt="" width="563"><figcaption><p>Oracle Database tile</p></figcaption></figure>

{% hint style="success" %}
You can also use the steps below to integrate with Apono using Terraform.

In step **11**, instead of clicking **Confirm**, follow the **Are you integrating with Apono using Terraform?** guidance.
{% endhint %}

Follow these steps to complete the integration:

1. On the [**Catalog**](https://app.apono.io/catalog?search=oracle) tab, click **Oracle Database**. The **Connect Integration** page appears.
2. Under **Discovery**, click one or more resource types to sync with Apono.

{% hint style="info" %}
Apono automatically discovers and syncs all the instances in the environment. After syncing, you can manage access flows to these resources.
{% endhint %}

3. Click **Next**. The **Apono connector** section expands.
4. From the dropdown menu, select a connector. Choosing a connector links Apono to all the services available on the account where the connector is located.

{% hint style="success" %}
If the desired connector is not listed, click **+ Add new connector** and follow the instructions for creating a connector ([AWS](/docs/aws-environment/apono-connector-for-aws.md), [Azure](/docs/azure-environment/apono-connector-for-azure.md), [GCP](/docs/gcp-environment/apono-connector-for-gcp.md), [Kubernetes](/docs/kubernetes-environment/apono-connector-for-kubernetes.md)).
{% endhint %}

5. Click **Next**. The **Integration Config** section expands.
6. Define the **Integration Config** settings.

   <table><thead><tr><th width="224">Setting</th><th>Description</th></tr></thead><tbody><tr><td><strong>Integration Name</strong></td><td>Unique, alphanumeric, user-friendly name used to identify this integration when constructing an access flow</td></tr><tr><td><strong>Hostname</strong></td><td>Hostname of the Oracle Database instance to connect</td></tr><tr><td><strong>Port</strong></td><td>Port value for the instance<br><br>By default, Apono sets this value to <em>1521</em>.</td></tr><tr><td><strong>Service Name</strong></td><td>Name of the service<br><br>By default, Apono sets this value to <em>ORCL</em>.</td></tr></tbody></table>
7. Click **Next**. The **Secret Store** section expands.
8. [Associate the secret or credentials](/docs/connectors-and-secrets/apono-integration-secret.md).
9. Click **Next**. The **Get more with Apono** section expands.
10. Define the **Get more with Apono** settings.

    <table><thead><tr><th width="224">Setting</th><th>Description</th></tr></thead><tbody><tr><td><strong>Credential Rotation</strong></td><td>(Optional) Number of days after which the database credentials must be rotated<br><br>Learn more about the <a href="/pages/UsMtClaCM1SlvPsARUsM">Credentials Rotation Policy</a>.</td></tr><tr><td><strong>User cleanup after access is revoked (in days)</strong></td><td><p>(Optional) Defines the number of days after access has been revoked that the user should be deleted</p><p><br>Learn more about <a href="/pages/zJwQEG15iEhbPYg9hpqp">Periodic User Cleanup &#x26; Deletion</a>.</p></td></tr><tr><td><strong>Custom Access Details</strong></td><td>(Optional) Instructions explaining how to access this integration's resources<br><br>Upon accessing an integration, a message with these instructions will be displayed to end users in the User Portal. The message may include up to <strong>400 characters</strong>.<br><br>To view the message as it appears to end users, click <strong>Preview</strong>.</td></tr><tr><td><strong>Integration Owner</strong></td><td><p>(Optional) Fallback approver if no <a href="/pages/Ey4wuziyr2BzKYQnd5am">resource owner</a> is found<br><br>Follow these steps to define one or several integration owners:</p><ol><li>From the <strong>Attribute</strong> dropdown menu, select <strong>User</strong> or <strong>Group</strong> under the relevant identity provider (IdP) platform.</li><li>From the <strong>Value</strong> dropdown menu, select one or multiple users or groups.</li></ol><p><br><strong>NOTE</strong>: When <strong>Resource Owner</strong> is defined, an <strong>Integration Owner</strong> must be defined.</p></td></tr><tr><td><strong>Resource Owner</strong></td><td><p>(Optional) Group or role responsible for managing access approvals or rejections for the resource<br><br>Follow these steps to define one or several <a href="/pages/Ey4wuziyr2BzKYQnd5am">resource owners</a>:</p><ol><li>Enter a <strong>Key name</strong>. This value is the name of the tag created in your cloud environment.</li><li>From the <strong>Attribute</strong> dropdown menu, select an attribute under the IdP platform to which the key name is associated.<br><br>Apono will use the value associated with the key (tag) to identify the resource owner. When you update the membership of the group or role in your IdP platform, this change is also reflected in Apono.</li></ol><p><br><strong>NOTE</strong>: When this setting is defined, an <strong>Integration Owner</strong> must also be defined.</p></td></tr></tbody></table>
11. Click **Confirm**.

<details>

<summary>💡Are you integrating with Apono using Terraform?</summary>

If you want to integrate with Apono using Terraform, follow these steps instead of clicking **Confirm**:

1. At the top of the screen, click **View as Code**. A modal appears with the completed Terraform configuration code.
2. Click to copy the code.
3. Make any additional edits.
4. Deploy the code in your Terraform.

Refer to [Integration Config Metadata](https://docs.apono.io/metadata-for-integration-config/integration-metadata/oracle-db) for more details about the schema definition.

</details>

Now that you have completed this integration, you can [create access flows](/docs/access-flows/access-flows.md) that grant permission to your Oracle Database resources.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.apono.io/docs/additional-integrations/databases-and-data-repositories/oracle-database.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.