25.4.0-6 Clients are now available for download.

Release Notes: https://docs.vertica.com/release-notes/26.2.x/resolved-issues/

Vertica Clients 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/.

Thank you.

26.2.0 Clients are now available for download.

Release Notes: https://docs.vertica.com/release-notes/26.2.x/resolved-issues/

Vertica Clients 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/.

Thank you.

The latest 2.4.3 patch has been released:
*24.3.0-14

Release Notes: https://docs.vertica.com/release-notes/24.3.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/.

Thank you.

The latest 26.1.0 patch has been released:
*26.1.0-5

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/.

Thank you.

The latest 25.3 patch has been released:
*25.3.0-9

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/.

Thank you

The latest 25.4 patch has been released:
*25.4.0-6

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/.

Thank you

The latest 25.2 patch has been released:
*25.2.0-8

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/.

Thank You

The latest 25.1 patch has been released:
*25.1.0-8

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/.

Thanks

The latest 2.4.1 patch has been released:
*24.1.0-14

Release Notes: https://docs.vertica.com/release-notes/24.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/.

Thank you.

The latest 24.4.0 patch has been released:
*24.4.0-10

Release Notes: https://docs.vertica.com/release-notes/24.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/.

Thank you.

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/.

Thank you.

Summary:
I'm encountering invalid UTF-8 characters in string columns after performing a UNION ALL of two CTEs, where one CTE references the other via a LEFT JOIN on a grouped subquery. Each CTE individually contains only valid UTF-8 data. The corruption only appears after the UNION ALL.

Error:

Severity: ERROR
Message: Regexp encountered an invalid UTF-8 character
Sqlstate: 22021
Error Code: 4551
Detail: String = E'\177\377\377\377\377\377\377'

How to reproduce:

The pattern that triggers this is:

1. cte1 — produces string columns from joined tables
2. cte2 — references cte1 via a LEFT JOIN on an aggregated subquery (GROUP BY + MAX)
3. Final query performs UNION ALL of cte1 and cte2
4. A downstream REGEXP_SUBSTR on the unioned result fails with invalid UTF-8

Key observations:

