Sybase启动不了服务

百年码农 2010-08-19 12:57:50
问题描述：
在服务中启动Sybase的服务，弹出信息“服务启动后又停止”。
昨天晚上还可以，今天早上来就不行了....

日志文件：
00:00000:00000:2010/08/19 12:29:32.04 kernel Use license file d:\sybase\SYSAM-1_0\licenses\license.dat.
00:00000:00000:2010/08/19 12:29:32.04 kernel Failed to log the current message in the Windows NT event log
00:00000:00000:2010/08/19 12:29:32.06 kernel Checked out license ASE_SERVER
00:00000:00000:2010/08/19 12:29:32.06 kernel Failed to log the current message in the Windows NT event log
00:00000:00000:2010/08/19 12:29:32.06 kernel Adaptive Server Enterprise Edition
00:00000:00000:2010/08/19 12:29:32.06 kernel Failed to log the current message in the Windows NT event log
00:00000:00000:2010/08/19 12:29:32.07 kernel Using config area from primary master device.
00:00000:00000:2010/08/19 12:29:32.09 kernel Warning: Using default file 'd:\sybase\PC200908272102.cfg' since a configuration file was not specified. Specify a configuration file name in the RUNSERVER file to avoid this message.
00:00000:00000:2010/08/19 12:29:32.09 kernel Failed to log the current message in the Windows NT event log
00:00000:00000:2010/08/19 12:29:32.18 kernel Using 100000 file descriptors.
00:00000:00000:2010/08/19 12:29:32.18 kernel Adaptive Server Enterprise/12.5.2/EBF 11798/P/NT (IX86)/OS 4.0/ase1252/1831/32-bit/OPT/Fri Apr 09 04:15:03 2004
00:00000:00000:2010/08/19 12:29:32.18 kernel Confidential property of Sybase, Inc.
00:00000:00000:2010/08/19 12:29:32.18 kernel Copyright 1987, 2004
00:00000:00000:2010/08/19 12:29:32.18 kernel Sybase, Inc. All rights reserved.
00:00000:00000:2010/08/19 12:29:32.18 kernel Unpublished rights reserved under U.S. copyright laws.
00:00000:00000:2010/08/19 12:29:32.18 kernel
00:00000:00000:2010/08/19 12:29:32.18 kernel This software contains confidential and trade secret information of Sybase,
00:00000:00000:2010/08/19 12:29:32.18 kernel Inc. Use, duplication or disclosure of the software and documentation by
00:00000:00000:2010/08/19 12:29:32.18 kernel the U.S. Government is subject to restrictions set forth in a license
00:00000:00000:2010/08/19 12:29:32.18 kernel agreement between the Government and Sybase, Inc. or other written
00:00000:00000:2010/08/19 12:29:32.18 kernel agreement specifying the Government's rights to use the software and any
00:00000:00000:2010/08/19 12:29:32.18 kernel applicable FAR provisions, for example, FAR 52.227-19.
00:00000:00000:2010/08/19 12:29:32.18 kernel Sybase, Inc. One Sybase Drive, Dublin, CA 94568, USA
00:00000:00000:2010/08/19 12:29:32.18 kernel ASE booted on Windows XP build 2600 Service Pack 3.
00:00000:00000:2010/08/19 12:29:32.18 kernel Using 'd:\sybase\PC200908272102.cfg' for configuration information.
00:00000:00000:2010/08/19 12:29:32.18 kernel Failed to log the current message in the Windows NT event log
00:00000:00000:2010/08/19 12:29:32.18 kernel Logging ASE messages in file 'd:\sybase\ASE-12_5\install\PC200908272102.log'.
00:00000:00000:2010/08/19 12:29:32.21 kernel Initializing MSDTC Connection
00:00000:00000:2010/08/19 12:29:32.21 kernel Failed to log the current message in the Windows NT event log
00:00000:00000:2010/08/19 12:29:32.25 kernel The DTC Operation DtcGetTransactionManagerC failed with error DTC Services not available (0x8004d01b)
00:00000:00000:2010/08/19 12:29:32.25 kernel Failed to log the current message in the Windows NT event log
00:00000:00000:2010/08/19 12:29:32.25 kernel MSDTC Initialization failed
00:00000:00000:2010/08/19 12:29:32.25 kernel Failed to log the current message in the Windows NT event log
00:00000:00000:2010/08/19 12:29:32.25 kernel Platform TCP network is forced to IPv4-only.
00:00000:00000:2010/08/19 12:29:32.25 kernel Failed to log the current message in the Windows NT event log
00:00000:00000:2010/08/19 12:29:32.25 kernel SQL Server booted with TCP_NODELAY enabled.
00:00000:00000:2010/08/19 12:29:32.25 kernel Failed to log the current message in the Windows NT event log
00:00000:00000:2010/08/19 12:29:32.25 kernel *** WARNING ******************
00:00000:00000:2010/08/19 12:29:32.25 kernel Failed to log the current message in the Windows NT event log
00:00000:00000:2010/08/19 12:29:32.25 kernel Operating system may favor the system cache when memory is at a premium.
To disable this warning, set the registry parameter 'LargeSystemCache' to 0 in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management.
00:00000:00000:2010/08/19 12:29:32.25 kernel Failed to log the current message in the Windows NT event log
00:00000:00000:2010/08/19 12:29:32.25 kernel SQL Server NT process id is 0xbb4.
00:00000:00000:2010/08/19 12:29:32.25 kernel SQL Server was started as a Service.
00:00000:00000:2010/08/19 12:29:32.25 kernel SSL Plus v3.1.5 security modules loaded successfully.
00:00000:00000:2010/08/19 12:29:32.25 kernel Failed to log the current message in the Windows NT event log
00:00000:00000:2010/08/19 12:29:32.25 kernel Network and device connection limit is 99992.
00:00000:00000:2010/08/19 12:29:32.32 server Number of blocks left for proc headers: 3232.
00:00000:00000:2010/08/19 12:29:32.34 server Proc header memory allocated 1616 pages for each per engine cache
00:00000:00000:2010/08/19 12:29:32.34 server Size of the 16K memory pool: 3264 Kb
00:00000:00000:2010/08/19 12:29:32.34 kernel Failed to log the current message in the Windows NT event log
00:00000:00000:2010/08/19 12:29:32.34 server Size of the 2K memory pool: 4928 Kb
00:00000:00000:2010/08/19 12:29:32.34 kernel Failed to log the current message in the Windows NT event log
00:00000:00000:2010/08/19 12:29:32.34 server Memory allocated for the default data cache cachelet 1: 8192 Kb
00:00000:00000:2010/08/19 12:29:32.34 kernel Initializing virtual device 0, 'd:\sybase\data\master.dat' with dsync 'on'.
00:00000:00000:2010/08/19 12:29:32.34 kernel Virtual device 0 started using asynchronous i/o.
00:00000:00000:2010/08/19 12:29:32.34 kernel Worker Thread Manager is not enabled for use in SQL Server.
00:00000:00000:2010/08/19 12:29:32.34 kernel Failed to log the current message in the Windows NT event log
00:00000:00000:2010/08/19 12:29:32.34 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:2010/08/19 12:29:32.34 kernel Failed to log the current message in the Windows NT event log
00:00000:00000:2010/08/19 12:29:32.35 kernel engine 0, os pid 232 online
00:00000:00000:2010/08/19 12:29:32.35 kernel Failed to log the current message in the Windows NT event log
00:00000:00000:2010/08/19 12:29:32.35 server No active traceflags
00:00000:00000:2010/08/19 12:29:32.35 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:32.35 kernel libomni1 - Component Integration Services loaded; version 'libomni1 - Component Integration Services/12.5.2/EBF 11798/P/NT (IX86)/OS 4.0/ase1252/1831/32-bit/OPT/Fri Apr 09 04:15:03 2004'.
00:00000:00001:2010/08/19 12:29:32.35 kernel libomni1 - Component Integration Services: using 'Sybase Client-Library/12.5.1/P-EBF11786 ESD #2/PC Intel/BUILD1251-002/OPT/Tue Apr 06 22:50:49 2004'
00:00000:00001:2010/08/19 12:29:32.35 server Opening Master Database ...
00:00000:00001:2010/08/19 12:29:32.40 server Loading SQL Server's default sort order and character set
00:00000:00001:2010/08/19 12:29:32.40 server Loaded default Unilib conversion handle.
00:00000:00001:2010/08/19 12:29:32.40 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:32.42 server Recovering database 'master'.
00:00000:00001:2010/08/19 12:29:32.42 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:32.42 server Started estimating recovery log boundaries for database 'master'.
00:00000:00001:2010/08/19 12:29:32.42 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:32.42 server Completed estimating recovery log boundaries for database 'master'.
00:00000:00001:2010/08/19 12:29:32.42 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:32.42 server Started ANALYSIS pass for database 'master'.
00:00000:00001:2010/08/19 12:29:32.42 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:32.42 server Completed ANALYSIS pass for database 'master'.
00:00000:00001:2010/08/19 12:29:32.42 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:32.42 server Started REDO pass for database 'master'. The total number of log records to process is 1.
00:00000:00001:2010/08/19 12:29:32.42 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:32.42 server Completed REDO pass for database 'master'.
00:00000:00001:2010/08/19 12:29:32.42 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:32.42 server Recovery of database 'master' will undo incomplete nested top actions.
...全文
352 10 打赏 收藏 转发到动态 举报
写回复
用AI写文章
10 条回复
切换为时间正序
请发表友善的回复…
发表回复
zhuzhangliang 2010-11-03
  • 打赏
  • 举报
 回复
