免费注册 查看新帖 |

Chinaunix

  平台 论坛 博客 文库
最近访问板块 发新帖
查看: 4998 | 回复: 6
打印 上一主题 下一主题

这几天数据库进程经常掉死,急询原因! [复制链接]

论坛徽章:
0
跳转到指定楼层
1 [收藏(0)] [报告]
发表于 2007-07-24 09:56 |只看该作者 |倒序浏览
10可用积分
日志如下:



00:07/07/21 16:36:18.78 kernel  current process (0x370037) infected with 11
00:07/07/21 16:36:18.79 kernel  Address 0x37fe5 (cm_bufunhash___1+0x51), siginfo (code, address) = (1, 0xfffffdac)
00:07/07/21 16:36:18.79 kernel  ************************************
00:07/07/21 16:36:18.79 kernel  SQL causing error : insert c_dev_history_log values (1,4,2,3617,40,0.000000,1,'2007/07/21 07:13:44',0,0)
00:07/07/21 16:36:18.79 kernel  curdb = 5 pstat = 0x10500 lasterror = 0
00:07/07/21 16:36:18.79 kernel  preverror = 0 transtate = 0
00:07/07/21 16:36:18.79 kernel  curcmd = 195 program =                              
00:07/07/21 16:36:18.79 kernel  Spinlocks held by  kpid 3604535

