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.

why did this dataserver crash?

6 posts in General Discussion Last posting was on 2010-02-26 09:32:31.0Z
vtpcnk Posted on 2010-02-22 08:20:16.0Z
Sender: e26.4b823796.1804289383@sybase.com
From: vtpcnk
Newsgroups: sybase.public.ase.general
Subject: why did this dataserver crash?
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4b823e40.ea4.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 22 Feb 2010 00:20:16 -0800
X-Trace: forums-1-dub 1266826816 10.22.241.41 (22 Feb 2010 00:20:16 -0800)
X-Original-Trace: 22 Feb 2010 00:20:16 -0800, 10.22.241.41
Lines: 124
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:28985
Article PK: 78223

i have a case where a production server crashed due to a 696
error in tempdb ie page in cache belongs to another object
than the object sought.

the standard 696 error is found multiple times towards the
end of the error log :

An attempt was made to fetch logical page '10420344' in
tempdb from cache 'tempdbcache'. Page belongs to object
'-45023282' and not to object '-65732658'. Restart of SQL
Server will clear the error. Please contact your System
Administrator for help.

then there is a bunch of stack trace with errors like :

00:00000:01003:2010/02/21 21:08:44.10 kernel Stack overflow
detected: limit: 0x00000100095180d0, sp: 0x0000010009519308
00:00000:01003:2010/02/21 21:08:44.10 kernel *** Stack
guardword corrupted.

00:00000:01003:2010/02/21 21:08:44.10 kernel *** Stack
corrupted, server aborting.

there is also repeated refrence to a particular device which
hosts tempdb - the device number and name are given.


sp_sysmon (with a reference to tempdb) seems to have started
the stack trace like 9 hours before the crash.

there is repeated "timeslice -501, current process infected"
messages in the stack trace due to sysmon.

also there is : "background task message: ****
INFORMATION_ONLY THRESHOLD Database:'tempdb'.
Segment:'default'. Total:'14000' Space used:'3072' Mb.
*****"

between the stack trace and the 696 errors there is also
this set of errors :

02:00000:00976:2010/02/21 21:00:59.14 kernel Cannot read,
host process disconnected: WNTBIMJ1PC8BX spid: 976
01:00000:01003:2010/02/21 21:02:43.23 server Starting
diagnostics for read failure:
01:00000:01003:2010/02/21 21:02:43.23 server Device
Information:
Device number = 103
Phyname =
/cfs/tempdb_data_03.dat
01:00000:01003:2010/02/21 21:02:43.23 server Buffer
Information:
Buf addr = 0x1030a791840,
Mass addr = 0x1030a791840
Buf pageno = 10420344, Mass
pageno = 10420344, dbid = 2
01:00000:01003:2010/02/21 21:02:43.23 server
Buf virtpg = 1729256056,
Mass virtpg = 1729256056
Buf stat = 0x1, Mass stat =
0x1008
Mass keep = 1, Mass awaited
= 0
01:00000:01003:2010/02/21 21:02:43.23 server Page
Information from first read attempt: Page read from disk
ppageno = 10420344
, pobjid = -43647026, pindid = 0 pnextpg = 10420345, pprevpg
= 10420343 plevel = 0, pstat = 0x101 pts_hi = 5, pts_lo =
-159054
2106
01:00000:01003:2010/02/21 21:02:43.23 server Page
Information from second read attempt: Page read from disk
ppageno = 1042034
4, pobjid = -43647026, pindid = 0 pnextpg = 10420345,
pprevpg = 10420343 plevel = 0, pstat = 0x101 pts_hi = 5,
pts_lo = -15905
42106
01:00000:01003:2010/02/21 21:02:43.23 server SDES
Information:
dbid = 2, objid =
-65732658, scur.pageid = 10420344
sstat = 0x10, sstat2 = 0x0
suid = 1, cacheid = 7
01:00000:01003:2010/02/21 21:02:43.23 server PSS
Information:
pstat = 0x10000, pcurdb =
1, pspid = 1003
p2stat = 0x141020, p3stat =
0x40081a
plasterror = 4002,
preverror = 0, pattention = 0
01:00000:01003:2010/02/21 21:02:43.23 server End
diagnostics for read failure:
01:00000:01003:2010/02/21 21:02:43.23 server WARNING: Pss
0x0000010044aa75d8 found with open sdes. pspid 1003, psuid
1340, pc
urdb 1, range entry 50, sdesp 0x000001007e638000, objid
-65732658.
01:00000:01003:2010/02/21 21:02:43.24 server Error: 6103,
Severity: 17, State: 1
01:00000:01003:2010/02/21 21:02:43.24 server Unable to do
cleanup for the killed process; received Msg 696.
03:00000:00630:2010/02/21 21:03:55.42 server background
task message: **** INFORMATION_ONLY THRESHOLD
Database:'tempdb'. Segm
ent:'default'. Total:'14000' Space used:'2560' Mb. *******
00:00000:01003:2010/02/21 21:08:43.98 server Starting
diagnostics for read failure:
00:00000:01003:2010/02/21 21:08:43.98 server Device
Information:
Device number = 103
Phyname =
/cfs/tempdb_data_03.dat
00:00000:01003:2010/02/21 21:08:43.98 server Buffer
Information:
Buf addr = 0x1030a799540,
Mass addr = 0x1030a799540




