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.

Oracle OCI 7 ; cursors not closing

17 posts in General Discussion (old) Last posting was on 2000-03-28 17:09:23.0Z
Glenn Santa Cruz Posted on 2000-03-28 00:40:57.0Z
Newsgroups: sybase.public.easerver
Date: Mon, 27 Mar 2000 18:40:57 -0600
From: Glenn Santa Cruz <spam?no.glenn_santacruz@dailyaccess.com>
Organization: Daily Access Concepts
X-Mailer: Mozilla 4.7 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Oracle OCI 7 ; cursors not closing
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 17
NNTP-Posting-Host: 12.6.74.30
Message-ID: <347_38DFFF99.E3BD0905@dailyaccess.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:25557
Article PK: 155630

Jaguar 3.01, build 30033
PB 7.01, build 7021
OCI 7.x cache
ociw32.dll version 8.0.4.0.0

I have a standard, transactional, poolable PB component that performs
both inserts and updates to an Oracle 7.3.4 database; transactions are
definitely being committed or rolled back as designed. However, cursors
are not being closed (verified via V$OPEN_CURSOR) at transaction
boundaries.

Anyone know of configurable settings (for Jaguar) to close open cursors
on a commit or rollback? Note that this behavior has not been seen when
using traditional 2-tier PB applications, presumably because they use a
different driver for connection.

Major TIA.

Glenn


Carson Hager[Team Sybase] Posted on 2000-03-28 02:15:36.0Z
Newsgroups: sybase.public.easerver
From: chager@dyn-data.com (Carson Hager[Team Sybase])
Subject: Re: Oracle OCI 7 ; cursors not closing
Date: Tue, 28 Mar 2000 02:15:36 GMT
Organization: Dynamic Data Solutions, Inc.
X-Newsreader: Forte Free Agent 1.21/32.243
Lines: 42
NNTP-Posting-Host: charon.lifescape.com 63.86.26.130
Message-ID: <347_38e015b2.94411746@forums.sybase.com>
References: <347_38DFFF99.E3BD0905@dailyaccess.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:25556
Article PK: 155633

They should definitely be closed. Is this using embedded SQL or
datastorers?


Carson

___________________________________________________________

Carson Hager
Team Sybase
Dynamic Data Solutions, Inc.
Enterprise Application Studio 3.0 Consulting and Training
http://www.dyn-data.com

DDS is now hiring EAServer consultants
to support its exploding EAServer business!
Please submit your resume to
hr@dyn-data.com!


On Mon, 27 Mar 2000 18:40:57 -0600, Glenn Santa Cruz

<spam?no.glenn_santacruz@dailyaccess.com> wrote:

>Jaguar 3.01, build 30033
>PB 7.01, build 7021
>OCI 7.x cache
>ociw32.dll version 8.0.4.0.0
>
>I have a standard, transactional, poolable PB component that performs
>both inserts and updates to an Oracle 7.3.4 database; transactions are
>definitely being committed or rolled back as designed. However, cursors
>are not being closed (verified via V$OPEN_CURSOR) at transaction
>boundaries.
>
>Anyone know of configurable settings (for Jaguar) to close open cursors
>on a commit or rollback? Note that this behavior has not been seen when
>using traditional 2-tier PB applications, presumably because they use a
>different driver for connection.
>
>Major TIA.
>
>Glenn

___________________________________________________________

Carson Hager
Team Sybase
Dynamic Data Solutions, Inc.
Enterprise Application Studio 3.0 Consulting and Training

DDS Enterprise Application Framework
Available Now as Open Source!
http://www.dyn-data.com


Glenn Santa Cruz Posted on 2000-03-28 01:16:48.0Z
Newsgroups: sybase.public.easerver
Date: Mon, 27 Mar 2000 19:16:48 -0600
From: Glenn Santa Cruz <spam?no.glenn_santacruz@dailyaccess.com>
Organization: Daily Access Concepts
X-Mailer: Mozilla 4.7 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: Oracle OCI 7 ; cursors not closing
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 52
NNTP-Posting-Host: 12.6.74.30
Message-ID: <347_38E00800.D6C10E4F@dailyaccess.com>
References: <347_38DFFF99.E3BD0905@dailyaccess.com> <347_38e015b2.94411746@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:25554
Article PK: 155629

I've tried both ways to no avail. Out on a limb here, but do you know
offhand if there may be a registry entry that the OCI dll uses to
determine whether or not to close cursors? I'm about to search technet
for advice; if I find anything, I'll be sure to post it.

Glenn

"Carson Hager[Team Sybase]" wrote:
>
> They should definitely be closed. Is this using embedded SQL or
> datastorers?
>
> Carson
>
> ___________________________________________________________
>
> Carson Hager
> Team Sybase
> Dynamic Data Solutions, Inc.
> Enterprise Application Studio 3.0 Consulting and Training
> http://www.dyn-data.com
>
> DDS is now hiring EAServer consultants
> to support its exploding EAServer business!
> Please submit your resume to
> hr@dyn-data.com!
>
> On Mon, 27 Mar 2000 18:40:57 -0600, Glenn Santa Cruz
> <spam?no.glenn_santacruz@dailyaccess.com> wrote:
>
> >Jaguar 3.01, build 30033
> >PB 7.01, build 7021
> >OCI 7.x cache
> >ociw32.dll version 8.0.4.0.0
> >
> >I have a standard, transactional, poolable PB component that performs
> >both inserts and updates to an Oracle 7.3.4 database; transactions are
> >definitely being committed or rolled back as designed. However, cursors
> >are not being closed (verified via V$OPEN_CURSOR) at transaction
> >boundaries.
> >
> >Anyone know of configurable settings (for Jaguar) to close open cursors
> >on a commit or rollback? Note that this behavior has not been seen when
> >using traditional 2-tier PB applications, presumably because they use a
> >different driver for connection.
> >
> >Major TIA.
> >
> >Glenn
>
> ___________________________________________________________
>
> Carson Hager
> Team Sybase
> Dynamic Data Solutions, Inc.
> Enterprise Application Studio 3.0 Consulting and Training
>
> DDS Enterprise Application Framework
> Available Now as Open Source!
> http://www.dyn-data.com


Glenn Santa Cruz Posted on 2000-03-28 01:38:46.0Z
Newsgroups: sybase.public.easerver
Date: Mon, 27 Mar 2000 19:38:46 -0600
From: Glenn Santa Cruz <spam?no.glenn_santacruz@dailyaccess.com>
Organization: Daily Access Concepts
X-Mailer: Mozilla 4.7 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: Oracle OCI 7 ; cursors not closing
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 62
NNTP-Posting-Host: 12.6.74.30
Message-ID: <347_38E00D26.84438FE@dailyaccess.com>
References: <347_38DFFF99.E3BD0905@dailyaccess.com> <347_38e015b2.94411746@forums.sybase.com> <347_38E00800.D6C10E4F@dailyaccess.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:25546
Article PK: 155620

No luck on technet -- site's not responding. However, I *did* find an
OCI attribute that deals with my situation:
OCI_ATTR_CURSOR_COMMIT_BEHAVIOR ; I'm not planning on approaching this
from a C/C++ level, so it doesn't do me much good...

Glenn Santa Cruz wrote:
>
> I've tried both ways to no avail. Out on a limb here, but do you know
> offhand if there may be a registry entry that the OCI dll uses to
> determine whether or not to close cursors? I'm about to search technet
> for advice; if I find anything, I'll be sure to post it.
>
> Glenn
>
> "Carson Hager[Team Sybase]" wrote:
> >
> > They should definitely be closed. Is this using embedded SQL or
> > datastorers?
> >
> > Carson
> >
> > ___________________________________________________________
> >
> > Carson Hager
> > Team Sybase
> > Dynamic Data Solutions, Inc.
> > Enterprise Application Studio 3.0 Consulting and Training
> > http://www.dyn-data.com
> >
> > DDS is now hiring EAServer consultants
> > to support its exploding EAServer business!
> > Please submit your resume to
> > hr@dyn-data.com!
> >
> > On Mon, 27 Mar 2000 18:40:57 -0600, Glenn Santa Cruz
> > <spam?no.glenn_santacruz@dailyaccess.com> wrote:
> >
> > >Jaguar 3.01, build 30033
> > >PB 7.01, build 7021
> > >OCI 7.x cache
> > >ociw32.dll version 8.0.4.0.0
> > >
> > >I have a standard, transactional, poolable PB component that performs
> > >both inserts and updates to an Oracle 7.3.4 database; transactions are
> > >definitely being committed or rolled back as designed. However, cursors
> > >are not being closed (verified via V$OPEN_CURSOR) at transaction
> > >boundaries.
> > >
> > >Anyone know of configurable settings (for Jaguar) to close open cursors
> > >on a commit or rollback? Note that this behavior has not been seen when
> > >using traditional 2-tier PB applications, presumably because they use a
> > >different driver for connection.
> > >
> > >Major TIA.
> > >
> > >Glenn
> >
> > ___________________________________________________________
> >
> > Carson Hager
> > Team Sybase
> > Dynamic Data Solutions, Inc.
> > Enterprise Application Studio 3.0 Consulting and Training
> >
> > DDS Enterprise Application Framework
> > Available Now as Open Source!
> > http://www.dyn-data.com


Carson Hager[Team Sybase] Posted on 2000-03-28 02:45:41.0Z
Newsgroups: sybase.public.easerver
From: chager@dyn-data.com (Carson Hager[Team Sybase])
Subject: Re: Oracle OCI 7 ; cursors not closing
Date: Tue, 28 Mar 2000 02:45:41 GMT
Organization: Dynamic Data Solutions, Inc.
X-Newsreader: Forte Free Agent 1.21/32.243
Lines: 88
NNTP-Posting-Host: charon.lifescape.com 63.86.26.130
Message-ID: <347_38e01cbe.96216181@forums.sybase.com>
References: <347_38DFFF99.E3BD0905@dailyaccess.com> <347_38e015b2.94411746@forums.sybase.com> <347_38E00800.D6C10E4F@dailyaccess.com> <347_38E00D26.84438FE@dailyaccess.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:25545
Article PK: 155619

I wonder if that could be dictated through the DBParm parameter...

Jim?


Carson

___________________________________________________________

Carson Hager
Team Sybase
Dynamic Data Solutions, Inc.
Enterprise Application Studio 3.0 Consulting and Training
http://www.dyn-data.com

DDS is now hiring EAServer consultants
to support its exploding EAServer business!
Please submit your resume to
hr@dyn-data.com!


On Mon, 27 Mar 2000 19:38:46 -0600, Glenn Santa Cruz

<spam?no.glenn_santacruz@dailyaccess.com> wrote:

>No luck on technet -- site's not responding. However, I *did* find an
>OCI attribute that deals with my situation:
>OCI_ATTR_CURSOR_COMMIT_BEHAVIOR ; I'm not planning on approaching this
>from a C/C++ level, so it doesn't do me much good...
>
>Glenn Santa Cruz wrote:
>>
>> I've tried both ways to no avail. Out on a limb here, but do you know
>> offhand if there may be a registry entry that the OCI dll uses to
>> determine whether or not to close cursors? I'm about to search technet
>> for advice; if I find anything, I'll be sure to post it.
>>
>> Glenn
>>
>> "Carson Hager[Team Sybase]" wrote:
>> >
>> > They should definitely be closed. Is this using embedded SQL or
>> > datastorers?
>> >
>> > Carson
>> >
>> > ___________________________________________________________
>> >
>> > Carson Hager
>> > Team Sybase
>> > Dynamic Data Solutions, Inc.
>> > Enterprise Application Studio 3.0 Consulting and Training
>> > http://www.dyn-data.com
>> >
>> > DDS is now hiring EAServer consultants
>> > to support its exploding EAServer business!
>> > Please submit your resume to
>> > hr@dyn-data.com!
>> >
>> > On Mon, 27 Mar 2000 18:40:57 -0600, Glenn Santa Cruz
>> > <spam?no.glenn_santacruz@dailyaccess.com> wrote:
>> >
>> > >Jaguar 3.01, build 30033
>> > >PB 7.01, build 7021
>> > >OCI 7.x cache
>> > >ociw32.dll version 8.0.4.0.0
>> > >
>> > >I have a standard, transactional, poolable PB component that performs
>> > >both inserts and updates to an Oracle 7.3.4 database; transactions are
>> > >definitely being committed or rolled back as designed. However, cursors
>> > >are not being closed (verified via V$OPEN_CURSOR) at transaction
>> > >boundaries.
>> > >
>> > >Anyone know of configurable settings (for Jaguar) to close open cursors
>> > >on a commit or rollback? Note that this behavior has not been seen when
>> > >using traditional 2-tier PB applications, presumably because they use a
>> > >different driver for connection.
>> > >
>> > >Major TIA.
>> > >
>> > >Glenn
>> >
>> > ___________________________________________________________
>> >
>> > Carson Hager
>> > Team Sybase
>> > Dynamic Data Solutions, Inc.
>> > Enterprise Application Studio 3.0 Consulting and Training
>> >
>> > DDS Enterprise Application Framework
>> > Available Now as Open Source!
>> > http://www.dyn-data.com

