SQL0954C Not enough storage is available in the application heap to process the statement. SQLSTATE=57011

[Justin]

Recieved the message: SQL0954C Not enough storage is available in the
application heap to process
the statement. SQLSTATE=57011

After viewing other posts, they recommended changing the applheapsz
(which was completed). We have restarted DB2. The query is not too
complex. The interesting point is that we ran the query yesterday
with no issues. The server we are testing is a new box in which
multiple "break DB2" queries were executed. This includes a cartesion
product that ran for a couple hours.

So, did I break the DB2 internal self memory manager. Queries that
ran yesterday - fail today. Also tried db2 reset database manager
configuration.

Thanks,

jb

[Serge Rielau]

Justin wrote:

Recieved the message: SQL0954C Not enough storage is available in the
application heap to process
the statement. SQLSTATE=57011

After viewing other posts, they recommended changing the applheapsz
(which was completed). We have restarted DB2. The query is not too
complex. The interesting point is that we ran the query yesterday
with no issues. The server we are testing is a new box in which
multiple "break DB2" queries were executed. This includes a cartesion
product that ran for a couple hours.

So, did I break the DB2 internal self memory manager. Queries that
ran yesterday - fail today. Also tried db2 reset database manager
configuration.

Oftentimes running out of application heap is caused by leaks in the
application.
E.g. not closing cursors properly or releasing statement handles...
Which version of DB2 is this anyway?

Cheers
Serge
--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab

[Justin]

We are running DB2 version 9.1 Fix pack 0 on a dell server. OS: Red
Hat Linux

The peculiar thing is that the query has been running for months on
version 8 with no problem. It ran fine on Monday - as I have test
results from the SP. We have stopped and restarted DB2.

We actually pulled the select statement out of the SP. Put the select
statement in a simple file and called it using: DB2 -tvf test.sql.
This gives us the heap error. The heap size is bigger on the machine
that fails ?!?

On Apr 11, 8:46 am, Serge Rielau <[e-mail]:

Justin wrote:

Recieved the message: SQL0954C Not enough storage is available in the
application heap to process
the statement. SQLSTATE=57011

After viewing other posts, they recommended changing the applheapsz
(which was completed). We have restarted DB2. The query is not too
complex. The interesting point is that we ran the query yesterday
with no issues. The server we are testing is a new box in which
multiple "break DB2" queries were executed. This includes a cartesion
product that ran for a couple hours.

So, did I break the DB2 internal self memory manager. Queries that
ran yesterday - fail today. Also tried db2 reset database manager
configuration.

Oftentimes running out of application heap is caused by leaks in the
application.
E.g. not closing cursors properly or releasing statement handles...
Which version of DB2 is this anyway?

Cheers
Serge
--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab

[Justin]

We bumped the app heap size to 12 K and it works. Not satisfied with
the change - but liveable.
Works fine db2 v 8 operating under only 4K.

Testing db2 v9 fix pack 2 - starting today. Not sure if we will come
across similar problems.

On Apr 11, 9:50 am, "Justin" <[e-mail]:

We are running DB2 version 9.1 Fix pack 0 on a dell server. OS: Red
Hat Linux

The peculiar thing is that the query has been running for months on
version 8 with no problem. It ran fine on Monday - as I have test
results from the SP. We have stopped and restarted DB2.

We actually pulled the select statement out of the SP. Put the select
statement in a simple file and called it using: DB2 -tvf test.sql.
This gives us the heap error. The heap size is bigger on the machine
that fails ?!?

On Apr 11, 8:46 am, Serge Rielau <[e-mail]:

Justin wrote:

Recieved the message: SQL0954C Not enough storage is available in the
application heap to process
the statement. SQLSTATE=57011

After viewing other posts, they recommended changing the applheapsz
(which was completed). We have restarted DB2. The query is not too
complex. The interesting point is that we ran the query yesterday
with no issues. The server we are testing is a new box in which
multiple "break DB2" queries were executed. This includes a cartesion
product that ran for a couple hours.

So, did I break the DB2 internal self memory manager. Queries that
ran yesterday - fail today. Also tried db2 reset database manager
configuration.

Oftentimes running out of application heap is caused by leaks in the
application.
E.g. not closing cursors properly or releasing statement handles...
Which version of DB2 is this anyway?

Cheers
Serge
--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab- Hide quoted text -

- Show quoted text -

[Serge Rielau]

Justin wrote:

We bumped the app heap size to 12 K and it works. Not satisfied with
the change - but liveable.
Works fine db2 v 8 operating under only 4K.

Testing db2 v9 fix pack 2 - starting today. Not sure if we will come
across similar problems.

I'm no expert on that topic, but I'd look into db2pd and the db2 memory
tracker as candidates to get to the bottom of this.

Cheers
Serge

--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab