Memory Errors

[John Esak]

Hi,
Yes, seems so different now that this place and the FP Room aren't seemingly
24 hour deals.  We actually make appointments to go into the FP Room now. At
least that keeps the core group talking now and again.

I wish I had an answer for you. Have you used the system arrays which tell
you how many open files and filePro files, etc. are active at that precise
WRITE.  It obviously is a specific WRITE like "WRITE alisa".  I wonder if
doing a generic CLOSE just before the WRITE would do anything.  Of course
opening the next files will take a bit longer, but if it clears up the
problem until you can figure out what it is... Why not.

JOhn 

> -----Original Message-----
> From: filepro-list-bounces+john=valar.com at lists.celestial.com 
> [mailto:filepro-list-bounces+john=valar.com at lists.celestial.co
m] On Behalf Of Nancy Palmquist
> Sent: Tuesday, October 20, 2009 5:58 PM
> To: filePro List
> Subject: Memory Errors
> 
> I need some suggestions.  On a Windows Server 2003, with XP 
> clients, we 
> have a situation that keeps returning.  We are running 
> filePro 5.0 and 
> filePro 5.0 Odbc versions on this system.
> 
> Dclerk is throwing memory errors at a point in the processing where I 
> open a file, change one piece of data and write the data.  
> The data is 
> included in 2 indexes.  I know if we rebuild these two indexes the 
> memory errors go away for some time.
> 
> The indexes in the file that throws the memory errors are 
> rebuilt every 
> night, so we start with clean indexes each day.  Once it 
> throws a memory 
> error, it seems that we start getting them often until we can rebuild 
> the indexes.
> 
> I have narrowed the logic that causes the memory errors to a 
> very narrow 
> 4 lines.
> 
> Open a file with a protect (lock).
> 
> write the one piece of data
> 
> WRITE the file to send the data and unlock the record.
> 
> The Write command seems to be what causes the memory error.  The very 
> next line, is not executed.
> 
> I open and update data in the same file many times before 
> this crash.  I 
> actually write all the previous data, and then reopen the same record 
> before this memory error to make sure I had everything working.
> 
> What I suspect:
> 1)  Some kind of I/O issue with the Server.  How can that be tested?  
> Are there logs or something else I can watch to see what is going on?
> 
> 2)  Some kind of switch fault.  We have seen this come and go 
> over the 
> last year, and it always seems to be bad for a while and then 
> a faulty 
> switch is replaced and it works wonderful for months.  How 
> can that be 
> tested?
> 
> I added some SLEEP commands around this logic to try to give 
> the Server 
> time to handle the I/O.  I find that sometimes this helps with issues 
> like this.  filePro is so fast, I think the Windows server 
> can not keep 
> up.  Usually do not see this kind of thing on my Unix/Linux stuff.
> 
> Anyone got an idea or two I can look at?  It would be appreciated.  I 
> really think since it comes and goes, it is more likely to be 
> related to 
> hardware, network, or OS. 
> 
> I have studied the processing many times over the years we have been 
> doing this and I think it would break all the time if I missed 
> something, but I am certainly not perfect so that might also be 
> possible.  ;-)
> 
> Anyway, I am tired of seeing the list so empty.  I feel so all alone 
> these days.
> 
> Nancy
> 
> -- 
> Nancy Palmquist 		MOS & filePro Training Available
> Virtual Software Systems	Web Based Training and Consulting	
> PHONE: (412) 835-9417		   Web site:  http://www.vss3.com
> 
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>