Unreleased locks would not, however, cause "available memory exceeded"
messages. What you get is <mumble mumble memory failing> something
along the lines of "lock threshold reached." Available memory exceeded
usually, in my experience, is caused by a program building a huge
string, like a dynamic array.
--
Regards,
Clif
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
W. Clifton Oliver, CCP
CLIFTON OLIVER & ASSOCIATES
Tel: +1 619 460 5678 Web: www.oliver.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
On Jun 28, 2004, at 11:26, Dan Fitzgerald wrote:
Recently we encounter a process of running 900,000
records and every internal of around 200,0000 record the process
terminated
and prompt this error message<<
Given just this much information, I'd start by looking at locks being
held and not released by this process. How many entries when you do a
"LIST.READU EVERY" during the run? If it's growing, then look in the
code for where a READU isn't released by a WRITE or RELEASE.
Of course, as a vipassana meditator, I'd love to come over and show
you how to troubleshoot this... ;)
"Our greatest duty in this life is to help others. And please, if you
can't help them, could you at least not hurt them?" - H.H. the Dalai
Lama
"When buying & selling are controlled by legislation, the first thing
to be bought & sold are the legislators" - P.J. O'Rourke
Dan Fitzgerald
-------
u2-users mailing list
[EMAIL PROTECTED]
To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
[EMAIL PROTECTED]
To unsubscribe please visit http://listserver.u2ug.org/
