关于sybase事务管理问题

zhouzx_gogo

-
select @@ version
go

Adaptive Server Enterprise/12.5.0.3/EBF 11442 ESD#4/P/Sun_svr4/OS 5.8/rel12503/1939/64-bit/FBO/Sun Sep 21 05:21:37 2003   

应用软件是pb6.5开发的系统，利用存储过程计算数据库内部的表并形成金额表，对金额进行增减，但是现在时常数据有时（用户测试应用程序的计算过程没有问题）应用程序无法减少。
我想请教各位专家：
1.下面日志的部分是否会对存储过程有影响，对SYBASE的事务的管理是否有问题
2.cache如何增加，内存为2G，物理为16，是否太小，我在应用数据库上已经绑定了cache
3.MAINTENANCE TOKEN是什么意思
4.more alarms available，现已经把number of alarms默认40改为5000了
5.是否需要补丁sybase服务器。

04:00000:00239:2005/04/01 15:53:14.88 server  The 4K memory pool of named cache default data cache (cache id 0, cachelet id is configured too small for current demands (state 2). Transaction progress may cease or response time may increase.


Deadlock Id 65: Process (Familyid 1639, 1639) (suid 3852) was executing a MAINTENANCE TOKEN command at line 1.
SQL Text: ccur8361

Deadlock Id 65: Process (Familyid 1993, 1993) (suid 3757) was executing a MAINTENANCE TOKEN command at line 1.
SQL Text: select F_VAL from LSCONF where F_VKEY ='ZW_JZPZZS'
Deadlock Id 65: Process (Familyid 0, Spid 1993) was waiting for a 'shared intent' lock on the 'syscolumns' table in database 7 but process (Familyid 1639, Spid 1639) already held a 'shared intent' lock on it.
Deadlock Id 65: Process (Familyid 0, Spid 1639) was waiting for a 'shared intent' lock on the 'syscolumns' table in database 5 but process (Familyid 1993, Spid 1993) already held a 'exclusive table' lock on it.


Deadlock Id 98: Process (Familyid 1396, 1396) (suid 3735) was executing a MAINTENANCE TOKEN command at line 1.
SQL Text: ccur2984

Deadlock Id 98: Process (Familyid 663, 663) (suid 3743) was executing a MAINTENANCE TOKEN command at line 1.
SQL Text: select F_GNBH from LSUSGN WHERE F_ZGBH ='2021' and F_GNBH ='0145'
Deadlock Id 98: Process (Familyid 0, Spid 663) was waiting for a 'shared intent' lock on the 'syscolumns' table in database 7 but process (Familyid 1396, Spid 1396) already held a 'shared intent' lock on it.
Deadlock Id 98: Process (Familyid 0, Spid 1396) was waiting for a 'shared intent' lock on the 'syscolumns' table in database 5 but process (Familyid 663, Spid 663) already held a 'exclusive table' lock on it.

Deadlock Id 98: Process (Familyid 0, 1396) was chosen as the victim. End of deadlock information.



Error: 1105, Severity: 17, State: 3
03:00000:00782:2005/05/27 14:30:41.08 server  Can't allocate space for object 'syslogs' in database 'tempdb1' 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.
03:00000:00782:2005/05/27 14:30:41.08 server  Error: 21, Severity: 21, State: 1
03:00000:00782:2005/05/27 14:30:41.08 server  WARNING - Fatal Error 3475 occurred at May 27 2005  2:30PM.  Please note the error and time, and contact a user with System Administrator (SA) authorization.
03:00000:00782:2005/05/27 14:30:41.08 server  Error: 3475, Severity: 21, State: 7
03:00000:00782:2005/05/27 14:30:41.08 server  There is no space available in SYSLOGS for process 782 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.
00:00000:00782:2005/05/27 14:30:41.08 kernel  uasetalarm: no more alarms available
00:00000:00782:2005/05/27 14:30:41.08 kernel  uppause: No free alarms available.00:00000:00782:2005/05/27 14:30:41.09 kernel  ************************************
00:00000:00782:2005/05/27 14:30:41.09 kernel  pc: 0x000000008071c8d4 pcstkwalk+0x28(0x000001000a283cd8, 0x000001000a283450, 0x000000000000270f, 0x0000000000000002, 0x0000000000000000)
00:00000:00782:2005/05/27 14:30:41.09 kernel  pc: 0x000000008071c7bc ucstkgentrace+0x1c8(0x000000000000270f, 0x000000006aae047f, 0x0000000000000000, 0x000001007490b340, 0x000001006092a10
00:00000:00782:2005/05/27 14:30:41.09 kernel  pc: 0x00000000806d77e4 ucbacktrace+0xac(0x0000000000000000, 0x0000000000000001, 0x000000000002e400, 0x0000000000000001, 0x00000100609319b0)
00:00000:00782:2005/05/27 14:30:41.09 kernel  pc: 0x00000000801da5f8 terminate_process+0x7f0(0x000001006092a108, 0xffffffffffffffff, 0x0000000000000000, 0x000000000000010f, 0xfffffffffffffffc)
00:00000:00782:2005/05/27 14:30:41.09 kernel  pc: 0x000000008012fb48 plc__flush+0x9a4(0x0000000000000004, 0x0000000000000000, 0x0000000000000000, 0x000000000000129a, 0x0000000000000000)
00:00000:00782:2005/05/27 14:30:41.09 kernel  pc: 0x000000008037f1c0 xxs__lr_getmarker+0x134(0x000001007691a908, 0x0000000000000000, 0x0000000000000001, 0x000001000a28442c, 0x0000000000000000)
00:00000:00782:2005/05/27 14:30:41.09 kernel  pc: 0x00000000801d5c5c xls_sessionid+0x30(0x000001007691a630, 0x000001000a28442c, 0x00000100469f0a80, 0x0000000080eec9b8, 0x000000000000012
00:00000:00782:2005/05/27 14:30:41.09 kernel  [Handler pc: 0x000000008033e924 getdoerr installed by the following function:-]
00:00000:00782:2005/05/27 14:30:41.09 kernel  pc: 0x00000000801b3fc8 rec_undo_session+0x2d0(0x000001007691a630, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000, 0x0000000000000004)
00:00000:00782:2005/05/27 14:30:41.09 kernel  pc: 0x000000008033411c abort__all+0x4c(0x000001007691a630, 0x000001006092a108, 0x0000000000000000, 0x0000000000000000, 0x000001000a28472
00:00000:00782:2005/05/27 14:30:41.09 kernel  pc: 0x00000000801b48c8 xact__rollbackxact+0x2a8(0x000000000000a4c0, 0x00000100609345c8, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000)
00:00000:00782:2005/05/27 14:30:41.09 kernel  pc: 0x000000008030b1f4 xact__rollback_local+0x3c(0x000001000a284990, 0x000001006092a108, 0x00000000810e1400, 0x0000000080210e90, 0x0000000080222784)
00:00000:00782:2005/05/27 14:30:41.09 kernel  [Handler pc: 0x0000000080210e90 cleanerr installed by the following function:-]
00:00000:00782:2005/05/27 14:30:41.09 kernel  [Handler pc: 0x00000000802222a4 hdl_backout installed by the following function:-]
00:00000:00782:2005/05/27 14:30:41.09 kernel  pc: 0x00000000801cbaf8 kill_proc+0x474(0x000000000000a800, 0x0000010060934950, 0x0000000000004000, 0x00000100609345b0, 0x00000100609345b
00:00000:00782:2005/05/27 14:30:41.09 kernel  pc: 0x00000000801da31c terminate_process+0x514(0x000001006092a108, 0xffffffffffffffff, 0x0000000000000000, 0x000000000000010f, 0xfffffffffffffffc)
00:00000:00782:2005/05/27 14:30:41.09 kernel  pc: 0x000000008012fb48 plc__flush+0x9a4(0x0000000000000004, 0x0000000000000000, 0x0000000000000000, 0x000000000000129a, 0x0000000000000000)
00:00000:00782:2005/05/27 14:30:41.09 kernel  end of stack trace, spid 782, kpid 1789789311, suid 3593

hobbylu

把number of open objects改的大一点试试看

chuxu

4K memory pool of named cache default data cache ，增加default data cache 的大小。
Deadlock Id 65: Process (Familyid 1639, 1639) (suid 3852) was executing a MAINTENANCE TOKEN command at line 1.
SQL Text: ccur8361。死锁了，检查你的程序吧。
kernel  uasetalarm: no more alarms available 。是否也是和default data cache太小相关呢？

zhouzx_gogo

我试一试！我更加期盼更多的消息


create procedure PR_A
as
begin
....
  EXEC PR_B
....
update ...
end

在上述情况下是否会调用PR_B出错或调用失败