• SELECT * FROM cte1 WHERE NOT isutf8(col1) returns 0 rows
• SELECT * FROM cte2 WHERE NOT isutf8(col1) returns 0 rows
• The UNION ALL of both returns rows with invalid UTF-8
• Removing the LEFT JOIN from cte2 makes the problem disappear
• The issue seems related to how the optimizer inlines the CTE when it is referenced multiple times (once in cte2's left join, once in the final UNION ALL)

Workaround:
Using the query hint /*+ENABLE_WITH_CLAUSE_MATERIALIZATION*/ or materializing cte1 into a temp table appears to resolve the issue.

Questions:
1. Is this a known issue?
2. Is there a fix planned or available in a later patch?
3. Is ENABLE_WITH_CLAUSE_MATERIALIZATION a safe setting to enable globally as a workaround?

Thank you for any guidance.

The latest 25.4 patch has been released:
*25.4.0-5

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/.

Thanks

The latest 26.1.0 patch has been released:
*26.1.0-4

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/.

Thank you.

Is there a way we can find if the query which is active for so long is progressing at all or not?

We see some sessions/queries active in the query_requests/sessions but not really sure if they are moving or just a stale connection which is stuck to close the session.

Do we have any easier way to find if the query is moving or not?

Please provide the vertica-ce image.

https://docs.vertica.com/25.1.x/en/containerized/images/

Community Edition 25.1.0-0
A single-node Enterprise Mode image for test environments. For more information, see Vertica community edition (CE).

Username Enumeration Observable Response Discrepancy vulnerability has been discovered in OpenText™ Vertica. The vulnerability could lead to Password Brute Forcing.

Systems affected:
Vertica version/s 10.x, 11.x, and 12.x

Affected version:
Username Enumeration Observable Response Discrepancy vulnerability affects OpenText Vertica versions 10.x, 11.x, and 12.x

CVE reference: CVE-2025-12455

CVSS v4.0 score: 5.1 / Medium

Impact:
The vulnerability could lead to Password Brute Forcing in Vertica management console application.

Solution:
For all Vertica versions prior to 23.3.x, customers need to upgrade to Vertica 23.3.0-0 or later.

More information
For more information, contact us through the Support Portal.

Copyright © 2024 Open Text. All rights reserved. OpenText is a trademark or registered trademark of Open Text. The list of trademarks is not exhaustive of other trademarks. Registered trademarks, product names, company names, brands and service names mentioned herein are property of Open Text or other respective owners.

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

Systems affected:
Vertica version/s 10.x, 11.x, 12.x, 23.x, 24.x, 25.1.x

Affected version:
Reflected XSS attack of cross-site scripting vulnerability affects OpenText Vertica versions 10.x, 11.x, 12.x, 23.x, 24. x., and 25.1.x

CVE reference: CVE-2025-12454

CVSS v4.0 score: 5.1 / Medium

Impact:
The vulnerability could lead to Reflected XSS attack of cross-site scripting in Vertica management console application.

Solution:
For all Vertica versions prior to 25.2.x, customers need to upgrade to Vertica 25.2.0-0 or later.

More information
For more information, contact us through the Support Portal.

Copyright © 2024 Open Text. All rights reserved. OpenText is a trademark or registered trademark of Open Text. The list of trademarks is not exhaustive of other trademarks. Registered trademarks, product names, company names, brands and service names mentioned herein are property of Open Text or other respective owners.

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

Systems affected:
Vertica version/s 10.x, 11.x, 12.x, 23.x, 24.x, 25.1.x, 25.2.x, and 25.3.x

Affected version:
Reflected XSS attack of cross-site scripting vulnerability affects OpenText Vertica versions 10.x, 11.x, 12.x, 23.x, 24. x., 25.1.x, 25.2.x, and 25.3.x

CVE reference: CVE-2025-12453

CVSS v4.0 score: 5.1 / Medium

Impact:
The vulnerability could lead to Reflected XSS attack of cross-site scripting in vertica management console application.

Solution:
For all Vertica versions prior to 25.4.x, customers need to upgrade to Vertica 25.4.0-0 or later

More information
For more information, contact us through the Support Portal.

Copyright © 2024 Open Text. All rights reserved. OpenText is a trademark or registered trademark of Open Text. The list of trademarks is not exhaustive of other trademarks. Registered trademarks, product names, company names, brands and service names mentioned herein are property of Open Text or other respective owners.

26.1.0 Clients are now available for download.

Release Notes: https://docs.vertica.com/release-notes/26.1.x/resolved-issues/

Vertica Clients 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/.

Thank you.

The latest 2.3.x patch has been released:
*23.3.0-14

Release Notes: https://docs.vertica.com/release-notes/23.3.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/.

Thank you.

Cleartext Storage of Sensitive Information vulnerability has been discovered in OpenText™ Vertica. The vulnerability could read Vertica agent plaintext apikey.

Systems affected:
Vertica version/s 23.x,24.x,25.x

Affected version:
Cleartext Storage of Sensitive Information vulnerability affects Opentext Vertica versions 23.x,24.x,25.x

CVE reference: CVE-2024-9432

CVSS v4.0 score: 6.9 / Medium

Impact:
The vulnerability could read Vertica agent plaintext apikey.

Solution:
Vertica versions Backport Summary Table

Version Issues Included

26.1.0.0
25.4.0-1
25.3.0-4
25.2.0-5
25.1.0-6
24.4.0-7
24.3.0-11
24.2.0-12
24.1.0-14
23.4.0-22
23.3.0-14

For questions, please contact customer support

More information
For more information, contact us through the Support Portal. https://portal.microfocus.com/s/customportalsearch?language=en_US

Copyright © 2024 Open Text. All rights reserved. OpenText is a trademark or registered trademark of Open Text. The list of trademarks is not exhaustive compared with other trademarks. Registered trademarks, product names, company names, brands and service names mentioned herein are property of Open Text or other respective owners.

The latest 24.2.0 patch has been released:
*24.2.0-12

Release Notes: https://docs.vertica.com/release-notes/24.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/.

SELECT '3.14' ;  `'3.14'`
SELECT '3.14' :: FLOAT ;  `3.14`
SELECT '3.14' :: INT  ;  ` Invalid input syntax for integer: "3.14" `
SELECT '3.14' ::! INT  ;  `Invalid input syntax for integer: "3.14" `
SELECT '3.14' !:: INT  ;  `7` (this was a fun one to figure out)
SELECT CAST('3.14' AS INT);  `Invalid input syntax for integer: "3.14"`
SELECT '3.14' :: FLOAT :: INT ; `3`
SELECT ROUND( '3.14') ; `3`

When I removed the EXCEPTION WHEN OTHERS part during testing, the error message on the constraint was correct, but I need to manage EXCEPTIONS. Do you have any recommendations on how to work with that within a stored procedure? How to handle all exceptions?

Here is simple script to test this issue:

CREATE TABLE test_schema.SRC_TABLE (
COLUMN_1 INT,
COLUMN_2 TIMESTAMP,
COLUMN_3 VARCHAR(32)
)
;

INSERT INTO test_schema.SRC_TABLE VALUES(1,getdate(),NULL);
INSERT INTO test_schema.SRC_TABLE VALUES(2,NULL,'string2');
INSERT INTO test_schema.SRC_TABLE VALUES(NULL,getdate(),'string3');

CREATE TABLE test_schema.TGT_TABLE (
COLUMN_1 INT NOT NULL,
COLUMN_2 TIMESTAMP NOT NULL,
COLUMN_3 VARCHAR(32) NOT NULL
)
;

CREATE OR REPLACE PROCEDURE test_schema.SP_TGT_TABLE()
AS
$$
BEGIN

EXECUTE
        'INSERT INTO test_schema.TGT_TABLE (COLUMN_1, COLUMN_2, COLUMN_3)
            SELECT
                 COLUMN_1
                ,COLUMN_2
                ,COLUMN_3
            FROM test_schema.SRC_TABLE';

/*** This query correctly handles exception ***/
/* 
        'INSERT INTO test_schema.TGT_TABLE (COLUMN_1, COLUMN_2, COLUMN_3)
            SELECT
                 NULL AS COLUMN_1
                ,NULL AS COLUMN_2
                ,NULL AS COLUMN_3
            FROM test_schema.SRC_TABLE';
*/

EXCEPTION WHEN OTHERS THEN
    RAISE NOTICE 'Error message: %', SQLERRM;

END;
$$;

CALL test_schema.SP_TGT_TABLE();

I work with Vertica version 24.4.

Thank you for feedback and ideas.

Regards,
Avinash

select * from cur;

displays currently executed queries and there are two columns: acquisition_duration and transaction_duration.

Usually the two are very close like this

acquisition_duration = 42min 4 sec
transaction_duration = 42min 5 sec

but sometimes acquisition duration is smaller, like

acquisition_duration = 34min
transaction_duration = 42min

how do I interpret this?

would that mean the second transaction held the resources for 8 minutes less because it was sitting in the queue waiting to get them for 8 minutes?

EXPORT TO PARQUET (directory='/data/export/test_table0', compression='zstd') AS SELECT * FROM test_table0;

and once all the exports are finished, I import them like so (all at the same time):

COPY test_table0 FROM '/data/export/test_table0/*.parquet' ON EACH NODE PARQUET (do_soft_schema_match_by_name='True');

I need both: ON EACH NODE and do_soft_schema_match_by_name, so they're there for a reason.

My problem is, that by varying pool's query budget and the command count, on EXPORT I can saturate the cluster's resources fully: up to 100% CPU usage and up to 100% RAM usage.

But whatever I do, I can't seem to get the COPY commands to consume above 50-55% CPU. It gets to 50% CPU at 5 COPY commands or so, and adding more COPY commands in parallel just makes them all finish proportionally later. Which makes me think there's room for optimization. Any idea what that could be?

Thank you!

I'm getting below error while reviving the vertica db which is created in the EON mode. Error seems to be that there is already an entry of the node001 exists somewhere in the configuration files. Please check the below error and let me know if you need any other details.

2025-09-16 13:04:50.357 admintools/21725:0x7fb644d05740 [DBReviveHelper.runLoadRemoteCatalogModule] Load Remote Catalog succeeded on all hosts

2025-09-16 13:04:50.357 admintools/21725:0x7fb644d05740 [adminExec.dbRevive] EVENT: type=Status job None {"type":"REVIVE", "state":"VALIDATING", "dbname":"testdb", "msg":"Updating Node configuration.", "maxSteps":"7", "currStep":"5"}

2025-09-16 13:04:50.357 admintools/21725:0x7fb644d05740 [adminExec.do_create_node] creating node w/ ['v_testdb_node0001', '172.130.XXX.XX', '/vertica/catalog', '/vertica/datadir']

2025-09-16 13:04:50.359 admintools/21725:0x7fb644d05740 [Configurator.init] MAX_ARG_STRLEN is set to: 131072

2025-09-16 13:04:50.359 admintools/21725:0x7fb644d05740 [adminExec.do_create_node] node v_testdb_node0001 already defined as ['v_testdb_node0001', '172.130.XXX.XX', '/vertica/catalog', '/vertica/catalog']

2025-09-16 13:04:50.361 admintools/21725:0x7fb644d05740 [adminExec.dbRevive] Traceback (most recent call last):

File "/opt/vertica/oss/python3/lib/python3.13/site-packages/vertica/engine/adminExec.py", line 2217, in dbRevive

helper.saveNodeDict(adminExec=self)

~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^

File "/opt/vertica/oss/python3/lib/python3.13/site-packages/vertica/engine/db_revive.py", line 628, in saveNodeDict

raise ATError("Can't create node {}, see {} for details.".format(node.name, DBinclude.adminToolLog))

vertica.engine.api.errors.ATError: Can't create node v_testdb_node0001, see /opt/vertica/log/adminTools.log for details.