In years past Oracle client libraries were notoriously leaky. In Oracle 7 it was possible to leak large chunks of memory simply by repeatedly connecting and disconnecting from the database. I've heard third-hand reports of leaks with Oracle 8 libraries, but have no first-hand knowledge.
Try this: To rule out Oracle as the culprit, set up a script that does nothing but connect and disconnect, and note its memory profile over a few hours of running.
Next, set up a script that repeatedly issues the same queries in the same that your production script does, but without storing any results in Perl data structures (this should rule out your code as the source of the leaks). If this doesn't demonstrate a leak, the culprit is your code. If it does show a leak, try some of the advice above (finish your queries, etc.)
Oh, and verifying that you're running the latest Oracle client libraries is usually a good idea.
In reply to Re: any way to control a memory leak
by dws
in thread any way to control a memory leak
by rdww
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |