Vertica database setup with voltage SecureData

jitmunchongjitmunchong Vertica Customer
edited April 2020 in General Discussion

after initial databse session,
testing syntax as follow,
SELECT VoltageSecureProtect('123-45-6789' USING PARAMETERS format='Numeric');
database retrun following error.
08:47:19 FAILED [SELECT - 0 rows, 0.024 secs] [Code: 5861, SQL State: VP001] [Vertica]VJDBC ERROR: Error calling setup() in User Function VoltageSecureProtect at [/data/qb_workspaces/jenkins2/ReleaseBuilds/Grader/REL-9_2_1-x_grader/build/udx/supported/voltagesecure/VoltageBase.hpp:222], error code: 15, message: Error initializing: Unrecognized Voltage SecureData error encountered. Please contact Voltage SecureData support for help.

What are the additional steps required for me to resolve above error?

I have performed the following steps as documented in Vertica.
1. Verify that Vertica has the right root certificate authority (CA) to authenticate with SecureData.
2. Grant users access to the SecureData library.
3. Configure parameters to tell Vertica how to access SecureData.

Any help with be appreciated, Thanks.


  • Options
    SruthiASruthiA Vertica Employee Administrator
    edited April 2020

    We will need logs to troubleshoot the issue. Could you please open a support case and share us the logs from voltage and vertica to review the issue?

  • Options
    jitmunchongjitmunchong Vertica Customer

    attache is the vertica log file

  • Options
    SergeBSergeB - Select Field - Employee

    Can you try using these Voltage formats instead of Numeric?

    SELECT VoltageSecureProtect('123-45-6789' USING PARAMETERS format='ssn');


    SELECT VoltageSecureProtect('123-45-6789' USING PARAMETERS format='Auto');

  • Options
    SruthiASruthiA Vertica Employee Administrator

    @jitmunchong I just reviewed the log and it is today's log. Please share the log from the day incident occured or please try to run the query which is causing the issue and share the log.

  • Options
    jitmunchongjitmunchong Vertica Customer
    HINT:  Cluster State: NDBVDB
        UP: 3 of 3 (v_ndbvdb_node0001, v_ndbvdb_node0002, v_ndbvdb_node0003)
    LOCATION:  initSession, /data/qb_workspaces/jenkins2/ReleaseBuilds/Grader/REL-9_2_1-x_grader/build/vertica/Session/ClientSession.cpp:533

    2020-04-02 08:47:18.903 DistCall Dispatch:0x7f3d037fa700-b000000009e197 [Txn] Starting Commit: Txn: b000000009e197 'select 1' 2934
    2020-04-02 08:47:18.903 DistCall Dispatch:0x7f3d037fa700 [Txn] Commit Complete: Txn: b000000009e197 at epoch 0x2bd and global catalog version 2934
    2020-04-02 08:47:19.001 AnalyzeRowCount:0x7f3d290d1700 [Command] TMTask: row count analyze - start
    2020-04-02 08:47:19.004 AnalyzeRowCount:0x7f3d290d1700-a00000003dece9 [Txn] Begin Txn: a00000003dece9 'getRowCountsForProj'
    2020-04-02 08:47:19.005 AnalyzeRowCount:0x7f3d290d1700-a00000003dece9 [Txn] Rollback Txn: a00000003dece9 'getRowCountsForProj'
    2020-04-02 08:47:19.015 AnalyzeRowCount:0x7f3d290d1700 [Command] TMTask: row count analyze - Done
    2020-04-02 08:47:19.016 AnalyzeRowCount:0x7f3d290d1700 [Util] Task 'AnalyzeRowCount' enabled
    2020-04-02 08:47:19.022 DistCall Dispatch:0x7f3d0afff700-b000000009e195 [Txn] Starting Commit: Txn: b000000009e195 'SELECT VoltageSecureProtect('123-45-6789' USING PARAMETERS format='auto')' 2934
    2020-04-02 08:47:19.022 DistCall Dispatch:0x7f3d0afff700 [Txn] Commit Complete: Txn: b000000009e195 at epoch 0x2bd and global catalog version 2934

  • Options
    SruthiASruthiA Vertica Employee Administrator

    This log shows that txn succeeded without any errors. Are you facing issue only with this query or anything pertaining to voltage securedata integration? Does the curl test from the below documentation succeed?


Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file