Infected with 11 again !!
John Green
Not sure if this is helpful but here goes. We were having the same problem with
our Sybase Database Server, we are running Sybase 12.0 on an E10K, getting the
Infected 11 error message and had to bounce our server. It happened 4 times in
a two week period before we discovered what was causing our problem, apparently
Sybase has a limit on the size of IN clauses in SQL queries. If your IN clause
has more than 85 values you will start to run into this problem.
Sybase has a patch to fix this problem, they installed it on our server and so
far it has worked. Our situation has happened at other organizations and this
patch has fixed the problem.
I don't know if your problem is database related, as ours was, but this worked
for us.
JD
Jorge Grijalba wrote:
> Hello all,
>
> We are running sybase 11.9.2.4 on Digital unix 4.0D . We are experiencing
> signal 11 errors followed by a stacktrace in sybase. ALWAYS the server
> hangs and we need to reboot sybase. This happens every seven days more or
> less. I've spoken with sybase tech support and they have seen all the error
> messages and the shared memory dump and they haven't any solution; meaning,
> that it doesn't look like a sybase problem... more like an OS or hardware
> problem. We had Compaq come in and we ran diagnostics on the memory and
> everything checked out. Besides, we've changed Sybase to another similar
> machine and the problem continues.
>
> I ask : Have the problem relation with the O.S. limit for the stack memory,
> I had only 2Mbytes and seven days ago I increased it to 10Mbytes (ulimit
> S.O. command), since that moment Sybase doesn't hang, but It was only seven
> days ago, I have to wait for seven days more at least. I hope it was the
> solution.
>
> This is the part of the ASE error log with the error:
>
> current process (0x5fb0107) infected with 11
> 00:00000:00128:2001/02/26 15:12:37.95 kernel Error at address 0x0 (static
> procedure (no name))
> 00:00000:00128:2001/02/26 15:12:37.95 kernel
> ************************************
> 00:00000:00128:2001/02/26 15:12:37.95 kernel SQL causing error :
> 00:00000:00128:2001/02/26 15:12:37.95 kernel
> ************************************
> 00:00000:00128:2001/02/26 15:12:37.98 server SQL Text:
> 00:00000:00128:2001/02/26 15:12:37.98 kernel curdb = 1 pstat = 0x14000
> lasterror = 4002
> 00:00000:00128:2001/02/26 15:12:37.98 kernel preverror = 0 transtate = 1
> 00:00000:00128:2001/02/26 15:12:37.98 kernel curcmd = 0 program =
> 00:00000:00128:2001/02/26 15:12:38.21 kernel pc: 0x12060fcb0
> pcstkwalk+0x58()
> 00:00000:00128:2001/02/26 15:12:38.24 kernel pc: 0x12060fad0
> ucstkgentrace+0x1d0()
> 00:00000:00128:2001/02/26 15:12:38.24 kernel pc: 0x1205e7a80
> ucbacktrace+0xb8()
> 00:00000:00128:2001/02/26 15:12:38.26 kernel pc: 0x1200a5f08
> terminate_process+0xa20()
> 00:00000:00128:2001/02/26 15:12:38.26 kernel pc: 0x12061dda8
> kisignal+0x120()
> 00:00000:00128:2001/02/26 15:12:38.26 kernel pc: 0x3ff800d5db4
> _call_remove_gp_range+0x3fe5fa071c4()
>
> I appreciated any light that can be shed on this situation
>
> Jorge Grijalba
Jorge Grijalba
A lot of thanks for your information.
We don't have these problem. I have just launched a select with more
than 85 values in the IN Clause and I have no problem.
Thanks
John Green <John_...@transcanada.com> escribió en el mensaje de noticias
3B0ED685...@transcanada.com...