___________________________________________________________

Carson Hager
Team Sybase
Dynamic Data Solutions, Inc.
Enterprise Application Studio 3.0 Consulting and Training

DDS Enterprise Application Framework
Available Now as Open Source!
http://www.dyn-data.com


Glenn Santa Cruz Posted on 2000-03-28 01:55:09.0Z
Newsgroups: sybase.public.easerver
Date: Mon, 27 Mar 2000 19:55:09 -0600
From: Glenn Santa Cruz <spam?no.glenn_santacruz@dailyaccess.com>
Organization: Daily Access Concepts
X-Mailer: Mozilla 4.7 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: Oracle OCI 7 ; cursors not closing
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 104
NNTP-Posting-Host: 12.6.74.30
Message-ID: <347_38E010FD.D2F8705F@dailyaccess.com>
References: <347_38DFFF99.E3BD0905@dailyaccess.com> <347_38e015b2.94411746@forums.sybase.com> <347_38E00800.D6C10E4F@dailyaccess.com> <347_38E00D26.84438FE@dailyaccess.com> <347_38e01cbe.96216181@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:25542
Article PK: 155614

I think I may have found it. Thanks Carson, for suggesting the DBParm
parameter. I started reading through the docs and found that SQLCache
does indeed have some control over open cursors. My dbParm was set for
SQLCache=8 (to help improve performance); removing the explicit setting
and using the default (SQLCache=0) seems to have fixed the problem, but
I now wonder if this is a bug?

Glenn

"Carson Hager[Team Sybase]" wrote:
>
> I wonder if that could be dictated through the DBParm parameter...
>
> Jim?
>
> Carson
>
> ___________________________________________________________
>
> Carson Hager
> Team Sybase
> Dynamic Data Solutions, Inc.
> Enterprise Application Studio 3.0 Consulting and Training
> http://www.dyn-data.com
>
> DDS is now hiring EAServer consultants
> to support its exploding EAServer business!
> Please submit your resume to
> hr@dyn-data.com!
>
> On Mon, 27 Mar 2000 19:38:46 -0600, Glenn Santa Cruz
> <spam?no.glenn_santacruz@dailyaccess.com> wrote:
>
> >No luck on technet -- site's not responding. However, I *did* find an
> >OCI attribute that deals with my situation:
> >OCI_ATTR_CURSOR_COMMIT_BEHAVIOR ; I'm not planning on approaching this
> >from a C/C++ level, so it doesn't do me much good...
> >
> >Glenn Santa Cruz wrote:
> >>
> >> I've tried both ways to no avail. Out on a limb here, but do you know
> >> offhand if there may be a registry entry that the OCI dll uses to
> >> determine whether or not to close cursors? I'm about to search technet
> >> for advice; if I find anything, I'll be sure to post it.
> >>
> >> Glenn
> >>
> >> "Carson Hager[Team Sybase]" wrote:
> >> >
> >> > They should definitely be closed. Is this using embedded SQL or
> >> > datastorers?
> >> >
> >> > Carson
> >> >
> >> > ___________________________________________________________
> >> >
> >> > Carson Hager
> >> > Team Sybase
> >> > Dynamic Data Solutions, Inc.
> >> > Enterprise Application Studio 3.0 Consulting and Training
> >> > http://www.dyn-data.com
> >> >
> >> > DDS is now hiring EAServer consultants
> >> > to support its exploding EAServer business!
> >> > Please submit your resume to
> >> > hr@dyn-data.com!
> >> >
> >> > On Mon, 27 Mar 2000 18:40:57 -0600, Glenn Santa Cruz
> >> > <spam?no.glenn_santacruz@dailyaccess.com> wrote:
> >> >
> >> > >Jaguar 3.01, build 30033
> >> > >PB 7.01, build 7021
> >> > >OCI 7.x cache
> >> > >ociw32.dll version 8.0.4.0.0
> >> > >
> >> > >I have a standard, transactional, poolable PB component that performs
> >> > >both inserts and updates to an Oracle 7.3.4 database; transactions are
> >> > >definitely being committed or rolled back as designed. However, cursors
> >> > >are not being closed (verified via V$OPEN_CURSOR) at transaction
> >> > >boundaries.
> >> > >
> >> > >Anyone know of configurable settings (for Jaguar) to close open cursors
> >> > >on a commit or rollback? Note that this behavior has not been seen when
> >> > >using traditional 2-tier PB applications, presumably because they use a
> >> > >different driver for connection.
> >> > >
> >> > >Major TIA.
> >> > >
> >> > >Glenn
> >> >
> >> > ___________________________________________________________
> >> >
> >> > Carson Hager
> >> > Team Sybase
> >> > Dynamic Data Solutions, Inc.
> >> > Enterprise Application Studio 3.0 Consulting and Training
> >> >
> >> > DDS Enterprise Application Framework
> >> > Available Now as Open Source!
> >> > http://www.dyn-data.com
>
> ___________________________________________________________
>
> Carson Hager
> Team Sybase
> Dynamic Data Solutions, Inc.
> Enterprise Application Studio 3.0 Consulting and Training
>
> DDS Enterprise Application Framework
> Available Now as Open Source!
> http://www.dyn-data.com


Carson Hager[Team Sybase] Posted on 2000-03-28 03:12:05.0Z
Newsgroups: sybase.public.easerver
From: chager@dyn-data.com (Carson Hager[Team Sybase])
Subject: Re: Oracle OCI 7 ; cursors not closing
Date: Tue, 28 Mar 2000 03:12:05 GMT
Organization: Dynamic Data Solutions, Inc.
X-Newsreader: Forte Free Agent 1.21/32.243
Lines: 131
NNTP-Posting-Host: charon.lifescape.com 63.86.26.130
Message-ID: <347_38e022d8.97777686@forums.sybase.com>
References: <347_38DFFF99.E3BD0905@dailyaccess.com> <347_38e015b2.94411746@forums.sybase.com> <347_38E00800.D6C10E4F@dailyaccess.com> <347_38E00D26.84438FE@dailyaccess.com> <347_38e01cbe.96216181@forums.sybase.com> <347_38E010FD.D2F8705F@dailyaccess.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:25535
Article PK: 155609

I would bet this is standard behavior to tell the DB connection
manager to keep them open until close.


Carson

___________________________________________________________

Carson Hager
Team Sybase
Dynamic Data Solutions, Inc.
Enterprise Application Studio 3.0 Consulting and Training
http://www.dyn-data.com

DDS is now hiring EAServer consultants
to support its exploding EAServer business!
Please submit your resume to
hr@dyn-data.com!


On Mon, 27 Mar 2000 19:55:09 -0600, Glenn Santa Cruz

<spam?no.glenn_santacruz@dailyaccess.com> wrote:

>I think I may have found it. Thanks Carson, for suggesting the DBParm
>parameter. I started reading through the docs and found that SQLCache
>does indeed have some control over open cursors. My dbParm was set for
>SQLCache=8 (to help improve performance); removing the explicit setting
>and using the default (SQLCache=0) seems to have fixed the problem, but
>I now wonder if this is a bug?
>
>Glenn
>
>"Carson Hager[Team Sybase]" wrote:
>>
>> I wonder if that could be dictated through the DBParm parameter...
>>
>> Jim?
>>
>> Carson
>>
>> ___________________________________________________________
>>
>> Carson Hager
>> Team Sybase
>> Dynamic Data Solutions, Inc.
>> Enterprise Application Studio 3.0 Consulting and Training
>> http://www.dyn-data.com
>>
>> DDS is now hiring EAServer consultants
>> to support its exploding EAServer business!
>> Please submit your resume to
>> hr@dyn-data.com!
>>
>> On Mon, 27 Mar 2000 19:38:46 -0600, Glenn Santa Cruz
>> <spam?no.glenn_santacruz@dailyaccess.com> wrote:
>>
>> >No luck on technet -- site's not responding. However, I *did* find an
>> >OCI attribute that deals with my situation:
>> >OCI_ATTR_CURSOR_COMMIT_BEHAVIOR ; I'm not planning on approaching this
>> >from a C/C++ level, so it doesn't do me much good...
>> >
>> >Glenn Santa Cruz wrote:
>> >>
>> >> I've tried both ways to no avail. Out on a limb here, but do you know
>> >> offhand if there may be a registry entry that the OCI dll uses to
>> >> determine whether or not to close cursors? I'm about to search technet
>> >> for advice; if I find anything, I'll be sure to post it.
>> >>
>> >> Glenn
>> >>
>> >> "Carson Hager[Team Sybase]" wrote:
>> >> >
>> >> > They should definitely be closed. Is this using embedded SQL or
>> >> > datastorers?
>> >> >
>> >> > Carson
>> >> >
>> >> > ___________________________________________________________
>> >> >
>> >> > Carson Hager
>> >> > Team Sybase
>> >> > Dynamic Data Solutions, Inc.
>> >> > Enterprise Application Studio 3.0 Consulting and Training
>> >> > http://www.dyn-data.com
>> >> >
>> >> > DDS is now hiring EAServer consultants
>> >> > to support its exploding EAServer business!
>> >> > Please submit your resume to
>> >> > hr@dyn-data.com!
>> >> >
>> >> > On Mon, 27 Mar 2000 18:40:57 -0600, Glenn Santa Cruz
>> >> > <spam?no.glenn_santacruz@dailyaccess.com> wrote:
>> >> >
>> >> > >Jaguar 3.01, build 30033
>> >> > >PB 7.01, build 7021
>> >> > >OCI 7.x cache
>> >> > >ociw32.dll version 8.0.4.0.0
>> >> > >
>> >> > >I have a standard, transactional, poolable PB component that performs
>> >> > >both inserts and updates to an Oracle 7.3.4 database; transactions are
>> >> > >definitely being committed or rolled back as designed. However, cursors
>> >> > >are not being closed (verified via V$OPEN_CURSOR) at transaction
>> >> > >boundaries.
>> >> > >
>> >> > >Anyone know of configurable settings (for Jaguar) to close open cursors
>> >> > >on a commit or rollback? Note that this behavior has not been seen when
>> >> > >using traditional 2-tier PB applications, presumably because they use a
>> >> > >different driver for connection.
>> >> > >
>> >> > >Major TIA.
>> >> > >
>> >> > >Glenn
>> >> >
>> >> > ___________________________________________________________
>> >> >
>> >> > Carson Hager
>> >> > Team Sybase
>> >> > Dynamic Data Solutions, Inc.
>> >> > Enterprise Application Studio 3.0 Consulting and Training
>> >> >
>> >> > DDS Enterprise Application Framework
>> >> > Available Now as Open Source!
>> >> > http://www.dyn-data.com
>>
>> ___________________________________________________________
>>
>> Carson Hager
>> Team Sybase
>> Dynamic Data Solutions, Inc.
>> Enterprise Application Studio 3.0 Consulting and Training
>>
>> DDS Enterprise Application Framework
>> Available Now as Open Source!
>> http://www.dyn-data.com