so is a 696 by itself cause enough for the dataserver to
crash? or did the stacktrace due to sysmon lead to the
crash? appreciate some insights.


vtpcnk Posted on 2010-02-22 08:32:21.0Z
Sender: ec2.4b823ee9.1804289383@sybase.com
From: vtpcnk
Newsgroups: sybase.public.ase.general
Subject: Re: why did this dataserver crash?
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4b824115.f29.1681692777@sybase.com>
References: <4b823e40.ea4.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 22 Feb 2010 00:32:21 -0800
X-Trace: forums-1-dub 1266827541 10.22.241.41 (22 Feb 2010 00:32:21 -0800)
X-Original-Trace: 22 Feb 2010 00:32:21 -0800, 10.22.241.41
Lines: 10
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:28987
Article PK: 78224

another related question is whether this crash could have
been avoided. so would stopping sysmon (i think it is
periodically run on this server by cron) have helped avert
this crash?

also how could multiple seperate runs of sysmon reference
the same page in tempdb? or is sysmon working based out of
some cached information?

appreciate the feedback.


"Mark A. Parsons" <iron_horse Posted on 2010-02-22 12:30:50.0Z
From: "Mark A. Parsons" <iron_horse@no_spamola.compuserve.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
Newsgroups: sybase.public.ase.general
Subject: Re: why did this dataserver crash?
References: <4b823e40.ea4.1681692777@sybase.com> <4b824115.f29.1681692777@sybase.com>
In-Reply-To: <4b824115.f29.1681692777@sybase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 100218-0, 02/18/2010), Outbound message
X-Antivirus-Status: Clean
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4b8278fa$1@forums-1-dub>
Date: 22 Feb 2010 04:30:50 -0800
X-Trace: forums-1-dub 1266841850 10.22.241.152 (22 Feb 2010 04:30:50 -0800)
X-Original-Trace: 22 Feb 2010 04:30:50 -0800, vip152.sybase.com
Lines: 22
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:28989
Article PK: 78227


vtpcnk wrote:
> another related question is whether this crash could have
> been avoided. so would stopping sysmon (i think it is
> periodically run on this server by cron) have helped avert
> this crash?

*shrug*

Not enough info to know if sysmon caused the crash.

Generally speaking, sysmon should not crash a dataserver regardless of how many copies you're running at the same time.

> also how could multiple seperate runs of sysmon reference
> the same page in tempdb? or is sysmon working based out of
> some cached information?

*shrug*

I don't know how you determined that separate sysmons were trying to access the same page in tempdb ... doesn't sound
right ... ???????


vtpcnk Posted on 2010-02-26 09:32:31.0Z
Sender: 1385.4b82527c.1804289383@sybase.com
From: vtpcnk
Newsgroups: sybase.public.ase.general
Subject: Re: why did this dataserver crash?
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4b87952f.6491.1681692777@sybase.com>
References: <4b8278fa$1@forums-1-dub>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 26 Feb 2010 01:32:31 -0800
X-Trace: forums-1-dub 1267176751 10.22.241.41 (26 Feb 2010 01:32:31 -0800)
X-Original-Trace: 26 Feb 2010 01:32:31 -0800, 10.22.241.41
Lines: 577
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:29003
Article PK: 78241

here is the actual error log.

version : Adaptive Server Enterprise/12.5.4/EBF 15432
ESD#8/P/Sun_svr4/OS 5.8/ase1254/2105/64-bit/FBO/Sat Mar 22
14:38:37 2008

appreciate any insights as to why the server crashed :

