Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Sybase Multiuser Issues , handling Dead locks and avoinding errors in SP.

2 posts in Windows NT Last posting was on 1998-04-24 14:10:48.0Z
cgvak Posted on 1998-04-17 10:36:21.0Z
From: "cgvak" <cgvak@giasmd01.vsnl.net.in>
Subject: Sybase Multiuser Issues , handling Dead locks and avoinding errors in SP.
Message-ID: <01bd69f6$37c3ebe0$d02136ca@cgvak>
X-Newsreader: Microsoft Internet News 4.70.1155
Newsgroups: sybase.public.sqlserver.nt
Date: Fri, 17 Apr 1998 06:36:21 -0400
Lines: 46
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.sqlserver.nt:5068
Article PK: 1092430

We are into developing business application software with a large volume
of data in a
multiuser environment. We are using Powerbuilder 5.0 with sybase system 11
running
on windows NT 4.0. We are facing problems in the following areas :

1. Multiuser issues & Dead locks
In our database design we have a table which is accessed during all the
time by multiple users. And the data has to be reflected to everyone. When
one user is trying to access that table from the frontend. And if that
table is already in use by another user.
The forthcoming requests for the tables are pending. And the enduser gets a
feeling as if
the application is hanged. We are not able to avoid this problem. And we
have crossed the stage of Horizontal partioning of the table.
So anyone who have already come across this type of error can suggest a
way out of this problem.

2. Database error 49
We often come across this error from the backend.This error says CT_SEND
anothercommand structure is pending. So it is unable to execute the current
request.
This happens when the same procedure is execute more than one time from the
trigger
or from the front end scripting thru function.
IF anyone can tell us how to avoid this error.

3. We are also coming across a lot of Dead locks on the common tables and
the sybase engine is supposed to terminate it automatically.But
unfortunately this doesn't
happens and the user who is responsible for the dead lock has to come out
of the application / disconnect from the database for end the DEAD lock. So
if anyone can
suggest what should be done to avoid this error or is there any
configuration to be
done at the back end to avoid this.


It would be very helpful if anyone can respond for these errors. Thanks in
advance.

With regards,

Rathan


David Pascuzzi Posted on 1998-04-24 14:10:48.0Z
Message-ID: <35409D68.8CFCB67F@concentric.net>
Date: Fri, 24 Apr 1998 08:10:48 -0600
From: David Pascuzzi <pascuzzi@concentric.net>
X-Mailer: Mozilla 4.04 [en] (WinNT; I)
MIME-Version: 1.0
To: cgvak <cgvak@giasmd01.vsnl.net.in>
Subject: Re: Sybase Multiuser Issues , handling Dead locks and avoinding errors in SP.
References: <01bd69f6$37c3ebe0$d02136ca@cgvak>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.sqlserver.nt
Lines: 76
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.sqlserver.nt:5054
Article PK: 1092417

1) Multi Users and deadlocks: What you have here is not a server deadlock. Instead
it is a lock that is stoping the other user from accessing the data. Does your
application begin transactions and holds them while waiting for user input? How do
yo have autocommit configured True or False? Do you have multiple connections open
to the database? if so yo might have an application deadlock? Also depending on the
indexes on the table and the query you might be generating table locks everytime
which would make it look like your application is hanging

2) If you return multiple result sets or have print statements in triggers and
procs, you must make sure that you loop through your results to clear the command
buffers before going on to the next SQL Statement. If each time you call the
procedure it selects or prints data you can get this problem.

3) See One, If you are having server side deadlocks Sybase will detect them and kick
out one users. ( If you have the deadlock checking interval set to high it might
take a while)

cgvak wrote:

> We are into developing business application software with a large volume
> of data in a
> multiuser environment. We are using Powerbuilder 5.0 with sybase system 11
> running
> on windows NT 4.0. We are facing problems in the following areas :
>
> 1. Multiuser issues & Dead locks
> In our database design we have a table which is accessed during all the
> time by multiple users. And the data has to be reflected to everyone. When
> one user is trying to access that table from the frontend. And if that
> table is already in use by another user.
> The forthcoming requests for the tables are pending. And the enduser gets a
> feeling as if
> the application is hanged. We are not able to avoid this problem. And we
> have crossed the stage of Horizontal partioning of the table.
> So anyone who have already come across this type of error can suggest a
> way out of this problem.
>
> 2. Database error 49
> We often come across this error from the backend.This error says CT_SEND
> anothercommand structure is pending. So it is unable to execute the current
> request.
> This happens when the same procedure is execute more than one time from the
> trigger
> or from the front end scripting thru function.
> IF anyone can tell us how to avoid this error.
>
> 3. We are also coming across a lot of Dead locks on the common tables and
> the sybase engine is supposed to terminate it automatically.But
> unfortunately this doesn't
> happens and the user who is responsible for the dead lock has to come out
> of the application / disconnect from the database for end the DEAD lock. So
> if anyone can
> suggest what should be done to avoid this error or is there any
> configuration to be
> done at the back end to avoid this.
>
>
> It would be very helpful if anyone can respond for these errors. Thanks in
> advance.
>
> With regards,
>
> Rathan