DB2 UDB ESE V8.1 (64bit) + fp2 on AIX5L
I kept fighting with this error and finally I got tired.

$ db2 "runstats on table blah.blah with distribution and detailed
indexes all"
SQL2310N The utility could not generate statistics. Error "-930" was
returned.

===========
2003-07-25-11.12.13.516092 Instance:xxxxxx Node:000
PID:34882(db2agent (xxxxxxx) 0) TID:1
Appid:*LOCAL.xxxxxx.0823B5154618
oper system services MemAllocate Probe:203 Database:xxxxxx
OS memory allocation (malloc()) failure.
errno =
0x0FFFFFFFFFFF2D60 : 0x0000000C
=============

How much memory does this utility try to get? ???
There is at least 6G physical memory left and my pageing space is 2G (I
don't need a big one).

Does anyone have any idea?
BTW, I need the detailed statistics information.

================================
$ db2 ? sql0930


SQL0930N There is not enough storage available to process the
statement.

Explanation:

A request was made to the database that required another memory
page but no more pages are available to the database manager.

The statement cannot be processed.

User Response:

Possible solutions include:

o Verify that your system has sufficient real and virtual
memory.

o Remove background processes.

o If the error occurs during DUOW resynchronization, increase
the maxagents and reduce the resync_interval database
manager configuration parameter values.

o If the error occurs on a statement which referenced a routine
(UDF, stored procedure or method), it may be that the storage
required to contain the arguments and return values was more
than the memory available in the system. This might occur if
the routine is defined with BLOB, CLOB, DBCLOB parameters or
return values, having a large size (2GB for example).



If the possible solutions listed above do not solve the problem,
it may be necessary to consider changing the definition of the
routine.

sqlcode : -930

sqlstate : 57011


Regards,
Fan Ruoxin

I'd play around here :

db2mtrk executable/memory tracker. (available on unix?)
Statistics Heap has max size of 18120704 bytes

GET DB CFG FOR ...
Statistics heap size (4KB) (STAT_HEAP_SZ) = 4384

PM

"Fan Ruo Xin" <fanruox (AT) sbcglobal (DOT) net> a écrit dans le message de news:
3F343794.352CD8CA (AT) sbcglobal (DOT) net...

Thank you, PM.

I believe the value of db cfg statistics heap is only a SOFT LIMIT,
which should not cause my runstats fail. Anyway I still use the maximum
allowed heap size and failed with the same error.

I found the reason - that because one of the indexes I created is based
on a generated column. Even the value of generated column is based on
the other column(s). But they are still physical stored, right? It is
hard to understand why runstats needs to malloc(a_big_size)???

I am really wondering why I am the first person who eats the crab.

Regards,
Fan Ruoxin

================================================== =====

From: PM \(pm3iinc-nospam\) (Pm3iinc.NoSpam (AT) sympatico (DOT) ca)

Subject: Re: runstats and error code 930

Date: 2003-08-08 21:48:11 PST



I'd play around here :

db2mtrk executable/memory tracker. (available on unix?)

Statistics Heap has max size of 18120704 bytes



GET DB CFG FOR ...

Statistics heap size (4KB) (STAT_HEAP_SZ) = 4384



PM



================================================== ==============

From: Fan Ruo Xin (fanruox (AT) sbcglobal (DOT) net)

Subject: runstats and error code 930

Date: 2003-08-08 17:02:09 PST



DB2 UDB ESE V8.1 (64bit) + fp2 on AIX5L

I kept fighting with this error and finally I got tired.



$ db2 "runstats on table blah.blah with distribution and detailed
indexes all"

SQL2310N The utility could not generate statistics. Error "-930" was
returned.



===========

2003-07-25-11.12.13.516092 Instance:xxxxxx Node:000

PID:34882(db2agent (xxxxxxx) 0) TID:1

Appid:*LOCAL.xxxxxx.0823B5154618

oper system services MemAllocate Probe:203 Database:xxxxxx

OS memory allocation (malloc()) failure.

errno =

0x0FFFFFFFFFFF2D60 : 0x0000000C

=============



How much memory does this utility try to get? ???

There is at least 6G physical memory left and my pageing space is 2G.



Does anyone have any idea?

BTW, I need the detailed statistics information.

Hello, Matt,

I load about 120,000,000 records into the table. My DDL is like the following:

CREATE TABLE xxx.xxx (
...
t_date date,
...
y1 int generated always as (year(t_date))

) ...

I think I know why db2 runstats need a big memory size to collect index
distribution statistics information. This is because the column - generated
column - is not a physical column, it is a VIRTUAL column, which never be
stored in the TABLE DATA PAGE(S).

I would not believe this. WHAT DOES THE PRE-CACULATE MEAN???

Regards,
Fan Ruoxin


Matthew Emmerton wrote: