Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Lello, Nick — — source: Usenet: comp.databases.informix
I'm looking for any ideas here as we seem to be getting the usual
round-around from both Informix and Sun...
We have an multi-database installation of IDS 10.0.UC4 on Solaris 9 (Sun
fire v480) which we are replacing with a reloaded engine IDS 11.10.FC2
on Solaris 10 (Sun fire v490).
The Solaris 10 + IDS 11 system runs really well (50%+ speed improvement)
until after a couple of days we start seeing:-
05:49:39 listener-thread: err = -25575: oserr = 12: errstr = :
Network driver cannot allocate the call structure. System error = 12.
The operating system has been configured in accordance with the Machine
Notes for the IDS 11.10.FC2 distribution - curiously there is no mention
of tuning the TCP stack through ndd.
Unfortunately the IBM (Informix) response has been a flat 'its an os
error - speak to Sun' which is correct, but they wont help with any
clues on what the call that is failing possibly is.... Sun are asking
for source code and/or a truss of the failing process.
I have tried setting the following prior to IDS startup:-
ndd -set /dev/tcp tcp_time_wait_interval 15000
ndd -set /dev/tcp tcp_conn_req_max_q 4096
ndd -set /dev/tcp tcp_conn_req_max_q0 16384
ndd -set /dev/tcp tcp_max_buf 655350
ndd -set /dev/tcp tcp_cwnd_max 655350
Following my gut instinct for dealing with networking issues that
*appear* to be with the queue depth
However, I'd love to hear from someone who has any solid ideas or
experience with this version mix....
Regards,
Nick
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.