Resolved issues
Resolved issues release notes for 25.1.x.
25.1.0-7
Updated 03/03/2026
| Issue Key | Application Module | Description |
|---|---|---|
| 4939031 | QA - MC | A fix has been implemented to address an issue where the Vertica Management Console (MC) extended monitoring was not streaming data in the MC. The fix ensures that data is correctly displayed in the MC. |
| 4989562 | Execution Engine | An issue was found, where a node crash was triggered by a VAssert failure related to memory allocation, specifically 'VAssert(toCheckCleared[0] == 0 && (memSize < 16 || toCheckCleared[1] == 0)) failed'. This fix addresses the underlying memory management issue to prevent node crashes in similar scenarios. |
| 5015455 | Admin Tools |
Corrected logrotate Help Output: Previously, running admintools -t logrotate --help displayed an incorrect usage message, showing Usage: logrotateconfig [options]. This was misleading as logrotateconfig is not a valid tool name. Now, the help output for admintools -t logrotate --help has been corrected to accurately display Usage: logrotate [options], along with the valid options list. This fix improves the accuracy of admintools help text and ensures consistency between the command-line interface and documentation. |
| 5079571 | Execution Engine | Replicated tables used to error out when performing cross namespace ILM operations. This issue has been resolved. |
| 5081951 | Backup/DR | Fixed an issue where server-based replication between two Eon mode clusters failed due to mismatched shard boundaries after migrating from an Enterprise Edition (EE) cluster to an Eon mode cluster. Replication now functions correctly between migrated and freshly installed clusters. |
| 5085486 | Data Networking |
A high-severity issue where the Vertica database would hang shortly after upgrading, particularly when MinTLSVersion was set to 3, has been resolved. This fix ensures database stability and prevents SQL queries from becoming stuck on all nodes, restoring normal operation. |
| 5086372 | Data Networking | TS callback dtor should cleanup without the lock: Addressed a potential deadlock scenario where TS callback destructors were executing while holding a lock. This could lead to conflicts with other system components, such as the async Messenger notifier, which might also require the same lock. Now, the system has been updated to ensure that TS callback destructors now execute outside of the lock, thereby preventing deadlocks and improving overall system stability. |
| 5092599 | Backup/DR | Int-String comparison in table expression used to fail VBR and VBR5 restore. This issue has been fixed. |
| 5104467 | UI - Management Console |
The Management Console has been updated to no longer query the EnableSSL configuration parameter, eliminating the daily error messages and false alarms. |
| 5107651 | System: Performance | This fix involved changing how we track scan columns for the general case vs. in a database that has been resharded. In v11.1, the resharding feature added tracking of segmentation columns to all scans, even when they are not needed; the fix was to only track the segmentation columns if they are specifically needed for the query or for a reshard scenario. |
| 5109098 | Optimizer |
Resolved an issue where UPDATE statements, when joining with multi-level views (views referencing other views and tables across different schemas), could incorrectly trigger an 'Internal Optimizer Error (11)'. UPDATE queries involving these complex view structures now execute as expected without error. |
| 5144016 | UI - Management Console | Several critical and high-severity security vulnerabilities (e.g., CVE-2025-58183, CVE-2025-58186, CVE-2025-58187 in stdlib) within the vertica-23.4.0-21.x86_64.SUSE.rpm package have been remediated. |
| 5181095 | DDL - Table | This fix resolves an issue where temporary relation (TempRel) decoding could lead to data corruption, specifically affecting string data within recursive Common Table Expressions (CTEs). The fix ensures proper handling of character encoding and VARCHAR length constraints, preventing the occurrence of non-UTF8 data and oversized strings, thereby restoring data integrity and eliminating the need for performance-impacting workarounds. |
| 5184562 | Admin Tools |
Before this fix, AdminTools restart_node may find a secondary UP node to run catalog editor for getting catalog information. After this fix, AdminTools restart_node consistently finds a primary UP node to run catalog editor for getting catalog information, ensuring getting the correct and up-to-date catalog information. |
| 5202438 | Execution Engine | Previously when a user using the COPY command with the delimited parser was trying to insert data for an array[varchar] column, they could trigger an internal error if their input began with back-to-back enclosing characters. Now, the server appropriately can parse multiple enclosing characters to begin an array[varchar] column, where the first enclosing character is treated as an enclosing character and the second enclosing character represents the first character in the varchar data. |
| 5223279 | Kubernetes, Vcluster | Before the fix, the Kubernetes operator may error out upon seeing remote user storage location when reviving an Eon database migrated from 10.x Enterprise database. With the fix, the Kubernetes operator correctly handles the remote user storage locations created in an older version enterprise database for reviving. |
25.1.0-6
Updated 12/5/2025
| Issue Key | Application Module | Description |
|---|---|---|
| 4562633 | UI - Management Console | DBD upload file permission error: The 'DBD upload file permission error' has been resolved. Users can now successfully upload query files in the DBD tab, or via MC > New design > Manual, without encountering a 'Permission denied' error. This fix ensures that superusers, and all users, can upload files without permission restrictions. |
| 4772296 | License | An issue occurred where license audit compliance status showed an anomaly. This issue has been resolved. The GET_COMPLIANCE_STATUS() function now accurately reflects the overall compliance status, aligning with individual schema audits. |
| 4854721 | Machine Learning | A fix has been implemented to address an issue encountered when importing XGBoost models in PMML format. Specifically, an error was triggered during the import process, resulting in a 'VIAssert' failure. This issue has been resolved to ensure successful PMML model imports. |
| 4866839 | Third Party Tools Integration | Fixed a critical security vulnerability (CVE-2024-45337) in the Vertica Docker image (opentext/vertica-k8s:24.4.0-1). |
| 4876455 | Optimizer | Fixed an issue where INSERT…SELECT statements would hang when GROUPBY PUSHDOWN was not occurring due to the presence of non-equi joins. The fix ensures that INSERT…SELECT queries with non-equi joins no longer result in indefinite hanging, restoring expected performance. |
| 4878506 | System: Performance |
Fix for 100% CPU Utilization with STRPOS Function: We’ve optimized the behavior of the STRPOS function to significantly improve performance in specific scenarios. What changed: Previously, all inputs to STRPOS were converted to UTF-16 to leverage the ICU (International Components for Unicode) library for string comparison. While ICU provides robust support for complex locale-aware comparisons, this conversion introduced overhead—especially for simple use cases. Now, for simple locales with 1-to-1 character mappings (such as en_US, de_DE, and other locales where each character maps directly between UTF-8 and UTF-16 without requiring normalization or multi-codepoint handling), STRPOS uses a UTF-8 based comparison. This avoids the need for conversion to UTF-16 and bypasses the ICU library entirely, resulting in much faster execution. |
| 4893665 | Machine Learning | Resolved an issue where the imported TensorFlow model required an unexpected number of input columns (64) instead of the expected 6 (based on tf_model_desc.json and model summary). The model now correctly predicts with the expected number of input features. |
| 4902083 | Hadoop, ResourceManager | Resolved an issue where Vertica clusters would experience a timeout and core dump during startup after an upgrade from version 12.0.4 to 25.1. This problem specifically occurred during disk space information refresh and storage location creation, impacting environments with replicated S3 buckets and HDFS storage. The fix ensures successful database initialization and proper handling of storage locations in Vertica Analytic Database v25.1.0-6. |
| 4904536 | Catalog Engine | Certain complex queries using internal temp relations in their plans could either error or output duplicate rows. This issue has been resolved. |
| 4950425 | Data load / COPY | Fixed a node down issue that occurred when the 'CopyFaultTolerantExpressions' parameter was enabled and FILLER was used in conjunction with specific TO_CHAR conversions. Specifically, the node would crash during COPY operations when using TO_CHAR with formats like 'YYYYMMDD', 'FMDay, FMDD HH12:MI:SS', etc. This fix ensures stability when using fault-tolerant expressions with FILLER and TO_CHAR functions. |
| 4970329 | Security | Fixed an issue where creating access policies added extra parentheses, causing COPY_TABLE to fail with an access policy mismatch error. |
| 4980425 | Cloud - Amazon | The cluster was experiencing "Cluster Truncation Lag" due to nodes encountering "ExpiredToken" errors when reading from Parquet files in S3. This issue was causing the catalog truncation version to lag, requiring node restarts to resolve. A fix has been implemented to ensure the SDK correctly handles token expiration and retries, preventing the "ExpiredToken" errors and subsequent catalog synchronization issues. |
| 5006749 | EON | This release addresses an issue where cluster nodes experienced frequent crashes due to out-of-memory (OOM) errors. The problem was observed across primary and secondary subclusters, with RSS memory usage growing constantly, even on idle secondary subclusters. The fix resolves a memory leak that was affecting all hosts, regardless of hardware specifications or operating system. |
| 5008271 | Optimizer | Previously when comparing string literals cast to array with LIKE ANY/ALL (i.e. select 'foo' like any ('bar'::Array[varchar]);) Vertica would improperly locate string array data in memory and cause a fatal crash. This no longer happens. |
| 5012269 | Security |
New Database Parameter: Introduced a new database parameter, OAuth2JITConflictPolicy, to control OAuth2 JIT login for existing users. MERGE, the default, allows OAuth2 login for existing vertica users and grants them the appropriate auth method. This is identical to the existing behavior. If set to IGNORE then existing users require an OAuth2 client authentication granted to log in with an OAuth2 token, no automatic granting is performed. Users with psuedosuperuser are always treated as if OAuth2JITConflictPolicy is set to IGNORE, ie. they can only use authentication methods that have been explicitly granted. |
| 5047814 | Node Management Agent, Vcluster | Critical security vulnerabilities have been identified and fixed in the Go binaries (vcluster, vcluster_server, and node_management_agent) that shipped with the Vertica database (both RPM and containers). |
| 5048882 | Admin Tools | This fix ensures the upgrade process is successful and correctly handles the FlexTableLib library, resolving the fjsonparser incompatibility issue. |
25.1.0-5
Updated 07/02/2025
| Issue Key | Application Module | Description |
|---|---|---|
| 4636969 | Optimizer | Historically, the statistics histogram would be invalidated if the row count was updated without fully reanalyzing the columns; this invalidation no longer happens. |
25.1.0-4
Updated 06/24/2025
| Issue Key | Application Module | Description |
|---|---|---|
| 4634966 | Kafka Integration | The Kafka scheduler was failing to create on both FIPS and non-FIPS systems after upgrading to Vertica 25.1 This issue has been resolved. |
| 4730767 | Client Drivers - VSQL | From Vertica 9.3, file names with special characters are in the UTF-8 format. If there are issues loading files with special characters in their names, ensure that the encoding, code page, and locale settings are configured to support UTF-8. |
| 4777392 | Data Collector | Fixed an issue where comments added to table columns were not being reflected in the remarks column of the jdbc_columns table. This update ensures that column comments are properly synchronized. |
| 4805905 | Control Networking | The Vertica upgrade process has been enhanced to allow for co-existence of different Vertica versions within the same cluster during rolling upgrades. This is achieved through an override mechanism that specifies compatible build hashes, enabling administrators to perform manual online upgrades with less disruption. |
| 4810716 | Linux, PCx86 | In specific scenarios involving large JSON files with escape characters in string fields, the parsed string value could be missing a few characters. This issue has been resolved. |
| 4832011 | Data load / COPY | A fix has been implemented to address an issue where a Vertica node would crash when loading JSON data containing inconsistent ARRAY column values (some files with data, others without). The crash occurred specifically when loading a mix of JSON files where some contained data for the ARRAY column and others did not. This issue has been resolved. |
| 4837349 | Execution Engine | Certain complex queries using internal temp relations in their plans could either error or output duplicate rows. This issue has been fixed. |
25.1.0-3
Updated 04/01/2025
| Issue Key | Application Module | Description |
|---|---|---|
| 4522089 | Third Party Tools Integration |
We have upgraded the rsync connection for Linux file systems from version 3.2.7 to version 3.4.0 to fix these security vulnerabilities:
|
| 4523911 | EON | The UsePeerToPeerDataTransfer knob can now be enforced at the node level. |
| 4535433 | License | Table error_messages used to frequently contain warning message entries with a description similar to: "Skipping node information due to: Unknown node_id". This message did not indicate a real problem, so it was removed. |
| 4536639 | Database Designer Core, Refresh | An issue that was blocking the ability to run historical queries at epochs prior to the Ancient History Mark, while running the Refresh command, has been resolved. |
25.1.0-2
Updated 03/24/2025
| Issue Key | Application Module | Description |
|---|---|---|
| 4404831 | Backup/DR | An issue occurred where if a Vertica node was down, vbr would fail. This issue has been resolved. Now, the backup location points to the same host as the Vertica node. |
| 4444326 | License | Depending on the number of nodes in the cluster, a license expiration NOTICE message was appearing repeatedly. Now, the server reports this NOTICE message a limited number of times. |
| 4449031 | Admin Tools, Backup/DR | Added IMDSv2 support for config setup at db start. |
| 4491417 | Kafka Integration | An issue that was causing nodes to crash after upgrade in librdkafka has been resolved. |
25.1.0-1
Updated 03/14/2025
| Issue Key | Application Module | Description |
|---|---|---|
| 4350656 | Installation Program | Installing Vertica on Amazon 2023 Linux fails and an error message is displayed. |
| 4392278 | UDX | Creating user-defined extensions (UDX) in Python with the DEPENDS clause when the dependent libraries are present in Azure blob storage or Google Cloud storage fails. This issue is now resolved. The value of maxNest is increased to 15 from a default value of 2. |
| 4393188 | Directed Query | Directed query search could fail to match in cases where the predicate included {{CONST op CONST. }}. This issue has been resolved. |
| 4403815 | Scrutinize, Vcluster | System table data from vcluster scrutinize now has column headers in the retrieved files. |
25.1.0-0
Updated 01/16/2025
| Issue Key | Component | Description |
|---|---|---|
| VER-87686 | Client Drivers - JDBC | executeLargeUpdate returns an incorrect row count. This is caused by a bug in Simba SDK. Upgrade to the latest upgrade of Simba SDK to resolve this issue. |
| VER-90265 | Kafka Integration | Running the vkconfig shutdown command with the "-conf" option would sometimes erroneously shutdown all running vkconfig instances and not just the ones started with the specified configuration. This issue is now fixed. |
| VER-93594 | Optimizer | An issue occurred, where a join spill was happening when processing the optimized delete part of the plan, which disallows Filter/Filter join distribution. Since the join inner was too large to fit in memory, an error was returned with a hint to retry with Filter/Filter enabled, even though it was already enabled in the session. This issue has been resolved; to address this, when the EnableFilterFilter hint is encountered when it's already enabled, we check if it's an optimized delete plan and in that case retry with optimized delete disabled, allowing the optimizer to choose a Filter/Filter join distribution. |
| VER-93700 | DDL | An issue occurred where the CREATE TABLE syntax using INCLUDING PROJECTIONS creates new pin policies. The CREATE TABLE syntax has been changed to allow user excludes storage policies when running CREATE TABLE ... LIKE to copy the table structure from existing table. |
| VER-93842 | Logging | Old trace profile (.prof) files were not deleted filling up the disk space. A new functionality was added to the do_logrotate() meta function and LogRotateTask Timer serivce that deletes an existing profile if it is older than the max_age (7 days by default). |
| VER-94182 | UI - Management Console | Security Enhancement: Both /opt/vconsole/temp and /opt/vconsole/tempkc directories created by MC have had their permissions change to 750 (drwxr-x---). |
| VER-94621 | UI - Management Console | In MC v11.0, the Query Profile page was working without any issues. MC v12.0 was localized and all labels were translated. However, the Query Profile page was not localized by oversight. This issue has been resolved. |
| VER-95684 | Kafka Integration, UDX |
In earlier releases, providing a value for the "enable_chunker" parameter had a negative impact on system performance. This issue is now resolved. The "enable_chunker" parameter is set to "True" resulting in improved system performance. |
| VER-95698 | Data load / COPY | Fixed a bug that may cause errors when loading more than 8k files at once using EXECUTE DATA LOADER. |
| VER-95699 | Data load / COPY | Performance improvement: Loading a small amount of files using EXECUTE DATA LOADER WITH FILES when the folder contains a large amount of files should be much faster now, especially when the source location is an object store. |
| VER-95880 | EON | To avoid potential FNF or leaked files, an issue was fixed by scanning all storages in the snapshot to restore/replicate, and removing the storages from tombstone and the reaper queue, while keeping others untouched in tombstone/reaper queue. |
| VER-95925 | Data load / COPY | Previously, when querying certain ORC/Parquet files in a certain way, a hang would occur. This issue has been resolved. |
| VER-96299 | Optimizer | Between v12 and v24, a previous bug fix made it so that null rows passed hash SIP filters. This led to a performance drop on queries that relied on SIPS to filter out nulls early. This has been resolved; now, SIP filters remove null rows again. |
| VER-96309 | Data load / COPY | Previously, expanding wild cards as part of COPY command failed on systems with certain versions of GLIBC. This issue has now been fixed. |
| VER-96377 | Admin Tools, Installation Program, Installation: Server RPM/Deb | urllib3 version is now upgraded from 1.26.18 to 1.26.19 |
| VER-96445 | Security | Clients not sending packets during initialization of TLS connections will no longer cause CPU usage to spike. |
| VER-96459 | Backup/DR | If we point the --communal-storage-location at the root of a bucket, and without a trailing slash, the show-restore-points does not automatically add the trailing slash when handling the path. We fixed this issue by canonicalize the path when we get it from the show-restore-points command. |
| VER-96609 | Execution Engine | In some cases, FCSVParser used to core dump when loading multiple files with glob patterns. The issue was resolved. |
| VER-96728 | Installation Program | nofile check does not work when installing Vertica on Ubuntu 18.04. This essue has been fixed. We are setting the nofile value via python module resource if the value is less than the recommended value. |
| VER-97123 | Optimizer | The view referenced in the UPDATE's target list had its subquery pruned during query rewrite, which misaligned a predicate reference to it and caused it to return a null value. This issue has been resolved; now, subquery targets are not pruned from the top-level UPDATE query's target list, instead only pruning FROM subqueries. |
| VER-97203 | HTTP | HSTS header was missing from the HTTPS Server. After the fix, Vertica Embedded HTTPS service enforces HSTS header. |
| VER-97299 | Client Drivers - VSQL | There was an issue that was preventing disabling or enabling of subcluster interior load balancing from taking effect immediately because an internal cache was not being cleared. Using ALTER DATABASE to set the EnableInteriorLoadBalancing parameter would have no impact on the result of the DESCRIBE_LOAD_BALANCE_DECISION function, which in turn would not change load balancing behavior of clients. This problem has been resolved. |
| VER-97476 | Procedural Languages | On Eon mode as of 24.3, stored procedures triggered by the scheduler could not see the current subscriptions, leading to failures for certain procedures. This has been resolved; now, scheduled stored procedures can see the subscriptions. |
| VER-97680 | Execution Engine | Previously, the priority field was not persisting in the catalog. When the database was restarted, the default value of 0 would be applied to every rule. Now, the priority field is accounted for and persists. |
| VER-97700 | License | In some cases, automated database size audits used to run at a different time of the day from the one specified by GET_AUDIT_TIME. The issue has been resolved. |
| VER-97819 | DDL | The knobs for Health Watchdog were not available. The knobs added for the watchdog metrics are now guided and documented. |
| VER-98563 | Optimizer | Queries utilizing WITH statements used on multiple query levels with different target lists on each level would sometimes return an error. The issue has been fixed. |