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.

Error in Jaguar log

7 posts in General Discussion (old) Last posting was on 2000-03-08 14:57:32.0Z
Jeff Strike Posted on 2000-03-03 21:10:24.0Z
Newsgroups: sybase.public.easerver
From: Jeff Strike <jstrike@wje.com>
Subject: Error in Jaguar log
Date: Fri, 03 Mar 2000 15:10:24 -0600
Reply-To: jstrike@wje.com
X-Newsreader: Forte Agent 1.7/32.534
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 14
NNTP-Posting-Host: wjetelnet.wje.com 12.27.23.134
Message-ID: <347_p8a0cs034efj6m7vd1gd3js6foqi9k490f@4ax.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:27186
Article PK: 158103

I have a single PB7 application using Jaguar 3.0.1 that has about 100
users connected at the same time. At least once a day I get the
following error message:
cm__odbc_error: SQLError: 0, SQLState: S1000, [Microsoft][ODBC SQL
Server Driver]Connection is busy with results for another hstmt.

When this shows up, no one else can get into the program and I have to
either stop and restart the service or go into Jaguar manager and
refresh the server. What causes this and what can I do to get rid of
it?

Thanks,
-Jeff


Larry Cermak[Team Sybase] Posted on 2000-03-03 23:11:32.0Z
Newsgroups: sybase.public.easerver
From: "Larry Cermak[Team Sybase]" <lcermak@ctpartners.com>
Subject: Re: Error in Jaguar log
Date: Fri, 3 Mar 2000 17:11:32 -0600
Lines: 29
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: node6.dhcpchi.dslspeed.zyan.com 208.41.199.6
Message-ID: <347_J91LBcWh$GA.251@forums.sybase.com>
References: <347_p8a0cs034efj6m7vd1gd3js6foqi9k490f@4ax.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:27173
Article PK: 158090

I've seen this several times at a client site and have not found a cause.
You are using MS SQL, right? I think the driver is getting hosed. Could
you be hitting a user limit of connections to the database?

--

