免费注册 查看新帖 |

Chinaunix

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

sybase 不能启动.请帮助解决! [复制链接]

论坛徽章:
0
跳转到指定楼层
1 [收藏(0)] [报告]
发表于 2005-10-07 17:47 |只看该作者 |倒序浏览
sybase 12.5安装到windowsXP
设置完成自启动了sybase服务.
系统重启动后怎么就不能启动sybase服务了?手动启动也失败!怎么解决?

论坛徽章:
0
2 [报告]
发表于 2005-10-07 18:02 |只看该作者

sybase 不能启动.请帮助解决!

日志?

论坛徽章:
0
3 [报告]
发表于 2005-10-07 19:00 |只看该作者

sybase 不能启动.请帮助解决!

1、日志
2、WindowsXP的UPNP服务占用了5000端口(猜测M$也是故意为之的吧,呵呵)。

论坛徽章:
0
4 [报告]
发表于 2005-10-07 22:00 |只看该作者

sybase 不能启动.请帮助解决!

00:00000:00000:2005/10/07 21:51:31.17 kernel  Use license file C:\sybase\SYSAM-1_0\licenses\license.dat.
00:00000:00000:2005/10/07 21:51:31.52 kernel  Failed to log the current message in the Windows NT event log
00:00000:00000:2005/10/07 21:51:31.71 kernel  Checked out license ASE_SERVER
00:00000:00000:2005/10/07 21:51:31.74 kernel  Failed to log the current message in the Windows NT event log
00:00000:00000:2005/10/07 21:51:31.74 kernel  Adaptive Server Enterprise Edition
00:00000:00000:2005/10/07 21:51:31.74 kernel  Failed to log the current message in the Windows NT event log
00:00000:00000:2005/10/07 21:51:32.42 kernel  Using config area from primary master device.
00:00000:00000:2005/10/07 21:51:32.60 kernel  Warning: Using default file 'C:\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:2005/10/07 21:51:32.60 kernel  Failed to log the current message in the Windows NT event log
00:00000:00000:2005/10/07 21:51:32.80 kernel  Using 100000 file descriptors.
00:00000:00000:2005/10/07 21:51:33.10 kernel  Adaptive Server Enterprise/12.5.3/EBF 12599 ESD#3/P/NT (IX86)/OS 4.0/ase1253/1912/32-bit/OPT/Fri Jul 08 18:58:47 2005
00:00000:00000:2005/10/07 21:51:33.10 kernel  Confidential property of Sybase, Inc.
00:00000:00000:2005/10/07 21:51:33.10 kernel  Copyright 1987, 2005
00:00000:00000:2005/10/07 21:51:33.10 kernel  Sybase, Inc.  All rights reserved.
00:00000:00000:2005/10/07 21:51:33.10 kernel  Unpublished rights reserved under U.S. copyright laws.
00:00000:00000:2005/10/07 21:51:33.10 kernel  
00:00000:00000:2005/10/07 21:51:33.10 kernel  This software contains confidential and trade secret information of Sybase,
00:00000:00000:2005/10/07 21:51:33.10 kernel  Inc.   Use,  duplication or disclosure of the software and documentation by
00:00000:00000:2005/10/07 21:51:33.10 kernel  the  U.S.  Government  is  subject  to  restrictions set forth in a license
00:00000:00000:2005/10/07 21:51:33.10 kernel  agreement  between  the  Government  and  Sybase,  Inc.  or  other  written
00:00000:00000:2005/10/07 21:51:33.10 kernel  agreement  specifying  the  Government's rights to use the software and any
00:00000:00000:2005/10/07 21:51:33.10 kernel  applicable FAR provisions, for example, FAR 52.227-19.
00:00000:00000:2005/10/07 21:51:33.10 kernel  Sybase, Inc. One Sybase Drive, Dublin, CA 94568, USA
00:00000:00000:2005/10/07 21:51:33.10 kernel  ASE booted on Windows XP build 2600 Service Pack 2.
00:00000:00000:2005/10/07 21:51:33.10 kernel  Using 'C:\sybase\SYBASE.cfg' for configuration information.
00:00000:00000:2005/10/07 21:51:33.10 kernel  Failed to log the current message in the Windows NT event log
00:00000:00000:2005/10/07 21:51:33.10 kernel  Logging ASE messages in file 'C:\sybase\ASE-12_5\install\SYBASE.log'.
00:00000:00000:2005/10/07 21:51:33.13 kernel  Initializing MSDTC Connection
00:00000:00000:2005/10/07 21:51:33.13 kernel  Failed to log the current message in the Windows NT event log
00:00000:00000:2005/10/07 21:51:34.06 kernel  The DTC Operation DtcGetTransactionManagerC failed with error DTC Services not available (0x8004d01b)
00:00000:00000:2005/10/07 21:51:34.06 kernel  Failed to log the current message in the Windows NT event log
00:00000:00000:2005/10/07 21:51:34.06 kernel  MSDTC Initialization failed
00:00000:00000:2005/10/07 21:51:34.06 kernel  Failed to log the current message in the Windows NT event log
00:00000:00000:2005/10/07 21:51:34.06 kernel  Platform TCP network is forced to IPv4-only.
00:00000:00000:2005/10/07 21:51:34.09 kernel  Failed to log the current message in the Windows NT event log
00:00000:00000:2005/10/07 21:51:34.09 kernel  SQL Server booted with TCP_NODELAY enabled.
00:00000:00000:2005/10/07 21:51:34.09 kernel  Failed to log the current message in the Windows NT event log
00:00000:00000:2005/10/07 21:51:34.09 kernel  SQL Server NT process id is 0x1cc.
00:00000:00000:2005/10/07 21:51:34.09 kernel  SQL Server was started as a Service.
00:00000:00000:2005/10/07 21:51:34.17 kernel  SSL Plus v3.1.15 security modules loaded successfully.
00:00000:00000:2005/10/07 21:51:34.17 kernel  Failed to log the current message in the Windows NT event log
00:00000:00000:2005/10/07 21:51:34.17 kernel  Network and device connection limit is 99992.
00:00000:00000:2005/10/07 21:51:34.45 server  Number of blocks left for proc headers: 3232.
00:00000:00000:2005/10/07 21:51:34.47 server  Proc header memory allocated 1616 pages for each per engine cache
00:00000:00000:2005/10/07 21:51:34.48 server  Size of the 2K memory pool: 8192 Kb
00:00000:00000:2005/10/07 21:51:34.48 kernel  Failed to log the current message in the Windows NT event log
00:00000:00000:2005/10/07 21:51:34.48 server  Memory allocated for the default data cache cachelet 1: 8192 Kb
00:00000:00000:2005/10/07 21:51:34.49 kernel  Initializing virtual device 0, 'C:\sybase\data\master.dat' with dsync 'on'.
00:00000:00000:2005/10/07 21:51:34.51 kernel  Virtual device 0 started using asynchronous i/o.
00:00000:00000:2005/10/07 21:51:34.51 kernel  Worker Thread Manager is not enabled for use in SQL Server.
00:00000:00000:2005/10/07 21:51:34.51 kernel  Failed to log the current message in the Windows NT event log
00:00000:00000:2005/10/07 21:51:34.51 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:2005/10/07 21:51:34.51 kernel  Failed to log the current message in the Windows NT event log
00:00000:00000:2005/10/07 21:51:34.69 kernel  engine 0, os pid 1872  online
00:00000:00000:2005/10/07 21:51:34.69 kernel  Failed to log the current message in the Windows NT event log
00:00000:00000:2005/10/07 21:51:34.71 server  No active traceflags
00:00000:00000:2005/10/07 21:51:34.72 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:34.97 kernel  libomni1 - Component Integration Services loaded; version 'libomni1 - Component Integration Services/12.5.3/EBF 12599 ESD#3/P/NT (IX86)/OS 4.0/ase1253/1912/32-bit/OPT/Fri Jul 08 18:58:47 2005'.
00:00000:00001:2005/10/07 21:51:34.97 kernel  libomni1 - Component Integration Services: using 'Sybase Client-Library/12.5.1/P-EBF12117 ESD #5/PC Intel/BUILD1251-038/OPT/Tue Aug 17 20:29:27 2004'
00:00000:00001:2005/10/07 21:51:34.99 server  Opening Master Database ...
00:00000:00001:2005/10/07 21:51:35.44 server  Loading SQL Server's default sort order and character set
00:00000:00001:2005/10/07 21:51:35.49 server  Loaded default Unilib conversion handle.
00:00000:00001:2005/10/07 21:51:35.49 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:35.60 server  Recovering database 'master'.
00:00000:00001:2005/10/07 21:51:35.60 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:35.69 server  Started estimating recovery log boundaries for database 'master'.
00:00000:00001:2005/10/07 21:51:35.69 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:35.73 server  Database 'master', checkpoint=(3003, 3), first=(3003, 2), last=(3003, 23).
00:00000:00001:2005/10/07 21:51:35.73 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:35.73 server  Completed estimating recovery log boundaries for database 'master'.
00:00000:00001:2005/10/07 21:51:35.73 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:35.73 server  Started ANALYSIS pass for database 'master'.
00:00000:00001:2005/10/07 21:51:35.73 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:35.75 server  Completed ANALYSIS pass for database 'master'.
00:00000:00001:2005/10/07 21:51:35.75 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:35.75 server  Started REDO pass for database 'master'. The total number of log records to process is 22.
00:00000:00001:2005/10/07 21:51:35.75 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:35.80 server  Redo pass of recovery has processed 4 committed and 0 aborted transactions.
00:00000:00001:2005/10/07 21:51:35.80 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:35.80 server  Completed REDO pass for database 'master'.
00:00000:00001:2005/10/07 21:51:35.80 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:35.82 server  Recovery of database 'master' will undo incomplete nested top actions.
00:00000:00001:2005/10/07 21:51:35.82 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:35.82 server  Started recovery checkpoint for database 'master'.
00:00000:00001:2005/10/07 21:51:35.82 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:35.86 server  Completed recovery checkpoint for database 'master'.
00:00000:00001:2005/10/07 21:51:35.87 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:35.87 server  Started filling free space info for database 'master'.
00:00000:00001:2005/10/07 21:51:35.87 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:35.97 server  Completed filling free space info for database 'master'.
00:00000:00001:2005/10/07 21:51:35.97 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:35.97 server  Started cleaning up the default data cache for database 'master'.
00:00000:00001:2005/10/07 21:51:35.97 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:35.97 server  Completed cleaning up the default data cache for database 'master'.
00:00000:00001:2005/10/07 21:51:35.97 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:36.04 server  Checking external objects.
00:00000:00001:2005/10/07 21:51:36.04 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:36.15 server  Database 'master' is now online.
00:00000:00001:2005/10/07 21:51:36.15 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:36.18 server  The transaction log in the database 'master' will use I/O size of 2 Kb.
00:00000:00001:2005/10/07 21:51:36.18 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:36.34 server  Warning: ASE_HA has no valid license and therefore is not initialized.
00:00000:00001:2005/10/07 21:51:36.34 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:36.40 server  server name is 'SYBASE'
00:00000:00001:2005/10/07 21:51:36.40 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:36.41 server  Activating disk 'sysprocsdev' of size 122880 KB.
00:00000:00001:2005/10/07 21:51:36.41 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:36.41 kernel  Initializing virtual device 1, 'C:\sybase\data\sysprocs.dat' with dsync 'on'.
00:00000:00001:2005/10/07 21:51:36.44 kernel  Virtual device 1 started using asynchronous i/o.
00:00000:00001:2005/10/07 21:51:36.61 server  Recovering database 'sybsystemdb'.
00:00000:00001:2005/10/07 21:51:36.61 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:36.61 server  Started estimating recovery log boundaries for database 'sybsystemdb'.
00:00000:00001:2005/10/07 21:51:36.61 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:36.62 server  Database 'sybsystemdb', checkpoint=(632, 14), first=(632, 14), last=(634, 1).
00:00000:00001:2005/10/07 21:51:36.62 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:36.62 server  Completed estimating recovery log boundaries for database 'sybsystemdb'.
00:00000:00001:2005/10/07 21:51:36.62 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:36.62 server  Started ANALYSIS pass for database 'sybsystemdb'.
00:00000:00001:2005/10/07 21:51:36.62 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:36.62 server  Completed ANALYSIS pass for database 'sybsystemdb'.
00:00000:00001:2005/10/07 21:51:36.62 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:36.62 server  Started REDO pass for database 'sybsystemdb'. The total number of log records to process is 42.
00:00000:00001:2005/10/07 21:51:36.62 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:36.70 server  Redo pass of recovery has processed 3 committed and 1 aborted transactions.
00:00000:00001:2005/10/07 21:51:36.70 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:36.70 server  Completed REDO pass for database 'sybsystemdb'.
00:00000:00001:2005/10/07 21:51:36.70 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:36.70 server  Recovery of database 'sybsystemdb' will undo incomplete nested top actions.
00:00000:00001:2005/10/07 21:51:36.70 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:36.70 server  Started recovery checkpoint for database 'sybsystemdb'.
00:00000:00001:2005/10/07 21:51:36.70 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:36.70 server  Completed recovery checkpoint for database 'sybsystemdb'.
00:00000:00001:2005/10/07 21:51:36.70 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:36.71 server  Started filling free space info for database 'sybsystemdb'.
00:00000:00001:2005/10/07 21:51:36.71 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:36.81 server  Completed filling free space info for database 'sybsystemdb'.
00:00000:00001:2005/10/07 21:51:36.81 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:36.81 server  Started cleaning up the default data cache for database 'sybsystemdb'.
00:00000:00001:2005/10/07 21:51:36.81 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:36.81 server  Completed cleaning up the default data cache for database 'sybsystemdb'.
00:00000:00001:2005/10/07 21:51:36.81 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:36.81 server  Boot Count: 5
00:00000:00001:2005/10/07 21:51:36.81 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:36.86 server  Checking external objects.
00:00000:00001:2005/10/07 21:51:36.86 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:36.88 server  The transaction log in the database 'sybsystemdb' will use I/O size of 2 Kb.
00:00000:00001:2005/10/07 21:51:36.88 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:36.88 server  Database 'sybsystemdb' is now online.
00:00000:00001:2005/10/07 21:51:36.88 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:36.94 server  Recovering database 'model'.
00:00000:00001:2005/10/07 21:51:36.94 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:36.94 server  Started estimating recovery log boundaries for database 'model'.
00:00000:00001:2005/10/07 21:51:36.94 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:36.94 server  Database 'model', checkpoint=(624, 22), first=(624, 22), last=(625, 22).
00:00000:00001:2005/10/07 21:51:36.94 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:36.94 server  Completed estimating recovery log boundaries for database 'model'.
00:00000:00001:2005/10/07 21:51:36.95 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:36.95 server  Started ANALYSIS pass for database 'model'.
00:00000:00001:2005/10/07 21:51:36.95 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:36.95 server  Completed ANALYSIS pass for database 'model'.
00:00000:00001:2005/10/07 21:51:36.95 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:36.95 server  Started REDO pass for database 'model'. The total number of log records to process is 29.
00:00000:00001:2005/10/07 21:51:36.95 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:36.95 server  Redo pass of recovery has processed 2 committed and 0 aborted transactions.
00:00000:00001:2005/10/07 21:51:36.95 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:36.95 server  Completed REDO pass for database 'model'.
00:00000:00001:2005/10/07 21:51:36.95 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:36.95 server  Recovery of database 'model' will undo incomplete nested top actions.
00:00000:00001:2005/10/07 21:51:36.95 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:36.95 server  Started recovery checkpoint for database 'model'.
00:00000:00001:2005/10/07 21:51:36.95 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:36.95 server  Completed recovery checkpoint for database 'model'.
00:00000:00001:2005/10/07 21:51:36.95 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:36.95 server  Started filling free space info for database 'model'.
00:00000:00001:2005/10/07 21:51:36.95 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:37.02 server  Completed filling free space info for database 'model'.
00:00000:00001:2005/10/07 21:51:37.02 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:37.02 server  Started cleaning up the default data cache for database 'model'.
00:00000:00001:2005/10/07 21:51:37.02 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:37.02 server  Completed cleaning up the default data cache for database 'model'.
00:00000:00001:2005/10/07 21:51:37.02 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:37.02 server  Checking external objects.
00:00000:00001:2005/10/07 21:51:37.02 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:37.05 server  The transaction log in the database 'model' will use I/O size of 2 Kb.
00:00000:00001:2005/10/07 21:51:37.05 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:37.05 server  Database 'model' is now online.
00:00000:00001:2005/10/07 21:51:37.05 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:37.05 server  The logical pagesize of the server is 2 Kb.
00:00000:00001:2005/10/07 21:51:37.05 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:37.05 server  0 dump conditions detected at boot time
00:00000:00001:2005/10/07 21:51:37.05 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:37.05 server  Resident Node id: d57aee651e2b
00:00000:00001:2005/10/07 21:51:37.05 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:37.05 server  Transaction coordinator initialized.
00:00000:00001:2005/10/07 21:51:37.05 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:37.05 server  Clearing temp db
00:00000:00001:2005/10/07 21:51:37.39 server  The transaction log in the database 'tempdb' will use I/O size of 2 Kb.
00:00000:00001:2005/10/07 21:51:37.39 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:37.42 server  The transaction log in the database 'tempdb' will use I/O size of 2 Kb.
00:00000:00001:2005/10/07 21:51:37.42 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:37.44 server  Database 'tempdb' is now online.
00:00000:00001:2005/10/07 21:51:37.44 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:37.52 server  Recovering database 'sybsystemprocs'.
00:00000:00001:2005/10/07 21:51:37.52 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:37.52 server  Started estimating recovery log boundaries for database 'sybsystemprocs'.
00:00000:00001:2005/10/07 21:51:37.53 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:37.54 server  Database 'sybsystemprocs', checkpoint=(28549, 9), first=(28549, , last=(28549, 1.
00:00000:00001:2005/10/07 21:51:37.54 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:37.54 server  Completed estimating recovery log boundaries for database 'sybsystemprocs'.
00:00000:00001:2005/10/07 21:51:37.54 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:37.54 server  Started ANALYSIS pass for database 'sybsystemprocs'.
00:00000:00001:2005/10/07 21:51:37.54 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:37.54 server  Completed ANALYSIS pass for database 'sybsystemprocs'.
00:00000:00001:2005/10/07 21:51:37.54 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:37.54 server  Started REDO pass for database 'sybsystemprocs'. The total number of log records to process is 11.
00:00000:00001:2005/10/07 21:51:37.54 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:37.54 server  Redo pass of recovery has processed 1 committed and 0 aborted transactions.
00:00000:00001:2005/10/07 21:51:37.54 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:37.54 server  Completed REDO pass for database 'sybsystemprocs'.
00:00000:00001:2005/10/07 21:51:37.54 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:37.54 server  Recovery of database 'sybsystemprocs' will undo incomplete nested top actions.
00:00000:00001:2005/10/07 21:51:37.54 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:37.54 server  Started recovery checkpoint for database 'sybsystemprocs'.
00:00000:00001:2005/10/07 21:51:37.54 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:37.55 server  Completed recovery checkpoint for database 'sybsystemprocs'.
00:00000:00001:2005/10/07 21:51:37.55 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:37.55 server  Started filling free space info for database 'sybsystemprocs'.
00:00000:00001:2005/10/07 21:51:37.55 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:38.32 server  Completed filling free space info for database 'sybsystemprocs'.
00:00000:00001:2005/10/07 21:51:38.32 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:38.33 server  Started cleaning up the default data cache for database 'sybsystemprocs'.
00:00000:00001:2005/10/07 21:51:38.33 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:38.33 server  Completed cleaning up the default data cache for database 'sybsystemprocs'.
00:00000:00001:2005/10/07 21:51:38.33 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:38.33 server  Checking external objects.
00:00000:00001:2005/10/07 21:51:38.33 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:38.36 server  The transaction log in the database 'sybsystemprocs' will use I/O size of 2 Kb.
00:00000:00001:2005/10/07 21:51:38.37 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:38.52 server  The transaction log in the database 'sybsystemprocs' will use I/O size of 2 Kb.
00:00000:00001:2005/10/07 21:51:38.52 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:38.52 server  Database 'sybsystemprocs' is now online.
00:00000:00001:2005/10/07 21:51:38.52 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:38.62 server  Database 'model' is now online.
00:00000:00001:2005/10/07 21:51:38.62 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:38.75 server  Database 'sybsystemdb' is now online.
00:00000:00001:2005/10/07 21:51:38.75 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:38.83 server  Database 'tempdb' is now online.
00:00000:00001:2005/10/07 21:51:38.83 kernel  Failed to log the current message in the Windows NT event log
00:00000:00010:2005/10/07 21:51:38.87 kernel  network name ibm-thinkpad, interface IPv4, address 192.168.1.100, type nlwnsck, port 5000, filter NONE
00:00000:00010:2005/10/07 21:51:38.88 kernel  Failed to log the current message in the Windows NT event log
00:00000:00010:2005/10/07 21:51:38.88 kernel  A listener with protocol nlwnsck, host ibm-thinkpad, port 5000 , engine 0 already exists.
00:00000:00010:2005/10/07 21:51:38.89 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:39.00 server  Recovery complete.
00:00000:00001:2005/10/07 21:51:39.00 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:39.00 kernel  Reenlistment of DTC Transactions Complete
00:00000:00001:2005/10/07 21:51:39.00 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:39.00 server  SQL Server's default unicode sort order is 'binary'.
00:00000:00001:2005/10/07 21:51:39.00 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:39.02 server  SQL Server's default sort order is:
00:00000:00001:2005/10/07 21:51:39.02 server          'bin_cp850' (ID = 50)
00:00000:00001:2005/10/07 21:51:39.02 server  on top of default character set:
00:00000:00001:2005/10/07 21:51:39.02 server          'cp850' (ID = 2).
00:00000:00001:2005/10/07 21:51:39.02 kernel  Failed to log the current message in the Windows NT event log
00:00000:00001:2005/10/07 21:51:39.02 server  Master device size: 60 megabytes, or 30720 virtual pages. (A virtual page is 2048 bytes.)
00:00000:00001:2005/10/07 21:51:39.02 kernel  Failed to log the current message in the Windows NT event log

论坛徽章:
0
5 [报告]
发表于 2005-10-08 09:51 |只看该作者

sybase 不能启动.请帮助解决!

从日志上看,已经启动了,没有问题。
清除一下WINDOWS XP系统日志。检查一下sql.ini,看是否配置了两个相同的LISTENER
您需要登录后才可以回帖 登录 | 注册

本版积分规则 发表回复

  

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

清除 Cookies - ChinaUnix - Archiver - WAP - TOP