Supported platforms

• 1: OpenText Analytics Database server and Management Console
• 2: Client drivers support
• 2.1: Perl driver requirements
• 2.2: Python driver requirements
• 3: OpenText Analytics Database SDKs
• 4: FIPS 140-2 supported platforms
• 5: Eon on-premises storage
• 6: OpenText Analytics Database on Amazon Web Services
• 7: Containerized environments
• 8: Virtualized environments
• 9: Hadoop integrations
• 10: Apache Kafka integrations
• 11: Apache Spark integrations
• 12: Linux volume manager (LVM)
• 13: End-of-support notices

1 - OpenText Analytics Database server and Management Console

Operating systems and versions

OpenText™ Analytics Database 25.3.x runs on the following 64-bit operating systems and versions on x86_x64 and AArch64 architecture.

In general, OpenText provides support for the database, not its host operating system, hardware, or other environmental elements. However, OpenText makes an effort to ensure the success of its customers on recent versions of the following popular operating systems for the x86_64 and AArch64 architecture.

When there are multiple minor versions supported for a major operating system release, it is recommended that you run the database on the latest minor version listed in the supported versions list. For example, if you run the database on a Red Hat Enterprise Linux 8.x release, it is recommended that you upgrade to or runn the latest supported RHEL 8.x release.

Recommended storage format types

Choose the storage format type based on deployment requirements. Vertica recommends the following storage format types where applicable:

• ext3

• ext4

• NFS for backup

• XFS

• Amazon S3 Standard, Azure Blob Storage, or Google Cloud Storage for communal storage and related backup tasks when running in Eon Mode

The storage format type at your backup and temporary directory locations must support fcntl lockf (POSIX) file locking.

You can view the file systems in use on your nodes by querying the system table STORAGE_USAGE.

While users have successfully deployed other file systems, we cannot guarantee desired outcomes on all storage format types. In certain support situations, you may be asked to migrate to a recommended storage format type to help with troubleshooting or to fix an issue.

The database supports Linux Volume Manager (LVM) on all supported operating systems. Your LVM version must be 2.02.66 or later and must include device-mapper version 1.02.48 or later. For information on requirements and restrictions, see the section, Database Support for LVM.

Network address family support

The database server supports IPv4 and IPv6 network addresses for both internal and external communications. The database cluster uses IPv4 by for internal communications by default. You can choose to have the cluster use IPv6 for its internal communications when you install the database and create the cluster.

Vertica supports using IPv6 to identify nodes in the database cluster. However, AWS DNS resolution does not support IPv6. To have a cluster in AWS that uses IPv6, use the IPv6 IP addresses instead of using host names when installing Vertica and forming the cluster.

Currently, the database does not support using IPv6 on Google Cloud Platform or Microsoft Azure.

The MC currently does not support IPv6. If your database uses IPv6 for internal communications, MC will not be able to connect to or manage the database. MC must communicate with the database cluster using its own internal network addresses.

Supported browsers for Management Console

The Management Console 25.3.x is supported on the following web browsers:

• Chrome
• Firefox
• Microsoft Edge

Database Server and Management Console compatibility

The Management Console (MC) version 25.3.x is compatible with all supported database server versions.

2 - Client drivers support

OpenText™ Analytics Database provides JDBC, ODBC, OLE DB, Python, vsql, and ADO.NET client drivers. Download the latest drivers from Client Drivers. Choose from drivers for the following platforms:

To view a list of driver and server version compatibility, see Client driver and server version compatibility.

ADO.NET Driver

The ADO.NET and OLE DB drivers are supported on the following platforms:

OLE DB Driver

The ADO.NET and OLE DB drivers are supported on the following platforms:

JDBC driver

All non-FIPS JDBC drivers are supported on any Java 8-compliant platform or later (Java 8 is the minimum).

ODBC driver

The database provides both 32-bit and 64-bit ODBC drivers. Database version 25.3.x ODBC drivers are supported on the following platforms:

vsql client

The vsql client is included in all client packages. It is not available as a separate download. The vsql client is supported on the following platforms:

2.1 - Perl driver requirements

To use Perl with OpenText™ Analytics Database, you must install the Perl driver modules (DBI and DBD::ODBC) and an ODBC driver on the machine where Perl is installed. The following table lists the Perl versions supported 25.3.x.

Later versions of Perl (5.10 and above), DBI, and DBD::ODBC might also work.

2.2 - Python driver requirements

To use Python with OpenText™ Analytics Database, you must install either:

• The vertica-python client.

• The pyodbc module.

For details, see Installing Python client drivers.

The following table lists compatible versions of Python, the Python drivers, and ODBC.

3 - OpenText Analytics Database SDKs

This section describes software requirements for running User Defined Extensions (UDxs) developed using the OpenText™ Analytics Database SDKs.

