Symptom
-
ASE stops accepting connections following a disk error in the sddostats routine.
- Connections start failing after the following stack trace was reported in the ASE log while dbcc usedextents was running:
00:0003:00000:00874:2017/03/30 09:20:17.01 server DBCC TRACEON 3604, SPID 874
00:0011:00000:00000:2017/03/30 09:20:21.16 kernel sddone: read error on virtual disk 3 block 48747520:
00:0011:00000:00000:2017/03/30 09:20:21.16 kernel sddone: Bad address
00:0011:00000:00000:2017/03/30 09:20:21.16 kernel Current process (0x0) infected with signal 11 (SIGSEGV)
00:0011:00000:00000:2017/03/30 09:20:21.16 kernel Address 0x0000000081770cf0 (sddostats+0x3c), siginfo (code, address) = (1, 0x000000000000000c)
00:0011:00000:00000:2017/03/30 09:20:21.16 kernel **** Saved signal context (0xffffffff78dfb2d0): ****
00:0011:00000:00000:2017/03/30 09:20:21.16 kernel uc_flags: 0x2f, uc_link: 0x0
00:0011:00000:00000:2017/03/30 09:20:21.16 kernel uc_sigmask: 0xefbe7877 0xfff7 0x0 0x0
00:0011:00000:00000:2017/03/30 09:20:21.16 kernel uc_stack: ss_sp: 0xffffffff78c00000, ss_size: 0x2080768, ss_flags: 0x0
00:0011:00000:00000:2017/03/30 09:20:21.16 kernel General Registers (uc_mcontext.gregs):
00:0011:00000:00000:2017/03/30 09:20:21.16 kernel PC : 0000000081770cf0 (sddostats+0x3c)
00:0011:00000:00000:2017/03/30 09:20:21.16 kernel Next PC : 0000000081770cf4 (sddostats+0x40)
00:0011:00000:00000:2017/03/30 09:20:21.16 kernel CCR : 0000000000000000 Y : 0000000000000000
00:0011:00000:00000:2017/03/30 09:20:21.16 kernel ASI : 0000000000000082 FPRS : 0000000000000007
00:0011:00000:00000:2017/03/30 09:20:21.16 kernel g0 : 0000000000000000 g1 : 0000000000000004 g2 : 0000000000000000
00:0011:00000:00000:2017/03/30 09:20:21.16 kernel g3 : 0000000000000000 g4 : 000000000000000b g5 : 0000000083835c00
00:0011:00000:00000:2017/03/30 09:20:21.16 kernel g6 : 0000000000000000 g7 : ffffffff7c20d240
00:0011:00000:00000:2017/03/30 09:20:21.16 kernel o0 : 000001000000f828 o1 : 0000000000000000 o2 : 0000010000000000
00:0011:00000:00000:2017/03/30 09:20:21.16 kernel o3 : 00000101828f3000 o4 : 0000000082fcf118 o5 : 000001000000f828
00:0011:00000:00000:2017/03/30 09:20:21.16 kernel o6 : ffffffff78dfaeb1 o7 : 0000000081769f88
00:0011:00000:00000:2017/03/30 09:20:21.16 kernel Windowed Registers (from stack frame ffffffff78dfb6b0):
00:0011:00000:00000:2017/03/30 09:20:21.16 kernel l0 : 0000000000000000 l1 : 0000000000008000 l2 : 0000000000000001
00:0011:00000:00000:2017/03/30 09:20:21.16 kernel l3 : 0000000000000000 l4 : 0000000000000000 l5 : 0000000000000047
00:0011:00000:00000:2017/03/30 09:20:21.16 kernel l6 : 0000000000000000 l7 : 0000000000000000
00:0011:00000:00000:2017/03/30 09:20:21.16 kernel i0 : 000001003e837950 i1 : 000001003e837950 i2 : 0000000000000000
00:0011:00000:00000:2017/03/30 09:20:21.16 kernel i3 : 0000000000020000 i4 : 0000000000420001 i5 : 0000000082fe1400
00:0011:00000:00000:2017/03/30 09:20:21.16 kernel i6 : ffffffff78dfaf61 i7 : 000000008054c510
00:0011:00000:00000:2017/03/30 09:20:21.16 kernel previous stack frame : ffffffff78dfb760
00:0011:00000:00000:2017/03/30 09:20:21.16 kernel **** end of signal context ****
00:0011:00000:00000:2017/03/30 09:20:21.16 kernel Run to completion task iocRunController(1bbbab0) exception 11
00:0011:00000:00000:2017/03/30 09:20:21.16 kernel pc: 0x000000008176da5c nthrd_backtrace+0x18(0x000000000000001b, 0x0000000000000001, 0xffffffff78dfb2d0, 0x0000000083358400, 0x0000010001cdee08)
00:0011:00000:00000:2017/03/30 09:20:21.16 kernel pc: 0x00000000817a4ae4 krtctskException+0xac(0x0000010001cdedf0, 0x000000000000000b, 0x0000000000000001, 0xffffffff78dfb2d0, 0xffffffff7c20d240)
00:0011:00000:00000:2017/03/30 09:20:21.16 kernel pc: 0x00000000817baa2c kisignal+0x544(0x000000000000000b, 0xffffffff78dfb5b0, 0xffffffff78dfb2d0, 0x000000008343c688, 0xffffffff78dfab7c)
00:0011:00000:00000:2017/03/30 09:20:21.16 kernel pc: 0x0000000081770cf0 sddostats+0x3c(0x000001003e837950, 0x000001003e837950, 0x0000000000000000, 0x0000000000020000, 0x0000000000420001)
00:0011:00000:00000:2017/03/30 09:20:21.16 kernel pc: 0x000000008054c510 _$o1cexxI0.sdfinish_normal(0x000001003e837950, 0xfffffffffffffffc, 0x000000000000f58b, 0x0000000000002400, 0x0000010000020300)
00:0011:00000:00000:2017/03/30 09:20:21.16 kernel pc: 0x00000000804534f0 sddone_normal+0x30(0x0000000000009c00, 0xfffffffffffffffc, 0x0000000002e7d400, 0x000001003e837950, 0x0000010000a93c68)
00:0011:00000:00000:2017/03/30 09:20:21.16 kernel pc: 0x000000008045339c blkioComplete+0x7c(0x000001003e837950, 0x0000000000010000, 0x0000000000000001, 0x0000000000000002, 0xfffffffffffffffc)
00:0011:00000:00000:2017/03/30 09:20:21.16 kernel pc: 0x0000000080453784 kdcProcessCompletions+0x104(0x0000010001bbbab0, 0x000001003e837950, 0x0000010001d681f0, 0x0000010001bbbce0, 0x000001003ebb1bc8)
00:0011:00000:00000:2017/03/30 09:20:21.16 kernel pc: 0x00000000804327a0 udcPoll+0x160(0x0000000000000000, 0x0000000000000000, 0x0000010001bbbab0, 0x00000000000025cc, 0x0000010001bbbcd0)
00:0011:00000:00000:2017/03/30 09:20:21.16 kernel pc: 0x00000000805715cc _$o1ceyaU0.iocRunController+0x2c(0x0000010001bbbab0, 0x0000000083399160, 0x0000000000000002, 0x000000000000002b, 0x0000000000000004)
00:0011:00000:00000:2017/03/30 09:20:21.16 kernel pc: 0x00000000817a49a8 krtctskRun+0x38(0x0000010001cdedf0, 0x0000010001ba6ab0, 0x000000008066c4b8, 0x0000010001cdedf0, 0x000000005254534b)
00:0011:00000:00000:2017/03/30 09:20:21.16 kernel pc: 0x000000008069a8e8 ktskRun+0x68(0x0000010001cdedf0, 0x0000010001c730f0, 0x000000005441534b, 0x000000005441534b, 0xffffffff7c20d238)
00:0011:00000:00000:2017/03/30 09:20:21.16 kernel pc: 0x00000000817f21ac kt__RTCMain+0xbc(0x0000010001c730f0, 0x0000000000000004, 0x0000000000000000, 0x0000000000000000, 0xfffffffffffffff0)
00:0011:00000:00000:2017/03/30 09:20:21.16 kernel pc: 0x00000000818445e8 thread_create_handler+0xa4(0x0000000081fb6000, 0xfffffffffffffff0, 0x0000010001c730f0, 0x00000000817f21e8, 0x0000000000000000)
Read more...
Environment
Any version of ASE.
Product
SAP Adaptive Server Enterprise 16.0
Keywords
sddone: read error, sddone: Bad address, hardware issue, ASE 16 , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview