Memory error

[Jim_McKinney]

In retrospect, I concur with Hein that pgflquo is the more likely culprit here.

[Jorge Cocomess]

Hi,

I stopped and restarted the process. So far, I am not seeing any errors. This is an in-house accounting application.

Thanks everyone. You're the best!!

[Jan van den Ende]

Jorge,



I saw the error in the batch log.


and


I stopped and restarted the process. So far, I am not seeing any errors.


Am I correct then that this is a continuously-running batch job?

If so, there are just two possibilities:
1), Your job happened to have to deal with a chunk of processing that was unusually big (for whatever reason). That means it is likely to happen again whenever a similar load is to be dealt with.
Raising PGFLQUO would greatly reduce the risk of this happening again.
2), there is some slow-creeping memory leak: allocated memory is not (completely) freed after the need, and upon repeat of the functionality a fresh chunk is allocated.
Now there really are only 2 solutions: the fundamentally correct of locating the incorrect dealloc and repair it, or the much simpler: regelarly restart, in a frequency high enough that the accumulated wasted memory does not yet hit the limit.
Especially for batch processes this is rather simple to automate, eg on a dayly or weekly basis.

hth

Proost.

Have one on me.

jpe