00:00000:01003:2010/02/21 21:08:44.03 server Error: 696,
Severity: 21, State: 1
00:00000:01003:2010/02/21 21:08:44.03 server An attempt was
made to fetch logical page '10420344' in tempdb from cache
'tempd
bcache'. Page belongs to object '-45023282' and not to
object '-65732658'. Restart of SQL Server will clear the
error. Please
contact your System Administrator for help.
00:00000:01003:2010/02/21 21:08:44.03 server Starting
diagnostics for read failure:
00:00000:01003:2010/02/21 21:08:44.03 server Device
Information:
Device number = 103
Phyname =
/cfs/dblinks/fs/tempdb_data/tempdb_data_03.dat
00:00000:01003:2010/02/21 21:08:44.03 server Buffer
Information:
Buf addr = 0x1030a799540,
Mass addr = 0x1030a799540
Buf pageno = 10420344, Mass
pageno = 10420344, dbid = 2
00:00000:01003:2010/02/21 21:08:44.03 server
Buf virtpg = 1729256056,
Mass virtpg = 1729256056
Buf stat = 0x1, Mass stat =
0x40001008
Mass keep = 1, Mass awaited
= 0
00:00000:01003:2010/02/21 21:08:44.03 server Page
Information from first read attempt: Page read from cache
ppageno = 1042034
4, pobjid = -45023282, pindid = 0 pnextpg = 10420344,
pprevpg = 10420344 plevel = 0, pstat = 0x8000 pts_hi = 5,
pts_lo = -1541
592463
00:00000:01003:2010/02/21 21:08:44.03 server Page
Information from second read attempt: Page read from disk
ppageno = 1042034
4, pobjid = -45023282, pindid = 0 pnextpg = 10420344,
pprevpg = 10420344 plevel = 0, pstat = 0x8000 pts_hi = 5,
pts_lo = -1541
592463
00:00000:01003:2010/02/21 21:08:44.03 server SDES
Information:
dbid = 2, objid =
-65732658, scur.pageid = 10420344
sstat = 0x210, sstat2 = 0x0
suid = 1, cacheid = 7
00:00000:01003:2010/02/21 21:08:44.03 server PSS
Information:
pstat = 0x10000, pcurdb =
26, pspid = 1003
p2stat = 0x40001000, p3stat
= 0x800
plasterror = 696, preverror
= 0, pattention = 0
00:00000:01003:2010/02/21 21:08:44.03 server End
diagnostics for read failure:
00:00000:01003:2010/02/21 21:08:44.03 server
Error 3602 encountered .
00:00000:01003:2010/02/21 21:08:44.03 server Original error
was 696, severity 21, state 1
00:00000:01003:2010/02/21 21:08:44.03 kernel
************************************
00:00000:01003:2010/02/21 21:08:44.03 kernel SQL causing
error : \346
00:00000:01003:2010/02/21 21:08:44.03 kernel
************************************
00:00000:01003:2010/02/21 21:08:44.03 server SQL Text: \346
00:00000:01003:2010/02/21 21:08:44.03 kernel curdb = 26
tempdb = 2 pstat = 0x110000
00:00000:01003:2010/02/21 21:08:44.03 kernel lasterror =
696 preverror = 0 transtate = 3
00:00000:01003:2010/02/21 21:08:44.03 kernel curcmd = 193
program =
00:00000:01003:2010/02/21 21:08:44.03 kernel pc:
0x00000000809a288c pcstkwalk+0x28(0x000000000000270f,
0x0000010009519240, 0x
000000000000270f, 0x0000000000000002, 0x0000000081924000)
00:00000:01003:2010/02/21 21:08:44.03 kernel pc:
0x00000000809a2774 ucstkgentrace+0x1c8(0x000000000000270f,
0x000000005d5f00f
5, 0x0000000000000000, 0x000001004a398fd0,
0x0000010044aa75d8)
00:00000:01003:2010/02/21 21:08:44.03 kernel pc:
0x00000000809366b8 ucbacktrace+0xb0(0x0000000000000000,
0x0000000000000001,
0x000000000000001e, 0x0000010044abb7c4, 0x000000008112c400)
00:00000:01003:2010/02/21 21:08:44.03 kernel pc:
0x000000008024879c
terminate_process+0x1224(0x0000010044aa75d8, 0xffffffffff
ffffff, 0x00000000000002b8, 0x0000000000000015,
0x0000000000000001)
00:00000:01003:2010/02/21 21:08:44.03 kernel [Handler pc:
0x00000000802a556c ex_stop_recursion installed by the
following fun
ction:-]
00:00000:01003:2010/02/21 21:08:44.03 kernel pc:
0x00000000802a5ea8 ex_doprint+0x134(0x00000000000002b8,
0x0000000000000015,
0x0000000000000001, 0x000001000951b7f0, 0xffffffffbabababa)
00:00000:01003:2010/02/21 21:08:44.03 kernel pc:
0x00000000805d196c s_handle+0x1684(0x0000000000000006,
0x0000000000000015, 0
x0000000000000001, 0x0000000000009c00, 0x0000000000001000)
00:00000:01003:2010/02/21 21:08:44.03 kernel pc:
0x00000000802a9f58 ex_raise+0x20c(0x0000000000000015,
0x0000000000000001, 0x
0000000051eb8400, 0x0000000000000000, 0x0000010044aaf1c0)
00:00000:01003:2010/02/21 21:08:44.03 kernel pc:
0x00000000804264c8 wrongpage+0x7bc(0x000000000000000b,
0x0000010044ab7730, 0
x000001030acc8548, 0x0000000000000000, 0x0000000000000000)
00:00000:01003:2010/02/21 21:08:44.03 kernel pc:
0x00000000801be0c4
getpage_with_validation+0x189c(0x000001030a799540, 0x0000
000000000002, 0x0000000000000020, 0x000001030a799540,
0x0000000000001382)
00:00000:01003:2010/02/21 21:08:44.03 kernel pc:
0x0000000080237648
getpage_noscan_with_validation+0x70(0x0000000000004730, 0
x000001000951be8c, 0x0000000000000002, 0x0000000000000020,
0x000001000951bd8c)
00:00000:01003:2010/02/21 21:08:44.03 kernel pc:
0x0000000080240afc pg_latchoam+0x30(0x0000010044ab7730,
0x00000000009f0078,
0x000001000951be8c, 0x0000000000000002, 0x0000000000000020)
00:00000:01003:2010/02/21 21:08:44.04 kernel pc:
0x000000008035f1e0 pg_objdeall+0x538(0x000001013631ba48,
0x0000000000000000,
0x0000010044aa75d8, 0x0000000000000000, 0x0000000000000001)
00:00000:01003:2010/02/21 21:08:44.04 kernel pc:
0x00000000801e0098 closetable+0x2c0(0x0000010044ab7730,
0x0000000000000000,
0x0000000000000128, 0x0000000080808080, 0x0000000000ff0000)
00:00000:01003:2010/02/21 21:08:44.04 kernel pc:
0x00000000801e656c close_range+0x19c(0x0000010044ab2010,
0x0000000000000006,
0x0000000000000032, 0x000000000000000e, 0x0000000000000000)
00:00000:01003:2010/02/21 21:08:44.04 kernel pc:
0x00000000805d1a80 s_cleanframe+0x44(0x0000010044ab118c,
0x00000000000076a8,
0x0000000000007400, 0x0000000000000015, 0x0000000000000001)
00:00000:01003:2010/02/21 21:08:44.04 kernel pc:
0x00000000805d08a4 s_handle+0x5bc(0x0000000000000024,
0x0000000000000019, 0x
0000000000000000, 0x0000000000009c00, 0x0000000000001000)
00:00000:01003:2010/02/21 21:08:44.04 kernel pc:
0x00000000802a9f58 ex_raise+0x20c(0x0000000000000019,
0x0000000000000000, 0x
0000000051eb8400, 0x0000000000000000, 0x0000010044aaf1c0)
00:00000:01003:2010/02/21 21:08:44.04 kernel pc:
0x00000000805d1980 s_handle+0x1698(0x0000000000000006,
0x0000000000000015, 0
x0000000000000001, 0x0000000000009c00, 0x0000000000001000)

