Home > Archive > SQL Anywhere for Linux > April 2005 > Database server not found with ASA 9.0.1









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author Database server not found with ASA 9.0.1
Bill Williams

2005-04-05, 8:03 pm

We have been running a database using ASA 8.0.3.5182 running on a
Mandrake 10.1 system.

I am using unixODBC 2.2.8.

I have just installed ASA 9.0.1.1989 and am trying to get the ODBC
connections to work but keep getting a "Database server not found error".

What I have done so far is just create the entries in the odbcinst.ini
and odbc.ini files. The database is still running on the 8.0.3 engine.

Whenever I try to connect using the 9.0.1 libraries, it fails but if I
switch back to the 8.0.3 libraries, everything works. I am able to
connect to the database from a Windows XP machine with 9.0.2 odbc
drivers installed; therefore, I don't think the problem is the 8.0.3 engine.

Here are my files:

odbcinst.ini:

[ODBC]
Trace = Yes
TraceFile = /tmp/sql.log
ForceTrace = No
Pooling = No
InstallDir = /opt/sybase/SYBSsa9/drivers
TraceDll=/opt/sybase/SYBSsa9/drivers/lib/odbctrac.so

[Sybase ASA 8.0.0]
Description = Sybase SQL Anywhere 8.0.0 driver
Driver = /opt/sybase/SYBSsa8/lib/dbodbc8_r.so
Setup = /opt/sybase/SYBSsa8/lib/dbodbc8_r.so
FileUsage = 1

[Sybase ASA 9.0.1]
Description = Sybase SQL Anywhere 9.0.1 driver
Driver = /opt/sybase/SYBSsa9/lib/libdbodbc9_r.so
Setup = /opt/sybase/SYBSsa9/lib/libdbodbc9_r.so
FileUsage = 1


odbc.ini:

[centralPet]
Description = Central Pet
Driver = Sybase ASA 8.0.0
Userid = qc
Password = xxxxx
ServerName = asa800
StartLine =
DatabaseName = centralPet
DatabaseFile =
CommLinks =
AutoStart = NO
AutoStop = NO
Unconditional = YES
DisableMultiRowFetch
= YES
CommBufferSize =
CommBufferSpace =
Debug = NO
LogFile = /tmp/sybase.log

[underArmour]
Description = Under Armour
Driver = Sybase ASA 9.0.1
Userid = qc
Password = xxxxx
ServerName = asa800
StartLine =
DatabaseName = underArmour
DatabaseFile =
CommLinks =
AutoStart = NO
AutoStop = NO
Unconditional = YES
DisableMultiRowFetch
= YES
CommBufferSize =
CommBufferSpace =
Debug = NO
LogFile = /tmp/sybase.log

I tested the underArmour DSN with both ASA 8 and ASA 9. I changed the
Driver parameter to "Sybase ASA 8.0.0" and then to the current value
above for the ASA 9 test.

Below are entries from the log file. The first entry is a successful
connection to the centralPet DSN. The second entry is a successful
connection to the underArmour DSN using the ASA 8 drivers just like
centralPet uses. The last one is the failed connection using the ASA 9
drivers.

Entries generated in the log:

Wed Mar 09 2005 14:07:11
14:07:11 Application information:
14:07:11 "IP=192.168.1. 1;HOST=batcave;OS=Li
nux 2.6.8.1-12mdksmp #1 SMP
Fri Oct 1 11:24:45 CEST
2004;PID=0x6b96;THRE
AD=0x40260080;VERSIO
N=8.0.3. 5182;API=ODBC;TIMEZO
NEADJUSTMENT=-300"
14:07:11 Attempting to connect using:
UID=qc;PWD=**;DBN=ce
ntralPet;ENG=asa800;
UNC=YES;CON=SQL_DBC_
808a560;ASTOP=NO;DBG
=NO;LOG=/tmp/sybase. log;DMRF=YES;ASTART=
NO
14:07:11 Attempting to connect to a running server...
14:07:11 Trying to start SharedMemory link ...
14:07:11 SharedMemory link started successfully
14:07:11 Attempting SharedMemory connection (no .asasrv.ini cached address)
14:07:11 Connected to server over SharedMemory
14:07:11 Connected to ASA Engine version 8.0.3.5182
14:07:11 Connected to the server, attempting to connect to a running
database...
14:07:11 [ 1457] Connected to database successfully

Wed Mar 09 2005 14:07:47
14:07:47 Application information:
14:07:47 "IP=192.168.1. 1;HOST=batcave;OS=Li
nux 2.6.8.1-12mdksmp #1 SMP
Fri Oct 1 11:24:45 CEST
2004;PID=0x6b9a;THRE
AD=0x40260080;VERSIO
N=8.0.3. 5182;API=ODBC;TIMEZO
NEADJUSTMENT=-300"
14:07:47 Attempting to connect using:
UID=qc;PWD=**;DBN=un
derArmour;ENG=asa800
;UNC=YES;CON=SQL_DBC
_808a560;ASTOP=NO;DB
G=YES;LOG=/tmp/sybase. log;DMRF=YES;ASTART=
NO
14:07:47 Attempting to connect to a running server...
14:07:47 Trying to start SharedMemory link ...
14:07:47 SharedMemory link started successfully
14:07:47 Attempting SharedMemory connection (no .asasrv.ini cached address)
14:07:47 Connected to server over SharedMemory
14:07:47 Connected to ASA Engine version 8.0.3.5182
14:07:47 Connected to the server, attempting to connect to a running
database...
14:07:47 [ 1458] Connected to database successfully

Wed Mar 09 2005 14:08:25
14:08:25 Application information:
14:08:25 "IP=192.168.1. 1;HOST=batcave;OS=Li
nux 2.6.8.1-12mdksmp #1 SMP
Fri Oct 1 11:24:45 CEST
2004;PID=0x6b9e;THRE
AD=0x40260080;VERSIO
N=9.0.1. 1989;API=ODBC;TIMEZO
NEADJUSTMENT=-300"
14:08:25 Attempting to connect using:
UID=qc;PWD=********;
DBN=underArmour;UNC=
YES;CON=SQL_DBC_8086
650;ASTOP=NO;DBG=YES
;LOG=/tmp/sybase. log;DMRF=YES;ASTART=
NO
14:08:25 Attempting to connect to a running server...
14:08:25 Trying to start SharedMemory link ...
14:08:25 SharedMemory link started successfully
14:08:25 Attempting SharedMemory connection (no .asasrv.ini cached address)
14:08:25 Failed to connect over SharedMemory
14:08:25 Not attempting to autostart server
14:08:25 Cannot connect to server
Greg Fenton

2005-04-05, 8:03 pm

Bill Williams wrote:
>
> I am using unixODBC 2.2.8.
>


I have not tried unixODBC before.

> 14:07:47 Attempting to connect using:
> UID=qc;PWD=**;DBN=un
derArmour;ENG=asa800
;UNC=YES;CON=SQL_DBC
_808a560;ASTOP=NO;DB
G=YES;LOG=/tmp/sybase. log;DMRF=YES;ASTART=
NO
>
> 14:08:25 Attempting to connect using:
> UID=qc;PWD=********;
DBN=underArmour;UNC=
YES;CON=SQL_DBC_8086
650;ASTOP=NO;DBG=YES
;LOG=/tmp/sybase. log;DMRF=YES;ASTART=
NO
>


I see that the second connection string does not contain an ENG
parameter. I also see that the ServerName parameter in your 9.0.1 is
asa800. Could something be missing here?

What command are you using to attempt to connect to the database?

I'd probably start off by using ASA only, avoiding the extra layer that
unixODBC throws in, just until you are sure you can connect.

First see what the ODBC entry looks like according to ASA:
$ASANY9/bin/dbdsn -l

Then try using the command:
$ASANY9/bin/dbping -d -c dsn=underArmour

Make sure you sourced $ASANY9/bin/asa_config.sh before you try to
connect using the ASA 9 tools.

Hope this helps,
greg.fenton
--
Greg Fenton
Consultant, Solution Services, iAnywhere Solutions
--------
Visit the iAnywhere Solutions Developer Community
Whitepapers, TechDocs, Downloads
http://www.ianywhere.com/developer/
Bill Williams

2005-04-05, 8:03 pm

The name of the ASA 8.0.3 engine is asa800 so the ServerName entry is
correct (at least I guess it is because that has always worked before).

I am working at home so the log entries below have different IP
addresses but I'm still running Mandrake 10.1.

Here's a dumb question, but how do I use only ASA without using unixODBC
or some other manager software? We have always used it for ASA versions
7 and 8.

Here's another weird thing I noticed. When I run the "dbdsn -l" command
either under ASA 8 or 9 (I'm sourcing the correct asa_config.sh before I
do this), it never displays any data yet under ASA 8, I am able to
connect to the database.

I have the environment variable ODBCINI set to
/usr/local/unixODBC/etc/odbc.ini which is where the file is.

I performed the dbping command like you suggested and it failed at
first. I then set CommLinks=tcpip and it worked. Perhaps the ASA 8
engine cannot do a shared memory connection with the ASA9 ODBC drivers.
Here is the log output (first enty is the failure and the second is the
success with tcpip set):

"dbping -d -c dsn=dcms" with "CommLink ="

Thu Mar 10 2005 09:46:05
09:46:05 Application information:
09:46:05 "IP=192.168.2. 1;HOST=mercury;OS=Li
nux 2.6.8.1-12mdk #1 Fri
Oct 1 12:53:41 CEST
2004;PID=0x3e00;THRE
AD=0x40376700;VERSIO
N=9.0.1. 1989;API=DBLIB;TIMEZ
ONEADJUSTMENT=-300"
09:46:05 Attempting to connect using:
UID=qc;PWD=********;
DBN=dcms;ENG=asa800;
UNC=YES;ASTOP=NO;DSN
=dcms;DBG=NO;LOG=/tmp/sybase. log;DMRF=NO;ASTART=N
O
09:46:05 Attempting to connect to a running server...
09:46:05 Trying to start SharedMemory link ...
09:46:05 SharedMemory link started successfully
09:46:05 Attempting SharedMemory connection (no .asasrv.ini cached
address)
09:46:05 Failed to connect over SharedMemory
09:46:05 Not attempting to autostart server
09:46:05 Cannot connect to server

