Network Observability DX NetOps Performance Management Data Repository multi-node cluster install is failing.
The DR install log for the dr_install.sh run shows these messages:
Unable to establish vsql script connection: Unable to connect to 'drdata'
Unable to install default extension packages without a vsql script connection
Database creation SQL tasks included on or more failures (see above).
The DA connects to the DR DB but the karaf.log shows this error when starting.
ERROR | ExtenderThread-1 | 2025-05-24T16:47:36,068 | ExtenderConfiguration | BundleApplicationContextListener 50 | emini.blueprint.extender | | Application context refresh failed (OsgiBundleXmlApplicationContext(bundle=com.ca.im.data-manager.core.database.dao.impl, config=osgibundle:/META-INF/spring/*.xml))
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'alarmSchemaManager': Invocation of init method failed; nested exception is org.springframework.jdbc.BadSqlGrammarException: StatementCallback; bad SQL grammar [select LOWER(projection_name), LISTAGG(LOWER(projection_column_name)) within group(order by LOWER(projection_column_name)) columns from projection_columns where table_name in ('alarm','alarm_clear') group by projection_name]; nested exception is java.sql.SQLSyntaxErrorException: [Vertica][VJDBC](3457) ERROR: Function LISTAGG(varchar) does not exist, or permission is denied for LISTAGG(varchar)
...
Caused by: org.springframework.jdbc.BadSqlGrammarException: StatementCallback; bad SQL grammar [select LOWER(projection_name), LISTAGG(LOWER(projection_column_name)) within group(order by LOWER(projection_column_name)) columns from projection_columns where table_name in ('alarm','alarm_clear') group by projection_name]; nested exception is java.sql.SQLSyntaxErrorException: [Vertica][VJDBC](3457) ERROR: Function LISTAGG(varchar) does not exist, or permission is denied for LISTAGG(varchar)
Running "./adminTools -t view_cluster" works properly. It shows all expected nodes in an UP state.
Connecting to the DB CLI through the adminTools UI works properly. We're able to run things like "select * from nodes;" with the correct expected results returned.
Connecting to the vsql CLI using /opt/vertica/bin/vsql as the dradmin user, or as the dauser, always fails. It returns the message:
vsql: could not connect to server: Cannot assign requested address
Is the server running on host "???" and accepting
TCP/IP connections on port 5433?
All supported Network Observability DX NetOps Performance Management Data Repository releases
The /etc/hosts file on the systems has the loopback address (127.0.0.1) entry commented out.
Uncomment the loopback address (127.0.0.1) entry in the /etc/hosts file to allow it's use.
After resolving the cause it's recommended that the DR DB be uninstalled and reinstalled properly without errors.
Follow the Uninstall the Data Repository documentation topic to uninstall the DR DB.
If the environment made it as far as successfully adding a Data Aggregator for the problem DR DB cluster as a Data Source in Portal, further fixes are recommended.
Follow the steps in the Recreate the Vertica Database in DX NetOps Performance Management KB article to recreate the DR DB database and reset the DA.