x0000000000000001, 0x0000000000009c00, 0x0000000000001000)
00:00000:01003:2010/02/21 21:08:44.04 kernel pc:
0x00000000802a9f58 ex_raise+0x20c(0x0000000000000015,
0x0000000000000001, 0x
0000000051eb8400, 0x0000000000000000, 0x0000010044aaf1c0)
00:00000:01003:2010/02/21 21:08:44.04 kernel pc:
0x00000000804264c8 wrongpage+0x7bc(0x000000000000000b,
0x0000010044ab7730, 0
x000001030acc8548, 0x0000000000000000, 0x0000000000000000)
00:00000:01003:2010/02/21 21:08:44.04 kernel pc:
0x00000000801be0c4
getpage_with_validation+0x189c(0x000001030a799540, 0x0000
000000000002, 0x0000000000000020, 0x000001030a799540,
0x0000000000001382)
00:00000:01003:2010/02/21 21:08:44.04 kernel pc:
0x0000000080237648
getpage_noscan_with_validation+0x70(0x0000000000004730, 0
x000001000951cd7c, 0x0000000000000002, 0x0000000000000020,
0x000001000951cc7c)
00:00000:01003:2010/02/21 21:08:44.04 kernel pc:
0x0000000080240afc pg_latchoam+0x30(0x0000010044ab7730,
0x00000000009f0078,
0x000001000951cd7c, 0x0000000000000002, 0x0000000000000020)
00:00000:01003:2010/02/21 21:08:44.04 kernel pc:
0x000000008035f1e0 pg_objdeall+0x538(0x000001013631ba48,
0x0000000000000000,
0x0000010044aa75d8, 0x0000000000000000, 0x0000000000000001)
00:00000:01003:2010/02/21 21:08:44.04 kernel pc:
0x00000000801e0098 closetable+0x2c0(0x0000010044ab7730,
0x0000000000000000,
0x0000000000000128, 0x0000000080808080, 0x0000000000ff0000)
00:00000:01003:2010/02/21 21:08:44.04 kernel pc:
0x00000000801e656c close_range+0x19c(0x0000010044ab2010,
0x0000000000000006,
0x0000000000000032, 0x000000000000000e, 0x0000000000000000)
00:00000:01003:2010/02/21 21:08:44.04 kernel pc:
0x00000000805d1a80 s_cleanframe+0x44(0x0000010044ab118c,
0x00000000000076a8,
0x0000000000007400, 0x0000000000000015, 0x0000000000000001)
00:00000:01003:2010/02/21 21:08:44.04 kernel pc:
0x00000000805d08a4 s_handle+0x5bc(0x0000000000000024,
0x0000000000000019, 0x
0000000000000000, 0x0000000000009c00, 0x0000000000001000)
00:00000:01003:2010/02/21 21:08:44.04 kernel pc:
0x00000000802a9f58 ex_raise+0x20c(0x0000000000000019,
0x0000000000000000, 0x
0000000051eb8400, 0x0000000000000000, 0x0000010044aaf1c0)
00:00000:01003:2010/02/21 21:08:44.04 kernel pc:
0x00000000805d1980 s_handle+0x1698(0x0000000000000006,
0x0000000000000015, 0
x0000000000000001, 0x0000000000009c00, 0x0000000000001000)
00:00000:01003:2010/02/21 21:08:44.04 kernel end of stack
trace, spid 1003, kpid 1566507253, suid 3138
00:00000:01003:2010/02/21 21:08:44.10 server Starting
diagnostics for read failure:
00:00000:01003:2010/02/21 21:08:44.10 server Device
Information:
Device number = 103
Phyname =
/cfs/dblinks/fs/tempdb_data/tempdb_data_03.dat
00:00000:01003:2010/02/21 21:08:44.10 server Buffer
Information:
Buf addr = 0x1030a799540,
Mass addr = 0x1030a799540
Buf pageno = 10420344, Mass
pageno = 10420344, dbid = 2
00:00000:01003:2010/02/21 21:08:44.10 server
Buf virtpg = 1729256056,
Mass virtpg = 1729256056
Buf stat = 0x1, Mass stat =
0x40001008
Mass keep = 1, Mass awaited
= 0