"dbping -d -c dsn=dcms" with "CommLinks = tcpip"

Thu Mar 10 2005 09:46:32
09:46:32 Application information:
09:46:32 "IP=192.168.2. 1;HOST=mercury;OS=Li
nux 2.6.8.1-12mdk #1 Fri
Oct 1 12:53:41 CEST
2004;PID=0x3e15;THRE
AD=0x40376700;VERSIO
N=9.0.1. 1989;API=DBLIB;TIMEZ
ONEADJUSTMENT=-300"
09:46:32 Attempting to connect using:
UID=qc;PWD=********;
DBN=dcms;ENG=asa800;
UNC=YES;ASTOP=NO;DSN
=dcms;DBG=NO;LOG=/tmp/sybase. log;DMRF=NO;LINKS=tc
pip;ASTART=NO
09:46:32 Attempting to connect to a running server...
09:46:32 Trying to start TCPIP link ...
09:46:32 My IP address is 192.168.2.1
09:46:32 My IP address is 127.0.0.1
09:46:32 TCPIP link started successfully
09:46:32 Attempting TCPIP connection (address 192.168.2.1:2638 found
in .asasrv.ini cache)
09:46:32 Trying to find server at cached address 192.168.2.1:2638
without broadcasting
09:46:32 Found server, verifying server name
09:46:32 Found database server at address 192.168.2.1:2638
09:46:32 Found database server asa800 on TCPIP link
09:46:32 Connected to server over TCPIP at address 192.168.2.1:2638
09:46:32 Connected to ASA Engine version 8.0.3.5182
09:46:32 Connected to the server, attempting to connect to a running
database...
09:46:32 [ 2] Connected to database successfully
09:46:33 [ 2] Client disconnected


I then tried to use dbisql. It always failed and it would not even make
an entry in the log file so it's as if it was not reading the odbc.ini
file.
I then tried to use dbisqlc. It worked. One with tcpip set worked and
the one without tcpip failed. Below are those log entries:

"dbisqlc -c "dsn=dcms" with "CommLinks = tcpip"

Thu Mar 10 2005 09:50:46
09:50:46 Application information:
09:50:46 "IP=192.168.2. 1;HOST=mercury;OS=Li
nux 2.6.8.1-12mdk #1 Fri
Oct 1 12:53:41 CEST
2004;PID=0x3efc;THRE
AD=0x40260840;VERSIO
N=9.0.1. 1989;API=DBLIB;TIMEZ
ONEADJUSTMENT=-300"
09:50:46 Attempting to connect using:
UID=qc;PWD=********;
DBN=dcms;ENG=asa800;
UNC=YES;ASTOP=NO;DSN
=dcms;DBG=NO;LOG=/tmp/sybase. log;DMRF=NO;LINKS=tc
pip;ASTART=NO
09:50:46 Attempting to connect to a running server...
09:50:46 Trying to start TCPIP link ...
09:50:46 My IP address is 192.168.2.1
09:50:46 My IP address is 127.0.0.1
09:50:46 TCPIP link started successfully
09:50:46 Attempting TCPIP connection (address 192.168.2.1:2638 found
in .asasrv.ini cache)
09:50:46 Trying to find server at cached address 192.168.2.1:2638
without broadcasting
09:50:46 Found server, verifying server name
09:50:46 Found database server at address 192.168.2.1:2638
09:50:46 Found database server asa800 on TCPIP link
09:50:46 Connected to server over TCPIP at address 192.168.2.1:2638
09:50:46 Connected to ASA Engine version 8.0.3.5182
09:50:46 Connected to the server, attempting to connect to a running
database...
09:50:46 [ 4] Connected to database successfully
09:50:58 [ 4] Client disconnected

"dbisqlc -c "dsn=dcms" with "CommLinks ="

Thu Mar 10 2005 09:51:41
09:51:41 Application information:
09:51:41 "IP=192.168.2. 1;HOST=mercury;OS=Li
nux 2.6.8.1-12mdk #1 Fri
Oct 1 12:53:41 CEST
2004;PID=0x3f21;THRE
AD=0x40260840;VERSIO
N=9.0.1. 1989;API=DBLIB;TIMEZ
ONEADJUSTMENT=-300"
09:51:41 Attempting to connect using:
UID=qc;PWD=********;
DBN=dcms;ENG=asa800;
UNC=YES;ASTOP=NO;DSN
=dcms;DBG=NO;LOG=/tmp/sybase. log;DMRF=NO;ASTART=N
O
09:51:41 Attempting to connect to a running server...
09:51:41 Trying to start SharedMemory link ...
09:51:41 SharedMemory link started successfully
09:51:41 Attempting SharedMemory connection (no .asasrv.ini cached
address)
09:51:41 Failed to connect over SharedMemory
09:51:41 Not attempting to autostart server
09:51:41 Cannot connect to server


Greg Fenton wrote:

> Bill Williams wrote:
>
>
> I have not tried unixODBC before.
>
>
>
> I see that the second connection string does not contain an ENG
> parameter. I also see that the ServerName parameter in your 9.0.1 is
> asa800. Could something be missing here?
>
> What command are you using to attempt to connect to the database?
>
> I'd probably start off by using ASA only, avoiding the extra layer
> that unixODBC throws in, just until you are sure you can connect.
>
> First see what the ODBC entry looks like according to ASA:
> $ASANY9/bin/dbdsn -l
>
> Then try using the command:
> $ASANY9/bin/dbping -d -c dsn=underArmour
>
> Make sure you sourced $ASANY9/bin/asa_config.sh before you try to
> connect using the ASA 9 tools.
>
> Hope this helps,
> greg.fenton



Mark Culp

2005-04-05, 8:03 pm

1) What are your command line switches when you start the engine?

2) What env vars are set when you start the engine?
Relevant ones in this case are TMP, TEMP, ASTMP, SATMP, ASANY, ASANY8

3) What env vars are set when you run the client?

My guess is that the shmem connection cannot be made between the client
and the server because the client cannot 'find' the server in its tmp
location.

Assuming that there are no special env var set for any of the above,
start the engine and then look in /tmp/.SQLAnywhere and you should see
a directory called asa800 (the name of your server). If you do not,
then go back and check #1 and #2 again.