___________________________________________________________

Carson Hager
Team Sybase
Dynamic Data Solutions, Inc.
Enterprise Application Studio 3.0 Consulting and Training

DDS Enterprise Application Framework
Available Now as Open Source!
http://www.dyn-data.com


Jim O'Neil [Sybase] Posted on 2000-03-28 14:49:55.0Z
Newsgroups: sybase.public.easerver
Date: Tue, 28 Mar 2000 09:49:55 -0500
From: "Jim O'Neil [Sybase]" <joneil@sybase.com>
Organization: Sybase, Inc.
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: Oracle OCI 7 ; cursors not closing
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 174
NNTP-Posting-Host: joneil-nt.sybase.com 204.167.42.111
Message-ID: <347_38E0C692.D31DDA2@sybase.com>
References: <347_38DFFF99.E3BD0905@dailyaccess.com> <347_38e015b2.94411746@forums.sybase.com> <347_38E00800.D6C10E4F@dailyaccess.com> <347_38E00D26.84438FE@dailyaccess.com> <347_38e01cbe.96216181@forums.sybase.com> <347_38E010FD.D2F8705F@dailyaccess.com> <347_38e022d8.97777686@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:25490
Article PK: 155573

I'm leaning with Carson on this one - I"m not sure what the specific OCI API call is
to set this number of cursors, but based on your experiences, it appears that it is a
post-connection setting. Since Jaguar is actually making the physical connection,
the only DBParms that will 'work' are those that cause calls to the client layer to
be issued AFTER the physical connection (versus some DBParms that set up an
environment before the connection is made). Since you are using a connection cache,
the physical connection is NOT closed when PowerBuilder issues the DISCONNECT, so it
would make sense that the cursors remain open.

You mentioned using OCI 7 - are you using this with a 7.x client? If so, then the
SQLCache parameter will have an effect on performance, so you might try setting
SQLCache=8 (or whatever) on the CONNECT statement and then set SQLCache=0 right
before the disconnect. I'm not certain that would work - depends on whether SQLCache
is a 'hot' DBParm (some only get acknowledged once on the CONNECT). If you are using
an 8.x client then actually SQLCache is not really buying you anything since the OCI
8 client does it's own caching that really obviates the need for PowerBuilder to do
so. (OK, one more caveat - I'm not 100% sure that's the case if you are going
through OCI 8 with the 7.x required support files).

Jim O'Neil
Sybase Technical Support

"Carson Hager[Team Sybase]" wrote:

> I would bet this is standard behavior to tell the DB connection
> manager to keep them open until close.
>
> Carson
>
> ___________________________________________________________
>
> Carson Hager
> Team Sybase
> Dynamic Data Solutions, Inc.
> Enterprise Application Studio 3.0 Consulting and Training
> http://www.dyn-data.com
>
> DDS is now hiring EAServer consultants
> to support its exploding EAServer business!
> Please submit your resume to
> hr@dyn-data.com!
>
> On Mon, 27 Mar 2000 19:55:09 -0600, Glenn Santa Cruz
> <spam?no.glenn_santacruz@dailyaccess.com> wrote:
>
> >I think I may have found it. Thanks Carson, for suggesting the DBParm
> >parameter. I started reading through the docs and found that SQLCache
> >does indeed have some control over open cursors. My dbParm was set for
> >SQLCache=8 (to help improve performance); removing the explicit setting
> >and using the default (SQLCache=0) seems to have fixed the problem, but
> >I now wonder if this is a bug?
> >
> >Glenn
> >
> >"Carson Hager[Team Sybase]" wrote:
> >>
> >> I wonder if that could be dictated through the DBParm parameter...
> >>
> >> Jim?
> >>
> >> Carson
> >>
> >> ___________________________________________________________
> >>
> >> Carson Hager
> >> Team Sybase
> >> Dynamic Data Solutions, Inc.
> >> Enterprise Application Studio 3.0 Consulting and Training
> >> http://www.dyn-data.com
> >>
> >> DDS is now hiring EAServer consultants
> >> to support its exploding EAServer business!
> >> Please submit your resume to
> >> hr@dyn-data.com!
> >>
> >> On Mon, 27 Mar 2000 19:38:46 -0600, Glenn Santa Cruz
> >> <spam?no.glenn_santacruz@dailyaccess.com> wrote:
> >>
> >> >No luck on technet -- site's not responding. However, I *did* find an
> >> >OCI attribute that deals with my situation:
> >> >OCI_ATTR_CURSOR_COMMIT_BEHAVIOR ; I'm not planning on approaching this
> >> >from a C/C++ level, so it doesn't do me much good...
> >> >
> >> >Glenn Santa Cruz wrote:
> >> >>
> >> >> I've tried both ways to no avail. Out on a limb here, but do you know
> >> >> offhand if there may be a registry entry that the OCI dll uses to
> >> >> determine whether or not to close cursors? I'm about to search technet
> >> >> for advice; if I find anything, I'll be sure to post it.
> >> >>
> >> >> Glenn
> >> >>
> >> >> "Carson Hager[Team Sybase]" wrote:
> >> >> >
> >> >> > They should definitely be closed. Is this using embedded SQL or
> >> >> > datastorers?
> >> >> >
> >> >> > Carson
> >> >> >
> >> >> > ___________________________________________________________
> >> >> >
> >> >> > Carson Hager
> >> >> > Team Sybase
> >> >> > Dynamic Data Solutions, Inc.
> >> >> > Enterprise Application Studio 3.0 Consulting and Training
> >> >> > http://www.dyn-data.com
> >> >> >
> >> >> > DDS is now hiring EAServer consultants
> >> >> > to support its exploding EAServer business!
> >> >> > Please submit your resume to
> >> >> > hr@dyn-data.com!
> >> >> >
> >> >> > On Mon, 27 Mar 2000 18:40:57 -0600, Glenn Santa Cruz
> >> >> > <spam?no.glenn_santacruz@dailyaccess.com> wrote:
> >> >> >
> >> >> > >Jaguar 3.01, build 30033
> >> >> > >PB 7.01, build 7021
> >> >> > >OCI 7.x cache
> >> >> > >ociw32.dll version 8.0.4.0.0
> >> >> > >
> >> >> > >I have a standard, transactional, poolable PB component that performs
> >> >> > >both inserts and updates to an Oracle 7.3.4 database; transactions are
> >> >> > >definitely being committed or rolled back as designed. However, cursors
> >> >> > >are not being closed (verified via V$OPEN_CURSOR) at transaction
> >> >> > >boundaries.
> >> >> > >
> >> >> > >Anyone know of configurable settings (for Jaguar) to close open cursors
> >> >> > >on a commit or rollback? Note that this behavior has not been seen when
> >> >> > >using traditional 2-tier PB applications, presumably because they use a
> >> >> > >different driver for connection.
> >> >> > >
> >> >> > >Major TIA.
> >> >> > >
> >> >> > >Glenn
> >> >> >
> >> >> > ___________________________________________________________
> >> >> >
> >> >> > Carson Hager
> >> >> > Team Sybase
> >> >> > Dynamic Data Solutions, Inc.
> >> >> > Enterprise Application Studio 3.0 Consulting and Training
> >> >> >
> >> >> > DDS Enterprise Application Framework
> >> >> > Available Now as Open Source!
> >> >> > http://www.dyn-data.com
> >>
> >> ___________________________________________________________
> >>
> >> Carson Hager
> >> Team Sybase
> >> Dynamic Data Solutions, Inc.
> >> Enterprise Application Studio 3.0 Consulting and Training
> >>
> >> DDS Enterprise Application Framework
> >> Available Now as Open Source!
> >> http://www.dyn-data.com
>
> ___________________________________________________________
>
> Carson Hager
> Team Sybase
> Dynamic Data Solutions, Inc.
> Enterprise Application Studio 3.0 Consulting and Training
>
> DDS Enterprise Application Framework
> Available Now as Open Source!
> http://www.dyn-data.com


Glenn Santa Cruz Posted on 2000-03-28 16:40:02.0Z
Newsgroups: sybase.public.easerver
Date: Tue, 28 Mar 2000 10:40:02 -0600
From: Glenn Santa Cruz <spam?no.glenn_santacruz@dailyaccess.com>
Organization: Daily Access Concepts
X-Mailer: Mozilla 4.7 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: Oracle OCI 7 ; cursors not closing
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 188
NNTP-Posting-Host: 12.6.74.30
Message-ID: <347_38E0E062.5A3F4AD@dailyaccess.com>
References: <347_38DFFF99.E3BD0905@dailyaccess.com> <347_38e015b2.94411746@forums.sybase.com> <347_38E00800.D6C10E4F@dailyaccess.com> <347_38E00D26.84438FE@dailyaccess.com> <347_38e01cbe.96216181@forums.sybase.com> <347_38E010FD.D2F8705F@dailyaccess.com> <347_38e022d8.97777686@forums.sybase.com> <347_38E0C692.D31DDA2@sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:25470
Article PK: 155553

I just tried your suggestion of setting SQLCache=0 prior to the
disconnect; unfortunately, it did not work. I will be experimenting a
bit further this week, and will keep you posted.

Thanks

Glenn

