---
title: "Integrating Decisions with External Oracle Database"
slug: "integrating-decisions-with-external-oracle-db"
tags: ["oracle"]
updated: 2024-07-16T16:08:29Z
published: 2024-07-16T16:08:29Z
canonical: "documentation.decisions.com/integrating-decisions-with-external-oracle-db"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.decisions.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrating Decisions with External Oracle Database

## Overview

**Oracle Database** is a multi-model database management system commonly used for running online transaction processing, data warehousing, and mixed database workloads. This tutorial demonstrates how to Integrate **Decisions** with Oracle Database.

---

## Oracle Integration

This example, will demonstrate how to Integrate Decisions with **Oracle Database**. Once the table has been added, [Specific tables](/v9/docs/integrate-with-database-table) and custom queries can be created in the connection folder.

1. Begin by Creating Database Connection. In the **Portal,** navigate to **System > Integrations > Databases** and click CREATE CONNECTION on the Folder Actions Panel. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2024-07-16_12h00_13.png) 2. First, define a desirable **Connection Name**.

3. Then, from the **Database Type** drop down, pick **ORACLE**.

![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2024-07-16_12h05_29.png)

Next, there are option to specify properties to connect to **Oracle Server**. Which are:

| Use TNS |
| --- |
| Database Name |
| User Name |
| Password |
| Host Name |
| Port |

4. Click TEST before saving. If the Test Status is **Success**, then click OK to save this Database Integration. 5. The database connection being created can be found in **System > Integrations > Databases** Folder.

---

## Fetch Size

In v8.12 and higher the Steps Raw SQL and Run Query [QueryName] have a configuration under CONNECTION SETTINGS called Fetch Size.

![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2023-07-17_15h12_14.png)

This setting allows for control over how many records are within a data packet. Either Step will return all records, but the driver will only fetch the number of records entered at a time. There are performance implications to how this is set. A database with 800,000 records will likely timeout if the fetch size is too low or too high. A single fetch of 800,000 records or 800,000 fetches of a single record will cause performance issues. The recommended way to determine the best performance is to start with a value of 100 and then try 500, 1000, and finally 5000.

---

Parameterized Query Characters

| Reserved Character | Reserved Word | Operator |
| --- | --- | --- |
| , | ACCUM | Accumulate |
| & | AND | And |
| ? | FUZZY | fuzzy |
| {} |  | escape characters (multiple) |
| \ |  | escape character (single) |
| () |  | grouping characters |
| [] |  | grouping characters |
| - | MINUS | MINUS |
| ; | NEAR | NEAR |
| ~ | NOT | NOT |
| \| | OR | OR |
| $ |  | stem |
| ! |  | threshold |
| > |  |  |
| * |  | weight |
| % |  | wildcard character (multiple) |
| _ |  | wildcard character (single) |

For further information on Integrations, visit the [Decisions Forum](https://community.decisions.com/categories/Integrations).