Coates
asked on
Timeout Error!
Im am accessing a Sybase system 10 database using Visual Basic and ODBC. There are a number of clients in operation.
When performing an Update to the database, the client occasionally times-out and the following message is returned from ODBC.
S1T00:[INTERSOLV][ODBC SQL SERVER DRIVER][SQL SERVER]ct_results():user api layer: internal Client Library error:Read from the server has timed out."
This only happens when there are a lot of people using the system. When a single person is accesing the database, it all works fine.
Could the server be causing this problem?
When performing an Update to the database, the client occasionally times-out and the following message is returned from ODBC.
S1T00:[INTERSOLV][ODBC SQL SERVER DRIVER][SQL SERVER]ct_results():user api layer: internal Client Library error:Read from the server has timed out."
This only happens when there are a lot of people using the system. When a single person is accesing the database, it all works fine.
Could the server be causing this problem?
On which OS your Sybase is running ?? Solaris ? SunOS ?? HP/UX ?? NT ??
ASKER
It is running on a Solaris Server.
I am writing a lot of Long data (TEXT etc).
Could this cause the problem?
I am writing a lot of Long data (TEXT etc).
Could this cause the problem?
I would suggest you to run the 2 following commands as root:
ndd -set /dev/tcp tcp_old_urp_interpretation
ndd -set /dev/tcp tcp_keepalive_interval 10000
and add it to your /etc/inetinit so if you reboot your system
it will remain set. This will set your keep alive timer long enough at the network level so your packets doesn't get discarded by the system.
ndd -set /dev/tcp tcp_old_urp_interpretation
ndd -set /dev/tcp tcp_keepalive_interval 10000
and add it to your /etc/inetinit so if you reboot your system
it will remain set. This will set your keep alive timer long enough at the network level so your packets doesn't get discarded by the system.
Have you checked the max number of user connections allowed? Maybe that or # of open databases. You could be hitting up against one of these. Check em with sp_configure
just a guess
just a guess
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
inform me what all options are sent with just sp_configure command.
ASKER
Ive already sorted this out...I was opening far too many connections and recordsets without closing them on my client, coupled with sending large amounts of text data. This made the affair very slow, but ive fixed it now, thanks.
ASKER