关于LOG SUSPEND疑问？急！(已解决，谢谢大家）

silamuwang

今天，公司ERP做年结帐，操作比较大，然后用sp_who看后，发现状态为LOG SUSPEND，上网查到是日志满了，然后执行dump transaction erp ，年结帐操作还是无法执行，状态仍是LOG SUSPEND，最后我对日志设备进行扩容，没有用命令，在sybase central下操作的，首先建立一个新设备用来存储日志，然后把这个设备分给这个数据库用，新设备有2G，然后执行年结帐，竟然还做不过去，状态还是LOG SUSPEND，郁闷了。各位还有什么高招吗？

[ 本帖最后由 silamuwang 于 2009-1-9 16:45 编辑 ]

sybase软件服务

检查一下syslogshold这张表，看看是否有进程堵了日志。

silamuwang

刚看了syslogshold表，里面就有一个进程，这个进程就是执行年结帐操作的进程，此时用sp_who查看，发现该进程处于LOG SUSPEND状态

sybase软件服务

用sa用户试一下
dump tran <userdb_name> with truncate_only
如果还不行，试一下
dump tran <userdb_name> with nolog

此业务如果以前运行没有问题，怀疑是日志无法自动截断，导致日志满。
可以使用sp_helpdb <userdb_name>看一下

chuxu

在sybase central下操作的，首先建立一个新设备用来存储日志，然后把这个设备分给这个数据库用，

你确认这2G是分配给了LOG？按照道理是分配给数据库的时候才能指定是data还是log，划分设备的时候没有地方指定呀？

sybase软件服务

如果你已手工做过截断日志，并成功，但还无法进行下去业务。也许需要考虑业务是否有变化，或数据量是否有大的变化。或者看看日志有没有问题。

silamuwang

我是在分配给数据库的时候才能指定是log的，而且用sp_helpsegment logsegment看过，日志空间已经增加。dump清空日志我也做过。sybase日志：
00:00000:00007:2009/01/09 14:39:45.64 server  1 task(s) are sleeping waiting for space to become available in the log segment for database hjdata.
02:00000:00007:2009/01/09 14:40:45.59 server  1 task(s) are sleeping waiting for space to become available in the log segment for database hjdata.
03:00000:00007:2009/01/09 14:41:45.72 server  1 task(s) are sleeping waiting for space to become available in the log segment for database hjdata.
00:00000:00007:2009/01/09 14:42:45.67 server  1 task(s) are sleeping waiting for space to become available in the log segment for database hjdata.
02:00000:00007:2009/01/09 14:43:45.66 server  1 task(s) are sleeping waiting for space to become available in the log segment for database hjdata.
02:00000:00007:2009/01/09 14:44:45.68 server  1 task(s) are sleeping waiting for space to become available in the log segment for database hjdata.
02:00000:00007:2009/01/09 14:45:45.79 server  1 task(s) are sleeping waiting for space to become available in the log segment for database hjdata.
03:00000:00007:2009/01/09 14:46:45.77 server  1 task(s) are sleeping waiting for space to become available in the log segment for database hjdata.
03:00000:00007:2009/01/09 14:47:45.77 server  1 task(s) are sleeping waiting for space to become available in the log segment for database hjdata.
03:00000:00007:2009/01/09 14:48:45.79 server  1 task(s) are sleeping waiting for space to become available in the log segment for database hjdata.
03:00000:00007:2009/01/09 14:49:45.79 server  1 task(s) are sleeping waiting for space to become available in the log segment for database hjdata.
00:00000:00007:2009/01/09 14:50:45.87 server  1 task(s) are sleeping waiting for space to become available in the log segment for database hjdata.
02:00000:00007:2009/01/09 14:51:45.88 server  1 task(s) are sleeping waiting for space to become available in the log segment for database hjdata.
03:00000:00007:2009/01/09 14:52:45.97 server  1 task(s) are sleeping waiting for space to become available in the log segment for database hjdata.
03:00000:00007:2009/01/09 14:53:45.98 server  1 task(s) are sleeping waiting for space to become available in the log segment for database hjdata.
02:00000:00007:2009/01/09 14:54:45.99 server  1 task(s) are sleeping waiting for space to become available in the log segment for database hjdata.
03:00000:00007:2009/01/09 14:55:46.06 server  1 task(s) are sleeping waiting for space to become available in the log segment for database hjdata.
00:00000:00007:2009/01/09 14:56:46.08 server  1 task(s) are sleeping waiting for space to become available in the log segment for database hjdata.
00:00000:00007:2009/01/09 14:57:46.10 server  1 task(s) are sleeping waiting for space to become available in the log segment for database hjdata.
00:00000:00007:2009/01/09 14:58:46.10 server  1 task(s) are sleeping waiting for space to become available in the log segment for database hjdata.
00:00000:00007:2009/01/09 14:59:46.09 server  1 task(s) are sleeping waiting for space to become available in the log segment for database hjdata.
00:00000:00007:2009/01/09 15:00:46.09 server  1 task(s) are sleeping waiting for space to become available in the log segment for database hjdata

基本上都是这个错误

sybase软件服务

先把所有业务停下来，手工截断日志，用sp_helpdb hjdata看一下日志剩余是否正常。
然后只加载结帐业务，看是否能够成功。
如果成功了，恐怕需要考虑其他事务的问题；如果还出现日志满，恐怕需要评估业务数据量与日志空间的问题。

silamuwang

不好意思，问题解决了，是年结帐的时候还需要另外一个数据库，sybase报的是另外一个库的日志空间不够。谢谢大家的帮助。

hobbylu

估计日志设备没有加正确sp_helpdb看看