# Pre-requisites

## Supported OS

The Oracle component type is supported on :

* Oracle Linux 8/9
* Red Hat entreprise Linux 8/9

## Networking requirements

The following port must be open on your local/enterprise/cloud firewall :

* Oracle listener port (usually 1521/tcp - see [component references](https://dbi-services.gitbook.io/yak-user-doc/manage-components/component-types/component-template/component-references))

## Artifacts

The artifacts **must** be uploaded into your [artifact provider](https://dbi-services.gitbook.io/yak-user-doc/configuration/manage-artifact-providers#upload-your-artifacts-to-the-repository).

{% hint style="warning" %}
The paths and names of the files uploaded must match exactly the structure defined in the release notes of the component type.

See [Artifacts requirements](https://dbi-services.gitbook.io/yak-user-doc/manage-components/artifacts-requirements) for more details.
{% endhint %}

## On-prem pre-requisites

Deploying an Oracle component on on-premises servers requires a few prerequisites.

### Ansible user

Ansible needs a user that can use `sudo` without password. Here is an example of how to accomplish that :

```shell
echo 'ansible        ALL=(ALL)       NOPASSWD: ALL' > /etc/sudoers.d/ansible
```

This user must be able to access remotely to the server with a SSH key defined in the [secret](https://dbi-services.gitbook.io/yak-user-doc/configuration/manage-secrets) section.

### File systems

According to the Oracle Flexible Architecture (OFA), the Oracle homes, the Oracle instance data directory and the Fast Recover Area should be on different file systems. The Oracle component type is configured to use the following directories structure by default :

* /u01 : to store the Oracle homes
* /u02 : to store the data directory of the Oracle instance
* /u03 : first location to store redo logs and control file
* /u04 : second location to store redo logs and control file
* /u90 : to store the FRA

Therefore /u01, /u02, /u03, /u04 and /u90 should, at least, be mounted on different file systems and ideally on different physical disks, whenever possible.