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.

unwanted setting of transaction lock levels

2 posts in ,  Windows NT General Discussion Last posting was on 2001-01-05 02:11:08.0Z
John Beatty Posted on 2001-01-04 19:09:55.0Z
From: "John Beatty" <jbeatty@lcb.state.nv.us>
Subject: unwanted setting of transaction lock levels
Date: Thu, 4 Jan 2001 11:09:55 -0800
Lines: 18
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.3018.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300
Message-ID: <862s5QodAHA.85@forums.sybase.com>
Newsgroups: powersoft.public.powerbuilder.database,powersoft.public.powerbuilder.ole-ocx-activex,sybase.public.sqlserver.general,sybase.public.sqlserver.nt
NNTP-Posting-Host: mail.lcb.state.nv.us 207.12.85.2
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub powersoft.public.powerbuilder.database:2449 powersoft.public.powerbuilder.ole-ocx-activex:432 sybase.public.sqlserver.general:153 sybase.public.sqlserver.nt:136
Article PK: 1103508

Hi-

I'm not sure who exactly is generating the following statements, but these
are being sent to SQL from a PowerBuilder application using OLEDB:

IF @@TRANCOUNT > 0 COMMIT TRAN
SET TRANSACTION ISOLATION LEVEL READ COMMITTED
SET TRANSACTION ISOLATION LEVEL SERIALIZABLE

These statements often follow ad hoc SQL SELECT statements , leaving the
current connection with a lock state of serializable.

Has any one else experienced this? If so, how do you supress those
statements? Especially setting the lock state to serializable.

Thanks.


Jim Egan Posted on 2001-01-05 02:11:08.0Z
From: Jim Egan <dbaguru@eganomics.com>
Subject: Re: unwanted setting of transaction lock levels
Date: Thu, 4 Jan 2001 20:11:08 -0600
Message-ID: <MPG.14bee932fca09e7f98affc@forums.sybase.com>
References: <862s5QodAHA.85@forums.sybase.com>
Reply-To: eganjp@compuserve.com
X-Newsreader: MicroPlanet Gravity v2.30
Newsgroups: powersoft.public.powerbuilder.database,powersoft.public.powerbuilder.ole-ocx-activex,sybase.public.sqlserver.general,sybase.public.sqlserver.nt
Lines: 16
NNTP-Posting-Host: 148.75.117.86
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub powersoft.public.powerbuilder.database:2448 powersoft.public.powerbuilder.ole-ocx-activex:431 sybase.public.sqlserver.general:152 sybase.public.sqlserver.nt:135
Article PK: 1103470

That's odd. I haven't seen or experienced like that in PowerBuilder using ODBC or Open
Client. I know that ODBC will set the isolation level to zero in SQL Anywhere. I don't
use OLEDB.

You might want to try running two different traces. First run a PowerBuilder trace by
adding the work TRACE prior to the name of the dbms in SQLCA.DBMS. This one is relatively
easy to read.

Next, run a trace from ODBC/OLEDB.

If you don't see it happening in either place then it could be a low level command coming
from ODBC/OLEDB but I doubt that is happening.
--
Jim Egan [TeamSybase]