Users need to test if the UNIX ODBC installation is working from both the queen node and worker nodes before proceeding.
-
Restart the Aster Database cluster, if users did not do it after setting up the environment.
# ncli system softrestart
If the cluster restart was NOT successful, check if all the previous steps are executed properly.If the user cannot solve the problem, the user may have to redo the installation by cleaning and restoring the backed up version of R sandbox area /opt/aster/third-party/R on queen node and restarting cluster. -
If the cluster restart is successful, then users can test the database access using the isql tool as shown here.
# export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib:/usr/local/lib/stage/clients-odbc-linux64/unixODBC/lib
-
Test the UNIX ODBC driver from the queen node.
Replace the AsterDSN in the example with the Data Source Name (DSN) defined in the odbc.ini file.
# chroot /opt/aster/third-party/R/ # isql -v AsterDSN db_superuser db_superuser +---------------------------------------+ | Connected! | | | | sql-statement | | help [tablename] | | quit | | | +---------------------------------------+ SQL>quit; # exit
-
Test the UNIX ODBC driver from the worker node. The output should be the same as shown in Step 2.a.
# chroot /opt/aster/third-party/R/ # isql -v AsterDSN db_superuser db_superuser # exit
-
Test the UNIX ODBC driver from the worker node using the "extensibility" user. The output should be the same as shown in Step 2.a.
# chroot /opt/aster/third-party/R/ # su - extensibility # isql -v 'AsterDSN' db_superuser db_superuser # exit
Teradata recommends users to test the UNIX ODBC driver from all the worker nodes. -
Test the UNIX ODBC driver from the queen node.