Google

master库日志满,server不能启动的解决

2007-08-26 19:34 来源: echoaix.cublog.cn 作者:echoaix 网友评论 0 条 浏览次数 234
 
master库日志满,server不能启动的解决

起因:
今天一个用户发来errorlog:如下
Recovering database 'master'
00:00000:00001:2004/03/12 10:05:27.70 server Redo pass of recovery has processed 10 committed and 0 aborted transactions.
00:00000:00001:2004/03/12 10:05:27.81 server No such message: 1105
00:00000:00001:2004/03/12 10:05:27.81 server There is no space available in SYSLOGS for process 1 to log a record for which space has been reserved. This process will retry at intervals of one minute. The internal error number is -4.
是 sybase 12.0 nt平台
第一步:
认为很简单,在启动文件中加-T3607 -m,然后用sa进
dump tran master with no_log或
alter database master on master_dev=xxxM 即可
问题:
启动报:Error: 3475, Severity: 21, State: 7
00:00000:00006:2004/03/12 10:38:55.71 server There is no space available in SYSLOGS for process 6 to log a record for which space has been reserved. This process will retry at intervals of one minute. The internal error number is -4.
用sa登陆进不去:报:
isql -Usa -Pxxx
Can't allocate space for object 'syslogs' in database 'master' because
'logsegment' segment is full/has no free extents. If you ran out of space in
syslogs, dump the transaction log. Otherwise, use ALTER DATABASE or
sp_extendsegment to increase size of the segment.
Msg 3475, Level 21, State 7:
There is no space available in SYSLOGS for process 6 to log a record for which
space has been reserved. This process will retry at intervals of one minute. The

internal error number is -4.
CT-LIBRARY error:
ct_connect(): user api layer: internal Client Library error: Read from t
he server has timed out.
第二步:从没遇到这种情况 再加 -T699(Turn off transaction logging for the entire SQL dataserver)
这次sa可进
执行
alter database master on master_dev=xxxM 报和上面一样的错
dump tran master with no_log也不行
本想bcp系统表再重建master,总是麻烦(懒),还是生产机
第三步: 再加-T7409
执行 alter database master on master_dev=xxxM ok
问题解决

上一篇: 下一篇:

相关主题:sybase  Sybase日志

网友评论