00:00000:01003:2010/02/21 21:08:44.10 server Page
Information from first read attempt: Page read from cache
ppageno = 1042034
4, pobjid = -45023282, pindid = 0 pnextpg = 10420344,
pprevpg = 10420344 plevel = 0, pstat = 0x8000 pts_hi = 5,
pts_lo = -1541
592463
00:00000:01003:2010/02/21 21:08:44.10 server Page
Information from second read attempt: Page read from disk
ppageno = 1042034
4, pobjid = -45023282, pindid = 0 pnextpg = 10420344,
pprevpg = 10420344 plevel = 0, pstat = 0x8000 pts_hi = 5,
pts_lo = -1541
592463
00:00000:01003:2010/02/21 21:08:44.10 server SDES
Information:
dbid = 2, objid =
-65732658, scur.pageid = 10420344
sstat = 0x210, sstat2 = 0x0
suid = 1, cacheid = 7
00:00000:01003:2010/02/21 21:08:44.10 server PSS
Information:
pstat = 0x110400, pcurdb =
26, pspid = 1003
p2stat = 0x40101000, p3stat
= 0x800
plasterror = 696, preverror
= 0, pattention = 0
00:00000:01003:2010/02/21 21:08:44.10 server End
diagnostics for read failure:
00:00000:01003:2010/02/21 21:08:44.10 kernel Stack overflow
detected: limit: 0x00000100095180d0, sp: 0x0000010009519308
00:00000:01003:2010/02/21 21:08:44.10 kernel *** Stack
guardword corrupted.
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x00000000809a288c pcstkwalk+0x28(0x000000000000270f,
0x0000010009518500, 0x
000000000000270f, 0x0000000000000002, 0x0000000081924000)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x00000000809a2774 ucstkgentrace+0x1c8(0x000000000000270f,
0x000000005d5f00f
5, 0x0000000000000000, 0x000001004a398fd0,
0x0000010044aa75d8)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x00000000809366b8 ucbacktrace+0xb0(0x0000000000000000,
0x0000000000000001,
0x00000100095180d0, 0x0000000000000010, 0x0000010009519308)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x000000008094c60c ucstackcrash+0xc8(0x0000000000000000,
0x0000000000000000,
0x0000000000000000, 0x000000000000001a, 0x00000000000003eb)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x00000000802a9fd0 ex_raise+0x284(0x0000000000000015,
0x0000000000000001, 0x
fffffffffd50ffce, 0xfffffffffc14ffce, 0x00000000009f0078)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x00000000804264c8 wrongpage+0x7bc(0x000000000000000b,
0x0000010044ab7730, 0
x000001030acc8548, 0x0000000000000000, 0x0000000000000000)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x00000000801be0c4
getpage_with_validation+0x189c(0x000001030a799540, 0x0000
000000000002, 0x0000000000000020, 0x000001030a799540,
0x0000000000001382)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x0000000080237648
getpage_noscan_with_validation+0x70(0x0000000000004730, 0
x0000010009519a6c, 0x0000000000000002, 0x0000000000000020,
0x000001000951996c)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x0000000080240afc pg_latchoam+0x30(0x0000010044ab7730,
0x00000000009f0078,
0x0000010009519a6c, 0x0000000000000002, 0x0000000000000020)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x000000008035f1e0 pg_objdeall+0x538(0x000001013631ba48,
0x0000000000000000,
0x0000010044aa75d8, 0x0000000000000000, 0x0000000000000001)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x000000008035f1e0 pg_objdeall+0x538(0x000001013631ba48,
0x0000000000000000,
0x0000010044aa75d8, 0x0000000000000000, 0x0000000000000001)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x00000000801e0098 closetable+0x2c0(0x0000010044ab7730,
0x0000000000000000,
0x0000000000000000, 0x0000000000000000, 0x000001004a344800)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x00000000801e656c close_range+0x19c(0x0000010044ab2010,
0x0000000000000006,
0x0000000000000032, 0x000000000000000e, 0x0000000000000000)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x00000000805d1a80 s_cleanframe+0x44(0x0000010044ab118c,
0x00000000000076a8,
0x0000000000007400, 0x000000000000a800, 0x0000000000000000)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x0000000080292910 clean_process+0x4ec(0x00000000000076a8,
0x0000010044aaec8
0, 0x0000000081647000, 0x0000000081647258,
0x0000000000000005)
00:00000:01003:2010/02/21 21:08:44.10 kernel [Handler pc:
0x000000008029327c cleanerr installed by the following
function:-]
00:00000:01003:2010/02/21 21:08:44.10 kernel [Handler pc:
0x00000000802aa208 hdl_backout installed by the following
function:
-]
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x0000000080291fc8 kill_proc+0xc30(0x0000010044ab1fe8,
0x0000000000009db4, 0
x0000010044ab1c48, 0x0000010044ab1c50, 0x0000000000000000)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x0000000080247aa8
terminate_process+0x530(0x0000010044aa75d8, 0xfffffffffff
fffff, 0x00000000000002b8, 0x0000000000000015,
0x0000000000000001)
00:00000:01003:2010/02/21 21:08:44.10 kernel [Handler pc:
0x00000000802a556c ex_stop_recursion installed by the
following fun
ction:-]
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x00000000802a5ea8 ex_doprint+0x134(0x00000000000002b8,
0x0000000000000015,
0x0000000000000001, 0x000001000951b7f0, 0xffffffffbabababa)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x00000000805d196c s_handle+0x1684(0x0000000000000006,
0x0000000000000015, 0
x0000000000000001, 0x0000000000009c00, 0x0000000000001000)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x00000000802a9f58 ex_raise+0x20c(0x0000000000000015,
0x0000000000000001, 0x
0000000051eb8400, 0x0000000000000000, 0x0000010044aaf1c0)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x00000000804264c8 wrongpage+0x7bc(0x000000000000000b,
0x0000010044ab7730, 0
x000001030acc8548, 0x0000000000000000, 0x0000000000000000)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x00000000801be0c4
getpage_with_validation+0x189c(0x000001030a799540, 0x0000
000000000002, 0x0000000000000020, 0x000001030a799540,
0x0000000000001382)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x0000000080237648
getpage_noscan_with_validation+0x70(0x0000000000004730, 0
x000001000951be8c, 0x0000000000000002, 0x0000000000000020,
0x000001000951bd8c)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x0000000080240afc pg_latchoam+0x30(0x0000010044ab7730,
0x00000000009f0078,
0x000001000951be8c, 0x0000000000000002, 0x0000000000000020)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x000000008035f1e0 pg_objdeall+0x538(0x000001013631ba48,
0x0000000000000000,
0x0000010044aa75d8, 0x0000000000000000, 0x0000000000000001)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x00000000801e0098 closetable+0x2c0(0x0000010044ab7730,
0x0000000000000000,
0x0000000000000128, 0x0000000080808080, 0x0000000000ff0000)
@
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x00000000801e0098 closetable+0x2c0(0x0000010044ab7730,
0x0000000000000000,
0x0000000000000128, 0x0000000080808080, 0x0000000000ff0000)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x00000000801e656c close_range+0x19c(0x0000010044ab2010,
0x0000000000000006,
0x0000000000000032, 0x000000000000000e, 0x0000000000000000)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x00000000805d1a80 s_cleanframe+0x44(0x0000010044ab118c,
0x00000000000076a8,
0x0000000000007400, 0x0000000000000015, 0x0000000000000001)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x00000000805d08a4 s_handle+0x5bc(0x0000000000000024,
0x0000000000000019, 0x
0000000000000000, 0x0000000000009c00, 0x0000000000001000)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x00000000802a9f58 ex_raise+0x20c(0x0000000000000019,
0x0000000000000000, 0x
0000000051eb8400, 0x0000000000000000, 0x0000010044aaf1c0)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x00000000805d1980 s_handle+0x1698(0x0000000000000006,
0x0000000000000015, 0
x0000000000000001, 0x0000000000009c00, 0x0000000000001000)
00:00000:01003:2010/02/21 21:08:44.10 kernel end of stack
trace, spid 1003, kpid 1566507253, suid 3138
00:00000:01003:2010/02/21 21:08:44.10 kernel *** Stack
corrupted, server aborting.
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x00000000809a288c pcstkwalk+0x28(0x000000000000270f,
0x0000010009518240, 0x
000000000000270f, 0x0000000000000002, 0x0000000081924000)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x00000000809a2774 ucstkgentrace+0x1c8(0x000000000000270f,
0x000000005d5f00f
5, 0x0000000000000000, 0x000001004a398fd0,
0x0000010044aa75d8)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x00000000809366b8 ucbacktrace+0xb0(0x0000000000000000,
0x0000000000000001,
0x0000000000000000, 0x0000000000000000, 0x0000010044aa75d8)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x000000008094c728 keipanic+0x60(0x000000000000753b,
0x00000000000003eb, 0x0
00000005d5f00f5, 0x0000000000000c42, 0x0000010009519308)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x000000008094c614 ucstackcrash+0xd0(0x0000000000000000,
0x0000000000000000,
0x0000000000000000, 0x000000000000001a, 0x00000000000003eb)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x00000000802a9fd0 ex_raise+0x284(0x0000000000000015,
0x0000000000000001, 0x
fffffffffd50ffce, 0xfffffffffc14ffce, 0x00000000009f0078)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x00000000804264c8 wrongpage+0x7bc(0x000000000000000b,
0x0000010044ab7730, 0
x000001030acc8548, 0x0000000000000000, 0x0000000000000000)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x00000000801be0c4
getpage_with_validation+0x189c(0x000001030a799540, 0x0000
000000000002, 0x0000000000000020, 0x000001030a799540,
0x0000000000001382)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x0000000080237648
getpage_noscan_with_validation+0x70(0x0000000000004730, 0
x0000010009519a6c, 0x0000000000000002, 0x0000000000000020,
0x000001000951996c)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x0000000080240afc pg_latchoam+0x30(0x0000010044ab7730,
0x00000000009f0078,
0x0000010009519a6c, 0x0000000000000002, 0x0000000000000020)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x000000008035f1e0 pg_objdeall+0x538(0x000001013631ba48,
0x0000000000000000,
0x0000010044aa75d8, 0x0000000000000000, 0x0000000000000001)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x00000000801e0098 closetable+0x2c0(0x0000010044ab7730,
0x0000000000000000,
0x0000000000000000, 0x0000000000000000, 0x000001004a344800)