If the asa800 dir does exist, then run a strace on the client (e.g. dbdsn)
to see where its looking. If it doesn't look in /tmp/.SQLAnywhere then
go back and check #3 again. :)
--
Mark Culp
ASA Research and Development
-------------------------------------------------------------------------
** Whitepapers, TechDocs, bug fixes are all available through the **
** iAnywhere Developer Community at http://www.ianywhere.com/developer **
-------------------------------------------------------------------------
[color=darkred]
> Bill Williams wrote:
>
> The name of the ASA 8.0.3 engine is asa800 so the ServerName entry is correct
> (at least I guess it is because that has always worked before).
>
> I am working at home so the log entries below have different IP addresses but
> I'm still running Mandrake 10.1.
>
> Here's a dumb question, but how do I use only ASA without using unixODBC or
> some other manager software? We have always used it for ASA versions 7 and 8.
>
> Here's another weird thing I noticed. When I run the "dbdsn -l" command
> either under ASA 8 or 9 (I'm sourcing the correct asa_config.sh before I do
> this), it never displays any data yet under ASA 8, I am able to connect to the
> database.
>
> I have the environment variable ODBCINI set to
> /usr/local/unixODBC/etc/odbc.ini which is where the file is.
>
> I performed the dbping command like you suggested and it failed at first. I
> then set CommLinks=tcpip and it worked. Perhaps the ASA 8 engine cannot do a
> shared memory connection with the ASA9 ODBC drivers. Here is the log output
> (first enty is the failure and the second is the success with tcpip set):
>
> "dbping -d -c dsn=dcms" with "CommLink ="
>
> Thu Mar 10 2005 09:46:05
> 09:46:05 Application information:
> 09:46:05 "IP=192.168.2. 1;HOST=mercury;OS=Li
nux 2.6.8.1-12mdk #1 Fri
> Oct 1 12:53:41 CEST
> 2004;PID=0x3e00;THRE
AD=0x40376700;VERSIO
N=9.0.1. 1989;API=DBLIB;TIMEZ
ONEADJUSTMENT=-300"
> 09:46:05 Attempting to connect using:
> UID=qc;PWD=********;
DBN=dcms;ENG=asa800;
UNC=YES;ASTOP=NO;DSN
=dcms;DBG=NO;LOG=/tmp/sybase. log;DMRF=NO;ASTART=N
O
> 09:46:05 Attempting to connect to a running server...
> 09:46:05 Trying to start SharedMemory link ...
> 09:46:05 SharedMemory link started successfully
> 09:46:05 Attempting SharedMemory connection (no .asasrv.ini cached
> address)
> 09:46:05 Failed to connect over SharedMemory
> 09:46:05 Not attempting to autostart server
> 09:46:05 Cannot connect to server
>
> "dbping -d -c dsn=dcms" with "CommLinks = tcpip"
>
> Thu Mar 10 2005 09:46:32
> 09:46:32 Application information:
> 09:46:32 "IP=192.168.2. 1;HOST=mercury;OS=Li
nux 2.6.8.1-12mdk #1 Fri
> Oct 1 12:53:41 CEST
> 2004;PID=0x3e15;THRE
AD=0x40376700;VERSIO
N=9.0.1. 1989;API=DBLIB;TIMEZ
ONEADJUSTMENT=-300"
> 09:46:32 Attempting to connect using:
> UID=qc;PWD=********;
DBN=dcms;ENG=asa800;
UNC=YES;ASTOP=NO;DSN
=dcms;DBG=NO;LOG=/tmp/sybase. log;DMRF=NO;LINKS=tc
pip;ASTART=NO
> 09:46:32 Attempting to connect to a running server...
> 09:46:32 Trying to start TCPIP link ...
> 09:46:32 My IP address is 192.168.2.1
> 09:46:32 My IP address is 127.0.0.1
> 09:46:32 TCPIP link started successfully
> 09:46:32 Attempting TCPIP connection (address 192.168.2.1:2638 found
> in .asasrv.ini cache)
> 09:46:32 Trying to find server at cached address 192.168.2.1:2638
> without broadcasting
> 09:46:32 Found server, verifying server name
> 09:46:32 Found database server at address 192.168.2.1:2638
> 09:46:32 Found database server asa800 on TCPIP link
> 09:46:32 Connected to server over TCPIP at address 192.168.2.1:2638
> 09:46:32 Connected to ASA Engine version 8.0.3.5182
> 09:46:32 Connected to the server, attempting to connect to a running
> database...
> 09:46:32 [ 2] Connected to database successfully
> 09:46:33 [ 2] Client disconnected
>
> I then tried to use dbisql. It always failed and it would not even make an
> entry in the log file so it's as if it was not reading the odbc.ini file.
> I then tried to use dbisqlc. It worked. One with tcpip set worked and the
> one without tcpip failed. Below are those log entries:
>
> "dbisqlc -c "dsn=dcms" with "CommLinks = tcpip"
>
> Thu Mar 10 2005 09:50:46
> 09:50:46 Application information:
> 09:50:46 "IP=192.168.2. 1;HOST=mercury;OS=Li
nux 2.6.8.1-12mdk #1 Fri
> Oct 1 12:53:41 CEST
> 2004;PID=0x3efc;THRE
AD=0x40260840;VERSIO
N=9.0.1. 1989;API=DBLIB;TIMEZ
ONEADJUSTMENT=-300"
> 09:50:46 Attempting to connect using:
> UID=qc;PWD=********;
DBN=dcms;ENG=asa800;
UNC=YES;ASTOP=NO;DSN
=dcms;DBG=NO;LOG=/tmp/sybase. log;DMRF=NO;LINKS=tc
pip;ASTART=NO
> 09:50:46 Attempting to connect to a running server...
> 09:50:46 Trying to start TCPIP link ...
> 09:50:46 My IP address is 192.168.2.1
> 09:50:46 My IP address is 127.0.0.1
> 09:50:46 TCPIP link started successfully
> 09:50:46 Attempting TCPIP connection (address 192.168.2.1:2638 found
> in .asasrv.ini cache)
> 09:50:46 Trying to find server at cached address 192.168.2.1:2638
> without broadcasting
> 09:50:46 Found server, verifying server name
> 09:50:46 Found database server at address 192.168.2.1:2638
> 09:50:46 Found database server asa800 on TCPIP link
> 09:50:46 Connected to server over TCPIP at address 192.168.2.1:2638
> 09:50:46 Connected to ASA Engine version 8.0.3.5182
> 09:50:46 Connected to the server, attempting to connect to a running
> database...
> 09:50:46 [ 4] Connected to database successfully
> 09:50:58 [ 4] Client disconnected
>
> "dbisqlc -c "dsn=dcms" with "CommLinks ="
>
> Thu Mar 10 2005 09:51:41
> 09:51:41 Application information:
> 09:51:41 "IP=192.168.2. 1;HOST=mercury;OS=Li
nux 2.6.8.1-12mdk #1 Fri
> Oct 1 12:53:41 CEST
> 2004;PID=0x3f21;THRE
AD=0x40260840;VERSIO
N=9.0.1. 1989;API=DBLIB;TIMEZ
ONEADJUSTMENT=-300"
> 09:51:41 Attempting to connect using:
> UID=qc;PWD=********;
DBN=dcms;ENG=asa800;
UNC=YES;ASTOP=NO;DSN
=dcms;DBG=NO;LOG=/tmp/sybase. log;DMRF=NO;ASTART=N
O
> 09:51:41 Attempting to connect to a running server...
> 09:51:41 Trying to start SharedMemory link ...
> 09:51:41 SharedMemory link started successfully
> 09:51:41 Attempting SharedMemory connection (no .asasrv.ini cached
> address)
> 09:51:41 Failed to connect over SharedMemory
> 09:51:41 Not attempting to autostart server
> 09:51:41 Cannot connect to server
>
> Greg Fenton wrote:
>
Greg Fenton

2005-04-05, 8:03 pm

Mark Culp wrote:
>
> If the asa800 dir does exist, then run a strace on the client (e.g. dbdsn)
> to see where its looking. If it doesn't look in /tmp/.SQLAnywhere then
> go back and check #3 again. :)



I believe Mark meant "on the client (e.g. dbping)", not "dbdsn".

greg.fenton
--
Greg Fenton
Consultant, Solution Services, iAnywhere Solutions
--------
Visit the iAnywhere Solutions Developer Community
Whitepapers, TechDocs, Downloads
http://www.ianywhere.com/developer/
Bill Williams

2005-04-05, 8:03 pm

I am using a parameter file to start the engine. Here are the contents:

-n asa800
-s none
-ti 0
-cs
/mnt/data/qc/Projects/CentralPet/System/Db/wcs1 -m -n centralPet
/mnt/data/qc/Projects/QcDemo/System/Db/qcDemo -m -n qcDemo
/mnt/data/qc/Projects/RedEnvelope/System/Db/WCS -m -n redEnvelope
/mnt/data/qc/Projects/TommyHilfiger2004/System/Db/coreWCS -m -n
tommyCore
/mnt/data/qc/Projects/Dcms/underArmour -m -n dcms

My command line is "dbsrv8 @paramFile".

Here are my env vars you asked about when I start the dbsrv8 server:

ASANY=/usr/local/sybase/SYBSsa8
ASANY8=/usr/local/sybase/SYBSsa8
TMP=/home/wlw/tmp

Once I am trying to use the ASA 9, here are the env vars (it appears
asa_config.sh in ASA9 does not set ASANY):

ASANY=/usr/local/sybase/SYBSsa8
ASANY8=/usr/local/sybase/SYBSsa8
ASANY9=/usr/local/sybase/SYBSsa9
TMP=/home/wlw/tmp

According to the docs, UNIX only uses ASTMP and since it is not set, I
would expect /tmp to be used.

The directory /tmp/.SQLAnywhere exists as you say it should after I
started the server.

I did the strace command on the dbping and I did not see it looking for
/tmp/.SQLAnywhere at all. The only thing it was doing in /tmp was
apparently creating a directory for itself. No where in the file did I
even see the word SQLAnywhere. It does however seem to work with the
tcpip argument set for CommLinks like I stated earlier.

I also did the strace to the dbisql command. It apparently never even
looked for the odbc.ini file whereas the dbisqlc file looks for
..odbc.ini and odbc.ini file pointed to by ODBCINI.

It's a real pain that dbisql is not working. I can live with using the
tcpip connection although I would like to figure out why the shared
memory is not working.

Mark Culp wrote:

>1) What are your command line switches when you start the engine?
>
>


>2) What env vars are set when you start the engine?
> Relevant ones in this case are TMP, TEMP, ASTMP, SATMP, ASANY, ASANY8
>
>


>3) What env vars are set when you run the client?
>
>My guess is that the shmem connection cannot be made between the client
>and the server because the client cannot 'find' the server in its tmp
>location.
>
>Assuming that there are no special env var set for any of the above,
>start the engine and then look in /tmp/.SQLAnywhere and you should see
>a directory called asa800 (the name of your server). If you do not,
>then go back and check #1 and #2 again.
>
>


>If the asa800 dir does exist, then run a strace on the client (e.g. dbdsn)
>to see where its looking. If it doesn't look in /tmp/.SQLAnywhere then
>go back and check #3 again. :)
>
>

[color=darkred]
>--
>Mark Culp
>ASA Research and Development
>-------------------------------------------------------------------------
>** Whitepapers, TechDocs, bug fixes are all available through the **
>** iAnywhere Developer Community at http://www.ianywhere.com/developer **
>-------------------------------------------------------------------------
>
>
>

Mark Culp

2005-04-05, 8:03 pm

Did you verify that /tmp/.SQLAnywhere/asa800 directory existed after you
had started the server (named asa800) ?

If the asa800 dir exists, run strace on dbping again:
strace -o foo dbping -c asa800
and then post the output to
grep asa800 foo

FWIW: dbisqlc is a ESQL app and therefore will use the contents of the
..odbc.ini file to look for DSN information.
dbisql is a java app, and in 8.0.x defaulted to using jConnect which is
a pure Java library that implements the JDBC interface and uses TDS (tcp/ip)
to communicate to the engine. You can switch dbisql/scjview to use
iAnywhere's JDBC driver which uses ASA's ODBC driver (and is faster),
and as a result will also look at your .odbc.ini file for DSN information.
--
Mark Culp
ASA Research and Development
-------------------------------------------------------------------------
** Whitepapers, TechDocs, bug fixes are all available through the **
** iAnywhere Developer Community at http://www.ianywhere.com/developer **
-------------------------------------------------------------------------
[color=darkred]
> Bill Williams wrote:
>
> I am using a parameter file to start the engine. Here are the contents:
>
> -n asa800
> -s none
> -ti 0
> -cs
> /mnt/data/qc/Projects/CentralPet/System/Db/wcs1 -m -n centralPet
> /mnt/data/qc/Projects/QcDemo/System/Db/qcDemo -m -n qcDemo
> /mnt/data/qc/Projects/RedEnvelope/System/Db/WCS -m -n redEnvelope
> /mnt/data/qc/Projects/TommyHilfiger2004/System/Db/coreWCS -m -n
> tommyCore
> /mnt/data/qc/Projects/Dcms/underArmour -m -n dcms
>
> My command line is "dbsrv8 @paramFile".
>
> Here are my env vars you asked about when I start the dbsrv8 server:
>
> ASANY=/usr/local/sybase/SYBSsa8
> ASANY8=/usr/local/sybase/SYBSsa8
> TMP=/home/wlw/tmp
>
> Once I am trying to use the ASA 9, here are the env vars (it appears
> asa_config.sh in ASA9 does not set ASANY):
>
> ASANY=/usr/local/sybase/SYBSsa8
> ASANY8=/usr/local/sybase/SYBSsa8
> ASANY9=/usr/local/sybase/SYBSsa9
> TMP=/home/wlw/tmp
>
> According to the docs, UNIX only uses ASTMP and since it is not set, I would
> expect /tmp to be used.
>
> The directory /tmp/.SQLAnywhere exists as you say it should after I started
> the server.
>
> I did the strace command on the dbping and I did not see it looking for
> /tmp/.SQLAnywhere at all. The only thing it was doing in /tmp was apparently
> creating a directory for itself. No where in the file did I even see the word
> SQLAnywhere. It does however seem to work with the tcpip argument set for
> CommLinks like I stated earlier.
>
> I also did the strace to the dbisql command. It apparently never even looked
> for the odbc.ini file whereas the dbisqlc file looks for .odbc.ini and
> odbc.ini file pointed to by ODBCINI.
>
> It's a real pain that dbisql is not working. I can live with using the tcpip
> connection although I would like to figure out why the shared memory is not
> working.
>
> Mark Culp wrote:
>
>
>
>
>
Bill Williams

