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.

ASE Database Locking

4 posts in Appeon (partner product) Last posting was on 2005-08-08 11:59:24.0Z
Chuck Kahn Posted on 2005-08-04 17:56:16.0Z
From: "Chuck Kahn" <chuck.kahn@lmco.com>
Newsgroups: sybase.public.appeon
Subject: ASE Database Locking
Lines: 20
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-RFC2646: Format=Flowed; Original
X-Original-NNTP-Posting-Host: edge1a.lmco.com
Message-ID: <42f256bc$1@forums-2-dub>
X-Original-Trace: 4 Aug 2005 10:56:12 -0700, edge1a.lmco.com
X-Original-NNTP-Posting-Host: forums-2-dub.sybase.com
X-Original-Trace: 4 Aug 2005 10:56:13 -0700, forums-2-dub.sybase.com
NNTP-Posting-Host: forums-master.sybase.com
X-Original-NNTP-Posting-Host: forums-master.sybase.com
Date: 4 Aug 2005 10:56:16 -0700
X-Trace: forums-1-dub 1123178176 10.22.108.75 (4 Aug 2005 10:56:16 -0700)
X-Original-Trace: 4 Aug 2005 10:56:16 -0700, forums-master.sybase.com
X-Authenticated-User: ngsysop
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.appeon:1021
Article PK: 12808

We have had a client / server application that has been running for about 8
years now. Now that we have converted it to Appeon, we are seeing that
within our Sybase ASE 12.5.3 database, tables are being locked and for the
most part do not unlock for about 5 minutes (on average). At the time they
unlock, we receive a database error within the application. We have checked
our transactions to verify if we Begin a Transaction, we always Commit or
Rollback and End the Transaction.

We looked at our current locking scheme and it is configured for "ALL Pages"

1) Is this issue possibly due to the Sybase JDBC driver?

2) Do you recommend using row level locking vs. All Page locking on all
tables to fix this issue?

Thanks

Chuck


Julie Jiang Posted on 2005-08-05 10:07:24.0Z
From: "Julie Jiang" <julie.jiang@appeon.net>
Newsgroups: sybase.public.appeon
References: <42f256bc$1@forums-2-dub>
Subject: Re: ASE Database Locking
Lines: 101
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01D0_01C599E8.72227390"
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
NNTP-Posting-Host: 210.21.221.178
X-Original-NNTP-Posting-Host: 210.21.221.178
Message-ID: <42f33a5c$1@forums-1-dub>
Date: 5 Aug 2005 03:07:24 -0700
X-Trace: forums-1-dub 1123236444 210.21.221.178 (5 Aug 2005 03:07:24 -0700)
X-Original-Trace: 5 Aug 2005 03:07:24 -0700, 210.21.221.178
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.appeon:1028
Article PK: 21004

We are studying the problem.  At the same time, please contact your technical support so the issue can be handled more efficiently. 
 
Please let me know what is the database error that appears at the "unlock" time?
 
Regards,
Julie
"Chuck Kahn" <chuck.kahn@lmco.com> wrote in message news:42f256bc$1@forums-2-dub...
We have had a client / server application that has been running for about 8
years now.  Now that we have converted it to Appeon, we are seeing that
within our Sybase ASE 12.5.3 database, tables are being locked and for the
most part do not unlock for about 5 minutes (on average).  At the time they
unlock, we receive a database error within the application.  We have checked
our transactions to verify if we Begin a Transaction, we always Commit or
Rollback and End the Transaction.

We looked at our current locking scheme and it is configured for "ALL Pages"

1) Is this issue possibly due to the Sybase JDBC driver?

2) Do you recommend using row level locking vs. All Page locking on all
tables to fix this issue?

Thanks

Chuck


Chuck Kahn Posted on 2005-08-05 14:39:25.0Z
From: "Chuck Kahn" <chuck.kahn@lmco.com>
Newsgroups: sybase.public.appeon
References: <42f256bc$1@forums-2-dub> <42f33a5c$1@forums-1-dub>
Subject: Re: ASE Database Locking
Lines: 163
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_000A_01C59999.2D43EF00"
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Original-NNTP-Posting-Host: edge1a.lmco.com
Message-ID: <42f37a19$1@forums-2-dub>
X-Original-Trace: 5 Aug 2005 07:39:21 -0700, edge1a.lmco.com
X-Original-NNTP-Posting-Host: forums-2-dub.sybase.com
X-Original-Trace: 5 Aug 2005 07:39:24 -0700, forums-2-dub.sybase.com
NNTP-Posting-Host: forums-master.sybase.com
X-Original-NNTP-Posting-Host: forums-master.sybase.com
Date: 5 Aug 2005 07:39:25 -0700
X-Trace: forums-1-dub 1123252765 10.22.108.75 (5 Aug 2005 07:39:25 -0700)
X-Original-Trace: 5 Aug 2005 07:39:25 -0700, forums-master.sybase.com
X-Authenticated-User: ngsysop
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.appeon:1030
Article PK: 21008

After about 5 minutes, a dialog box appears indicating:
 
A database error has occurred.
 
Database error code: -1
 
Database error Message:
Failed to update data to the server
 
 
We changed one of the tables that we had issues with that was always locking to Row Locking and everything appears to be working properly now.  We may just change all of our tables to Row Locking to see if this totally fixes the issue.  However, I will contact out Tech Support with this information on Monday morning. 
 
