Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I am running into an issue while setting Teradata endpoint in QlikRepliate v2023.11
While configuring connection properties, I complete required information like server name and authentification information, and click "Test Connection", then following errors occur.
ERROR: check_async_command_complete failed
ERROR: Cancel async command failed.
Rarely the error below displayed on the screen.
no rest handler for url </attunityreplicate/rest/servers/local/commands/?action=check_async_complete&task=null>
Environment:
- QlikReplicate : v2023.11 on Linux
Teradata ODBC 17.20
TeradataToolsAndUtilitiesBase 17.20
- Target database : Teradate 17.20
ODBC connection to the database is fine.
During the Test Connection, repctl process seems to end abnormally. So it seems to be a issue of Qlik replicate.
Are there any workarounds for this issue?
I will attach repserv.log.
If some more information is required, could you let me know?
Regards,
Kyoko Tajima
Hello @iti-attunity-sup ,
Thanks for reaching out to Qlik Community.
How about if you use a general ODBC driver connect to the DSN? What's the result if you press "Test Connection"? For example:
Regards,
John.
Hello @iti-attunity-sup ,
In my labs, Qlik Replicate 2023.11.0.159 (GA Release) works fine with the ODBC v17.10 + Teradata Server 17.10.
I will try to get an env with 17.20 ODBC + 17.20 TD Server later, will keep you posted.
Regards,
John.
Hello @iti-attunity-sup ,
I've confirmed Replicate 2023.11.0.159 works fine on Linux with
Please take note you need 2 internal parameters in Teradata target endpoint:
additionalConnectionProperties, value is "SSLMode=allow"
provider, value is "Teradata Database ODBC Driver 17.20"
Hope this helps.
Regards,
John.
Hello team,
If our response has been helpful, please consider clicking "Accept as Solution". This will assist other users in easily finding the answer.
Regards,
Sushil Kumar
Hello John,
Thank you for your confirmation and update.
But still encounter the same errors.
I setup our environment according to the document below:
Are there some more required settings to work fine?
My environment is :
* Qlik Replicate 2023.11.0.159 on Linux
$ md5sum QlikReplicate_2023_11_0_Linux_X64.tar.gz
54ccd4881731b48575beb75368f00068 QlikReplicate_2023_11_0_Linux_X64.tar.gz
* Teradata ODBC and Teradata Tools And UtilitiesBase 17.20
$ ./ttulistproducts_unix.sh
TTUListProducts v.17.20.20.00
Copyright 2016-2023 Teradata. All rights reserved.
....................
Active Release: 17.20
The following packages are installed:
Teradata Access Module for Azure - 17.20.00.01
Teradata BTEQ - 17.20.00.08
Teradata FastExport Utility - 17.20.00.03
Teradata FastLoad Utility - 17.20.00.04
Teradata Access Module for Google Cloud Storage - 17.20.00.02
Teradata Access Module for JMS - 17.20.00.00
Teradata Kafka Access Module - 17.20.00.03
Teradata MultiLoad Utility - 17.20.00.04
WebSphere Access Module for Teradata - 17.20.00.00
Teradata Named Pipes Access Module - 17.20.00.00
Teradata Access Module for S3 - 17.20.00.04
Teradata C Preprocessor - 17.20.00.01
ODBC Driver for Teradata - 17.20.00.20
Teradata Wallet - 17.20.00.28
Teradata Parallel Transporter Base - 17.20.00.15
Teradata Parallel Data Pump Utility - 17.20.00.03
Teradata Data Connector - 17.20.00.03
Teradata CLIv2 - 17.20.00.26
Shared ICU Libraries for Teradata - 17.20.00.08
Teradata Public Key - 17.20.00.04
* Teradata odbcinst.ini file contains
$ cat /opt/teradata/client/17.20/odbc_64/odbcinst.ini
[ODBC Drivers]
Teradata Database ODBC Driver 17.20=Installed
[Teradata Database ODBC Driver 17.20]
Description=Teradata Database ODBC Driver 17.20
Driver=/opt/teradata/client/17.20/odbc_64/lib/tdataodbc_sb64.so
# Note: Currently, Data Direct Driver Manager does not support Connection Pooling feature.
CPTimeout=60
* /usr/lib64 contains symbolic links to the DataDirect driver manager shared libraries:
$ ll /usr/lib64/libodbc*.so
lrwxrwxrwx 1 root root 47 Nov 24 14:47 /usr/lib64/libodbcinst.so -> /opt/teradata/client/17.20/lib64/libodbcinst.so
lrwxrwxrwx 1 root root 43 Nov 24 14:47 /usr/lib64/libodbc.so -> /opt/teradata/client/17.20/lib64/libodbc.so
* hosts file (/etc/hosts) includes the entry below (IP is masked)
***.**.**.*** TDExpress1720_Sles12 dbccop1 sysdbacop1
* Set environment value below before starting
export LD_LIBRARY_PATH=/opt/teradata/client/17.20/lib64:/opt/attunity/replicate/lib:/lib64:/usr/lib64:
export ODBCINI=/opt/teradata/client/17.20/odbc_64/odbc.ini
export AREP_ODBC_DRIVER_MANAGER=/opt/teradata/client/17.20/odbc_64/lib/libodbc.so
* ODBC connection works fine:
cd /opt/teradata/client/17.20/bin
export ODBCINST=/opt/teradata/client/17.20/odbc_64/odbcinst.ini
export ODBCINI=/opt/teradata/client/17.20/odbc_64/odbc.ini
export LD_LIBRARY_PATH=/opt/teradata/client/17.20/lib64:$LD_LIBRARY_PATH
./tdxodbc64 -c SQLDriverConnect -C "DRIVER={Teradata Database ODBC Driver 17.20};DBCName=dbccop1;UID=dbc;PWD=dbc" -t;
Connecting with SQLDriverConnect("DRIVER={Teradata Database ODBC Driver 17.20};DBCName=dbccop1;UID=dbc;PWD=dbc")...
.....ODBC connection successful.
ODBC version = -03.52.0000-
DBMS name = -Teradata-
DBMS version = -17.20.0309 17.20.03.09-
Driver name = -tdataodbc_sb64.so-
Driver version = -17.20.00.020-
Driver ODBC version = -03.52-
ODBC connection closed.
* Internal parameter set
additionalConnectionProperties, value is "SSLMode=allow"
provider, value is "Teradata Database ODBC Driver 17.20"
Regards,
Kyoko Tajima
Hello @iti-attunity-sup ,
Thanks for the feedback. Would you please add the below codes (copy from "/opt/teradata/client/17.20/odbc_64/odbcinst.ini" ) to "/etc/odbcinst.ini" ?
[Teradata Database ODBC Driver 17.20] Description=Teradata Database ODBC Driver 17.20 Driver=/opt/teradata/client/17.20/odbc_64/lib/tdataodbc_sb64.so # Note: Currently, Data Direct Driver Manager does not support Connection Pooling feature. CPTimeout=60 |
BTW, please remove the 2 variable definitions "ODBCINST" and "ODBCINI".
Try again and let me know if it works.
Regards,
John.
Thank you for your prompt reply.
I copied the /opt/teradata/client/17.20/odbc_64/odbcinst.ini to /etc/odbcinst.ini, still same error occurs.
$cat /etc/odbcinst.ini
[ODBC Drivers]
Teradata Database ODBC Driver 17.20=Installed
[Teradata Database ODBC Driver 17.20]
Description=Teradata Database ODBC Driver 17.20
Driver=/opt/teradata/client/17.20/odbc_64/lib/tdataodbc_sb64.so
# Note: Currently, Data Direct Driver Manager does not support Connection Pooling feature.
CPTimeout=60
BTW, I tried to start without ODBCINI valiable, then it failed.
Is this the operation you intended?
$ export LD_LIBRARY_PATH=/opt/teradata/client/17.20/lib64:/opt/attunity/replicate/lib:/lib64:/usr/lib64
$ export AREP_ODBC_DRIVER_MANAGER=/opt/teradata/client/17.20/odbc_64/lib/libodbc.so
$ areplicate start
Failed to start service
$ export ODBCINI=/opt/teradata/client/17.20/odbc_64/odbc.ini
$ areplicate start
$ areplicate status
running: /opt/attunity/replicate/bin/repctl -d /opt/attunity/replicate/data service start port=3550 rest_port=3552
Regards,
Kyoko Tajima
Hello @iti-attunity-sup ,
Thanks for your update.
Let's use the default odbcinit.ini file, which is "/etc/odbcinst.ini" so we need not "export ODBCINI".
Starting with version 16.20, the new Teradata ODBC Driver supports the industry standard iODBC Driver Manager and unixODBC Driver Manager on Unix platforms, we need not "export AREP_ODBC_DRIVER_MANAGER".
Please remove the two environment variables and let me know if it works for you.
Regards,
John.
Hello @john_wang
Thank you for your kind reply.
Though I remove the two environment variables, still error occurs.
(Error messages change depending on the timing, but it always fails.)
My current settings are below:
$ cat /etc/odbcinst.ini
[ODBC Drivers]
Teradata Database ODBC Driver 17.20=Installed
[Teradata Database ODBC Driver 17.20]
Description=Teradata Database ODBC Driver 17.20
Driver=/opt/teradata/client/17.20/odbc_64/lib/tdataodbc_sb64.so
# Note: Currently, Data Direct Driver Manager does not support Connection Pooling feature.
$ export LD_LIBRARY_PATH=/opt/teradata/client/17.20/lib64:/opt/attunity/replicate/lib:/lib64:/usr/lib64
$ areplicate start
$ areplicate status
running: /opt/attunity/replicate/bin/repctl -d /opt/attunity/replicate/data service start port=3550 rest_port=3552
Can you think of any other ideas to resolve the errors?
I appreciate your help.
Regards,
Kyoko Tajima