> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/concepts/resources/depot/supported-sources/oracle.md).

# Oracle

To create an Oracle Depot you must have the following details:

## Pre-requisites specific to DataOS

To create a Depot, you need the Data Admin role. Contact the DataOS Operator or Tenant Admin to get it.

Run this command to see your assigned roles.

```bash
dataos-ctl user get
#Expected Output: 
time="2026-03-30T17:49:18+05:30" level=info msg="😃 user get..."
time="2026-03-30T17:49:19+05:30" level=info msg="😃 user get...complete"

     NAME     │        ID         │  TYPE  │        EMAIL         │                  TAGS
──────────────┼───────────────────┼────────┼──────────────────────┼────────────────────────────────────────
 I Am Groot   │ iamgroottmdcio    │ person │ iam.groot@tmdc.io    │ roles:id:ct-onboarding-data-developer,
              │                   │        │                      │ roles:id:data-dev,
              │                   │        │                      │ roles:id:system-dev,
              │                   │        │                      │ roles:id:user,
              │                   │        │                      │ users:id:iamgroottmdcio

```

## Pre-requisites specific to the source system

* **URL of the Oracle account**: The URL or hostname of the Oracle database server where the database is hosted. This is typically provided by the database administrator and may include additional connection parameters.
* **Username**: The login username used to authenticate the connection to the Oracle database. This username is created by the database administrator and must have the appropriate permissions to access the desired database.
* **Password**: The password associated with the provided username for authentication. This is required to establish a secure connection and is typically set by the administrator or the user during account creation.
* **Database Name**: The name of the Oracle database you want to connect to. This is used to specify the target database within the Oracle server and is provided by the database administrator.
* **Database Schema**: The schema in the Oracle database where the desired tables are located. Schemas are logical containers for database objects like tables, views, and indexes, and this information helps you access the correct data.

## Create an Oracle Depot

A Depot of type `ORACLE` connects to an Oracle database and reads from its tables. One Depot covers all schemas within the configured service. Create multiple Depots for multiple Oracle servers or databases. To create a Depot of type `ORACLE`, follow these steps:

### **Step 1: Create a Secret for securing Oracle credentials**

Create a Secret Resource using the [Oracle](/concepts/resources/secret/data-sources/oracle.md) guide.

### **Step 2: Create a Oracle Depot manifest file**

Create a manifest file for the Oracle Depot.

{% tabs %}
{% tab title="Manifest file" %}

```yaml
name: ${{oracle-name}}
version: v2alpha
type: depot
tags:
  - Oracle
  - depot
  - rdbms
description: "Oracle relational database depot for enterprise data storage and querying"
spec:
  type: oracle
  spec:
    subprotocol: "oracle:thin"
    host: ${{oracle-host}}
    port: 1521
    service: ${{oracle-database}}
  secrets:
    - id: "${{tenant-id}}:${{oracle-secret-name}}"
      purpose: scan
    - id: "${{tenant-id}}:${{oracle-secret-name}}"
      purpose: query
    - id: "${{tenant-id}}:${{oracle-secret-name}}"
      purpose: rw
```

{% endtab %}

{% tab title="Example" %}

```yaml
name: ${{oracle-name}}
version: v2alpha
type: depot
tags:
  - Oracle
  - depot
  - rdbms
description: "Oracle relational database depot for enterprise data storage and querying"
spec:
  type: oracle
  spec:
    subprotocol: "oracle:thin"
    host: ${{oracle-host}}
    port: 1521
    service: ${{oracle-database}}
  secrets:
    - id: "${{tenant-id}}:${{oracle-secret-name}}"
      purpose: scan
    - id: "${{tenant-id}}:${{oracle-secret-name}}"
      purpose: query
    - id: "${{tenant-id}}:${{oracle-secret-name}}"
      purpose: rw
```

{% endtab %}
{% endtabs %}

### **Step 3: Apply the Depot manifest file**

Apply the manifest with the DataOS CLI:

```bash
dataos-ctl resource apply -f ${{manifest-file-path}}
```

## Verify the Depot creation

Verify the Depot in two ways:

* List Depots where you are the owner:

  ```bash
  dataos-ctl resource get -t depot
  ```
* List all Depots in the current Tenant:

  ```bash
  dataos-ctl resource get -t depot -a
  ```

## Delete a Depot

{% hint style="warning" %}
Best practice: Delete Resources that are no longer in use to save time and reduce costs.
{% endhint %}

To delete a Depot, use the DataOS CLI:

{% tabs %}
{% tab title="Command 1" %}

```bash
dataos-ctl resource delete -t depot -n ${{name}}
```

{% endtab %}

{% tab title="Command 2 " %}

```bash
dataos-ctl resource delete -i "${{resource-name}}|v2alpha|depot"
```

{% endtab %}

{% tab title="Command 3" %}

```bash
dataos-ctl resource delete -f ${{manifest-file-path}}
```

{% endtab %}
{% endtabs %}

Specify the Resource type and Depot name in the `delete` command.

**Example:**

{% tabs %}
{% tab title="Command 1" %}

```bash
dataos-ctl resource delete -t depot -n testdepot
#output
time="2026-03-25T15:53:55+05:30" level=info msg="🗑 delete..."
time="2026-03-25T15:53:55+05:30" level=info msg="🗑 deleting testdepot:v2alpha:depot..."
time="2026-03-25T15:53:56+05:30" level=info msg="🗑 deleting testdepot:v2alpha:depot...deleted"
time="2026-03-25T15:53:56+05:30" level=info msg="🗑 delete...complete"
time="2026-03-25T15:53:56+05:30" level=info msg="🗑 delete...complete"
```

{% endtab %}

{% tab title="Command 2" %}

```bash
dataos-ctl resource delete -i "testdepot|v2alpha|depot"
#output
time="2026-03-25T15:55:37+05:30" level=info msg="🗑 delete..."
time="2026-03-25T15:55:37+05:30" level=info msg="🗑 deleting testdepot:v2alpha:depot..."
time="2026-03-25T15:55:37+05:30" level=info msg="🗑 deleting testdepot:v2alpha:depot...deleted"
time="2026-03-25T15:55:37+05:30" level=info msg="🗑 delete...complete"
```

{% endtab %}

{% tab title="Command 3" %}

```bash
dataos-ctl resource delete -f /path/to/depot.yaml
#output
time="2026-03-25T15:53:55+05:30" level=info msg="🗑 delete..."
time="2026-03-25T15:53:55+05:30" level=info msg="🗑 deleting testdepot:v2alpha:depot..."
time="2026-03-25T15:53:56+05:30" level=info msg="🗑 deleting testdepot:v2alpha:depot...deleted"
time="2026-03-25T15:53:56+05:30" level=info msg="🗑 delete...complete"
```

{% endtab %}
{% endtabs %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://v2.dataos.info/concepts/resources/depot/supported-sources/oracle.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.