Rod Anderson
Member
First time poster. I applogize in advance if I missed anything of value.
10.2A Linux
Issue: srt file hits 2 gig and crashes (this is not an index build).
I have a new program that has to make calls to a fairly old "processing engine" as they call it that might run through 8-10 scenarios (calling a 'C' program) and eventually returning the recommended formula based on data that I pass it.
The good is it's worked in the lab for about two months.
The bad is that as soon as I hooked it up for a pilot it failed (every time) with the described srt file issue.
The known is changes where made to the calling program (which one would think would make it easy to find since I know the stack trace).
The structure is as follows:
<code>
/* my code */
Run GetPointers.p
Run PrepExtract.p (Pass handles)
FOR EACH ttTable EXCLUSIVE-LOCK:
/* I can't touch "ProcessingEngine.p and noticed it was much fast one row at a time */
CREATE bttTable.
BUFFER COPY ttTable TO bttTable.
/* existing code */ RUN ProcessingEngine.p (INPUT-OUTPUT TABLE bttTable).
BUFFER-COPY bttTable TO ttTable.
EMPTY TEMP-TABLE bttTable.
END.
</code>
Some things to note about ProcessingEngine.p. It's old. Lots of shared variables and shared temp-tables. Lot's of shared locks. Lot's of bad guys in general. There are no query's in this old program.
I've:
- Enabled -t
- Enabled client statement caching
- Ran though it with the debugger
- Used the -noautoresultlist startup param even thought I didn't think it would help.
At this point I'm seeing a bunch of letters and numbers on a page. Any suggestions or insults would be very appreciated.
Best Regards and thanks in advance,
Rod Anderson
10.2A Linux
Issue: srt file hits 2 gig and crashes (this is not an index build).
I have a new program that has to make calls to a fairly old "processing engine" as they call it that might run through 8-10 scenarios (calling a 'C' program) and eventually returning the recommended formula based on data that I pass it.
The good is it's worked in the lab for about two months.
The bad is that as soon as I hooked it up for a pilot it failed (every time) with the described srt file issue.
The known is changes where made to the calling program (which one would think would make it easy to find since I know the stack trace).
The structure is as follows:
<code>
/* my code */
Run GetPointers.p
Run PrepExtract.p (Pass handles)
FOR EACH ttTable EXCLUSIVE-LOCK:
/* I can't touch "ProcessingEngine.p and noticed it was much fast one row at a time */
CREATE bttTable.
BUFFER COPY ttTable TO bttTable.
/* existing code */ RUN ProcessingEngine.p (INPUT-OUTPUT TABLE bttTable).
BUFFER-COPY bttTable TO ttTable.
EMPTY TEMP-TABLE bttTable.
END.
</code>
Some things to note about ProcessingEngine.p. It's old. Lots of shared variables and shared temp-tables. Lot's of shared locks. Lot's of bad guys in general. There are no query's in this old program.
I've:
- Enabled -t
- Enabled client statement caching
- Ran though it with the debugger
- Used the -noautoresultlist startup param even thought I didn't think it would help.
At this point I'm seeing a bunch of letters and numbers on a page. Any suggestions or insults would be very appreciated.
Best Regards and thanks in advance,
Rod Anderson