<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Thanks, Stephanie, for your help and to Andrew for his
explanations.</p>
<p>I already thought that there might be a difference between
privileges for frequency list creation and other ad hoc databases,
but I (as a more or less sane person) had not searched at the
bottom of the user page for further privileges. Instead I had
commented out the relevant bit in db-lib.php</p>
<blockquote>
<p># if ($num_of_rows > $table_max)<br>
# {<br>
# unregister_db_process();<br>
# exiterror("The action you have requested uses up
a lot of diskspace.\n"<br>
# . "Your limit is currently set to
$table_max instances.\n"<br>
# . "Please contact your system
administrator if you need access to the information you
requested."<br>
# );<br>
# }</p>
</blockquote>
<p>which did the job. (Or rather, this was done by a more daring
colleague of mine.)<br>
</p>
<p>It seems to me though that – at least in the outdated v3.2.41
running on our server – the $table_max value is effectively
divided by four also for frequency breakdowns. <br>
</p>
<blockquote type="cite"
cite="mid:LO4P265MB34854132B1C4B1D56E6E2674CBE69@LO4P265MB3485.GBRP265.PROD.OUTLOOK.COM">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">This is bizarre because (a) a breakdown of 300,000 matches should have less than 1 mio. instances and (b) the user has been explicitly granted the right to build frequency lists of up to 1 billion tokens.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
The 1,000,000 limit should allow you to do a frequency breakdown of 300,000 matches, but for a collocation database the # of matches is multiplied by a (default) cost factor of 4, giving an effective table size of 1,200,000 > 1,000,000 rows.
</pre>
</blockquote>
<p>With the value being set to 1,000,000, I can create frequency
breakdowns for a query with 241,233 matches – but not for one with
255,249 matches.</p>
<p>Thanks again and all the best,</p>
<p>Philipp<br>
</p>
</body>
</html>