可以改为开发版本啊
whshizy 2010-10-06
  • 打赏
  • 举报
 回复
Server PC200908272102 not registered in the interfaces file or directory services
是接口文件的问题，没有在dsedit中注册这个服务名
tmx 2010-09-25
  • 打赏
  • 举报
 回复
通过日志看出，是授权文件出了问题，或者是试用版本到期，建议联系SYBASE公司，解决授权问题。
iihero 2010-08-23
  • 打赏
  • 举报
 回复
5楼是原因，4楼是结果。
Sybase数据库恢复 2010-08-23
  • 打赏
  • 举报
 回复
[Quote=引用 6 楼 iihero 的回复:]

5楼是原因，4楼是结果。
[/Quote]

呵呵，光往后面看了， 只看到了结果。
yanran_hill 2010-08-22
  • 打赏
  • 举报
 回复

Server PC200908272102 not registered in the interfaces file or directory services
在接口文件中是否缺少了对PC20090827210的注册?使用DsEdit工具看一下
百年码农 2010-08-19
  • 打赏
  • 举报
 回复
00:00000:00001:2010/08/19 12:29:32.42 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:32.42 server Started recovery checkpoint for database 'master'.
00:00000:00001:2010/08/19 12:29:32.42 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:32.42 server Completed recovery checkpoint for database 'master'.
00:00000:00001:2010/08/19 12:29:32.42 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:32.42 server Started filling free space info for database 'master'.
00:00000:00001:2010/08/19 12:29:32.42 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.51 server Completed filling free space info for database 'master'.
00:00000:00001:2010/08/19 12:29:34.51 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.51 server Started cleaning up the default data cache for database 'master'.
00:00000:00001:2010/08/19 12:29:34.51 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.51 server Completed cleaning up the default data cache for database 'master'.
00:00000:00001:2010/08/19 12:29:34.51 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.53 server Checking external objects.
00:00000:00001:2010/08/19 12:29:34.53 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.54 server Database 'master' is now online.
00:00000:00001:2010/08/19 12:29:34.54 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.54 server The transaction log in the database 'master' will use I/O size of 2 Kb.
00:00000:00001:2010/08/19 12:29:34.54 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.54 server Warning: ASE_HA has no valid license and therefore is not initialized.
00:00000:00001:2010/08/19 12:29:34.54 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.54 server server name is 'PC200908272102'
00:00000:00001:2010/08/19 12:29:34.54 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.56 server Activating disk 'jzx_db' of size 2611200 KB.
00:00000:00001:2010/08/19 12:29:34.56 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.56 kernel Initializing virtual device 2, 'D:\sybase\jzx_db' with dsync 'on'.
00:00000:00001:2010/08/19 12:29:34.56 kernel Virtual device 2 started using asynchronous i/o.
00:00000:00001:2010/08/19 12:29:34.56 server Activating disk 'jzx_log' of size 1075200 KB.
00:00000:00001:2010/08/19 12:29:34.56 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.56 kernel Initializing virtual device 3, 'D:\sybase\jzx_log' with dsync 'on'.
00:00000:00001:2010/08/19 12:29:34.56 kernel Virtual device 3 started using asynchronous i/o.
00:00000:00001:2010/08/19 12:29:34.56 server Activating disk 'sysprocsdev' of size 122880 KB.
00:00000:00001:2010/08/19 12:29:34.56 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.56 kernel Initializing virtual device 1, 'd:\sybase\data\sysprocs.dat' with dsync 'on'.
00:00000:00001:2010/08/19 12:29:34.56 kernel Virtual device 1 started using asynchronous i/o.
00:00000:00001:2010/08/19 12:29:34.59 server Recovering database 'sybsystemdb'.
00:00000:00001:2010/08/19 12:29:34.59 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.59 server Started estimating recovery log boundaries for database 'sybsystemdb'.
00:00000:00001:2010/08/19 12:29:34.59 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.60 server Completed estimating recovery log boundaries for database 'sybsystemdb'.
00:00000:00001:2010/08/19 12:29:34.60 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.60 server Started ANALYSIS pass for database 'sybsystemdb'.
00:00000:00001:2010/08/19 12:29:34.60 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.60 server Completed ANALYSIS pass for database 'sybsystemdb'.
00:00000:00001:2010/08/19 12:29:34.60 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.60 server Started REDO pass for database 'sybsystemdb'. The total number of log records to process is 1.
00:00000:00001:2010/08/19 12:29:34.60 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.60 server Completed REDO pass for database 'sybsystemdb'.
00:00000:00001:2010/08/19 12:29:34.60 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.60 server Recovery of database 'sybsystemdb' will undo incomplete nested top actions.
00:00000:00001:2010/08/19 12:29:34.60 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.60 server Started recovery checkpoint for database 'sybsystemdb'.
00:00000:00001:2010/08/19 12:29:34.60 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.60 server Completed recovery checkpoint for database 'sybsystemdb'.
Sybase数据库恢复 2010-08-19
  • 打赏
  • 举报
 回复