C++ SDK

The database cluster does not have any special requirements for running UDxs written in C++.

Java SDK

Your database cluster must have a Java runtime installed to run UDxs developed using the Java SDK. The following Java Runtime Environments (JREs) have been tested with this version of the Java SDK:

• Oracle Java Platform Standard Edition 6 (version number 1.6)

• Oracle Java Platform Standard Edition 7 (version number 1.7)

• Oracle Java Platform Standard Edition 8 (version number 1.8)

• OpenJDK 6 (version number 1.6)

• OpenJDK 7 (version number 1.7)

• OpenJDK 8 (version number 1.8)

Python SDK

The Python SDK does not require any additional configuration or header files.

R language pack

The R Language Pack provides version 3.5 of the R runtime and associated libraries. You install the R Language Pack on the database server.

4 - FIPS 140-2 supported platforms

OpenText™ Analytics Database uses a certified OpenSSL FIPS 140-2 cryptographic module to meet the security standards set by the National Institute of Standards and Technology (NIST) for Federal Agencies in the United States or other countries. The database links with the version of OpenSSL on the system to perform cryptographic operations at run time. When operating in FIPS mode, the database relies on the operating system's FIPS configuration to ensure a FIPS-certified version of OpenSSL is present in the environment.

OpenText supports running the database in FIPS mode on Red Hat Enterprise Linux versions 9.2 and higher with FIPS-compliant versions of OpenSSL 3.0. OpenSSL version 1.1.1k is not supported. For information on downloading FIPS-compliant libraries, see the OpenSSL documentation.

FIPS-enabled database requires the following:

• A user-generated certificate signed by an approved Certificate Authority.

• TLS 1.2 to support the server-client connection for a FIPS-enabled system.

Supported drivers

The database supports the following client drivers for FIPS-compliance:

• vsql

• ODBC

• JDBC

For more information see Federal information processing standard.

5 - Eon on-premises storage

OpenText™ Analytics Database supports the following storage platforms for the Eon Mode running on-premises.

Hewlett Packard Enterprises (HPE)

The database supports Hewlett Packard Enterprise (HPE) Alletra Storage MP X10000 for databases running in Eon Mode on-premises:

• HPE Alletra Storage MP X10000
• HPE Data Fabric

Pure Storage FlashBlade

The database supports communal storage on Pure Storage FlashBlade version 3.0.0 and later. See Create an Eon Mode database on-premises with FlashBlade for more information.

The database does not support Management Console or admintools to administer data in Pure Storage hardware.

For information about configuring Pure Storage, see support.purestorage.com.

MinIO

The database supports communal storage on MinIO version 2018-12-27T18:33:08Z and later. See Create an Eon Mode database on-premises with MinIO for more information.

The database does not support Management Console or admintools to administer data in MinIO.

See the MinIO website for more information about MinIO.

HDFS

The database supports communal storage on HDFS when accessed through WebHDFS. For more information, see Create an Eon Mode database on-premises with HDFS.

For HDFS, the following are not supported:

• The MapR distribution of HDFS, which is accessed through an NFS mount point and not through WebHDFS.

• Using the Management Console or admintools to administer data in HDFS.

• Cloudera (CDH) versions 5.x in Eon Mode.

• The copycluster vbr backup and restore utility for communal storage on HDFS.

CEPH

The database supports communal storage on CEPH, an open source distributed storage platform. CEPH spreads data across a cluster of servers. This means that no single server stores all the data, making it a shared resource that is accessible by multiple users within a network, rather than local storage on a single device.

For details, see Red Hat CEPH Storage.

Other validated object storage

The preceding sections detail storage platforms and versions that the engineering team tests for specific performance and load thresholds. In addition to these storage platforms, the Partner Engineering team validates object storage platforms that meet strict performance requirements.

For details, see On-Premises.

6 - OpenText Analytics Database on Amazon Web Services

For information about deploying OpenText™ Analytics Database on Amazon Web Services (AWS), see OpenText Analytics Database on Amazon Web Services.

AWS instance types

The database supports a range of AWS instance types to deploy cluster hosts or MC hosts on AWS. See Supported AWS instance types for a complete list of supported instance types.

Amazon machine images

The database provides tested and pre-configured Amazon Machine Images (AMIs) to deploy cluster hosts or MC hosts on AWS. The AMI allows users to configure their own storage using the officially supported version of the database for AWS.

See Choose an AMI Operating System for a list of operating systems currently available in the AMIs.

Consider the following when using the AMI:

• The database develops AMIs on a slightly different schedule than the product release schedule. The AMIs for the database releases are available sometime following the initial release of the database.

• Each AMI is pre-configured with default resource limit settings.

