Scribd
Upload
515 views

HANA Client Installtion and Configuration

1. The document discusses installing HANA and Teradata drivers and configuring them for use as data sources. It provides steps to install the HANA client, add HANA drivers, and configure environment variables. 2. For Teradata, it outlines installing various RPM packages, extracting and installing the ODBC driver RPM, and notes that the DSConnectionManager.sh script can be used to configure the Teradata drivers. 3. The installation process for both drivers involves confirming packages, extracting and installing driver files, modifying configuration files, and setting environment variables so that the drivers can be used as data sources.

Uploaded by

Sreeram Kaki
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
515 views

HANA Client Installtion and Configuration

1. The document discusses installing HANA and Teradata drivers and configuring them for use as data sources. It provides steps to install the HANA client, add HANA drivers, and configure environment variables. 2. For Teradata, it outlines installing various RPM packages, extracting and installing the ODBC driver RPM, and notes that the DSConnectionManager.sh script can be used to configure the Teradata drivers. 3. The installation process for both drivers involves confirming packages, extracting and installing driver files, modifying configuration files, and setting environment variables so that the drivers can be used as data sources.

Uploaded by

Sreeram Kaki
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 6

Installing HANA Drivers and configuring for use in DATA Sources.

[root@bbcsapd221l SAP_HANA_CLIENT]# ./hdbinst


SAP HANA Database Client installation kit detected.
SAP HANA Lifecycle Management - Client Installation 1.00.73.00.389160
*********************************************************************

Enter Installation Path [/usr/sap/hdbclient]: /usr/sap/hdbclient


Checking installation...
Preparing package "Python Runtime"...
Preparing package "Product Manifest"...
Preparing package "SQLDBC"...
Preparing package "REPOTOOLS"...
Preparing package "Python DB API"...
Preparing package "ODBC"...
Preparing package "JDBC"...
Preparing package "Client Installer"...
Installing SAP HANA Database Client to /usr/sap/hdbclient...
Installing package 'Python Runtime' ...
Installing package 'Product Manifest' ...
Installing package 'SQLDBC' ...
Installing package 'REPOTOOLS' ...
Installing package 'Python DB API' ...
Installing package 'ODBC' ...
Installing package 'JDBC' ...
Installing package 'Client Installer' ...
Installation done

Log file written to '/var/tmp/hdb_client_2014-11-07_15.28.18/hdbinst_client.log'.


[root@bbcsapd221l SAP_HANA_CLIENT]# cd /usr/sap/hdbclient
[root@bbcsapd221l hdbclient]# ls
hdbcli
hdbodbc_cons hdbsqldbc_cons install
libodbcHDB.so manifest
odbcreg
Python rtt sdk
hdbclient.lst hdbsql
hdbuserstore libodbcHDB.a libSQLDBCHDB.so ngdbc.jar
pyhdbcli.so regi rtt.sh

Once the installation is completed successfully, run the command ./


DSConnectionManager.sh to add the drivers

Use option 1 to add the datasource and use option 2 for configuring drives.
Have to provide the details of the HANA server to complete configuration

Now execute the command ./dsodbcdb_env.sh to distribute the ENV variables


For SQL Driver identify the ___location of the drivers and add the path to ./dsodbcdb_env.sh
Use the file DAsqls27.so
Check the files odbc.ini and dsodbcdb_env.sh, al.env.sh add the library path to env
setenv PATH /opt/sap/dataservices/DataDirect/odbc/lib:$PATH
setenv LD_LIBRARY_PATH
/opt/sap/dataservices/DataDirect/odbc/lib:$LD_LIBRARY_PATH
Execute ./ al.env.sh
./ dsodbcdb_env.sh
./odbc.sh
Now restart the DS services

3.

Installing TERADATA drivers

1)

rpm -ivh --nodeps cliv2-13.10.00.15-1.noarch.rpm

[root@bbcsapd221l cliv2]# rpm -ivh --nodeps cliv2-13.10.00.15-1.noarch.rpm


Preparing...
########################################### [100%]
Teradata cliv2 requires TeraGSS_suselinux-x8664
1:cliv2
########################################### [100%]
Adding cliv2 COPLIB environment variable to /etc/profile file.
Adding cliv2 COPERR environment variable to /etc/profile file.
Adding tdmst entry to /etc/services file.

2)

rpm -ivh --nodeps tdicu-13.10.00.02-1.noarch.rpm

[root@bbcsapd221l tdicu]# rpm -ivh --nodeps tdicu-13.10.00.02-1.noarch.rpm


Preparing...
########################################### [100%]
1:tdicu
########################################### [100%]
Adding TD_ICU_DATA environment variable to /etc/profile file.
Adding TD_ICU_DATA environment variable to /etc/csh.login file.
[root@bbcsapd221l tdicu]# cd ..
[root@bbcsapd221l teradata]# ls
3)

rpm -i TeraGSS_redhatlinux-i386-13.10.07.09-1.i386.rpm

[root@bbcsapd221l TeraGSS]# rpm -i TeraGSS_redhatlinux-i386-13.10.07.091.i386.rpm