00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x00000000801e0098 closetable+0x2c0(0x0000010044ab7730,
0x0000000000000000,
0x0000000000000000, 0x0000000000000000, 0x000001004a344800)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x00000000801e656c close_range+0x19c(0x0000010044ab2010,
0x0000000000000006,
0x0000000000000032, 0x000000000000000e, 0x0000000000000000)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x00000000805d1a80 s_cleanframe+0x44(0x0000010044ab118c,
0x00000000000076a8,
0x0000000000007400, 0x000000000000a800, 0x0000000000000000)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x0000000080292910 clean_process+0x4ec(0x00000000000076a8,
0x0000010044aaec8
0, 0x0000000081647000, 0x0000000081647258,
0x0000000000000005)
00:00000:01003:2010/02/21 21:08:44.10 kernel [Handler pc:
0x000000008029327c cleanerr installed by the following
function:-]
00:00000:01003:2010/02/21 21:08:44.10 kernel [Handler pc:
0x00000000802aa208 hdl_backout installed by the following
function:
-]
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x0000000080291fc8 kill_proc+0xc30(0x0000010044ab1fe8,
0x0000000000009db4, 0
x0000010044ab1c48, 0x0000010044ab1c50, 0x0000000000000000)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x0000000080247aa8
terminate_process+0x530(0x0000010044aa75d8, 0xfffffffffff
fffff, 0x00000000000002b8, 0x0000000000000015,
0x0000000000000001)
00:00000:01003:2010/02/21 21:08:44.10 kernel [Handler pc:
0x00000000802a556c ex_stop_recursion installed by the
following fun
ction:-]
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x00000000802a5ea8 ex_doprint+0x134(0x00000000000002b8,
0x0000000000000015,
0x0000000000000001, 0x000001000951b7f0, 0xffffffffbabababa)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x00000000805d196c s_handle+0x1684(0x0000000000000006,
0x0000000000000015, 0
x0000000000000001, 0x0000000000009c00, 0x0000000000001000)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x00000000802a9f58 ex_raise+0x20c(0x0000000000000015,
0x0000000000000001, 0x
0000000051eb8400, 0x0000000000000000, 0x0000010044aaf1c0)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x00000000804264c8 wrongpage+0x7bc(0x000000000000000b,
0x0000010044ab7730, 0
x000001030acc8548, 0x0000000000000000, 0x0000000000000000)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x00000000801be0c4
getpage_with_validation+0x189c(0x000001030a799540, 0x0000
000000000002, 0x0000000000000020, 0x000001030a799540,
0x0000000000001382)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x0000000080237648
getpage_noscan_with_validation+0x70(0x0000000000004730, 0
x000001000951be8c, 0x0000000000000002, 0x0000000000000020,
0x000001000951bd8c)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x0000000080240afc pg_latchoam+0x30(0x0000010044ab7730,
0x00000000009f0078,
0x000001000951be8c, 0x0000000000000002, 0x0000000000000020)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x000000008035f1e0 pg_objdeall+0x538(0x000001013631ba48,
0x0000000000000000,
0x0000010044aa75d8, 0x0000000000000000, 0x0000000000000001)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x00000000801e0098 closetable+0x2c0(0x0000010044ab7730,
0x0000000000000000,
0x0000000000000128, 0x0000000080808080, 0x0000000000ff0000)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x00000000801e656c close_range+0x19c(0x0000010044ab2010,
0x0000000000000006,
0x0000000000000032, 0x000000000000000e, 0x0000000000000000)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x00000000805d1a80 s_cleanframe+0x44(0x0000010044ab118c,
0x00000000000076a8,
0x0000000000007400, 0x0000000000000015, 0x0000000000000001)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x00000000805d08a4 s_handle+0x5bc(0x0000000000000024,
0x0000000000000019, 0x
0000000000000000, 0x0000000000009c00, 0x0000000000001000)
00:00000:01003:2010/02/21 21:08:44.10 kernel pc:
0x00000000802a9f58 ex_raise+0x20c(0x0000000000000019,
0x0000000000000000, 0x
0000000051eb8400, 0x0000000000000000, 0x0000010044aaf1c0)
00:00000:01003:2010/02/21 21:08:44.10 kernel end of stack
trace, spid 1003, kpid 1566507253, suid 3138
00:00000:01003:2010/02/21 21:08:44.10 kernel ueshutdown:
exiting
00:00000:01003:2010/02/21 21:08:44.10 kernel RTDS Server is
already down.
00:00000:01003:2010/02/21 21:08:44.10 kernel Abnormal exit
detected - SQL Server process level execution bindings will
be cle
ared on startup.


