Rocket® Vertica

Few queries would often throw file not found error in eon mode Environment Vertica analytics database: v23.x and higher   Situation Few queries throw below error - ExceptionMessage: [Vertica][VJDBC](8912) ERROR: FileColumnReader: unable to open position index [s3://bucket_url/58e   Find complete article on support portal

How to create a separate PVC for catalog and depot paths in k8s deployment Environment Vertica Analytics Database: v25.x and earlier   Situation How to create a separate PVC for catalog and depot paths in k8s deployment Find resolution on support portal

The article will help identify one of the cause of the slow performance Environment Vertica version 11.0.x Situation Vertica performance became slow during heavy use, the below network error was seen in dmesg DROP: IN=bond0 OUT= MAC=ff:ff:ff:ff:ff:ff:e4:3d:1a:83:b0:91:08:00 SRC=0.0.0.0 DST=255.255.255.255 LEN=316 TOS=0x00 Find complete article on support portal

This article provides information on why the Vertica create_db command is failing and how to resolve it. Environment Vertica analytics Database: v23.4.x Situation Admintools create_db command is failing with the below error,   Unhandled exception during admintools operation raised error: <class 'KeyError'> error message: '<db_name>' Stack trace written to file: /opt/vertica/log/adminTools.errors Find complete article on support portal

How to enable GCLX profiling in Vertica Environment Vertica Analytics Database: v23.x and higher   Situation How to enable Global Catalog X Lock profiling   Find complete article on support portal

How to generate and use Vertica api keys Environment Vertica Analytics Database: v9.x and above   Situation How to generate api keys in Vertica   Find complete article on support portal

How to integrate Vertica k8s with vaults Environment Vertica Analytics Database: v24 and higher Situation In Vertica k8s deployment the passwords/licenses are taken from dedicated k8s secrets. From security point of view, is there any way/any configuration to be added so that verticadb directly connects to Vault to get the proper secrets from a dedicated path?   Find complete article on support portal

Vertica Patch Notice 23.4.0-x HOT-FIX The latest 23.4.x patch has been released: *23.4.0-21 Products Vertica Analytics Platform, Analytics Database Vertica Patch Notice23.4.0-x HOT-FIX The latest 23.4.x patch has been released:*23.4.0-21 Release Notes: https://docs.vertica.com/release-notes/23.4.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/.

The vertica in-db server replication doesn't work between 12.0.4 and 25.3 Environment Vertica analytics database: v12.0.4 and versions earlier than 24.3   Situation While trying to run Vertica's in db server replication, the process fails with below error- 025-10-24 06:04:35.490 Init Session:0x7fd9f2ffa640 [Catalog] <WARNING> Replicating objects failed: Unexpected error: Find resolution on support portal

After Upgrade to 25.x, the vertica agent does not start automatically after reboot, this article will help work around Environment Vertica version 25.x Situation The agent wouldn't start automatically after reboot. Find complete article on support portal

Users using a username with cases diferent than what were used at creation time Environment Vertica analytics database: v23.4 and above   Situation Users created with md5 hashing algorithm experience authentication failures if the cases of usernames are different - test=> create user ajilani1 identified by 'abc123'; CREATE USER test=> ALTER USER ajilani1 SECURITY_ALGORITHM 'MD5'; WARNING 9760: MD5 authentication is deprecated ALTER USER test=> [dbadmin@ajilani07 ~]$ vsql -U ajilani1 -w abc123 Welcome to vsql, the Vertica Analytic Database interactive terminal. Type: \h or \? for help with vsql commands \g or terminate with semicolon to execute query \q to quit test=> test=> \q [dbadmin@ajilani07 ~]$ [dbadmin@ajilani07 ~]$ [dbadmin@ajilani07 ~]$ vsql -U AJILANI1 -w abc123 vsql: FATAL 2248: Authentication failed for username "AJILANI1" Here in the 2nd failed attempt, we are using uppercase in the username while authentication.

We’re proud to share that OpenText has been named a Major Player in the IDC MarketScape: Worldwide Business Intelligence and Analytics Platforms 2025 Vendor Assessment. This recognition reflects our continued focus on delivering powerful, unified analytics solutions that meet the needs of large enterprises—especially those with complex, regulated, and high-scale data environments. A unified platform for enterprise-grade analytics OpenText™ Analytics Cloud combines two foundational technologies: Together, they deliver end-to-end analytics—from data ingestion to AI-powered decision intelligence—within a single, modern architecture. Find out more

Attending OpenText World 2025? Make sure you attend the OpenText Analytics and AI Cloud keynote on Nov. 19 at 1 p.m. CST to learn how to break through barriers with high-performance analytics, native machine learning, and flexible deployment at scale. Learn about all of OpenText Analytics Cloud activities at OpenText World

troubleshoot and address the node dependency issue related to DFS files on adding nodes and completion of rebalance. Environment Vertica analytics database: Enterprise mode all versions   Situation On adding node(s) to an existing cluster and completion of rebalance, node_dependencies showing similar to below: get_node_dependencies Deps: .... .... 0011111111 - cnt: 6 1111111111 - cnt: 86 => select get_node_dependencies('0011111111'); get_node_dependencies 0011111111 - DFS file logWordITokenizer_defaultConfig 0011111111 - DFS file logNgramTokenizer_defaultConfig 0011111111 - DFS file logICUTokenizer_defaultConfig 0011111111 - DFS file 49539595901076520 0011111111 - DFS file 49539595901076532 0011111111 - DFS file 49539595901076546 DFS files info not rebalanced to newly added 2 nodes in this case. Find complete article on support portal

After successful upgrade, the library version of the system packages is still pointing to previous version Environment Vertica Analytics Database: version All   Situation After successful upgrade, the library version of the system packages is still pointing to previous version - => select schema_name, lib_name, author, sdk_version, lib_version, lib_sdk_version from user_libraries; schema_name | lib_name | author | sdk_version | lib_version | lib_sdk_version -------------+--------------------+---------+-------------+-------------+----------------- public | ComplexTypesLib | Vertica | 25.2.0 | v25.3.0-1 | 25.2.0 public | DelimitedExportLib | Vertica | 25.2.0 | v25.3.0-1 | 25.2.0 public | JsonExportLib | Vertica | 25.2.0 | v25.3.0-1 | 25.2.0 public | MachineLearningLib | Vertica | 25.2.0 | 25.3.0 | 25.2.0 public | OrcExportLib | Vertica | 25.2.0 | v25.3.0 | 25.2.0 public | Parq

OpenText is announcing the release of Product: Analytics Database 25.4Version: 25.4Languages: English The following new key features are available with this version: External Archives for Disaster RecoveryAbility to replicate the DB for disaster recovery without having a live cluster. Customers can manage full state backups in multiple data centers easier, including across clouds, buckets and regions. That brings more confidence in the product. The DR story is always an important part of any deal. Built-in auto tuningImprove better default settings for auto projections. We will introduce algorithms to periodically generate efficient projection plans and apply them. The outcome is that customers can avoid manual tuning in common scenarios. Online upgrades for non-K8sExtend current K8s online upgrade to other environment settings like on-prem. Reduce the need for additional resources during the online upgrade. Reduce hiccup time and improve performance. Outcome is that non-K8s customer

After the user finishes importing the database in Management Console, the user interface fails to generate graphs for metrics Environment Vertica Analytics Database: version 24.x and 25.x   Situation After the user finishes importing the database in Vertica Management Console, the user interface fails to generate graphs for metrics. The management console shows the below error- Error occurred while getting database thresholds null Find complete article on support portal

Hello, I was trying to install the CE of this product but I'm unable to find any listed resource. On the documentation is stated that there are two options: either a container image or a prebuild vm image, the problem I face is that every link is broken. The Vertica DockerHub registry is empty, so I tried to build a custom CE image using the one-node-ce GitHub repository (which last version seem to be 12.x), needing a the free CE trial RPM. I've tried to start a trial using the new website, but it only seem to point me to a cloud version: Using this https://forum.vertica.com/discussion/244836/vertica-12-0-download thread as a guide, I've tried to get to the Software Licenses and Downloads Portal to get the license to the trial, and or the software, but it needs now I need to be given permission first: For what it seems I need a serial I can't find. Can you help me thru this, please?

This article explains a brief communication loss in a Vertica cluster caused by a transient network socket error in the Spread messaging layer. The error triggered a temporary k-safety reassessment but did not indicate a persistent issue. Environment Vertica Cluster Spread messaging layer Vertica version with default Spread configuration Situation A Vertica node experienced a brief communication loss, and logs showed the following error: Spread Mailbox Dequeue: [Comms] <WARNING> error SP_receive: The network socket experienced an error. This Spread mailbox will no longer work until the connection is disconnected and then reconnected Cause The issue was caused by a transient network socket error in Vertica’s Spread messaging layer. This led to a temporary loss of communication between nodes and triggered a k-safety reassessment. Find complete article on support portal

This article summarizes a performance health check of a Vertica system. All key metrics—including CPU usage, query concurrency, and I/O wait—were found to be within acceptable thresholds, indicating stable and healthy system behavior. Environment Vertica Database Cloud or virtualized infrastructure Monitoring tools capturing CPU, I/O, and query metrics Situation A customer requested a review of system performance metrics to assess overall health and identify any potential bottlenecks or anomalies. Cause No performance issues were detected. All metrics reviewed were consistent with expected values for a healthy Vertica deployment. Find complete article on support portal

Vertica currently supports license installation only during initial database creation in Operator-based deployments. License updates or replacements after creation are not yet supported. An enhancement request has been accepted and is planned for Vertica version 26.2. Environment Vertica Operator-based deployments Vertica versions prior to 26.2 License management Situation A customer attempted to update or replace a Vertica license after database creation using the Operator and found that the operation was not supported. Find complete article on support portal

This article addresses a previously reported flooding issue with the vertica_health_watchdog_txn counter. The issue has been resolved in Vertica versions 25.1 and 25.2. Customers experiencing this behavior are advised to upgrade to Vertica 25.x. Environment Vertica versions prior to 25.1 Vertica 25.1 and 25.2 Health monitoring and watchdog counters Situation Customers observed excessive logging or metric flooding related to the vertica_health_watchdog_txn counter, impacting monitoring clarity and system performance. Find complete article on support portal

This article addresses a query failure caused by data corruption in a Vertica table. It outlines how to identify and resolve the issue, and provides recommendations for prevention. Environment Vertica Database Analytical workloads Table-level operations Situation A customer reported query failures when accessing a specific table in Vertica. The issue persisted across multiple sessions and was isolated to a single table. Find complete article on support portal

This article shares guidance and performance benchmarks from the official Pure Storage white paper on deploying Vertica in Eon Mode with FlashBlade. It clarifies that throughput and query performance are more relevant than traditional IOPS metrics for analytical workloads. Environment Vertica in Eon Mode Pure Storage FlashBlade Analytical workloads Backup and replication operations Situation A customer inquired about the performance characteristics and deployment considerations of Vertica in Eon Mode using Pure Storage FlashBlade. Find complete article on support portal