Thanks
 
Chuck
"Julie Jiang" <julie.jiang@appeon.net> wrote in message news:42f33a5c$1@forums-1-dub...
We are studying the problem.  At the same time, please contact your technical support so the issue can be handled more efficiently. 
 
Please let me know what is the database error that appears at the "unlock" time?
 
Regards,
Julie
"Chuck Kahn" <chuck.kahn@lmco.com> wrote in message news:42f256bc$1@forums-2-dub...
We have had a client / server application that has been running for about 8
years now.  Now that we have converted it to Appeon, we are seeing that
within our Sybase ASE 12.5.3 database, tables are being locked and for the
most part do not unlock for about 5 minutes (on average).  At the time they
unlock, we receive a database error within the application.  We have checked
our transactions to verify if we Begin a Transaction, we always Commit or
Rollback and End the Transaction.

We looked at our current locking scheme and it is configured for "ALL Pages"

1) Is this issue possibly due to the Sybase JDBC driver?

2) Do you recommend using row level locking vs. All Page locking on all
tables to fix this issue?

Thanks

Chuck


Julie Jiang Posted on 2005-08-08 11:59:24.0Z
From: "Julie Jiang" <julie.jiang@appeon.net>
Newsgroups: sybase.public.appeon
Organization: 218.17.71.48
References: <42f256bc$1@forums-2-dub> <42f33a5c$1@forums-1-dub> <42f37a19$1@forums-2-dub>
X-Newsreader: AspNNTP 1.50 (Takeshi Eto)
Subject: Re: ASE Database Locking
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: web110.discountasp.net
X-Original-NNTP-Posting-Host: web110.discountasp.net
Message-ID: <42f7491c$1@forums-1-dub>
Date: 8 Aug 2005 04:59:24 -0700
X-Trace: forums-1-dub 1123502364 64.79.161.40 (8 Aug 2005 04:59:24 -0700)
X-Original-Trace: 8 Aug 2005 04:59:24 -0700, web110.discountasp.net
Lines: 90
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.appeon:1044
Article PK: 21015

Hi Chuck,

First, I suggest you set the log mode in AEM to debug, and study the jaguar.log
at %JAGUAR%\bin and log files at %JAGUAR%\bin\appeonlog for better clue.

You can do the following test for checking whether the problem is caused by
JDBC:
1. Set an ODBC data source for the application
2. Run the application in PowerBuilder with the ODBC connection, checking
whether any data locking occurs or not.
3. Configure a JDBC-ODBC bridge cache for connecting to the ODBC data source.
4. Deploy and run the application on the Web with the JDBC-ODBC bridge cache,
checking whether any data locking occurs or not.

As for the setting about "All Pages" or "Row Locking", "Row Locking" should
reduce the chances of database locks since it only locks the relevant row, so it
is worthwhile for changing the setting to "Row Locking" in your case. Actually,
Appeon engineers usually use the default "All Pages" and do not have much
issues.

Because of the inherent features with Web architecture, the chances of getting
database lock is indeed increased compared with in client/server architecture.
There is an important tip for reducing locks on the Web: commit database
operations more quickly so a transaction does not take too long time from begin
to commit (we call this "long transaction"). Such long transactions consume
database resources and greatly increase the chances of lock. Instead, please
place the long transactions in server NVO or database procedure for execution or
break a long transaction into small ones.

Hope your technical support can study the issue closely and resolve the issue
for you.



On 5 Aug 2005 07:39:25 -0700,
in sybase.public.appeon

Chuck Kahn <chuck.kahn@lmco.com> wrote:
>After about 5 minutes, a dialog box appears indicating:
>
>A database error has occurred.
>
>Database error code: -1
>
>Database error Message:
>Failed to update data to the server
>
>
>We changed one of the tables that we had issues with that was always locking to

Row Locking and everything appears to be working properly now. We may just
change all of our tables to Row Locking to see if this totally fixes the issue.
However, I will contact out Tech Support with this information on Monday
morning.
>
>Thanks
>
>Chuck
> "Julie Jiang" <julie.jiang@appeon.net> wrote in message
news:42f33a5c$1@forums-1-dub...
> We are studying the problem. At the same time, please contact your technical
support so the issue can be handled more efficiently.
>
> Please let me know what is the database error that appears at the "unlock"
time?
>
> Regards,
> Julie
> "Chuck Kahn" <chuck.kahn@lmco.com> wrote in message
news:42f256bc$1@forums-2-dub...
> We have had a client / server application that has been running for about 8
> years now. Now that we have converted it to Appeon, we are seeing that
> within our Sybase ASE 12.5.3 database, tables are being locked and for the
> most part do not unlock for about 5 minutes (on average). At the time they
> unlock, we receive a database error within the application. We have
checked
> our transactions to verify if we Begin a Transaction, we always Commit or
> Rollback and End the Transaction.
>
> We looked at our current locking scheme and it is configured for "ALL
Pages"
>
> 1) Is this issue possibly due to the Sybase JDBC driver?
>
> 2) Do you recommend using row level locking vs. All Page locking on all
> tables to fix this issue?
>
> Thanks
>
> Chuck
>
>