vtpcnk Posted on 2010-02-22 08:26:15.0Z
Sender: ec2.4b823ee9.1804289383@sybase.com
From: vtpcnk
Newsgroups: sybase.public.ase.general
Subject: Re: why did this dataserver crash?
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4b823fa7.edf.1681692777@sybase.com>
References: <4b823e40.ea4.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 22 Feb 2010 00:26:15 -0800
X-Trace: forums-1-dub 1266827175 10.22.241.41 (22 Feb 2010 00:26:15 -0800)
X-Original-Trace: 22 Feb 2010 00:26:15 -0800, 10.22.241.41
Lines: 12
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:28986
Article PK: 78225

btw what i am actually asking is :

the stacktrace due to sysmon started like 9 hours before the
crash. and at the end i am not sure if this was the reason
for the crash. towards the end the 696 error is repeated but
without any mention of the process involved (not sure if it
is the same sysmon).

but i have seen 696 errors on a lot of servers which did not
crash the server. so why did this? or is it actually the
problem associated with the stack trace which cause the
server to crash?


"Mark A. Parsons" <iron_horse Posted on 2010-02-22 12:23:40.0Z
From: "Mark A. Parsons" <iron_horse@no_spamola.compuserve.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
Newsgroups: sybase.public.ase.general
Subject: Re: why did this dataserver crash?
References: <4b823e40.ea4.1681692777@sybase.com> <4b823fa7.edf.1681692777@sybase.com>
In-Reply-To: <4b823fa7.edf.1681692777@sybase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 100218-0, 02/18/2010), Outbound message
X-Antivirus-Status: Clean
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4b82774c$1@forums-1-dub>
Date: 22 Feb 2010 04:23:40 -0800
X-Trace: forums-1-dub 1266841420 10.22.241.152 (22 Feb 2010 04:23:40 -0800)
X-Original-Trace: 22 Feb 2010 04:23:40 -0800, vip152.sybase.com
Lines: 38
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:28988
Article PK: 78226

