[Info-ingres] Weird problem in Ingres 10

[Laframboise, André (BAC/LAC)]

Easiest way to check for rules is checking the rule catalog table.

select * from iirules where table_name='YOUR_TABLE_NAME';



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 Mark
Sent: Wednesday, May 16, 2018 11:08 AM
To: info-ingres at lists.planetingres.org
Subject: Re: [Info-ingres] Weird problem in Ingres 10

On Wed, 16 May 2018 07:54:00 -0400, Karl and Betty Schendel <schendel at kbcomputer.com> wrote:

>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.

Thanks for your help, Karl.  There should not be any rules on the table but I've no idea how to check.  This is all getting way beyond my knowledge.  Anyway I've looked at articles about enabling SC930 tracing but I don't see any output since I made the changes.

We have the II_SC930_LOC environment variable set to a valid directory and I have added "SET TRACE POINT SC930 1" to the code, but no files appear in the II_SC930_LOC directory and stdout has the following:

"trace directory has not been set or is invalid, tracing will not be enabled.
Please enter 'SET TRACE RECORD <logdir>' or set II_SC930_LOC and re-try."

I will try to get some help from Ingres themselves, if possible!

--
<insert witty sig here>
_______________________________________________
Info-ingres mailing list
Info-ingres at lists.planetingres.org
http://lists.planetingres.org/mailman/listinfo/info-ingres