Sybase NNTP forums - End Of Life (EOL)

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

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

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

ASE stack trace with perl scripts

20 posts in General Discussion Last posting was on 2009-10-28 15:21:33.0Z
syb_user Posted on 2009-10-22 16:58:05.0Z
Sender: 4495.4ae08eac.1804289383@sybase.com
From: syb_user
Newsgroups: sybase.public.ase.general
Subject: ASE stack trace with perl scripts
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4ae08f1d.449d.1681692777@sybase.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 22 Oct 2009 09:58:05 -0700
X-Trace: forums-1-dub 1256230685 10.22.241.41 (22 Oct 2009 09:58:05 -0700)
X-Original-Trace: 22 Oct 2009 09:58:05 -0700, 10.22.241.41
Lines: 154
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:28528
Article PK: 77770

Environment::
Sybase ASE 15.0.3 ,ESD#2,
Open Client 15.0 and
DBD::Sybase 1.09

Problem::
Perl scripts causing stack traces on Sybase ASE with error
8203 (2 samples below - several more identical errors/stack
traces)

I am already pursuing this with Sybase Technical Support.
However, am interested to know if any of the DBD::Sybase
users have seen anything similar
since this problem seems to be occurring in our environment
only with perl scripts.




01:00000:00320:2009/10/14 05:13:02.27 server Error: 8203,
Severity: 26, State: 4
01:00000:00320:2009/10/14 05:13:02.27 server Expected to
find the descriptor for object -20971521 in database 2 in
DROP state.
01:00000:00320:2009/10/14 05:13:02.27 kernel
************************************
01:00000:00320:2009/10/14 05:13:02.27 kernel SQL causing
error :
01:00000:00320:2009/10/14 05:13:02.27 kernel
************************************
01:00000:00320:2009/10/14 05:13:02.27 server SQL Text:
01:00000:00320:2009/10/14 05:13:02.27 kernel curdb = 7
tempdb = 4 pstat = 0x10000
01:00000:00320:2009/10/14 05:13:02.27 kernel lasterror =
8203 preverror = 0 transtate = 1
01:00000:00320:2009/10/14 05:13:02.27 kernel curcmd = 311
program = item_enddate_update.pl
01:00000:00320:2009/10/14 05:13:02.27 kernel extended error
information: hostname: servo login: sa
01:00000:00320:2009/10/14 05:13:02.27 kernel pc:
0x0000000001684835 pcstkwalk+0x30()
01:00000:00320:2009/10/14 05:13:02.27 kernel pc:
0x0000000001684629 ucstkgentrace+0x199()
01:00000:00320:2009/10/14 05:13:02.27 kernel pc:
0x000000000163d83e ucbacktrace+0x40()
01:00000:00320:2009/10/14 05:13:02.27 kernel pc:
0x000000000074e6db terminate_process+0xccb()
01:00000:00320:2009/10/14 05:13:02.27 kernel pc:
0x00000000014a6ed6 hdl_default+0x45()
01:00000:00320:2009/10/14 05:13:02.27 kernel pc:
0x0000000000c33592 s_handle+0x5f2()
01:00000:00320:2009/10/14 05:13:02.27 kernel pc:
0x0000000000c54c6e ex_raise+0x21e()
01:00000:00320:2009/10/14 05:13:02.27 kernel pc:
0x0000000000b20713 des__markdestroy+0xc3()
01:00000:00320:2009/10/14 05:13:02.27 kernel pc:
0x0000000000b1ad51 des_objdrop+0x11()
01:00000:00320:2009/10/14 05:13:02.27 kernel pc:
0x000000000153ac65 lwp_drop+0xf7()
01:00000:00320:2009/10/14 05:13:02.27 kernel pc:
0x0000000000c9ba8d dropobject+0x17d()
01:00000:00320:2009/10/14 05:13:02.27 kernel pc:
0x0000000000c25c12 s_execute+0x3772()
01:00000:00320:2009/10/14 05:13:02.27 kernel [Handler pc:
0x0x0000000000c54fc0 hdl_stack installed by the following
function:-]
01:00000:00320:2009/10/14 05:13:02.27 kernel [Handler pc:
0x0x0000000000c32fa0 s_handle installed by the following
function:-]
01:00000:00320:2009/10/14 05:13:02.27 kernel pc:
0x000000000196996e sequencer+0x71e()
01:00000:00320:2009/10/14 05:13:02.27 kernel pc:
0x000000000110789b tdsrecv_dynamic+0x222()
01:00000:00320:2009/10/14 05:13:02.27 kernel [Handler pc:
0x0x0000000000ce0920 ut_handle installed by the following
function:-]
01:00000:00320:2009/10/14 05:13:02.27 kernel pc:
0x0000000001827ba0 conn_hdlr+0x1340()
01:00000:00320:2009/10/14 05:13:02.27 kernel end of stack
trace, spid 320, kpid 823264075, suid 1
01:00000:00320:2009/10/14 05:13:02.27 server Error: 6103,
Severity: 17, State: 1
01:00000:00320:2009/10/14 05:13:02.27 server Unable to do
cleanup for the killed process; received Msg 8203.





01:00000:00616:2009/10/21 22:11:01.79 server Error: 8203,
Severity: 26, State: 4
01:00000:00616:2009/10/21 22:11:01.90 server Expected to
find the descriptor for object -40370178 in database 2 in
DROP state.
01:00000:00616:2009/10/21 22:11:01.90 kernel
************************************
01:00000:00616:2009/10/21 22:11:01.91 kernel SQL causing
error : 
01:00000:00616:2009/10/21 22:11:01.91 kernel
************************************
01:00000:00616:2009/10/21 22:11:01.91 server SQL Text: 
01:00000:00616:2009/10/21 22:11:01.91 kernel curdb = 7
tempdb = 2 pstat = 0x10000
01:00000:00616:2009/10/21 22:11:01.91 kernel lasterror =
8203 preverror = 0 transtate = 1
01:00000:00616:2009/10/21 22:11:01.91 kernel curcmd = 311
program = upload_tf.pl
01:00000:00616:2009/10/21 22:11:01.91 kernel extended error
information: hostname: servo login: report
01:00000:00616:2009/10/21 22:11:02.00 kernel pc:
0x0000000001684835 pcstkwalk+0x30()
01:00000:00616:2009/10/21 22:11:02.00 kernel pc:
0x0000000001684629 ucstkgentrace+0x199()
01:00000:00616:2009/10/21 22:11:02.07 kernel pc:
0x000000000163d83e ucbacktrace+0x40()
01:00000:00616:2009/10/21 22:11:02.07 kernel pc:
0x000000000074e6db terminate_process+0xccb()
01:00000:00616:2009/10/21 22:11:02.07 kernel pc:
0x00000000014a6ed6 hdl_default+0x45()
01:00000:00616:2009/10/21 22:11:02.07 kernel pc:
0x0000000000c33592 s_handle+0x5f2()
01:00000:00616:2009/10/21 22:11:02.07 kernel pc:
0x0000000000c54c6e ex_raise+0x21e()
01:00000:00616:2009/10/21 22:11:02.07 kernel pc:
0x0000000000b20713 des__markdestroy+0xc3()
01:00000:00616:2009/10/21 22:11:02.07 kernel pc:
0x0000000000b1ad51 des_objdrop+0x11()
01:00000:00616:2009/10/21 22:11:02.07 kernel pc:
0x000000000153ac65 lwp_drop+0xf7()
01:00000:00616:2009/10/21 22:11:02.07 kernel pc:
0x0000000000c9ba8d dropobject+0x17d()
01:00000:00616:2009/10/21 22:11:02.07 kernel pc:
0x0000000000c25c12 s_execute+0x3772()
01:00000:00616:2009/10/21 22:11:02.07 kernel [Handler pc:
0x0x0000000000c54fc0 hdl_stack installed by the following
function:-]
01:00000:00616:2009/10/21 22:11:02.07 kernel [Handler pc:
0x0x0000000000c32fa0 s_handle installed by the following
function:-]
01:00000:00616:2009/10/21 22:11:02.07 kernel pc:
0x000000000196996e sequencer+0x71e()
01:00000:00616:2009/10/21 22:11:02.07 kernel pc:
0x000000000110789b tdsrecv_dynamic+0x222()
01:00000:00616:2009/10/21 22:11:02.07 kernel [Handler pc:
0x0x0000000000ce0920 ut_handle installed by the following
function:-]
01:00000:00616:2009/10/21 22:11:02.07 kernel pc:
0x0000000001827ba0 conn_hdlr+0x1340()
01:00000:00616:2009/10/21 22:11:02.07 kernel end of stack
trace, spid 616, kpid 1558971316, suid 179
01:00000:00616:2009/10/21 22:11:02.07 server Error: 6103,
Severity: 17, State: 1
01:00000:00616:2009/10/21 22:11:02.07 server Unable to do
cleanup for the killed process; received Msg 8203.


J Posted on 2009-10-22 17:36:22.0Z
From: jtotally_bogus@sbcglobal.net (J)
Newsgroups: sybase.public.ase.general
Subject: Re: ASE stack trace with perl scripts
Reply-To: J@bogusemailAddress.com
Message-ID: <4ae097dc.7578377@forums.sybase.com>
References: <4ae08f1d.449d.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: 22 Oct 2009 10:36:22 -0700
X-Trace: forums-1-dub 1256232982 10.22.241.152 (22 Oct 2009 10:36:22 -0700)
X-Original-Trace: 22 Oct 2009 10:36:22 -0700, vip152.sybase.com
Lines: 162
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:28529
Article PK: 77771

On 22 Oct 2009 09:58:05 -0700, syb_user wrote:

I dont' know what the problem is but I would suggest getting a Ribo
trace between this client and the ASE to see the sql/tds that causes
the problem. I think support will need this.

Jay

>Environment::
>Sybase ASE 15.0.3 ,ESD#2,
>Open Client 15.0 and
>DBD::Sybase 1.09
>
>Problem::
>Perl scripts causing stack traces on Sybase ASE with error
>8203 (2 samples below - several more identical errors/stack
>traces)
>
>I am already pursuing this with Sybase Technical Support.
>However, am interested to know if any of the DBD::Sybase
>users have seen anything similar
>since this problem seems to be occurring in our environment
>only with perl scripts.
>
>
>
>
>01:00000:00320:2009/10/14 05:13:02.27 server Error: 8203,
>Severity: 26, State: 4
>01:00000:00320:2009/10/14 05:13:02.27 server Expected to
>find the descriptor for object -20971521 in database 2 in
>DROP state.
>01:00000:00320:2009/10/14 05:13:02.27 kernel
>************************************
>01:00000:00320:2009/10/14 05:13:02.27 kernel SQL causing
>error :
>01:00000:00320:2009/10/14 05:13:02.27 kernel
>************************************
>01:00000:00320:2009/10/14 05:13:02.27 server SQL Text:
>01:00000:00320:2009/10/14 05:13:02.27 kernel curdb =3d 7
>tempdb =3d 4 pstat =3d 0x10000
>01:00000:00320:2009/10/14 05:13:02.27 kernel lasterror =3d
>8203 preverror =3d 0 transtate =3d 1
>01:00000:00320:2009/10/14 05:13:02.27 kernel curcmd =3d 311
>program =3d item_enddate_update.pl
>01:00000:00320:2009/10/14 05:13:02.27 kernel extended error
>information: hostname: servo login: sa
>01:00000:00320:2009/10/14 05:13:02.27 kernel pc:
>0x0000000001684835 pcstkwalk+0x30()
>01:00000:00320:2009/10/14 05:13:02.27 kernel pc:
>0x0000000001684629 ucstkgentrace+0x199()
>01:00000:00320:2009/10/14 05:13:02.27 kernel pc:
>0x000000000163d83e ucbacktrace+0x40()
>01:00000:00320:2009/10/14 05:13:02.27 kernel pc:
>0x000000000074e6db terminate_process+0xccb()
>01:00000:00320:2009/10/14 05:13:02.27 kernel pc:
>0x00000000014a6ed6 hdl_default+0x45()
>01:00000:00320:2009/10/14 05:13:02.27 kernel pc:
>0x0000000000c33592 s_handle+0x5f2()
>01:00000:00320:2009/10/14 05:13:02.27 kernel pc:
>0x0000000000c54c6e ex_raise+0x21e()
>01:00000:00320:2009/10/14 05:13:02.27 kernel pc:
>0x0000000000b20713 des__markdestroy+0xc3()
>01:00000:00320:2009/10/14 05:13:02.27 kernel pc:
>0x0000000000b1ad51 des_objdrop+0x11()
>01:00000:00320:2009/10/14 05:13:02.27 kernel pc:
>0x000000000153ac65 lwp_drop+0xf7()
>01:00000:00320:2009/10/14 05:13:02.27 kernel pc:
>0x0000000000c9ba8d dropobject+0x17d()
>01:00000:00320:2009/10/14 05:13:02.27 kernel pc:
>0x0000000000c25c12 s_execute+0x3772()
>01:00000:00320:2009/10/14 05:13:02.27 kernel [Handler pc:
>0x0x0000000000c54fc0 hdl_stack installed by the following
>function:-]
>01:00000:00320:2009/10/14 05:13:02.27 kernel [Handler pc:
>0x0x0000000000c32fa0 s_handle installed by the following
>function:-]
>01:00000:00320:2009/10/14 05:13:02.27 kernel pc:
>0x000000000196996e sequencer+0x71e()
>01:00000:00320:2009/10/14 05:13:02.27 kernel pc:
>0x000000000110789b tdsrecv_dynamic+0x222()
>01:00000:00320:2009/10/14 05:13:02.27 kernel [Handler pc:
>0x0x0000000000ce0920 ut_handle installed by the following
>function:-]
>01:00000:00320:2009/10/14 05:13:02.27 kernel pc:
>0x0000000001827ba0 conn_hdlr+0x1340()
>01:00000:00320:2009/10/14 05:13:02.27 kernel end of stack
>trace, spid 320, kpid 823264075, suid 1
>01:00000:00320:2009/10/14 05:13:02.27 server Error: 6103,
>Severity: 17, State: 1
>01:00000:00320:2009/10/14 05:13:02.27 server Unable to do
>cleanup for the killed process; received Msg 8203.
>
>
>
>
>
>01:00000:00616:2009/10/21 22:11:01.79 server Error: 8203,
>Severity: 26, State: 4
>01:00000:00616:2009/10/21 22:11:01.90 server Expected to
>find the descriptor for object -40370178 in database 2 in
>DROP state.
>01:00000:00616:2009/10/21 22:11:01.90 kernel
>************************************
>01:00000:00616:2009/10/21 22:11:01.91 kernel SQL causing
>error : =0e
>01:00000:00616:2009/10/21 22:11:01.91 kernel
>************************************
>01:00000:00616:2009/10/21 22:11:01.91 server SQL Text: =0e
>01:00000:00616:2009/10/21 22:11:01.91 kernel curdb =3d 7
>tempdb =3d 2 pstat =3d 0x10000
>01:00000:00616:2009/10/21 22:11:01.91 kernel lasterror =3d
>8203 preverror =3d 0 transtate =3d 1
>01:00000:00616:2009/10/21 22:11:01.91 kernel curcmd =3d 311
>program =3d upload_tf.pl
>01:00000:00616:2009/10/21 22:11:01.91 kernel extended error
>information: hostname: servo login: report
>01:00000:00616:2009/10/21 22:11:02.00 kernel pc:
>0x0000000001684835 pcstkwalk+0x30()
>01:00000:00616:2009/10/21 22:11:02.00 kernel pc:
>0x0000000001684629 ucstkgentrace+0x199()
>01:00000:00616:2009/10/21 22:11:02.07 kernel pc:
>0x000000000163d83e ucbacktrace+0x40()
>01:00000:00616:2009/10/21 22:11:02.07 kernel pc:
>0x000000000074e6db terminate_process+0xccb()
>01:00000:00616:2009/10/21 22:11:02.07 kernel pc:
>0x00000000014a6ed6 hdl_default+0x45()
>01:00000:00616:2009/10/21 22:11:02.07 kernel pc:
>0x0000000000c33592 s_handle+0x5f2()
>01:00000:00616:2009/10/21 22:11:02.07 kernel pc:
>0x0000000000c54c6e ex_raise+0x21e()
>01:00000:00616:2009/10/21 22:11:02.07 kernel pc:
>0x0000000000b20713 des__markdestroy+0xc3()
>01:00000:00616:2009/10/21 22:11:02.07 kernel pc:
>0x0000000000b1ad51 des_objdrop+0x11()
>01:00000:00616:2009/10/21 22:11:02.07 kernel pc:
>0x000000000153ac65 lwp_drop+0xf7()
>01:00000:00616:2009/10/21 22:11:02.07 kernel pc:
>0x0000000000c9ba8d dropobject+0x17d()
>01:00000:00616:2009/10/21 22:11:02.07 kernel pc:
>0x0000000000c25c12 s_execute+0x3772()
>01:00000:00616:2009/10/21 22:11:02.07 kernel [Handler pc:
>0x0x0000000000c54fc0 hdl_stack installed by the following
>function:-]
>01:00000:00616:2009/10/21 22:11:02.07 kernel [Handler pc:
>0x0x0000000000c32fa0 s_handle installed by the following
>function:-]
>01:00000:00616:2009/10/21 22:11:02.07 kernel pc:
>0x000000000196996e sequencer+0x71e()
>01:00000:00616:2009/10/21 22:11:02.07 kernel pc:
>0x000000000110789b tdsrecv_dynamic+0x222()
>01:00000:00616:2009/10/21 22:11:02.07 kernel [Handler pc:
>0x0x0000000000ce0920 ut_handle installed by the following
>function:-]
>01:00000:00616:2009/10/21 22:11:02.07 kernel pc:
>0x0000000001827ba0 conn_hdlr+0x1340()
>01:00000:00616:2009/10/21 22:11:02.07 kernel end of stack
>trace, spid 616, kpid 1558971316, suid 179
>01:00000:00616:2009/10/21 22:11:02.07 server Error: 6103,
>Severity: 17, State: 1
>01:00000:00616:2009/10/21 22:11:02.07 server Unable to do
>cleanup for the killed process; received Msg 8203.