端口冲突：Cannot start any network listeners.
百年码农 2010-08-19
  • 打赏
  • 举报
 回复
00:00000:00001:2010/08/19 12:29:34.70 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.70 server Resident Node id: c9bf395bfba3
00:00000:00001:2010/08/19 12:29:34.70 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.70 server Transaction coordinator initialized.
00:00000:00001:2010/08/19 12:29:34.70 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.70 server Clearing temp db
00:00000:00001:2010/08/19 12:29:34.76 server The transaction log in the database 'tempdb' will use I/O size of 2 Kb.
00:00000:00001:2010/08/19 12:29:34.76 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.78 server Database 'tempdb' is now online.
00:00000:00001:2010/08/19 12:29:34.78 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.81 server Recovering database 'sybsystemprocs'.
00:00000:00001:2010/08/19 12:29:34.81 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.81 server Started estimating recovery log boundaries for database 'sybsystemprocs'.
00:00000:00001:2010/08/19 12:29:34.81 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.81 server Completed estimating recovery log boundaries for database 'sybsystemprocs'.
00:00000:00001:2010/08/19 12:29:34.81 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.81 server Started ANALYSIS pass for database 'sybsystemprocs'.
00:00000:00001:2010/08/19 12:29:34.81 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.81 server Completed ANALYSIS pass for database 'sybsystemprocs'.
00:00000:00001:2010/08/19 12:29:34.81 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.81 server Started REDO pass for database 'sybsystemprocs'. The total number of log records to process is 1.
00:00000:00001:2010/08/19 12:29:34.81 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.81 server Completed REDO pass for database 'sybsystemprocs'.
00:00000:00001:2010/08/19 12:29:34.81 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.81 server Recovery of database 'sybsystemprocs' will undo incomplete nested top actions.
00:00000:00001:2010/08/19 12:29:34.81 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.81 server Started recovery checkpoint for database 'sybsystemprocs'.
00:00000:00001:2010/08/19 12:29:34.81 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.82 server Completed recovery checkpoint for database 'sybsystemprocs'.
00:00000:00001:2010/08/19 12:29:34.82 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.82 server Started filling free space info for database 'sybsystemprocs'.
00:00000:00001:2010/08/19 12:29:34.82 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:35.87 server Completed filling free space info for database 'sybsystemprocs'.
00:00000:00001:2010/08/19 12:29:35.87 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:35.87 server Started cleaning up the default data cache for database 'sybsystemprocs'.
00:00000:00001:2010/08/19 12:29:35.87 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:35.87 server Completed cleaning up the default data cache for database 'sybsystemprocs'.
00:00000:00001:2010/08/19 12:29:35.87 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:35.87 server Checking external objects.
00:00000:00001:2010/08/19 12:29:35.87 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:35.87 server The transaction log in the database 'sybsystemprocs' will use I/O size of 2 Kb.
00:00000:00001:2010/08/19 12:29:35.87 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:35.87 server Database 'sybsystemprocs' is now online.
00:00000:00001:2010/08/19 12:29:35.87 kernel Failed to log the current message in the Windows NT event log
00:00000:00011:2010/08/19 12:29:35.89 kernel Connectivity Library (Directory Control Layer) Error: Error returned by service provider.
00:00000:00011:2010/08/19 12:29:35.89 kernel Failed to log the current message in the Windows NT event log
00:00000:00011:2010/08/19 12:29:35.89 kernel Connectivity Library (Directory Control Layer) Error: (InterfacesDriver): Requested server name not found.
00:00000:00011:2010/08/19 12:29:35.89 kernel Failed to log the current message in the Windows NT event log
00:00000:00011:2010/08/19 12:29:35.89 kernel Server PC200908272102 not registered in the interfaces file or directory services.
00:00000:00011:2010/08/19 12:29:35.89 kernel Failed to log the current message in the Windows NT event log
00:00000:00011:2010/08/19 12:29:35.89 kernel Cannot start any network listeners.
00:00000:00011:2010/08/19 12:29:35.89 kernel Failed to log the current message in the Windows NT event log
00:00000:00011:2010/08/19 12:29:35.89 kernel ueshutdown: exiting
00:00000:00011:2010/08/19 12:29:35.89 kernel Failed to log the current message in the Windows NT event log


