In article <Pine.SOL.3.91.950717092239.5112A-100000@iglou.iglou.com>
ris@iglou.com "Lucky Leavell" writes:
> On Mon, 17 Jul 1995, Sally Woolrich wrote:
>
> > In article <3u0ps7$1vf@access5.digex.net>
> > briang@access5.digex.net "Brian G." writes:
> >
> > > <big snip>
> > > >You could have exceeded max. files open per process, which won't show
> > > >in 'sar -v' so far as I know, though it DOES show if you are out of UNIX
> > > >locks.
> > >
> > > The kernel currently supports 60 open files per process. How many
> > > does the Unix version open to do transactions? I'm only updating two
> > > tables in the code?
> >
> > You could use the 'fuser' command to check to see just which UNIX
> > files the process (the 'sqlexec' one) has open. Certainly each
> > database table (SE) will be two open files.
> >
> PMJI, but doesn't Informix use "raw" partitions for their DB tables? If
> so, then only temporary working files would use up locks (FLCKREC). I
> use the CA-INGRES RDBMS which does use OS files and we've never
> experienced any problems with per process file limits (MAXUP) or locks.
> (I suppose an Informix internals expert could clear this up for us.)
>
Above all applies to SE not OL. I presume from the original post that
they were using SE as the error seemed to be that sort of error. If they
are using OL, over to the OL exports ;-)
--
============================================================================
Sally Woolrich | This mail contains my personal
sally@excelsis.demon.co.uk | views not those of my employer!
============================================================================