2005-04-05, 8:03 pm

Yes, the asa800 directory did exist under /tmp/.SQLAnywhere.

Here is the output from the grep:

execve("/usr/local/sybase/SYBSsa9/bin/dbping", ["dbping", "-c",
"asa800"], [/* 123 vars */]) = 0

That's all there is.

As far as dbisql is concerned, wouldn't it have to at least read the
odbc.ini file to figure out the parameters to use for jConnect since I
am only supplying the ODBC datasource name in the connection data
(dbisql -c "dsn=dcms")? Now, I'm not trying to start something here,
but according to the docs, dbisql defaults to ODBC. I thought I'd
mention that in case the docs are wrong and need to be corrected. I
also tried to run dbisql with the -ODBC option and it still did not look
in the odbc.ini file (according to strace).

Mark Culp wrote:
[color=darkred]
>Did you verify that /tmp/.SQLAnywhere/asa800 directory existed after you
>had started the server (named asa800) ?
>
>If the asa800 dir exists, run strace on dbping again:
> strace -o foo dbping -c asa800
>and then post the output to
> grep asa800 foo
>
>FWIW: dbisqlc is a ESQL app and therefore will use the contents of the
>.odbc.ini file to look for DSN information.
>dbisql is a java app, and in 8.0.x defaulted to using jConnect which is
>a pure Java library that implements the JDBC interface and uses TDS (tcp/ip)
>to communicate to the engine. You can switch dbisql/scjview to use
>iAnywhere's JDBC driver which uses ASA's ODBC driver (and is faster),
>and as a result will also look at your .odbc.ini file for DSN information.
>--
>Mark Culp
>ASA Research and Development
>-------------------------------------------------------------------------
>** Whitepapers, TechDocs, bug fixes are all available through the **
>** iAnywhere Developer Community at http://www.ianywhere.com/developer **
>-------------------------------------------------------------------------
>
>
>

Mark Culp

2005-04-05, 8:03 pm

First you are correct about dbisql defaulting to ODBC in 9.0.x.
AFAIK 8.0.x dbisql defaulted to jConnect.

As for the dbping, we must be missing some information...
Run the following test:
1) in one xterm/shell, run
strace -o foo.eng.log dbeng9 -n foo -z -o foo.console.log
2) in another xterm/shell, run
strace -o foo.ping.log dbping -c eng=foo
3) shutdown the engine

and then email me the foo.eng.log and foo.console.log and foo.ping.log
I'll have a quick look at the logs to see if I can figure out what's
happening. (email address: mark dot culp at ianywhere dot com)
--
Mark Culp
ASA Research and Development
-------------------------------------------------------------------------
** Whitepapers, TechDocs, bug fixes are all available through the **
** iAnywhere Developer Community at http://www.ianywhere.com/developer **
-------------------------------------------------------------------------
[color=darkred]
> Bill Williams wrote:
>
> Yes, the asa800 directory did exist under /tmp/.SQLAnywhere.
>
> Here is the output from the grep:
>
> execve("/usr/local/sybase/SYBSsa9/bin/dbping", ["dbping", "-c",
> "asa800"], [/* 123 vars */]) = 0
>
> That's all there is.
>
> As far as dbisql is concerned, wouldn't it have to at least read the odbc.ini
> file to figure out the parameters to use for jConnect since I am only
> supplying the ODBC datasource name in the connection data (dbisql -c
> "dsn=dcms")? Now, I'm not trying to start something here, but according to
> the docs, dbisql defaults to ODBC. I thought I'd mention that in case the
> docs are wrong and need to be corrected. I also tried to run dbisql with the
> -ODBC option and it still did not look in the odbc.ini file (according to
> strace).
>
> Mark Culp wrote:
>
Mark Culp

2005-04-05, 8:03 pm

I've looked at the logs that you sent me, and it appears that you are not
running the client and server in the same environment.

Your 8.0.x engine is creating its temp files in
/tmp/.SQLAnywhere/
But your 9.0.x engine and ping is using
/home/wlw/tmp/
and this is why the client cannot find/connect to the server via shmem.

So you must have something in your environment (between the two shells)
that is causing the s/w to pick/use different temp directories.

Please run
env > env.log
and post the results of the env.log file.

FYI: You commented that:
"I should have been smart enough to realize that it
is possible the shared memory connection between ASA versions 8 and 9
are not compatible."
and I would like to note that ASA version 6,7,8 and 9 are completely
compatible with each other and there is no reason (as long as your
environment is setup appropriately) that any client version should not
be able to connect to any other version of engine via tcp/ip or shmem.
[Of course to connect via shmem, both client and server must be running
on the same computer! :-]
--
Mark Culp
ASA Research and Development
-------------------------------------------------------------------------
** Whitepapers, TechDocs, bug fixes are all available through the **
** iAnywhere Developer Community at http://www.ianywhere.com/developer **
-------------------------------------------------------------------------
[color=darkred]
> Bill Williams wrote:
>
> Yes, the asa800 directory did exist under /tmp/.SQLAnywhere.
>
> Here is the output from the grep:
>
> execve("/usr/local/sybase/SYBSsa9/bin/dbping", ["dbping", "-c",
> "asa800"], [/* 123 vars */]) = 0
>
> That's all there is.
>
> As far as dbisql is concerned, wouldn't it have to at least read the odbc.ini
> file to figure out the parameters to use for jConnect since I am only
> supplying the ODBC datasource name in the connection data (dbisql -c
> "dsn=dcms")? Now, I'm not trying to start something here, but according to
> the docs, dbisql defaults to ODBC. I thought I'd mention that in case the
> docs are wrong and need to be corrected. I also tried to run dbisql with the
> -ODBC option and it still did not look in the odbc.ini file (according to
> strace).
>
> Mark Culp wrote:
>
Bill Williams

2005-04-05, 8:03 pm

Okay, I managed to confuse things here.

First, my asa800 engine I've been running has been an ASA 8.0.3 engine
with ASA 9 applications trying to create a shared memory connection. It
appears this does not work but I can understand why since these are
different versions. The tcpip link does work so that allows me to
connect to the database and I'm happy. I am sorry about any confusion I
created with this.

I am however still having issues connecting to the ASA 9.0.1 engine.
Everything I am trying below is using ASA 9 stuff right after I source
the asa_config.sh from the ASA9 bin directory.

* I can connect to the database using dbisqlc either with a shared
memory connection or a tcpip connection so I know connection is
possible.
* I can use dbping and ping the databases with both shared memory
and tcpip connections.
* I cannot connect to the database using dbisql with either type of
connection. I verified again with strace that the odbc.ini file
is never being looked at by dbisql. The details window when the
connection fails is full of unreadable characters.
* I cannot connect to the database with our application that we have
developed with either type of connection. These are C application
that are using ODBC linking in the unixODBC library. I verified
with strace that the application I'm trying to run is at least
opening odbc.ini. These applications work with no problems with
the combination of unixODBC and either ASA versions 7 or 8.
* Another thing I noticed running the dbsrv9 engine. It is creating
a /tmp/.SQLAnywhere directory, but nothing is in it. Instead, it
apparently is using my TMP variable setting and putting the asa900
(that's the name of this engine) under my /home/wlw/tmp
directory. According to the docs, the unix version uses only
ASTMP which I do not have set but that does not appear to be the case.
* <>Here is the parameter file I am using when starting the dbsrv9
engine (command line "dbsrv9 @asa900opts"):
<>-n asa900
<>-s none
<>-ti 0
<>-cs
<>/mnt/data/qc/Projects/UnderArmour/System/Db/underArmour -m
-n underArmour
<>

Again, I'm sorry if I got people off on a wild goose chase below.

Mark Culp wrote:
[color=darkred]
>First you are correct about dbisql defaulting to ODBC in 9.0.x.
>AFAIK 8.0.x dbisql defaulted to jConnect.
>
>As for the dbping, we must be missing some information...
>Run the following test:
>1) in one xterm/shell, run
> strace -o foo.eng.log dbeng9 -n foo -z -o foo.console.log
>2) in another xterm/shell, run
> strace -o foo.ping.log dbping -c eng=foo
>3) shutdown the engine
>
>and then email me the foo.eng.log and foo.console.log and foo.ping.log
>I'll have a quick look at the logs to see if I can figure out what's
>happening. (email address: mark dot culp at ianywhere dot com)
>--
>Mark Culp
>ASA Research and Development
>-------------------------------------------------------------------------
>** Whitepapers, TechDocs, bug fixes are all available through the **
>** iAnywhere Developer Community at http://www.ianywhere.com/developer **
>-------------------------------------------------------------------------
>
>
>

Bill Williams

2005-04-05, 8:03 pm

I have attached the environment from a shell for ASA 8 and a shell for
ASA 9. If I should not be attaching files, I apologize but there was so
much data, I thought it would be easier.

I just posted a message before I read this one where I notice that
dbsrv9 was using my /home/wlw/tmp directory. I noted in it according
the docs, the unix versions use only the ASTMP variable and since I
don't have it set, I would expect everything to use /tmp.

