Rocket® Vertica

Environment Analytics Database 25.2  Situation An issue has been identified involving super projections in the database. Recent troubleshooting actions appear to have affected not only existing projections but also the engine’s behavior when generating new super projections for newly created tables. A comparative test was executed on both the new cluster and the previous Vertica environment by loading an 85 GB CSV file into an empty table created specifically for validation. In the older database, the loaded table occupies approximately 15 GB. In the new cluster, the same dataset results in a table size of nearly 35 GB—more than double the previous footprint.Clarification is needed regarding the underlying cause of this discrepancy and the changes occurring within the database engine.   Find resolution on support portal

Environment Analytics Database 25.3  Situation Debian documentation recommends a minimum readahead of 2048. The code in /opt/vertica/oss/python3/lib/python3.13/site-packages/vertica/platform/node/t/disk.py triggers a failure when readahead exceeds 8192. Guidance is needed on whether readahead should match the hardware’s maximum supported value and whether values above 8192 create any risks when supported by the hardware. Find resolution on support portal

Environment Vertica Analytics Platform 12.0.4  Situation Guidance is requested regarding available and recommended operating‑system options. Specific requirements include: Identification of supported or recommended free RHEL‑compatible distributions Recommended upgrade methodology with zero down time.  Clarification on whether AlmaLinux is supported for Vertica deployments  Feasibility of operating a heterogeneous cluster when upgrading 1–3 nodes at a time Find resolution on support portal

Environment Vertica Analytics Platform 11.1 Situation Production Database is down, and all database nodes are unreachable. Resolution The below location was created as DATA and since it is shared path, it has caused issues. This location was retired and next step is to drop the tables associated with this location and the copy the data from other database.   CREATE LOCATION '/ver_hdfs_move/CVM'Find article on support portal

Environment Vertica Analytics Platform 12.0.4.-18 Situation A production six‑node cluster running Vertica 12.0.4‑18 in Enterprise mode on Linux 8.8 experienced a severe performance degradation. Vertica‑reported CPU and memory usage on all nodes remained below 50%. As part of initial remediation, Vertica was stopped on node 1 and the host was rebooted, but the issue persisted. A simple diagnostic test showed that, despite identical hardware metrics (CPU, memory, network, I/O, and load), the query SELECT 1 required approximately 1 second on node v_ops_node0002 (10.218.0.17), compared to the usual sub‑10 ms response time. A full node restart and host reboot eventually resolved the condition. Scrutinize data can be provided for further analysis. Find resolution on support portal

Environment Analytics Database 24.4  Situation  A nine‑node physical Vertica cluster encountered a startup failure after the removal of one node. Following the removal process, the database reported the error: “Database startup failed: too many nodes have invalid or missing last good epoch values to continue. Run diFind resolution on support portal

Products Analytics Database Environment Vertica Analytics Database 12.0.4  Situation On a replicated DR database one node had hardware issues and was rebuilt from scratch. The OS was rebuilt, node recovery keeps failing Find resolution on support portal