• Amazon does not support using 32-bit binaries on Amazon Linux 2.0 AMIs. Therefore, you cannot use the 32-bit client libraries on these AMIs.

IPv6 support

Vertica supports using IPv6 to identify nodes in the database cluster. However, AWS DNS resolution does not support IPv6. To have a cluster in AWS that uses IPv6, use the IPv6 IP addresses instead of using host names when installing Vertica and forming the cluster.

7 - Containerized environments

OpenText™ Analytics Database supports containerized environments that conform to the performance requirements for vioperf, vnetperf, and vcpuperf.

As the database extends support and deployment in containerized environments including Kubernetes, we cannot test and certify all possible configurations. However, OpenText makes an effort to ensure the success of its customers on recent versions of supported operating systems for the x86_64 architecture.

The database tests containers running on Docker. When the underlying hardware, OS, and container are configured correctly, the database system performs well. In some circumstances, there is a minor performance difference for queries made against a cold- or partially-populated depot when accessing communal storage.

The database support contract covers database products only. If you choose to run the database on a container configuration and experience an issue that might not be caused by database products, the support team might ask you to reproduce the issue in a different environment or engage with the support resources for your containerization technology.

For guidelines on how to provision and size your Kubernetes resources for database deployments, see Recommendations for Sizing Vertica Nodes and Clusters in the Knowledge Base.

VerticaDB operator and OpenText™ Analytics Database server version support

The VerticaDB operator supports database server versions 11.0.0 and higher.

For more information about downloading images, version details, creating custom images, and the security vulnerability policy, see images.

Container orchestration version support

Communal storage support

Containerized OpenText™ Analytics Database on Kubernetes supports the following public and private cloud providers:

• Amazon Web Services S3

• S3-compatible storage, such as MinIO

• Google Cloud Storage

• Azure Blob Storage

• Hadoop File Storage

Managed Kubernetes services support

OpenText™ Analytics Database supports the following managed Kubernetes services:

• Amazon Elastic Kubernetes Service (EKS)

• Google Kubernetes Engine (GKE)

• Azure Kubernetes Service (AKS)

Cluster management platform support

OpenText™ Analytics Database supports the VerticaDB operator and database in Kubernetes environment on Red Hat OpenShift versions 4.8 and higher.

8 - Virtualized environments

OpenText™ Analytics Database supports running in any virtualized environment that conforms to the performance requirements for vioperf, vnetperf, and vcpuperf.

The database does not support VM Snapshot.

OpenText has tested VMware and when the underlying hardware is configured correctly, VMWare performs well. Customers have also deployed other virtualization configurations successfully. If you choose to run the database on a different virtualization configuration and you experience an issue, the support team may request you to reproduce the issue using a bare-metal environment to aid in troubleshooting. Depending on the details of the case, the Support team may also request you to enter a support ticket with your virtualization vendor.

Guidelines for hypervisor and virtual machine configuration

There are many enterprise-grade hypervisors available in the market today, most of which support Linux-based virtual machines (VMs) in support of the database. When selecting and configuring your virtual environment, refer to the following guidelines.

• Do not over-subscribe the physical resources (CPU, memory, and network) of the hosting hardware. Many hypervisors allow you to take advantage of scaling out solutions by over-subscribing resources, for example, deploying more virtual CPUs than are physically installed in the host hardware. However, this type of deployment has a negative performance effect on a database cluster.

• Configure the hypervisor to run low-latency, high-performance applications. This means that you should disable power-saving features and CPU frequency scaling on the hypervisor hardware because these technologies contribute to latency in the applications.

• Choose an operating system for the database VMs that is supported by the database and by the hypervisor you are using. For some hypervisors, different operating systems may perform better than others. It is recommended that you investigate the options with your hypervisor vendor.

• Configure attached storage for high I/O performance. A virtualized database node requires the same amount of disk I/O performance as a non-virtualized one. It is recommended to use the vioperf utility to validate the actual performance throughput on each VM.

• If you are providing storage using a shared storage device, make sure to validate disk I/O performance on the cluster as a whole to ensure that the shared resource(s) do not create a bottleneck. To achieve this validation, run the vioperf utility on all the cluster nodes simultaneously to determine the maximum disk I/O performance that can be achieved on each VM during times of heavy I/O load.

• Memory recommendations for the database running in a virtualized environment are no different than running in a non-virtualized environment. It is recommended that you allocate 8 GB of memory per virtual core. Do not over-subscribe the memory available in the hypervisor, because this creates contention for the physical resources, causes negative performance impacts, and possibly crashes the VMs.