Mark Culp wrote:
[color=darkred]
>I've looked at the logs that you sent me, and it appears that you are not
>running the client and server in the same environment.
>
>Your 8.0.x engine is creating its temp files in
> /tmp/.SQLAnywhere/
>But your 9.0.x engine and ping is using
> /home/wlw/tmp/
>and this is why the client cannot find/connect to the server via shmem.
>
>So you must have something in your environment (between the two shells)
>that is causing the s/w to pick/use different temp directories.
>
>Please run
> env > env.log
>and post the results of the env.log file.
>
>FYI: You commented that:
> "I should have been smart enough to realize that it
> is possible the shared memory connection between ASA versions 8 and 9
> are not compatible."
>and I would like to note that ASA version 6,7,8 and 9 are completely
>compatible with each other and there is no reason (as long as your
>environment is setup appropriately) that any client version should not
>be able to connect to any other version of engine via tcp/ip or shmem.
>[Of course to connect via shmem, both client and server must be running
>on the same computer! :-]
>--
>Mark Culp
>ASA Research and Development
>-------------------------------------------------------------------------
>** Whitepapers, TechDocs, bug fixes are all available through the **
>** iAnywhere Developer Community at http://www.ianywhere.com/developer **
>-------------------------------------------------------------------------
>
>
>

Mark Culp

2005-04-05, 8:03 pm

Ok, I had another look at the code, and it appears that sometime between
8.0.x and 9.0.x the code got changed so that the unix s/w looks for
ASTMP
TMP
TMPDIR
TEMP
(in that order) to determine where to puts its temporary files.

I checked the 9.0.x docs and at least the version that I'm looking at
already has the correct list (shown above).

As for your problem, make sure that both/all of your environments are
set up so that ASA/SQLAnywhere will use the same location for their
temporary files - I suggest that you set ASTMP to be something consistent.

This should solve your connections problems.

I do not know why dbisql is not using your odbc.ini file - I suggest you
start a new posting since I suspect most people have long dropped this
discussion. FWIW Since you have already done an strace on it, look for
any references to shared objects (.so) and see if there is any reference
to libdb*.so*. The java tool should be attempting to load one of the
ASA libraries in order to read the odbc.ini file. If dbisql cannot
find/load the library, that would explain why there is no reference to
your odbc.ini file.

- Mark

Bill Williams wrote:
>
> I have attached the environment from a shell for ASA 8 and a shell for
> ASA 9. If I should not be attaching files, I apologize but there was so
> much data, I thought it would be easier.
>
> I just posted a message before I read this one where I notice that
> dbsrv9 was using my /home/wlw/tmp directory. I noted in it according
> the docs, the unix versions use only the ASTMP variable and since I
> don't have it set, I would expect everything to use /tmp.
>
> Mark Culp wrote:
>
>
> --------------------------------------------------------------------------------
> AIPC=/mnt/data/qc/Projects/AIPC
> AMGREET=/mnt/data/qc/Projects/AmericanGreetings
> ANT=/usr/local/apache-ant
> ANT_HOME=/usr/local/apache-ant
> ASA=/usr/local/sybase/SYBSsa8
> ASA8=/usr/local/sybase/SYBSsa8
> ASA9=/usr/local/sybase/SYBSsa9
> ASANY=/usr/local/sybase/SYBSsa8
> ASANY8=/usr/local/sybase/SYBSsa8
> ASANYSH8=/usr/local/sybase/shared
> BABBAGES=/mnt/data/qc/Projects/Babbages
> BACKSPACE=Delete
> BASH=/bin/bash
> BASH_VERSINFO=([0]="2" [1]="05b" [2]="0" [3]="1" [4]="release" [5]="i586-mandrake-linux-gnu")
> BASH_VERSION='2.05b.0(1)-release'
> BSNUM=14
> CATALINA_HOME=/usr/local/jakarta-tomcat
> CENTRALPET=/mnt/data/qc/Projects/CentralPet
> CHILDGROUP=/mnt/data/qc/Projects/ChildrensGroup
> CLASS=beginner
> CLASSPATH=/usr/local/sybase/SYBSsa8/java/jlogon.jar:/usr/local/sybase/shared/jConnect-5_5/classes/jconn2.jar::/usr/local/hsqldb/lib/hsqldb.jar:/mnt/data/qc/Products/Classes:/mnt/data/qc/Products/Classes/JarFiles/java-getopt-1.0.9.jar:.
> COACH=/mnt/data/qc/Projects/Coach
> COLUMNS=155
> COMPILER=GNU
> COMPILER_ENV=Linux
> DEVDEFAULTS=/mnt/data/qc/Develop/Src/.defaults
> DEVDIR=/mnt/data/qc/Develop
> DIRSTACK=()
> DISPLAY=:0.0
> DOW=/mnt/data/qc/Projects/Dow
> ENV=/home/wlw/.bashrc
> EUID=108
> FIDELITY=/mnt/data/qc/Projects/Fidelity
> GAMESTOP=/mnt/data/qc/Projects/GameStop
> GCONF_TMPDIR=/tmp
> GFS=/mnt/data/qc/Projects/GFS
> GROUPS=()
> G_BROKEN_FILENAMES=1

> HISTCONTROL=ignoredu
ps
> HISTFILE=/home/wlw/.bash_history
> HISTFILESIZE=1000
> HISTSIZE=1000
> HOME=/home/wlw
> HOSTNAME=mercury
> HOSTTYPE=i586
> HSQLDB_HOME=/usr/local/hsqldb
> IFS=$' \t\n'
> INGRAMMICRO=/mnt/data/qc/Projects/IngramMicro
> INPUTRC=/etc/inputrc
> JAVA=/usr/local/java
> JAVADOC_HOME=/mnt/data/qc/JavaDoc
> JAVA_HOME=/usr/local/java/jdk1.5.0_01
> JDK=/usr/local/java/jdk1.5.0_01
> JDK142=/usr/local/java/j2sdk1.4.2_01
> JDK150=/usr/local/java/jdk1.5.0_01
> JRE=/usr/local/java/jdk1.5.0_01/jre
> JSWAT=/usr/local/jswat
> JVER=1.5
> KBCHARSET=C
> KEYBOARD=us
> KEYTABLE=us
> LANG=en_US
> LANGUAGE=en_US:en
> LC_ADDRESS=en_US
> LC_COLLATE=en_US
> LC_CTYPE=en_US
> LC_IDENTIFICATION=en
_US
> LC_MEASUREMENT=en_US

> LC_MESSAGES=en_US
> LC_MONETARY=en_US
> LC_NAME=en_US
> LC_NUMERIC=en_US
> LC_PAPER=en_US
> LC_SOURCED=1
> LC_TELEPHONE=en_US
> LC_TIME=en_US
> LD_LIBRARY_PATH=/usr/local/sybase/SYBSsa8/lib:/usr/local/sybase/SYBSsa8/jre/lib/i386/client:/usr/local/sybase/SYBSsa8/jre/lib/i386:/usr/local/sybase/SYBSsa8/jre/lib/i386/native_threads:/usr/local/sybase/SYBSsa8/drivers/lib:/usr/local/unixODBC/lib::/usr/

local/netscape/Cool:/usr/local/netscape:/usr/local/lib:/usr/local/sybase/SYBSsa8/lib:/mnt/data/qc/Develop/Obj/Linux/Lib:/mnt/data/qc/Products/Obj/Linux/Lib
> LESS=-MM
> LESSKEY=/etc/.less
> LESSOPEN='|/usr/bin/lesspipe.sh %s'
> LIBSAFE=no
> LINES=29
> LOGNAME=wlw
> LS_COLORS='no=00:fi=
00:di=01;34:ln=01;36
:pi=40;33:so=01;35:b
d=40;33;01:cd=40;33;
01:or=01;05;37;41:mi
=01;05;37;41:ex=01;3
2:*.cmd=01;32:*.exe=01;32:*.com=01;32:*.btm=01;32:*.bat=01;32:*.sh=01;32:*.csh=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:

*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.bz2=01;31:*.bz=01;31:*.tz=01;31:*.rpm=01;31:*.cpio=01;31:*.jpg=01;35:*.gif=01;35:*.bmp=01;35:*.xbm=01;35:*.xpm=01;35:*.png=01;35:*. tif=01;35:'
> LS_OPTIONS='-F --color=auto'
> MACHTYPE=i586-mandrake-linux-gnu
> MAIL=/var/spool/mail/wlw
> MAILCHECK=60
> META_CLASS=download
> MOZILLA_FIVE_HOME=/usr/local/netscape
> MVC=/mnt/data/qc/Projects/MajorVideoConcept
> NLSPATH=/usr/share/locale/%l/%N
> OAKLEY=/mnt/data/qc/Projects/Oakley
> ODBC=/usr/local/unixODBC
> ODBCINI=/usr/local/unixODBC/etc/odbc.ini
> OLDPWD=/mnt/data/qc/Projects
> OPTERR=1
> OPTIND=1
> OSTYPE=linux-gnu
> PATH=/usr/local/sybase/SYBSsa8/bin:/usr/local/sybase/shared/sybcentral41:/bin:/usr/bin:/usr/local/bin:/usr/bin/X11:/usr/X11R6/bin:/usr/local/java/jdk1.5.0_01/bin:/etc/ppp:/usr/local/sybase/SYBSsa8/bin:/usr/local/netscape:/usr/local/apache-ant/bin:/usr/l