syb_user Posted on 2009-10-22 19:04:44.0Z
Sender: 4495.4ae08eac.1804289383@sybase.com
From: syb_user
Newsgroups: sybase.public.ase.general
Subject: Re: ASE stack trace with perl scripts
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4ae0accc.4991.1681692777@sybase.com>
References: <4ae08f1d.449d.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 22 Oct 2009 12:04:44 -0700
X-Trace: forums-1-dub 1256238284 10.22.241.41 (22 Oct 2009 12:04:44 -0700)
X-Original-Trace: 22 Oct 2009 12:04:44 -0700, 10.22.241.41
Lines: 25
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:28531
Article PK: 77772

I collected the CSMD as requested by Sybase and received the
following response from Sybase

"Please send me the text for the DBD868 stored procedure.
In the CSMD, it looks like the problem was caused by a drop
of this procedure. However, the PSE can't find any
information about this procedure in the CSMD."

Since these procedures are dynamic sql statements and while
several DBD procedures have been recorded and collected in
our performance warehouse this particular one doesn't show
up, probably because the process was terminated.

(1) Not sure how to isolate the SQL statements when the
failure occurs, but have the DBD procedures from the
successful executions of the perl batch job.
(2) We have applications that use Open Client versions 12.5
and some that use version 15. The perl scripts are using
OCS-15
(3) Not running into any issues with isql
(4) BTW, first ran into this issue in 2008 with 12.5.4. Was
a one time occurrence. Of late, in the last 2 months, the
frequency of this problem has increased and it occurred with
both ASE 15.0.3 esd1 and esd2. Also, with Open Client 12.5
and now with Open Client 15


J Posted on 2009-10-22 21:01:24.0Z
From: jtotally_bogus@sbcglobal.net (J)
Newsgroups: sybase.public.ase.general
Subject: Re: ASE stack trace with perl scripts
Reply-To: J@bogusemailAddress.com
Message-ID: <4ae0c70f.19659879@forums.sybase.com>
References: <4ae08f1d.449d.1681692777@sybase.com> <4ae0accc.4991.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: 22 Oct 2009 14:01:24 -0700
X-Trace: forums-1-dub 1256245284 10.22.241.152 (22 Oct 2009 14:01:24 -0700)
X-Original-Trace: 22 Oct 2009 14:01:24 -0700, vip152.sybase.com
Lines: 38
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:28532
Article PK: 77773

On 22 Oct 2009 12:04:44 -0700, syb_user wrote:

If possible you need to get some idea of what the perl script is doing
at the time that you get the error. It usually a lot easier to do this
by some small diagnostic outputs from the scripts than it is from the
server. Alternatively, you run Ribo across entire client sessions to
capture the complete dialog.

isql will not have the problem because it is not using dynamic sql to
do it work. Once the dialog is better understood the problem might be
isolated from sybperl but this is speculation now.

>I collected the CSMD as requested by Sybase and received the
>following response from Sybase
>
>"Please send me the text for the DBD868 stored procedure.
>In the CSMD, it looks like the problem was caused by a drop
>of this procedure. However, the PSE can't find any
>information about this procedure in the CSMD."
>
>Since these procedures are dynamic sql statements and while
>several DBD procedures have been recorded and collected in
>our performance warehouse this particular one doesn't show
>up, probably because the process was terminated.
>
>(1) Not sure how to isolate the SQL statements when the
>failure occurs, but have the DBD procedures from the
>successful executions of the perl batch job.
>(2) We have applications that use Open Client versions 12.5
>and some that use version 15. The perl scripts are using
>OCS-15
>(3) Not running into any issues with isql
>(4) BTW, first ran into this issue in 2008 with 12.5.4. Was
>a one time occurrence. Of late, in the last 2 months, the
>frequency of this problem has increased and it occurred with
>both ASE 15.0.3 esd1 and esd2. Also, with Open Client 12.5
>and now with Open Client 15


