Re: [Info-ingres] OPF_memory logging.

Hi Paul

Well as far as the server is concerned a session hitting the limit of
how much OPF memory it can use is not an error, it's a normal
condition to be handled, business as usual. So the message is rightly
front-end. I'd no more expect to see it in the errlog.log than I would
a duplicate key on insert or constraint violation message.

Now if the server tried to allocate more OPF and failed, or there was
an error reading/writing OPF memory then I'd expect to see that in the
errlog.log.

Now as to whether the errlog.log should be considered the _server(s)_
error log or the _installation_ error log - i.e. should all errors be
logged there, including front-end - is open to debate, but as things
stand it's really the former. Since it's friday I'll now hand it over
to the group to a) tell me why that's the wrong design and b) how
there are all sorts of exceptions now anyway. ;)

Ahh a challenge.

The difference being that the opf_memory is a server tunable
commodity, whereas duplicate key etc are database design, application
specific issues.

Granted the server may have been exhausted due to the number of
active sessions, or the max percentage of memory being too small, but
nonetheless I would still see these as potential server tuning issues and
they should go into a log.

Or at least be configurable to do so - like a lock escalation.

Marty

--
Random Duckman Quote #115:
King Chicken: My morals are beyond reproach and I'll brutally kill
anyone who says otherwise.