Problem Note 52665: Segmentation violations occur when you connect to Teradata using longer LDAP logon IDs
 |  |  |  |  |
Segmentation violations might occur when you use a Lightweight Directory Access Protocol (LDAP) login ID for connecting to Teradata. Here is an example:
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
LIBNAME test TERADATA SERVER="mylongserver.myteradataserver.myqualifier.net" DATABASE=mydatabase
USER="my_very_long userid@LDAP" PASSWORD="mypassword";
The SAS task name is [Line Mod]
Segmentation Violation
Traceback of the Exception:
/sas/Install/v9/SASFoundation/9.3/sasexe/sas() [0x51676d]
/sas/Install/v9/SASFoundation/9.3/sasexe/sas() [0x41e9f8]
/sas/Install/v9/SASFoundation/9.3/sasexe/sas() [0x41e6cf]
/sas/Install/v9/SASFoundation/9.3/sasexe/tkmk.so(bkt_signal_handler+0x144)
[0x7fd2a078e764]
The problem occurs when the value of the SERVER= parameter is a fully qualified machine name and the LDAP user ID is also very long. To circumvent the problem, do one of the following:
- Use the host Alias name instead of the full server name for the SERVER= parameter. You can find the Alias name in the hosts file for your system.
- Use the server IP address (such as '10.12.142.58') instead of the full server name.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS/ACCESS Interface to Teradata | Microsoft Windows NT Workstation | 9.31_M2 | |||
| Microsoft Windows 2000 Professional | 9.31_M2 | |||||
| Microsoft Windows 2000 Server | 9.31_M2 | |||||
| Microsoft Windows 2000 Datacenter Server | 9.31_M2 | |||||
| Microsoft Windows 2000 Advanced Server | 9.31_M2 | |||||
| Microsoft Windows 95/98 | 9.31_M2 | |||||
| Microsoft Windows 8.1 Pro 32-bit | 9.31_M2 | |||||
| Microsoft Windows 8.1 Pro | 9.31_M2 | |||||
| Microsoft Windows 8.1 Enterprise x64 | 9.31_M2 | |||||
| Microsoft Windows 8.1 Enterprise 32-bit | 9.31_M2 | |||||
| Microsoft Windows 8 Pro x64 | 9.31_M2 | |||||
| Microsoft Windows 8 Pro 32-bit | 9.31_M2 | |||||
| Microsoft Windows 8 Enterprise x64 | 9.31_M2 | |||||
| Microsoft Windows 8 Enterprise 32-bit | 9.31_M2 | |||||
| Microsoft® Windows® for x64 | 9.31_M2 | |||||
| Microsoft Windows Server 2003 Datacenter Edition | 9.31_M2 | |||||
| Microsoft Windows Server 2003 Enterprise Edition | 9.31_M2 | |||||
| Microsoft Windows Server 2003 Standard Edition | 9.31_M2 | |||||
| Microsoft Windows Server 2003 for x64 | 9.31_M2 | |||||
| Microsoft Windows Server 2008 | 9.31_M2 | |||||
| Microsoft Windows Server 2008 R2 | 9.31_M2 | |||||
| Microsoft Windows Server 2008 for x64 | 9.31_M2 | |||||
| Microsoft Windows Server 2012 Datacenter | 9.31_M2 | |||||
| Microsoft Windows Server 2012 R2 Datacenter | 9.31_M2 | |||||
| Microsoft Windows Server 2012 R2 Std | 9.31_M2 | |||||
| Microsoft Windows Server 2012 Std | 9.31_M2 | |||||
| Microsoft Windows XP Professional | 9.31_M2 | |||||
| Windows 7 Enterprise 32 bit | 9.31_M2 | |||||
| Windows 7 Enterprise x64 | 9.31_M2 | |||||
| Windows 7 Home Premium 32 bit | 9.31_M2 | |||||
| Windows 7 Home Premium x64 | 9.31_M2 | |||||
| Windows 7 Professional 32 bit | 9.31_M2 | |||||
| Windows 7 Professional x64 | 9.31_M2 | |||||
| Windows 7 Ultimate 32 bit | 9.31_M2 | |||||
| Windows 7 Ultimate x64 | 9.31_M2 | |||||
| Windows Millennium Edition (Me) | 9.31_M2 | |||||
| Windows Vista | 9.31_M2 | |||||
| Windows Vista for x64 | 9.31_M2 | |||||
| 64-bit Enabled AIX | 9.31_M2 | |||||
| 64-bit Enabled HP-UX | 9.31_M2 | |||||
| 64-bit Enabled Solaris | 9.31_M2 | |||||
| HP-UX IPF | 9.31_M2 | |||||
| Linux | 9.31_M2 | |||||
| Linux for x64 | 9.31_M2 | |||||
| Solaris for x64 | 9.31_M2 | |||||
A fix for this issue for SAS/ACCESS Interface to Teradata 9.31_M2 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/I32.html#52665
When using longer Lightweight Directory Access Protocol (LDAP) logon IDs with Teradata, segmentation violations can occur. The problem occurs because of memory addresses.
| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2014-04-24 11:02:57 |
| Date Created: | 2014-03-31 12:19:16 |