请教sybase老突然死掉的问题

aps_hero

我有一个生产系统上线1个月了，操作系统是unixware，数据库版本是11.9.2.4，这套系统每过几天sybase数据库就会“死掉”，客户端也不能登陆，在服务器上通过isql也不能登陆。而检查操作系统都正常，没有办法只能kill掉sybase进程，然后重新启动sybase就好了，但是过几天有会出现该问题。开始我怀疑是数据库日志满了，但我已经将truncate log on checkpoint选上了，并且我的业务量很少，一天才几笔业务，下面是sybae的日志，请各位大侠帮我看看呀！！多谢！
4/08/17 09:40:50.03 kernel  nspacket: t_snd, event requires attention
00:00000:00012:2004/08/17 09:42:33.68 kernel  nconnect: t_rcvconnect, event requires attention
00:00000:00012:2004/08/17 09:42:33.68 server  Failed to connect to remote server SYB_BACKUP tli tcp /dev/tcp \x00021f410a0011030000000000000000 for site SYB_BACKUP. Trying the next query entry of this server, if any.
00:00000:00012:2004/08/17 09:42:33.68 server  Error: 7235, Severity: 17, State: 0
00:00000:00012:2004/08/17 09:42:33.68 server  No other query entry found for the remote server SYB_BACKUP - site SYB_BACKUP. Aborting this site handler, as no remote server responded. Please make sure the remote server is accepting connections.
00:00000:00012:2004/08/17 09:42:33.71 kernel  nconnect: t_rcvconnect, event requires attention
00:00000:00012:2004/08/17 09:42:33.71 server  Failed to connect to remote server SYB_BACKUP tli tcp /dev/tcp \x00021f410a0011030000000000000000 for site SYB_BACKUP. Trying the next query entry of this server, if any.
00:00000:00012:2004/08/17 09:42:33.71 server  Error: 7235, Severity: 17, State: 0
00:00000:00012:2004/08/17 09:42:33.71 server  No other query entry found for the remote server SYB_BACKUP - site SYB_BACKUP. Aborting this site handler, as no remote server responded. Please make sure the remote server is accepting connections.
00:00000:00012:2004/08/17 09:42:33.71 kernel  nconnect: t_rcvconnect, event requires attention
00:00000:00012:2004/08/17 09:42:33.71 server  Failed to connect to remote server SYB_BACKUP tli tcp /dev/tcp \x00021f410a0011030000000000000000 for site SYB_BACKUP. Trying the next query entry of this server, if any.
00:00000:00012:2004/08/17 09:42:33.71 server  Error: 7235, Severity: 17, State: 0
00:00000:00012:2004/08/17 09:42:33.71 server  No other query entry found for the remote server SYB_BACKUP - site SYB_BACKUP. Aborting this site handler, as no remote server responded. Please make sure the remote server is accepting connections.
00:00000:00010:2004/09/02 19:33:13.05 server  SQL Server shutdown by request.
00:00000:00010:2004/09/02 19:33:13.05 kernel  ueshutdown: exiting
00:00000:00000:2004/09/02 19:38:56.53 kernel  Using config area from primary master device.
00:00000:00000:2004/09/02 19:38:56.57 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:00000:00000:2004/09/02 19:38:57.86 kernel  Using 256 file descriptors.
00:00000:00000:2004/09/02 19:38:57.87 kernel  Adaptive Server Enterprise/11.9.2.4/P/SWR 9486(Data General) ROLLUP, SWR 9487(UNIXWARE) ROLLUP/DG AViiON/SCO UnixWare 2.1.3/FBO/Wed Feb 21 22:08:20 2001
00:00000:00000:2004/09/02 19:38:57.87 kernel  Confidential property of Sybase, Inc.
00:00000:00000:2004/09/02 19:38:57.87 kernel  Copyright 1987, 2001
00:00000:00000:2004/09/02 19:38:57.87 kernel  Sybase, Inc.  All rights reserved.
00:00000:00000:2004/09/02 19:38:57.87 kernel  Unpublished rights reserved under U.S. copyright laws.
00:00000:00000:2004/09/02 19:38:57.87 kernel  
00:00000:00000:2004/09/02 19:38:57.87 kernel  This software contains confidential and trade secret information of Sybase,
00:00000:00000:2004/09/02 19:38:57.87 kernel  Inc.   Use,  duplication or disclosure of the software and documentation by
00:00000:00000:2004/09/02 19:38:57.87 kernel  the  U.S.  Government  is  subject  to  restrictions set forth in a license
00:00000:00000:2004/09/02 19:38:57.87 kernel  agreement  between  the  Government  and  Sybase,  Inc.  or  other  written
00:00000:00000:2004/09/02 19:38:57.87 kernel  agreement  specifying  the  Government's rights to use the software and any
00:00000:00000:2004/09/02 19:38:57.87 kernel  applicable FAR provisions, for example, FAR 52.227-19.
00:00000:00000:2004/09/02 19:38:57.87 kernel  Sybase, Inc. 6475 Christie Avenue, Emeryville, CA 94608, USA
00:00000:00000:2004/09/02 19:38:57.87 kernel  Using '/sybase/SYBASE.cfg' for configuration information.
00:00000:00000:2004/09/02 19:38:57.87 kernel  Logging SQL Server messages in file '/sybase/install/SYBASE.log'.
00:00000:00000:2004/09/02 19:38:58.05 kernel  kdcl_init: connectivity library supports master/query syntax
00:00000:00000:2004/09/02 19:38:58.05 kernel  Directory Control Layer (DCL) using directory driver: InterfacesDriver
00:00000:00000:2004/09/02 19:38:58.07 kernel  Network and device connection limit is 246.
00:00000:00000:2004/09/02 19:38:58.10 server  Number of proc buffers allocated: 86057.
00:00000:00000:2004/09/02 19:38:59.01 server  Proc header memory allocated 43028 pages for each per engine cache
00:00000:00000:2004/09/02 19:38:59.01 server  Number of blocks left for proc headers: 86145.
00:00000:00000:2004/09/02 19:38:59.01 server  Memory allocated for the default data cache cache: 378116 Kb
00:00000:00000:2004/09/02 19:38:59.03 server  Size of the 2K memory pool: 378116 Kb
00:00000:00000:2004/09/02 19:38:59.04 kernel  Initializing virtual device 0, '/sybase/data/master'
00:00000:00000:2004/09/02 19:38:59.04 kernel  Virtual device 0 started using standard unix i/o.
00:00000:00000:2004/09/02 19:38:59.04 kernel  Worker Thread Manager is not enabled for use in SQL Server.
00:00000:00000:2004/09/02 19:38:59.04 kernel  Either the config parameter 'use security services' is set to 0, or ASE does not support use of external security mechanisms on this platform. The Security Control Layer will not be initialized. No external security mechanisms will be supported.
00:00000:00000:2004/09/02 19:38:59.04 kernel  engine 0, os pid 1473  online
00:00000:00000:2004/09/02 19:38:59.05 server  No active traceflags
00:00000:00001:2004/09/02 19:38:59.05 server  Opening Master Database ...
00:00000:00001:2004/09/02 19:38:59.11 server  Loading SQL Server's default sort order and character set
00:00000:00002:2004/09/02 19:38:59.11 kernel  ninit:0: listener type: master
00:00000:00002:2004/09/02 19:38:59.11 kernel  ninit:0: listener endpoint: /dev/tcp
00:00000:00002:2004/09/02 19:38:59.11 kernel  ninit:0: listener raw address: \x00021f400a0011030000000000000000
00:00000:00002:2004/09/02 19:38:59.11 kernel  ninit:0: transport provider: T_COTS_ORD
00:00000:00001:2004/09/02 19:38:59.12 server  Recovering database 'master'
00:00000:00001:2004/09/02 19:38:59.17 server  Database 'master' is now online.
00:00000:00001:2004/09/02 19:38:59.17 server  The transaction log in the database 'master' will use I/O size of 2 Kb.
00:00000:00001:2004/09/02 19:38:59.19 server  0 dump conditions detected at boot time
00:00000:00001:2004/09/02 19:38:59.20 server  server is unnamed
00:00000:00001:2004/09/02 19:38:59.20 server  Activating disk 'hisdatadb'.
00:00000:00001:2004/09/02 19:38:59.20 kernel  Initializing virtual device 7, '/sybase/data/hisdatadb'
00:00000:00001:2004/09/02 19:38:59.20 kernel  Virtual device 7 started using asynchronous i/o.
00:00000:00001:2004/09/02 19:38:59.20 server  Activating disk 'hisdblog'.
00:00000:00001:2004/09/02 19:38:59.20 kernel  Initializing virtual device 9, '/sybase/data/hisdblog'
00:00000:00001:2004/09/02 19:38:59.20 kernel  Virtual device 9 started using asynchronous i/o.
00:00000:00001:2004/09/02 19:38:59.20 server  Activating disk 'hisindexdb'.
00:00000:00001:2004/09/02 19:38:59.20 kernel  Initializing virtual device 8, '/sybase/data/hisindexdb'
00:00000:00001:2004/09/02 19:38:59.20 kernel  Virtual device 8 started using asynchronous i/o.
00:00000:00001:2004/09/02 19:38:59.20 server  Activating disk 'sysprocsdev'.
00:00000:00001:2004/09/02 19:38:59.20 kernel  Initializing virtual device 1, '/sybase/data/systemprocs'
00:00000:00001:2004/09/02 19:38:59.20 kernel  Virtual device 1 started using standard unix i/o.
00:00000:00001:2004/09/02 19:38:59.20 server  Activating disk 'systemdbdev'.
00:00000:00001:2004/09/02 19:38:59.20 kernel  Initializing virtual device 2, '/sybase/data/systemdb'
00:00000:00001:2004/09/02 19:38:59.20 kernel  Virtual device 2 started using standard unix i/o.
00:00000:00001:2004/09/02 19:38:59.20 server  Activating disk 'tempdb'.
00:00000:00001:2004/09/02 19:38:59.20 kernel  Initializing virtual device 3, '/sybase/data/tempdb'
00:00000:00001:2004/09/02 19:38:59.20 kernel  Virtual device 3 started using standard unix i/o.
00:00000:00001:2004/09/02 19:38:59.20 server  Activating disk 'wkdatadb'.
00:00000:00001:2004/09/02 19:38:59.20 kernel  Initializing virtual device 4, '/sybase/data/wkdatadb'
00:00000:00001:2004/09/02 19:38:59.20 kernel  Virtual device 4 started using asynchronous i/o.
00:00000:00001:2004/09/02 19:38:59.20 server  Activating disk 'wkdblog'.
00:00000:00001:2004/09/02 19:38:59.20 kernel  Initializing virtual device 6, '/sybase/data/wkdblog'
00:00000:00001:2004/09/02 19:38:59.20 kernel  Virtual device 6 started using asynchronous i/o.
00:00000:00001:2004/09/02 19:38:59.20 server  Activating disk 'wkindexdb'.
00:00000:00001:2004/09/02 19:38:59.20 kernel  Initializing virtual device 5, '/sybase/data/wkindexdb'
00:00000:00001:2004/09/02 19:38:59.20 kernel  Virtual device 5 started using asynchronous i/o.
00:00000:00001:2004/09/02 19:38:59.23 server  Recovering database 'model'.
00:00000:00001:2004/09/02 19:38:59.26 server  The transaction log in the database 'model' will use I/O size of 2 Kb.
00:00000:00001:2004/09/02 19:38:59.28 server  Database 'model' is now online.
00:00000:00001:2004/09/02 19:38:59.28 server  Clearing temp db
00:00000:00001:2004/09/02 19:38:59.61 server  The transaction log in the database 'tempdb' will use I/O size of 2 Kb.
00:00000:00001:2004/09/02 19:38:59.63 server  The transaction log in the database 'tempdb' will use I/O size of 2 Kb.
00:00000:00001:2004/09/02 19:38:59.65 server  Database 'tempdb' is now online.
00:00000:00001:2004/09/02 19:38:59.65 server  The transaction log in the database 'tempdb' will use I/O size of 2 Kb.
00:00000:00001:2004/09/02 19:38:59.69 server  Recovering database 'sybsystemdb'.
00:00000:00001:2004/09/02 19:38:59.72 server  The transaction log in the database 'sybsystemdb' will use I/O size of 2 Kb.
00:00000:00001:2004/09/02 19:38:59.74 server  Database 'sybsystemdb' is now online.
00:00000:00001:2004/09/02 19:38:59.76 server  Recovering database 'sybsystemprocs'.
00:00000:00001:2004/09/02 19:38:59.81 server  The transaction log in the database 'sybsystemprocs' will use I/O size of 2 Kb.
00:00000:00001:2004/09/02 19:38:59.83 server  Database 'sybsystemprocs' is now online.
00:00000:00001:2004/09/02 19:38:59.86 server  Recovering database 'MBFEWKDB'.
00:00000:00001:2004/09/02 19:39:00.08 server  The transaction log in the database 'MBFEWKDB' will use I/O size of 2 Kb.
00:00000:00001:2004/09/02 19:39:00.11 server  Database 'MBFEWKDB' is now online.
00:00000:00001:2004/09/02 19:39:00.13 server  Recovering database 'MBFEHISDB'.
00:00000:00001:2004/09/02 19:39:00.20 server  The transaction log in the database 'MBFEHISDB' will use I/O size of 2 Kb.
00:00000:00001:2004/09/02 19:39:00.22 server  Database 'MBFEHISDB' is now online.
00:00000:00001:2004/09/02 19:39:00.23 server  Recovery complete.
00:00000:00001:2004/09/02 19:39:00.23 server  SQL Server's default sort order is:
00:00000:00001:2004/09/02 19:39:00.23 server          'bin_iso_1' (ID = 50)
00:00000:00001:2004/09/02 19:39:00.23 server  on top of default character set:
00:00000:00001:2004/09/02 19:39:00.23 server          'iso_1' (ID = 1).
00:00000:00001:2004/09/02 19:39:00.23 server  Loaded default Unilib conversion handle.
00:00000:00000:2004/09/06 09:09:26.12 kernel  ueshutdown: exiting
00:00000:00000:2004/09/06 09:09:26.12 kernel  Abnormal exit detected - SQL Server process level execution bindings will be cleared on startup.
00:00000:00000:2004/09/06 09:10:34.57 kernel  Using config area from primary master device.

chenfeng825

看起来像网络问题。具体由更详细的log吗