"Jim O'Neil [Sybase]" wrote:
>
> I'm leaning with Carson on this one - I"m not sure what the specific OCI API call is
> to set this number of cursors, but based on your experiences, it appears that it is a
> post-connection setting. Since Jaguar is actually making the physical connection,
> the only DBParms that will 'work' are those that cause calls to the client layer to
> be issued AFTER the physical connection (versus some DBParms that set up an
> environment before the connection is made). Since you are using a connection cache,
> the physical connection is NOT closed when PowerBuilder issues the DISCONNECT, so it
> would make sense that the cursors remain open.
>
> You mentioned using OCI 7 - are you using this with a 7.x client? If so, then the
> SQLCache parameter will have an effect on performance, so you might try setting
> SQLCache=8 (or whatever) on the CONNECT statement and then set SQLCache=0 right
> before the disconnect. I'm not certain that would work - depends on whether SQLCache
> is a 'hot' DBParm (some only get acknowledged once on the CONNECT). If you are using
> an 8.x client then actually SQLCache is not really buying you anything since the OCI
> 8 client does it's own caching that really obviates the need for PowerBuilder to do
> so. (OK, one more caveat - I'm not 100% sure that's the case if you are going
> through OCI 8 with the 7.x required support files).
>
> Jim O'Neil
> Sybase Technical Support
>
> "Carson Hager[Team Sybase]" wrote:
>
> > I would bet this is standard behavior to tell the DB connection
> > manager to keep them open until close.
> >
> > Carson
> >
> > ___________________________________________________________
> >
> > Carson Hager
> > Team Sybase
> > Dynamic Data Solutions, Inc.
> > Enterprise Application Studio 3.0 Consulting and Training
> > http://www.dyn-data.com
> >
> > DDS is now hiring EAServer consultants
> > to support its exploding EAServer business!
> > Please submit your resume to
> > hr@dyn-data.com!
> >
> > On Mon, 27 Mar 2000 19:55:09 -0600, Glenn Santa Cruz
> > <spam?no.glenn_santacruz@dailyaccess.com> wrote:
> >
> > >I think I may have found it. Thanks Carson, for suggesting the DBParm
> > >parameter. I started reading through the docs and found that SQLCache
> > >does indeed have some control over open cursors. My dbParm was set for
> > >SQLCache=8 (to help improve performance); removing the explicit setting
> > >and using the default (SQLCache=0) seems to have fixed the problem, but
> > >I now wonder if this is a bug?
> > >
> > >Glenn
> > >
> > >"Carson Hager[Team Sybase]" wrote:
> > >>
> > >> I wonder if that could be dictated through the DBParm parameter...
> > >>
> > >> Jim?
> > >>
> > >> Carson
> > >>
> > >> ___________________________________________________________
> > >>
> > >> Carson Hager
> > >> Team Sybase
> > >> Dynamic Data Solutions, Inc.
> > >> Enterprise Application Studio 3.0 Consulting and Training
> > >> http://www.dyn-data.com
> > >>
> > >> DDS is now hiring EAServer consultants
> > >> to support its exploding EAServer business!
> > >> Please submit your resume to
> > >> hr@dyn-data.com!
> > >>
> > >> On Mon, 27 Mar 2000 19:38:46 -0600, Glenn Santa Cruz
> > >> <spam?no.glenn_santacruz@dailyaccess.com> wrote:
> > >>
> > >> >No luck on technet -- site's not responding. However, I *did* find an
> > >> >OCI attribute that deals with my situation:
> > >> >OCI_ATTR_CURSOR_COMMIT_BEHAVIOR ; I'm not planning on approaching this
> > >> >from a C/C++ level, so it doesn't do me much good...
> > >> >
> > >> >Glenn Santa Cruz wrote:
> > >> >>
> > >> >> I've tried both ways to no avail. Out on a limb here, but do you know
> > >> >> offhand if there may be a registry entry that the OCI dll uses to
> > >> >> determine whether or not to close cursors? I'm about to search technet
> > >> >> for advice; if I find anything, I'll be sure to post it.
> > >> >>
> > >> >> Glenn
> > >> >>
> > >> >> "Carson Hager[Team Sybase]" wrote:
> > >> >> >
> > >> >> > They should definitely be closed. Is this using embedded SQL or
> > >> >> > datastorers?
> > >> >> >
> > >> >> > Carson
> > >> >> >
> > >> >> > ___________________________________________________________
> > >> >> >
> > >> >> > Carson Hager
> > >> >> > Team Sybase
> > >> >> > Dynamic Data Solutions, Inc.
> > >> >> > Enterprise Application Studio 3.0 Consulting and Training
> > >> >> > http://www.dyn-data.com
> > >> >> >
> > >> >> > DDS is now hiring EAServer consultants
> > >> >> > to support its exploding EAServer business!
> > >> >> > Please submit your resume to
> > >> >> > hr@dyn-data.com!
> > >> >> >
> > >> >> > On Mon, 27 Mar 2000 18:40:57 -0600, Glenn Santa Cruz
> > >> >> > <spam?no.glenn_santacruz@dailyaccess.com> wrote:
> > >> >> >
> > >> >> > >Jaguar 3.01, build 30033
> > >> >> > >PB 7.01, build 7021
> > >> >> > >OCI 7.x cache
> > >> >> > >ociw32.dll version 8.0.4.0.0
> > >> >> > >
> > >> >> > >I have a standard, transactional, poolable PB component that performs
> > >> >> > >both inserts and updates to an Oracle 7.3.4 database; transactions are
> > >> >> > >definitely being committed or rolled back as designed. However, cursors
> > >> >> > >are not being closed (verified via V$OPEN_CURSOR) at transaction
> > >> >> > >boundaries.
> > >> >> > >
> > >> >> > >Anyone know of configurable settings (for Jaguar) to close open cursors
> > >> >> > >on a commit or rollback? Note that this behavior has not been seen when
> > >> >> > >using traditional 2-tier PB applications, presumably because they use a
> > >> >> > >different driver for connection.
> > >> >> > >
> > >> >> > >Major TIA.
> > >> >> > >
> > >> >> > >Glenn
> > >> >> >
> > >> >> > ___________________________________________________________
> > >> >> >
> > >> >> > Carson Hager
> > >> >> > Team Sybase
> > >> >> > Dynamic Data Solutions, Inc.
> > >> >> > Enterprise Application Studio 3.0 Consulting and Training
> > >> >> >
> > >> >> > DDS Enterprise Application Framework
> > >> >> > Available Now as Open Source!
> > >> >> > http://www.dyn-data.com
> > >>
> > >> ___________________________________________________________
> > >>
> > >> Carson Hager
> > >> Team Sybase
> > >> Dynamic Data Solutions, Inc.
> > >> Enterprise Application Studio 3.0 Consulting and Training
> > >>
> > >> DDS Enterprise Application Framework
> > >> Available Now as Open Source!
> > >> http://www.dyn-data.com
> >
> > ___________________________________________________________
> >
> > Carson Hager
> > Team Sybase
> > Dynamic Data Solutions, Inc.
> > Enterprise Application Studio 3.0 Consulting and Training
> >
> > DDS Enterprise Application Framework
> > Available Now as Open Source!
> > http://www.dyn-data.com


Glenn Santa Cruz Posted on 2000-03-28 17:09:23.0Z
Newsgroups: sybase.public.easerver
Date: Tue, 28 Mar 2000 11:09:23 -0600
From: Glenn Santa Cruz <spam?no.glenn_santacruz@dailyaccess.com>
Organization: Daily Access Concepts
X-Mailer: Mozilla 4.7 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: Oracle OCI 7 ; cursors not closing
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 210
NNTP-Posting-Host: 12.6.74.30
Message-ID: <347_38E0E743.207BECA7@dailyaccess.com>
References: <347_38DFFF99.E3BD0905@dailyaccess.com> <347_38e015b2.94411746@forums.sybase.com> <347_38E00800.D6C10E4F@dailyaccess.com> <347_38E00D26.84438FE@dailyaccess.com> <347_38e01cbe.96216181@forums.sybase.com> <347_38E010FD.D2F8705F@dailyaccess.com> <347_38e022d8.97777686@forums.sybase.com> <347_38E0C692.D31DDA2@sybase.com> <347_38E0E062.5A3F4AD@dailyaccess.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:25466
Article PK: 155549

My DBA and I just went through a few test cases, and have found that any
non-zero value for SQLCache is effectively ignored. For zero values, the
total number of cursors opened at any given time does not exceed one.
Non-zero values allow the total number of open cursors to grow without
apparent bound; the database will throw an exception once the allowable
limit is reached. Quite likely we'll open a case for this, and I'll
post the number once we do so.

Thanks for your help.

Glenn

Glenn Santa Cruz wrote:
>
> I just tried your suggestion of setting SQLCache=0 prior to the
> disconnect; unfortunately, it did not work. I will be experimenting a
> bit further this week, and will keep you posted.
>
> Thanks
>
> Glenn
>
> "Jim O'Neil [Sybase]" wrote:
> >
> > I'm leaning with Carson on this one - I"m not sure what the specific OCI API call is
> > to set this number of cursors, but based on your experiences, it appears that it is a
> > post-connection setting. Since Jaguar is actually making the physical connection,
> > the only DBParms that will 'work' are those that cause calls to the client layer to
> > be issued AFTER the physical connection (versus some DBParms that set up an
> > environment before the connection is made). Since you are using a connection cache,
> > the physical connection is NOT closed when PowerBuilder issues the DISCONNECT, so it
> > would make sense that the cursors remain open.
> >
> > You mentioned using OCI 7 - are you using this with a 7.x client? If so, then the
> > SQLCache parameter will have an effect on performance, so you might try setting
> > SQLCache=8 (or whatever) on the CONNECT statement and then set SQLCache=0 right
> > before the disconnect. I'm not certain that would work - depends on whether SQLCache
> > is a 'hot' DBParm (some only get acknowledged once on the CONNECT). If you are using
> > an 8.x client then actually SQLCache is not really buying you anything since the OCI
> > 8 client does it's own caching that really obviates the need for PowerBuilder to do
> > so. (OK, one more caveat - I'm not 100% sure that's the case if you are going
> > through OCI 8 with the 7.x required support files).
> >
> > Jim O'Neil
> > Sybase Technical Support
> >
> > "Carson Hager[Team Sybase]" wrote:
> >
> > > I would bet this is standard behavior to tell the DB connection
> > > manager to keep them open until close.
> > >
> > > Carson
> > >
> > > ___________________________________________________________
> > >
> > > Carson Hager
> > > Team Sybase
> > > Dynamic Data Solutions, Inc.
> > > Enterprise Application Studio 3.0 Consulting and Training
> > > http://www.dyn-data.com
> > >
> > > DDS is now hiring EAServer consultants
> > > to support its exploding EAServer business!
> > > Please submit your resume to
> > > hr@dyn-data.com!
> > >
> > > On Mon, 27 Mar 2000 19:55:09 -0600, Glenn Santa Cruz
> > > <spam?no.glenn_santacruz@dailyaccess.com> wrote:
> > >
> > > >I think I may have found it. Thanks Carson, for suggesting the DBParm
> > > >parameter. I started reading through the docs and found that SQLCache
> > > >does indeed have some control over open cursors. My dbParm was set for
> > > >SQLCache=8 (to help improve performance); removing the explicit setting
> > > >and using the default (SQLCache=0) seems to have fixed the problem, but
> > > >I now wonder if this is a bug?
> > > >
> > > >Glenn
> > > >
> > > >"Carson Hager[Team Sybase]" wrote:
> > > >>
> > > >> I wonder if that could be dictated through the DBParm parameter...
> > > >>
> > > >> Jim?
> > > >>
> > > >> Carson
> > > >>
> > > >> ___________________________________________________________
> > > >>
> > > >> Carson Hager
> > > >> Team Sybase
> > > >> Dynamic Data Solutions, Inc.
> > > >> Enterprise Application Studio 3.0 Consulting and Training
> > > >> http://www.dyn-data.com
> > > >>
> > > >> DDS is now hiring EAServer consultants
> > > >> to support its exploding EAServer business!
> > > >> Please submit your resume to
> > > >> hr@dyn-data.com!
> > > >>
> > > >> On Mon, 27 Mar 2000 19:38:46 -0600, Glenn Santa Cruz
> > > >> <spam?no.glenn_santacruz@dailyaccess.com> wrote:
> > > >>
> > > >> >No luck on technet -- site's not responding. However, I *did* find an
> > > >> >OCI attribute that deals with my situation:
> > > >> >OCI_ATTR_CURSOR_COMMIT_BEHAVIOR ; I'm not planning on approaching this
> > > >> >from a C/C++ level, so it doesn't do me much good...
> > > >> >
> > > >> >Glenn Santa Cruz wrote:
> > > >> >>
> > > >> >> I've tried both ways to no avail. Out on a limb here, but do you know
> > > >> >> offhand if there may be a registry entry that the OCI dll uses to
> > > >> >> determine whether or not to close cursors? I'm about to search technet
> > > >> >> for advice; if I find anything, I'll be sure to post it.
> > > >> >>
> > > >> >> Glenn
> > > >> >>
> > > >> >> "Carson Hager[Team Sybase]" wrote:
> > > >> >> >
> > > >> >> > They should definitely be closed. Is this using embedded SQL or
> > > >> >> > datastorers?
> > > >> >> >
> > > >> >> > Carson
> > > >> >> >
> > > >> >> > ___________________________________________________________
> > > >> >> >
> > > >> >> > Carson Hager
> > > >> >> > Team Sybase
> > > >> >> > Dynamic Data Solutions, Inc.
> > > >> >> > Enterprise Application Studio 3.0 Consulting and Training
> > > >> >> > http://www.dyn-data.com
> > > >> >> >
> > > >> >> > DDS is now hiring EAServer consultants
> > > >> >> > to support its exploding EAServer business!
> > > >> >> > Please submit your resume to
> > > >> >> > hr@dyn-data.com!
> > > >> >> >
> > > >> >> > On Mon, 27 Mar 2000 18:40:57 -0600, Glenn Santa Cruz
> > > >> >> > <spam?no.glenn_santacruz@dailyaccess.com> wrote:
> > > >> >> >
> > > >> >> > >Jaguar 3.01, build 30033
> > > >> >> > >PB 7.01, build 7021
> > > >> >> > >OCI 7.x cache
> > > >> >> > >ociw32.dll version 8.0.4.0.0
> > > >> >> > >
> > > >> >> > >I have a standard, transactional, poolable PB component that performs
> > > >> >> > >both inserts and updates to an Oracle 7.3.4 database; transactions are
> > > >> >> > >definitely being committed or rolled back as designed. However, cursors
> > > >> >> > >are not being closed (verified via V$OPEN_CURSOR) at transaction
> > > >> >> > >boundaries.
> > > >> >> > >
> > > >> >> > >Anyone know of configurable settings (for Jaguar) to close open cursors
> > > >> >> > >on a commit or rollback? Note that this behavior has not been seen when
> > > >> >> > >using traditional 2-tier PB applications, presumably because they use a
> > > >> >> > >different driver for connection.
> > > >> >> > >
> > > >> >> > >Major TIA.
> > > >> >> > >
> > > >> >> > >Glenn
> > > >> >> >
> > > >> >> > ___________________________________________________________
> > > >> >> >
> > > >> >> > Carson Hager
> > > >> >> > Team Sybase
> > > >> >> > Dynamic Data Solutions, Inc.
> > > >> >> > Enterprise Application Studio 3.0 Consulting and Training
> > > >> >> >
> > > >> >> > DDS Enterprise Application Framework
> > > >> >> > Available Now as Open Source!
> > > >> >> > http://www.dyn-data.com
> > > >>
> > > >> ___________________________________________________________
> > > >>
> > > >> Carson Hager
> > > >> Team Sybase
> > > >> Dynamic Data Solutions, Inc.
> > > >> Enterprise Application Studio 3.0 Consulting and Training
> > > >>
> > > >> DDS Enterprise Application Framework
> > > >> Available Now as Open Source!
> > > >> http://www.dyn-data.com
> > >
> > > ___________________________________________________________
> > >
> > > Carson Hager
> > > Team Sybase
> > > Dynamic Data Solutions, Inc.
> > > Enterprise Application Studio 3.0 Consulting and Training
> > >
> > > DDS Enterprise Application Framework
> > > Available Now as Open Source!
> > > http://www.dyn-data.com


