Undocumented Sybase errors (error: 335)

Bret_Halford

2009-11-17 18:33:14 UTC

Post by Daoud
20, State: 1
04:00000:00393:2009/11/16 14:06:13.55 server Internal error: bitmap
allocation inconsistency, please contact Sybase Technical Support.
I can't find anything about this error in Sybase documentation. The
only thing I found at all was a brief mention in a Sybase CR list for
15.0.3 found athttp://www.sybase.com/detail?id=1063632
"An error 335 could be raised during a select-into statement when
proxy tables with unique indexes are present."
Anyone know more about this error? Or where I can find some
documentation? I admit, in my 6 years administering Sybase
11.9.2/12.5/15.0 ASE servers, I have found the official Sybase
documentation and website to be horribly lacking.

335 is a fairly new error, although I'm not sure exactly when it was
created,
it doesn't exist in the 1502 installmessages script, but does in the
1503.
It certainly was created after the publication of the current edition
of the
Troubleshooting / Error Messages Guide.

I don't think there would be much more to write about it though. The
bitmap
mentioned is an internal memory structure used by the optimizer. The
message
appears to have been added as a sanity check for an event that
shouldn't
happen, that there would be no known cause for. So the direction to
contact
tech support is about the only advice that can be given. There aren't
any obvious
configuration changes we can recommend to avoid the error as the cause
is unknown.

As it happens, there was a bug that caused the error to be raised. It
happened
when the proxy table was empty; the optimizer dropped a reference to
the table
without updating the bitmap. This was only figured out because
someone hit
the problem and reported it to tech support. That bug has now been
fixed (in 1503 ESD 2)
and we once again in the position that we don't know the cause should
the
error occur on a version of ASE where the known bug is fixed and so
the thing
to do is report the error to tech support.