Starting with TTU 15.10.01, the Teradata® Tools and Utilities products no longer depend on DYLD_LIBRARY_PATH, so this environment variable is no longer set during install. The Teradata® Tools and Utilities products now use relative locations to find and load dependent libraries. Do not move the installed files to any other location.
Starting with TTU 15.10.01, Teradata® Tools and Utilities products no longer depend on LD_LIBRARY_PATH or the symbolic links created in /usr/lib and /usr/lib64 to find and load any dependent Teradata® Tools and Utilities library. The Teradata® Tools and Utilities products now use relative paths to find and load Teradata® Tools and Utilities-dependent libraries. Moving any of the installed files to a different location will likely result in failures.
The symbolic links created in /usr/lib and /usr/lib64 are to allow third-party applications, such as Informatica, to find our shared libraries.
Starting with TTU 15.10.01, Teradata® Tools and Utilities products no longer depend on LIBPATH or the symbolic links created in /usr/lib to find and load any dependent Teradata® Tools and Utilities library. The Teradata® Tools and Utilities products now use relative paths to find and load Teradata® Tools and Utilities-dependent libraries. Moving any of the installed files to a different location will likely result in failures.
- setusrliblinks.sh 32|64
Starting with TTU 15.10.01, the Teradata® Tools and Utilities products use relative locations to find and load dependent libraries. Do not move the installed files to any other location. The bin path of the release is the only path added to the PATH environment variable to enable third-party applications to locate the TTU shared libraries. All public executables and libraries are now located in the bin folder.