ocal/hsqldb/bin:/usr/local/unixODBC/bin:/mnt/data/qc/Bin/Linux:/mnt/data/qc/Bin:/mnt/data/qc/Develop/Obj/Linux/Bin:/mnt/data/qc/Products/Obj/Linux/Bin:/home/wlw/bin
> PIPESTATUS=([0]="0")
> PLEASANT=/mnt/data/qc/Projects/Pleasant
> PLOWHEARTH=/mnt/data/qc/Projects/PlowHearth
> PPID=29821
> PRINTER=dj692c
> PRODUCTS=/mnt/data/qc/Products
> PROJECTS=/mnt/data/qc/Projects
> PROMPT_COMMAND='echo
-ne " \033]0;${USER}@${HOS
TNAME}: ${PWD}\007"'
> PS1='JDK1.5:\w\$ '
> PS2='> '
> PS4='+ '
> PWD=/home/wlw
> PYTHONSTARTUP=/etc/pythonrc.py
> QCDEMO=/mnt/data/qc/Projects/QcDemo
> QTDIR=/usr/lib/qt3/
> RAYTHEON=/mnt/data/qc/Projects/Raytheon
> REDENVELOPE=/mnt/data/qc/Projects/RedEnvelope
> ROTRACK=/mnt/data/qc/Projects/RotaryRakY2k
> SECURE_LEVEL=2
> SECURITY=2
> SHELL=/bin/bash
> SHELLOPTS=braceexpan
d:emacs:hashall:hist
expand:history:inter
active-comments:monitor
> SHLVL=1
> STAPLES=/mnt/data/qc/Projects/Staples
> SYBASE=/usr/local/sybase
> TERM=xterm
> TMOUT=0
> TMP=/home/wlw/tmp
> TMPDIR=/home/wlw/tmp
> TOMMYHILFIGER=/mnt/data/qc/Projects/TommyHilfiger
> UARMOUR=/mnt/data/qc/Projects/UnderArmour
> UID=108
> UMASK_ROOT=02
> UMASK_USER=02
> USER=wlw
> USERNAME=
> USPS=/mnt/data/qc/Projects/PostOffice
> VANDERLANDE=/mnt/data/qc/Projects/VanDerLande
> VERIZON=/mnt/data/qc/Projects/Verizon
> XAUTHORITY=/home/wlw/.Xauthority
> _=cd
> choice=2
> screen ()
> {
> if [ -z "$SCREENDIR" ]; then
> export SCREENDIR=$HOME/tmp;
> fi;
> /usr/bin/screen $@
> }
>
> --------------------------------------------------------------------------------
> AIPC=/mnt/data/qc/Projects/AIPC
> AMGREET=/mnt/data/qc/Projects/AmericanGreetings
> ANT=/usr/local/apache-ant
> ANT_HOME=/usr/local/apache-ant
> ASA=/usr/local/sybase/SYBSsa8
> ASA8=/usr/local/sybase/SYBSsa8
> ASA9=/usr/local/sybase/SYBSsa9
> ASANY9=/usr/local/sybase/SYBSsa9
> ASANYSH9=/usr/local/sybase/shared
> BABBAGES=/mnt/data/qc/Projects/Babbages
> BACKSPACE=Delete
> BASH=/bin/bash
> BASH_VERSINFO=([0]="2" [1]="05b" [2]="0" [3]="1" [4]="release" [5]="i586-mandrake-linux-gnu")
> BASH_VERSION='2.05b.0(1)-release'
> BSNUM=14
> CATALINA_HOME=/usr/local/jakarta-tomcat
> CENTRALPET=/mnt/data/qc/Projects/CentralPet
> CHILDGROUP=/mnt/data/qc/Projects/ChildrensGroup
> CLASS=beginner
> CLASSPATH=:/usr/local/hsqldb/lib/hsqldb.jar:/mnt/data/qc/Products/Classes:/mnt/data/qc/Products/Classes/JarFiles/java-getopt-1.0.9.jar:.
> COACH=/mnt/data/qc/Projects/Coach
> COLUMNS=155
> COMPILER=GNU
> COMPILER_ENV=Linux
> DEVDEFAULTS=/mnt/data/qc/Develop/Src/.defaults
> DEVDIR=/mnt/data/qc/Develop
> DIRSTACK=()
> DISPLAY=:0.0
> DOW=/mnt/data/qc/Projects/Dow
> ENV=/home/wlw/.bashrc
> EUID=108
> FIDELITY=/mnt/data/qc/Projects/Fidelity
> GAMESTOP=/mnt/data/qc/Projects/GameStop
> GCONF_TMPDIR=/tmp
> GFS=/mnt/data/qc/Projects/GFS
> GROUPS=()
> G_BROKEN_FILENAMES=1

> HISTCONTROL=ignoredu
ps
> HISTFILE=/home/wlw/.bash_history
> HISTFILESIZE=1000
> HISTSIZE=1000
> HOME=/home/wlw
> HOSTNAME=mercury
> HOSTTYPE=i586
> HSQLDB_HOME=/usr/local/hsqldb
> IFS=$' \t\n'
> INGRAMMICRO=/mnt/data/qc/Projects/IngramMicro
> INPUTRC=/etc/inputrc
> JAVA=/usr/local/java
> JAVADOC_HOME=/mnt/data/qc/JavaDoc
> JAVA_HOME=/usr/local/java/jdk1.5.0_01
> JDK=/usr/local/java/jdk1.5.0_01
> JDK142=/usr/local/java/j2sdk1.4.2_01
> JDK150=/usr/local/java/jdk1.5.0_01
> JRE=/usr/local/java/jdk1.5.0_01/jre
> JSWAT=/usr/local/jswat
> JVER=1.5
> KBCHARSET=C
> KEYBOARD=us
> KEYTABLE=us
> LANG=en_US
> LANGUAGE=en_US:en
> LC_ADDRESS=en_US
> LC_COLLATE=en_US
> LC_CTYPE=en_US
> LC_IDENTIFICATION=en
_US
> LC_MEASUREMENT=en_US

> LC_MESSAGES=en_US
> LC_MONETARY=en_US
> LC_NAME=en_US
> LC_NUMERIC=en_US
> LC_PAPER=en_US
> LC_SOURCED=1
> LC_TELEPHONE=en_US
> LC_TIME=en_US
> LD_LIBRARY_PATH=/usr/local/sybase/SYBSsa9/lib:/usr/local/sybase/SYBSsa9/jre142/lib/i386/client:/usr/local/sybase/SYBSsa9/jre142/lib/i386:/usr/local/sybase/SYBSsa9/jre142/lib/i386/native_threads:/usr/local/sybase/SYBSsa9/drivers/lib:/usr/local/unixODBC/l

ib::/usr/local/netscape/Cool:/usr/local/netscape:/usr/local/lib:/usr/local/sybase/SYBSsa8/lib:/mnt/data/qc/Develop/Obj/Linux/Lib:/mnt/data/qc/Products/Obj/Linux/Lib
> LESS=-MM
> LESSKEY=/etc/.less
> LESSOPEN='|/usr/bin/lesspipe.sh %s'
> LIBSAFE=no
> LINES=29
> LOGNAME=wlw
> LS_COLORS='no=00:fi=
00:di=01;34:ln=01;36
:pi=40;33:so=01;35:b
d=40;33;01:cd=40;33;
01:or=01;05;37;41:mi
=01;05;37;41:ex=01;3
2:*.cmd=01;32:*.exe=01;32:*.com=01;32:*.btm=01;32:*.bat=01;32:*.sh=01;32:*.csh=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:

*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.bz2=01;31:*.bz=01;31:*.tz=01;31:*.rpm=01;31:*.cpio=01;31:*.jpg=01;35:*.gif=01;35:*.bmp=01;35:*.xbm=01;35:*.xpm=01;35:*.png=01;35:*. tif=01;35:'
> LS_OPTIONS='-F --color=auto'
> MACHTYPE=i586-mandrake-linux-gnu
> MAIL=/var/spool/mail/wlw
> MAILCHECK=60
> META_CLASS=download
> MOZILLA_FIVE_HOME=/usr/local/netscape
> MVC=/mnt/data/qc/Projects/MajorVideoConcept
> NLSPATH=/usr/share/locale/%l/%N
> OAKLEY=/mnt/data/qc/Projects/Oakley
> ODBC=/usr/local/unixODBC
> ODBCINI=/usr/local/unixODBC/etc/odbc.ini
> OPTERR=1
> OPTIND=1
> OSTYPE=linux-gnu
> PATH=/usr/local/sybase/SYBSsa9/bin:/usr/local/sybase/shared/sybcentral43:/bin:/usr/bin:/usr/local/bin:/usr/bin/X11:/usr/X11R6/bin:/usr/local/java/jdk1.5.0_01/bin:/etc/ppp:/usr/local/sybase/SYBSsa8/bin:/usr/local/netscape:/usr/local/apache-ant/bin:/usr/l

ocal/hsqldb/bin:/usr/local/unixODBC/bin:/mnt/data/qc/Bin/Linux:/mnt/data/qc/Bin:/mnt/data/qc/Develop/Obj/Linux/Bin:/mnt/data/qc/Products/Obj/Linux/Bin:/home/wlw/bin
> PIPESTATUS=([0]="0")
> PLEASANT=/mnt/data/qc/Projects/Pleasant
> PLOWHEARTH=/mnt/data/qc/Projects/PlowHearth
> PPID=30224
> PRINTER=dj692c
> PRODUCTS=/mnt/data/qc/Products
> PROJECTS=/mnt/data/qc/Projects
> PROMPT_COMMAND='echo
-ne " \033]0;${USER}@${HOS
TNAME}: ${PWD}\007"'
> PS1='JDK1.5:\w\$ '
> PS2='> '
> PS4='+ '
> PWD=/home/wlw
> PYTHONSTARTUP=/etc/pythonrc.py
> QCDEMO=/mnt/data/qc/Projects/QcDemo
> QTDIR=/usr/lib/qt3/
> RAYTHEON=/mnt/data/qc/Projects/Raytheon
> REDENVELOPE=/mnt/data/qc/Projects/RedEnvelope
> ROTRACK=/mnt/data/qc/Projects/RotaryRakY2k
> SECURE_LEVEL=2
> SECURITY=2
> SHELL=/bin/bash
> SHELLOPTS=braceexpan
d:emacs:hashall:hist
expand:history:inter
active-comments:monitor
> SHLVL=1
> STAPLES=/mnt/data/qc/Projects/Staples
> SYBASE=/usr/local/sybase
> TERM=xterm
> TMOUT=0
> TMP=/home/wlw/tmp
> TMPDIR=/home/wlw/tmp
> TOMMYHILFIGER=/mnt/data/qc/Projects/TommyHilfiger
> UARMOUR=/mnt/data/qc/Projects/UnderArmour
> UID=108
> UMASK_ROOT=02
> UMASK_USER=02
> USER=wlw
> USERNAME=
> USPS=/mnt/data/qc/Projects/PostOffice
> VANDERLANDE=/mnt/data/qc/Projects/VanDerLande
> VERIZON=/mnt/data/qc/Projects/Verizon
> XAUTHORITY=/home/wlw/.Xauthority
> _=/usr/local/sybase/SYBSsa9/bin/asa_config.sh
> choice=2
> screen ()
> {
> if [ -z "$SCREENDIR" ]; then
> export SCREENDIR=$HOME/tmp;
> fi;
> /usr/bin/screen $@
> }

