XCOM for Linux 12.0 history database connection fails

Products

• XCOM Data Transport
• XCOM Data Transport - Linux PC

Issue/Introduction

New XCOM for Linux 12.0 installation.
Everything is working except the History Database access in MySQL is failing.
A trace file collected with XTRACE=10 in the xcom.glb file shows

sqlutil.c 7039: pcparmblock->xcomhist(8) = cdinvpcd
sqlutil.c 7044: XCOM_ODBC=/usr/lib64/libmyodbc8w.so
util.c 2956: In xdlopen, lib-length = 25, lib-path = </usr/lib64/libmyodbc8w.so>
sqlutil.c 7103: History_Connect failed to obtain one of the ODBC function pointer.
fsmachin.c 3541: History_Connect return code = -1

Environment

XCOM Data Transport for Linux

Cause

Using XCOM_ODBC=/usr/lib64/libmyodbc8w.so in the xcom.glb file.

Resolution

Per the doc. page for parameter XCOM_ODBC it should point to the file /usr/lib64/libodbc.so.
That file comes with the unixODBC installation and is independent of the DB server being used i.e. it doesn't change whether using MySQL or DB2 or Oracle. The xcomd service will need to be restarted to pick up the change.
Also in the /etc/odbc.ini file, it needs to reference the driver name of the ANSI version of the ODBC driver (see file /etc/odbcinist.ini) and not the Unicode version.

Additional Information

Verify the connectivity of unixODBC DSN using isql utility using the command. In this command, histdb is the DSN name.

isql histdb -v

The output look like this:
+---------------------------------------+
| Connected! |
| |
| sql-statement |
| help [tablename] |
| quit |
| |
+---------------------------------------+
SQL> quit

Setup the values of the below parameters in xcom.glb

XCOMHIST=<DSN name>
XCOMHIST_PASSWORD=<DB PWD>
XCOMHIST_TBL=xcom_history_tbl
XCOMHIST_USER=<DB User>
XCOMHIST_OWNER=<Owner, generally leave it blank or same name as DB in MySQL>

To encrypt the History DB password in the  xcom.glb file please refer to: Encrypting XCOM xcom.glb file parameters with xcomencr