Glenn Santa Cruz Posted on 2000-03-28 15:39:52.0Z
Newsgroups: sybase.public.easerver
Date: Tue, 28 Mar 2000 09:39:52 -0600
From: Glenn Santa Cruz <spam?no.glenn_santacruz@dailyaccess.com>
Organization: Daily Access Concepts
X-Mailer: Mozilla 4.7 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: Oracle OCI 7 ; cursors not closing
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 196
NNTP-Posting-Host: 12.6.74.30
Message-ID: <347_38E0D248.9C0A8FE4@dailyaccess.com>
References: <347_38DFFF99.E3BD0905@dailyaccess.com> <347_38e015b2.94411746@forums.sybase.com> <347_38E00800.D6C10E4F@dailyaccess.com> <347_38E00D26.84438FE@dailyaccess.com> <347_38e01cbe.96216181@forums.sybase.com> <347_38E010FD.D2F8705F@dailyaccess.com> <347_38e022d8.97777686@forums.sybase.com> <347_38E0C692.D31DDA2@sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:25475
Article PK: 155558

I will post results as soon as I try your suggestion. The back-end DB
is 7.3.4, but the client-side dll for oci7 connectivity was installed
from an 8.0 client. For argument's sake, with regards to some dbparms
being set before a connection is made, is it possible to make/change
these settings somewhere in jaguar? Possibly within
com.sybase.jaguar.conncache.xxx ?? Or are these pre-connect dbparms set
by the first instance requesting a connection when no connections are in
the pool?

Glenn

"Jim O'Neil [Sybase]" wrote:
>
> I'm leaning with Carson on this one - I"m not sure what the specific OCI API call is
> to set this number of cursors, but based on your experiences, it appears that it is a
> post-connection setting. Since Jaguar is actually making the physical connection,
> the only DBParms that will 'work' are those that cause calls to the client layer to
> be issued AFTER the physical connection (versus some DBParms that set up an
> environment before the connection is made). Since you are using a connection cache,
> the physical connection is NOT closed when PowerBuilder issues the DISCONNECT, so it
> would make sense that the cursors remain open.
>
> You mentioned using OCI 7 - are you using this with a 7.x client? If so, then the
> SQLCache parameter will have an effect on performance, so you might try setting
> SQLCache=8 (or whatever) on the CONNECT statement and then set SQLCache=0 right
> before the disconnect. I'm not certain that would work - depends on whether SQLCache
> is a 'hot' DBParm (some only get acknowledged once on the CONNECT). If you are using
> an 8.x client then actually SQLCache is not really buying you anything since the OCI
> 8 client does it's own caching that really obviates the need for PowerBuilder to do
> so. (OK, one more caveat - I'm not 100% sure that's the case if you are going
> through OCI 8 with the 7.x required support files).
>
> Jim O'Neil
> Sybase Technical Support
>
> "Carson Hager[Team Sybase]" wrote:
>
> > I would bet this is standard behavior to tell the DB connection
> > manager to keep them open until close.
> >
> > Carson
> >
> > ___________________________________________________________
> >
> > Carson Hager
> > Team Sybase
> > Dynamic Data Solutions, Inc.
> > Enterprise Application Studio 3.0 Consulting and Training
> > http://www.dyn-data.com
> >
> > DDS is now hiring EAServer consultants
> > to support its exploding EAServer business!
> > Please submit your resume to
> > hr@dyn-data.com!
> >
> > On Mon, 27 Mar 2000 19:55:09 -0600, Glenn Santa Cruz
> > <spam?no.glenn_santacruz@dailyaccess.com> wrote:
> >
> > >I think I may have found it. Thanks Carson, for suggesting the DBParm
> > >parameter. I started reading through the docs and found that SQLCache
> > >does indeed have some control over open cursors. My dbParm was set for
> > >SQLCache=8 (to help improve performance); removing the explicit setting
> > >and using the default (SQLCache=0) seems to have fixed the problem, but
> > >I now wonder if this is a bug?
> > >
> > >Glenn
> > >
> > >"Carson Hager[Team Sybase]" wrote:
> > >>
> > >> I wonder if that could be dictated through the DBParm parameter...
> > >>
> > >> Jim?
> > >>
> > >> Carson
> > >>
> > >> ___________________________________________________________
> > >>
> > >> Carson Hager
> > >> Team Sybase
> > >> Dynamic Data Solutions, Inc.
> > >> Enterprise Application Studio 3.0 Consulting and Training
> > >> http://www.dyn-data.com
> > >>
> > >> DDS is now hiring EAServer consultants
> > >> to support its exploding EAServer business!
> > >> Please submit your resume to
> > >> hr@dyn-data.com!
> > >>
> > >> On Mon, 27 Mar 2000 19:38:46 -0600, Glenn Santa Cruz
> > >> <spam?no.glenn_santacruz@dailyaccess.com> wrote:
> > >>
> > >> >No luck on technet -- site's not responding. However, I *did* find an
> > >> >OCI attribute that deals with my situation:
> > >> >OCI_ATTR_CURSOR_COMMIT_BEHAVIOR ; I'm not planning on approaching this
> > >> >from a C/C++ level, so it doesn't do me much good...
> > >> >
> > >> >Glenn Santa Cruz wrote:
> > >> >>
> > >> >> I've tried both ways to no avail. Out on a limb here, but do you know
> > >> >> offhand if there may be a registry entry that the OCI dll uses to
> > >> >> determine whether or not to close cursors? I'm about to search technet
> > >> >> for advice; if I find anything, I'll be sure to post it.
> > >> >>
> > >> >> Glenn
> > >> >>
> > >> >> "Carson Hager[Team Sybase]" wrote:
> > >> >> >
> > >> >> > They should definitely be closed. Is this using embedded SQL or
> > >> >> > datastorers?
> > >> >> >
> > >> >> > Carson
> > >> >> >
> > >> >> > ___________________________________________________________
> > >> >> >
> > >> >> > Carson Hager
> > >> >> > Team Sybase
> > >> >> > Dynamic Data Solutions, Inc.
> > >> >> > Enterprise Application Studio 3.0 Consulting and Training
> > >> >> > http://www.dyn-data.com
> > >> >> >
> > >> >> > DDS is now hiring EAServer consultants
> > >> >> > to support its exploding EAServer business!
> > >> >> > Please submit your resume to
> > >> >> > hr@dyn-data.com!
> > >> >> >
> > >> >> > On Mon, 27 Mar 2000 18:40:57 -0600, Glenn Santa Cruz
> > >> >> > <spam?no.glenn_santacruz@dailyaccess.com> wrote:
> > >> >> >
> > >> >> > >Jaguar 3.01, build 30033
> > >> >> > >PB 7.01, build 7021
> > >> >> > >OCI 7.x cache
> > >> >> > >ociw32.dll version 8.0.4.0.0
> > >> >> > >
> > >> >> > >I have a standard, transactional, poolable PB component that performs
> > >> >> > >both inserts and updates to an Oracle 7.3.4 database; transactions are
> > >> >> > >definitely being committed or rolled back as designed. However, cursors
> > >> >> > >are not being closed (verified via V$OPEN_CURSOR) at transaction
> > >> >> > >boundaries.
> > >> >> > >
> > >> >> > >Anyone know of configurable settings (for Jaguar) to close open cursors
> > >> >> > >on a commit or rollback? Note that this behavior has not been seen when
> > >> >> > >using traditional 2-tier PB applications, presumably because they use a
> > >> >> > >different driver for connection.
> > >> >> > >
> > >> >> > >Major TIA.
> > >> >> > >
> > >> >> > >Glenn
> > >> >> >
> > >> >> > ___________________________________________________________
> > >> >> >
> > >> >> > Carson Hager
> > >> >> > Team Sybase
> > >> >> > Dynamic Data Solutions, Inc.
> > >> >> > Enterprise Application Studio 3.0 Consulting and Training
> > >> >> >
> > >> >> > DDS Enterprise Application Framework
> > >> >> > Available Now as Open Source!
> > >> >> > http://www.dyn-data.com
> > >>
> > >> ___________________________________________________________
> > >>
> > >> Carson Hager
> > >> Team Sybase
> > >> Dynamic Data Solutions, Inc.
> > >> Enterprise Application Studio 3.0 Consulting and Training
> > >>
> > >> DDS Enterprise Application Framework
> > >> Available Now as Open Source!
> > >> http://www.dyn-data.com
> >
> > ___________________________________________________________
> >
> > Carson Hager
> > Team Sybase
> > Dynamic Data Solutions, Inc.
> > Enterprise Application Studio 3.0 Consulting and Training
> >
> > DDS Enterprise Application Framework
> > Available Now as Open Source!
> > http://www.dyn-data.com


Jim O'Neil [Sybase] Posted on 2000-03-28 15:55:53.0Z
Newsgroups: sybase.public.easerver
Date: Tue, 28 Mar 2000 10:55:53 -0500
From: "Jim O'Neil [Sybase]" <joneil@sybase.com>
Organization: Sybase, Inc.
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: Oracle OCI 7 ; cursors not closing
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 227
NNTP-Posting-Host: joneil-nt.sybase.com 204.167.42.111
Message-ID: <347_38E0D608.944A2B3D@sybase.com>
References: <347_38DFFF99.E3BD0905@dailyaccess.com> <347_38e015b2.94411746@forums.sybase.com> <347_38E00800.D6C10E4F@dailyaccess.com> <347_38E00D26.84438FE@dailyaccess.com> <347_38e01cbe.96216181@forums.sybase.com> <347_38E010FD.D2F8705F@dailyaccess.com> <347_38e022d8.97777686@forums.sybase.com> <347_38E0C692.D31DDA2@sybase.com> <347_38E0D248.9C0A8FE4@dailyaccess.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:25471
Article PK: 155552

