Sybase NNTP forums - End Of Life (EOL)

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

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

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

Sybase ASE - silently dies mid procedure

5 posts in General Discussion Last posting was on 2011-06-01 04:25:25.0Z
Simon Scott Posted on 2011-05-31 05:55:29.0Z
Sender: e8b.4de480e5.1804289383@sybase.com
From: Simon Scott
Newsgroups: sybase.public.ase.general
Subject: Sybase ASE - silently dies mid procedure
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4de482d1.ec3.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 30 May 2011 22:55:29 -0700
X-Trace: forums-1-dub 1306821329 10.22.241.41 (30 May 2011 22:55:29 -0700)
X-Original-Trace: 30 May 2011 22:55:29 -0700, 10.22.241.41
Lines: 25
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:30202
Article PK: 72381

Hi all

Adaptive Server Enterprise/15.0.3/EBF 16549
ESD#1/P/x86_64/Enterprise Linux/ase1503/2681/64-bit/FBO/Mon
Mar 9 04:10:47 2009

Really strange one this..... we have a proc (which works
flawlessly in several other environments) which fails
*silently* sometimes. It doesnt give an error, nor leave
anything in the log - putting print statements everywhere
shows that it literally just returns mid-proc, during/before
a simple insert statement.

It *did* crash the whole database at some point, leaving an
error in the log concerning stack size, so we upped the
stack size (96k!) and recompiled and it still fails... but
at least it doesnt crash the database.

Has anyone witnessed silently failing procedures before?
Especially with 12.5.4 compatibility flag (which we have
switched on for various reasons).

HELP!!!! :)

thanks


Rob V [ Sybase ] Posted on 2011-05-31 07:41:03.0Z
From: "Rob V [ Sybase ]" <rob@DO.NOT.SPAM.sypron.nl.REMOVE.THIS.DECOY>
Reply-To: rob@DO.NOT.SPAM.sypron.nl.REMOVE.THIS.DECOY
Organization: Sypron BV / TeamSybase / Sybase
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
Newsgroups: sybase.public.ase.general
Subject: Re: Sybase ASE - silently dies mid procedure
References: <4de482d1.ec3.1681692777@sybase.com>
In-Reply-To: <4de482d1.ec3.1681692777@sybase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4de49b8f$1@forums-1-dub>
Date: 31 May 2011 00:41:03 -0700
X-Trace: forums-1-dub 1306827663 10.22.241.152 (31 May 2011 00:41:03 -0700)
X-Original-Trace: 31 May 2011 00:41:03 -0700, vip152.sybase.com
Lines: 48
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:30203
Article PK: 72382


On 31-May-2011 07:55, Simon Scott wrote:
> Hi all
>
> Adaptive Server Enterprise/15.0.3/EBF 16549
> ESD#1/P/x86_64/Enterprise Linux/ase1503/2681/64-bit/FBO/Mon
> Mar 9 04:10:47 2009
>
> Really strange one this..... we have a proc (which works
> flawlessly in several other environments) which fails
> *silently* sometimes. It doesnt give an error, nor leave
> anything in the log - putting print statements everywhere
> shows that it literally just returns mid-proc, during/before
> a simple insert statement.
>
> It *did* crash the whole database at some point, leaving an
> error in the log concerning stack size, so we upped the
> stack size (96k!) and recompiled and it still fails... but
> at least it doesnt crash the database.
>
> Has anyone witnessed silently failing procedures before?
> Especially with 12.5.4 compatibility flag (which we have
> switched on for various reasons).
>
> HELP!!!! :)
>
> thanks

I haven't seen this before. As you may have guessed, you ought to open
case with Sybase TechSupport.

HTH,

Rob V.
-----------------------------------------------------------------
Rob Verschoor

Certified Sybase Professional DBA for ASE 15.0/12.5/12.0/11.5/11.0
and Replication Server 15.0.1/12.5 // TeamSybase

Author of Sybase books (order online at www.sypron.nl/shop):
"Tips, Tricks& Recipes for Sybase ASE" (ASE 15 edition)
"The Complete Sybase ASE Quick Reference Guide"
"The Complete Sybase Replication Server Quick Reference Guide"

rob@NO.SPAM.sypron.nl | www.sypron.nl | Twitter: @rob_verschoor
Sypron B.V., The Netherlands | Chamber of Commerce 27138666
-----------------------------------------------------------------


jobless Posted on 2011-05-31 15:02:08.0Z
Sender: 7ece.4de3e494.1804289383@sybase.com
From: jobless
Newsgroups: sybase.public.ase.general
Subject: Re: Sybase ASE - silently dies mid procedure
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4de502f0.1c8c.1681692777@sybase.com>
References: <4de482d1.ec3.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 31 May 2011 08:02:08 -0700
X-Trace: forums-1-dub 1306854128 10.22.241.41 (31 May 2011 08:02:08 -0700)
X-Original-Trace: 31 May 2011 08:02:08 -0700, 10.22.241.41
Lines: 30
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:30204
Article PK: 72383

