I'm using SapDB 7.3.0 Build 040-000-091-740 on RedHat Linux 9.
Here I'm having troubles with user tasks in production, in any time user tasks goes quickly to top of MAXUSERTASKS and then the server stops to respond for new COMMUNIC threads, the only way is to change database to off-line then to warm again, this is a reinstalation after a server HD crash, but the RedHat Linux and SapDB are the same versions of old crashed instance.
I followed a message (http://lists.mysql.com/maxdb/19368) sended by Markus D�hr, and setup my MAXUSERTASKS from 50 to 100 but the user tasks again goes quickly to top of MAXUSERTASKS.
ps: If I attempt to change this to 150 the server don't start and in knldiag the message appear:
ERR 11330 COREHAND ABORTING due to signal 11
Now I need to solve this, and make sure that this problem don't occur again.
I have a suspect case, checking the knldiag I have follow messages:
MsgID: 11509
Label: COMMUNIC Message-Text: Connection broken by appl state 10 T74
MsgID: 53214 Label: B*TREE Message-Text: SET READ ONLY: 1A00 FFFFFFFFFFFF0605
What this messages explain? What is the possible ways to USER TASKS increase quickly? There is way to check what a USER TASK it is executing?
another tips?
Thanks for any help
Clovis
-- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
