sekharrao
asked on
Adaptive Server 6.0.4 Connection Problems
Hi
I have a problem with my ASA6.0.4. The problem is like
I have installed the ASA Server in WinNT and the clients are with Win 2000.Wht happens is it connects to the server and the users can able to work,but it gets frequently disconnects from the server.I tried with the dbping and i am able to connect.If i try with the ODBC its not..Kindly advise me what coould be the reason.
I have a problem with my ASA6.0.4. The problem is like
I have installed the ASA Server in WinNT and the clients are with Win 2000.Wht happens is it connects to the server and the users can able to work,but it gets frequently disconnects from the server.I tried with the dbping and i am able to connect.If i try with the ODBC its not..Kindly advise me what coould be the reason.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I had a similar problem with sqlanywhere 5. I solved using 2 additional parameters in dbclient -x command line flag.
{dobroadcast=no;host=192.1 68.0.1}.
Ex: dbclient -x tcpip{dobroadcast=no;host= 192.168.0. 1} banco
Note brackets; host can be numeric address or server name.
Please note that there are other server flag controlling time issues:
-ti min Client idle time before shutdown:—default 240 minutes
-tl sec Default liveness timeout for clients in seconds—default is 120 seconds
Please control also the auto stop database flag in odbc driver (try setting it to no) and eventually another dbclient flag:
-ga Automatically shut down after last connection closed
{dobroadcast=no;host=192.1
Ex: dbclient -x tcpip{dobroadcast=no;host=
Note brackets; host can be numeric address or server name.
Please note that there are other server flag controlling time issues:
-ti min Client idle time before shutdown:—default 240 minutes
-tl sec Default liveness timeout for clients in seconds—default is 120 seconds
Please control also the auto stop database flag in odbc driver (try setting it to no) and eventually another dbclient flag:
-ga Automatically shut down after last connection closed
I had a similar problem with sqlanywhere 5. I solved using 2 additional parameters in dbclient -x command line flag.
{dobroadcast=no;host=192.1 68.0.1}.
Ex: dbclient -x tcpip{dobroadcast=no;host= 192.168.0. 1} banco
Note brackets; host can be numeric address or server name.
Please note that there are other server flag controlling time issues:
-ti min Client idle time before shutdown:—default 240 minutes
-tl sec Default liveness timeout for clients in seconds—default is 120 seconds
Please control also the auto stop database flag in odbc driver (try setting it to no) and eventually another dbclient flag:
-ga Automatically shut down after last connection closed
{dobroadcast=no;host=192.1
Ex: dbclient -x tcpip{dobroadcast=no;host=
Note brackets; host can be numeric address or server name.
Please note that there are other server flag controlling time issues:
-ti min Client idle time before shutdown:—default 240 minutes
-tl sec Default liveness timeout for clients in seconds—default is 120 seconds
Please control also the auto stop database flag in odbc driver (try setting it to no) and eventually another dbclient flag:
-ga Automatically shut down after last connection closed
{dobroadcast=no;host=192.1
Ex: dbclient -x tcpip{dobroadcast=no;host=
Note brackets; host can be numeric address or server name.
Please note that there are other server flag controlling time issues:
-ti min Client idle time before shutdown:—default 240 minutes
-tl sec Default liveness timeout for clients in seconds—default is 120 seconds
Please control also the auto stop database flag in odbc driver (try setting it to no) and eventually another dbclient flag:
-ga Automatically shut down after last connection closed