I would also check if there are any triggers on the tables
the procedure inserts/updates/deletes, sometimes triggers do
play in the 'stack' when you see the proc to be simple and
un-harmly.

> Hi all
>
> Adaptive Server Enterprise/15.0.3/EBF 16549
> ESD#1/P/x86_64/Enterprise
> Linux/ase1503/2681/64-bit/FBO/Mon Mar 9 04:10:47 2009
>
> Really strange one this..... we have a proc (which works
> flawlessly in several other environments) which fails
> *silently* sometimes. It doesnt give an error, nor leave
> anything in the log - putting print statements everywhere
> shows that it literally just returns mid-proc,
> during/before a simple insert statement.
>
> It *did* crash the whole database at some point, leaving
> an error in the log concerning stack size, so we upped the
> stack size (96k!) and recompiled and it still fails... but
> at least it doesnt crash the database.
>
> Has anyone witnessed silently failing procedures before?
> Especially with 12.5.4 compatibility flag (which we have
> switched on for various reasons).
>
> HELP!!!! :)
>
> thanks


Simon Scott Posted on 2011-06-01 04:25:25.0Z
Sender: eeb.4de48482.1804289383@sybase.com
From: Simon Scott
Newsgroups: sybase.public.ase.general
Subject: Re: Sybase ASE - silently dies mid procedure
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4de5bf35.3018.1681692777@sybase.com>
References: <4de502f0.1c8c.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 31 May 2011 21:25:25 -0700
X-Trace: forums-1-dub 1306902325 10.22.241.41 (31 May 2011 21:25:25 -0700)
X-Original-Trace: 31 May 2011 21:25:25 -0700, 10.22.241.41
Lines: 12
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:30209
Article PK: 72388


> I would also check if there are any triggers on the tables
> the procedure inserts/updates/deletes, sometimes triggers
> do play in the 'stack' when you see the proc to be simple
> and un-harmly.

Oh, there are triggers.... I guess that perhaps the trigger
is where the stack was used up and the error was lost?

We got rid of the crashing database by increasing the guard
(logically), and we're now getting an actual error
returned.... it could be that the error doesnt propagate
correctly from a trigger...


J Posted on 2011-05-31 16:32:43.0Z
From: jtotally_bogus@sbcglobal.net (J)
Newsgroups: sybase.public.ase.general
Subject: Re: Sybase ASE - silently dies mid procedure
Reply-To: J@bogusemailAddress.com
Message-ID: <4de5157a.352121093@forums.sybase.com>
References: <4de482d1.ec3.1681692777@sybase.com>
X-Newsreader: Forte Free Agent 1.21/32.243
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Date: 31 May 2011 09:32:43 -0700
X-Trace: forums-1-dub 1306859563 10.22.241.152 (31 May 2011 09:32:43 -0700)
X-Original-Trace: 31 May 2011 09:32:43 -0700, vip152.sybase.com
Lines: 65
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:30205
Article PK: 72384

On 30 May 2011 22:55:29 -0700, Simon Scott wrote:

Check the program which is running the procedure to see if it checks
for unexpected results and if it checks for the stored procedure
"return status". Note: the return status is different from the value
returned from the "return" statement in the procedure.

It can be tricky to get a good "results processing loop" esp. if the
client application is using a jdbc driver.

The return status might give an ASE failure cause which caused the
pre-mature termination of the procedure.

TSQL User's Guide: "Returning information from stored procedures"

e.g.
1> create proc proc_xx as
2> exec someserver...sp_who
3> return 0
4> go
1> select srvname from master..sysservers where srvname = 'someserver'
2> go
srvname
------------------------------

(0 rows affected)
1> proc_xx
2> go
Msg 7218, Level 16, State 3:
Server 'jaylinux_1502', Procedure 'proc_xx', Line 2:
Site 'someserver' not found in sysservers.
(return status = -6)

In this case the client application might be looking for "row results"
and not handle the error messages or the ASE generated (-6) return
status.

Jay

>Hi all
>
>Adaptive Server Enterprise/15.0.3/EBF 16549
>ESD#1/P/x86_64/Enterprise Linux/ase1503/2681/64-bit/FBO/Mon
>Mar 9 04:10:47 2009
>
>Really strange one this..... we have a proc (which works
>flawlessly in several other environments) which fails
>*silently* sometimes. It doesnt give an error, nor leave
>anything in the log - putting print statements everywhere
>shows that it literally just returns mid-proc, during/before
>a simple insert statement.
>
>It *did* crash the whole database at some point, leaving an
>error in the log concerning stack size, so we upped the
>stack size (96k!) and recompiled and it still fails... but
>at least it doesnt crash the database.
>
>Has anyone witnessed silently failing procedures before?
>Especially with 12.5.4 compatibility flag (which we have
>switched on for various reasons).
>
>HELP!!!! :)
>
>thanks