Linux Oracle

This document describes the minimum configuration requirements to install the application and/or data servers on a Linux server with an Oracle 19c or 12c database.

Please note that any fresh installation should be performed with Oracle 19c as support for Oracle 12c could be removed in the future (from Oracle and Sage).

On installations where Oracle RDBMS and Sage X3 runtime components are in the same host, Oracle 19c is the only version where the connection from Sage X3 runtime and database can leverage the BEQ protocol.

If using Oracle RDBMS 12c, the connection must be done through embedded Oracle Instant Client 19 and listener even in a single-server configuration.

Category Configuration requirements
Operating system
  • Red Hat Enterprise Linux Server x64 release 8 (with mandatory compat-openssl10 and libnsl.x86_64 packages).
  • Oracle Enterprise Linux 8.
Server
  • Industry-standard server or virtual machine in a certified virtualization platform/operating system configuration.
  • Processors:
    • Intel® CPUs:
      • Minimal models: Intel® Xeon® E5 v4, E7 v4
      • Recommended: Latest (third generation) or previous generation (second and first) Intel® Xeon® Scalable Processors, Gold or Platinum variants
    • AMD™ CPUs:
      • Opteron™ family is very slow on integer computation and should not be used at all.
      • EPYC™ gen.1 (7001 series) are behind equivalent Intel® Xeon® CPUs of the same generation. Their use is discouraged.
      • EPYC™ gen.2 (7002 series) can be used. Its performance is similar to equivalent Intel® Xeon® Scalable processors.
    • Processor clock frequency:
      • Avoid low energy processors with low clock frequency. This will give poor results.
      • The base clock frequency should be ≥ 2.4 GHz.
      • For heavy single-threaded loads, consider using a processor with a 2.8 GHz or higher base clock speed.
  • Standard needs for the Sage X3 runtime (no database, and no Syracuse in the same VM), with 2.4 GHz Intel® Xeon®:
    • 2 logical cores for the first 40 Sage X3 sessions.
    • 1 additional logical core for each additional 40 Sage X3 sessions.
  • Add at least two logical cores for Oracle RDBMS if it is on the same host as Sage X3 application or runtime components.
RAM
  • 2 GB minimum for Linux operating system, 4 GB minimum (more is better) per Oracle database instance if hosted in the same server as Sage X3 application or runtime components.
  • Generally, the RAM usage per X3 session is under 100 MB, but it can be higher in the case of non-standard settings of maxmem.
Disk space
  • For Oracle 19c RDBMS software (binaries):
    • 8 GB for 19.3.0.0. SE2
    • Can be more for Enterprise Edition
    • Add free space for installing updates/patches
  • For Oracle 12c RDBMS software (binaries):
    • 5 GB for 12.1.0.2 SE2
    • Can be more for 12.2.0.1 and/or Enterprise Edition
    • Add free space for installing updates/patches
  • For Sage X3 (reference folder and software): 10 GB.
  • For the SEED demonstration folder (SEED): 10 GB.
  • For the production folder:
    • Depends on the amount of data in the folder. It will never be less than 10 or 20 GB.
    • A sizing tool is available in Sage X3 to estimate the size requirements.
Database software
  • Oracle 19c (19.3.0.0 or later):
    • Should be the version used for any new installation or in upgrade projects.
    • Editions: SE2 (Standard Edition 2) or EE (Enterprise Edition).
  • Oracle 12cR2(12.2.0.1):
    • Is End of Life or near and should not be used for new installations.
    • Editions: SE2 (Standard Edition 2) or EE (Enterprise Edition).
  • Oracle 12cR1(12.1.0.2):
    • Is End of Life and should absolutely not be used for new installations.
    • Editions: SE2 (Standard Edition 2) or EE (Enterprise Edition).
  • It is necessary to set up an Oracle TNS listener (for Print Server connectivity at least).
  • Since recent Sage X3 Print Server versions embed Oracle 19c ODBC, there is no need to deprecate security in sqlnet.ora to allow legacy DataDirect ODBC drivers connection.
Software prerequisites for Sage X3 components
  • If you want to perform the Sage X3 components installation in graphical mode on Linux, make sure you have installed the minimal set of X11 components.
    To check if X11 components are operational, install the xclock X11 application (yum install xclock) and try to use it.
    Otherwise, you can launch the Sage X3 components EZpack installer in character mode by adding the -console option.
  • Ksh (Korn Shell) should be present on application and runtime servers, as it is used for some scripts during installation and later operations.
    Perform a yum install ksh before configuring the Sage X3 solution with the console.
  • SELINUX should be set to Permissive on the application and runtime servers.
  • Pay attention to firewall settings on Sage X3 servers.
  • A JDK or Java Runtime Environment (version 8) must be installed before any Sage X3 component installation.
    • You can use the OpenJDK packages from Red Hat or Oracle Linux standard distribution medium/repositories.
    • Use yum install java-1.8.0-openjdk.
  • The SAFE X3 Adxadmin administration engine component must be installed before installing Sage X3 application and runtime components.
  • The latest SAFE X3 management console should be used to configure the Sage X3 solution. Use at least the version provided in the ISO of the installed release.
  • For more details regarding Powershell, consult the pre-requisites documentation.
Mail server
  • The workflow engine used in classic mode requires an SMTP server or gateway accessible from all Sage X3 runtime servers.