You are not logged in or registered. Please login or register to use the full functionality of this SYBASETEAM.COM Website...
Current time: 03-12-2010, 07:53 PM Hello There, Guest! (LoginRegister)
Tags: Net lib operation terminated,
Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Sybase Error : Net-lib operation terminated due to disconnect
12-15-2009, 05:35 PM
Post: #1
Sybase Error : Net-lib operation terminated due to disconnect
Net-lib operation terminated due to disconnect error in Sybase

Message Text

Number: (6) Severity (5) Layer (5), Origin (3) ct_results(): network packet layer: internal netlibrary error: Net-Library operation terminated due to disconnect.
Note:This error message occurs only with UNIX versions of Client-Library.

Possible Cause

This error is raised by the network services layer when a client disconnects abnormally. This can happen when:
• The server refuses a connection because it would exceed the maximum number of user connections that the server is configured for.
• A problem in the network causes connections to be dropped.
• The client has been killed.

Action

To resolve this problem, take the following actions, as appropriate:

• To see if you have exceeded the configured server value for the maximum number of user connections, log into the server with
isql and issue this command:
1> sp_configure ‘user connections’
2> go
The “run value” is the value of the maximum number of users parameter. Some of the connections are used for housekeeping tasks, so the number of connections your application may open is less than the maximum number of users allowed.
See the System Administration Guide for an explanation of the number of user connections parameter.
Then, issue sp_who to see how many connections have already been established. The sp_who output may show a lower number of connections than existed when the error occurred. You may need to monitor the output continuously while the application runs to get an accurate picture.
If you need more connections than the server allows, ask your database administrator to raise the value of the number of maximum connections parameter.

• Check your network for lost packets. You may want to use a “sniffer” or equivalent tool to do this.
• On UNIX platforms, check the value of the tcp ip abort interval. If your client application is waiting for the server to return results from a large or time-consuming query, the operating system may disconnect the client.
• Consider disabling tcp no delay.
• Check the operating system parameter for the number of file descriptors for both the client and server machines. On most UNIX machines, you can get this value by issuing the limit or ulimit -a command. If you need to open more connections than the number of file descriptors allowed, ask the UNIX system administrator to set this parameter to a higher value.
Find all posts by this user
Quote this message in a reply

Post Reply 


Possibly Related Threads...
Thread: Author Replies: Views: Last Post
  CTLIB: ct_send_data() may report error Cannot perform more than one read Kishor 0 72 12-05-2009 12:13 AM
Last Post: Kishor
  Sybase Open Client DB-Library Error Messages albert 0 96 04-16-2009 03:28 AM
Last Post: albert

Forum Jump: