[Info-ingres] Weird problem in Ingres 10

Karl and Betty Schendel schendel at kbcomputer.com
Wed May 16 11:54:00 UTC 2018


On May 16, 2018, at 7:44 AM, Mark <i at dontgetlotsofspamanymore.net> wrote:
> 
> On Tue, 15 May 2018 12:27:09 -0400, Karl and Betty Schendel
> <schendel at kbcomputer.com> wrote:
> 
>> It's certainly not something I have heard of or seen before.  Do you have any rules
>> defined on the relevant tables?  Try enabling LOG_TRACE if the problem is
>> sufficiently predictable, or do a logdump after the problem occurs if it's not;
>> the idea being to try to see whether you actually got any PUT (insert) or
>> REP (replace) log records that were then rolled back, or whether the insert / update
>> was never executed at all.
> 
> After enabling log_trace all I got was:
> 
>    LOG: SAVEPOINT   Size written/reserved:      0/     0  Flags:
> -------------------------------------------------------------------

So the insert/update isn't ever being executed.  Either it's failing with some sort of
silent error, which would seem odd, or it's not reaching the backend at all, or
it's being pre-empted by a before rule.  I think the next step would be to enable
sc930 tracing and see if the backend is getting the insert-update, and what
end-of-query status it's recording.  There should be KB articles on enabling
SC930 tracing.

Karl




More information about the Info-ingres mailing list