vsq: Bad terminal type: "xterm". Will assume vt100.

raulk89

[dbadmin@yyyyyyyyyy ~]$ vsql
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

SSL connection (cipher: ECDHE-RSA-AES256-GCM-SHA384, bits: 256, protocol: TLSv1.2)

Bad terminal type: "xterm". Will assume vt100.
yyyyydb=> \q

I just upgraded from 12.0.4 to 23.3 and noticed that when initiating vsql, I get

Bad terminal type: "xterm". Will assume vt100.

Is there something need to be done ?

Regards
Raul

SruthiA

it is a known issue.. engineering is working on the fix. it is specific to 23.3. it will not cause any issues.

raulk89

Ok, thanks.

Raul

mgksk03

I updated to Vertica version 23.3.0.7 released on 2024-01-17, but the same problem occurs.
Are there any plans for additional patches?

SruthiA

this issue has been fixed in 24.1. please upgrade to 24.1

mgksk03

I am using CentOS 7.9 version. It is said that CentOS 7.x is not supported starting from Vertica 24.1 version.
Updated to version 23.3, the latest version available. Is there any other way other than upgrading to version 24.1? Is a patch possible if a customer formally requests it?

SruthiA

This issue was not backported to old versions. so you need to perform OS upgrade and upgrade vertica.. for 24.1 on RHEL 9 you will not receive that error.

vsql
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=> select version();

version

Vertica Analytic Database v24.1.0-0
(1 row)

test=>

mosheg

Indeed the problem was fixed in version 24.1 and you can install a Vertica server, vsql client or MC version 24.1 or later to fix the issue.
However, this can lead to confusion when multiple vsql clients are present on the system. These include one installed through the Vertica server installation (/opt/vertica/bin/vsql) and another possibly installed separately or as part of the Management Console (/opt/vconsole/bin/vsql), each with differing versions.
It is advisable to ensure that the correct version of vsql is invoked to address the terminal type error using the command:
$ vsql --version