Environment Analytics Database 25.3  Situation Vertica EON is being configured, and documentation indicates that Vertica can access the S3 location defined as communal storage, allowing direct COPY operations from that S3 bucket. A separate requirement involves loading files from another S3 bucket that uses a different endpoint, access key, and secret. The per‑bucket configuration documentation (https://docs.vertica.com/24.2.x/en/sql-reference/file-systems-and-object-stores/s3-object-store/per-bucket-s3-configs/#recommended-usage) provides partial guidance, but questions remain regarding management of S3BucketCredentials. Documentation advises against storing credentials with ALTER DATABASE DEFAULT and instead recommends ALTER SESSION or alternative mechanisms. Because the load process is executed by an automated job, issuing ALTER SESSION before every file load is not feasible. Guidance is requested on alternative supported methods for storing S3BucketCredentials, including whether a

Vertica Patch Notice 25.2.0-x Patch The latest 25.2 patch has been released: *25.2.0-6 Products Vertica Analytics Platform, Analytics Database Vertica Patch Notice25.2.0-x Patch The latest 25.2 patch has been released:*25.2.0-6 Release Notes: https://docs.vertica.com/release-notes/25.2.x/resolved-issues/ Vertica Patches available on the SLD Site: https://sld.microfocus.com/mysoftware/index If you need assistance, please contact Vertica Technical support via the customer portal at https://portal.microfocus.com/.

This article describes the reasons why COPY statements fail when reading from HDFS and how to resolve the issue. Environment Vertica analytics Database: v9.2.x Situation The user is experiencing a high number of COPY statement failures when reading from HDFS. How can this issue be resolved? Find complete article on support portal

Vertica Patch Notice 26.1.0-x HOT-FIX The latest 26.1.0 patch has been released: *26.1.0-2 Vertica Patch Notice26.1.0-x HOT-FIX The latest 26.1.0 patch has been released:*26.1.0-2 Release Notes: https://docs.vertica.com/release-notes/26.1.x/resolved-issues/ Vertica Patches available on the SLD Site: https://sld.microfocus.com/mysoftware/index If you need assistance, please contact Vertica Technical support via the customer portal at https://portal.microfocus.com/.

This article explains the reasons behind the Vertica node crashes and how to resolve it. Environment Vertica analytics Database: v25.3.x Situation Multiple Vertica nodes down in a cluster with the below error. Need to find RCA on why those nodes are down and how to fix the issue permanently. [Main] <PANIC> Received fatal signal SIGSEGV [Main] <PANIC> Info: si_code: 1, si_pid: 40, si_uid: 0, si_addr: 0x28Find complete article on support portal

If Users imported through LDAPSync are no more able to sync with vertica database, any grants provided by that user to some other user for an obeject owned by LDAP user , don't work any more. Environment All Vertica Versions with ldapsync  Situation Customer has a ladaplink setup where users/groups are imported to Vertica database as user/roles basedof filter criteria mentioned in ldaplink setup. One day, there is a change in ldaplink filter criteriaand a LADAP user suppose named "LDAPUSER1" is no more getting authenticated by LDAP, but is already imported in Vertica database. Now if that LDAP user "LDAPUSER1" is: a) Owner of object "A" b) have internally granted permissions of SELECT/INSERT/UPDATE on object "A" to another database user "USER2" It is seen that, "USER2" will not be able to do operations like SELECT/INSERT on obejct "A" - permission denied. Find complete article on support portal

Username Enumeration Observable Response Discrepancy vulnerability has been discovered in OpenText™ Vertica. The vulnerability could lead to Password Brute Forcing. Find complete article on support portal

Improper neutralization of input during web page generation vulnerability has been discovered in OpenText™ Vertica. The vulnerability could lead to Reflected XSS attack of cross-site scripting Find complete article on support portal

Improper neutralization of input during web page generation vulnerability has been discovered in OpenText™ Vertica. The vulnerability could lead to Reflected XSS attack of cross-site scripting Access article on support portal

PL/vSQL loop runs dynamic SQL many times inside one statement, creating huge internal executions and monitoring growth; batch/limit or redesign to set-based SQL to reduce it. Environment Vertica Analytics Database Workloads using PL/vSQL (or other procedural SQL blocks) that build and execute dynamic SQL in loops Situation Monitoring/history data (for example, “query consumption” / “execution records”) grows extremely fast. A small number of executions account for the majority of the growth. The workload looks like one outer statement, but the system shows many internal executions associated with it. Customers may report: Rapid growth of monitoring/history storage Increased overhead when querying monitoring/history Performance impact during or after running the procedural script Find resolution on support portal

Vertica Patch Notice 25.3.0-x Patch The latest 25.3 patch has been released: *25.3.0-8 Products Analytics Database, Vertica Analytics Platform Vertica Patch Notice25.3.0-x Patch The latest 25.3 patch has been released:*25.3.0-8 Release Notes: https://docs.vertica.com/release-notes/25.3/ Vertica Patches available on the SLD Site: https://sld.microfocus.com/mysoftware/index If you need assistance, please contact Vertica Technical support via the customer portal at https://portal.microfocus.com/.

This article describes the use of an Amazon S3 bucket with Versioning enabled as a backup location. Environment OpenText Analytics Database (Vertica) Situation AWS provides a Versioning feature for Amazon S3 buckets, which enhances data protection and durability. This article addresses whether users can benefit from enabling Versioning on an Amazon S3 bucket used as a backup location. Find resolution on support portal

Is Unbreakable Enterprise Kernel supported by Vertica Environment Vertica Analytics database: v12.x and higher   Situation Support for Unbreakable Enterprise Kernel Find resolution on support portal

The Vertica process on a failed node fails to start after the attempt upgrade failed Environment Vertica Analytics Database: v11.x and higher   Situation After a failed upgrade, one of the nodes failed to start. After checking the status of the node using admintools, it was learnt that the upgrade activity had failed. Only the failed node received the upgrade package while the peer nodes were still reporting the previous package - Find complete article on support portal

Vertica Patch Notice 25.1.0-x HOT-FIX The latest 25.1 patch has been released: *25.1.0-7 Products Vertica Analytics Platform, Analytics Database Vertica Patch Notice25.1.0-x HOT-FIX The latest 25.1 patch has been released:*25.1.0-7 Release Notes: https://docs.vertica.com/release-notes/25.1.x/resolved-issues/ Vertica Patches available on the SLD Site: https://sld.microfocus.com/mysoftware/index If you need assistance, please contact Vertica Technical support via the customer portal at https://portal.microfocus.com/.

Vertica Patch Notice 25.4.0-x Patch The latest 25.4 patch has been released: *25.4.0-4 Products Vertica Analytics Platform, Analytics Database Vertica Patch Notice25.4.0-x Patch The latest 25.4 patch has been released:*25.4.0-4 Release Notes: https://docs.vertica.com/release-notes/25.4/ Vertica Patches available on the SLD Site: https://sld.microfocus.com/mysoftware/index If you need assistance, please contact Vertica Technical support via the customer portal at https://portal.microfocus.com/

In today’s era of rising citizen expectations, expanding cyber threats, and increasingly complex mandates, government agencies must not only modernize — they must do so with purpose, agility, and vision. Welcome to AI-powered public sector transformation, where every agency touchpoint is smarter, every service is faster, and every system is built for resilience. At the OpenText Government Summit, we’ll explore how public sector leaders are streamlining digital operations, harnessing AI, and designing future-ready platforms enabled under a single provider. From achieving compliance with executive orders and security mandates to building seamless citizen experiences, discover how a unified cloud and information management strategy can simplify your tech stack and accelerate your mission. Join us to examine what’s next for digital government. You’ll gain first-hand insights from the country’s foremost experts on: Implementing Zero Trust cybersecurity and securing software supply chains Le