"Out of locks" not shown in errorlog
Posted on 2004-03-29
I'm working on Sybase 18.104.22.168 on HP-UX.
Now we've had this situation where, in an applicationlog an error 'Out of locks' is shown but when I look in the Sybase-errorlog I do not see this message...
In my understanding the errormessage, with severity 17, should be presented in the errorlog.
Can anyone think of a reason why it isn't?
Here's a few copies from the logs.
The names have changed to protect the innocent :) The message 'disconnection failed' is from an errorfunction in the application which disconnects all connections from that application. The application itself is a serverprocess.
First the applicationlog:
26/03/04 15:09:12: (cv_sqlprt.c:720) sql failed :select <columns> from <tablename>
26/03/04 15:09:12: Error: failed to process 13, <procedurename>
26/03/04 15:09:12: Disconnection failed: Server message:
number(5701) severity(10) state(2) line(1)
Changed database context to 'db_namel'.
number(1204) severity(17) state(2) line(1)
SQL Server has run out of LOCKS. Re-run your command when there are fewer active users, or contact a user with System Administrator (SA) role to reconfigure SQL Server with more LOCKS.
Client Library error:
severity(0) number(49) origin(1) layer(1)
ct_close(): user api layer: external error: This routine cannot be called because another command structure has results pending.
(cv_sbs.c:676) ct_close failed
Then the Sybase errorlog:
01:00000:00034:2004/03/26 15:08:11.97 kernel Cannot send, host process disconnected: 00002dac spid: 34
01:00000:00034:2004/03/26 15:08:11.97 server Error: 1608, Severity: 18, State: 3
01:00000:00034:2004/03/26 15:08:11.97 server A client process exited abnormally, or a network error was encountered. Unless other errors occurred, continue processing normally.
01:00000:00186:2004/03/26 15:09:27.59 kernel Cannot send, host process disconnected: 00002104 spid: 186
01:00000:00186:2004/03/26 15:09:27.59 server Error: 1608, Severity: 18, State: 3
01:00000:00186:2004/03/26 15:09:27.59 server A client process exited abnormally, or a network error was encountered. Unless other errors occurred, continue processing normally.
You can see at the times that the 1204 message is not in the errolog.