I suggest you open a case with Sybase Tech Support.

-------------------

Can a 696 crash a dataserver? *shrug* I don't recall seeing this happen before, but I can't rule it out.

Can a stack corruption crash a dataserver? yes

Did sysmon cause the crash? *shrug* Yes, no, maybe. With stack corruption it's not always the reporting spid that has
the problem (eg, the reporting spid may be the victim of another spid overwriting it's stack).

You haven't provided your ASE version so it's hard to tell if you've run into a known issue.

You've only provided snippets of what's in your ASE errorlog. You've left out stack trace details which could help in
tracking down the issue. You may have misread parts of the errorlog (ie, it's better for someone to have access to the
full text of the errorlog than working with a rehash of what someone else thinks is important). You may have missed
some important entries in the errorlog (easy to do if there's a large volume of entries to sort through).

'course, solved cases @ sybase.com is on the fritz so even if we had your ASE version and the entire contents of your
errorlog we may not be able to help.

Sybase Tech Support are the folks who have the best chance of tracking down the cause of your dataserver crash.

vtpcnk wrote:
> btw what i am actually asking is :
>
> the stacktrace due to sysmon started like 9 hours before the
> crash. and at the end i am not sure if this was the reason
> for the crash. towards the end the 696 error is repeated but
> without any mention of the process involved (not sure if it
> is the same sysmon).
>
> but i have seen 696 errors on a lot of servers which did not
> crash the server. so why did this? or is it actually the
> problem associated with the stack trace which cause the
> server to crash?