There is a handful of things you can put in for ct-lib connections in the conncache.props
file, but I don't believe there's anything for Oracle - may be a case for an enhancement
request. Basically, my last understanding from development was that the DBParms are not
passed to Jaguar when it makes the physical connection, so the 'pre-connect' DBParms are
essentially ignored (this is somewhat validated by the 7.0.1 release notes which talk about
all the SYC/SYJ DBParms which have no effect in Jaguar). Only the 'post-connect' parms
would have effect, because essentially the CONNECT in PowerBuilder would get the existing
connection handle for the cache from Jaguar and then execute a few OCI setup calls (the
same calls it would make after a physical connection in a two-tier PB environment).


--
Jim O'Neil
Senior Technical Support Engineer
Sybase, Inc

Glenn Santa Cruz wrote:

> I will post results as soon as I try your suggestion. The back-end DB
> is 7.3.4, but the client-side dll for oci7 connectivity was installed
> from an 8.0 client. For argument's sake, with regards to some dbparms
> being set before a connection is made, is it possible to make/change
> these settings somewhere in jaguar? Possibly within
> com.sybase.jaguar.conncache.xxx ?? Or are these pre-connect dbparms set
> by the first instance requesting a connection when no connections are in
> the pool?
>
> Glenn
>
> "Jim O'Neil [Sybase]" wrote:
> >
> > I'm leaning with Carson on this one - I"m not sure what the specific OCI API call is
> > to set this number of cursors, but based on your experiences, it appears that it is a
> > post-connection setting. Since Jaguar is actually making the physical connection,
> > the only DBParms that will 'work' are those that cause calls to the client layer to
> > be issued AFTER the physical connection (versus some DBParms that set up an
> > environment before the connection is made). Since you are using a connection cache,
> > the physical connection is NOT closed when PowerBuilder issues the DISCONNECT, so it
> > would make sense that the cursors remain open.
> >
> > You mentioned using OCI 7 - are you using this with a 7.x client? If so, then the
> > SQLCache parameter will have an effect on performance, so you might try setting
> > SQLCache=8 (or whatever) on the CONNECT statement and then set SQLCache=0 right
> > before the disconnect. I'm not certain that would work - depends on whether SQLCache
> > is a 'hot' DBParm (some only get acknowledged once on the CONNECT). If you are using
> > an 8.x client then actually SQLCache is not really buying you anything since the OCI
> > 8 client does it's own caching that really obviates the need for PowerBuilder to do
> > so. (OK, one more caveat - I'm not 100% sure that's the case if you are going
> > through OCI 8 with the 7.x required support files).
> >
> > Jim O'Neil
> > Sybase Technical Support
> >
> > "Carson Hager[Team Sybase]" wrote:
> >
> > > I would bet this is standard behavior to tell the DB connection
> > > manager to keep them open until close.
> > >
> > > Carson
> > >
> > > ___________________________________________________________
> > >
> > > Carson Hager
> > > Team Sybase
> > > Dynamic Data Solutions, Inc.
> > > Enterprise Application Studio 3.0 Consulting and Training
> > > http://www.dyn-data.com
> > >
> > > DDS is now hiring EAServer consultants
> > > to support its exploding EAServer business!
> > > Please submit your resume to
> > > hr@dyn-data.com!
> > >
> > > On Mon, 27 Mar 2000 19:55:09 -0600, Glenn Santa Cruz
> > > <spam?no.glenn_santacruz@dailyaccess.com> wrote:
> > >
> > > >I think I may have found it. Thanks Carson, for suggesting the DBParm
> > > >parameter. I started reading through the docs and found that SQLCache
> > > >does indeed have some control over open cursors. My dbParm was set for
> > > >SQLCache=8 (to help improve performance); removing the explicit setting
> > > >and using the default (SQLCache=0) seems to have fixed the problem, but
> > > >I now wonder if this is a bug?
> > > >
> > > >Glenn
> > > >
> > > >"Carson Hager[Team Sybase]" wrote:
> > > >>
> > > >> I wonder if that could be dictated through the DBParm parameter...
> > > >>
> > > >> Jim?
> > > >>
> > > >> Carson
> > > >>
> > > >> ___________________________________________________________
> > > >>
> > > >> Carson Hager
> > > >> Team Sybase
> > > >> Dynamic Data Solutions, Inc.
> > > >> Enterprise Application Studio 3.0 Consulting and Training
> > > >> http://www.dyn-data.com
> > > >>
> > > >> DDS is now hiring EAServer consultants
> > > >> to support its exploding EAServer business!
> > > >> Please submit your resume to
> > > >> hr@dyn-data.com!
> > > >>
> > > >> On Mon, 27 Mar 2000 19:38:46 -0600, Glenn Santa Cruz
> > > >> <spam?no.glenn_santacruz@dailyaccess.com> wrote:
> > > >>
> > > >> >No luck on technet -- site's not responding. However, I *did* find an
> > > >> >OCI attribute that deals with my situation:
> > > >> >OCI_ATTR_CURSOR_COMMIT_BEHAVIOR ; I'm not planning on approaching this
> > > >> >from a C/C++ level, so it doesn't do me much good...
> > > >> >
> > > >> >Glenn Santa Cruz wrote:
> > > >> >>
> > > >> >> I've tried both ways to no avail. Out on a limb here, but do you know
> > > >> >> offhand if there may be a registry entry that the OCI dll uses to
> > > >> >> determine whether or not to close cursors? I'm about to search technet
> > > >> >> for advice; if I find anything, I'll be sure to post it.
> > > >> >>
> > > >> >> Glenn
> > > >> >>
> > > >> >> "Carson Hager[Team Sybase]" wrote:
> > > >> >> >
> > > >> >> > They should definitely be closed. Is this using embedded SQL or
> > > >> >> > datastorers?
> > > >> >> >
> > > >> >> > Carson
> > > >> >> >
> > > >> >> > ___________________________________________________________
> > > >> >> >
> > > >> >> > Carson Hager
> > > >> >> > Team Sybase
> > > >> >> > Dynamic Data Solutions, Inc.
> > > >> >> > Enterprise Application Studio 3.0 Consulting and Training
> > > >> >> > http://www.dyn-data.com
> > > >> >> >
> > > >> >> > DDS is now hiring EAServer consultants
> > > >> >> > to support its exploding EAServer business!
> > > >> >> > Please submit your resume to
> > > >> >> > hr@dyn-data.com!
> > > >> >> >
> > > >> >> > On Mon, 27 Mar 2000 18:40:57 -0600, Glenn Santa Cruz
> > > >> >> > <spam?no.glenn_santacruz@dailyaccess.com> wrote:
> > > >> >> >
> > > >> >> > >Jaguar 3.01, build 30033
> > > >> >> > >PB 7.01, build 7021
> > > >> >> > >OCI 7.x cache
> > > >> >> > >ociw32.dll version 8.0.4.0.0
> > > >> >> > >
> > > >> >> > >I have a standard, transactional, poolable PB component that performs
> > > >> >> > >both inserts and updates to an Oracle 7.3.4 database; transactions are
> > > >> >> > >definitely being committed or rolled back as designed. However, cursors
> > > >> >> > >are not being closed (verified via V$OPEN_CURSOR) at transaction
> > > >> >> > >boundaries.
> > > >> >> > >
> > > >> >> > >Anyone know of configurable settings (for Jaguar) to close open cursors
> > > >> >> > >on a commit or rollback? Note that this behavior has not been seen when
> > > >> >> > >using traditional 2-tier PB applications, presumably because they use a
> > > >> >> > >different driver for connection.
> > > >> >> > >
> > > >> >> > >Major TIA.
> > > >> >> > >
> > > >> >> > >Glenn
> > > >> >> >
> > > >> >> > ___________________________________________________________
> > > >> >> >
> > > >> >> > Carson Hager
> > > >> >> > Team Sybase
> > > >> >> > Dynamic Data Solutions, Inc.
> > > >> >> > Enterprise Application Studio 3.0 Consulting and Training
> > > >> >> >
> > > >> >> > DDS Enterprise Application Framework
> > > >> >> > Available Now as Open Source!
> > > >> >> > http://www.dyn-data.com
> > > >>
> > > >> ___________________________________________________________
> > > >>
> > > >> Carson Hager
> > > >> Team Sybase
> > > >> Dynamic Data Solutions, Inc.
> > > >> Enterprise Application Studio 3.0 Consulting and Training
> > > >>
> > > >> DDS Enterprise Application Framework
> > > >> Available Now as Open Source!
> > > >> http://www.dyn-data.com
> > >
> > > ___________________________________________________________
> > >
> > > Carson Hager
> > > Team Sybase
> > > Dynamic Data Solutions, Inc.
> > > Enterprise Application Studio 3.0 Consulting and Training
> > >
> > > DDS Enterprise Application Framework
> > > Available Now as Open Source!
> > > http://www.dyn-data.com


Carson Hager[Team Sybase] Posted on 2000-03-28 02:44:28.0Z
Newsgroups: sybase.public.easerver
From: chager@dyn-data.com (Carson Hager[Team Sybase])
Subject: Re: Oracle OCI 7 ; cursors not closing
Date: Tue, 28 Mar 2000 02:44:28 GMT
Organization: Dynamic Data Solutions, Inc.
X-Newsreader: Forte Free Agent 1.21/32.243
Lines: 79
NNTP-Posting-Host: charon.lifescape.com 63.86.26.130
Message-ID: <347_38e01c71.96139250@forums.sybase.com>
References: <347_38DFFF99.E3BD0905@dailyaccess.com> <347_38e015b2.94411746@forums.sybase.com> <347_38E00800.D6C10E4F@dailyaccess.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:25547
Article PK: 155621

The only time I've seen this in Jag has been when I forgot to close a
ResultSet in java. This should be handled by EAServer/PBVM.


Carson

___________________________________________________________

Carson Hager
Team Sybase
Dynamic Data Solutions, Inc.
Enterprise Application Studio 3.0 Consulting and Training
http://www.dyn-data.com

DDS is now hiring EAServer consultants
to support its exploding EAServer business!
Please submit your resume to
hr@dyn-data.com!


On Mon, 27 Mar 2000 19:16:48 -0600, Glenn Santa Cruz

<spam?no.glenn_santacruz@dailyaccess.com> wrote:

>I've tried both ways to no avail. Out on a limb here, but do you know
>offhand if there may be a registry entry that the OCI dll uses to
>determine whether or not to close cursors? I'm about to search technet
>for advice; if I find anything, I'll be sure to post it.
>
>Glenn
>
>
>"Carson Hager[Team Sybase]" wrote:
>>
>> They should definitely be closed. Is this using embedded SQL or
>> datastorers?
>>
>> Carson
>>
>> ___________________________________________________________
>>
>> Carson Hager
>> Team Sybase
>> Dynamic Data Solutions, Inc.
>> Enterprise Application Studio 3.0 Consulting and Training
>> http://www.dyn-data.com
>>
>> DDS is now hiring EAServer consultants
>> to support its exploding EAServer business!
>> Please submit your resume to
>> hr@dyn-data.com!
>>
>> On Mon, 27 Mar 2000 18:40:57 -0600, Glenn Santa Cruz
>> <spam?no.glenn_santacruz@dailyaccess.com> wrote:
>>
>> >Jaguar 3.01, build 30033
>> >PB 7.01, build 7021
>> >OCI 7.x cache
>> >ociw32.dll version 8.0.4.0.0
>> >
>> >I have a standard, transactional, poolable PB component that performs
>> >both inserts and updates to an Oracle 7.3.4 database; transactions are
>> >definitely being committed or rolled back as designed. However, cursors
>> >are not being closed (verified via V$OPEN_CURSOR) at transaction
>> >boundaries.
>> >
>> >Anyone know of configurable settings (for Jaguar) to close open cursors
>> >on a commit or rollback? Note that this behavior has not been seen when
>> >using traditional 2-tier PB applications, presumably because they use a
>> >different driver for connection.
>> >
>> >Major TIA.
>> >
>> >Glenn
>>
>> ___________________________________________________________
>>
>> Carson Hager
>> Team Sybase
>> Dynamic Data Solutions, Inc.
>> Enterprise Application Studio 3.0 Consulting and Training
>>
>> DDS Enterprise Application Framework
>> Available Now as Open Source!
>> http://www.dyn-data.com