Output has been written to Binary file "/usr/teragss/redhatlinuxi386/13.10.07.09/bin/../etc/tdgssconfig.bin"
4)

Install Drivers:

[root@bbcsapd221l drive_raw]# gunzip tdodbc__linux_indep.13.10.00.11-1.tar.gz


[root@bbcsapd221l drive_raw]# ls
tdodbc__linux_indep.13.10.00.11-1.tar
[root@bbcsapd221l drive_raw]# tar -xvf tdodbc__linux_indep.13.10.00.11-1.tar
rpm -ivh tdodbc-13.10.00.11-1.noarch.rpm --nodeps
[root@bbcsapd221l drive_raw]# rpm -ivh tdodbc-13.10.00.11-1.noarch.rpm --nodeps
Preparing...
########################################### [100%]
Warning : ODBC Driver for Teradata requires TeraGSS_suselinux-x8664
1:tdodbc
########################################### [100%]
set_default_version -b 32 -v 13.10 -i /opt
/var/tmp/rpm-tmp.7MaV20:
/opt/teradata/client/13.10/odbc_32/bin/set_default_version: /usr/bin/ksh: bad interpreter:
No such file or directory
/bin/cp: cannot create regular file `/opt/teradata/client/ODBC_32/odbc.ini.tmp.20347': No
such file or directory
/var/tmp/rpm-tmp.7MaV20: line 133: /opt/teradata/client/ODBC_32/odbc.ini.tmp.20347:
No such file or directory
/bin/rm: cannot remove `/opt/teradata/client/ODBC_32/odbc.ini.tmp.20347': No such file
or directory
/bin/cp: cannot create regular file `/opt/teradata/client/ODBC_32/odbcinst.ini.tmp.20347':
No such file or directory
/var/tmp/rpm-tmp.7MaV20: line 133:
/opt/teradata/client/ODBC_32/odbcinst.ini.tmp.20347: No such file or directory
/bin/rm: cannot remove `/opt/teradata/client/ODBC_32/odbcinst.ini.tmp.20347': No such
file or directory
.build_pre130_bridge -b 32 -i /opt
/var/tmp/rpm-tmp.7MaV20: /opt/teradata/client/13.10/odbc_32/bin/.build_pre130_bridge:
/usr/bin/ksh: bad interpreter: No such file or directory
enable_legacy_installdir -b 32 -i /opt -I /usr/odbc
/var/tmp/rpm-tmp.7MaV20:
/opt/teradata/client/13.10/odbc_32/bin/enable_legacy_installdir: /usr/bin/ksh: bad
interpreter: No such file or directory
set_default_version -b 64 -v 13.10 -i /opt

/var/tmp/rpm-tmp.7MaV20:
/opt/teradata/client/13.10/odbc_64/bin/set_default_version: /usr/bin/ksh: bad interpreter:
No such file or directory
/bin/cp: cannot create regular file `/opt/teradata/client/ODBC_64/odbc.ini.tmp.20347': No
such file or directory
/var/tmp/rpm-tmp.7MaV20: line 133: /opt/teradata/client/ODBC_64/odbc.ini.tmp.20347:
No such file or directory
/bin/rm: cannot remove `/opt/teradata/client/ODBC_64/odbc.ini.tmp.20347': No such file
or directory
/bin/cp: cannot create regular file `/opt/teradata/client/ODBC_64/odbcinst.ini.tmp.20347':
No such file or directory
/var/tmp/rpm-tmp.7MaV20: line 133:
/opt/teradata/client/ODBC_64/odbcinst.ini.tmp.20347: No such file or directory
/bin/rm: cannot remove `/opt/teradata/client/ODBC_64/odbcinst.ini.tmp.20347': No such
file or directory
.build_pre130_bridge -b 64 -i /opt
/var/tmp/rpm-tmp.7MaV20: /opt/teradata/client/13.10/odbc_64/bin/.build_pre130_bridge:
/usr/bin/ksh: bad interpreter: No such file or directory
enable_legacy_installdir -b 64 -i /opt -I /opt/teradata/client/odbc
/var/tmp/rpm-tmp.7MaV20:
/opt/teradata/client/13.10/odbc_64/bin/enable_legacy_installdir: /usr/bin/ksh: bad
interpreter: No such file or directory
===============================================================
=============
***
IMPORTANT ODBC USER BULLETIN
***
===============================================================
=============
The TTU 13.0 release has introduced a new TTU directory tree structure
which has unified all the TTU products under a common TTU release directory.
The ODBC 13.0 installation package has taken steps to make this new tree
structure transparent to the existing ODBC users that have selected the
default install directory when installing an ODBC release prior to 13.0.
In the case where the user has selected a non-default install directory,
the user will need to follow the instructions that are documented in the
ODBC README file.
In either case, it is strongly recommended that the user read the ODBC README
file to understand the new TTU tree structure and how it relates to the
ODBC Driver and its odbc.ini and odbcinst.ini files.

===============================================================
=============
***
IMPORTANT ODBC USER BULLETIN
***
===============================================================
=============
Once the installation is complete use the ./ DSConnectionManager.sh to configure the
drivers

You might also like