可能日志有点多了.
谢谢各位！！！
百年码农 2010-08-19
  • 打赏
  • 举报
 回复
00:00000:00001:2010/08/19 12:29:34.60 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.60 server Started filling free space info for database 'sybsystemdb'.
00:00000:00001:2010/08/19 12:29:34.60 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.60 server Completed filling free space info for database 'sybsystemdb'.
00:00000:00001:2010/08/19 12:29:34.60 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.60 server Started cleaning up the default data cache for database 'sybsystemdb'.
00:00000:00001:2010/08/19 12:29:34.60 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.60 server Completed cleaning up the default data cache for database 'sybsystemdb'.
00:00000:00001:2010/08/19 12:29:34.60 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.60 server Boot Count: 554
00:00000:00001:2010/08/19 12:29:34.60 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.64 server Checking external objects.
00:00000:00001:2010/08/19 12:29:34.64 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.64 server The transaction log in the database 'sybsystemdb' will use I/O size of 2 Kb.
00:00000:00001:2010/08/19 12:29:34.64 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.65 server Database 'sybsystemdb' is now online.
00:00000:00001:2010/08/19 12:29:34.65 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.67 server Recovering database 'model'.
00:00000:00001:2010/08/19 12:29:34.67 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.67 server Started estimating recovery log boundaries for database 'model'.
00:00000:00001:2010/08/19 12:29:34.67 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.67 server Completed estimating recovery log boundaries for database 'model'.
00:00000:00001:2010/08/19 12:29:34.67 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.67 server Started ANALYSIS pass for database 'model'.
00:00000:00001:2010/08/19 12:29:34.67 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.67 server Completed ANALYSIS pass for database 'model'.
00:00000:00001:2010/08/19 12:29:34.68 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.68 server Started REDO pass for database 'model'. The total number of log records to process is 1.
00:00000:00001:2010/08/19 12:29:34.68 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.68 server Completed REDO pass for database 'model'.
00:00000:00001:2010/08/19 12:29:34.68 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.68 server Recovery of database 'model' will undo incomplete nested top actions.
00:00000:00001:2010/08/19 12:29:34.68 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.68 server Started recovery checkpoint for database 'model'.
00:00000:00001:2010/08/19 12:29:34.68 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.68 server Completed recovery checkpoint for database 'model'.
00:00000:00001:2010/08/19 12:29:34.68 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.68 server Started filling free space info for database 'model'.
00:00000:00001:2010/08/19 12:29:34.68 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.68 server Completed filling free space info for database 'model'.
00:00000:00001:2010/08/19 12:29:34.68 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.68 server Started cleaning up the default data cache for database 'model'.
00:00000:00001:2010/08/19 12:29:34.68 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.68 server Completed cleaning up the default data cache for database 'model'.
00:00000:00001:2010/08/19 12:29:34.68 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.68 server Checking external objects.
00:00000:00001:2010/08/19 12:29:34.68 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.68 server The transaction log in the database 'model' will use I/O size of 2 Kb.
00:00000:00001:2010/08/19 12:29:34.68 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.70 server Database 'model' is now online.
00:00000:00001:2010/08/19 12:29:34.70 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.70 server The logical pagesize of the server is 2 Kb.
00:00000:00001:2010/08/19 12:29:34.70 kernel Failed to log the current message in the Windows NT event log
00:00000:00001:2010/08/19 12:29:34.70 server 0 dump conditions detected at boot time
双机软件中sybase服务启动失败的解决之道
解决sybase数据库服务启动失败的方法
sybase 11.03 for scounix5
SYBASE SQL SERVER V11.0.3.2版在SCO5.0.X上的安装说明 一、先建sybase组，再建sybase用户 注意：sybase用户必须属于sybase组，假定sybase用户的主目录是：/u/sybase 二、调整系统核心参数 1. 共享内存 #cd /etc/conf/cf.d #./configure 选择(16) share data SHMMAX: 输入新值（如：67108864） 退出 2. 激活异步I/O #cd /etc/conf/sdevice.d #vi aio 将“N"改为”Y" #vi suds 将“N"改为”Y" #vi /etc/rc2 在最后一行加入下面一行 /etc/suds_ctrl -a 100 (注意：100是sybase用户的gid，即组标示。) 3. 重建内核并重启 #/etc/conf/cf.d/link_unix #reboot 三、安装sybase以及 a. 在sybase用户下展开文件，安装sybase compress -d SYBASE.TAR.Z tar xvf SYBASE.TAR 四、安装sybase development system a. 在sybase用户下展开文件 compress -d SYBASE_D.TAR.Z tar xvf SYABASE_D.TAR b. 开发系统的安装文件如下∶ sybload sybimage c. 安装 chmod 777 sybload ./sybload -D press 'L'键 /usr/sybase/sybimage press 'y'键，输入下列CAS码 BYBKBYBKHIBYBYIOHYDQBKBKBKBORNUDJU press '1'键 press 'y'键 五、用sybase用户登陆，执行sybinit， 配置 1、interfaces文件 2、sybase server 其中master等设备文件可以放在/u/sybase/dev目录下 3、sybase backup server 配置完后，会自动装载数据库，可用showserver命令检查是否启动。 (详细配置说明参见$HOME/sample_sessions/install.spl) 修改.profile文件。在其中加入环境参数。 DSQUERY=SERVERNAME #sybase server的名字，sybinit安装时起的名字 SYBASE=$HOME #这里是指interfaces文件所在的路径 export DSQUERY SYBASE 另外，PATH中可加入$HOME/install路径，方便执行startserver，showserver命令 六、用root登陆，在/etc/rc2.d中加入开机时自启动文件：S99startsybase 该文件的内容为： su - sybase -c "/u/sybase/install/startserver -f /u/sybase/RUN_SERVERNAME 1>/dev/null 2>/dev/null" su - sybase -c "/u/sybase/install/startserver -f /u/sybase/RUN_BACKUP_SERVR 1>/dev/null 2>/dev/null" 其中，SERVERNAME，RUN_BACKUP_SERVER分别为你的sybase服务器和备份服务器的名字。 七、登陆数据库后需要立即修改的参数 八、建立用户数据库
Sybase数据库连接工具
使用方法: 1.解压下载的sqladv-12_5.zip至任意目录下！ 2.编辑sqladv-12_5\ini目录下的sql.ini文件，添加想要连接的Sybase服务器信息。 文件sqladv-12_5\ini\sql.ini中有个示例： [syb1254] master=NLWNSCK,192.168.1.5,5000 query=NLWNSCK,192.168.1.5,5000 你新添加Sybase服务器的时候，仅需要在sqladv-12_5\ini\sql.ini文件的尾部 添加类似上面的信息。中括号中表示服务器名称，你可以自己起一个标记性的 名字。将192.168.100.2替换成你将要连接的Sybase服务器的IP地址，将8888 替换成Sybase服务器的监听端口。 注意：中间使用英文逗号分割。 3.双击目录sqladv-12_5下的“启动sqladv.bat”文件，即可运行SQL Advantage工具了。不要执行“sqladv.exe”这个文件，因为没有配置环境变量SYBASE。 直接执行 "start_sqladv.bat”即可。 4.打开SQL Advantage工具后，点菜单Server>Connect，在连接信息配置窗口中 其中Server列表中的Sybase服务名就是在第二步中配置的。Client host表示连接到Sybase 服务器中的客户端标志。 如果想配置网络包大小、大文本字段的长度、客户端字符集等属性，可以点Options...按钮 成功连接到Sybase服务器后，查看数据库内的表，点菜单View>Pick Lists>Tables & Columns
Sybase12.5-11449补丁.part04
11449补丁，安装补丁后可在windows服务管理启动sybase服务，打包一共4个文件，这是最后一个。
如何单独在备份机上启动Sybase ASE12.5
如何单独在备份机上启动Sybase ASE12.5
Sybase

2,596

社区成员

25,614

社区内容

发帖
与我相关
我的任务
社区描述
Sybase相关技术讨论区
社区管理员
  • Sybase社区
加入社区
  • 近7日
  • 近30日
  • 至今

加载中

查看更多榜单
社区公告
暂无公告

试试用AI创作助手写篇文章吧

+ 用AI写文章