Usage Note 16105: Code appendage errors when connecting to Unix Spawner via the BI
environment
The following errors may occur when connecting to a database on a remote
UNIX Connect Server in the Business Intelligence environment:
Could not load /opt/app/sasadmin/sasinstall/SAS_9.1/sasexe/sastra (42
images loaded)
Error: ld.so.1: /opt/app/sasadmin/sasinstall/SAS_9.1/sasexe/sas:
fatal: /usr/local/lib/libcliv2.so: wrong ELF class: ELFCLASS32
ERROR: The SAS/ACCESS Interface to Teradata cannot be loaded. The
SASTRA code appendage could not be loaded.
ERROR: A Connection to the teradata DBMS is not currently supported,
or is not installed at your site.
If this worked prior to converting to the Business Intelligence
environment, the reason may be that previous connections to the SAS
server were via a telnet connection. However, in the Business
Intelligence environment, the Connect Server starts a Unix Spawner which
waits for requests. By default, the Unix Spawner does not source UNIX
profiles.
To correct this problem, the -SASCMD option is needed to point to a file
that executes (sources) all necessary startup scripts, when installing
the UNIX Spawner.
Following is an example of a sascmd file.
(make sure that the #!/bin/ksh is the 1st line in the script):
***********************************************************************
#!/bin/ksh
. ~/.profile
xxxx/xxxx/xxx/sas -dmr -noterminal -no$syntaxcheck -comamid tcp
-device grlink $*
***********************************************************************
The file should have the execute bit set. To set the bit, use the
following command:
chmod 755 /mystartup
The file should have the following settings: -rwxr-xr-x
The -SASCMD specification will need to be added to the Spawner
installation statement in the ConnectServer.sh file. The modified file
may resemble the following:
start /b "Connect Spawner" "%sasdir%\spawner" -omrconfigfile
"c:\SAS\9.1.3\Lev1\SASMain\ConnectServer\OMRConfig.xml" -sasSpawnerCn
"%SPWNNAME%" -logfile
"c:\SAS\9.1.3\Lev1\SASMain\connectserver\logs\spawner.log" -sascmd
~mystartupfile -verbose -install -name "%SASServiceNAME%" %DEPENDS%
goto end
Alternatively, the necessary environment variables may be added to the
file !SASROOT/bin/sasenv which will allow these environment variables
to be set globally for all SAS processes.
Once it is ensured that the profile is being sourced properly, also
verify that the correct shared library is placed first in the
!SASROOT/bin/sasenv path, ensuring that the correct version is called.
Operating System and Release Information
SAS System | SAS/CONNECT | 64-bit Enabled Solaris | 9.1 TS1M3 | |
Linux | 9.1 TS1M3 | |
64-bit Enabled HP-UX | 9.1 TS1M3 | |
64-bit Enabled AIX | 9.1 TS1M3 | |
*
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.
Type: | Usage Note |
Priority: | low |
Topic: | Software Components ==> Connect Spawner
|
Date Modified: | 2005-09-07 10:27:20 |
Date Created: | 2005-09-07 10:27:20 |