Talk About Network

Google


Register and Login
Nick
Password
Register create new account Sign up is FREE and you can post replies, new topics, bookmark posts and more!
Recover lost password


Data Bases > Ingres > [Info-Ingres] Q...
Latest [ Topics | Posts ] Archive Post A New Topic Post a Reply
<< Topic < Post Post 1 of 1 Topic 5974 of 6093
Post > Topic >>

[Info-Ingres] Query crashes server with E_UL000B_NOT_ALLOCATED

by "Martin Bowes" <martin.bowes@[EMAIL PROTECTED] > Jul 14, 2008 at 02:23 PM

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8E5B4.BE36A8A0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Hi Everyone,

=20

II 9.0.4 (a64.lnx/105)NPTL + patch12707

=20

I have a horriblly long query which generates E_UL000B_NOT_ALLOCATED.
The query is using a series of case statements to pivot a table. There
is one case statement per column.

eg select pid

    , max(case when name=3D'sv1' then value end) as sv1

    ,max(case when name=3D'sv7' then value end) as sv7

    ,max(case when name=3D'sv8' then value end) as sv8

    ,max(case when name=3D'sv9' then value end) as sv9

    ,max(case when name=3D'sv10' then value end) as sv10

    ,max(case when name=3D'sv11' then value end) as sv11

    ,max(case when name=3D'sv12' then value end) as sv12

    ,max(case when name=3D'sv13' then value end) as sv13

    ,max(case when name=3D'sv15' then value end) as sv15

etc...

from string_value_best_case=20

where mod(pid,10)=3D1

group by pid;

=20

If the query has <=3D40 case statements it works fine. But if it has >40
it crashes (and occasionally takes out the server)  with the following
in the errlog:

E_UL000B_NOT_ALLOCATED   Attempt to perform some ULM operation on a
memory pool that was not  allocated by you.

E_QE009C_UNKNOWN_ERROR   Unexpected error received from another
facility.  Check the server error log.

E_UL000B_NOT_ALLOCATED   Attempt to perform some ULM operation on a
memory pool that was not  allocated by you.

E_QE009C_UNKNOWN_ERROR   Unexpected error received from another
facility.  Check the server error log.

E_SC0216_QEF_ERROR   Error returned by QEF.

E_SC0206_CANNOT_PROCESS  An internal error prevents further processing
of this query.=20

 Associated error messages which provide more detailed information about
the problem can be found in the error log, II_CONFIG:errlog.log

=20

Now here's the kicker...

The basic query has been working fine with much higher numbers of
columns when their data type has been integers, dates and float4. But
when I switched the query to work on varchar(25) types it has suddenly
developed this limit.

=20

Anyone got any ideas what might be causing this and how to fix it?

=20

In the meantime I'm going to try and bump the QEF memory and see if that
helps....

=20

Martin Bowes


------_=_NextPart_001_01C8E5B4.BE36A8A0
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml"
=
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @[EMAIL PROTECTED]
 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
..MsoChpDefault
	{mso-style-type:ex****t-only;}
@[EMAIL PROTECTED]
 Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-GB link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal>Hi Everyone,<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>II 9.0.4 (a64.lnx/105)NPTL + =
patch12707<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>I have a horriblly long query which generates =
E_UL000B_NOT_ALLOCATED.
The query is using a series of case statements to pivot a table. There =
is one
case statement per column.<o:p></o:p></p>

<p class=3DMsoNormal>eg select pid<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp; , max(case when name=3D'sv1' =
then value
end) as sv1<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp; ,max(case when name=3D'sv7' then =
value end)
as sv7<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp; ,max(case when name=3D'sv8' then =
value end)
as sv8<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp; ,max(case when name=3D'sv9' then =
value end)
as sv9<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp; ,max(case when name=3D'sv10' =
then value
end) as sv10<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp; ,max(case when name=3D'sv11' =
then value
end) as sv11<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp; ,max(case when name=3D'sv12' =
then value
end) as sv12<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp; ,max(case when name=3D'sv13' =
then value
end) as sv13<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp; ,max(case when name=3D'sv15' =
then value
end) as sv15<o:p></o:p></p>

<p class=3DMsoNormal>etc&#8230;<o:p></o:p></p>

<p class=3DMsoNormal>from string_value_best_case <o:p></o:p></p>

<p class=3DMsoNormal>where mod(pid,10)=3D1<o:p></o:p></p>

<p class=3DMsoNormal>group by pid;<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>If the query has &lt;=3D40 case statements it works =
fine. But
if it has &gt;40 it crashes (and occasionally takes out the server) =
&nbsp;with
the following in the errlog:<o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-left:36.0pt'><span =
style=3D'font-size:9.0pt;
color:red'>E_UL000B_NOT_ALLOCATED&nbsp;&nbsp; Attempt to perform some =
ULM
operation on a memory pool that was not&nbsp; allocated by =
you.<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-left:36.0pt'><span =
style=3D'font-size:9.0pt;
color:red'>E_QE009C_UNKNOWN_ERROR&nbsp;&nbsp; Unexpected error received =
from
another facility.&nbsp; Check the server error =
log.<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-left:36.0pt'><span =
style=3D'font-size:9.0pt;
color:red'>E_UL000B_NOT_ALLOCATED&nbsp;&nbsp; Attempt to perform some =
ULM
operation on a memory pool that was not&nbsp; allocated by =
you.<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-left:36.0pt'><span =
style=3D'font-size:9.0pt;
color:red'>E_QE009C_UNKNOWN_ERROR&nbsp;&nbsp; Unexpected error received =
from
another facility.&nbsp; Check the server error =
log.<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-left:36.0pt'><span =
style=3D'font-size:9.0pt;
color:red'>E_SC0216_QEF_ERROR&nbsp;&nbsp; Error returned by =
QEF.<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-left:36.0pt'><span =
style=3D'font-size:9.0pt;
color:red'>E_SC0206_CANNOT_PROCESS&nbsp; An internal error prevents =
further
processing of this query. <o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-left:36.0pt'><span =
style=3D'font-size:9.0pt;
color:red'>&nbsp;Associated error messages which provide more detailed =
information
about the problem can be found in the error log, =
II_CONFIG:errlog.log<o:p></o:p></span></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Now here's the kicker&#8230;<o:p></o:p></p>

<p class=3DMsoNormal>The basic query has been working fine with much =
higher
numbers of columns when their data type has been integers, dates and =
float4.
But when I switched the query to work on varchar(25) types it has =
suddenly
developed this limit.<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Anyone got any ideas what might be causing this and =
how to
fix it?<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>In the meantime I'm going to try and bump the QEF =
memory and
see if that helps&#8230;.<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Martin Bowes<o:p></o:p></p>

</div>

</body>

</html>

------_=_NextPart_001_01C8E5B4.BE36A8A0--
 




 1 Posts in Topic:
[Info-Ingres] Query crashes server with E_UL000B_NOT_ALLOCATED
"Martin Bowes"   2008-07-14 14:23:01 

Post A Reply:
  Go here to Signup

AddThis Feed Button


About - Advertising - Contact - Frequently Asked Questions - Privacy Policy - Terms of Use - Signup

Contact
tan12V112 Fri Sep 5 6:39:32 CDT 2008.