• Networking requirements for a virtualized database cluster are the same as for a non-virtualized cluster. Each node in the cluster must be able to communicate with all the other nodes, and latency in those communications can have a negative effect on cluster performance. When you are running multiple virtual machines on a single host server, the network communication is very fast. This occurs because the network traffic is virtualized in the memory space of the hypervisor and never leaves the physical server. However, if the cluster expands beyond a single host, the physical networking of that host can become a bottleneck for the cluster. If you are deploying in a virtual environment, that environment has a robust networking infrastructure that can provide the necessary connection speeds between physical hosts. In most cases, there will be multiple 10 GBE networking connections. Use the vnetperf utility to validate actual network performance speeds between nodes in your database cluster.

• When deploying multiple database VMs per physical host, the fewer the better. The goal of virtualization is to consolidate workloads to reduce overall hardware footprints. However, running multiple database VMs on the same host can place the database cluster in a situation where a single hardware failure can take down multiple nodes in a cluster and perhaps even the cluster itself. When you virtualize a database cluster, OpenText recommends that you spread the VMs across as many physical hosts as possible with an ideal goal of having one database VM per physical host.

• While virtual networking can be very robust, UDP broadcast traffic that is used in the spread daemon can be unreliable in most virtual environments, especially when those environments are spread across more than one physical host. In order for the database to function effectively in a virtualized environment, use the --point-to-point flag when you execute the /opt/vertica/sbin/install_vertica script. This flag configures the spread daemons to communicate directly with one another.

9 - Hadoop integrations

OpenText™ Analytics Database 25.3.x supports the following Hadoop distributions. The database is expected to work with subsequent Hadoop distributions. OpenText tests these Hadoop distributions as soon as possible.

* OpenText is phasing out support for this platform. For more information, see End-of-support notices.

You must apply patches for the following issues: HDFS-8855 and HDFS-8696. See your Hadoop vendor documentation for further instructions.

MapR versions 5.2 and later are expected to work. You cannot use MapR in Eon Mode.

10 - Apache Kafka integrations

You can use OpenText™ Analytics Database with the Apache Kafka message broker. For more information on Kafka integration, refer to Apache Kafka integration.

Kafka versions

The database has been tested with different versions of Apache Kafka. The following table lists the Kafka versions that each database version supports:

Avro schema registry versions

Database integration for Apache Kafka has been tested with the Avro schema registry distributed with Confluent 3.3.1 and 4.0.0. For more information about Confluent, see the Confluent website.

Java versions

The data streaming job scheduler uses the JDBC library to connect to the target database and requires Java 8 or later.

11 - Apache Spark integrations

You can use the OpenText™ Analytics Database Connector for Apache Spark to transfer data between the database and Apache Spark. The following table shows the versions Apache Spark and Scala the Connector supports as well as the name of the Spark Connector JAR file to use for each combination:

* OpenText is phasing out this Apache Spark version. For more information, see End-of-support notices.

Notes

• A Spark Connector JAR file can support multiple versions of Spark. For example, vertica-spark2.1_scala2.11.jar supports Spark 2.1, 2.2, 2.3, and 2.4.1.

• It is recommended that you always use the version of the Spark Connector shipped with your version of the database server. When you upgrade your database server, you should also upgrade your version of the Spark Connector.

For more information about Apache Spark integration, see Apache Spark integration.

12 - Linux volume manager (LVM)

OpenText™ Analytics Database 25.3.x supports Linux Volume Manager (LVM) on all supported operating systems.

LVM version supported

The database supports LVM version 2.02.66 or later and includes device-mapper version 1.02.48 or later.

LVM configuration notes

In configuring LVM:

• When you create logical volumes with the lvcreate command, use the readahead option to set the read ahead sector count to greater than 2048 KB.

• You can use the default settings for all other LVM options.

LVM restrictions

The following limitations apply to LVM support:

• You cannot have physical drives shared across several nodes.

• The database supports linear logical volumes only. It does not support striped or mirrored logical volumes.

• The database supports extending logical volumes (lvextend) but not reducing the size of a logical volume.

• We recommend frequent backups.

• The database does not support LVM backup and restore features, such as LVM snapshot and merge. Instead, use the database's backup utility vbr.

• The database does not support LVM space reclamation because space reclamation is duplicated when reducing the size of a logical volume.

• The database does not support LVM migration. Use Copy operations.

• The database does not support LVM high availability. Use the high availability capabilities of the database.

• The database does not support LVM RAID. Configure RAID at the disk controller level.

13 - End-of-support notices

These end-of-support notices apply to specific client, Linux, Hadoop, and Kafka distributions.

End-of-support notices

OpenText™ Analytics Database no longer supports the following client platforms and server distributions:

• AIX (all releases)

• Amazon Linux 2017.09

• Debian 7.6, 7.7

• HP-UX (all releases)

• macOS 10.10

• Red Hat Enterprise Linux/CentOS 6.x

• SUSE 11SP3

• Ubuntu 12.04