Bill Williams

2005-04-05, 8:03 pm

Thanks for the help.

I'll do the additional checking you suggest for dbisql and start a new
post if I'm still having problems.

Mark Culp wrote:[color=darkred
]
> Ok, I had another look at the code, and it appears that sometime between
> 8.0.x and 9.0.x the code got changed so that the unix s/w looks for
> ASTMP
> TMP
> TMPDIR
> TEMP
> (in that order) to determine where to puts its temporary files.
>
> I checked the 9.0.x docs and at least the version that I'm looking at
> already has the correct list (shown above).
>
> As for your problem, make sure that both/all of your environments are
> set up so that ASA/SQLAnywhere will use the same location for their
> temporary files - I suggest that you set ASTMP to be something consistent.
>
> This should solve your connections problems.
>
> I do not know why dbisql is not using your odbc.ini file - I suggest you
> start a new posting since I suspect most people have long dropped this
> discussion. FWIW Since you have already done an strace on it, look for
> any references to shared objects (.so) and see if there is any reference
> to libdb*.so*. The java tool should be attempting to load one of the
> ASA libraries in order to read the odbc.ini file. If dbisql cannot
> find/load the library, that would explain why there is no reference to
> your odbc.ini file.
>
> - Mark
>
> Bill Williams wrote:
>
local/netscape/Cool:/usr/local/netscape:/usr/local/lib:/usr/local/sybase/SYBSsa8/lib:/mnt/data/qc/Develop/Obj/Linux/Lib:/mnt/data/qc/Products/Obj/Linux/Lib[color=darkred]
*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.bz2=01;31:*.bz=01;31:*.tz=01;31:*.rpm=01;31:*.cpio=01;31:*.jpg=01;35:*.gif=01;35:*.bmp=01;35:*.xbm=01;35:*.xpm=01;35:*.png=01;35:*. tif=01;35:'[color=da
rkred]
ocal/hsqldb/bin:/usr/local/unixODBC/bin:/mnt/data/qc/Bin/Linux:/mnt/data/qc/Bin:/mnt/data/qc/Develop/Obj/Linux/Bin:/mnt/data/qc/Products/Obj/Linux/Bin:/home/wlw/bin[color=darkred]
ib::/usr/local/netscape/Cool:/usr/local/netscape:/usr/local/lib:/usr/local/sybase/SYBSsa8/lib:/mnt/data/qc/Develop/Obj/Linux/Lib:/mnt/data/qc/Products/Obj/Linux/Lib[color=darkred]
*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.bz2=01;31:*.bz=01;31:*.tz=01;31:*.rpm=01;31:*.cpio=01;31:*.jpg=01;35:*.gif=01;35:*.bmp=01;35:*.xbm=01;35:*.xpm=01;35:*.png=01;35:*. tif=01;35:'[color=da
rkred]
ocal/hsqldb/bin:/usr/local/unixODBC/bin:/mnt/data/qc/Bin/Linux:/mnt/data/qc/Bin:/mnt/data/qc/Develop/Obj/Linux/Bin:/mnt/data/qc/Products/Obj/Linux/Bin:/home/wlw/bin[color=darkred]
Bill Williams

2005-04-05, 8:03 pm

The shared memory connection between ASA 9 client software (dbping) and
a ASA 8 engine is still failing.

I just performed a test. I have the ASA 8 engine running and verified
the .SQLAnywhere directory is in the /tmp directory.

I then started a xterm and sourced the asa_config.sh from ASA 9. I
first did a strace on dbping without setting the ASTMP variable and
verified it was looking in /home/wlw/tmp. It apparently is creating
some temporary files of its own in that directory. One thing I noticed
is it never looked for any directory called .SQLAnywhere. Obviously
this failed like expected based off of the information you have given me.

I then set the ASTMP to be /tmp. I then ran strace again and it was
using /tmp for its own temp files. However this failed also. Again, I
noticed it never even tried to look in .SQLAnywhere (at least I could
find no reference to it in the strace output).

Mark Culp wrote:
[color=darkred]
> Ok, I had another look at the code, and it appears that sometime between
> 8.0.x and 9.0.x the code got changed so that the unix s/w looks for
> ASTMP
> TMP
> TMPDIR
> TEMP
> (in that order) to determine where to puts its temporary files.
>
> I checked the 9.0.x docs and at least the version that I'm looking at
> already has the correct list (shown above).
>
> As for your problem, make sure that both/all of your environments are
> set up so that ASA/SQLAnywhere will use the same location for their
> temporary files - I suggest that you set ASTMP to be something consistent.
>
> This should solve your connections problems.
>
> I do not know why dbisql is not using your odbc.ini file - I suggest you
> start a new posting since I suspect most people have long dropped this
> discussion. FWIW Since you have already done an strace on it, look for
> any references to shared objects (.so) and see if there is any reference
> to libdb*.so*. The java tool should be attempting to load one of the
> ASA libraries in order to read the odbc.ini file. If dbisql cannot
> find/load the library, that would explain why there is no reference to
> your odbc.ini file.
>
> - Mark
>
> Bill Williams wrote:
>
local/netscape/Cool:/usr/local/netscape:/usr/local/lib:/usr/local/sybase/SYBSsa8/lib:/mnt/data/qc/Develop/Obj/Linux/Lib:/mnt/data/qc/Products/Obj/Linux/Lib[color=darkred]
*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.bz2=01;31:*.bz=01;31:*.tz=01;31:*.rpm=01;31:*.cpio=01;31:*.jpg=01;35:*.gif=01;35:*.bmp=01;35:*.xbm=01;35:*.xpm=01;35:*.png=01;35:*. tif=01;35:'[color=da
rkred]
ocal/hsqldb/bin:/usr/local/unixODBC/bin:/mnt/data/qc/Bin/Linux:/mnt/data/qc/Bin:/mnt/data/qc/Develop/Obj/Linux/Bin:/mnt/data/qc/Products/Obj/Linux/Bin:/home/wlw/bin[color=darkred]
ib::/usr/local/netscape/Cool:/usr/local/netscape:/usr/local/lib:/usr/local/sybase/SYBSsa8/lib:/mnt/data/qc/Develop/Obj/Linux/Lib:/mnt/data/qc/Products/Obj/Linux/Lib[color=darkred]
*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.bz2=01;31:*.bz=01;31:*.tz=01;31:*.rpm=01;31:*.cpio=01;31:*.jpg=01;35:*.gif=01;35:*.bmp=01;35:*.xbm=01;35:*.xpm=01;35:*.png=01;35:*. tif=01;35:'[color=da
rkred]
ocal/hsqldb/bin:/usr/local/unixODBC/bin:/mnt/data/qc/Bin/Linux:/mnt/data/qc/Bin:/mnt/data/qc/Develop/Obj/Linux/Bin:/mnt/data/qc/Products/Obj/Linux/Bin:/home/wlw/bin[color=darkred]
Mark Culp

2005-04-05, 8:03 pm

For the client and server to be able to connect via shmem, they both must
be looking in the same place. i.e. they must both have the same tmp dir.
For some reason, your client and server are using different directories,
so there must be something in your environment that is causing this issue.

Try setting ASTMP before starting the engine AND before starting the client.

- Mark

Bill Williams wrote:[color=darkred
]
>
> The shared memory connection between ASA 9 client software (dbping) and
> a ASA 8 engine is still failing.
>
> I just performed a test. I have the ASA 8 engine running and verified
> the .SQLAnywhere directory is in the /tmp directory.
>
> I then started a xterm and sourced the asa_config.sh from ASA 9. I
> first did a strace on dbping without setting the ASTMP variable and
> verified it was looking in /home/wlw/tmp. It apparently is creating
> some temporary files of its own in that directory. One thing I noticed
> is it never looked for any directory called .SQLAnywhere. Obviously
> this failed like expected based off of the information you have given me.
>
> I then set the ASTMP to be /tmp. I then ran strace again and it was
> using /tmp for its own temp files. However this failed also. Again, I
> noticed it never even tried to look in .SQLAnywhere (at least I could
> find no reference to it in the strace output).
>
> Mark Culp wrote:
>
r/local/netscape/Cool:/usr/local/netscape:/usr/local/lib:/usr/local/sybase/SYBSsa8/lib:/mnt/data/qc/Develop/Obj/Linux/Lib:/mnt/data/qc/Products/Obj/Linux/Lib[color=darkred]
1:*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.bz2=01;31:*.bz=01;31:*.tz=01;31:*.rpm=01;31:*.cpio=01;31:*.jpg=01;35:*.gif=01;35:*.bmp=01;35:*.xbm=01;35:*.xpm=01;35:*.png=01;35:*. tif=01;35:'[color=da
rkred]
/local/hsqldb/bin:/usr/local/unixODBC/bin:/mnt/data/qc/Bin/Linux:/mnt/data/qc/Bin:/mnt/data/qc/Develop/Obj/Linux/Bin:/mnt/data/qc/Products/Obj/Linux/Bin:/home/wlw/bin[color=darkred]
/lib::/usr/local/netscape/Cool:/usr/local/netscape:/usr/local/lib:/usr/local/sybase/SYBSsa8/lib:/mnt/data/qc/Develop/Obj/Linux/Lib:/mnt/data/qc/Products/Obj/Linux/Lib[color=darkred]
1:*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.bz2=01;31:*.bz=01;31:*.tz=01;31:*.rpm=01;31:*.cpio=01;31:*.jpg=01;35:*.gif=01;35:*.bmp=01;35:*.xbm=01;35:*.xpm=01;35:*.png=01;35:*. tif=01;35:'[color=da
rkred]
/local/hsqldb/bin:/usr/local/unixODBC/bin:/mnt/data/qc/Bin/Linux:/mnt/data/qc/Bin:/mnt/data/qc/Develop/Obj/Linux/Bin:/mnt/data/qc/Products/Obj/Linux/Bin:/home/wlw/bin[color=darkred]
Bill Williams