Michael Peppler [Team Sybase] Posted on 2009-10-22 18:07:29.0Z
From: "Michael Peppler [Team Sybase]" <mpeppler@peppler.org>
Organization: Peppler Consulting SARL
Subject: Re: ASE stack trace with perl scripts
User-Agent: Pan/0.14.2 (This is not a psychotic episode. It's a cleansing moment of clarity.)
Message-ID: <pan.2009.10.22.18.07.27.133768@peppler.org>
Newsgroups: sybase.public.ase.general
References: <4ae08f1d.449d.1681692777@sybase.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Date: 22 Oct 2009 11:07:29 -0700
X-Trace: forums-1-dub 1256234849 10.22.241.152 (22 Oct 2009 11:07:29 -0700)
X-Original-Trace: 22 Oct 2009 11:07:29 -0700, vip152.sybase.com
Lines: 32
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:28530
Article PK: 77774


On Thu, 22 Oct 2009 09:58:05 -0700, syb_user wrote:

> Environment::
> Sybase ASE 15.0.3 ,ESD#2,
> Open Client 15.0 and
> DBD::Sybase 1.09
>
> Problem::
> Perl scripts causing stack traces on Sybase ASE with error
> 8203 (2 samples below - several more identical errors/stack
> traces)
>
> I am already pursuing this with Sybase Technical Support.
> However, am interested to know if any of the DBD::Sybase
> users have seen anything similar
> since this problem seems to be occurring in our environment
> only with perl scripts.

DBD::Sybase is only a fairly thin wrapper around Sybase's Client
Library...

Have you been able to isolate the SQL statement(s) that causes
the problem? Also - are the perl scripts using the same OpenClient version
as other applications?
Have you tried to execute the same statements via isql?

(BTW - we use DBD:Sybase against 15.0.3 ESD 2 with no particular problems)

Thanks,

Michael


syb_user Posted on 2009-10-22 21:31:24.0Z
Sender: 4495.4ae08eac.1804289383@sybase.com
From: syb_user
Newsgroups: sybase.public.ase.general
Subject: Re: ASE stack trace with perl scripts
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4ae0cf2c.4e07.1681692777@sybase.com>
References: <4ae08f1d.449d.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 22 Oct 2009 14:31:24 -0700
X-Trace: forums-1-dub 1256247084 10.22.241.41 (22 Oct 2009 14:31:24 -0700)
X-Original-Trace: 22 Oct 2009 14:31:24 -0700, 10.22.241.41
Lines: 5
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:28534
Article PK: 77775

Was able to isolate the SQL from a successful run

DYNAMIC_SQL DBD663: create proc DBD663 as select
rtrim(zip_desc), rtrim(zip_state) from db_name..zip where
substring(zip_code,1,5) = ?


mpeppler@peppler.org [Team Sybase] Posted on 2009-10-23 06:55:41.0Z
From: "mpeppler@peppler.org [Team Sybase]" <michael.peppler@gmail.com>
Newsgroups: sybase.public.ase.general
Subject: Re: ASE stack trace with perl scripts
Date: Thu, 22 Oct 2009 23:55:41 -0700 (PDT)
Organization: http://groups.google.com
Lines: 11
Message-ID: <034cfa04-501c-46d4-9508-a5d8b3c52d29@j9g2000vbp.googlegroups.com>
References: <4ae08f1d.449d.1681692777@sybase.com> <4ae0cf2c.4e07.1681692777@sybase.com>
NNTP-Posting-Host: 170.148.215.156
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Trace: posting.google.com 1256280941 23881 127.0.0.1 (23 Oct 2009 06:55:41 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Fri, 23 Oct 2009 06:55:41 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: j9g2000vbp.googlegroups.com; posting-host=170.148.215.156; posting-account=9rHMzAoAAADtzToS8d2WKVGlkISAvPdk
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3,gzip(gfe),gzip(gfe)
Path: forums-1-dub!forums-master!newssvr.sybase.com!news-sj-1.sprintlink.net!news-peer1.sprintlink.net!nntp1.phx1.gblx.net!nntp.gblx.net!nntp.gblx.net!newsfeed.news2me.com!news.glorb.com!news2.glorb.com!postnews.google.com!j9g2000vbp.googlegroups.com!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:28536
Article PK: 77777


On Oct 22, 11:31 pm, syb_user wrote:
> Was able to isolate the SQL from a successful run
>
> DYNAMIC_SQL DBD663: create proc DBD663 as select
> rtrim(zip_desc), rtrim(zip_state) from db_name..zip where
> substring(zip_code,1,5) = ?

Which is a trivial statement.... Have you checked that the table is
sound (dbcc checktable, etc) ?

Michael


J Posted on 2009-10-27 00:00:58.0Z
From: jtotally_bogus@sbcglobal.net (J)
Newsgroups: sybase.public.ase.general
Subject: Re: ASE stack trace with perl scripts
Reply-To: J@bogusemailAddress.com
Message-ID: <4ae6378d.7511040@forums.sybase.com>
References: <4ae08f1d.449d.1681692777@sybase.com> <4ae0cf2c.4e07.1681692777@sybase.com> <034cfa04-501c-46d4-9508-a5d8b3c52d29@j9g2000vbp.googlegroups.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: 26 Oct 2009 16:00:58 -0800
X-Trace: forums-1-dub 1256601658 10.22.241.152 (26 Oct 2009 16:00:58 -0800)
X-Original-Trace: 26 Oct 2009 16:00:58 -0800, vip152.sybase.com
Lines: 26
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:28551
Article PK: 77793

On Thu, 22 Oct 2009 23:55:41 -0700 (PDT), "mpeppler@peppler.org [Team
Sybase]" <michael.peppler@gmail.com> wrote:

Michael,

If you could look at the TDS that he posted. I don't know why the
BUF_ATTN would have flowed given the tds that we see unless the
application decided not to look at the rows that were sent. Is there
an option setting for this? I am requesting a good flow from a
non-failure to see if the BUF_ATTN and its response has anything to do
with the problem that they later see on the dealloc command.

Jay

>On Oct 22, 11:31=A0pm, syb_user wrote:
>> Was able to isolate the SQL from a successful run
>>
>> DYNAMIC_SQL DBD663: create proc DBD663 as select
>> rtrim(zip_desc), rtrim(zip_state) from db_name..zip where
>> substring(zip_code,1,5) =3D ?
>
>Which is a trivial statement.... Have you checked that the table is
>sound (dbcc checktable, etc) ?
>
>Michael


Michael Peppler [Team Sybase] Posted on 2009-10-27 05:15:41.0Z
From: "Michael Peppler [Team Sybase]" <mpeppler@peppler.org>
Organization: Peppler Consulting SARL
Subject: Re: ASE stack trace with perl scripts
User-Agent: Pan/0.14.2 (This is not a psychotic episode. It's a cleansing moment of clarity.)
Message-ID: <pan.2009.10.27.05.15.40.83661@peppler.org>
Newsgroups: sybase.public.ase.general
References: <4ae08f1d.449d.1681692777@sybase.com> <4ae0cf2c.4e07.1681692777@sybase.com> <034cfa04-501c-46d4-9508-a5d8b3c52d29@j9g2000vbp.googlegroups.com> <4ae6378d.7511040@forums.sybase.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Date: 26 Oct 2009 21:15:41 -0800
X-Trace: forums-1-dub 1256620541 10.22.241.152 (26 Oct 2009 21:15:41 -0800)
X-Original-Trace: 26 Oct 2009 21:15:41 -0800, vip152.sybase.com
Lines: 40
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:28552
Article PK: 77794


On Mon, 26 Oct 2009 16:00:58 -0800, J wrote:

> On Thu, 22 Oct 2009 23:55:41 -0700 (PDT), "mpeppler@peppler.org [Team
> Sybase]" <michael.peppler@gmail.com> wrote:
>
> Michael,
>
> If you could look at the TDS that he posted. I don't know why the
> BUF_ATTN would have flowed given the tds that we see unless the
> application decided not to look at the rows that were sent. Is there
> an option setting for this? I am requesting a good flow from a
> non-failure to see if the BUF_ATTN and its response has anything to do
> with the problem that they later see on the dealloc command.
>

Hmmm...

There might be a situation where a ct_cancel() could be called.

When a statement finishes executing it can in some cases think that there
might be additional results on the line. In that case if the perl code
indicates that the rest of the result set is not wanted (i.e. calling
$sth->finish for example) then a ct_cancel() could be generated.

The original poster could try setting the "flush finish" option:

$sth->{syb_flush_finish} = 1;

This will convert any ct_cancel() calls to a loop that consumes all the
results that might be pending.

The OP could also turn on tracing at the DBD::Sybase level to see what
call are made:

DBI->trace(5);

will turn on some pretty detailed tracing (to stderr).

Michael


J Posted on 2009-10-23 15:45:24.0Z
From: jtotally_bogus@sbcglobal.net (J)
Newsgroups: sybase.public.ase.general
Subject: Re: ASE stack trace with perl scripts
Reply-To: J@bogusemailAddress.com
Message-ID: <4ae1cf47.2689837@forums.sybase.com>
References: <4ae08f1d.449d.1681692777@sybase.com> <4ae0cf2c.4e07.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: 23 Oct 2009 08:45:24 -0700
X-Trace: forums-1-dub 1256312724 10.22.241.152 (23 Oct 2009 08:45:24 -0700)
X-Original-Trace: 23 Oct 2009 08:45:24 -0700, vip152.sybase.com
Lines: 15
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:28538
Article PK: 77781

On 22 Oct 2009 14:31:24 -0700, syb_user wrote:

I would get the Ribo trace of the creation and execution for support.
I would log from the script the value of the parameter when the proc
fails. I would disable statement cache if this is enabled for this
session possibly.

J

>Was able to isolate the SQL from a successful run
>
>DYNAMIC_SQL DBD663: create proc DBD663 as select
>rtrim(zip_desc), rtrim(zip_state) from db_name..zip where
>substring(zip_code,1,5) = ?


J Posted on 2009-10-23 17:49:32.0Z
From: jtotally_bogus@sbcglobal.net (J)
Newsgroups: sybase.public.ase.general
Subject: Re: ASE stack trace with perl scripts
Reply-To: J@bogusemailAddress.com
Message-ID: <4ae1ec8f.10185195@forums.sybase.com>
References: <4ae08f1d.449d.1681692777@sybase.com> <4ae0cf2c.4e07.1681692777@sybase.com> <4ae1cf47.2689837@forums.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: 23 Oct 2009 10:49:32 -0700
X-Trace: forums-1-dub 1256320172 10.22.241.152 (23 Oct 2009 10:49:32 -0700)
X-Original-Trace: 23 Oct 2009 10:49:32 -0700, vip152.sybase.com
Lines: 22
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:28539
Article PK: 77780

On 23 Oct 2009 08:45:24 -0700, jtotally_bogus@sbcglobal.net (J) wrote:

Looking closer at this. What is the case number you have open?

Jay

>On 22 Oct 2009 14:31:24 -0700, syb_user wrote:
>
>I would get the Ribo trace of the creation and execution for support.
>I would log from the script the value of the parameter when the proc
>fails. I would disable statement cache if this is enabled for this
>session possibly.
>
>J
>
>>Was able to isolate the SQL from a successful run
>>
>>DYNAMIC_SQL DBD663: create proc DBD663 as select
>>rtrim(zip_desc), rtrim(zip_state) from db_name..zip where
>>substring(zip_code,1,5) = ?
>


syb_user Posted on 2009-10-23 19:34:13.0Z
Sender: 6ef4.4ae1c48d.1804289383@sybase.com
From: syb_user
Newsgroups: sybase.public.ase.general
Subject: Re: ASE stack trace with perl scripts
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4ae20535.77b2.1681692777@sybase.com>
References: <4ae1ec8f.10185195@forums.sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 23 Oct 2009 12:34:13 -0700
X-Trace: forums-1-dub 1256326453 10.22.241.41 (23 Oct 2009 12:34:13 -0700)
X-Original-Trace: 23 Oct 2009 12:34:13 -0700, 10.22.241.41
Lines: 2
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:28540
Article PK: 77782

11563427


syb_user Posted on 2009-10-23 14:37:28.0Z
Sender: 4495.4ae08eac.1804289383@sybase.com
From: syb_user
Newsgroups: sybase.public.ase.general
Subject: Re: ASE stack trace with perl scripts
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4ae1bfa8.6e4a.1681692777@sybase.com>
References: <4ae08f1d.449d.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 23 Oct 2009 07:37:28 -0700
X-Trace: forums-1-dub 1256308648 10.22.241.41 (23 Oct 2009 07:37:28 -0700)
X-Original-Trace: 23 Oct 2009 07:37:28 -0700, 10.22.241.41
Lines: 6
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:28537
Article PK: 77778

(1) The dbcc checks do not return any errors.
(2) The SQL statement as you noted is fairly innocuous. But
it appears that there are a number of perl jobs that execute
a similar DBD procedure (ie a similar select statement) that
may run concurrently. Looks like a concurrency issue with
multiple DBD connections executing prepared statements.


syb_user Posted on 2009-10-25 16:07:59.0Z
Sender: 6ef4.4ae1c48d.1804289383@sybase.com
From: syb_user
Newsgroups: sybase.public.ase.general
Subject: Re: ASE stack trace with perl scripts
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4ae485ef.7a07.1681692777@sybase.com>
References: <4ae08f1d.449d.1681692777@sybase.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 25 Oct 2009 09:07:59 -0700
X-Trace: forums-1-dub 1256490479 10.22.241.41 (25 Oct 2009 09:07:59 -0700)
X-Original-Trace: 25 Oct 2009 09:07:59 -0700, 10.22.241.41
Lines: 381
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:28546
Article PK: 77788

(1) Errors happened again last night

01:00000:00512:2009/10/24 22:42:01.79 server Error: 8203,
Severity: 26, State: 4
01:00000:00512:2009/10/24 22:42:01.79 server Expected to
find the descriptor for object -33554434 in database 2 in
DROP state.
01:00000:00512:2009/10/24 22:42:01.79 kernel
************************************
01:00000:00512:2009/10/24 22:42:01.79 kernel SQL causing
error : 
01:00000:00512:2009/10/24 22:42:01.79 kernel
************************************
01:00000:00512:2009/10/24 22:42:01.79 server SQL Text: 
01:00000:00512:2009/10/24 22:42:01.79 kernel curdb = 7
tempdb = 2 pstat = 0x10000
01:00000:00512:2009/10/24 22:42:01.79 kernel lasterror =
8203 preverror = 0 transtate = 1
01:00000:00512:2009/10/24 22:42:01.79 kernel curcmd = 311
program = upload_euram.pl
01:00000:00512:2009/10/24 22:42:01.79 kernel extended error
information: hostname: servo login: report
01:00000:00512:2009/10/24 22:42:01.79 kernel pc:
0x0000000001684835 pcstkwalk+0x30()
01:00000:00512:2009/10/24 22:42:01.80 kernel pc:
0x0000000001684629 ucstkgentrace+0x199()
01:00000:00512:2009/10/24 22:42:01.80 kernel pc:
0x000000000163d83e ucbacktrace+0x40()
01:00000:00512:2009/10/24 22:42:01.80 kernel pc:
0x000000000074e6db terminate_process+0xccb()
01:00000:00512:2009/10/24 22:42:01.80 kernel pc:
0x00000000014a6ed6 hdl_default+0x45()
01:00000:00512:2009/10/24 22:42:01.80 kernel pc:
0x0000000000c33592 s_handle+0x5f2()
01:00000:00512:2009/10/24 22:42:01.80 kernel pc:
0x0000000000c54c6e ex_raise+0x21e()
01:00000:00512:2009/10/24 22:42:01.80 kernel pc:
0x0000000000b20713 des__markdestroy+0xc3()
01:00000:00512:2009/10/24 22:42:01.80 kernel pc:
0x0000000000b1ad51 des_objdrop+0x11()
01:00000:00512:2009/10/24 22:42:01.80 kernel pc:
0x000000000153ac65 lwp_drop+0xf7()
01:00000:00512:2009/10/24 22:42:01.80 kernel pc:
0x0000000000c9ba8d dropobject+0x17d()
01:00000:00512:2009/10/24 22:42:01.80 kernel pc:
0x0000000000c25c12 s_execute+0x3772()
01:00000:00512:2009/10/24 22:42:01.80 kernel [Handler pc:
0x0x0000000000c54fc0 hdl_stack installed by the following
function:-]
01:00000:00512:2009/10/24 22:42:01.80 kernel [Handler pc:
0x0x0000000000c32fa0 s_handle installed by the following
function:-]
01:00000:00512:2009/10/24 22:42:01.80 kernel pc:
0x000000000196996e sequencer+0x71e()
01:00000:00512:2009/10/24 22:42:01.80 kernel pc:
0x000000000110789b tdsrecv_dynamic+0x222()
01:00000:00512:2009/10/24 22:42:01.80 kernel [Handler pc:
0x0x0000000000ce0920 ut_handle installed by the following
function:-]
01:00000:00512:2009/10/24 22:42:01.80 kernel pc:
0x0000000001827ba0 conn_hdlr+0x1340()
01:00000:00512:2009/10/24 22:42:01.80 kernel end of stack
trace, spid 512, kpid 1596719689, suid 179
01:00000:00512:2009/10/24 22:42:01.80 server Error: 6103,
Severity: 17, State: 1
01:00000:00512:2009/10/24 22:42:01.80 server Unable to do
cleanup for the killed process; received Msg 8203.



(2) This time, was able to collect the Ribo trace.

Last few lines of the translated output:

DYNAMIC2 Token (0x62); variable length
Length [4]: 131
Type [1]: DYN_PREPARE (0x01)
Status [1]: DYNAMIC_UNUSED (0x00)
Name Length [1]: 7
Name [7]: "DBD7023"
Statement Length [4]: 117
Statement [117]: "create proc DBD7023 as
select rtrim(zip_desc), rtrim(zip_state) from inventory..zip
where substring(zip_code,1,5) = ?"

Capture Record Header
Source [4]: RESPONSE (0x00000002)
Length [4]: 90

PDU Header
TDS Packet Type [1]: BUF_RESPONSE (0x04)
Status [1]: BUFSTAT_EOM (0x01)
Length [2]: 90
Channel [2]: 0
Packet No. [1]: 0
Window [1]: 0

DYNAMIC2 Token (0x62); variable length
Length [4]: 10
Type [1]: DYN_ACK (0x20)
Status [1]: DYNAMIC_UNUSED (0x00)
Name Length [1]: 7
Name [7]: "DBD7023"

PARAMFMT2 Token (0x20); variable length.
Length [4]: 14
Number of Params [2]: 1
Param 1
Name Length [1]: 0
Status [1]: <unrecognized> (0x00)
User Type [4]: 0
Data Type [1]: VARCHAR
Length [1]: 5
Locale Length [1]: 0

ROWFMT2 Token (0x61);
Length [4]: 34
Number of Columns [2]: 2
Column 1
Column Label Length [1]: 0
Catalog Name Length [1]: 0
Schema Length [1]: 0
Table Name Length [1]: 0
Column Name Length [1]: 0
Status [4]: ROW_UPDATABLE +
ROW_NULLALLOWED (0x00000030)
User Type [4]: 0x00000002
Data Type [1]: VARCHAR
Length [1]: 30
Locale Length [1]: 0
Column 2
Column Label Length [1]: 0
Catalog Name Length [1]: 0
Schema Length [1]: 0
Table Name Length [1]: 0
Column Name Length [1]: 0
Status [4]: ROW_UPDATABLE +
ROW_NULLALLOWED (0x00000030)
User Type [4]: 0x00000002
Data Type [1]: VARCHAR
Length [1]: 6
Locale Length [1]: 0

DONE Token (0xFD); fixed length.
Length [0]: [8]
Status [2]: DONE_FINAL (0x0000)
TranState [2]: TDS_TRAN_PROGRESS (0x0002)
Count (unused) [4]: 0

Capture Record Header
Source [4]: REQUEST (0x00000001)
Length [4]: 53

PDU Header
TDS Packet Type [1]: BUF_NORMAL (0x0F)
Status [1]: BUFSTAT_EOM (0x01)
Length [2]: 53
Channel [2]: 0
Packet No. [1]: 0
Window [1]: 0

DYNAMIC2 Token (0x62); variable length
Length [4]: 14
Type [1]: DYN_EXEC (0x02)
Status [1]: DYNAMIC_HASARGS (0x01)
Name Length [1]: 7
Name [7]: "DBD7023"

PARAMFMT2 Token (0x20); variable length.
Length [4]: 14
Number of Params [2]: 1
Param 1
Name Length [1]: 0
Status [1]: <unrecognized> (0x00)
User Type [4]: 0
Data Type [1]: VARCHAR
Length [1]: 5
Locale Length [1]: 0

PARAMS Token (0xD7); variable length.
Param 1
Length [1]: 5
Param data [5]: "70112" (0x3730313132)

Capture Record Header
Source [4]: RESPONSE (0x00000002)
Length [4]: 101

PDU Header
TDS Packet Type [1]: BUF_RESPONSE (0x04)
Status [1]: BUFSTAT_EOM (0x01)
Length [2]: 101
Channel [2]: 0
Packet No. [1]: 0
Window [1]: 0

DYNAMIC2 Token (0x62); variable length
Length [4]: 10
Type [1]: DYN_ACK (0x20)
Status [1]: DYNAMIC_UNUSED (0x00)
Name Length [1]: 7
Name [7]: "DBD7023"

ROWFMT2 Token (0x61);
Length [4]: 34
Number of Columns [2]: 2
Column 1
Column Label Length [1]: 0
Catalog Name Length [1]: 0
Schema Length [1]: 0
Table Name Length [1]: 0
Column Name Length [1]: 0
Status [4]: ROW_UPDATABLE +
ROW_NULLALLOWED (0x00000030)
User Type [4]: 0x00000002
Data Type [1]: VARCHAR
Length [1]: 30
Locale Length [1]: 0
Column 2
Column Label Length [1]: 0
Catalog Name Length [1]: 0
Schema Length [1]: 0
Table Name Length [1]: 0
Column Name Length [1]: 0
Status [4]: ROW_UPDATABLE +
ROW_NULLALLOWED (0x00000030)
User Type [4]: 0x00000002
Data Type [1]: VARCHAR
Length [1]: 6
Locale Length [1]: 0

CONTROL Token (0xAE); variable length.
Length [2]: 2
Control Info Length [1]: 0
Control Info Length [1]: 0

ROW Token (0xD1); variable length.
Column 1
Length [1]: 11
Row data [11]: "New Orleans"
(0x4E6577204F726C65616E73)
Column 2
Length [1]: 2
Row data [2]: "LA" (0x4C41)

DONEINPROC Token (0xFF); fixed length.
Length [0]: [8]
Status [2]: DONE_MORE + DONE_COUNT +
DONE_EVENT (0x0051)
TranState [2]: TDS_TRAN_PROGRESS (0x0002)
Count [4]: 1

DONEPROC Token (0xFE); fixed length.
Length [0]: [8]
Status [2]: DONE_PROC (0x0008)
TranState [2]: TDS_TRAN_PROGRESS (0x0002)
Count (unused) [4]: 1

Capture Record Header
Source [4]: REQUEST (0x00000001)
Length [4]: 8

PDU Header
TDS Packet Type [1]: BUF_ATTN (0x06)
Status [1]: BUFSTAT_EOM (0x01)
Length [2]: 8
Channel [2]: 0
Packet No. [1]: 0
Window [1]: 0

--
PDU packet not dumped.
--

Capture Record Header
Source [4]: RESPONSE (0x00000002)
Length [4]: 17

PDU Header
TDS Packet Type [1]: BUF_RESPONSE (0x04)
Status [1]: BUFSTAT_EOM (0x01)
Length [2]: 17
Channel [2]: 0
Packet No. [1]: 0
Window [1]: 0

DONE Token (0xFD); fixed length.
Length [0]: [8]
Status [2]: DONE_ATTN (0x0020)
TranState [2]: TDS_TRAN_PROGRESS (0x0002)
Count (unused) [4]: 1

Capture Record Header
Source [4]: REQUEST (0x00000001)
Length [4]: 27

PDU Header
TDS Packet Type [1]: BUF_NORMAL (0x0F)
Status [1]: BUFSTAT_EOM (0x01)
Length [2]: 27
Channel [2]: 0
Packet No. [1]: 0
Window [1]: 0

DYNAMIC2 Token (0x62); variable length
Length [4]: 14
Type [1]: DYN_DEALLOC (0x04)
Status [1]: DYNAMIC_UNUSED (0x00)
Name Length [1]: 7
Name [7]: "DBD7023"

Capture Record Header
Source [4]: RESPONSE (0x00000002)
Length [4]: 293

PDU Header
TDS Packet Type [1]: BUF_RESPONSE (0x04)
Status [1]: BUFSTAT_BEGIN (0x00)
Length [2]: 293
Channel [2]: 0
Packet No. [1]: 0
Window [1]: 0

DYNAMIC2 Token (0x62); variable length
Length [4]: 10
Type [1]: DYN_ACK (0x20)
Status [1]: DYNAMIC_UNUSED (0x00)
Name Length [1]: 7
Name [7]: "DBD7023"

EED Token (0xE5); variable length.
Length [2]: 190
Message Number [4]: 21
Message State [1]: 1
Message Class [1]: 26
SQL State Length [1]: 5
SQL State [5]: "ZZZZZ"
Status [1]: NO_EED (0x00)
Transaction State [2]: TDS_TRAN_SUCCEED (0x0001)
Message Length [2]: 158
Message Text [158]: "WARNING - Fatal Error 8203
occurred at Oct 24 2009 10:42PM. Please note the error and
time, and contact a user with System Administrator (SA)
authorization.
"
Server Name Length [1]: 11
Server Name [11]: "PROD"
Stored Proc. Name Length [1]: 0
Line Number [2]: -1

EED Token (0xE5); variable length.
Length [2]: 65
Message Number [4]: 5702
Message State [1]: 1
Message Class [1]: 10
SQL State Length [1]: 5
SQL State [5]: "ZZZZZ"
Status [1]: NO_EED (0x00)
Transaction State [2]: TDS_TRAN_SUCCEED (0x0001)
Message Length [2]: 33
Message Text [33]: "ASE is terminating this
process.
"
Server Name Length [1]: 11
Server Name [11]: "PROD"
Stored Proc. Name Length [1]: 0
Line Number [2]: -1

DONE Token (0xFD); fixed length.
Length [0]: [8]
Status [2]: DONE_ERROR (0x0002)
TranState [2]: TDS_TRAN_PROGRESS (0x0002)
Count (unused) [4]: 0

>>>>> Exception caught while reading a token:
java.io.EOFException

Exception caught while reading a token: java.io.EOFException
--
Error processing TDS. Attempting to skip.
--


J Posted on 2009-10-26 15:27:54.0Z
From: jtotally_bogus@sbcglobal.net (J)
Newsgroups: sybase.public.ase.general
Subject: Re: ASE stack trace with perl scripts
Reply-To: J@bogusemailAddress.com
Message-ID: <4ae5bed0.2193233@forums.sybase.com>
References: <4ae08f1d.449d.1681692777@sybase.com> <4ae485ef.7a07.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: 26 Oct 2009 07:27:54 -0800
X-Trace: forums-1-dub 1256570874 10.22.241.152 (26 Oct 2009 07:27:54 -0800)
X-Original-Trace: 26 Oct 2009 07:27:54 -0800, vip152.sybase.com
Lines: 397
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:28548
Article PK: 77790

On 25 Oct 2009 09:07:59 -0700, syb_user wrote:

This trace should help in the Support diagnosis.

What is happening is that you are doing a dynamic creation of the
stored procedure but before it completes the client is cancelling the
operation (this is the BUF_ATTN event in the trace). The server
responds with a response to cancel event. The client then issues a
dynamic command to deallocate the proc.

I will pass this information along to the engineer holding the
subcase/case.

Jay

>(1) Errors happened again last night
>
>01:00000:00512:2009/10/24 22:42:01.79 server Error: 8203,
>Severity: 26, State: 4
>01:00000:00512:2009/10/24 22:42:01.79 server Expected to
>find the descriptor for object -33554434 in database 2 in
>DROP state.
>01:00000:00512:2009/10/24 22:42:01.79 kernel
>************************************
>01:00000:00512:2009/10/24 22:42:01.79 kernel SQL causing
>error : =0e
>01:00000:00512:2009/10/24 22:42:01.79 kernel
>************************************
>01:00000:00512:2009/10/24 22:42:01.79 server SQL Text: =0e
>01:00000:00512:2009/10/24 22:42:01.79 kernel curdb =3d 7
>tempdb =3d 2 pstat =3d 0x10000
>01:00000:00512:2009/10/24 22:42:01.79 kernel lasterror =3d
>8203 preverror =3d 0 transtate =3d 1
>01:00000:00512:2009/10/24 22:42:01.79 kernel curcmd =3d 311
>program =3d upload_euram.pl
>01:00000:00512:2009/10/24 22:42:01.79 kernel extended error
>information: hostname: servo login: report
>01:00000:00512:2009/10/24 22:42:01.79 kernel pc:
>0x0000000001684835 pcstkwalk+0x30()
>01:00000:00512:2009/10/24 22:42:01.80 kernel pc:
>0x0000000001684629 ucstkgentrace+0x199()
>01:00000:00512:2009/10/24 22:42:01.80 kernel pc:
>0x000000000163d83e ucbacktrace+0x40()
>01:00000:00512:2009/10/24 22:42:01.80 kernel pc:
>0x000000000074e6db terminate_process+0xccb()
>01:00000:00512:2009/10/24 22:42:01.80 kernel pc:
>0x00000000014a6ed6 hdl_default+0x45()
>01:00000:00512:2009/10/24 22:42:01.80 kernel pc:
>0x0000000000c33592 s_handle+0x5f2()
>01:00000:00512:2009/10/24 22:42:01.80 kernel pc:
>0x0000000000c54c6e ex_raise+0x21e()
>01:00000:00512:2009/10/24 22:42:01.80 kernel pc:
>0x0000000000b20713 des__markdestroy+0xc3()
>01:00000:00512:2009/10/24 22:42:01.80 kernel pc:
>0x0000000000b1ad51 des_objdrop+0x11()
>01:00000:00512:2009/10/24 22:42:01.80 kernel pc:
>0x000000000153ac65 lwp_drop+0xf7()
>01:00000:00512:2009/10/24 22:42:01.80 kernel pc:
>0x0000000000c9ba8d dropobject+0x17d()
>01:00000:00512:2009/10/24 22:42:01.80 kernel pc:
>0x0000000000c25c12 s_execute+0x3772()
>01:00000:00512:2009/10/24 22:42:01.80 kernel [Handler pc:
>0x0x0000000000c54fc0 hdl_stack installed by the following
>function:-]
>01:00000:00512:2009/10/24 22:42:01.80 kernel [Handler pc:
>0x0x0000000000c32fa0 s_handle installed by the following
>function:-]
>01:00000:00512:2009/10/24 22:42:01.80 kernel pc:
>0x000000000196996e sequencer+0x71e()
>01:00000:00512:2009/10/24 22:42:01.80 kernel pc:
>0x000000000110789b tdsrecv_dynamic+0x222()
>01:00000:00512:2009/10/24 22:42:01.80 kernel [Handler pc:
>0x0x0000000000ce0920 ut_handle installed by the following
>function:-]
>01:00000:00512:2009/10/24 22:42:01.80 kernel pc:
>0x0000000001827ba0 conn_hdlr+0x1340()
>01:00000:00512:2009/10/24 22:42:01.80 kernel end of stack
>trace, spid 512, kpid 1596719689, suid 179
>01:00000:00512:2009/10/24 22:42:01.80 server Error: 6103,
>Severity: 17, State: 1
>01:00000:00512:2009/10/24 22:42:01.80 server Unable to do
>cleanup for the killed process; received Msg 8203.
>
>
>
>(2) This time, was able to collect the Ribo trace.
>
>Last few lines of the translated output:
>
>DYNAMIC2 Token (0x62); variable length
> Length [4]: 131
> Type [1]: DYN_PREPARE (0x01)
> Status [1]: DYNAMIC_UNUSED (0x00)
> Name Length [1]: 7
> Name [7]: "DBD7023"
> Statement Length [4]: 117
> Statement [117]: "create proc DBD7023 as
>select rtrim(zip_desc), rtrim(zip_state) from inventory..zip
>where substring(zip_code,1,5) =3d ?"
>
>Capture Record Header
> Source [4]: RESPONSE (0x00000002)
> Length [4]: 90
>
>PDU Header
> TDS Packet Type [1]: BUF_RESPONSE (0x04)
> Status [1]: BUFSTAT_EOM (0x01)
> Length [2]: 90
> Channel [2]: 0
> Packet No. [1]: 0
> Window [1]: 0
>
>DYNAMIC2 Token (0x62); variable length
> Length [4]: 10
> Type [1]: DYN_ACK (0x20)
> Status [1]: DYNAMIC_UNUSED (0x00)
> Name Length [1]: 7
> Name [7]: "DBD7023"
>
>PARAMFMT2 Token (0x20); variable length.
> Length [4]: 14
> Number of Params [2]: 1
> Param 1
> Name Length [1]: 0
> Status [1]: <unrecognized> (0x00)
> User Type [4]: 0
> Data Type [1]: VARCHAR
> Length [1]: 5
> Locale Length [1]: 0
>
>ROWFMT2 Token (0x61);
> Length [4]: 34
> Number of Columns [2]: 2
> Column 1
> Column Label Length [1]: 0
> Catalog Name Length [1]: 0
> Schema Length [1]: 0
> Table Name Length [1]: 0
> Column Name Length [1]: 0
> Status [4]: ROW_UPDATABLE +
>ROW_NULLALLOWED (0x00000030)
> User Type [4]: 0x00000002
> Data Type [1]: VARCHAR
> Length [1]: 30
> Locale Length [1]: 0
> Column 2
> Column Label Length [1]: 0
> Catalog Name Length [1]: 0
> Schema Length [1]: 0
> Table Name Length [1]: 0
> Column Name Length [1]: 0
> Status [4]: ROW_UPDATABLE +
>ROW_NULLALLOWED (0x00000030)
> User Type [4]: 0x00000002
> Data Type [1]: VARCHAR
> Length [1]: 6
> Locale Length [1]: 0
>
>DONE Token (0xFD); fixed length.
> Length [0]: [8]
> Status [2]: DONE_FINAL (0x0000)
> TranState [2]: TDS_TRAN_PROGRESS (0x0002)
> Count (unused) [4]: 0
>
>Capture Record Header
> Source [4]: REQUEST (0x00000001)
> Length [4]: 53
>
>PDU Header
> TDS Packet Type [1]: BUF_NORMAL (0x0F)
> Status [1]: BUFSTAT_EOM (0x01)
> Length [2]: 53
> Channel [2]: 0
> Packet No. [1]: 0
> Window [1]: 0
>
>DYNAMIC2 Token (0x62); variable length
> Length [4]: 14
> Type [1]: DYN_EXEC (0x02)
> Status [1]: DYNAMIC_HASARGS (0x01)
> Name Length [1]: 7
> Name [7]: "DBD7023"
>
>PARAMFMT2 Token (0x20); variable length.
> Length [4]: 14
> Number of Params [2]: 1
> Param 1
> Name Length [1]: 0
> Status [1]: <unrecognized> (0x00)
> User Type [4]: 0
> Data Type [1]: VARCHAR
> Length [1]: 5
> Locale Length [1]: 0
>
>PARAMS Token (0xD7); variable length.
> Param 1
> Length [1]: 5
> Param data [5]: "70112" (0x3730313132)
>
>Capture Record Header
> Source [4]: RESPONSE (0x00000002)
> Length [4]: 101
>
>PDU Header
> TDS Packet Type [1]: BUF_RESPONSE (0x04)
> Status [1]: BUFSTAT_EOM (0x01)
> Length [2]: 101
> Channel [2]: 0
> Packet No. [1]: 0
> Window [1]: 0
>
>DYNAMIC2 Token (0x62); variable length
> Length [4]: 10
> Type [1]: DYN_ACK (0x20)
> Status [1]: DYNAMIC_UNUSED (0x00)
> Name Length [1]: 7
> Name [7]: "DBD7023"
>
>ROWFMT2 Token (0x61);
> Length [4]: 34
> Number of Columns [2]: 2
> Column 1
> Column Label Length [1]: 0
> Catalog Name Length [1]: 0
> Schema Length [1]: 0
> Table Name Length [1]: 0
> Column Name Length [1]: 0
> Status [4]: ROW_UPDATABLE +
>ROW_NULLALLOWED (0x00000030)
> User Type [4]: 0x00000002
> Data Type [1]: VARCHAR
> Length [1]: 30
> Locale Length [1]: 0
> Column 2
> Column Label Length [1]: 0
> Catalog Name Length [1]: 0
> Schema Length [1]: 0
> Table Name Length [1]: 0
> Column Name Length [1]: 0
> Status [4]: ROW_UPDATABLE +
>ROW_NULLALLOWED (0x00000030)
> User Type [4]: 0x00000002
> Data Type [1]: VARCHAR
> Length [1]: 6
> Locale Length [1]: 0
>
>CONTROL Token (0xAE); variable length.
> Length [2]: 2
> Control Info Length [1]: 0
> Control Info Length [1]: 0
>
>ROW Token (0xD1); variable length.
> Column 1
> Length [1]: 11
> Row data [11]: "New Orleans"
>(0x4E6577204F726C65616E73)
> Column 2
> Length [1]: 2
> Row data [2]: "LA" (0x4C41)
>
>DONEINPROC Token (0xFF); fixed length.
> Length [0]: [8]
> Status [2]: DONE_MORE + DONE_COUNT +
>DONE_EVENT (0x0051)
> TranState [2]: TDS_TRAN_PROGRESS (0x0002)
> Count [4]: 1
>
>DONEPROC Token (0xFE); fixed length.
> Length [0]: [8]
> Status [2]: DONE_PROC (0x0008)
> TranState [2]: TDS_TRAN_PROGRESS (0x0002)
> Count (unused) [4]: 1
>
>Capture Record Header
> Source [4]: REQUEST (0x00000001)
> Length [4]: 8
>
>PDU Header
> TDS Packet Type [1]: BUF_ATTN (0x06)
> Status [1]: BUFSTAT_EOM (0x01)
> Length [2]: 8
> Channel [2]: 0
> Packet No. [1]: 0
> Window [1]: 0
>
>--
>PDU packet not dumped.
>--
>
>Capture Record Header
> Source [4]: RESPONSE (0x00000002)
> Length [4]: 17
>
>PDU Header
> TDS Packet Type [1]: BUF_RESPONSE (0x04)
> Status [1]: BUFSTAT_EOM (0x01)
> Length [2]: 17
> Channel [2]: 0
> Packet No. [1]: 0
> Window [1]: 0
>
>DONE Token (0xFD); fixed length.
> Length [0]: [8]
> Status [2]: DONE_ATTN (0x0020)
> TranState [2]: TDS_TRAN_PROGRESS (0x0002)
> Count (unused) [4]: 1
>
>Capture Record Header
> Source [4]: REQUEST (0x00000001)
> Length [4]: 27
>
>PDU Header
> TDS Packet Type [1]: BUF_NORMAL (0x0F)
> Status [1]: BUFSTAT_EOM (0x01)
> Length [2]: 27
> Channel [2]: 0
> Packet No. [1]: 0
> Window [1]: 0
>
>DYNAMIC2 Token (0x62); variable length
> Length [4]: 14
> Type [1]: DYN_DEALLOC (0x04)
> Status [1]: DYNAMIC_UNUSED (0x00)
> Name Length [1]: 7
> Name [7]: "DBD7023"
>
>Capture Record Header
> Source [4]: RESPONSE (0x00000002)
> Length [4]: 293
>
>PDU Header
> TDS Packet Type [1]: BUF_RESPONSE (0x04)
> Status [1]: BUFSTAT_BEGIN (0x00)
> Length [2]: 293
> Channel [2]: 0
> Packet No. [1]: 0
> Window [1]: 0
>
>DYNAMIC2 Token (0x62); variable length
> Length [4]: 10
> Type [1]: DYN_ACK (0x20)
> Status [1]: DYNAMIC_UNUSED (0x00)
> Name Length [1]: 7
> Name [7]: "DBD7023"
>
>EED Token (0xE5); variable length.
> Length [2]: 190
> Message Number [4]: 21
> Message State [1]: 1
> Message Class [1]: 26
> SQL State Length [1]: 5
> SQL State [5]: "ZZZZZ"
> Status [1]: NO_EED (0x00)
> Transaction State [2]: TDS_TRAN_SUCCEED (0x0001)
> Message Length [2]: 158
> Message Text [158]: "WARNING - Fatal Error 8203
>occurred at Oct 24 2009 10:42PM. Please note the error and
>time, and contact a user with System Administrator (SA)
>authorization.
>"
> Server Name Length [1]: 11
> Server Name [11]: "PROD"
> Stored Proc. Name Length [1]: 0
> Line Number [2]: -1
>
>EED Token (0xE5); variable length.
> Length [2]: 65
> Message Number [4]: 5702
> Message State [1]: 1
> Message Class [1]: 10
> SQL State Length [1]: 5
> SQL State [5]: "ZZZZZ"
> Status [1]: NO_EED (0x00)
> Transaction State [2]: TDS_TRAN_SUCCEED (0x0001)
> Message Length [2]: 33
> Message Text [33]: "ASE is terminating this
>process.
>"
> Server Name Length [1]: 11
> Server Name [11]: "PROD"
> Stored Proc. Name Length [1]: 0
> Line Number [2]: -1
>
>DONE Token (0xFD); fixed length.
> Length [0]: [8]
> Status [2]: DONE_ERROR (0x0002)
> TranState [2]: TDS_TRAN_PROGRESS (0x0002)
> Count (unused) [4]: 0
>
>>>>>> Exception caught while reading a token:
>java.io.EOFException
>
>Exception caught while reading a token: java.io.EOFException
>--
>Error processing TDS. Attempting to skip.
>--


J Posted on 2009-10-27 17:36:11.0Z
From: jtotally_bogus@sbcglobal.net (J)
Newsgroups: sybase.public.ase.general
Subject: Re: ASE stack trace with perl scripts
Reply-To: J@bogusemailAddress.com
Message-ID: <4ae72f61.8198528@forums.sybase.com>
References: <4ae08f1d.449d.1681692777@sybase.com> <4ae485ef.7a07.1681692777@sybase.com> <4ae5bed0.2193233@forums.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: 27 Oct 2009 09:36:11 -0800
X-Trace: forums-1-dub 1256664971 10.22.241.152 (27 Oct 2009 09:36:11 -0800)
X-Original-Trace: 27 Oct 2009 09:36:11 -0800, vip152.sybase.com
Lines: 405
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:28553
Article PK: 77795

On 26 Oct 2009 07:27:54 -0800, jtotally_bogus@sbcglobal.net (J) wrote:

Please take a look at Micheal's post and mine on the other thread
here. re. ct_cancel (finish).

Jay

>On 25 Oct 2009 09:07:59 -0700, syb_user wrote:
>
>This trace should help in the Support diagnosis.
>
>What is happening is that you are doing a dynamic creation of the
>stored procedure but before it completes the client is cancelling the
>operation (this is the BUF_ATTN event in the trace). The server
>responds with a response to cancel event. The client then issues a
>dynamic command to deallocate the proc.
>
>I will pass this information along to the engineer holding the
>subcase/case.
>
>Jay
>
>>(1) Errors happened again last night
>>
>>01:00000:00512:2009/10/24 22:42:01.79 server Error: 8203,
>>Severity: 26, State: 4
>>01:00000:00512:2009/10/24 22:42:01.79 server Expected to
>>find the descriptor for object -33554434 in database 2 in
>>DROP state.
>>01:00000:00512:2009/10/24 22:42:01.79 kernel
>>************************************
>>01:00000:00512:2009/10/24 22:42:01.79 kernel SQL causing
>>error : =0e
>>01:00000:00512:2009/10/24 22:42:01.79 kernel
>>************************************
>>01:00000:00512:2009/10/24 22:42:01.79 server SQL Text: =0e
>>01:00000:00512:2009/10/24 22:42:01.79 kernel curdb =3d 7
>>tempdb =3d 2 pstat =3d 0x10000
>>01:00000:00512:2009/10/24 22:42:01.79 kernel lasterror =3d
>>8203 preverror =3d 0 transtate =3d 1
>>01:00000:00512:2009/10/24 22:42:01.79 kernel curcmd =3d 311
>>program =3d upload_euram.pl
>>01:00000:00512:2009/10/24 22:42:01.79 kernel extended error
>>information: hostname: servo login: report
>>01:00000:00512:2009/10/24 22:42:01.79 kernel pc:
>>0x0000000001684835 pcstkwalk+0x30()
>>01:00000:00512:2009/10/24 22:42:01.80 kernel pc:
>>0x0000000001684629 ucstkgentrace+0x199()
>>01:00000:00512:2009/10/24 22:42:01.80 kernel pc:
>>0x000000000163d83e ucbacktrace+0x40()
>>01:00000:00512:2009/10/24 22:42:01.80 kernel pc:
>>0x000000000074e6db terminate_process+0xccb()
>>01:00000:00512:2009/10/24 22:42:01.80 kernel pc:
>>0x00000000014a6ed6 hdl_default+0x45()
>>01:00000:00512:2009/10/24 22:42:01.80 kernel pc:
>>0x0000000000c33592 s_handle+0x5f2()
>>01:00000:00512:2009/10/24 22:42:01.80 kernel pc:
>>0x0000000000c54c6e ex_raise+0x21e()
>>01:00000:00512:2009/10/24 22:42:01.80 kernel pc:
>>0x0000000000b20713 des__markdestroy+0xc3()
>>01:00000:00512:2009/10/24 22:42:01.80 kernel pc:
>>0x0000000000b1ad51 des_objdrop+0x11()
>>01:00000:00512:2009/10/24 22:42:01.80 kernel pc:
>>0x000000000153ac65 lwp_drop+0xf7()
>>01:00000:00512:2009/10/24 22:42:01.80 kernel pc:
>>0x0000000000c9ba8d dropobject+0x17d()
>>01:00000:00512:2009/10/24 22:42:01.80 kernel pc:
>>0x0000000000c25c12 s_execute+0x3772()
>>01:00000:00512:2009/10/24 22:42:01.80 kernel [Handler pc:
>>0x0x0000000000c54fc0 hdl_stack installed by the following
>>function:-]
>>01:00000:00512:2009/10/24 22:42:01.80 kernel [Handler pc:
>>0x0x0000000000c32fa0 s_handle installed by the following
>>function:-]
>>01:00000:00512:2009/10/24 22:42:01.80 kernel pc:
>>0x000000000196996e sequencer+0x71e()
>>01:00000:00512:2009/10/24 22:42:01.80 kernel pc:
>>0x000000000110789b tdsrecv_dynamic+0x222()
>>01:00000:00512:2009/10/24 22:42:01.80 kernel [Handler pc:
>>0x0x0000000000ce0920 ut_handle installed by the following
>>function:-]
>>01:00000:00512:2009/10/24 22:42:01.80 kernel pc:
>>0x0000000001827ba0 conn_hdlr+0x1340()
>>01:00000:00512:2009/10/24 22:42:01.80 kernel end of stack
>>trace, spid 512, kpid 1596719689, suid 179
>>01:00000:00512:2009/10/24 22:42:01.80 server Error: 6103,
>>Severity: 17, State: 1
>>01:00000:00512:2009/10/24 22:42:01.80 server Unable to do
>>cleanup for the killed process; received Msg 8203.
>>
>>
>>
>>(2) This time, was able to collect the Ribo trace.
>>
>>Last few lines of the translated output:
>>
>>DYNAMIC2 Token (0x62); variable length
>> Length [4]: 131
>> Type [1]: DYN_PREPARE (0x01)
>> Status [1]: DYNAMIC_UNUSED (0x00)
>> Name Length [1]: 7
>> Name [7]: "DBD7023"
>> Statement Length [4]: 117
>> Statement [117]: "create proc DBD7023 as
>>select rtrim(zip_desc), rtrim(zip_state) from inventory..zip
>>where substring(zip_code,1,5) =3d ?"
>>
>>Capture Record Header
>> Source [4]: RESPONSE (0x00000002)
>> Length [4]: 90
>>
>>PDU Header
>> TDS Packet Type [1]: BUF_RESPONSE (0x04)
>> Status [1]: BUFSTAT_EOM (0x01)
>> Length [2]: 90
>> Channel [2]: 0
>> Packet No. [1]: 0
>> Window [1]: 0
>>
>>DYNAMIC2 Token (0x62); variable length
>> Length [4]: 10
>> Type [1]: DYN_ACK (0x20)
>> Status [1]: DYNAMIC_UNUSED (0x00)
>> Name Length [1]: 7
>> Name [7]: "DBD7023"
>>
>>PARAMFMT2 Token (0x20); variable length.
>> Length [4]: 14
>> Number of Params [2]: 1
>> Param 1
>> Name Length [1]: 0
>> Status [1]: <unrecognized> (0x00)
>> User Type [4]: 0
>> Data Type [1]: VARCHAR
>> Length [1]: 5
>> Locale Length [1]: 0
>>
>>ROWFMT2 Token (0x61);
>> Length [4]: 34
>> Number of Columns [2]: 2
>> Column 1
>> Column Label Length [1]: 0
>> Catalog Name Length [1]: 0
>> Schema Length [1]: 0
>> Table Name Length [1]: 0
>> Column Name Length [1]: 0
>> Status [4]: ROW_UPDATABLE +
>>ROW_NULLALLOWED (0x00000030)
>> User Type [4]: 0x00000002
>> Data Type [1]: VARCHAR
>> Length [1]: 30
>> Locale Length [1]: 0
>> Column 2
>> Column Label Length [1]: 0
>> Catalog Name Length [1]: 0
>> Schema Length [1]: 0
>> Table Name Length [1]: 0
>> Column Name Length [1]: 0
>> Status [4]: ROW_UPDATABLE +
>>ROW_NULLALLOWED (0x00000030)
>> User Type [4]: 0x00000002
>> Data Type [1]: VARCHAR
>> Length [1]: 6
>> Locale Length [1]: 0
>>
>>DONE Token (0xFD); fixed length.
>> Length [0]: [8]
>> Status [2]: DONE_FINAL (0x0000)
>> TranState [2]: TDS_TRAN_PROGRESS (0x0002)
>> Count (unused) [4]: 0
>>
>>Capture Record Header
>> Source [4]: REQUEST (0x00000001)
>> Length [4]: 53
>>
>>PDU Header
>> TDS Packet Type [1]: BUF_NORMAL (0x0F)
>> Status [1]: BUFSTAT_EOM (0x01)
>> Length [2]: 53
>> Channel [2]: 0
>> Packet No. [1]: 0
>> Window [1]: 0
>>
>>DYNAMIC2 Token (0x62); variable length
>> Length [4]: 14
>> Type [1]: DYN_EXEC (0x02)
>> Status [1]: DYNAMIC_HASARGS (0x01)
>> Name Length [1]: 7
>> Name [7]: "DBD7023"
>>
>>PARAMFMT2 Token (0x20); variable length.
>> Length [4]: 14
>> Number of Params [2]: 1
>> Param 1
>> Name Length [1]: 0
>> Status [1]: <unrecognized> (0x00)
>> User Type [4]: 0
>> Data Type [1]: VARCHAR
>> Length [1]: 5
>> Locale Length [1]: 0
>>
>>PARAMS Token (0xD7); variable length.
>> Param 1
>> Length [1]: 5
>> Param data [5]: "70112" (0x3730313132)
>>
>>Capture Record Header
>> Source [4]: RESPONSE (0x00000002)
>> Length [4]: 101
>>
>>PDU Header
>> TDS Packet Type [1]: BUF_RESPONSE (0x04)
>> Status [1]: BUFSTAT_EOM (0x01)
>> Length [2]: 101
>> Channel [2]: 0
>> Packet No. [1]: 0
>> Window [1]: 0
>>
>>DYNAMIC2 Token (0x62); variable length
>> Length [4]: 10
>> Type [1]: DYN_ACK (0x20)
>> Status [1]: DYNAMIC_UNUSED (0x00)
>> Name Length [1]: 7
>> Name [7]: "DBD7023"
>>
>>ROWFMT2 Token (0x61);
>> Length [4]: 34
>> Number of Columns [2]: 2
>> Column 1
>> Column Label Length [1]: 0
>> Catalog Name Length [1]: 0
>> Schema Length [1]: 0
>> Table Name Length [1]: 0
>> Column Name Length [1]: 0
>> Status [4]: ROW_UPDATABLE +
>>ROW_NULLALLOWED (0x00000030)
>> User Type [4]: 0x00000002
>> Data Type [1]: VARCHAR
>> Length [1]: 30
>> Locale Length [1]: 0
>> Column 2
>> Column Label Length [1]: 0
>> Catalog Name Length [1]: 0
>> Schema Length [1]: 0
>> Table Name Length [1]: 0
>> Column Name Length [1]: 0
>> Status [4]: ROW_UPDATABLE +
>>ROW_NULLALLOWED (0x00000030)
>> User Type [4]: 0x00000002
>> Data Type [1]: VARCHAR
>> Length [1]: 6
>> Locale Length [1]: 0
>>
>>CONTROL Token (0xAE); variable length.
>> Length [2]: 2
>> Control Info Length [1]: 0
>> Control Info Length [1]: 0
>>
>>ROW Token (0xD1); variable length.
>> Column 1
>> Length [1]: 11
>> Row data [11]: "New Orleans"
>>(0x4E6577204F726C65616E73)
>> Column 2
>> Length [1]: 2
>> Row data [2]: "LA" (0x4C41)
>>
>>DONEINPROC Token (0xFF); fixed length.
>> Length [0]: [8]
>> Status [2]: DONE_MORE + DONE_COUNT +
>>DONE_EVENT (0x0051)
>> TranState [2]: TDS_TRAN_PROGRESS (0x0002)
>> Count [4]: 1
>>
>>DONEPROC Token (0xFE); fixed length.
>> Length [0]: [8]
>> Status [2]: DONE_PROC (0x0008)
>> TranState [2]: TDS_TRAN_PROGRESS (0x0002)
>> Count (unused) [4]: 1
>>
>>Capture Record Header
>> Source [4]: REQUEST (0x00000001)
>> Length [4]: 8
>>
>>PDU Header
>> TDS Packet Type [1]: BUF_ATTN (0x06)
>> Status [1]: BUFSTAT_EOM (0x01)
>> Length [2]: 8
>> Channel [2]: 0
>> Packet No. [1]: 0
>> Window [1]: 0
>>
>>--
>>PDU packet not dumped.
>>--
>>
>>Capture Record Header
>> Source [4]: RESPONSE (0x00000002)
>> Length [4]: 17
>>
>>PDU Header
>> TDS Packet Type [1]: BUF_RESPONSE (0x04)
>> Status [1]: BUFSTAT_EOM (0x01)
>> Length [2]: 17
>> Channel [2]: 0
>> Packet No. [1]: 0
>> Window [1]: 0
>>
>>DONE Token (0xFD); fixed length.
>> Length [0]: [8]
>> Status [2]: DONE_ATTN (0x0020)
>> TranState [2]: TDS_TRAN_PROGRESS (0x0002)
>> Count (unused) [4]: 1
>>
>>Capture Record Header
>> Source [4]: REQUEST (0x00000001)
>> Length [4]: 27
>>
>>PDU Header
>> TDS Packet Type [1]: BUF_NORMAL (0x0F)
>> Status [1]: BUFSTAT_EOM (0x01)
>> Length [2]: 27
>> Channel [2]: 0
>> Packet No. [1]: 0
>> Window [1]: 0
>>
>>DYNAMIC2 Token (0x62); variable length
>> Length [4]: 14
>> Type [1]: DYN_DEALLOC (0x04)
>> Status [1]: DYNAMIC_UNUSED (0x00)
>> Name Length [1]: 7
>> Name [7]: "DBD7023"
>>
>>Capture Record Header
>> Source [4]: RESPONSE (0x00000002)
>> Length [4]: 293
>>
>>PDU Header
>> TDS Packet Type [1]: BUF_RESPONSE (0x04)
>> Status [1]: BUFSTAT_BEGIN (0x00)
>> Length [2]: 293
>> Channel [2]: 0
>> Packet No. [1]: 0
>> Window [1]: 0
>>
>>DYNAMIC2 Token (0x62); variable length
>> Length [4]: 10
>> Type [1]: DYN_ACK (0x20)
>> Status [1]: DYNAMIC_UNUSED (0x00)
>> Name Length [1]: 7
>> Name [7]: "DBD7023"
>>
>>EED Token (0xE5); variable length.
>> Length [2]: 190
>> Message Number [4]: 21
>> Message State [1]: 1
>> Message Class [1]: 26
>> SQL State Length [1]: 5
>> SQL State [5]: "ZZZZZ"
>> Status [1]: NO_EED (0x00)
>> Transaction State [2]: TDS_TRAN_SUCCEED (0x0001)
>> Message Length [2]: 158
>> Message Text [158]: "WARNING - Fatal Error 8203
>>occurred at Oct 24 2009 10:42PM. Please note the error and
>>time, and contact a user with System Administrator (SA)
>>authorization.
>>"
>> Server Name Length [1]: 11
>> Server Name [11]: "PROD"
>> Stored Proc. Name Length [1]: 0
>> Line Number [2]: -1
>>
>>EED Token (0xE5); variable length.
>> Length [2]: 65
>> Message Number [4]: 5702
>> Message State [1]: 1
>> Message Class [1]: 10
>> SQL State Length [1]: 5
>> SQL State [5]: "ZZZZZ"
>> Status [1]: NO_EED (0x00)
>> Transaction State [2]: TDS_TRAN_SUCCEED (0x0001)
>> Message Length [2]: 33
>> Message Text [33]: "ASE is terminating this
>>process.
>>"
>> Server Name Length [1]: 11
>> Server Name [11]: "PROD"
>> Stored Proc. Name Length [1]: 0
>> Line Number [2]: -1
>>
>>DONE Token (0xFD); fixed length.
>> Length [0]: [8]
>> Status [2]: DONE_ERROR (0x0002)
>> TranState [2]: TDS_TRAN_PROGRESS (0x0002)
>> Count (unused) [4]: 0
>>
>>>>>>> Exception caught while reading a token:
>>java.io.EOFException
>>
>>Exception caught while reading a token: java.io.EOFException
>>--
>>Error processing TDS. Attempting to skip.
>>--
>


syb_user Posted on 2009-10-27 18:51:49.0Z
Sender: 30d9.4ae5c7f9.1804289383@sybase.com
From: syb_user
Newsgroups: sybase.public.ase.general
Subject: Re: ASE stack trace with perl scripts
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4ae74145.6eb9.1681692777@sybase.com>
References: <4ae72f61.8198528@forums.sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 27 Oct 2009 10:51:49 -0800
X-Trace: forums-1-dub 1256669509 10.22.241.41 (27 Oct 2009 10:51:49 -0800)
X-Original-Trace: 27 Oct 2009 10:51:49 -0800, 10.22.241.41
Lines: 6
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:28554
Article PK: 77796

Ok -- i will ask the application developer if he can
incorporate these changes to the script and let you know if
we are able to collect addl. diagnostic information if and
when the next stack trace errors occur.

Thanks for your help


syb_user Posted on 2009-10-27 20:00:58.0Z
Sender: 30d9.4ae5c7f9.1804289383@sybase.com
From: syb_user
Newsgroups: sybase.public.ase.general
Subject: Re: ASE stack trace with perl scripts
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4ae7517a.71ac.1681692777@sybase.com>
References: <4ae74145.6eb9.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 27 Oct 2009 12:00:58 -0800
X-Trace: forums-1-dub 1256673658 10.22.241.41 (27 Oct 2009 12:00:58 -0800)
X-Original-Trace: 27 Oct 2009 12:00:58 -0800, 10.22.241.41
Lines: 505
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:28555
Article PK: 77798

It seems to me that a similar pattern exists even for a
successful run of the perl script (without termination and
ASE stack trace errors).
I have uploaded the complete file to the case directory.

%grep BUF_ATTN successful_ue_pl.out | wc -l
11828
%grep DBD successful_ue_pl.out | grep "select
rtrim(zip_desc), rtrim(zip_state) from inventory..zip where
substring(zip_code,1,5) = ?" | wc -l
11828

From a translated ribo trace of a successful completion of
the perl job :


DONE Token (0xFD); fixed length.
Length [0]: [8]
Status [2]: DONE_COUNT (0x0010)
TranState [2]: TDS_TRAN_PROGRESS (0x0002)
Count [4]: 5914

Capture Record Header
Source [4]: REQUEST (0x00000001)
Length [4]: 138

PDU Header
TDS Packet Type [1]: BUF_NORMAL (0x0F)
Status [1]: BUFSTAT_EOM (0x01)
Length [2]: 138
Channel [2]: 0
Packet No. [1]: 0
Window [1]: 0

DYNAMIC2 Token (0x62); variable length
Length [4]: 125
Type [1]: DYN_PREPARE (0x01)
Status [1]: DYNAMIC_UNUSED (0x00)
Name Length [1]: 4
Name [4]: "DBD1"
Statement Length [4]: 114
Statement [114]: "create proc DBD1 as select
rtrim(zip_desc), rtrim(zip_state) from inventory..zip where
substring(zip_code,1,5) = ?"

Capture Record Header
Source [4]: RESPONSE (0x00000002)
Length [4]: 87

PDU Header
TDS Packet Type [1]: BUF_RESPONSE (0x04)
Status [1]: BUFSTAT_EOM (0x01)
Length [2]: 87
Channel [2]: 0
Packet No. [1]: 0
Window [1]: 0

DYNAMIC2 Token (0x62); variable length
Length [4]: 7
Type [1]: DYN_ACK (0x20)
Status [1]: DYNAMIC_UNUSED (0x00)
Name Length [1]: 4
Name [4]: "DBD1"

PARAMFMT2 Token (0x20); variable length.
Length [4]: 14
Number of Params [2]: 1
Param 1
Name Length [1]: 0
Status [1]: <unrecognized> (0x00)
User Type [4]: 0
Data Type [1]: VARCHAR
Length [1]: 5
Locale Length [1]: 0

ROWFMT2 Token (0x61);
Length [4]: 34
Number of Columns [2]: 2
Column 1
Column Label Length [1]: 0
Catalog Name Length [1]: 0
Schema Length [1]: 0
Table Name Length [1]: 0
Column Name Length [1]: 0
Status [4]: ROW_UPDATABLE +
ROW_NULLALLOWED (0x00000030)
User Type [4]: 0x00000002
Data Type [1]: VARCHAR
Length [1]: 30
Locale Length [1]: 0
Column 2
Column Label Length [1]: 0
Catalog Name Length [1]: 0
Schema Length [1]: 0
Table Name Length [1]: 0
Column Name Length [1]: 0
Status [4]: ROW_UPDATABLE +
ROW_NULLALLOWED (0x00000030)
User Type [4]: 0x00000002
Data Type [1]: VARCHAR
Length [1]: 6
Locale Length [1]: 0

DONE Token (0xFD); fixed length.
Length [0]: [8]
Status [2]: DONE_FINAL (0x0000)
TranState [2]: TDS_TRAN_PROGRESS (0x0002)
Count (unused) [4]: 0

Capture Record Header
Source [4]: REQUEST (0x00000001)
Length [4]: 50

PDU Header
TDS Packet Type [1]: BUF_NORMAL (0x0F)
Status [1]: BUFSTAT_EOM (0x01)
Length [2]: 50
Channel [2]: 0
Packet No. [1]: 0
Window [1]: 0

DYNAMIC2 Token (0x62); variable length
Length [4]: 11
Type [1]: DYN_EXEC (0x02)
Status [1]: DYNAMIC_HASARGS (0x01)
Name Length [1]: 4
Name [4]: "DBD1"

PARAMFMT2 Token (0x20); variable length.
Length [4]: 14
Number of Params [2]: 1
Param 1
Name Length [1]: 0
Status [1]: <unrecognized> (0x00)
User Type [4]: 0
Data Type [1]: VARCHAR
Length [1]: 5
Locale Length [1]: 0

PARAMS Token (0xD7); variable length.
Param 1
Length [1]: 5
Param data [5]: "18920" (0x3138393230)

Capture Record Header
Source [4]: RESPONSE (0x00000002)
Length [4]: 94

PDU Header
TDS Packet Type [1]: BUF_RESPONSE (0x04)
Status [1]: BUFSTAT_EOM (0x01)
Length [2]: 94
Channel [2]: 0
Packet No. [1]: 0
Window [1]: 0

DYNAMIC2 Token (0x62); variable length
Length [4]: 7
Type [1]: DYN_ACK (0x20)
Status [1]: DYNAMIC_UNUSED (0x00)
Name Length [1]: 4
Name [4]: "DBD1"

ROWFMT2 Token (0x61);
Length [4]: 34
Number of Columns [2]: 2
Column 1
Column Label Length [1]: 0
Catalog Name Length [1]: 0
Schema Length [1]: 0
Table Name Length [1]: 0
Column Name Length [1]: 0
Status [4]: ROW_UPDATABLE +
ROW_NULLALLOWED (0x00000030)
User Type [4]: 0x00000002
Data Type [1]: VARCHAR
Length [1]: 30
Locale Length [1]: 0
Column 2
Column Label Length [1]: 0
Catalog Name Length [1]: 0
Schema Length [1]: 0
Table Name Length [1]: 0
Column Name Length [1]: 0
Status [4]: ROW_UPDATABLE +
ROW_NULLALLOWED (0x00000030)
User Type [4]: 0x00000002
Data Type [1]: VARCHAR
Length [1]: 6
Locale Length [1]: 0

CONTROL Token (0xAE); variable length.
Length [2]: 2
Control Info Length [1]: 0
Control Info Length [1]: 0

ROW Token (0xD1); variable length.
Column 1
Length [1]: 7
Row data [7]: "Erwinna" (0x457277696E6E61)
Column 2
Length [1]: 2
Row data [2]: "PA" (0x5041)

DONEINPROC Token (0xFF); fixed length.
Length [0]: [8]
Status [2]: DONE_MORE + DONE_COUNT +
DONE_EVENT (0x0051)
TranState [2]: TDS_TRAN_PROGRESS (0x0002)
Count [4]: 1

DONEPROC Token (0xFE); fixed length.
Length [0]: [8]
Status [2]: DONE_PROC (0x0008)
TranState [2]: TDS_TRAN_PROGRESS (0x0002)
Count (unused) [4]: 1

Capture Record Header
Source [4]: REQUEST (0x00000001)
Length [4]: 8

PDU Header
TDS Packet Type [1]: BUF_ATTN (0x06)
Status [1]: BUFSTAT_EOM (0x01)
Length [2]: 8
Channel [2]: 0
Packet No. [1]: 0
Window [1]: 0

--
PDU packet not dumped.
--

Capture Record Header
Source [4]: RESPONSE (0x00000002)
Length [4]: 17

PDU Header
TDS Packet Type [1]: BUF_RESPONSE (0x04)
Status [1]: BUFSTAT_EOM (0x01)
Length [2]: 17
Channel [2]: 0
Packet No. [1]: 0
Window [1]: 0

DONE Token (0xFD); fixed length.
Length [0]: [8]
Status [2]: DONE_ATTN (0x0020)
TranState [2]: TDS_TRAN_PROGRESS (0x0002)
Count (unused) [4]: 1

Capture Record Header
Source [4]: REQUEST (0x00000001)
Length [4]: 24

PDU Header
TDS Packet Type [1]: BUF_NORMAL (0x0F)
Status [1]: BUFSTAT_EOM (0x01)
Length [2]: 24
Channel [2]: 0
Packet No. [1]: 0
Window [1]: 0

DYNAMIC2 Token (0x62); variable length
Length [4]: 11
Type [1]: DYN_DEALLOC (0x04)
Status [1]: DYNAMIC_UNUSED (0x00)
Name Length [1]: 4
Name [4]: "DBD1"

Capture Record Header
Source [4]: RESPONSE (0x00000002)
Length [4]: 29

PDU Header
TDS Packet Type [1]: BUF_RESPONSE (0x04)
Status [1]: BUFSTAT_EOM (0x01)
Length [2]: 29
Channel [2]: 0
Packet No. [1]: 0
Window [1]: 0

DYNAMIC2 Token (0x62); variable length
Length [4]: 7
Type [1]: DYN_ACK (0x20)
Status [1]: DYNAMIC_UNUSED (0x00)
Name Length [1]: 4
Name [4]: "DBD1"

DONE Token (0xFD); fixed length.
Length [0]: [8]
Status [2]: DONE_FINAL (0x0000)
TranState [2]: TDS_TRAN_PROGRESS (0x0002)
Count (unused) [4]: 0

Capture Record Header
Source [4]: REQUEST (0x00000001)
Length [4]: 138

PDU Header
TDS Packet Type [1]: BUF_NORMAL (0x0F)
Status [1]: BUFSTAT_EOM (0x01)
Length [2]: 138
Channel [2]: 0
Packet No. [1]: 0
Window [1]: 0

DYNAMIC2 Token (0x62); variable length
Length [4]: 125
Type [1]: DYN_PREPARE (0x01)
Status [1]: DYNAMIC_UNUSED (0x00)
Name Length [1]: 4
Name [4]: "DBD2"
Statement Length [4]: 114
Statement [114]: "create proc DBD2 as select
rtrim(zip_desc), rtrim(zip_state) from inventory..zip where
substring(zip_code,1,5) = ?"

Capture Record Header
Source [4]: RESPONSE (0x00000002)
Length [4]: 87

PDU Header
TDS Packet Type [1]: BUF_RESPONSE (0x04)
Status [1]: BUFSTAT_EOM (0x01)
Length [2]: 87
Channel [2]: 0
Packet No. [1]: 0
Window [1]: 0

DYNAMIC2 Token (0x62); variable length
Length [4]: 7
Type [1]: DYN_ACK (0x20)
Status [1]: DYNAMIC_UNUSED (0x00)
Name Length [1]: 4
Name [4]: "DBD2"

PARAMFMT2 Token (0x20); variable length.
Length [4]: 14
Number of Params [2]: 1
Param 1
Name Length [1]: 0
Status [1]: <unrecognized> (0x00)
User Type [4]: 0
Data Type [1]: VARCHAR
Length [1]: 5
Locale Length [1]: 0

ROWFMT2 Token (0x61);
Length [4]: 34
Number of Columns [2]: 2
Column 1
Column Label Length [1]: 0
Catalog Name Length [1]: 0
Schema Length [1]: 0
Table Name Length [1]: 0
Column Name Length [1]: 0
Status [4]: ROW_UPDATABLE +
ROW_NULLALLOWED (0x00000030)
User Type [4]: 0x00000002
Data Type [1]: VARCHAR
Length [1]: 30
Locale Length [1]: 0
Column 2
Column Label Length [1]: 0
Catalog Name Length [1]: 0
Schema Length [1]: 0
Table Name Length [1]: 0
Column Name Length [1]: 0
Status [4]: ROW_UPDATABLE +
ROW_NULLALLOWED (0x00000030)
User Type [4]: 0x00000002
Data Type [1]: VARCHAR
Length [1]: 6
Locale Length [1]: 0

DONE Token (0xFD); fixed length.
Length [0]: [8]
Status [2]: DONE_FINAL (0x0000)
TranState [2]: TDS_TRAN_PROGRESS (0x0002)
Count (unused) [4]: 0

Capture Record Header
Source [4]: REQUEST (0x00000001)
Length [4]: 50

PDU Header
TDS Packet Type [1]: BUF_NORMAL (0x0F)
Status [1]: BUFSTAT_EOM (0x01)
Length [2]: 50
Channel [2]: 0
Packet No. [1]: 0
Window [1]: 0

DYNAMIC2 Token (0x62); variable length
Length [4]: 11
Type [1]: DYN_EXEC (0x02)
Status [1]: DYNAMIC_HASARGS (0x01)
Name Length [1]: 4
Name [4]: "DBD2"

PARAMFMT2 Token (0x20); variable length.
Length [4]: 14
Number of Params [2]: 1
Param 1
Name Length [1]: 0
Status [1]: <unrecognized> (0x00)
User Type [4]: 0
Data Type [1]: VARCHAR
Length [1]: 5
Locale Length [1]: 0

PARAMS Token (0xD7); variable length.
Param 1
Length [1]: 5
Param data [5]: "18920" (0x3138393230)

Capture Record Header
Source [4]: RESPONSE (0x00000002)
Length [4]: 94

PDU Header
TDS Packet Type [1]: BUF_RESPONSE (0x04)
Status [1]: BUFSTAT_EOM (0x01)
Length [2]: 94
Channel [2]: 0
Packet No. [1]: 0
Window [1]: 0

DYNAMIC2 Token (0x62); variable length
Length [4]: 7
Type [1]: DYN_ACK (0x20)
Status [1]: DYNAMIC_UNUSED (0x00)
Name Length [1]: 4
Name [4]: "DBD2"

ROWFMT2 Token (0x61);
Length [4]: 34
Number of Columns [2]: 2
Column 1
Column Label Length [1]: 0
Catalog Name Length [1]: 0
Schema Length [1]: 0
Table Name Length [1]: 0
Column Name Length [1]: 0
Status [4]: ROW_UPDATABLE +
ROW_NULLALLOWED (0x00000030)
User Type [4]: 0x00000002
Data Type [1]: VARCHAR
Length [1]: 30
Locale Length [1]: 0
Column 2
Column Label Length [1]: 0
Catalog Name Length [1]: 0
Schema Length [1]: 0
Table Name Length [1]: 0
Column Name Length [1]: 0
Status [4]: ROW_UPDATABLE +
ROW_NULLALLOWED (0x00000030)
User Type [4]: 0x00000002
Data Type [1]: VARCHAR
Length [1]: 6
Locale Length [1]: 0

CONTROL Token (0xAE); variable length.
Length [2]: 2
Control Info Length [1]: 0
Control Info Length [1]: 0

ROW Token (0xD1); variable length.
Column 1
Length [1]: 7
Row data [7]: "Erwinna" (0x457277696E6E61)
Column 2
Length [1]: 2
Row data [2]: "PA" (0x5041)

DONEINPROC Token (0xFF); fixed length.
Length [0]: [8]
Status [2]: DONE_MORE + DONE_COUNT +
DONE_EVENT (0x0051)
TranState [2]: TDS_TRAN_PROGRESS (0x0002)
Count [4]: 1

DONEPROC Token (0xFE); fixed length.
Length [0]: [8]
Status [2]: DONE_PROC (0x0008)
TranState [2]: TDS_TRAN_PROGRESS (0x0002)
Count (unused) [4]: 1

Capture Record Header
Source [4]: REQUEST (0x00000001)
Length [4]: 8

PDU Header
TDS Packet Type [1]: BUF_ATTN (0x06)
Status [1]: BUFSTAT_EOM (0x01)
Length [2]: 8
Channel [2]: 0
Packet No. [1]: 0
Window [1]: 0

--
PDU packet not dumped.
--


J Posted on 2009-10-28 14:57:49.0Z
From: jtotally_bogus@sbcglobal.net (J)
Newsgroups: sybase.public.ase.general
Subject: Re: ASE stack trace with perl scripts
Reply-To: J@bogusemailAddress.com
Message-ID: <4ae85b86.1105749@forums.sybase.com>
References: <4ae74145.6eb9.1681692777@sybase.com> <4ae7517a.71ac.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: 28 Oct 2009 06:57:49 -0800
X-Trace: forums-1-dub 1256741869 10.22.241.152 (28 Oct 2009 06:57:49 -0800)
X-Original-Trace: 28 Oct 2009 06:57:49 -0800, vip152.sybase.com
Lines: 516
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:28559
Article PK: 77804

On 27 Oct 2009 12:00:58 -0800, syb_user wrote:

I have looked at your "good Ribo" trace now. I am going to speak with
the case owner and make some recommendations. I would like to
continue the dialog thru the support case owner for now. I think when
it is all done then maybe updating the newsgroup is good but not too
productive for now.

Jay

>It seems to me that a similar pattern exists even for a
>successful run of the perl script (without termination and
>ASE stack trace errors).
>I have uploaded the complete file to the case directory.
>
>%grep BUF_ATTN successful_ue_pl.out | wc -l
>11828
>%grep DBD successful_ue_pl.out | grep "select
>rtrim(zip_desc), rtrim(zip_state) from inventory..zip where
>substring(zip_code,1,5) = ?" | wc -l
>11828
>
>From a translated ribo trace of a successful completion of
>the perl job :
>
>
>DONE Token (0xFD); fixed length.
> Length [0]: [8]
> Status [2]: DONE_COUNT (0x0010)
> TranState [2]: TDS_TRAN_PROGRESS (0x0002)
> Count [4]: 5914
>
>Capture Record Header
> Source [4]: REQUEST (0x00000001)
> Length [4]: 138
>
>PDU Header
> TDS Packet Type [1]: BUF_NORMAL (0x0F)
> Status [1]: BUFSTAT_EOM (0x01)
> Length [2]: 138
> Channel [2]: 0
> Packet No. [1]: 0
> Window [1]: 0
>
>DYNAMIC2 Token (0x62); variable length
> Length [4]: 125
> Type [1]: DYN_PREPARE (0x01)
> Status [1]: DYNAMIC_UNUSED (0x00)
> Name Length [1]: 4
> Name [4]: "DBD1"
> Statement Length [4]: 114
> Statement [114]: "create proc DBD1 as select
>rtrim(zip_desc), rtrim(zip_state) from inventory..zip where
>substring(zip_code,1,5) = ?"
>
>Capture Record Header
> Source [4]: RESPONSE (0x00000002)
> Length [4]: 87
>
>PDU Header
> TDS Packet Type [1]: BUF_RESPONSE (0x04)
> Status [1]: BUFSTAT_EOM (0x01)
> Length [2]: 87
> Channel [2]: 0
> Packet No. [1]: 0
> Window [1]: 0
>
>DYNAMIC2 Token (0x62); variable length
> Length [4]: 7
> Type [1]: DYN_ACK (0x20)
> Status [1]: DYNAMIC_UNUSED (0x00)
> Name Length [1]: 4
> Name [4]: "DBD1"
>
>PARAMFMT2 Token (0x20); variable length.
> Length [4]: 14
> Number of Params [2]: 1
> Param 1
> Name Length [1]: 0
> Status [1]: <unrecognized> (0x00)
> User Type [4]: 0
> Data Type [1]: VARCHAR
> Length [1]: 5
> Locale Length [1]: 0
>
>ROWFMT2 Token (0x61);
> Length [4]: 34
> Number of Columns [2]: 2
> Column 1
> Column Label Length [1]: 0
> Catalog Name Length [1]: 0
> Schema Length [1]: 0
> Table Name Length [1]: 0
> Column Name Length [1]: 0
> Status [4]: ROW_UPDATABLE +
>ROW_NULLALLOWED (0x00000030)
> User Type [4]: 0x00000002
> Data Type [1]: VARCHAR
> Length [1]: 30
> Locale Length [1]: 0
> Column 2
> Column Label Length [1]: 0
> Catalog Name Length [1]: 0
> Schema Length [1]: 0
> Table Name Length [1]: 0
> Column Name Length [1]: 0
> Status [4]: ROW_UPDATABLE +
>ROW_NULLALLOWED (0x00000030)
> User Type [4]: 0x00000002
> Data Type [1]: VARCHAR
> Length [1]: 6
> Locale Length [1]: 0
>
>DONE Token (0xFD); fixed length.
> Length [0]: [8]
> Status [2]: DONE_FINAL (0x0000)
> TranState [2]: TDS_TRAN_PROGRESS (0x0002)
> Count (unused) [4]: 0
>
>Capture Record Header
> Source [4]: REQUEST (0x00000001)
> Length [4]: 50
>
>PDU Header
> TDS Packet Type [1]: BUF_NORMAL (0x0F)
> Status [1]: BUFSTAT_EOM (0x01)
> Length [2]: 50
> Channel [2]: 0
> Packet No. [1]: 0
> Window [1]: 0
>
>DYNAMIC2 Token (0x62); variable length
> Length [4]: 11
> Type [1]: DYN_EXEC (0x02)
> Status [1]: DYNAMIC_HASARGS (0x01)
> Name Length [1]: 4
> Name [4]: "DBD1"
>
>PARAMFMT2 Token (0x20); variable length.
> Length [4]: 14
> Number of Params [2]: 1
> Param 1
> Name Length [1]: 0
> Status [1]: <unrecognized> (0x00)
> User Type [4]: 0
> Data Type [1]: VARCHAR
> Length [1]: 5
> Locale Length [1]: 0
>
>PARAMS Token (0xD7); variable length.
> Param 1
> Length [1]: 5
> Param data [5]: "18920" (0x3138393230)
>
>Capture Record Header
> Source [4]: RESPONSE (0x00000002)
> Length [4]: 94
>
>PDU Header
> TDS Packet Type [1]: BUF_RESPONSE (0x04)
> Status [1]: BUFSTAT_EOM (0x01)
> Length [2]: 94
> Channel [2]: 0
> Packet No. [1]: 0
> Window [1]: 0
>
>DYNAMIC2 Token (0x62); variable length
> Length [4]: 7
> Type [1]: DYN_ACK (0x20)
> Status [1]: DYNAMIC_UNUSED (0x00)
> Name Length [1]: 4
> Name [4]: "DBD1"
>
>ROWFMT2 Token (0x61);
> Length [4]: 34
> Number of Columns [2]: 2
> Column 1
> Column Label Length [1]: 0
> Catalog Name Length [1]: 0
> Schema Length [1]: 0
> Table Name Length [1]: 0
> Column Name Length [1]: 0
> Status [4]: ROW_UPDATABLE +
>ROW_NULLALLOWED (0x00000030)
> User Type [4]: 0x00000002
> Data Type [1]: VARCHAR
> Length [1]: 30
> Locale Length [1]: 0
> Column 2
> Column Label Length [1]: 0
> Catalog Name Length [1]: 0
> Schema Length [1]: 0
> Table Name Length [1]: 0
> Column Name Length [1]: 0
> Status [4]: ROW_UPDATABLE +
>ROW_NULLALLOWED (0x00000030)
> User Type [4]: 0x00000002
> Data Type [1]: VARCHAR
> Length [1]: 6
> Locale Length [1]: 0
>
>CONTROL Token (0xAE); variable length.
> Length [2]: 2
> Control Info Length [1]: 0
> Control Info Length [1]: 0
>
>ROW Token (0xD1); variable length.
> Column 1
> Length [1]: 7
> Row data [7]: "Erwinna" (0x457277696E6E61)
> Column 2
> Length [1]: 2
> Row data [2]: "PA" (0x5041)
>
>DONEINPROC Token (0xFF); fixed length.
> Length [0]: [8]
> Status [2]: DONE_MORE + DONE_COUNT +
>DONE_EVENT (0x0051)
> TranState [2]: TDS_TRAN_PROGRESS (0x0002)
> Count [4]: 1
>
>DONEPROC Token (0xFE); fixed length.
> Length [0]: [8]
> Status [2]: DONE_PROC (0x0008)
> TranState [2]: TDS_TRAN_PROGRESS (0x0002)
> Count (unused) [4]: 1
>
>Capture Record Header
> Source [4]: REQUEST (0x00000001)
> Length [4]: 8
>
>PDU Header
> TDS Packet Type [1]: BUF_ATTN (0x06)
> Status [1]: BUFSTAT_EOM (0x01)
> Length [2]: 8
> Channel [2]: 0
> Packet No. [1]: 0
> Window [1]: 0
>
>--
>PDU packet not dumped.
>--
>
>Capture Record Header
> Source [4]: RESPONSE (0x00000002)
> Length [4]: 17
>
>PDU Header
> TDS Packet Type [1]: BUF_RESPONSE (0x04)
> Status [1]: BUFSTAT_EOM (0x01)
> Length [2]: 17
> Channel [2]: 0
> Packet No. [1]: 0
> Window [1]: 0
>
>DONE Token (0xFD); fixed length.
> Length [0]: [8]
> Status [2]: DONE_ATTN (0x0020)
> TranState [2]: TDS_TRAN_PROGRESS (0x0002)
> Count (unused) [4]: 1
>
>Capture Record Header
> Source [4]: REQUEST (0x00000001)
> Length [4]: 24
>
>PDU Header
> TDS Packet Type [1]: BUF_NORMAL (0x0F)
> Status [1]: BUFSTAT_EOM (0x01)
> Length [2]: 24
> Channel [2]: 0
> Packet No. [1]: 0
> Window [1]: 0
>
>DYNAMIC2 Token (0x62); variable length
> Length [4]: 11
> Type [1]: DYN_DEALLOC (0x04)
> Status [1]: DYNAMIC_UNUSED (0x00)
> Name Length [1]: 4
> Name [4]: "DBD1"
>
>Capture Record Header
> Source [4]: RESPONSE (0x00000002)
> Length [4]: 29
>
>PDU Header
> TDS Packet Type [1]: BUF_RESPONSE (0x04)
> Status [1]: BUFSTAT_EOM (0x01)
> Length [2]: 29
> Channel [2]: 0
> Packet No. [1]: 0
> Window [1]: 0
>
>DYNAMIC2 Token (0x62); variable length
> Length [4]: 7
> Type [1]: DYN_ACK (0x20)
> Status [1]: DYNAMIC_UNUSED (0x00)
> Name Length [1]: 4
> Name [4]: "DBD1"
>
>DONE Token (0xFD); fixed length.
> Length [0]: [8]
> Status [2]: DONE_FINAL (0x0000)
> TranState [2]: TDS_TRAN_PROGRESS (0x0002)
> Count (unused) [4]: 0
>
>Capture Record Header
> Source [4]: REQUEST (0x00000001)
> Length [4]: 138
>
>PDU Header
> TDS Packet Type [1]: BUF_NORMAL (0x0F)
> Status [1]: BUFSTAT_EOM (0x01)
> Length [2]: 138
> Channel [2]: 0
> Packet No. [1]: 0
> Window [1]: 0
>
>DYNAMIC2 Token (0x62); variable length
> Length [4]: 125
> Type [1]: DYN_PREPARE (0x01)
> Status [1]: DYNAMIC_UNUSED (0x00)
> Name Length [1]: 4
> Name [4]: "DBD2"
> Statement Length [4]: 114
> Statement [114]: "create proc DBD2 as select
>rtrim(zip_desc), rtrim(zip_state) from inventory..zip where
>substring(zip_code,1,5) = ?"
>
>Capture Record Header
> Source [4]: RESPONSE (0x00000002)
> Length [4]: 87
>
>PDU Header
> TDS Packet Type [1]: BUF_RESPONSE (0x04)
> Status [1]: BUFSTAT_EOM (0x01)
> Length [2]: 87
> Channel [2]: 0
> Packet No. [1]: 0
> Window [1]: 0
>
>DYNAMIC2 Token (0x62); variable length
> Length [4]: 7
> Type [1]: DYN_ACK (0x20)
> Status [1]: DYNAMIC_UNUSED (0x00)
> Name Length [1]: 4
> Name [4]: "DBD2"
>
>PARAMFMT2 Token (0x20); variable length.
> Length [4]: 14
> Number of Params [2]: 1
> Param 1
> Name Length [1]: 0
> Status [1]: <unrecognized> (0x00)
> User Type [4]: 0
> Data Type [1]: VARCHAR
> Length [1]: 5
> Locale Length [1]: 0
>
>ROWFMT2 Token (0x61);
> Length [4]: 34
> Number of Columns [2]: 2
> Column 1
> Column Label Length [1]: 0
> Catalog Name Length [1]: 0
> Schema Length [1]: 0
> Table Name Length [1]: 0
> Column Name Length [1]: 0
> Status [4]: ROW_UPDATABLE +
>ROW_NULLALLOWED (0x00000030)
> User Type [4]: 0x00000002
> Data Type [1]: VARCHAR
> Length [1]: 30
> Locale Length [1]: 0
> Column 2
> Column Label Length [1]: 0
> Catalog Name Length [1]: 0
> Schema Length [1]: 0
> Table Name Length [1]: 0
> Column Name Length [1]: 0
> Status [4]: ROW_UPDATABLE +
>ROW_NULLALLOWED (0x00000030)
> User Type [4]: 0x00000002
> Data Type [1]: VARCHAR
> Length [1]: 6
> Locale Length [1]: 0
>
>DONE Token (0xFD); fixed length.
> Length [0]: [8]
> Status [2]: DONE_FINAL (0x0000)
> TranState [2]: TDS_TRAN_PROGRESS (0x0002)
> Count (unused) [4]: 0
>
>Capture Record Header
> Source [4]: REQUEST (0x00000001)
> Length [4]: 50
>
>PDU Header
> TDS Packet Type [1]: BUF_NORMAL (0x0F)
> Status [1]: BUFSTAT_EOM (0x01)
> Length [2]: 50
> Channel [2]: 0
> Packet No. [1]: 0
> Window [1]: 0
>
>DYNAMIC2 Token (0x62); variable length
> Length [4]: 11
> Type [1]: DYN_EXEC (0x02)
> Status [1]: DYNAMIC_HASARGS (0x01)
> Name Length [1]: 4
> Name [4]: "DBD2"
>
>PARAMFMT2 Token (0x20); variable length.
> Length [4]: 14
> Number of Params [2]: 1
> Param 1
> Name Length [1]: 0
> Status [1]: <unrecognized> (0x00)
> User Type [4]: 0
> Data Type [1]: VARCHAR
> Length [1]: 5
> Locale Length [1]: 0
>
>PARAMS Token (0xD7); variable length.
> Param 1
> Length [1]: 5
> Param data [5]: "18920" (0x3138393230)
>
>Capture Record Header
> Source [4]: RESPONSE (0x00000002)
> Length [4]: 94
>
>PDU Header
> TDS Packet Type [1]: BUF_RESPONSE (0x04)
> Status [1]: BUFSTAT_EOM (0x01)
> Length [2]: 94
> Channel [2]: 0
> Packet No. [1]: 0
> Window [1]: 0
>
>DYNAMIC2 Token (0x62); variable length
> Length [4]: 7
> Type [1]: DYN_ACK (0x20)
> Status [1]: DYNAMIC_UNUSED (0x00)
> Name Length [1]: 4
> Name [4]: "DBD2"
>
>ROWFMT2 Token (0x61);
> Length [4]: 34
> Number of Columns [2]: 2
> Column 1
> Column Label Length [1]: 0
> Catalog Name Length [1]: 0
> Schema Length [1]: 0
> Table Name Length [1]: 0
> Column Name Length [1]: 0
> Status [4]: ROW_UPDATABLE +
>ROW_NULLALLOWED (0x00000030)
> User Type [4]: 0x00000002
> Data Type [1]: VARCHAR
> Length [1]: 30
> Locale Length [1]: 0
> Column 2
> Column Label Length [1]: 0
> Catalog Name Length [1]: 0
> Schema Length [1]: 0
> Table Name Length [1]: 0
> Column Name Length [1]: 0
> Status [4]: ROW_UPDATABLE +
>ROW_NULLALLOWED (0x00000030)
> User Type [4]: 0x00000002
> Data Type [1]: VARCHAR
> Length [1]: 6
> Locale Length [1]: 0
>
>CONTROL Token (0xAE); variable length.
> Length [2]: 2
> Control Info Length [1]: 0
> Control Info Length [1]: 0
>
>ROW Token (0xD1); variable length.
> Column 1
> Length [1]: 7
> Row data [7]: "Erwinna" (0x457277696E6E61)
> Column 2
> Length [1]: 2
> Row data [2]: "PA" (0x5041)
>
>DONEINPROC Token (0xFF); fixed length.
> Length [0]: [8]
> Status [2]: DONE_MORE + DONE_COUNT +
>DONE_EVENT (0x0051)
> TranState [2]: TDS_TRAN_PROGRESS (0x0002)
> Count [4]: 1
>
>DONEPROC Token (0xFE); fixed length.
> Length [0]: [8]
> Status [2]: DONE_PROC (0x0008)
> TranState [2]: TDS_TRAN_PROGRESS (0x0002)
> Count (unused) [4]: 1
>
>Capture Record Header
> Source [4]: REQUEST (0x00000001)
> Length [4]: 8
>
>PDU Header
> TDS Packet Type [1]: BUF_ATTN (0x06)
> Status [1]: BUFSTAT_EOM (0x01)
> Length [2]: 8
> Channel [2]: 0
> Packet No. [1]: 0
> Window [1]: 0
>
>--
>PDU packet not dumped.
>--