The Teradata Tools and Utilities products no longer depend on DYLD_LIBRARY_PATH, so this environment variable will no longer be set during install. The Teradata Tools and Utilities products now use relative locations to find and load dependent libraries, so it is strongly recommended that the installed files not be moved to any other location.
- ttu_1510_bash.env (bash shell)
- ttu_1510_csh.env (c shell)
They are located in the following folder:
/prefix/Library/Application Support/teradata/client/15.10/etc
The prefix is the default drive ("/") or an alternate drive (for example, /Volumes/Data) chosen during install. If the .env file is sourced in a terminal window, the TTU library path will be added to DYLD_LIBRARY_PATH.
Teradata Tools and Utilities products no longer depend on LD_LIBRARY_PATH and/or the softlinks 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. This implies that the installed files should not be moved. Moving any of the installed files to a different location can, and most likely will, result in failures.
The softlinks created in /usr/lib and /usr/lib64 are to allow third party applications, such as Informatica, to find our shared libraries.
Teradata Tools and Utilities products no longer depend on LIBPATH and/or the softlinks 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. This implies that the installed files should not be moved. Moving any of the installed files to a different location can, and most likely will, result in failures.
- setusrliblinks.sh 32|64
The Teradata Tools and Utilities products now use relative locations to find and load dependent libraries, so it is strongly recommended that the installed files not be moved to any other location. The bin path of the release will be the only path added to the PATH environment variable. This is done to enable third party applications to locate the TTU shared libraries. All public executables and libraries are now located in the bin folder.