2005-04-05, 8:03 pm

I did set ASTMP for the ASA 9 client software but did not for the ASA 8
server engine. I assumed (I know this is not good) that since the
..SQLAnywhere directory was being created by the server engine in the
/tmp directory, the only thing I needed to do was set ASTMP for ASA 9 to
/tmp.

I'll try setting ASTMP for both the engine and client software today.

Mark Culp wrote:[color=darkred
]
> For the client and server to be able to connect via shmem, they both must
> be looking in the same place. i.e. they must both have the same tmp dir.
> For some reason, your client and server are using different directories,
> so there must be something in your environment that is causing this issue.
>
> Try setting ASTMP before starting the engine AND before starting the client.
>
> - Mark
>
> Bill Williams wrote:
>
r/local/netscape/Cool:/usr/local/netscape:/usr/local/lib:/usr/local/sybase/SYBSsa8/lib:/mnt/data/qc/Develop/Obj/Linux/Lib:/mnt/data/qc/Products/Obj/Linux/Lib[color=darkred]
1:*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.bz2=01;31:*.bz=01;31:*.tz=01;31:*.rpm=01;31:*.cpio=01;31:*..jpg=01;35:*.gif=01;35:*.bmp=01;35:*.xbm=01;35:*.xpm=01;35:*.png=01;35:*. tif=01;35:'[color=da
rkred]
/local/hsqldb/bin:/usr/local/unixODBC/bin:/mnt/data/qc/Bin/Linux:/mnt/data/qc/Bin:/mnt/data/qc/Develop/Obj/Linux/Bin:/mnt/data/qc/Products/Obj/Linux/Bin:/home/wlw/bin[color=darkred]
/lib::/usr/local/netscape/Cool:/usr/local/netscape:/usr/local/lib:/usr/local/sybase/SYBSsa8/lib:/mnt/data/qc/Develop/Obj/Linux/Lib:/mnt/data/qc/Products/Obj/Linux/Lib[color=darkred]
1:*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.bz2=01;31:*.bz=01;31:*.tz=01;31:*.rpm=01;31:*.cpio=01;31:*.jpg=01;35:*.gif=01;35:*.bmp=01;35:*.xbm=01;35:*.xpm=01;35:*.png=01;35:*. tif=01;35:'[color=da
rkred]
/local/hsqldb/bin:/usr/local/unixODBC/bin:/mnt/data/qc/Bin/Linux:/mnt/data/qc/Bin:/mnt/data/qc/Develop/Obj/Linux/Bin:/mnt/data/qc/Products/Obj/Linux/Bin:/home/wlw/bin[color=darkred]
Bill Williams

2005-04-05, 8:03 pm

I just set it up as you suggested and everything worked. I learned
something here. I had assumed that the .SQLAnywhere directory would be
created under the directory pointed to by ASTMP. And then within that
directory would be the asa800 directory for the engine itself. That
wasn't the case. I set ASTMP=/tmp and noticed the asa800 directory was
created directly under /tmp, .SQLAnywhere was not used at all.

Thanks for the help.

BTW, I also figured out the problem with dbisql. It has to do with the
order of directories in my LD_LIBRARY_PATH. When I was sourcing
asa_config.sh, it was putting all of its directories first. Well, then
I noticed in my /etc/profile, I would source asa_config.sh and then add
the unixODBC library directory in front of everything else in
LD_LIBRARY_PATH which effectively put it before the ASA stuff. Once I
made sure I was doing something like that when I source the ASA 9
asa_config.sh, everything worked fine.

Again, thanks for helping me out.

Mark Culp wrote:
[color=darkred]
> For the client and server to be able to connect via shmem, they both must
> be looking in the same place. i.e. they must both have the same tmp dir.
> For some reason, your client and server are using different directories,
> so there must be something in your environment that is causing this issue.
>
> Try setting ASTMP before starting the engine AND before starting the client.
>
> - Mark
>
> Bill Williams wrote:
>
r/local/netscape/Cool:/usr/local/netscape:/usr/local/lib:/usr/local/sybase/SYBSsa8/lib:/mnt/data/qc/Develop/Obj/Linux/Lib:/mnt/data/qc/Products/Obj/Linux/Lib[color=darkred]
1:*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.bz2=01;31:*.bz=01;31:*.tz=01;31:*.rpm=01;31:*.cpio=01;31:*.jpg=01;35:*.gif=01;35:*.bmp=01;35:*.xbm=01;35:*.xpm=01;35:*.png=01;35:*. tif=01;35:'[color=da
rkred]
/local/hsqldb/bin:/usr/local/unixODBC/bin:/mnt/data/qc/Bin/Linux:/mnt/data/qc/Bin:/mnt/data/qc/Develop/Obj/Linux/Bin:/mnt/data/qc/Products/Obj/Linux/Bin:/home/wlw/bin[color=darkred]
/lib::/usr/local/netscape/Cool:/usr/local/netscape:/usr/local/lib:/usr/local/sybase/SYBSsa8/lib:/mnt/data/qc/Develop/Obj/Linux/Lib:/mnt/data/qc/Products/Obj/Linux/Lib[color=darkred]
1:*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.bz2=01;31:*.bz=01;31:*.tz=01;31:*.rpm=01;31:*.cpio=01;31:*.jpg=01;35:*.gif=01;35:*.bmp=01;35:*.xbm=01;35:*.xpm=01;35:*.png=01;35:*. tif=01;35:'[color=da
rkred]
/local/hsqldb/bin:/usr/local/unixODBC/bin:/mnt/data/qc/Bin/Linux:/mnt/data/qc/Bin:/mnt/data/qc/Develop/Obj/Linux/Bin:/mnt/data/qc/Products/Obj/Linux/Bin:/home/wlw/bin[color=darkred]
Mark Culp

2005-04-05, 8:03 pm

I'm glad that you finally have it working.

FWIW: Your issue has shown that there is a subtle incompatibility between
8.0.x and 9.0.x. The issue is:
- 8.0.x looks for/uses ASTMP
and then uses /tmp/.SQLAnywhere if it is not found
- 9.0.x looks for/uses ASTMP, TMP, TMPDIR, and TEMP
and then uses /tmp/.SQLAnywhere if none of them are found

So the problem is that if a user (like you) has TMP set and is using
a mix of 8.0.x and 9.0.x (like you are), they can't connect using shmem.
I don't see any fix to this issue other than to set ASTMP.

I've sent a note to the doc team to get this documented appropriately.

- Mark

Bill Williams wrote:[color=darkred
]
>
> I just set it up as you suggested and everything worked. I learned
> something here. I had assumed that the .SQLAnywhere directory would be
> created under the directory pointed to by ASTMP. And then within that
> directory would be the asa800 directory for the engine itself. That
> wasn't the case. I set ASTMP=/tmp and noticed the asa800 directory was
> created directly under /tmp, .SQLAnywhere was not used at all.
>
> Thanks for the help.
>
> BTW, I also figured out the problem with dbisql. It has to do with the
> order of directories in my LD_LIBRARY_PATH. When I was sourcing
> asa_config.sh, it was putting all of its directories first. Well, then
> I noticed in my /etc/profile, I would source asa_config.sh and then add
> the unixODBC library directory in front of everything else in
> LD_LIBRARY_PATH which effectively put it before the ASA stuff. Once I
> made sure I was doing something like that when I source the ASA 9
> asa_config.sh, everything worked fine.
>
> Again, thanks for helping me out.
>
> Mark Culp wrote:
>
usr/local/netscape/Cool:/usr/local/netscape:/usr/local/lib:/usr/local/sybase/SYBSsa8/lib:/mnt/data/qc/Develop/Obj/Linux/Lib:/mnt/data/qc/Products/Obj/Linux/Lib[color=darkred]
;31:*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.bz2=01;31:*.bz=01;31:*.tz=01;31:*.rpm=01;31:*.cpio=01;31:*.jpg=01;35:*.gif=01;35:*.bmp=01;35:*.xbm=01;35:*.xpm=01;35:*.png=01;35:*. tif=01;35:'[color=da
rkred]
sr/local/hsqldb/bin:/usr/local/unixODBC/bin:/mnt/data/qc/Bin/Linux:/mnt/data/qc/Bin:/mnt/data/qc/Develop/Obj/Linux/Bin:/mnt/data/qc/Products/Obj/Linux/Bin:/home/wlw/bin[color=darkred]
BC/lib::/usr/local/netscape/Cool:/usr/local/netscape:/usr/local/lib:/usr/local/sybase/SYBSsa8/lib:/mnt/data/qc/Develop/Obj/Linux/Lib:/mnt/data/qc/Products/Obj/Linux/Lib[color=darkred]
;31:*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.bz2=01;31:*.bz=01;31:*.tz=01;31:*.rpm=01;31:*.cpio=01;31:*.jpg=01;35:*.gif=01;35:*.bmp=01;35:*.xbm=01;35:*.xpm=01;35:*.png=01;35:*. tif=01;35:'[color=da
rkred]
sr/local/hsqldb/bin:/usr/local/unixODBC/bin:/mnt/data/qc/Bin/Linux:/mnt/data/qc/Bin:/mnt/data/qc/Develop/Obj/Linux/Bin:/mnt/data/qc/Products/Obj/Linux/Bin:/home/wlw/bin[color=darkred]
Sponsored Links





Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive | Programming forum archive

Copyright 2008 droptable.com