00:07/07/21 16:36:18.79 kernel  Spinlock Resource->rcaches->cspin at address 8000bda0 owned by 370037
00:07/07/21 16:36:18.79 kernel  End of spinlock display.
00:07/07/21 16:36:18.79 kernel  pc: 0x2e4b85 ucbacktrace+0x55(0x0,0x1,0x80231cfc,0xfffffdac,0xb)
00:07/07/21 16:36:18.79 kernel  pc: 0x26d0 terminate_process+0x250(0x0,0xffffffff,0x120,0x0,0x3a9b2)
00:07/07/21 16:36:18.79 kernel  pc: 0x2fb95f kisignal+0x9f(0xb,0x80231ef4,0x80231cf4,0x0,0x0)
00:07/07/21 16:36:18.79 kernel  pc: 0x351a7c sigismember+0x64(0x80898000,0x1,0x802feac0,0x0,0x802321b
00:07/07/21 16:36:18.79 kernel  pc: 0x2f830 bufgrab___1+0x2ec(0x802feac0,0x5,0x802feac0,0x0,0x802321b
00:07/07/21 16:36:18.79 kernel  pc: 0x1c8ea0 getpage___1+0x52c(0x80232780,0x80962000,0x802321b8,0x0,0x80232214)
00:07/07/21 16:36:18.80 kernel  pc: 0x1c9079 getpage_noscan+0x39(0x802feac0,0x802321b8,0x80232780,0x8099af20,0x0)
00:07/07/21 16:36:18.80 kernel  pc: 0x1b9f2b linksplit___1+0xe7(0x80232780,0x80232780,0x80962000,0x80232780,0x802feac0)
00:07/07/21 16:36:18.80 kernel  pc: 0x1cf1e3 insnewpg+0x53(0x80232780,0x1ba6e7,0x802feac0,0x80232604,0x5)
00:07/07/21 16:36:18.80 kernel  pc: 0x1babcd datasplit+0x73d(0x80232780,0x3,0x802feac0,0x2c,0x802327fc)
00:07/07/21 16:36:18.80 kernel  pc: 0x1cdc59 cinsert___1+0x2bd(0x80232814,0x1cd478,0x802cbef0,0x802327fc,0x0)
00:07/07/21 16:36:18.80 kernel  pc: 0x1cd4cb insert+0x14b(0x802feac0,0x807b0580,0x2c,0x1,0x0)
00:07/07/21 16:36:18.80 kernel  pc: 0x1aae61 run+0xe481(0x807ab3d4,0x807ab530,0x80233290,0x803bf708,0x0)
00:07/07/21 16:36:18.80 kernel  pc: 0x1842bb exec_eop___1+0x18df(0x803bf708,0x807ab3d4,0x0,0x0,0x803bf70
00:07/07/21 16:36:18.80 kernel  [Handler pc: 0x186500 execerr(num=9500, sev=0) installed by the following function]
00:07/07/21 16:36:18.80 kernel  [Handler pc: 0x186500 execerr(num=500, sev=0) installed by the following function]
00:07/07/21 16:36:18.80 kernel  [Handler pc: 0xc4270 aritherr(num=0, sev=0) installed by the following function]
00:07/07/21 16:36:18.80 kernel  pc: 0x181f7f execute+0xa8f(0x807ab37c,0x807ab3d4,0xc3,0x80233290,0xffff00ff)
00:07/07/21 16:36:18.80 kernel  pc: 0xd7587 s_execute+0x2267(0x803bf708,0x803bf708,0x802333c4,0x0,0x0)
00:07/07/21 16:36:18.80 kernel  [Handler pc: 0xe2070 s_handle(num=0, sev=0) installed by the following function]
00:07/07/21 16:36:18.80 kernel  pc: 0xdfa70 sequencer+0xc70(0x802ad000,0x290c33,0xffffffff,0x4,0x80)
00:07/07/21 16:36:18.80 kernel  pc: 0x21ff4f tdsrecv_language+0x31f(0x0,0x803bf708,0x0,0x0,0x0)
00:07/07/21 16:36:18.80 kernel  [Handler pc: 0xf0c50 hdl_backout(num=3600, sev=25) installed by the following function]
00:07/07/21 16:36:18.80 kernel  [Handler pc: 0x173a30 ut_handle(num=700, sev=0) installed by the following function]
00:07/07/21 16:36:18.80 kernel  pc: 0x20b3a6 conn_hdlr+0x16b6(0x2,0x802336c0,0x6a006a,0x0,0x0)
00:07/07/21 16:36:18.80 kernel  pc: 0x2f8e30 kpexit(0x0,0x0,0x5374616b,0x0,0x0)
00:07/07/21 16:36:18.80 kernel  pc: 0x6a006a frexp+0x346236(0x5374616b,0x0,0x0,0x0,0x0)
00:07/07/21 16:36:18.80 kernel  end of stack trace, spid 7, kpid 3604535, suid 3
00:07/07/21 16:36:18.80 kernel  ueshutdown: exiting
00:07/07/21 16:36:18.81 kernel  os_detach_region: shmdt(0x80000000): Device busy.
00:07/07/22 00:48:24.47 kernel  Using config area from primary master device.
00:07/07/22 00:48:24.47 kernel  Warning: Using default file '/sybase/SYBASE.cfg' since a configuration file was not specified. Specify a configuration file name in the RUNSERVER file to avoid this message.
00:07/07/22 00:48:24.48 kernel  Using 11000 file descriptors.
00:07/07/22 00:48:24.48 kernel  SQL Server/11.0.3/P/SCO/SCO_SV r3.2v5.0.2/2/OPT/Fri Jul 18 19:10:23 PDT 1997
00:07/07/22 00:48:24.48 kernel  Confidential property of Sybase, Inc.
00:07/07/22 00:48:24.48 kernel  (c) Copyright Sybase Inc., 1987, 1997.
00:07/07/22 00:48:24.48 kernel  All rights reserved.
00:07/07/22 00:48:24.48 kernel   
00:07/07/22 00:48:24.48 kernel  Use, duplication, or disclosure by the United States Government
00:07/07/22 00:48:24.48 kernel  is subject to restrictions as set forth in FAR subparagraphs
00:07/07/22 00:48:24.48 kernel  52.227-19(a)-(d) for civilian agency contracts and DFARS
00:07/07/22 00:48:24.48 kernel  252.227-7013(c) (1) (ii) for Department of Defense contracts.
00:07/07/22 00:48:24.48 kernel  Sybase reserves all unpublished rights under the copyright
00:07/07/22 00:48:24.48 kernel  laws of the United States.
00:07/07/22 00:48:24.48 kernel  Sybase, Inc. 6475 Christie Avenue, Emeryville, CA 94608 USA.
00:07/07/22 00:48:24.48 kernel  Using '/sybase/SYBASE.cfg' for configuration information.
00:07/07/22 00:48:24.48 kernel  Logging SQL Server messages in file '/sybase/install/errorlog'
.
00:07/07/22 00:48:24.48 kernel  Network and device connection limit is 10990.
00:07/07/22 00:48:24.48 server  Number of proc buffers allocated: 835.
00:07/07/22 00:48:24.48 server  Number of blocks left for proc headers: 884.
00:07/07/22 00:48:24.48 server  Memory allocated for the default data cache cache: 996 Kb
00:07/07/22 00:48:24.48 server  Size of the 2K memory pool: 996 Kb
00:07/07/22 00:48:24.48 kernel  Initializing virtual device 0, '/dev/rdb0'
00:07/07/22 00:48:24.48 kernel  Virtual device 0 started using asynchronous i/o.
00:07/07/22 00:48:24.48 server  No active traceflags
00:07/07/22 00:48:24.48 server  Opening Master Database ...
00:07/07/22 00:48:24.49 server  Loading SQL Server's default sort order and character set
00:07/07/22 00:48:24.50 kernel  ninit:0: listener type: master
00:07/07/22 00:48:24.50 kernel  ninit:0: listener endpoint: /dev/tcp
00:07/07/22 00:48:24.50 kernel  ninit:0: listener raw address: \x00021d7786f23e010000000000000000
00:07/07/22 00:48:24.50 kernel  ninit:0: transport provider: T_COTS_ORD
00:07/07/22 00:48:24.51 server  Recovering database 'master'
00:07/07/22 00:48:24.51 server  Recovery dbid 1 ckpt (2076,9)
00:07/07/22 00:48:24.51 server  Recovery no active transactions before ckpt.
00:07/07/22 00:48:24.60 server  Database 'master' is now online.
00:07/07/22 00:48:24.60 server  The transaction log in the database 'master' will use I/O size of 2 Kb.
00:07/07/22 00:48:24.62 server  server is unnamed
00:07/07/22 00:48:24.62 server  Activating disk 'dev_db1'.
00:07/07/22 00:48:24.62 kernel  Initializing virtual device 2, '/dev/rdb3'
00:07/07/22 00:48:24.62 kernel  Virtual device 2 started using asynchronous i/o.
00:07/07/22 00:48:24.62 server  Activating disk 'dev_db10'.
00:07/07/22 00:48:24.62 kernel  Initializing virtual device 13, '/dev/rdb12'
00:07/07/22 00:48:24.62 kernel  Virtual device 13 started using asynchronous i/o.
00:07/07/22 00:48:24.62 server  Activating disk 'dev_db11'.
00:07/07/22 00:48:24.62 kernel  Initializing virtual device 14, '/dev/rdb13'
00:07/07/22 00:48:24.62 kernel  Virtual device 14 started using asynchronous i/o.
00:07/07/22 00:48:24.62 server  Activating disk 'dev_db12'.
00:07/07/22 00:48:24.62 kernel  Initializing virtual device 15, '/dev/rdb14'
00:07/07/22 00:48:24.62 kernel  Virtual device 15 started using asynchronous i/o.
00:07/07/22 00:48:24.62 server  Activating disk 'dev_db13'.
00:07/07/22 00:48:24.62 kernel  Initializing virtual device 16, '/dev/rdb15'
00:07/07/22 00:48:24.62 kernel  Virtual device 16 started using asynchronous i/o.
00:07/07/22 00:48:24.62 server  Activating disk 'dev_db14'.
00:07/07/22 00:48:24.62 kernel  Initializing virtual device 17, '/dev/rdb16'
00:07/07/22 00:48:24.62 kernel  Virtual device 17 started using asynchronous i/o.
00:07/07/22 00:48:24.62 server  Activating disk 'dev_db2'.
00:07/07/22 00:48:24.62 kernel  Initializing virtual device 3, '/dev/rdb4'
00:07/07/22 00:48:24.62 kernel  Virtual device 3 started using asynchronous i/o.
00:07/07/22 00:48:24.62 server  Activating disk 'dev_db3'.
00:07/07/22 00:48:24.62 kernel  Initializing virtual device 4, '/dev/rdb5'
00:07/07/22 00:48:24.62 kernel  Virtual device 4 started using asynchronous i/o.
00:07/07/22 00:48:24.62 server  Activating disk 'dev_db4'.
00:07/07/22 00:48:24.62 kernel  Initializing virtual device 5, '/dev/rdb6'
00:07/07/22 00:48:24.62 kernel  Virtual device 5 started using asynchronous i/o.
00:07/07/22 00:48:24.62 server  Activating disk 'dev_db5'.
00:07/07/22 00:48:24.62 kernel  Initializing virtual device 6, '/dev/rdb7'
00:07/07/22 00:48:24.62 kernel  Virtual device 6 started using asynchronous i/o.
00:07/07/22 00:48:24.62 server  Activating disk 'dev_db6'.
00:07/07/22 00:48:24.62 kernel  Initializing virtual device 7, '/dev/rdb8'
00:07/07/22 00:48:24.62 kernel  Virtual device 7 started using asynchronous i/o.
00:07/07/22 00:48:24.62 server  Activating disk 'dev_db7'.
00:07/07/22 00:48:24.62 kernel  Initializing virtual device 10, '/dev/rdb9'
00:07/07/22 00:48:24.63 kernel  Virtual device 10 started using asynchronous i/o.
00:07/07/22 00:48:24.63 server  Activating disk 'dev_db8'.
00:07/07/22 00:48:24.63 kernel  Initializing virtual device 11, '/dev/rdb10'
00:07/07/22 00:48:24.63 kernel  Virtual device 11 started using asynchronous i/o.
00:07/07/22 00:48:24.63 server  Activating disk 'dev_db9'.
00:07/07/22 00:48:24.63 kernel  Initializing virtual device 12, '/dev/rdb11'
00:07/07/22 00:48:24.63 kernel  Virtual device 12 started using asynchronous i/o.
00:07/07/22 00:48:24.63 server  Activating disk 'log_db1'.
00:07/07/22 00:48:24.63 kernel  Initializing virtual device 8, '/dev/rdb20'
00:07/07/22 00:48:24.63 kernel  Virtual device 8 started using asynchronous i/o.
00:07/07/22 00:48:24.63 server  Activating disk 'log_db2'.
00:07/07/22 00:48:24.63 kernel  Initializing virtual device 9, '/dev/rdb19'
00:07/07/22 00:48:24.63 kernel  Virtual device 9 started using asynchronous i/o.
00:07/07/22 00:48:24.63 server  Activating disk 'log_db3'.
00:07/07/22 00:48:24.63 kernel  Initializing virtual device 18, '/dev/rdb18'
00:07/07/22 00:48:24.63 kernel  Virtual device 18 started using asynchronous i/o.
00:07/07/22 00:48:24.63 server  Activating disk 'log_db4'.
00:07/07/22 00:48:24.63 kernel  Initializing virtual device 19, '/dev/rdb17'
00:07/07/22 00:48:24.63 kernel  Virtual device 19 started using asynchronous i/o.
00:07/07/22 00:48:24.63 server  Activating disk 'sysprocsdev'.
00:07/07/22 00:48:24.63 kernel  Initializing virtual device 1, '/dev/rdb1'
00:07/07/22 00:48:24.63 kernel  Virtual device 1 started using asynchronous i/o.
00:07/07/22 00:48:24.64 server  Recovering database 'model'.
00:07/07/22 00:48:24.65 server  Recovery dbid 3 ckpt (437,15)
00:07/07/22 00:48:24.65 server  Recovery no active transactions before ckpt.
00:07/07/22 00:48:24.70 server  The transaction log in the database 'model' will use I/O size of 2 Kb.
00:07/07/22 00:48:24.71 server  Database 'model' is now online.
00:07/07/22 00:48:24.71 server  Clearing temp db
00:07/07/22 00:48:32.09 server  The transaction log in the database 'tempdb' will use I/O size of 2 Kb.
00:07/07/22 00:48:36.93 server  Database 'tempdb' is now online.
00:07/07/22 00:48:36.95 server  Recovering database 'sybsystemprocs'.
00:07/07/22 00:48:36.96 server  Recovery dbid 4 ckpt (7560,19)
00:07/07/22 00:48:36.96 server  Recovery no active transactions before ckpt.
00:07/07/22 00:48:37.17 server  The transaction log in the database 'sybsystemprocs' will use I/O size of 2 Kb.
00:07/07/22 00:48:37.18 server  Database 'sybsystemprocs' is now online.
00:07/07/22 00:48:37.19 server  Recovering database 'cpem'.
00:07/07/22 00:48:37.88 server  Recovery dbid 5 ckpt (16955636,14) oldest tran=(16955636,13)
00:07/07/22 00:48:38.79 server  565 transactions rolled forward.
00:07/07/22 00:50:42.72 server  The transaction log in the database 'cpem' will use I/O size of 2 Kb.
00:07/07/22 00:50:42.73 server  Database 'cpem' is now online.
00:07/07/22 00:50:42.74 server  Recovery complete.
00:07/07/22 00:50:42.74 server  SQL Server's default sort order is:
00:07/07/22 00:50:42.74 server          'bin_iso_1' (ID = 50)
00:07/07/22 00:50:42.74 server  on top of default character set:
00:07/07/22 00:50:42.74 server          'iso_1' (ID = 1).
00:07/07/22 00:56:10.29 kernel  dstartio: I/O request repeatedly delayed; block number: 331002, vdn: 2
00:07/07/22 00:56:10.29 kernel  dstartio: I/O request repeatedly delayed; block number: 333986, vdn: 2
00:07/07/22 00:56:10.30 kernel  dstartio: I/O request repeatedly delayed; block number: 333986, vdn: 2
00:07/07/22 00:56:10.31 kernel  dstartio: I/O request repeatedly delayed; block number: 635092, vdn: 2
00:07/07/22 00:56:10.31 kernel  dstartio: I/O request repeatedly delayed; block number: 333988, vdn: 2
00:07/07/22 00:56:10.31 kernel  dstartio: I/O request repeatedly delayed; block number: 635092, vdn: 2
00:07/07/22 00:56:10.31 kernel  dstartio: I/O request repeatedly delayed; block number: 333988, vdn: 2
00:07/07/22 00:56:10.32 kernel  dstartio: I/O request repeatedly delayed; block number: 333988, vdn: 2
00:07/07/22 00:56:10.33 kernel  dstartio: I/O request repeatedly delayed; block number: 798636, vdn: 2
00:07/07/22 00:56:10.33 kernel  dstartio: I/O request repeatedly delayed; block number: 333991, vdn: 2
00:07/07/22 00:56:10.34 kernel  dstartio: I/O request repeatedly delayed; block number: 334000, vdn: 2
00:07/07/22 00:56:10.35 kernel  dstartio: I/O request repeatedly delayed; block number: 334002, vdn: 2
00:07/07/22 00:56:10.35 kernel  dstartio: I/O request repeatedly delayed; block number: 334003, vdn: 2
00:07/07/22 00:56:10.35 kernel  dstartio: I/O request repeatedly delayed; block number: 334005, vdn: 2
00:07/07/22 00:56:10.37 kernel  dstartio: I/O request repeatedly delayed; block number: 334010, vdn: 2
00:07/07/22 01:04:31.09 kernel  dstartio: I/O request repeatedly delayed; block number: 334804, vdn: 2
00:07/07/22 01:04:31.53 kernel  dstartio: I/O request repeatedly delayed; block number: 10039, vdn: 2
00:07/07/22 01:04:31.54 kernel  dstartio: I/O request repeatedly delayed; block number: 10039, vdn: 2
00:07/07/22 01:04:31.54 kernel  dstartio: I/O request repeatedly delayed; block number: 10039, vdn: 2
00:07/07/22 01:04:31.55 kernel  dstartio: I/O request repeatedly delayed; block number: 10029, vdn: 2
00:07/07/22 01:04:31.56 kernel  dstartio: I/O request repeatedly delayed; block number: 624107, vdn: 2
00:07/07/22 01:04:31.56 kernel  dstartio: I/O request repeatedly delayed; block number: 10037, vdn: 2
00:07/07/22 01:04:31.56 kernel  dstartio: I/O request repeatedly delayed; block number: 10037, vdn: 2
00:07/07/22 01:04:31.56 kernel  dstartio: I/O request repeatedly delayed; block number: 10037, vdn: 2
00:07/07/22 01:04:31.58 kernel  dstartio: I/O request repeatedly delayed; block number: 798, vdn: 2
00:07/07/22 12:40:10.39 kernel  dstartio: I/O request repeatedly delayed; block number: 334806, vdn: 2
00:07/07/22 13:29:17.05 kernel  dstartio: I/O request repeatedly delayed; block number: 334805, vdn: 2
00:07/07/22 13:29:17.06 kernel  dstartio: I/O request repeatedly delayed; block number: 334805, vdn: 2
00:07/07/22 13:29:17.06 kernel  dstartio: I/O request repeatedly delayed; block number: 334805, vdn: 2
00:07/07/22 13:29:17.06 kernel  dstartio: I/O request repeatedly delayed; block number: 334805, vdn: 2
00:07/07/22 13:29:17.07 kernel  dstartio: I/O request repeatedly delayed; block number: 334805, vdn: 2
00:07/07/22 13:29:17.08 kernel  dstartio: I/O request repeatedly delayed; block number: 334812, vdn: 2
00:07/07/22 13:29:17.10 kernel  dstartio: I/O request repeatedly delayed; block number: 334820, vdn: 2
00:07/07/22 13:29:17.10 kernel  dstartio: I/O request repeatedly delayed; block number: 334821, vdn: 2
00:07/07/22 13:29:17.11 kernel  dstartio: I/O request repeatedly delayed; block number: 334830, vdn: 2
00:07/07/22 13:29:17.12 kernel  dstartio: I/O request repeatedly delayed; block number: 245266, vdn: 2
00:07/07/22 13:29:32.22 kernel  dstartio: I/O request repeatedly delayed; block number: 797370, vdn: 2
00:07/07/22 13:29:32.22 kernel  dstartio: I/O request repeatedly delayed; block number: 334811, vdn: 2
00:07/07/22 13:29:32.22 kernel  dstartio: I/O request repeatedly delayed; block number: 334811, vdn: 2
00:07/07/22 13:29:32.23 kernel  dstartio: I/O request repeatedly delayed; block number: 865579, vdn: 2
00:07/07/22 13:29:32.23 kernel  dstartio: I/O request repeatedly delayed; block number: 334812, vdn: 2
00:07/07/22 13:29:32.25 kernel  dstartio: I/O request repeatedly delayed; block number: 861709, vdn: 2
00:07/07/22 13:29:32.25 kernel  dstartio: I/O request repeatedly delayed; block number: 334820, vdn: 2
00:07/07/22 13:29:32.25 kernel  dstartio: I/O request repeatedly delayed; block number: 861709, vdn: 2
00:07/07/22 13:29:32.25 kernel  dstartio: I/O request repeatedly delayed; block number: 334820, vdn: 2
00:07/07/22 13:29:32.27 kernel  dstartio: I/O request repeatedly delayed; block number: 334822, vdn: 2
00:07/07/22 13:29:32.28 kernel  dstartio: I/O request repeatedly delayed; block number: 334832, vdn: 2
00:07/07/22 13:29:32.28 kernel  dstartio: I/O request repeatedly delayed; block number: 334832, vdn: 2
00:07/07/22 13:29:32.28 kernel  dstartio: I/O request repeatedly delayed; block number: 334832, vdn: 2
00:07/07/22 15:33:04.50 kernel  dstartio: I/O request repeatedly delayed; block number: 334843, vdn: 2
00:07/07/22 15:33:04.56 kernel  dstartio: I/O request repeatedly delayed; block number: 3004, vdn: 0
00:07/07/22 17:06:28.21 kernel  dstartio: I/O request repeatedly delayed; block number: 2566, vdn: 0
00:07/07/22 17:06:28.21 kernel  dstartio: I/O request repeatedly delayed; block number: 2566, vdn: 0
00:07/07/22 17:06:28.21 kernel  dstartio: I/O request repeatedly delayed; block number: 9277, vdn: 2
00:07/07/22 17:06:28.22 kernel  dstartio: I/O request repeatedly delayed; block number: 9277, vdn: 2
00:07/07/22 17:06:28.22 kernel  dstartio: I/O request repeatedly delayed; block number: 9277, vdn: 2
00:07/07/22 17:06:28.23 kernel  dstartio: I/O request repeatedly delayed; block number: 9277, vdn: 2
00:07/07/22 17:06:28.23 kernel  dstartio: I/O request repeatedly delayed; block number: 9277, vdn: 2
00:07/07/22 19:10:19.30 kernel  dstartio: I/O request repeatedly delayed; block number: 318892, vdn: 2
00:07/07/22 19:10:19.32 kernel  dstartio: I/O request repeatedly delayed; block number: 334815, vdn: 2
00:07/07/22 19:10:19.32 kernel  dstartio: I/O request repeatedly delayed; block number: 334815, vdn: 2
00:07/07/22 19:10:19.33 kernel  dstartio: I/O request repeatedly delayed; block number: 334820, vdn: 2
00:07/07/22 19:10:19.34 kernel  dstartio: I/O request repeatedly delayed; block number: 334822, vdn: 2
00:07/07/22 19:10:19.35 kernel  dstartio: I/O request repeatedly delayed; block number: 334829, vdn: 2
00:07/07/22 19:10:19.35 kernel  dstartio: I/O request repeatedly delayed; block number: 334843, vdn: 2
00:07/07/22 19:10:19.36 kernel  dstartio: I/O request repeatedly delayed; block number: 334843, vdn: 2
00:07/07/22 19:10:19.36 kernel  dstartio: I/O request repeatedly delayed; block number: 334843, vdn: 2
00:07/07/22 19:10:19.37 kernel  dstartio: I/O request repeatedly delayed; block number: 334846, vdn: 2

论坛徽章:
0
2 [报告]
发表于 2007-07-24 11:13 |只看该作者

回复 #1 lanfeng527 的帖子

把number of online engines改成1,试试。

论坛徽章:
0
3 [报告]
发表于 2007-07-24 11:39 |只看该作者
原帖由 aliking 于 2007-7-24 11:13 发表
把number of online engines改成1,试试。


谢谢你!我想知道在线引擎改成1的意义是什么?原始默认值是多少?因为数据库现在处于在用状态,我必须搞明白了我才改~

论坛徽章:
1
2017金鸡报晓
日期:2017-01-10 15:19:56
4 [报告]
发表于 2007-07-24 11:40 |只看该作者
版本太老了,考虑升级吧

论坛徽章:
0
5 [报告]
发表于 2007-07-24 13:07 |只看该作者

current process (0x370037) infected with 11

Spinlocks held by  kpid 3604535
可以推断可能是spinlock竞争引起的,即多个进程争用多CPU的问题,需要修改online engines确认一下。
查看当前值:
sp_configure 'number of online engines'

感觉你ASE系统管理方面的知识比较欠缺,如果要维护这个系统,最好学习一下。

论坛徽章:
0
6 [报告]
发表于 2007-07-31 20:50 |只看该作者
做一下 c_dev_history_log 这个表的DBCC。看看有没有报错

论坛徽章:
0
7 [报告]
发表于 2007-08-01 13:56 |只看该作者
确实太老了,即使确认了问题的原因,也可能没有办法解决,建议升级吧
您需要登录后才可以回帖 登录 | 注册

本版积分规则 发表回复

  

北京盛拓优讯信息技术有限公司. 版权所有 京ICP备16024965号-6 北京市公安局海淀分局网监中心备案编号:11010802020122 niuxiaotong@pcpop.com 17352615567
未成年举报专区
中国互联网协会会员  联系我们:huangweiwei@itpub.net
感谢所有关心和支持过ChinaUnix的朋友们 转载本站内容请注明原作者名及出处

清除 Cookies - ChinaUnix - Archiver - WAP - TOP