Larry Cermak [Team Sybase]
Corporate Technology Partners, Inc.
www.ctpartners.com
Web DataWindow Articles
(http://sdn.sybase.com/sdn/appdev/get_doc.stm?loc=1001708)

"Jeff Strike" <jstrike@wje.com> wrote in message
news:p8a0cs034efj6m7vd1gd3js6foqi9k490f@4ax.com...
> I have a single PB7 application using Jaguar 3.0.1 that has about 100
> users connected at the same time. At least once a day I get the
> following error message:
> cm__odbc_error: SQLError: 0, SQLState: S1000, [Microsoft][ODBC SQL
> Server Driver]Connection is busy with results for another hstmt.
>
> When this shows up, no one else can get into the program and I have to
> either stop and restart the service or go into Jaguar manager and
> refresh the server. What causes this and what can I do to get rid of
> it?
>
> Thanks,
> -Jeff


Jeff Strike Posted on 2000-03-05 00:40:06.0Z
Newsgroups: sybase.public.easerver
From: Jeff Strike <jstrike@execpc.com>
Subject: Re: Error in Jaguar log
Date: Sat, 04 Mar 2000 18:40:06 -0600
X-Newsreader: Forte Agent 1.7/32.534
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 24
NNTP-Posting-Host: lianna-1-138.mdm.prk.execpc.com 169.207.209.140
Message-ID: <347_kta3cs8bpllqgcv11mk67hha236s5u3mbi@4ax.com>
References: <347_p8a0cs034efj6m7vd1gd3js6foqi9k490f@4ax.com> <347_J91LBcWh$GA.251@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:27152
Article PK: 158075

Yes, MS SQL 7.01. The database should allow unlimited connections. I
had thought that I didn't have enough connections setup in the
connection cache so I bumped it up from 50 to 75. I still get the
message. Is there anyway I can tell how many people are connected to
Jaguar at once, what about the max number of people using the database
connection? One of the stored procedures is somewhat complex. It
calls 2-3 other stored procs and involves 3 sizable temporary tables.
I'm wondering if that's not helping matters any.

I'll call Sybase and open an issue on it.

Thanks,
-Jeff

On Fri, 3 Mar 2000 17:11:32 -0600, "Larry Cermak[Team Sybase]"

<lcermak@ctpartners.com> wrote:

>I've seen this several times at a client site and have not found a cause.
>You are using MS SQL, right? I think the driver is getting hosed. Could
>you be hitting a user limit of connections to the database?


Jim O'Neil [Sybase] Posted on 2000-03-05 02:43:29.0Z
Newsgroups: sybase.public.easerver
Date: Sat, 04 Mar 2000 21:43:29 -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: Error in Jaguar log
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 35
NNTP-Posting-Host: nomad6-18.sybase.com 157.133.176.18
Message-ID: <347_38C1C9D0.34F410CF@sybase.com>
References: <347_p8a0cs034efj6m7vd1gd3js6foqi9k490f@4ax.com> <347_J91LBcWh$GA.251@forums.sybase.com> <347_kta3cs8bpllqgcv11mk67hha236s5u3mbi@4ax.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:27150
Article PK: 158070


Jeff Strike wrote:

> Yes, MS SQL 7.01. The database should allow unlimited connections. I
> had thought that I didn't have enough connections setup in the
> connection cache so I bumped it up from 50 to 75. I still get the
> message. Is there anyway I can tell how many people are connected to
> Jaguar at once, what about the max number of people using the database
> connection? One of the stored procedures is somewhat complex. It
> calls 2-3 other stored procs and involves 3 sizable temporary tables.
> I'm wondering if that's not helping matters any.
>
> I'll call Sybase and open an issue on it.
>
> Thanks,
> -Jeff
>
> On Fri, 3 Mar 2000 17:11:32 -0600, "Larry Cermak[Team Sybase]"
> <lcermak@ctpartners.com> wrote:
>
> >I've seen this several times at a client site and have not found a cause.
> >You are using MS SQL, right? I think the driver is getting hosed. Could
> >you be hitting a user limit of connections to the database?

The ODBC error would actually indicate that you are doing something like
opening cursor and fetching a result set and then trying to issue another SQL
statement while that cursor is still open. Given the complexity of the stored
procedure can you verify that it works with a single user from, say, MSQuery.
--
Jim O'Neil
Senior Technical Support Engineer
Sybase, Inc


Jeff Strike Posted on 2000-03-06 19:48:59.0Z
Newsgroups: sybase.public.easerver
From: Jeff Strike <jstrike@wje.com>
Subject: Re: Error in Jaguar log
Date: Mon, 06 Mar 2000 13:48:59 -0600
Reply-To: jstrike@wje.com
X-Newsreader: Forte Agent 1.7/32.534
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 76
NNTP-Posting-Host: wjetelnet.wje.com 12.27.23.134
Message-ID: <347_6rv7cschqvn5mdkh35iri8umfa3fdsbma5@4ax.com>
References: <347_p8a0cs034efj6m7vd1gd3js6foqi9k490f@4ax.com> <347_J91LBcWh$GA.251@forums.sybase.com> <347_kta3cs8bpllqgcv11mk67hha236s5u3mbi@4ax.com> <347_38C1C9D0.34F410CF@sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:27067
Article PK: 158002

On Sat, 04 Mar 2000 21:43:29 -0500, "Jim O'Neil [Sybase]"

<joneil@sybase.com> wrote:

>Jeff Strike wrote:
>
>> Yes, MS SQL 7.01. The database should allow unlimited connections. I
>> had thought that I didn't have enough connections setup in the
>> connection cache so I bumped it up from 50 to 75. I still get the
>> message. Is there anyway I can tell how many people are connected to
>> Jaguar at once, what about the max number of people using the database
>> connection? One of the stored procedures is somewhat complex. It
>> calls 2-3 other stored procs and involves 3 sizable temporary tables.
>> I'm wondering if that's not helping matters any.
>>
>> I'll call Sybase and open an issue on it.
>>
>> Thanks,
>> -Jeff
>>
>> On Fri, 3 Mar 2000 17:11:32 -0600, "Larry Cermak[Team Sybase]"
>> <lcermak@ctpartners.com> wrote:
>>
>> >I've seen this several times at a client site and have not found a cause.
>> >You are using MS SQL, right? I think the driver is getting hosed. Could
>> >you be hitting a user limit of connections to the database?
>
>The ODBC error would actually indicate that you are doing something like
>opening cursor and fetching a result set and then trying to issue another SQL
>statement while that cursor is still open. Given the complexity of the stored
>procedure can you verify that it works with a single user from, say, MSQuery.

There are no cursors in what I'm doing unless Jaguar is treating a
composite dw that has a group dw containing 4 nested reports as a
cursor. The entire procedure works fine by itself. The group dw and
all the nested datawindows all call stored procs, those procs in turn
call other procs. This is a breakdown of the dw's nested in the group
dw and stored procs they call:

dw_prebill_group (group dw)
Calls stored proc: ps_prebill_billinggroups
(That stored procdure returns a single column that all nested reports
listed below use as their retrieval argument)
dw_cumminq_summary (Header band)
1. Calls: ps_cumminq
2. Calls: ps_prebill_summary_exp
3. Calls ps_prebill_calc_exp
2. Calls: ps_prebill_summary_fee
3. Calls ps_prebill_calc_fee
dw_prebill_summary (Detail band)
1. Calls: ps_prebill_summary
2. Calls: ps_prebill_summary_exp
3. Calls ps_prebill_calc_exp
2. Calls: ps_prebill_summary_fee
3. Calls ps_prebill_calc_fee
dw_prebill_detail_fee (Detail band)
1. Calls: ps_prebill_detail_fee
2. Calls: ps_prebill_calc_fee

dw_prebill_detail_exp (Detail band)
1. Calls: ps_prebill_detail_exp
2. Calls: ps_prebill_calc_exp

This is for what we call our Prebill. Basically a list of fees and
expenses broken down and displayed in different ways.
The only potential problem I see is that there's 1 stored procedure
for the fees calculations and 1 for the expenses that that are shared
across the other stored procs. They all use temp tables. Normally I
wouldn't think this would be a problem, now I'm not so sure.

-Jeff


Larry Cermak[Team Sybase] Posted on 2000-03-07 03:06:25.0Z
Newsgroups: sybase.public.easerver
From: "Larry Cermak[Team Sybase]" <lcermak@ctpartners.com>
Subject: Re: Error in Jaguar log
Date: Mon, 6 Mar 2000 21:06:25 -0600
Lines: 91
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: node6.dhcpchi.dslspeed.zyan.com 208.41.199.6
Message-ID: <347_LzqgXN#h$GA.201@forums.sybase.com>
References: <347_p8a0cs034efj6m7vd1gd3js6foqi9k490f@4ax.com> <347_J91LBcWh$GA.251@forums.sybase.com> <347_kta3cs8bpllqgcv11mk67hha236s5u3mbi@4ax.com> <347_38C1C9D0.34F410CF@sybase.com> <347_6rv7cschqvn5mdkh35iri8umfa3fdsbma5@4ax.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:27011
Article PK: 157951

Just a guess, but I bet the nested dws are firing when the transaction is
complete. Try altering the transaction setting for the component to
requires new transaction and see what happens.

--

Larry Cermak [Team Sybase]
Corporate Technology Partners, Inc.
www.ctpartners.com
Web DataWindow Articles
(http://sdn.sybase.com/sdn/appdev/get_doc.stm?loc=1001708)

"Jeff Strike" <jstrike@wje.com> wrote in message
news:6rv7cschqvn5mdkh35iri8umfa3fdsbma5@4ax.com...
> On Sat, 04 Mar 2000 21:43:29 -0500, "Jim O'Neil [Sybase]"
> <joneil@sybase.com> wrote:
>
> >Jeff Strike wrote:
> >
> >> Yes, MS SQL 7.01. The database should allow unlimited connections. I
> >> had thought that I didn't have enough connections setup in the
> >> connection cache so I bumped it up from 50 to 75. I still get the
> >> message. Is there anyway I can tell how many people are connected to
> >> Jaguar at once, what about the max number of people using the database
> >> connection? One of the stored procedures is somewhat complex. It
> >> calls 2-3 other stored procs and involves 3 sizable temporary tables.
> >> I'm wondering if that's not helping matters any.
> >>
> >> I'll call Sybase and open an issue on it.
> >>
> >> Thanks,
> >> -Jeff
> >>
> >> On Fri, 3 Mar 2000 17:11:32 -0600, "Larry Cermak[Team Sybase]"
> >> <lcermak@ctpartners.com> wrote:
> >>
> >> >I've seen this several times at a client site and have not found a
cause.
> >> >You are using MS SQL, right? I think the driver is getting hosed.
Could
> >> >you be hitting a user limit of connections to the database?
> >
> >The ODBC error would actually indicate that you are doing something like
> >opening cursor and fetching a result set and then trying to issue another
SQL
> >statement while that cursor is still open. Given the complexity of the
stored
> >procedure can you verify that it works with a single user from, say,
MSQuery.
>
> There are no cursors in what I'm doing unless Jaguar is treating a
> composite dw that has a group dw containing 4 nested reports as a
> cursor. The entire procedure works fine by itself. The group dw and
> all the nested datawindows all call stored procs, those procs in turn
> call other procs. This is a breakdown of the dw's nested in the group
> dw and stored procs they call:
>
> dw_prebill_group (group dw)
> Calls stored proc: ps_prebill_billinggroups
> (That stored procdure returns a single column that all nested reports
> listed below use as their retrieval argument)
> dw_cumminq_summary (Header band)
> 1. Calls: ps_cumminq
> 2. Calls: ps_prebill_summary_exp
> 3. Calls ps_prebill_calc_exp
> 2. Calls: ps_prebill_summary_fee
> 3. Calls ps_prebill_calc_fee
> dw_prebill_summary (Detail band)
> 1. Calls: ps_prebill_summary
> 2. Calls: ps_prebill_summary_exp
> 3. Calls ps_prebill_calc_exp
> 2. Calls: ps_prebill_summary_fee
> 3. Calls ps_prebill_calc_fee
> dw_prebill_detail_fee (Detail band)
> 1. Calls: ps_prebill_detail_fee
> 2. Calls: ps_prebill_calc_fee
>
> dw_prebill_detail_exp (Detail band)
> 1. Calls: ps_prebill_detail_exp
> 2. Calls: ps_prebill_calc_exp
>
> This is for what we call our Prebill. Basically a list of fees and
> expenses broken down and displayed in different ways.
> The only potential problem I see is that there's 1 stored procedure
> for the fees calculations and 1 for the expenses that that are shared
> across the other stored procs. They all use temp tables. Normally I
> wouldn't think this would be a problem, now I'm not so sure.
>
> -Jeff


Jeff Strike Posted on 2000-03-08 14:57:32.0Z
Newsgroups: sybase.public.easerver
From: Jeff Strike <jstrike@wje.com>
Subject: Re: Error in Jaguar log
Date: Wed, 08 Mar 2000 08:57:32 -0600
Reply-To: jstrike@wje.com
X-Newsreader: Forte Agent 1.7/32.534
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 14
NNTP-Posting-Host: wukkar-2-69.mdm.prk.execpc.com 169.207.211.197
Message-ID: <347_dgqccsg648c8e7st4f0p8pctdmod1ftq9l@4ax.com>
References: <347_p8a0cs034efj6m7vd1gd3js6foqi9k490f@4ax.com> <347_J91LBcWh$GA.251@forums.sybase.com> <347_kta3cs8bpllqgcv11mk67hha236s5u3mbi@4ax.com> <347_38C1C9D0.34F410CF@sybase.com> <347_6rv7cschqvn5mdkh35iri8umfa3fdsbma5@4ax.com> <347_LzqgXN#h$GA.201@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:26895
Article PK: 157853

It was set to transaction not required since this is just a search and
report tool. The only updating is taking place on SQL Server and
that's just temp tables. Do I need it for that? I'll change it and
see what happens.

-Jeff

On Mon, 6 Mar 2000 21:06:25 -0600, "Larry Cermak[Team Sybase]"

<lcermak@ctpartners.com> wrote:

>Just a guess, but I bet the nested dws are firing when the transaction is
>complete. Try altering the transaction setting for the component to
>requires new transaction and see what happens.