___________________________________________________________

Carson Hager
Team Sybase
Dynamic Data Solutions, Inc.
Enterprise Application Studio 3.0 Consulting and Training

DDS Enterprise Application Framework
Available Now as Open Source!
http://www.dyn-data.com


Glenn Santa Cruz Posted on 2000-03-28 01:41:58.0Z
Newsgroups: sybase.public.easerver
Date: Mon, 27 Mar 2000 19:41:58 -0600
From: Glenn Santa Cruz <spam?no.glenn_santacruz@dailyaccess.com>
Organization: Daily Access Concepts
X-Mailer: Mozilla 4.7 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: Oracle OCI 7 ; cursors not closing
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 93
NNTP-Posting-Host: 12.6.74.30
Message-ID: <347_38E00DE6.6E8FB558@dailyaccess.com>
References: <347_38DFFF99.E3BD0905@dailyaccess.com> <347_38e015b2.94411746@forums.sybase.com> <347_38E00800.D6C10E4F@dailyaccess.com> <347_38e01c71.96139250@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:25544
Article PK: 155617

Well, now that you mention it, there *is* a bit of java in the mix, but
it resides only as a non-transactional service component, making an
intercomponent call to a transactional PB component. I'll attempt to
call the PB component directly from the client tomorrow morning, to see
if that changes anything.

Thanks

Glenn

"Carson Hager[Team Sybase]" wrote:
>
> The only time I've seen this in Jag has been when I forgot to close a
> ResultSet in java. This should be handled by EAServer/PBVM.
>
> Carson
>
> ___________________________________________________________
>
> Carson Hager
> Team Sybase
> Dynamic Data Solutions, Inc.
> Enterprise Application Studio 3.0 Consulting and Training
> http://www.dyn-data.com
>
> DDS is now hiring EAServer consultants
> to support its exploding EAServer business!
> Please submit your resume to
> hr@dyn-data.com!
>
> On Mon, 27 Mar 2000 19:16:48 -0600, Glenn Santa Cruz
> <spam?no.glenn_santacruz@dailyaccess.com> wrote:
>
> >I've tried both ways to no avail. Out on a limb here, but do you know
> >offhand if there may be a registry entry that the OCI dll uses to
> >determine whether or not to close cursors? I'm about to search technet
> >for advice; if I find anything, I'll be sure to post it.
> >
> >Glenn
> >
> >
> >"Carson Hager[Team Sybase]" wrote:
> >>
> >> They should definitely be closed. Is this using embedded SQL or
> >> datastorers?
> >>
> >> Carson
> >>
> >> ___________________________________________________________
> >>
> >> Carson Hager
> >> Team Sybase
> >> Dynamic Data Solutions, Inc.
> >> Enterprise Application Studio 3.0 Consulting and Training
> >> http://www.dyn-data.com
> >>
> >> DDS is now hiring EAServer consultants
> >> to support its exploding EAServer business!
> >> Please submit your resume to
> >> hr@dyn-data.com!
> >>
> >> On Mon, 27 Mar 2000 18:40:57 -0600, Glenn Santa Cruz
> >> <spam?no.glenn_santacruz@dailyaccess.com> wrote:
> >>
> >> >Jaguar 3.01, build 30033
> >> >PB 7.01, build 7021
> >> >OCI 7.x cache
> >> >ociw32.dll version 8.0.4.0.0
> >> >
> >> >I have a standard, transactional, poolable PB component that performs
> >> >both inserts and updates to an Oracle 7.3.4 database; transactions are
> >> >definitely being committed or rolled back as designed. However, cursors
> >> >are not being closed (verified via V$OPEN_CURSOR) at transaction
> >> >boundaries.
> >> >
> >> >Anyone know of configurable settings (for Jaguar) to close open cursors
> >> >on a commit or rollback? Note that this behavior has not been seen when
> >> >using traditional 2-tier PB applications, presumably because they use a
> >> >different driver for connection.
> >> >
> >> >Major TIA.
> >> >
> >> >Glenn
> >>
> >> ___________________________________________________________
> >>
> >> Carson Hager
> >> Team Sybase
> >> Dynamic Data Solutions, Inc.
> >> Enterprise Application Studio 3.0 Consulting and Training
> >>
> >> DDS Enterprise Application Framework
> >> Available Now as Open Source!
> >> http://www.dyn-data.com
>
> ___________________________________________________________
>
> Carson Hager
> Team Sybase
> Dynamic Data Solutions, Inc.
> Enterprise Application Studio 3.0 Consulting and Training
>
> DDS Enterprise Application Framework
> Available Now as Open Source!
> http://www.dyn-data.com


Dave Wolf [Sybase] Posted on 2000-03-28 02:03:03.0Z
Newsgroups: sybase.public.easerver
From: "Dave Wolf [Sybase]" <dwolf@sybase.com>
Subject: Re: Oracle OCI 7 ; cursors not closing
Date: Mon, 27 Mar 2000 21:03:03 -0500
Lines: 127
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
NNTP-Posting-Host: nomad6-31.sybase.com 157.133.176.31
Message-ID: <347_5mUwnpFm$GA.290@forums.sybase.com>
References: <347_38DFFF99.E3BD0905@dailyaccess.com> <347_38e015b2.94411746@forums.sybase.com> <347_38E00800.D6C10E4F@dailyaccess.com> <347_38e01c71.96139250@forums.sybase.com> <347_38E00DE6.6E8FB558@dailyaccess.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:25537
Article PK: 155610

You should dig into that. The Oracle JDBC driver is very touchy and a bit
odd about ResultSet.close() and Statement.close(). Statement.close() should
close the ResultSet butttt its seems the JDBC driver is very touchy about
that. And sometimes when you do get this to work, then also close the
ResultSet it throws a SQLException, but not others. For a few benchmarks
this drove me batty as it makes Oracle run out of available statements very
fast. I cant remember the specifics but I had to be very very anal about
how I closed everything up.

Dave Wolf
Internet Applications Division

"Glenn Santa Cruz" <spam?no.glenn_santacruz@dailyaccess.com> wrote in
message news:38E00DE6.6E8FB558@dailyaccess.com...
> Well, now that you mention it, there *is* a bit of java in the mix, but
> it resides only as a non-transactional service component, making an
> intercomponent call to a transactional PB component. I'll attempt to
> call the PB component directly from the client tomorrow morning, to see
> if that changes anything.
>
> Thanks
>
> Glenn
>
> "Carson Hager[Team Sybase]" wrote:
> >
> > The only time I've seen this in Jag has been when I forgot to close a
> > ResultSet in java. This should be handled by EAServer/PBVM.
> >
> > Carson
> >
> > ___________________________________________________________
> >
> > Carson Hager
> > Team Sybase
> > Dynamic Data Solutions, Inc.
> > Enterprise Application Studio 3.0 Consulting and Training
> > http://www.dyn-data.com
> >
> > DDS is now hiring EAServer consultants
> > to support its exploding EAServer business!
> > Please submit your resume to
> > hr@dyn-data.com!
> >
> > On Mon, 27 Mar 2000 19:16:48 -0600, Glenn Santa Cruz
> > <spam?no.glenn_santacruz@dailyaccess.com> wrote:
> >
> > >I've tried both ways to no avail. Out on a limb here, but do you know
> > >offhand if there may be a registry entry that the OCI dll uses to
> > >determine whether or not to close cursors? I'm about to search technet
> > >for advice; if I find anything, I'll be sure to post it.
> > >
> > >Glenn
> > >
> > >
> > >"Carson Hager[Team Sybase]" wrote:
> > >>
> > >> They should definitely be closed. Is this using embedded SQL or
> > >> datastorers?
> > >>
> > >> Carson
> > >>
> > >> ___________________________________________________________
> > >>
> > >> Carson Hager
> > >> Team Sybase
> > >> Dynamic Data Solutions, Inc.
> > >> Enterprise Application Studio 3.0 Consulting and Training
> > >> http://www.dyn-data.com
> > >>
> > >> DDS is now hiring EAServer consultants
> > >> to support its exploding EAServer business!
> > >> Please submit your resume to
> > >> hr@dyn-data.com!
> > >>
> > >> On Mon, 27 Mar 2000 18:40:57 -0600, Glenn Santa Cruz
> > >> <spam?no.glenn_santacruz@dailyaccess.com> wrote:
> > >>
> > >> >Jaguar 3.01, build 30033
> > >> >PB 7.01, build 7021
> > >> >OCI 7.x cache
> > >> >ociw32.dll version 8.0.4.0.0
> > >> >
> > >> >I have a standard, transactional, poolable PB component that
performs
> > >> >both inserts and updates to an Oracle 7.3.4 database; transactions
are
> > >> >definitely being committed or rolled back as designed. However,
cursors
> > >> >are not being closed (verified via V$OPEN_CURSOR) at transaction
> > >> >boundaries.
> > >> >
> > >> >Anyone know of configurable settings (for Jaguar) to close open
cursors
> > >> >on a commit or rollback? Note that this behavior has not been seen
when
> > >> >using traditional 2-tier PB applications, presumably because they
use a
> > >> >different driver for connection.
> > >> >
> > >> >Major TIA.
> > >> >
> > >> >Glenn
> > >>
> > >> ___________________________________________________________
> > >>
> > >> Carson Hager
> > >> Team Sybase
> > >> Dynamic Data Solutions, Inc.
> > >> Enterprise Application Studio 3.0 Consulting and Training
> > >>
> > >> DDS Enterprise Application Framework
> > >> Available Now as Open Source!
> > >> http://www.dyn-data.com
> >
> > ___________________________________________________________
> >
> > Carson Hager
> > Team Sybase
> > Dynamic Data Solutions, Inc.
> > Enterprise Application Studio 3.0 Consulting and Training
> >
> > DDS Enterprise Application Framework
> > Available Now as Open Source!
> > http://www.dyn-data.com


Carson Hager[Team Sybase] Posted on 2000-03-28 03:12:51.0Z
Newsgroups: sybase.public.easerver
From: chager@dyn-data.com (Carson Hager[Team Sybase])
Subject: Re: Oracle OCI 7 ; cursors not closing
Date: Tue, 28 Mar 2000 03:12:51 GMT
Organization: Dynamic Data Solutions, Inc.
X-Newsreader: Forte Free Agent 1.21/32.243
Lines: 143
NNTP-Posting-Host: charon.lifescape.com 63.86.26.130
Message-ID: <347_38e0231f.97848678@forums.sybase.com>
References: <347_38DFFF99.E3BD0905@dailyaccess.com> <347_38e015b2.94411746@forums.sybase.com> <347_38E00800.D6C10E4F@dailyaccess.com> <347_38e01c71.96139250@forums.sybase.com> <347_38E00DE6.6E8FB558@dailyaccess.com> <347_5mUwnpFm$GA.290@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:25534
Article PK: 155607

Totally forgot to mention the Statement/PreparedStatement part...


Carson

___________________________________________________________

Carson Hager
Team Sybase
Dynamic Data Solutions, Inc.
Enterprise Application Studio 3.0 Consulting and Training
http://www.dyn-data.com

DDS is now hiring EAServer consultants
to support its exploding EAServer business!
Please submit your resume to
hr@dyn-data.com!


On Mon, 27 Mar 2000 21:03:03 -0500, "Dave Wolf [Sybase]"

<dwolf@sybase.com> wrote:

