[Info-ingres] Weird problem in Ingres 10

[Laframboise, André (BAC/LAC)]

You can also get similar information with GCC tracing.

André Laframboise

Conseiller Principal Base de Données, Direction générale de l'Innovation et du Dirigeant principal de l'information
Bibliothèque et Archives Canada / Gouvernement du Canada
andre.laframboise at canada.ca / Tél. : 613-298-1346

Senior Database Advisor, Innovation and Chief Information Officer Branch
Library and Archives Canada / Government of Canada
andre.laframboise at canada.ca / Tel: 613-298-1346

-----Original Message-----
From: info-ingres-bounces at lists.planetingres.org <info-ingres-bounces at lists.planetingres.org> On Behalf Of Adrian Williamson
Sent: Wednesday, May 16, 2018 8:25 AM
To: 'Karl and Betty Schendel' <schendel at kbcomputer.com>; 'Ingres and related product discussion forum' <info-ingres at lists.planetingres.org>
Subject: Re: [Info-ingres] Weird problem in Ingres 10

Hi,

If are you running in a client server mode i.e. using Ingres net - you would be able to quickly setup a packet capture using something like WireShark.

Sniffers never lie.

<Crawls back under stone.>

Cheers

Adrian


-----Original Message-----
From: info-ingres-bounces at lists.planetingres.org
<info-ingres-bounces at lists.planetingres.org> On Behalf Of Karl and Betty Schendel
Sent: 16 May 2018 12:54
To: Ingres and related product discussion forum <info-ingres at lists.planetingres.org>
Subject: Re: [Info-ingres] Weird problem in Ingres 10

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

_______________________________________________
Info-ingres mailing list
Info-ingres at lists.planetingres.org
http://lists.planetingres.org/mailman/listinfo/info-ingres

_______________________________________________
Info-ingres mailing list
Info-ingres at lists.planetingres.org
http://lists.planetingres.org/mailman/listinfo/info-ingres