Symptom
- During a reboot of ASE does not come up
- sddone errors are reported in the ASE error log
server Opening Master Database ...
kernel block 52:
kernel sddone: 4096 bytes passed, 409
server Opening Master Database ...
kernel sddone: write error on virtual disk 0 block 52:
kernel sddone: 4096 bytes passed, 4096 returned on write for virt disk 0 block 52
- Error 823 is reported in the ASE error log:
server Error: 823, Severity: 24, State: 2
server I/O error detected during wait for BUF=0x0x00002ab28aa5bf10, MASS=0x0x00002ab28aa5bf10, Buf#=0, page=0x0x00002aacd75bb000, dbid=1, Mass vdevno=0, vpage=52, Buf lpage=24, Mass stat=0x4091108, Buf stat=0x1, size=4096, cid=0 ('default data cache'), Pinned xdes=0x(nil), spid=0.
- Error 834 is reported in the ASE error log with the following stack trace:
server Error: 834, Severity: 20, State: 4
server Illegal attempt to clean buffer: BUF=0x0x00002ab28aa5bf10, MASS=0x0x00002ab28aa5bf10, Buf#=0, page=0x0x00002aacd75bb000, dbid=1, Mass vdevno=0, vpage=52, Buf lpage=24, Mass stat=0 x4091108, Buf stat=0x1, size=4096, cid=0 ('default data cache'), Pinned xdes=0x(nil), spid=0.
kernel ************************************
server SQL Text: [no text]
kernel curdb = 0 tempdb = 0 pstat = 0x0 p2stat = 0x100000
kernel p3stat = 0x800 p4stat = 0x0 p5stat = 0x0 p6stat = 0x200000 p7stat = 0x10000
kernel lasterror = 834 preverror = 0 transtate = 1
kernel curcmd = 0 program =
kernel extended error information: hostname: login:
kernel pc: 0x0000000000cfd3a4 ex_raise+0x324()
kernel pc: 0x0000000001b85102 cm_dbclean+0x892()
kernel pc: 0x0000000000b6d911 bufdbclean+0x71()
kernel pc: 0x0000000001431938 dbt_removeall+0x59()
kernel pc: 0x0000000001b99761 dbt_get+0xb51()
kernel pc: 0x0000000000b9455b dbt_get_with_statuscheck+0x1b()
kernel pc: 0x0000000000b87b87 dbcontext_change+0x37()
kernel pc: 0x0000000000b88179 usedb+0x39()
kernel pc: 0x00000000007525d9 dsinit+0x3f9()
kernel end of stack trace, spid 2, kpid 1966110, suid 0
kernel ueshutdown: exiting
kernel Instance inst02(2) is shutting down, disk access is being fenced off from that instance
kernel iof_release_device: 0 number of database devices mapped to this fence device /dev/sg106
kernel Abnormal exit detected - ASE process level execution bindings will be cleared on startup.
- Other information found - sd 3 - reservation conflict
Jan 9 15:19:45 inst02 kernel: sd 3:0:1:22: reservation conflict
Jan 9 15:19:45 inst02 kernel: sd 3:0:0:22: reservation conflict
Jan 9 15:19:45 inst02 kernel: sd 3:0:0:22: reservation conflict
Jan 9 15:19:45 inst02 kernel: sd 3:0:1:22: reservation conflict
Jan 9 15:19:45 inst02 kernel: sd 3:0:1:22: reservation conflict
Jan 9 15:19:45 inst02 kernel: sd 3:0:0:22: reservation conflict
Jan 9 15:19:45 inst02 kernel: sd 3:0:0:22: reservation conflict
- No messages in var logs(OS error logs) about sd3 being unavailable
Read more...
Environment
Sybase Adaptive Server Enterprise (ASE) Cluster Edition (CE) 15.5 ESD4
Product
Keywords
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.