>You should dig into that. The Oracle JDBC driver is very touchy and a bit
>odd about ResultSet.close() and Statement.close(). Statement.close() should
>close the ResultSet butttt its seems the JDBC driver is very touchy about
>that. And sometimes when you do get this to work, then also close the
>ResultSet it throws a SQLException, but not others. For a few benchmarks
>this drove me batty as it makes Oracle run out of available statements very
>fast. I cant remember the specifics but I had to be very very anal about
>how I closed everything up.
>
>Dave Wolf
>Internet Applications Division
>
>"Glenn Santa Cruz" <spam?no.glenn_santacruz@dailyaccess.com> wrote in
>message news:38E00DE6.6E8FB558@dailyaccess.com...
>> Well, now that you mention it, there *is* a bit of java in the mix, but
>> it resides only as a non-transactional service component, making an
>> intercomponent call to a transactional PB component. I'll attempt to
>> call the PB component directly from the client tomorrow morning, to see
>> if that changes anything.
>>
>> Thanks
>>
>> Glenn
>>
>> "Carson Hager[Team Sybase]" wrote:
>> >
>> > The only time I've seen this in Jag has been when I forgot to close a
>> > ResultSet in java. This should be handled by EAServer/PBVM.
>> >
>> > Carson
>> >
>> > ___________________________________________________________
>> >
>> > Carson Hager
>> > Team Sybase
>> > Dynamic Data Solutions, Inc.
>> > Enterprise Application Studio 3.0 Consulting and Training
>> > http://www.dyn-data.com
>> >
>> > DDS is now hiring EAServer consultants
>> > to support its exploding EAServer business!
>> > Please submit your resume to
>> > hr@dyn-data.com!
>> >
>> > On Mon, 27 Mar 2000 19:16:48 -0600, Glenn Santa Cruz
>> > <spam?no.glenn_santacruz@dailyaccess.com> wrote:
>> >
>> > >I've tried both ways to no avail. Out on a limb here, but do you know
>> > >offhand if there may be a registry entry that the OCI dll uses to
>> > >determine whether or not to close cursors? I'm about to search technet
>> > >for advice; if I find anything, I'll be sure to post it.
>> > >
>> > >Glenn
>> > >
>> > >
>> > >"Carson Hager[Team Sybase]" wrote:
>> > >>
>> > >> They should definitely be closed. Is this using embedded SQL or
>> > >> datastorers?
>> > >>
>> > >> Carson
>> > >>
>> > >> ___________________________________________________________
>> > >>
>> > >> Carson Hager
>> > >> Team Sybase
>> > >> Dynamic Data Solutions, Inc.
>> > >> Enterprise Application Studio 3.0 Consulting and Training
>> > >> http://www.dyn-data.com
>> > >>
>> > >> DDS is now hiring EAServer consultants
>> > >> to support its exploding EAServer business!
>> > >> Please submit your resume to
>> > >> hr@dyn-data.com!
>> > >>
>> > >> On Mon, 27 Mar 2000 18:40:57 -0600, Glenn Santa Cruz
>> > >> <spam?no.glenn_santacruz@dailyaccess.com> wrote:
>> > >>
>> > >> >Jaguar 3.01, build 30033
>> > >> >PB 7.01, build 7021
>> > >> >OCI 7.x cache
>> > >> >ociw32.dll version 8.0.4.0.0
>> > >> >
>> > >> >I have a standard, transactional, poolable PB component that
>performs
>> > >> >both inserts and updates to an Oracle 7.3.4 database; transactions
>are
>> > >> >definitely being committed or rolled back as designed. However,
>cursors
>> > >> >are not being closed (verified via V$OPEN_CURSOR) at transaction
>> > >> >boundaries.
>> > >> >
>> > >> >Anyone know of configurable settings (for Jaguar) to close open
>cursors
>> > >> >on a commit or rollback? Note that this behavior has not been seen
>when
>> > >> >using traditional 2-tier PB applications, presumably because they
>use a
>> > >> >different driver for connection.
>> > >> >
>> > >> >Major TIA.
>> > >> >
>> > >> >Glenn
>> > >>
>> > >> ___________________________________________________________
>> > >>
>> > >> Carson Hager
>> > >> Team Sybase
>> > >> Dynamic Data Solutions, Inc.
>> > >> Enterprise Application Studio 3.0 Consulting and Training
>> > >>
>> > >> DDS Enterprise Application Framework
>> > >> Available Now as Open Source!
>> > >> http://www.dyn-data.com
>> >
>> > ___________________________________________________________
>> >
>> > Carson Hager
>> > Team Sybase
>> > Dynamic Data Solutions, Inc.
>> > Enterprise Application Studio 3.0 Consulting and Training
>> >
>> > DDS Enterprise Application Framework
>> > Available Now as Open Source!
>> > http://www.dyn-data.com
>
>

___________________________________________________________

Carson Hager
Team Sybase
Dynamic Data Solutions, Inc.
Enterprise Application Studio 3.0 Consulting and Training

DDS Enterprise Application Framework
Available Now as Open Source!
http://www.dyn-data.com


Glenn Santa Cruz Posted on 2000-03-28 15:43:05.0Z
Newsgroups: sybase.public.easerver
Date: Tue, 28 Mar 2000 09:43:05 -0600
From: Glenn Santa Cruz <spam?no.glenn_santacruz@dailyaccess.com>
Organization: Daily Access Concepts
X-Mailer: Mozilla 4.7 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: Oracle OCI 7 ; cursors not closing
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 160
NNTP-Posting-Host: 12.6.74.30
Message-ID: <347_38E0D309.EECF28CF@dailyaccess.com>
References: <347_38DFFF99.E3BD0905@dailyaccess.com> <347_38e015b2.94411746@forums.sybase.com> <347_38E00800.D6C10E4F@dailyaccess.com> <347_38e01c71.96139250@forums.sybase.com> <347_38E00DE6.6E8FB558@dailyaccess.com> <347_5mUwnpFm$GA.290@forums.sybase.com> <347_38e0231f.97848678@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:25474
Article PK: 155557

I'll certainly archive this thread for future reference when I start
using JDBC. Due to our in-house PB background and the speed with which
JDBC fetches rows, we've opted to code database components in PB and use
Java for other logic. Of course, this may very well change, as long as
Dave keeps posting handy Java tips.

Thanks

Glenn

"Carson Hager[Team Sybase]" wrote:
>
> Totally forgot to mention the Statement/PreparedStatement part...
>
> Carson
>
> ___________________________________________________________
>
> Carson Hager
> Team Sybase
> Dynamic Data Solutions, Inc.
> Enterprise Application Studio 3.0 Consulting and Training
> http://www.dyn-data.com
>
> DDS is now hiring EAServer consultants
> to support its exploding EAServer business!
> Please submit your resume to
> hr@dyn-data.com!
>
> On Mon, 27 Mar 2000 21:03:03 -0500, "Dave Wolf [Sybase]"
> <dwolf@sybase.com> wrote:
>
> >You should dig into that. The Oracle JDBC driver is very touchy and a bit
> >odd about ResultSet.close() and Statement.close(). Statement.close() should
> >close the ResultSet butttt its seems the JDBC driver is very touchy about
> >that. And sometimes when you do get this to work, then also close the
> >ResultSet it throws a SQLException, but not others. For a few benchmarks
> >this drove me batty as it makes Oracle run out of available statements very
> >fast. I cant remember the specifics but I had to be very very anal about
> >how I closed everything up.
> >
> >Dave Wolf
> >Internet Applications Division
> >
> >"Glenn Santa Cruz" <spam?no.glenn_santacruz@dailyaccess.com> wrote in
> >message news:38E00DE6.6E8FB558@dailyaccess.com...
> >> Well, now that you mention it, there *is* a bit of java in the mix, but
> >> it resides only as a non-transactional service component, making an
> >> intercomponent call to a transactional PB component. I'll attempt to
> >> call the PB component directly from the client tomorrow morning, to see
> >> if that changes anything.
> >>
> >> Thanks
> >>
> >> Glenn
> >>
> >> "Carson Hager[Team Sybase]" wrote:
> >> >
> >> > The only time I've seen this in Jag has been when I forgot to close a
> >> > ResultSet in java. This should be handled by EAServer/PBVM.
> >> >
> >> > Carson
> >> >
> >> > ___________________________________________________________
> >> >
> >> > Carson Hager
> >> > Team Sybase
> >> > Dynamic Data Solutions, Inc.
> >> > Enterprise Application Studio 3.0 Consulting and Training
> >> > http://www.dyn-data.com
> >> >
> >> > DDS is now hiring EAServer consultants
> >> > to support its exploding EAServer business!
> >> > Please submit your resume to
> >> > hr@dyn-data.com!
> >> >
> >> > On Mon, 27 Mar 2000 19:16:48 -0600, Glenn Santa Cruz
> >> > <spam?no.glenn_santacruz@dailyaccess.com> wrote:
> >> >
> >> > >I've tried both ways to no avail. Out on a limb here, but do you know
> >> > >offhand if there may be a registry entry that the OCI dll uses to
> >> > >determine whether or not to close cursors? I'm about to search technet
> >> > >for advice; if I find anything, I'll be sure to post it.
> >> > >
> >> > >Glenn
> >> > >
> >> > >
> >> > >"Carson Hager[Team Sybase]" wrote:
> >> > >>
> >> > >> They should definitely be closed. Is this using embedded SQL or
> >> > >> datastorers?
> >> > >>
> >> > >> Carson
> >> > >>
> >> > >> ___________________________________________________________
> >> > >>
> >> > >> Carson Hager
> >> > >> Team Sybase
> >> > >> Dynamic Data Solutions, Inc.
> >> > >> Enterprise Application Studio 3.0 Consulting and Training
> >> > >> http://www.dyn-data.com
> >> > >>
> >> > >> DDS is now hiring EAServer consultants
> >> > >> to support its exploding EAServer business!
> >> > >> Please submit your resume to
> >> > >> hr@dyn-data.com!
> >> > >>
> >> > >> On Mon, 27 Mar 2000 18:40:57 -0600, Glenn Santa Cruz
> >> > >> <spam?no.glenn_santacruz@dailyaccess.com> wrote:
> >> > >>
> >> > >> >Jaguar 3.01, build 30033
> >> > >> >PB 7.01, build 7021
> >> > >> >OCI 7.x cache
> >> > >> >ociw32.dll version 8.0.4.0.0
> >> > >> >
> >> > >> >I have a standard, transactional, poolable PB component that
> >performs
> >> > >> >both inserts and updates to an Oracle 7.3.4 database; transactions
> >are
> >> > >> >definitely being committed or rolled back as designed. However,
> >cursors
> >> > >> >are not being closed (verified via V$OPEN_CURSOR) at transaction
> >> > >> >boundaries.
> >> > >> >
> >> > >> >Anyone know of configurable settings (for Jaguar) to close open
> >cursors
> >> > >> >on a commit or rollback? Note that this behavior has not been seen
> >when
> >> > >> >using traditional 2-tier PB applications, presumably because they
> >use a
> >> > >> >different driver for connection.
> >> > >> >
> >> > >> >Major TIA.
> >> > >> >
> >> > >> >Glenn
> >> > >>
> >> > >> ___________________________________________________________
> >> > >>
> >> > >> Carson Hager
> >> > >> Team Sybase
> >> > >> Dynamic Data Solutions, Inc.
> >> > >> Enterprise Application Studio 3.0 Consulting and Training
> >> > >>
> >> > >> DDS Enterprise Application Framework
> >> > >> Available Now as Open Source!
> >> > >> http://www.dyn-data.com
> >> >
> >> > ___________________________________________________________
> >> >
> >> > Carson Hager
> >> > Team Sybase
> >> > Dynamic Data Solutions, Inc.
> >> > Enterprise Application Studio 3.0 Consulting and Training
> >> >
> >> > DDS Enterprise Application Framework
> >> > Available Now as Open Source!
> >> > http://www.dyn-data.com
> >
> >
>
> ___________________________________________________________
>
> Carson Hager
> Team Sybase
> Dynamic Data Solutions, Inc.
> Enterprise Application Studio 3.0 Consulting and Training
>
> DDS Enterprise Application Framework
> Available Now as Open Source!
> http://www.dyn-data.com