[Info-Ingres] Ingres 6.4(07) urgently required

Roy Hann specially at processed.almost.meat
Thu Nov 15 06:40:57 CST 2007


<james.goodwill at googlemail.com> wrote in message 
news:8d22f941-e27b-4abd-93c0-c4439aa3401c at b32g2000hsa.googlegroups.com...
> Hello there,
>
> Yes, you did read this post correctly! We have a system still running
> Ingres 6.4(07).

That is a bit of a fossil alright.  I suppose there is a good reason you've 
not upgraded?

> Over the last couple of day we've seen the following messages in the
> Ingres error log.
>
> Can anyone suggest a way forward. I've increased the stack size, and
> increased the opf.memory (300,000 bytes * 32 active_sessions). So, the
> rundbms.opt file looks like this:
>
> -names
> -connected_sessions 32
> -active_sessions 32
> -cursors_per_session 1
> -database_count 44
> -stack_size 393216
> -shared_cache
> -fast_commit
> -write_behind 4
> -qsf.pool_size 2097152
> -opf.memory 9600000
>
> Any help would be much appreciated.

You're not exactly pushing the boat out with the resouce allocations.  (I 
bet you've got a DMF cache that can't quite hold the contents of a 3.5" 
floppy disk.)
I don't have a lot to go on but you could try setting psf.memory to 
something generous, maybe -psf.memory=5000000 to start. I would probably 
also double the connect_sessions and active_sessions just on spec.

Roy 




More information about the Info-Ingres mailing list