YaK User Documentation
YaK Landing PageVisit dbi-services.comContact us
YaK Release 2.1
YaK Release 2.1
  • Welcome
  • Introduction
    • YaK Core
    • YaK Components
    • Terms and definitions
  • User interface
    • Dashboard
    • Infrastructures
    • Servers
    • Components
    • Jobs
    • Configuration
    • Administration
  • YaK Demo
  • Versioning & Compatibility matrix
  • Release Notes
    • YaK components types
      • PostgreSQL
      • Oracle
  • Installation
    • System requirements
    • Install YaK Core
      • Install YaK on your own K8S cluster
      • Install YaK on Rancher Desktop
      • Uninstall Yak
  • YaK step-by-step usage
  • Configuration
    • Secrets
    • Templates
    • Provider shapes
    • Provider images
    • Artifact providers
  • Manage infrastructures
    • Declare infrastructures
    • Attach Secrets
    • Detach Secrets
  • Manage Servers
    • Declare servers
      • Basics
      • Storage
      • Attach secrets
    • Edit server configuration
    • Deploy servers
    • Destroy servers
    • Delete servers
    • Start / Stop servers
  • Manage Components
    • Artifacts requirements
    • Component types
      • PostgreSQL
        • Description
        • Pre-requisites
        • Component references
          • PostgreSQL 2.0.0
            • Standalone deployment variables
            • HA deployment variables
      • Oracle
        • Description
        • Pre-requisites
        • Component references
          • Oracle 2.0.0
            • Standalone variables
  • Use cases
    • On-Premises
    • AWS
    • Azure
    • OCI
  • Appendix
    • Create SSH Keys with PuTTYgen
    • Roles
Powered by GitBook
On this page
  • Supported OS
  • Networking requirements
  • Artifacts
  • On-prem pre-requisites
  • Ansible user
  • File systems
  1. Manage Components
  2. Component types
  3. Oracle

Pre-requisites

PreviousDescriptionNextComponent references

Last updated 22 days ago

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 )

Artifacts

The artifacts must be uploaded into your .

The paths and names of the files uploaded must match exactly the structure defined in the release notes of the component type.

See for more details.

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 :

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

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.

This user must be able to access remotely to the server with a SSH key defined in the section.

secret
component references
Artifacts requirements
artifact provider